FTW93LA129 · Cessna 150K
Cessna 150K · Accident: total loss of engine power (non-mechanical) on approach
From F67 · Grand Prairie, TX to an unrecorded destination
Event
- NTSB case
- FTW93LA129
- 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 150K
- Aircraft type
- Cessna 150
- 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
- N6099G
- Operator
- Senter, Jossete · private individual
- Onboard fatalities
- Unknown
- Route
- From F67 · Grand Prairie, TXTo 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
- Approach · VFR pattern final
- 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 › Refueling, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PRIVATE PILOT HAD FLOWN APPROXIMATELY TWO HOURS AND FORTY FIVE MINUTES AND WHEN CLEARED FOR LANDING AT HIS DESTINATION, HE REPORTED TO THE CONTROL TOWER THAT THE AIRPLANE WAS RUNNING OUT OF FUEL. HE THEN REPORTED THE ENGINE HAD QUIT AND HE DID NOT THINK HE COULD MAKE THE RUNWAY FROM HIS CURRENT ALTITUDE OF 1,800 FEET MSL. THE AIRPLANE LANDED HARD APPROXIMATELY 1,331 FEET FROM THE END OF RUNWAY 17. THE NOSE GEAR COLLAPSED UPON IMPACT AND THE AIRPLANE TRAVELED APPROXIMATELY 17 FEET WHERE IT NOSED OVER ONTO ITS BACK. NO FUEL WAS FOUND IN THE FUEL TANKS AND NO LEAKAGE WAS REPORTED BY AIRCRAFT RESCUE AND FIRE FIGHTING PERSONNEL. THE CARBURETOR'S VENTURI WAS FOUND TO BE DIRTY
Probable cause
FUEL EXHAUSTION INDUCED POWER LOSS AND THE PILOT'S FAILURE TO REFUEL. A FACTOR WAS THE EXISTING NIGHT CONDITIONS
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW93LA129
- Event ID
- 20001211X12141
- Case number
- FTW93LA129
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1993-04-13.
- API snapshot SHA-256: 242637dafc3bc4089d304852ece44ad321b9fb2346df49a46da4299079d76cef; retrieved 2026-09-21T22:59:32.619Z.