MIA01LA059 · Cessna 182A
Cessna 182A · Accident: loss of engine power en route
From 35W · Parkton, NC to an unrecorded destination
Event
- NTSB case
- MIA01LA059
- 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 182A
- Aircraft type
- Cessna 182
- 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
- N5883B
- Operator
- Airanch Skydivers
- Onboard fatalities
- Unknown
- Route
- From 35W · Parkton, NCTo 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 · 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
- 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
- Fluid, fuel › Undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight departed with approximately 20 gallons of fuel in each fuel tank and offloaded skydivers at 10,500 feet, then descended to return with the throttle at idle, the fuel/air ratio leaned; and carburetor heat applied. At 2,000 feet, the pilot began to level off and, "realized I was having engine trouble and began my emergency procedures for an engine failure at altitude...." He checked the position of the fuel selector valve which was in the same position it was selected for takeoff, "both on." He positioned the fuel selector to the left, right, and both positions with negative results, and also checked "my ignition and check all fuses." He was unable to start the engine and performed a forced landing in a field. Before touchdown he turned off the fuel selector valve; after touchdown, the airplane nosed over. The fuel strainer was empty when examined by a mechanic approximately 45 minutes after the accident. Examination of the airplane by an FAA inspector approximately 24 hours after the accident revealed the flexible hose from the fuel strainer to the carburetor contained a slight amount of fuel (capful). No discrepancies with the fuel strainer, ignition, or vent systems noted. Following release by the FAA for recovery, the carburetor was removed and no fuel spray noted from the accelerator pump discharge nozzle when the throttle was activated. The fuel flow rate through the fuel selector valve was less with the fuel selector valve positioned to the right tank than with the valve positioned to the left or both positions. Disassembly of the fuel selector valve revealed no evidence of debris or wear; no determination was made as to the reason for the low fuel flow rate with the fuel selector positioned to the "right" position. Historical uneven fuel consumption greater from the left tank was noted while operating the airplane in skydiving operations that involve mainly climbs and descents. After repairs, the engine was placed on the airframe and operated with no discrepancies noted. Post accident testing with an exemplar carburetor, the accident fuel strainer and flexible hose from the fuel strainer to the carburetor with the assembly placed inverted revealed the carburetor leaks fluid to a certain level but fluid remains in the bowl. Additionally, with the assembly inverted and the carburetor bowl empty but fluid in the fuel strainer and flexible line, fluid does not flow into the carburetor bowl. The fuel selector valve was repaired last on March 18, 1977, in which an o-ring on the fuel selector shaft was replaced.
Probable cause
The loss of engine power during a normal descent due to fuel starvation for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA01LA059
- Event ID
- 20010116X00306
- Case number
- MIA01LA059
- 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: 2a9a0a03005a32e50b8c11f88524dbc6dd063c13e400b3355883ab1adf1528c3; retrieved 2026-09-22T12:14:25.506Z.