MIA94LA200 · Cessna 152
Cessna 152 · Accident: loss of engine power en route
From Orlando Sanford International Airport (SFB) to an unrecorded destination
Event
- NTSB case
- MIA94LA200
- 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 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
- N6088H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orlando Sanford International Airport (SFB), Sanford, FLTo 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
- En route · climb to 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
- Loss of engine power
- 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, carburetor › Blocked(partial)
- Fuel system, carburetor › Foreign object
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOTS STATED THAT THEY PERFORMED A SIMULATED FORCED LANDING AND INITIATED A G0-AROUND AT 600 FT. NORMAL ENGINE POWER WAS OBTAINED. WHILE CLIMBING THROUGH 800 FT POWER SUDDENLY WENT TO IDLE, AND ATTEMPTS TO RESTORE POWER WERE UNSUCCESSFUL. DURING A FORCED LANDING IN A FIELD THE AIRCRAFT NOSED OVER. AFTER THE ACCIDENT THE CARBURETOR WAS CHANGED, AND THE ENGINE OPERATED TO FULL POWER. A 3/32 INCH DIAMETER PORTION OF AN INSECT WAS FOUND IN THE CARBURETOR MIXTURE METERING SLEEVE WHICH BLOCKED THE PICKUP TO THE FUEL DISCHARGE NOZZLE. THE INSECT PORTION WAS TOO LARGE TO HAVE ENTERED THE CARBURETOR THROUGH THE FUEL INLET SCREEN. THE CARBURETOR WAS OVERHAULED IN 10/93, AND WAS INSTALLED ON THE ACCIDENT AIRCRAFT ON 8/5/94, 50 FLIGHT HOURS BEFORE THE ACCIDENT.
Probable cause
ENGINE POWER LOSS DUE TO BLOCKAGE OF THE CARBURETOR FUEL DISCHARGE NOZZLE PICKUP BY AN INSECT THAT INADVERTENTLY ENTERED THE CARBURETOR DURING OVERHAUL RESULTING IN FUEL STARVATION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA94LA200
- Event ID
- 20001206X02109
- Case number
- MIA94LA200
- 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: 5daa654701b55dbe8e110e799581bc9d89660f4caabc874a2903f544f6ec08b2; retrieved 2026-09-23T00:47:03.882Z.