MIA03LA160 · Cessna T210M
Cessna T210M · Accident: total loss of engine power (mechanical failure) en route
From Miami-Opa Locka Executive Airport (OPF) to Opa Locka, FL
Event
- NTSB case
- MIA03LA160
- 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
- Unknown
- 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 T210M
- 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
- N86PH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Miami-Opa Locka Executive Airport (OPF), Opa Locka, FLTo Opa Locka, 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 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)
- 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, bearing › Loose
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that they departed Opa Locka Airport, Opa Locka, Florida, about 1040. They flew to a practice area to the west of Opa Locka West Airport and performed basic instrument work. The right front seat passenger was acting as the safety pilot. While they were returning to Opa Locka Airport, while in cruise flight at 1,500 feet, the engine ceased operating abruptly. Attempts to restart the engine were unsuccessful and the airplane was ditched in the Everglades, about 2 miles west of the Opa Locka West Airport. Prior to the forced landing they made contact with a controller at the FAA Opa Locka Airport Control Tower. They were rescued by a Miami-Dade County Police Department helicopter and taken back to the Opa Locka Airport. Post accident examination of the airplane and engine after the airplane was recovered from the Everglades showed the engine rotated when the propeller was rotated, but it was determined the accessory section of the engine was not rotating. Disassembly of the engine showed the crankshaft had fractured in the aft cheek of the No. 2 main bearing. The remains of the main bearing were found in the bottom of the engine crankcase. Metallurgical examination of the forward end of the crankshaft revealed that the fracture was located in the aft cheek of the No. 2 main bearing journal. The fracture surface showed features typical of fatigue progression from the radius of the journal in a plane perpendicular to the radius surface (approximately 45 degrees to the journal surface) with multiple origins. The mating fracture surface was completely damaged by rubbing. The fatigue initiation site at the radius surface did not contain scoring marks or scratches, but circumferential skidding marks and rub damage that intersected the origin area were observed elsewhere in the radius. Skidding/rub damage was also observed on the journal surface, with the surface being heat-tinted and rougher than the other main bearing journal surfaces. Examination of the No. 2 main bearing pieces showed that the pieces appeared to make one complete set of bearings. Sections of the bearings were rounded and showed a copper-colored region toward the edge (the copper-colored region is the middle layer in the tri-metal bearings used). The bearing contour matched the crankshaft radius. One bearing piece showed that the anti-rotation tab was fractured off in overstress. Examination of the crankcase halves showed that the No. 2 main bearing bosses revealed severe rotational rub damage, consistent with rotation of the bearing against the boss. Some minor wearing/fretting damage was observed on the boss mating surface of main bearing No. 3. Examination of the cylinder mounting surfaces in the vicinity of the locations where through-bolts at the No. 2 main bearing emerge from the case did not reveal significant fretting/corrosion damage. Only minor localized areas of fretting/corrosion damage were observed. Engine logbook records show that the engine last received a major overhaul on April 1, 1997, 865.5 flight hours before the accident. On November 25, 1998, 557.5 flight hours before the accident, all six cylinders were replaced with new cylinders. On August 23, 2001, 298 flight hours before the accident, all six cylinders were replaced with overhauled cylinders. On March 8, 2003, 31.8 flight hours before the accident, the engine received a 100-hour inspection.
Probable cause
Spinning of the crankshaft No. 2 main bearing for undetermined reasons resulting in damage to the aft cheek of the No. 2 main bearing journal, fatigue failure of the crankshaft cheek, failure of the engine in cruise flight, and damage to the airplane during the subsequent forced landing on unsuitable terrain..
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03LA160
- Event ID
- 20030815X01343
- Case number
- MIA03LA160
- 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: investigation status, coordinates. 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: 06854b8c8875770fc9f1a854f81949f1b1ef078fa908a4726f67b05771a8ddb3; retrieved 2026-09-22T08:47:49.290Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: destination. The narrative states the flight departed "Opa Locka Airport, Opa Locka, Florida" and the engine failed "While they were returning to Opa Locka Airport"; the destination was not recorded.