CEN25LA051 · Cessna 340 A
Cessna 340 A · Accident: fuel exhaustion on approach
From Mission Field (LVM) to Muskogee-Davis Regional Airport (MKO)
Event
- NTSB case
- CEN25LA051
- 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 340 A
- Aircraft type
- Cessna 340
- 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
- N5757C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mission Field (LVM), Livingston, MTTo Muskogee-Davis Regional Airport (MKO), Muskogee, OK
- Aircraft age
- About 44 years (built 1980)
- 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
- 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 › Action/decision
- Personnel issues › Experience/knowledge
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that the airplane was “topped off” with fuel before departing on the night cross-country flight. The pilot performed a preflight inspection, but he did not have his headlamp with him, only his cellular phone. The pilot reported that he typically verified fuel levels at night by feeling inside the fuel tank with his finger, but recalled not verifying the fuel level in the right main fuel tank before departing on the night of the accident flight. The pilot reported that the fuel consumption rate during the first half of the flight was higher than normal due to his operation of the engines slightly rich and his use of the airplane’s heater. While enroute, the pilot transferred fuel from the auxiliary fuel tanks and the left side locker fuel tank to the main fuel tanks. After the “final transfer” was completed, the pilot calculated that there was adequate fuel remaining, including the required reserve fuel, to reach the destination airport; however, he noticed that the indicated fuel remaining levels were less than he expected. Shortly after the pilot was cleared for a visual approach at the destination, the right engine lost total power, followed by the left engine. The pilot reported that, at the time of the initial power loss, gauges indicated that the left side of the airplane had about 30 pounds (about 4.84 gallons) of fuel remaining and the right side had about 30 to 35 pounds (about 4.84 to 5.65 gallons) of fuel remaining. During the subsequent forced landing, the right wing impacted a permanent elevated static display and the airplane came to rest upright on airport property. The airplane sustained substantial damage to the fuselage and the right wing. Examination of the airplane revealed no evidence of fuel at the accident site. The right main fuel tank and the right auxiliary fuel tank were separated from the right wing during the impact sequence and sustained damage. All other fuel tanks were found intact. All the fuel tank caps were found installed on their respective fuel tank. Fuel was not observed in any of the fuel tanks. All the fuel tank bladders were found intact, and they were not collapsed. The left side fuel selector was found on the left main fuel tank. The right side fuel selector was found on the right auxiliary fuel tank. No signs of fuel leakage were observed on the airframe or on the two engines. During the recovery operation, no usable fuel was recovered from the airplane. It is possible that the pilot departed on the accident flight with less fuel than he calculated, given that he did not verify the level of fuel in the right main tank. Additionally, he reported higher than normal fuel consumption during the accident flight, and as he neared the destination, he observed that the indicated fuel remaining was less than expected. The absence of fuel at the accident site and onboard the airplane during postaccident examination is consistent with the pilot’s improper fuel planning, which resulted in fuel exhaustion, a total loss of power to both engines, a subsequent forced landing, and collision with an obstacle and terrain.
Probable cause
The pilot’s improper fuel planning, which resulted in fuel exhaustion and a total loss of power to both engines.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA051
- Event ID
- 20241127195556
- Case number
- CEN25LA051
- 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, coordinates, 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: 10ed7478f1e6c472d9e4e2d0fdf11ff4e0620ba4e5256f278cd326ae30443307; retrieved 2026-09-16T19:30:32.581Z.