CEN23LA163 · Cessna 150J
Cessna 150J · Accident: fuel exhaustion en route
From Omar N Bradley Airport (MBY) to Davenport Municipal Airport (DVN)
Event
- NTSB case
- CEN23LA163
- 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
- Event fatalities
- Unknown
- 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
Cessna 150J
- 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
- N60860
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Omar N Bradley Airport (MBY), Moberly, MOTo Davenport Municipal Airport (DVN), Davenport, IA
- Aircraft age
- About 54 years (built 1969)
- 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
- 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
The pilot had completed 3 flight legs immediately before the accident flight without incident. The accident flight proceeded normally until it neared the destination airport. The pilot reported a rapid drop in engine speed as if the throttle control had been abruptly moved to idle. The engine seemed to completely lose power for about 30 to 45 seconds. It then regained a “strong burst” of power. However, about 5 to 10 seconds later, the engine lost power again. His efforts to restore engine power were not successful. He attempted to execute a forced landing to a road; however, a wind gust caused the airplane to impact a light pole before it came to rest on railroad tracks. The nose landing gear collapsed and the airplane was oriented in a nose-down position, with damage to the fuselage, engine mount, and both wings.
Postaccident examination did not identify any engine anomalies consistent with an inability to produce rated power. Both main fuel tanks appeared to be intact; however, both appeared to contain only a minimal amount of fuel. The gascolator bowl contained fuel, which was consistent with the airplane resting in a nose-low attitude after the accident.
The airplane was fully fueled (22.5 gallons useable) before departing initially and was fueled with 20 additional gallons during the previous flights. According to the airplane owner’s manual, the expected fuel consumption varied from about 5.5 gallons per hour (gph) to about 7.0 gph. The pilot reported the engine was leaned as appropriate for all stages of flight.
The pilot also noted that the engine took about 2 minutes to shut down after the mixture control was moved to the idle/cutoff position at 2 of the intermediate stops. This suggests an improperly adjusted mixture control that would have resulted in a slightly rich mixture and higher than anticipated fuel consumption. The pilot also reported the fuel gauges were not reliable as they did not indicate the correct amount of fuel that he visually verified was in the tanks.
The total flight time over the 3 preceding flights and the accident flight was about 6 hours. Based on the lack of fuel onboard the airplane, a total fuel consumption of 42.5 gallons would equate to about 7 gallons per hour, within the range of the published fuel consumption for the airplane. Also, the fuel consumption was likely higher than anticipated due to the improperly adjusted mixture.
Although weather conditions at the time of the accident were conducive to carburetor icing, the loss of engine power as described by the pilot was not consistent with a carburetor icing scenario.
Based on the available information, the engine lost power due to fuel exhaustion. It is likely that a slightly rich mixture increased the fuel consumption from that anticipated by the owner’s manual.
Probable cause
A loss of engine power due to fuel exhaustion as a result of the pilot’s inadequate preflight planning. Contributing to the accident were the unreliable fuel quantity gauges and the improperly adjusted mixture control, which increased the fuel consumption above that anticipated by the owner’s manual.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA163
- Event ID
- 20230424107106
- Case number
- CEN23LA163
- 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: bd1e55cc1361262f832d5374d114ffe0c9effc8642e8b9e4e4719d5732aec3d4; retrieved 2026-09-16T17:32:11.412Z.