Cherokee Express Air Cargo Cessna 210M incident
Cessna 210M · Incident: partial loss of engine power (mechanical failure) during initial climb
From Tampa International Airport (TPA) to Orlando Executive Airport (ORL)
Event
- NTSB case
- MIA91IA061
- 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
- Incident
- 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
- Cherokee Express Air Cargo
- Onboard fatalities
- Unknown
- Route
- From Tampa International Airport (TPA), Tampa, FLTo Orlando Executive Airport (ORL), Orlando, 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
- 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
- Partial loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Electrical system › Shorted
- Fuel system, line › Chafed
- Pilot in command › Gear extension, not possible
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
SHORTLY AFTER TAKEOFF WHILE CLIMBING THROUGH 1,000 FT, THE PLT REPORTED AN ELECTRICAL FIRE & PARTIAL LOSS OF ENG POWER. HE WAS UNABLE TO EXTEND THE LANDING GEAR USING THE NORMAL & EMERGENCY METHOD DUE TO HYDRAULIC FLUID LOSS FROM FIRE DAMAGED HYDRAULIC LINES. WITH THE GEAR OFF THE UPLOCKS BUT NOT DOWN & LOCKED, THE PLT LANDED THE ACFT ON A ROAD. EXAM OF THE ACFT REVEALED THAT A FUEL LINE WHICH EXITS THE FUEL STRAINER LOCATED IN THE NOSE LANDING GEAR WHEEL WELL HAD A PIN-SIZE HOLE DUE TO CHAFING OF AN ELECTRICAL WIRE BUNDLE WHICH CROSSES THE LINE. AS A RESULT, THE INSULATION COVERING THE WIRES WAS DAMAGED & FUEL WHICH CONTACTED THE WIRES WAS IGNITED.
Probable cause
FUEL LINE CHAFING, AND IN-FLIGHT FIRE CAUSED BY SHORTING OF THE ELECTRICAL SYSTEM WHICH RESULTED IN A FORCED LANDING WITH THE LANDING GEAR NOT EXTENDED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA91IA061
- Event ID
- 20001212X16349
- Case number
- MIA91IA061
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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 1991-01-05.
- API snapshot SHA-256: cb95e567c9df403caae26e36c7c1556e20e1207c994397b506ebe263689d673b; retrieved 2026-09-18T18:57:32.585Z.
- The NTSB's operator name is blank for N823AR; the operator shown is the name the NTSB records it doing business as.