ASN Wikibase Occurrence # 162802
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can
submit corrected information.
Date: | 19-DEC-2013 |
Time: | 23:51 |
Type: | Cessna 210N Centurion |
Owner/operator: | AirNet Systems, Inc. |
Registration: | N5307A |
MSN: | 21063360 |
Fatalities: | Fatalities: 0 / Occupants: 1 |
Aircraft damage: | Substantial |
Category: | Accident |
Location: | Tampa International Airport (KTPA), Tampa, FL -
United States of America
|
Phase: | Landing |
Nature: | Cargo |
Departure airport: | Valdosta, GA (VLD) |
Destination airport: | Tampa, FL (TPA) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
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.
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.
Sources:
NTSB
FAA register:
http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=5307A Location
Media:
Revision history:
Date/time | Contributor | Updates |
20-Dec-2013 11:32 |
gerard57 |
Added |
20-Dec-2013 11:33 |
harro |
Updated [Aircraft type, Registration, Cn, Operator, Embed code] |
20-Dec-2013 16:33 |
Geno |
Updated [Time, Operator, Location, Destination airport, Source, Embed code, Damage] |
14-Jan-2014 22:53 |
Geno |
Updated [Nature, Departure airport, Source, Narrative] |
21-Dec-2016 19:28 |
ASN Update Bot |
Updated [Time, Damage, Category, Investigating agency] |
29-Nov-2017 09:28 |
ASN Update Bot |
Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Embed code, Narrative] |
The Aviation Safety Network is an exclusive service provided by:

CONNECT WITH US:
©2023 Flight Safety Foundation