Skip to content

Atlas / NTSB / CEN20LA174

NTSB CAROL · Event

Event CEN20LA174

2020-05-06 Gonazales, Texas, United States Airport · T20 None 1 aircraft Status: Completed

Registry · N25HE

FAA Aircraft Registry record.

Make / Model

CESSNA T240

Year of manufacture

2013 · 7 years old at event

Engine

CONT MOTOR TSIO-550-C (310 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

20131217

ADS-B equipped

Yes — Mode-S A255D9

Registrant of record

BNB INDUSTRIES LLC

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's failure to retract the speedbrakes during a delayed go-around attempt, which resulted in a runway excursion.

Factual narrative

On May 6, 2020, about 1650 central daylight time, a Cessna T240 airplane, N25HE, was substantially damaged during a runway excursion after landing at the Roger M. Dreyer Memorial Airport (T20), Gonzales, Texas. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot entered the airport traffic pattern for runway 33 and set the wing flaps to the takeoff (12°) position. The airspeed on final approach was about 130 kts and he extended the speed brakes to reduce the speed. He did not use full landing flaps (40°) because he was concerned about the "strong wind gusts." The airplane touched down approximately one-third of the way down the runway at about 100 kts. The pilot stated he did not believe the airplane would be able to stop on the remaining runway and decided to execute a go-around. He added full engine power and left the flaps at the takeoff (12°) position. He did not recall retracting the speed brakes and noted the airplane seemed to get "no lift." The airplane subsequently departed the runway pavement and came to rest about 200 yards beyond the end of the runway in a field. The pilot commented the go-around could have been initiated earlier. He stated there were no mechanical failures or malfunctions before the accident. Federal Aviation Administration inspectors conducted a postaccident examination of the airplane at the accident site. At the time of the examination, the cockpit speed brake switch was in the UP position. The speed brakes were in the down (retracted) position at that time consistent with the airplane electrical power being off. Recovery personnel confirmed damage to the right wing and engine mount. The airplane flight manual (AFM) noted the speed brakes can be used for glide path control on final approach and airspeed reduction. Both the normal and short field landing checklists specified, "SPD BRK Switch – UP (as desired)" after touching down. The balked landing (go-around) checklist included retracing the speed brakes, "SPD BRK Switch – DN." The amplified landing procedures contained in the AFM did not include any additional guidance related to the use of the speed brakes. According to the airframe manufacturer, the speed brakes are electrically actuated by the cockpit instrument panel mounted switch. They will not retract automatically due to a go-around condition, pressing the go-around button, or throttle lever advancement. The flight manual systems description stated there are three conditions that will automatically retract the speed brakes: if the circuit breaker is pulled, if they deploy asymmetrically, or due to a low voltage electrical condition. The pilot reported landing about one-third of the way down the runway. He did not believe the airplane would be able to stop on the remaining runway and decided to execute a go-around. The pilot added full engine power and left the flaps at the takeoff position. He did not recall retracting the speedbrakes and noted the airplane seemed to get "no lift." The airplane subsequently departed the runway pavement, which resulted in substantial damage to the left wing. Postaccident examination revealed the cockpit speedbrake switch was in the UP position. The airframe manufacturer noted the speedbrakes were actuated by the instrument panel-mounted switch and will not retract automatically due to a go-around condition, by pressing the go-around button, or with throttle lever advancement. The pilot commented the go-around could have been initiated earlier; if so, he may have had more time to fully prepare for a go-around. It is likely that the pilot did not retract the speedbrakes during the delayed go-around attempt, which resulted in a reduction of lift and a subsequent runway excursion. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • C Personnel issues-Action/decision-Action-Delayed action-Pilot - C
  • C Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot - C
  • Personnel issues-Action/decision-Action-Forgotten action/omission-Pilot
  • Aircraft-Aircraft oper/perf/capability-Aircraft capability-Climb capability-Not attained/maintained

Verbatim from NTSB's published report. Source file NTSB_2020_CEN20LA174.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway excursion, go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗