CEN23FA401 · Cessna 150K
Cessna 150K · Accident: fuel starvation during initial climb
From Conroe-North Houston Regional Airport (CXO) to an unrecorded destination
Event
- NTSB case
- CEN23FA401
- 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 150K
- 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
- N6059G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Conroe-North Houston Regional Airport (CXO), Conroe, TXTo not recorded
- Aircraft age
- About 53 years (built 1970)
- 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
- Initial climb
- 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 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot and his flight instructor were conducting touch-and-go landings during an instructional flight when a partial loss of engine power occurred during the initial climb from the runway. Two witnesses reported that they were on the ramp preparing for a flight when they heard a sudden decrease in engine rpm. They turned and saw the airplane flying about 500 ft above the runway in a level attitude with the wings rocking. The airplane then entered a left turn in a nose-down attitude. One of the witnesses believed that the pilot was attempting a descending left 180° turn to land on the opposite runway direction used for the takeoff. The airplane completed about 90° of turn when it entered an aerodynamic spin and descended to the ground in a nose-down attitude.
Postaccident examination revealed debris that obstructed the inlet elbow fuel fitting to the fuel shutoff valve. Similar debris was also recovered from the fuel shutoff valve and the left and right fuel lines. Borescope examination of the fuel tanks revealed additional loose debris inside each fuel tank. Laboratory analysis determined the elemental composition of the fuel system debris consisted mostly of silicon, iron, and lead. Silicon and iron are consistent with soil. The presence of lead was consistent with transfer contact with fuel system components where leaded fuel, such as aviation 100 low-lead fuel, had been present. Based on the available evidence, the partial loss of engine power was likely due to fuel starvation from a blockage of the inlet elbow fuel fitting to the fuel shutoff valve.
According to the airplane’s maintenance logbooks, the last maintenance of the fuel shutoff valve was completed more than 8 years before the accident. However, about 9 months before the accident, the fight instructor, who was also the airplane owner, made an entry in the airplane’s discrepancy record that the airplane was using fuel from the left tank “slower” than the right tank. The discrepancy was deferred until the next annual inspection. The discrepancy log entry further noted that the issue could not be duplicated during the annual inspection that was completed about 14 flight hours before the accident. Comparing the signatures on the discrepancy entry to signatures found in the flight instructor’s pilot logbook established that it was the flight instructor who entered and closed out the discrepancy entry. As described, the discrepancy was likely indicative of a fuel system blockage forming that resulted in uneven fuel usage between the left and right fuel tanks.
The wreckage examination did not reveal any preimpact flight control or mechanical malfunctions or failures of the engine that would have prevented normal operation. The airplane’s nose-down attitude and aerodynamic spin are consistent with the flight instructor failing to maintain adequate airspeed during the return to the runway.
Probable cause
A partial loss of engine power due to fuel starvation caused by a fuel system blockage, and the flight instructor’s subsequent failure to maintain adequate airspeed after the loss of engine power, which resulted in the airplane exceeding its critical angle of attack and entering an aerodynamic stall at a low altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23FA401
- Event ID
- 20230906193017
- Case number
- CEN23FA401
- 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: cc6c3538965e1ca248a4c72561924d1f7a49bbd20b50db46a7e65f53ef527f27; retrieved 2026-09-15T08:05:32.815Z.