FTW03LA176 · Cessna 172M
Cessna 172M · Accident: loss of control in flight during landing
From Jack Brooks Regional Airport (BPT) to Jack Brooks Regional Airport (BPT)
Event
- NTSB case
- FTW03LA176
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172M
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N753MF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jack Brooks Regional Airport (BPT), Beaumont, TXTo Jack Brooks Regional Airport (BPT), Beaumont, TX
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command(cfi) › Compensation for wind conditions, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 4,582-hour flight instructor who was occupying the right seat, reduced engine power at mid-field to simulate an engine failure for the 18-hour student pilot that was flying the airplane from the left seat. As the airplane rolled out on final landing. The flight instructor noted that the airplane was "approximately 200 feet high" when the student pilot stated that he felt "uncomfortable." The flight instructor reported that as he took command of the airplane and added full engine power, a gust of wind pushed the airplane to the right and south of the runway. The airplane then struck the ground and bounced. Approximately 80 knots and 60 feet of altitude, the airplane's left wing dropped, and the flight instructor then "chopped the power and fuel." The airplane impacted the ground and come to rest upright off the runway. At the time of the accident, the wind was reported from 120 degrees and 9 knots.
Probable cause
The instructor's delay in executing a go-around and his failure to maintain aircraft control due to inadequate compensation of wind gusts. A contributing factor was the gusty winds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW03LA176
- Event ID
- 20030714X01091
- Case number
- FTW03LA176
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 34758995b8fe795671af8d0027815499e482b7fdabab4da27987130627013bec; retrieved 2026-09-21T09:26:58.331Z.