MIA98LA005 · Cessna P172D
Cessna P172D · Accident: total loss of engine power (non-mechanical) during initial climb
From Umatilla Municipal Airport (X23) to Orlando Apopka Airport (X04)
Event
- NTSB case
- MIA98LA005
- 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 P172D
- Aircraft type
- Cessna 172
- 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
- N8582X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Umatilla Municipal Airport (X23)To Orlando Apopka Airport (X04), PLYMOUTH, FL
- 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
- 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
- Pilot in command › Fuel tank selector position, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before takeoff the passenger noted that the right and left fuel tank gauges indicated empty and 3/4 full respectively. After takeoff with the fuel selector positioned to the right tank, the engine experienced a total loss of engine power due to fuel starvation. The pilot pumped the throttle and the engine sputtered then quit. While descending for a forced landing in a field, the nose landing gear collided with a fence causing the airplane to nose over and impact the ground inverted. Post accident examination of the airplane revealed that the right fuel tank contained about 4.5 gallons of fuel and the left fuel tank contained about 13.0 gallons of fuel. According to the airplane type certificate data sheet the unusable fuel quantity for each fuel tank is 5.25 gallons.
Probable cause
The improper fuel tank selector position by the pilot-in-command resulting in the total loss of engine power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA98LA005
- Event ID
- 20001208X09079
- Case number
- MIA98LA005
- 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: fff4e01da43f22df5c5f254ab4cb7eeb18332ca05a5cace67bc6c18968dfcc22; retrieved 2026-09-21T21:07:12.196Z.