MIA86LA221 · Cessna 210B
Cessna 210B · Accident: total loss of engine power (mechanical failure) en route
From 1X6 · Brandon, FL to Terre Haute Regional Airport, Hulman Field (HUF)
Event
- NTSB case
- MIA86LA221
- 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 210B
- 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
- N9620X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 1X6 · Brandon, FLTo Terre Haute Regional Airport, Hulman Field (HUF), Terre Haute, IN
- 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 (mechanical failure)
- 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
- Substantial
Cause areas
- Engine assembly, crankshaft › Fatigue
- Engine assembly, crankshaft › Separation
- Other maintenance personnel › Maintenance, inspection, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
FLIGHT EXPERIENCED COMPLETE ENGINE FAILURE WHEN CRANKSHAFT FAILED DUE TO FATIGUE CRACKING OF THE CRANKSHAFT CHEEK BETWEEN THE NUMBER 1 AND 2 RODBEARING JOURNAL. DURING THE SUBSEQUENT FORCED LANDING THE AIRCRAFT COLLIDED WITH TREES DUE TO THE PILOT NOT WANTING TO LAND ON A DIRT ROAD DUE TO AN UNSAFE INDICATION ON THE NOSE LANDING GEAR. EXAMINATION OF THE ENGINES RECORDS REVEALED THE ENGINE HAD SUSTAINED SUDDEN STOPPAGE IN MUD 25 FLIGHT HOURS BEFORE THE CRANKSHAFT FAILURE. THE ENGINE WAS NOT DISASSEMBLED AND INSPECTED AT THAT TIME AS REQUIRED BY THE ENGINE MANUFACTURER. ADDITIONALLY IT WAS LEARNED THE ENGINE HAD 1788 TOTAL FLIGHT HOURS SINCE FACTORY OVERHAUL. THE MANUFACTURER RECOMMENDS THAT THE ENGINE BE OVERHAULED EACH 1600 FLIGHT HOURS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA86LA221
- Event ID
- 20001213X34260
- Case number
- MIA86LA221
- 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: bd5658b7381d7730bf2a70066fac7d65faed2018de4e78b5fb567e3eb6418389; retrieved 2026-09-22T01:17:45.074Z.