CEN20LA397 · Zenith CH 750
Zenith CH 750 · Accident: fuel exhaustion on approach
From Murray-Calloway County Airport Kyle-Oakley Field (CEY) to Mexico Memorial Airport (MYJ)
Event
- NTSB case
- CEN20LA397
- 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
Zenith CH 750
- Aircraft type
- Zenith CH-750
- 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
- N4744M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Murray-Calloway County Airport Kyle-Oakley Field (CEY), Murray, KYTo Mexico Memorial Airport (MYJ), Mexico, MO
- Aircraft age
- About 3 years (built 2017)
- 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
- Defining eventThe 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
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, the airplane was fueled with 22-23 gallons of fuel before he departed, and the airplane’s fuel consumption rate was about 6 gallons of fuel per hour. He had been airborne about 4 hours and was approaching his destination when the engine sputtered and lost total power. The pilot made a forced landing into rough terrain and the airplane nosed over. Examination of the airplane revealed minimal fuel was onboard, with no leaks of the fuel system. No preimpact anomalies were observed during examination of the engine.
The pilot’s preflight planning notes indicated he considered a fuel stop prior to the destination. After the accident, the pilot stated that the onboard fuel quantity indicating system was unreliable and a fuel stop may have been warranted. The pilot’s decision to proceed to the destination without a fuel stop likely resulted in a total loss of engine power due to exhaustion of usable fuel.
Probable cause
The pilot’s inadequate fuel management and flight planning, which led to a total loss of engine power due to fuel exhaustion and a forced landing into rough terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20LA397
- Event ID
- 20200917X31028
- Case number
- CEN20LA397
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: bf2dc1c246e936042130cb0365da0cb85be1f1353e2a17be5ac6c7916c490745; retrieved 2026-09-16T13:03:18.007Z.