FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA96LA002 · Cessna T210M

4 Oct 1995 · Apopka, FL, United States

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

From Leesburg International Airport (LEE) to Space Coast Regional Airport (TIX)

Report a problem

Event

NTSB case
MIA96LA002
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 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
N6508B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Leesburg International Airport (LEE), Leesburg, FLTo Space Coast Regional Airport (TIX), Titusville, 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 · 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
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

  • Fluid, fuel › Exhaustion
  • Pilot in command › Fuel consumption calculations, not performed

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PILOT STATED HE DID NOT PERFORM ANY FUEL CONSUMPTION CALCULATION BEFORE DEPARTING ON THE FLIGHT. HE ESTIMATED HE HAD ABOUT 1 INCH TO 1 1/2 INCHES OF FUEL PRESENT IN THE LEFT AND RIGHT FUEL TANKS, AND ADDED 10 GALLONS OF FUEL TO EACH FUEL TANK. HE FLEW TO HIS INTERMEDIATE STOP, PICKED UP HIS PASSENGER, AND DEPARTED FOR HIS DESTINATION AIRPORT. UPON LEVELING THE AIRPLANE AT 1,800 FEET AGL, THE ENGINE STARTED TO RUN ROUGH. HE SWITCHED FUEL TANKS AND TURNED THE BOOST PUMP ON HIGH. THE ENGINE SMOOTHED OUT AND HE TURNED THE BOOST PUMP OFF. ABOUT 3 MINUTES LATER THE ENGINE STARTED RUNNING ROUGH AGAIN AND HE REPEATED THE SAME STEPS WITH NEGATIVE RESULTS. A FORCED LANDING WAS MADE TO THE ONLY AVAILABLE LANDING AREA, AND THE AIRPLANE COLLIDED WITH A FENCE POST. EXAMINATION OF THE FUEL SYSTEM BY THE FAA REVEALED THE FUEL TANKS WERE NOT RUPTURED. ONE PINT OF FUEL WAS PRESENT IN THE FUEL SYSTEM. THE PILOT STATED, 'I MADE A MISTAKE OF TRUSTING THE FUEL GAGES AND RAN THE AIRPLANE OUT OF FUEL'.

Probable cause

THE PILOT'S FAILURE TO PERFORM FUEL CONSUMPTION CALCULATIONS FOR THE FLIGHT WHICH RESULTED IN A LOSS OF ENGINE POWER DUE TO FUEL EXHAUSTION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA96LA002
Event ID
20001207X04750
Case number
MIA96LA002
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: ea0daff56effebf82341ecb3f58c37fa38c499114d170cc5e6610ab20a278c36; retrieved 2026-09-22T23:11:41.572Z.