FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA86LA030 · Cessna 210M

18 Nov 1985 · FT.LAUDERDALE, FL, United States

Cessna 210M · Accident: airframe, component or system failure en route

From Sebring Regional Airport (SEF) to Fort Lauderdale Hollywood International Airport (FLL)

Report a problem

Event

NTSB case
MIA86LA030
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 210M

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
N823AR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sebring Regional Airport (SEF), Sebring, FLTo Fort Lauderdale Hollywood International Airport (FLL), FT.LAUDERDALE, 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
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
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

  • Landing gear, normal retraction/extension assembly › Failure, partial
  • Landing gear, normal retraction/extension assembly › Fatigue

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

NTSB narrative

WHILE IN CRUISE FLIGHT THE PILOT ATTEMPTED TO LOWER THE LANDING GEAR AND THE RIGHT MAIN LANDING GEAR WOULD NOT EXTEND. DURING THIS PROCESS THE AIRCRAFT GENERATOR WENT OFF THE LINE. THE PILOT ATTEMPTED TO MANUALLY LOWER THE LANDING GEAR AND EXTENDED THE NOSE GEAR EXTENDED AND THE LEFT MAIN GEAR EXTENDED, BUT THE RIGHT GEAR STILL DID NOT EXTEND. THE PILOT LANDED THE AIRCRAFT AND THE AIRCRAFT SLID OFF THE RUNWAY AND WAS SUBSTANTIALLY DAMAGED. POST ACCIDENT EXAMINATION OF THE RIGHT LANDING GEAR HYDRAULIC ACTUATOR REVEALED THAT IT WAS CRACKED IN FATIGUE. THIS ALLOWED THE HYDRAULIC FLUID TO BE PUMPED OVERBOARD AND CAUSED THE ACTUATOR TO NOT EXTEND THE RIGHT MAIN GEAR.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MIA86LA030
Event ID
20001214X38282
Case number
MIA86LA030
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1985-11-19.
  • API snapshot SHA-256: ab4f3e6872ff99be56e3a6e9789ba3a15a3feacb75c47ec3edd2c4af5f3612a2; retrieved 2026-09-18T20:13:30.352Z.