FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA92FA121 · Cessna 310Q

3 May 1992 · Odessa, FL, United States

Cessna 310Q · Accident: total loss of engine power (non-mechanical) during initial climb

From an unrecorded airport to Decatur County Industrial Air Park (BGE)

Report a problem

Event

NTSB case
MIA92FA121
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
3 · 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 310Q

Aircraft type
Cessna 310
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
N300DG
Operator
Randall, ASA T. · private individual
Onboard fatalities
Unknown
Route
From not recordedTo Decatur County Industrial Air Park (BGE), Bainbridge, GA
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
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

THE COMMERCIAL PILOT DEPARTED ON A VFR FLIGHT IN VFR CONDITIONS. NO FLIGHT PLAN WAS FILED. WITNESSES STATED THE AIRPLANE CLIMBED TO ABOUT 50-75 FEET AGL WHEN THE LANDING GEAR WAS RETRACTED. THE AIRPLANE WAS OBSERVED TO DRIFT TO THE LEFT OF THE RUNWAY AND DID NOT APPEAR TO GAIN ANY ADDITIONAL ALTITUDE. THE AIRPLANE CONTINUED TO ABOUT 3/4 OF A MILE OFF THE DEPARTURE END OF THE RUNWAY, WHEN THE AIRPLANE DISAPPEARED BELOW THE TREE LINE COLLIDING WITH TREES AND THE GROUND. A POSTCRASH FIRE ENSUED, AND THE PILOT AND TWO PASSENGERS WERE FATALLY INJURED. THE INVESTIGATION, INCLUDING AN EXAMINATION OF THE ENGINES AND PROPELLERS, DID NOT REVEAL EVIDENCE TO EXPLAIN A LOSE OF ENGINE POWER.

Probable cause

LOSS OF ENGINE POWER ON INITIAL TAKEOFF CLIMB ON ALL ENGINES FOR UNDETERMINED REASONS. THIS RESULTED IN A FORCED LANDING, IN FLIGHT COLLISION WITH TREES, TERRAIN, AND POSTCRASH FIRE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA92FA121
Event ID
20001211X14705
Case number
MIA92FA121
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: 5a9085fefef9d13277161168839ba31edb75ffd8eaa2cdfcd65e1d3d69b1755d; retrieved 2026-09-21T01:13:25.555Z.