CHI85LA308 · Cessna 150M
Cessna 150M · Accident: total loss of engine power (non-mechanical) on approach
From Maple Grove Airport (65G) to an unrecorded destination
Event
- NTSB case
- CHI85LA308
- 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
- N6350K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Maple Grove Airport (65G), Fowlerville, MITo not recorded
- 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
- Approach · VFR pattern final
- 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 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
- Fluid, fuel › Starvation
- Pilot in command › Mixture, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PLT WAS ON A SOLO X-COUNTRY FLT BETWEEN MAPLE GROVE ARPT & HOUGHTON LAKE ARPT. DURING THE FLT, THE PLT REQUESTED RADAR ASSISTANCE TO LOCATE HOUGHTON LAKE. DUE TO HER SOLO STUDENT STATUS & THE CLOSE PROXIMITY OF MT PLEASANT ARPT, SHE WAS ADVISED TO LAND THERE. WHILE ON A SHORT FINAL APPROACH TO RWY 27 AT MT PLEASANT, SHE PULLED THE MIXTURE KNOB BY MISTAKE & STARVED THE ENG OF FUEL. THIS RESULTED IN A FORCED LANDING IN A FIELD APRX 200 FT SHORT OF THE PAVED SURFACE OF THE RWY. THE TERRAIN AT THAT POINT WAS ROUGH ENOUGH TO CAUSE THE PLANE TO NOSE OVER.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI85LA308
- Event ID
- 20001214X37060
- Case number
- CHI85LA308
- 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: a2dbe8d2c23a41f8b93687256eb17cc4933a17528f694e560763380eb3cb3517; retrieved 2026-09-23T16:39:20.401Z.