CHI96LA195 · Cessna 150M
Cessna 150M · Accident: total loss of engine power (non-mechanical) en route
From 19D · Mora, MN to Gorno-Altaysk Airport (RGK)
Event
- NTSB case
- CHI96LA195
- 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
- 0
- 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 150M
- 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
- N9132U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 19D · Mora, MNTo Gorno-Altaysk Airport (RGK)
- 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 · descent
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel supply, inadequate
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that during a descent from 3,500 feet mean sea level (MSL), the engine lost power. She attempted to restart the engine, but was unsuccessful. She performed a forced landing to a corn field. While landing, the nose wheel sank into soft terrain, and the airplane nosed over. Examination of the airplane revealed that about 3.5 gallons of fuel were remaining, but no fuel was found in the carburetor. No other anomalies were found. The airplane had a fuel capacity of 26 gallons, of which, 22.5 gallons were considered to be usable. There were three occupants in the 2-place airplane. One passenger was occupying the right seat; the other passenger was in the back of the airplane, although it was not equipped with an optional child seat.
Probable cause
the pilot's improper planning/decision, which resulted in fuel exhaustion due to an inadequate supply. A factor relating to the accident was: soft terrain in the emergency landing area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA195
- Event ID
- 20001208X05922
- Case number
- CHI96LA195
- 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: df7f967e35da7ab4ae4defa1b0a955e05c4936877d0659c17232ed14c2f1121e; retrieved 2026-09-22T22:19:09.632Z.