CEN18FA384 · Cessna 150 H
Cessna 150 H · Accident: fuel exhaustion on approach
From Greensburg Municipal Airport (I34) to FES · Festus, MO
Event
- NTSB case
- CEN18FA384
- 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
- 2 · 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
Cessna 150 H
- 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
- N7152S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Greensburg Municipal Airport (I34), Greensburg, INTo FES · Festus, MO
- Aircraft age
- About 50 years (built 1968)
- 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 go-around
- 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 › Aircraft oper/perf/capability
- Aircraft › Fluids/miscellaneous hardware
- 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 commercial pilot and his son were conducting a cross-country flight from New York to Missouri. Before the final fuel stop, they communicated to the pilot's fiancée via text message that the airplane was experiencing a "small electrical problem." The pilot refueled the airplane about 275 miles from the destination airport and continued on the final leg of the flight into dark night conditions.
The passenger subsequently messaged the pilot's fiancée and asked her to stand at the end of the runway with a flashlight to help direct the airplane toward the runway for landing. He stated that they would attempt to use a handheld radio onboard to activate the runway lights but were unsure if the radio would have sufficient battery. The passenger also indicated that they had "picked up a head wind" during the flight.
The pilot's fiancée reported that the airplane attempted to land, but she was unsure if it touched down on the runway due to the night conditions and the fact that the airplane was "blacked out" and did not have any exterior lights on. The last text message from the passenger stated, "keep light on." The airplane impacted terrain about 1/4 mile from the departure end of the runway in a nose-down attitude consistent with an aerodynamic stall. The two intact fuel tanks contained no usable fuel, and the propeller blades lacked chordwise scratches or torsional deformation, consistent with a loss of engine power. No preimpact mechanical malfunctions or failures with the airframe and engine were noted during the examination, with the exception of the voltage regulator, which was found to be inoperable.
Manufacturer guidance stated that, following an electrical system failure, the pilot should land the airplane as soon as practical; however, the pilot chose to both initiate and continue the flight into dark night conditions with a known electrical problem to an airport that required him to activate the runway lights. Though the extent of the pilot's preflight and inflight fuel planning could not be determined, it is possible that the airplane consumed more fuel than planned, as the passenger indicated that the airplane had encountered a headwind inflight, and it is likely that the absence of a fuel quantity indication contributed to the fuel exhaustion.
Based on the location of the airplane relative to the runway, it is likely that the pilot initiated a go-around following the first landing attempt. During the go-around, the airplane experienced a total loss of engine power and the pilot subsequently failed to maintain airspeed and exceeded the airplane's critical angle of attack, which resulted in an aerodynamic stall and impact with terrain.
Probable cause
A total loss of engine power due to fuel exhaustion and the pilot's subsequent exceedance of the airplane's critical angle of attack, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's decision to initiate and continue the flight into dark night conditions with a known electrical problem.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18FA384
- Event ID
- 20180921X14852
- Case number
- CEN18FA384
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2018-09-21.
- API snapshot SHA-256: 1724dadd2c908b95456c658ddbe8f8aea59179d9ea1aa3f16059ec43c6201a21; retrieved 2026-09-15T06:48:15.961Z.