CEN10CA092 · Cessna 150L
Cessna 150L · Accident: fuel exhaustion en route
From Decatur Airport (DEC) to Litchfield Municipal Airport (3LF)
Event
- NTSB case
- CEN10CA092
- 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
Cessna 150L
- 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
- N10401
- Operator
- Cuvar Philip M
- Onboard fatalities
- Unknown
- Route
- From Decatur Airport (DEC), Decatur, ILTo Litchfield Municipal Airport (3LF), Litchfield, IL
- Aircraft age
- Not recorded
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot stated that he was given a clearance to climb out to the west after taking off on the last leg of a three-leg cross-country flight. He departed at 3:35 local time, with 26 gallons of fuel on board. He stated that by the time he was able to turn onto his course heading he was off his planned route of flight. He reported that the haze and setting sun made it difficult to see and that he was not able to locate his checkpoints to get back on course. After flying around in order to attempt to identify his visual checkpoints, the engine experienced fuel exhaustion and the pilot performed an off-airport landing to a dark area in the terrain; however, the field was short and the airplane contacted trees and nosed over during the landing flare. The airplane sustained substantial damage to the wings and fuselage.
Probable cause
A total loss of engine power due to fuel exhaustion as a result of the student pilot becoming lost/disoriented in flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA092
- Event ID
- 20100107X52853
- Case number
- CEN10CA092
- 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. 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: 024c0c2bfd254e44bcd8ccd768ea8a5b6c51c344ed3736e3d010748368448b32; retrieved 2026-09-15T13:36:58.094Z.