CESSNA 210N near Tampa, FL — 2013-12-20
- Date
- 2013-12-20
- Location
- Tampa, FL, USA
- Airport
- TPA
- Aircraft
- CESSNA 210N
- Registration
- N5307A
- Category
- Airplane
- Highest injury
- Serious
- Fatalities
- 0
- Phase of flight
- Approach
Probable cause
A total loss of engine power due to the fatigue failure of the No. 4 connecting rod. Contributing to the accident was a likely loss of lubrication for reasons that could not be determined during a postaccident engine examination.
Contributing factors
Contributing to the accident was a likely loss of lubrication for reasons that could not be determined during a postaccident engine examination.
NTSB narrative
As the on-demand air cargo flight approached the destination airport, the pilot advised air traffic control that the airplane's engine had "lost oil pressure." Subsequently, an air traffic controller cleared the flight to land on an alternate runway. The airplane impacted a berm short of the runway threshold, which resulted in serious injury to the pilot and substantial damage to the airframe. Postaccident examination of the wreckage revealed that engine oil was present from the windscreen to the vertical stabilizer and that the engine case had been breached near the Nos. 4 and 6 cylinders. Detailed examination of the engine revealed signatures consistent with oil starvation and a fatigue failure of the No. 4 connecting rod and connecting rod cap. Although the metallurgical hardness of one of the No. 4 connecting rod bolts was slightly below its specified value, this likely did not contribute to its separation, and it likely failed in overstress after the fatigue-related separation of the mating connecting rod. The engine's oil sump was breached and only contained residual traces of engine oil; the preaccident quantity of oil within the engine could not be determined. Examination of the engine's oil galleys and passages revealed that they were intact, clear, and unrestricted. The root cause for the loss of lubrication and subsequent fatigue failure of the No. 4 connecting rod could not be determined.
Analysis
- Primary failure mode
- Engine power loss
- First missed decision gate
- Pilot could have requested emergency equipment earlier to prepare for engine issues.
NTSB coding
Evidence available
- ATC audio
- Photos
- 10 docket documents
Docket documents10
- Air Traffic Control Transcriptatc
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Release of Aircraft Wreckage, NTSB Form 6120.15form
- Statement of Party Representatives to NTSB Investigationinterview
- Engine Log Excerptsother
- Photo 1 – View of Main Wreckage From Right (Photo Courtesy of Cessna)photos
- Photo 2 – View of Main Wreckage From Front (Photo Courtesy of Cessna)photos
- Photo 3 – View of Engine Case from Top (Photo Courtesy of Cessna)photos
- Materials Laboratory Factual Reportreport
- Police Report (Excerpt)report
Related mishaps
- AEROPRAKT MFG SP Z O O A32
2026-04-16 · Lexington, KY
- ICON A5
2026-04-15 · Levittown, PR
- PITTS S1S
2025-12-31 · Carbondale, IL
- CESSNA 185A
2025-09-27 · Ilwaco, WA
- CubCrafters CCK-2000
2025-09-07 · Thompsonville, MI
- BELLANCA 17-30A
2024-04-05 · Galveston, TX