CHI02LA041 · Cessna 152
Cessna 152 · Accident: total loss of engine power (non-mechanical) en route
From Terre Haute Regional Airport, Hulman Field (HUF) to Sedalia Memorial Airport (DMO)
Event
- NTSB case
- CHI02LA041
- 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 152
- Aircraft type
- Cessna 152
- 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
- N48285
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Terre Haute Regional Airport, Hulman Field (HUF), Terre Haute, INTo Sedalia Memorial Airport (DMO), Sedalia, MO
- 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
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- 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
- 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
- Pilot in command › In-flight planning/decision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that approximately four miles from the airport the engine "slowed and then stopped." The pilot reported that he established best glide speed and made a forced landing to an agricultural field. The pilot stated that the agricultural field was "freshly plowed and muddy." A post-accident inspection of the airplane revealed there was no usable fuel remaining in either of the wing fuel tanks. The fuel tanks were not ruptured. The accident airplane had been fueled with 24.7 gallons of fuel 30 minutes prior to the accident flight. The useable fuel for the Cessna 150 is 24.5 gallons. The fuel endurance for a Cessna 152 at maximum cruise power at 2,000 feet above mean sea level is 3.25 hours. The accident occurred 4 hours and 10 minutes after departure.
Probable cause
The pilot's inadequate in-flight planning/decision which led to fuel exhaustion and subsequent loss of engine power. Contributing to the accident was the soft, rough/uneven terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI02LA041
- Event ID
- 20011129X02316
- Case number
- CHI02LA041
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 98af340d74b1f60cdb5d507f1772f769fc9051340a69b45862a5913950831c5c; retrieved 2026-09-22T11:21:17.106Z.