MKC89LA086 · Cessna 150
Cessna 150 · Accident: partial loss of engine power (mechanical failure) during initial climb
From 74NE · Papillion, NE to an unrecorded destination
Event
- NTSB case
- MKC89LA086
- 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 150
- 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
- N3832J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 74NE · Papillion, NETo 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
- Initial climb
- 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
- Partial loss of engine power (mechanical failure)
- 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
- Fuel system, screen › Blocked(partial)
- Pilot in command › Operation with known deficiencies in equipment, intentional
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PVT PLT SAID HE WAS PRACTICING TAKEOFFS AND LDGS. DURING A TAKEOFF THE ENGINE HESITATED, SO HE ABORTED THE T.O. AND RE-LANDED ON THE REMAINING RUNWAY. AFTER TAXIING BACK, HE RAN THE ENGINE UP AND CHECKED AND CONFIRMED NORMAL OPERATION. HE THEN TOOK OFF AND AFTER ATTAINING ABOUT 150 TO 200 FEET AGL, THE ENGINE BEGAN LOSING POWER AND AN EMERGENCY LANDING WAS ATTEMPTED ON THE AIRPORT PROPERTY, RESULTING IN COLLISION WITH A TERRACE AND NOSING OVER. POST ACCIDENT INVESTIGATION AND ENGINE RUNUP REVEALED FOREIGN MATTER IN THE CARBURETOR FINGER SCREEN. THE ACFT HAD BEEN INACTIVE OVER AN EXTENSIVE PERIOD OF TIME BEFORE PURCHASE BY THE PRESENT OWNER.
Probable cause
THE CONTAMINATION OF THE FUEL SCREEN BY FOREIGN MATTER AND OPERATION OF THE AIRCRAFT WITH KNOWN DEFICIENCIES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MKC89LA086
- Event ID
- 20001213X27976
- Case number
- MKC89LA086
- 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: 953a9de3ef3baff998a108b69cdf2505e6f77e1f893e15b13cd856fed8dc6dbe; retrieved 2026-09-21T15:57:06.563Z.