Skip to content

Atlas / NTSB / GAA17CA232

NTSB CAROL · Event

Event GAA17CA232

2017-04-11 Houston, Texas, United States Airport · DWH None 1 aircraft Status: Completed

Registry · N92873

FAA Aircraft Registry record.

Make / Model

CESSNA 172M

Year of manufacture

1973 · 44 years old at event

Engine

LYCOMING 0-360 SERIES (180 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

19730412

ADS-B equipped

Yes — Mode-S ACDF4B

Registrant of record

SONDAY TERRANCE P

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot’s delayed attempt to abort the takeoff with a tailwind, which resulted in a runway overrun.

Factual narrative

The pilot of the float-equipped airplane reported that prior to takeoff, the windsock showed "no significant wind" and the control tower "confirmed using a southerly traffic pattern". He added that during the takeoff on the waterway, the airplane initially accelerated as expected. He further added that "it became clear that the take-off run was not progressing as anticipated" and decided to abort the takeoff. He brought the power to idle and applied back pressure to the control yoke. The airplane slid onto the grass embankment at the end of the runway and came to rest on the adjacent taxiway. The airplane sustained substantial damage to the fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Weather observations, located on the airport, showed that from about 20 minutes before the accident to 60 minutes after the accident, the wind varied in direction from 360° to 050°, and the speed varied 4 to 11 knots, with a peak wind of 360° at 30 knots. The pilot departed waterway 17W. The pilot of the float-equipped airplane reported that, before takeoff, the windsock showed "no significant wind" and that the control tower "confirmed using a southerly traffic pattern." He added that, during the takeoff from the waterway, the airplane initially accelerated as expected. He further added that "it became clear that the take-off run was not progressing as anticipated" and that he decided to abort the takeoff. He brought the power to idle and applied back pressure to the control yoke. The airplane slid onto the grass embankment at the end of the runway and came to rest on the adjacent taxiway. The airplane sustained substantial damage to the fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Weather observations from the airport showed that, from about 20 minutes before the accident to 60 minutes after the accident, the wind varied in direction from 360° to 050°, and the speed varied from 4 to 11 knots, with a peak wind from 360° at 30 knots. The pilot departed waterway 17W. 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 Aircraft-Aircraft oper/perf/capability-Aircraft capability-Takeoff distance-Capability exceeded - C
  • C Personnel issues-Action/decision-Action-Delayed action-Pilot - C
  • Environmental issues-Conditions/weather/phenomena-Wind-Sudden wind shift-Effect on operation
  • Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Effect on operation

Verbatim from NTSB's published report. Source file NTSB_2017_GAA17CA232.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. 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 ↗