FTW84LA174 · Cessna 150M
Cessna 150M · Accident: total loss of engine power (non-mechanical) en route
From Halliburton Field (DUC) to an unrecorded destination
Event
- NTSB case
- FTW84LA174
- 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 150M
- 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
- N6494K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Halliburton Field (DUC), Duncan, OKTo 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
- 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
- Destroyed
Cause areas
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel supply, misjudged
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ENG LOST POWER FROM FUEL EXHAUSTION BEFORE THE PLT REACHED HIS FINAL DESTINATION. DURING A SUBSEQUENT EMERGENCY LANDING AT NIGHT THE ACFT COLLIDED WITH A FENCE AS IT WAS TOUCHING DOWN. THE PLT STATED THAT HE ESTIMATED THERE WAS 1.5 GALS OF USABLE FUEL ON BOARD WHEN THE ENG STOPPED & THAT THE FUEL GAGES INDICATED THAT THERE WAS ABOUT THAT MUCH REMAINING. THE PLT BELIEVED THAT USE OF THE SHOULDER HARNESSES SPARED HIM & THE PASSENGER FROM INJURY. IN HIS WRITTEN STATEMENT, THE PLT RELATED THAT AN INTERMEDIATE STOP FOR FUEL WOULD HAVE COST 'TOO MUCH IN TIME & MONEY' & HE SAW NO REASON TO TERMINATE THE FLT. HE OVERFLEW SEVERAL SUITABLE REFUELING POINTS IN ORDER TO REACH HIS DESTINATION NON-STOP.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW84LA174
- Event ID
- 20001214X39041
- Case number
- FTW84LA174
- 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 1984-03-26.
- API snapshot SHA-256: d31bf5172d4581c1fad6c5ffec4ef3ba8ea96ff59cd2be2e37d90e5bc08e626e; retrieved 2026-09-23T20:42:22.696Z.