FTW97LA247 · Cessna 172P
Cessna 172P · Accident: propeller blast or jet exhaust/suction while taxiing
From Fort Worth Meacham International Airport (FTW) to an unrecorded destination
Event
- NTSB case
- FTW97LA247
- 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
- 0
- 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 172P
- 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
- N53795
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fort Worth Meacham International Airport (FTW)To not recorded
- 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
- Taxi
- 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
- Propeller blast or jet exhaust/suction
- 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) › Planning/decision, improper
- Pilot in command(cfi) › Propeller/jet blast encounter, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to a flight instructor (CFI), he taxied a Cessna (N53795) northbound on taxiway A, behind a twin jet transport airplane to takeoff on runway 16L. The twin jet transport airplane turned west and stopped at the hold short line for runway 16L. The CFI stated that he proceeded to taxi behind the jet towards the run up pad. As the Cessna was passing behind the jet, the jet was cleared to takeoff. The CFI further stated that when the 'jet increased [its] throttles, the blast from the added exhaust caught Cessna 795 broadside and tipped it over onto its right wing tip and nose.' The CFI stated that when the 'exhaust blast dissipated, Cessna 795 righted itself.' The pilot shut down the airplane, and evacuated the plane along with the student pilot.
Probable cause
improper planning/decision by the flight instructor (CFI), which resulted in his inadvertent encounter with jet blast from a twin jet transport airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW97LA247
- Event ID
- 20001208X08142
- Case number
- FTW97LA247
- 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. 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: 98ed4d5bb185be85b20d15736d6cc786f77f02ec47a464d1bd930c2600364c4c; retrieved 2026-09-22T19:20:46.503Z.