FTW89LA113 · Cessna 152
Cothron Aviation Cessna 152 · Accident: total loss of engine power (non-mechanical) en route
From F54 · Arlington, TX to Tyler Pounds Regional Airport (TYR)
Event
- NTSB case
- FTW89LA113
- 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 152
- Aircraft type
- Cessna 152
- 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
- N24258
- Operator
- Cothron Aviation
- Onboard fatalities
- Unknown
- Route
- From F54 · Arlington, TXTo Tyler Pounds Regional Airport (TYR), Tyler, 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
- En route · cruise
- 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Became lost/disoriented, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PILOT WAS SENT ON A SOLO CROSS-COUNTRY FLIGHT WITH AN AIRPLANE THAT WAS LESS THAN FULL. HE WAS TOLD THAT THE AIRPLANE HAD BEEN FLOWN 1.5 HOURS SINCE IT HAD BEEN TOPPED OFF WITH FUEL. HE FLEW THE AIRPLANE FOR ONE HOUR AND FIFTY MINUTES BEFORE THE ENGINE STOPPED DUE TO FUEL EXHAUSTION AND MADE A FORCED LANDING ON A ROAD. DURING THE LANDING ON THE ROAD, THE AIRPLANE RAN OFF THE SIDE, HIT A DITCH AND THEN A UTILITY POLE. LATER IT WAS DETERMINED THE AIRPLANE HAD BEEN FLOWN 2.5 HOURS BEFORE THE STUDENT PILOT RECEIVED IT FOR HIS FLIGHT. HE WAS ABLE TO KEEP IT AIRBORNE LONGER THAN NORMAL FOR THE AMOUNT OF FUEL HE STARTED WITH. THE STUDENT PILOT STATED HE HAD BEEN UNABLE TO LOCATE HIS AIRPORT DUE TO FLOODED CONDITIONS AND A FAULTY RADIO, AND THAT HE WAS RETURNING TO HIS DEPARTURE AIRPORT WHEN THE ENGINE STOPPED PRODUCING POWER.
Probable cause
STUDENT PILOT INADVERTENTLY BECOMING LOST/DISORIENTED AND EXHAUSTING THE FUEL IN THE FUEL SYSTEM.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW89LA113
- Event ID
- 20001213X28585
- Case number
- FTW89LA113
- 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: 29c3dbbd31acbad9c84795b22c29a3ffcf6e817811d849712f062f2c19dab561; retrieved 2026-09-23T07:31:26.122Z.