CHI05CA170 · Mooney M20K
Mooney M20K · Accident: total loss of engine power (non-mechanical) on approach
From Miami-Opa Locka Executive Airport (OPF) to Kennett Memorial Airport (TKX)
Event
- NTSB case
- CHI05CA170
- 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
Mooney M20K
- Aircraft type
- Mooney M20
- 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
- N5791U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Miami-Opa Locka Executive Airport (OPF), Miami, FLTo Kennett Memorial Airport (TKX), Kennett, MO
- 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 starvation
- 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 › Starvation
- Pilot in command › In-flight planning/decision, inadequate
- Pilot in command › Preflight planning/preparation, 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 airplane impacted terrain during a final approach to the destination airport. The airplane experienced a total loss of engine power about 1/4 mile from the landing runway and 200-300 feet above ground level. The airplane impacted terrain about 200 feet from the touchdown zone of the landing runway. Inspection of the airplane revealed that the right fuel tank contained less than 6 ounces of fuel and the left fuel tank contained 8.5 gallons of fuel. During the inspection, the left fuel gauge indicated 9 gallons of fuel.
Probable cause
The fuel starvation, inadequate preflight planning and preparation, and inadequate in-flight planning/decision by the pilot.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05CA170
- Event ID
- 20050815X01245
- Case number
- CHI05CA170
- 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: 79b9d0ec15f8c86255ab0743701ab496cda93ff0859876f46c5675e74cd0c0b1; retrieved 2026-09-22T05:40:45.054Z.