FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight Express Cessna 210L accident

21 Sept 1992 · Orlando, FL, United States

Cessna 210L · Accident: airframe, component or system failure on approach

From Orlando Executive Airport (ORL) to Tallahassee International Airport (TLH)

Report a problem

Event

NTSB case
MIA92LA188
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
Charter & commuter
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 210L

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
N777BK
Onboard fatalities
Unknown
Route
From Orlando Executive Airport (ORL)To Tallahassee International Airport (TLH), Tallahassee, 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 135: Air Taxi & Commuter
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
Approach
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
Airframe, component or system failure
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, hydraulic › Loss, total
  • Landing gear, normal retraction/extension assembly › Failure, total
  • Landing gear, normal retraction/extension assembly › Ruptured
  • Landing gear, normal retraction/extension assembly › Undetermined
  • Pilot in command › Gear extension, not possible

Approximate · Estimated position: the centre of Orlando, FL, the place the record names. Not the accident site.

NTSB narrative

FLIGHT WAS UNABLE TO GET SAFE INDICATION FOR LANDING GEAR EXTENDED WHILE APPROACHING DESTINATION AIRPORT. FLIGHT RETURNED TO DEPARTURE AIRPORT. AFTER ACCOMPLISHING EMERGENCY PROCEDURES FOR GEAR EXTENSION, GEAR SAFE INDICATION WAS STILL NOT OBTAINED. PILOT DETERMINED ALL HYDRAULIC FLUID HAD BEEN LOST. FLIGHT WAS LANDED WITH THE NOSE GEAR LOCKED AND THE MAIN GEARS PARTIALLY EXTENDED. POSTLANDING EXAMINATION REVEALED RIGHT MAIN GEAR HYDRAULIC ACTUATOR HAD FAILED DUE TO OVERSTRESS ALONG METAL GRAIN BOUNDARIES AND AT AREA OF LOW WALL THICKNESS. ALL HYDRAULIC SYSTEM PRESSURE WERE FOUND TO BE NORMAL AND NO OTHER LANDING GEAR SYSTEM FAILURES WERE FOUND. AFTER FAILURE OF THE GEAR ACTUATOR ALL NORMAL AND EMERGENCY SYSTEM FLUID WAS LOST THROUGH THE ACTUATOR.

Probable cause

FAILURE OF THE RIGHT MAIN LANDING GEAR ACTUATOR DUE TO OVERSTRESS FOR UNDETERMINED REASONS WHICH RESULTED IN LOSS OF ALL LANDING GEAR SYSTEM HYDRAULIC FLUID WHICH IN TURN RESULTED IN THE PILOT BEING UNABLE TO EXTEND AND LOCK THE LANDING GEAR.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA92LA188
Event ID
20001211X15759
Case number
MIA92LA188
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: c8f5cf98ad5f90e28be5dcf07612fe765fce4b421267e22d0092ba967fa9d856; retrieved 2026-09-18T18:43:56.179Z.