FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA05LA147 · Cessna T210M

7 Aug 2005 · Kissimmee, FL, United States

Cessna T210M · Accident: total loss of engine power (non-mechanical) en route

From Northeast Ohio Regional Airport (HZY) to Winter Haven Regional Airport - Gilbert Field (GIF)

Report a problem

Event

NTSB case
MIA05LA147
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 T210M

Aircraft type
Cessna 210
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
N732WN
Operator
Unknown
Onboard fatalities
Unknown
Route
From Northeast Ohio Regional Airport (HZY), Ashtabula, OHTo Winter Haven Regional Airport - Gilbert Field (GIF), Winter Haven, 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
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
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 exhaustion
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 consumption calculations, inaccurate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was fueled prior to departure with 86.82 gallons of fuel, making the total amount of fuel onboard the airplane 90 gallons. The pilot stated that he departed about 0830 that morning and the flight was uneventful until descending toward the intended airport, with fuel gauge and calculations showing 30 to 40 minutes of fuel remaining. The airplane's engine started running rough and stopped. He tried to restart the engine without success and elected to perform a forced landing on a road under construction. The airplane ran into a ditch and nosed over. Fire department personnel on the scene reported that no fuel was leaking from the aircraft. The fuel strainer and the two reservoir tanks in the fuselage yielded a total of 4 ounces of fuel. The flow divider contained a negligible amount of fuel. The pilot stated to the FAA inspector that he must have run out of fuel. The pilot stated there were no mechanical failures or malfunctions with the airplane or any of its systems.

Probable cause

A loss of engine power due to the pilot's inaccurate fuel consumption calculations and subsequent fuel exhaustion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA05LA147
Event ID
20050823X01303
Case number
MIA05LA147
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, coordinates. 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: ca7842e190297bcad175688f6c895330c93543d423166f34ab8ecdf8deece6d5; retrieved 2026-09-22T05:31:28.879Z.