# NTSB WPR18LA051: Piper PA 32-300, N4326X, Hinesville, GA, December 14, 2017 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Class 3 · Limited · Final report - Date: December 14, 2017, 08:54 local (13:54 UTC) - Place: Hinesville, GA - Coordinates: 31.888334, -81.561668 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=31.8883&lon=-81.5617&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Uncontained engine failure](https://openairdocs.org/ntsb-events/343) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - NTSB case key (mKey): 96507 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR18LA051 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96507/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96507 - Page: https://openairdocs.org/ntsb/WPR18LA051 ## Probable cause A total loss of engine power due to the failure of a connecting rod. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Engine (reciprocating): recip eng cyl section](https://openairdocs.org/ntsb-findings/01058530): Aircraft › Aircraft power plant · Failure (probable cause); cases with it: [Piper PA-32-300, 6 cases](https://openairdocs.org/ntsb-findings/01058530/cases.md?model=7103212), [All aircraft, 373 cases](https://openairdocs.org/ntsb-findings/01058530/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Uncontained engine failure](https://openairdocs.org/ntsb-events/343) (defining event); cases with it: [Piper PA-32-300, 1 case](https://openairdocs.org/ntsb-events/343/sequence.md?model=7103212), [All aircraft, 47 cases](https://openairdocs.org/ntsb-events/343/sequence.md) - [Approach-VFR pattern final: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Piper PA-32-300, 25 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7103212), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32-300, 43 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103212), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that, while on final approach for landing, he felt a shudder followed by a loud bang. Immediately after, the windscreen was covered in oil and the engine lost all power. The airplane impacted trees about 2 miles short of the runway. Examination of the engine revealed a large hole in the crankcase above the No. 4 cylinder. Further examination revealed that one connecting rod bolt and the connecting rod cap were missing, and the connecting rod was not attached to the crankshaft. About 6 inches of the camshaft was also missing. The remaining components of the connecting rod, piston assembly, and pieces of connecting rod bearing were examined; all of the discernible fracture surfaces exhibited features consistent with overstress. Extensive postfracture damage to the recovered pieces precluded the determination of any preexisting damage. Based upon the lack of available evidence (the missing connecting rod cap and rod bolt), the cause of the connecting rod failure could not be determined. ## Factual narrative On December 14, 2017 about 0854 eastern standard time, a Piper PA32-300, N4326X, was substantially damaged when it was involved in an accident near Hinesville, Georgia. The private pilot received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. In a statement provided to the Federal Aviation Administration (FAA) Inspector, the pilot said he was on final approach to runway 24R at Wright Army Airfield (Fort Stewart)/Midcoast Regional Airport (LHW), when he felt a shutter, followed by a loud bang. Immediately after, the windshield was covered in oil and the engine experienced a complete loss of power. The pilot reported to the air traffic controller that he was unable to land on the runway, and that he is "going down". About 2 miles short of the runway, the airplane impacted trees. In the National Transportation Safety Board Pilot/Operator Aircraft Accident/Incident Report 6120.1 the pilot reported he was near LHW when "the plane's engine sustained a catastrophic failure; camshaft broke and blew through engine block". The FAA Inspector examined the engine and observed a large hole in the crankcase above cylinder No.4. The crankcase surrounding the hole appeared to be displaced from the inside of the engine, outward. Further examination revealed that one connecting rod bolt and the rod cap were missing, and the connecting rod was not attached to the crankshaft. Furthermore, about 6 in of the camshaft was separated and not located. The NTSB Office of Research and Engineering further examined the remnants of the connecting rod, piston assembly, and pieces of connecting rod bearing. Bearings Both bearing halves had been deformed and flattened; one of the halves was intact and the other had fractured. The fracture surfaces had been heavily damaged which was consistent with post-fracture damage. Portions of the undamaged fracture surface exhibited features consistent with tensile overstress. The fracture surface exhibited a general rough texture with a dull luster, while the areas adjacent to the fracture surface exhibited local plastic deformation in the form of thinning or necking. These features were consistent with overstress fracture. The mating fracture faces of the fractured bearing half also showed a circular impact imprint, consistent with impact from the head of a connecting rod bolt. Connecting Rod Bolt The remaining connecting rod bolt had fractured mid length. The fracture features were generally rough in texture and flat in luster, consistent with fracture from bending overstress. Piston The piston was intact, with the connecting rod still affixed to the piston with the piston pin. The connecting rod had fractured near the crankshaft side at the rod yoke. There were no cracks or indications of severe deformation on any portion of the piston. The underside of the piston exhibited multiple impact and gouge marks, consistent with repeated batter of adjacent or loose components. Thecrown of the piston, the side of the piston and the piston pin exhibited normal wear. Connecting Rod All of the discernible fracture surfaces on the connecting rod exhibited features consistent with overstress fracture. Due to the extensive post-fracture damage to the parts, no indication was found of pre-existing damage. ## Aircraft - Registration: [N4326X](https://openairdocs.org/deregistered/N4326X-2021-01-09), registration cancelled 2021-01-09, S/N 32-7640010, built 1975 (OpenAirDocs) - Reported make and model: PIPER PA 32-300 (301) - Registry model: [Piper PA-32-300](https://openairdocs.org/model/piper-pa-32-300) (registry code 7103212) (OpenAirDocs) - Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 32-7640010 - Year built: 1975 - Airframe hours: 3664.6 - Engines: Lycoming IO-540-K1A5 reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 7, 2017 - Departed: MHP, METTER, GA - Destination: LHW, Hinesville, GA - Airport: LHW, Wright Aaf (Fort Stewart)/Midc, runway 24R, 6,505 × 100 ft, asphalt - Equipment: Satellite tracking device, Stall warning system, ADS-B, Auto-pilot, Data recorder, Onboard weather ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 65; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 190 total, 90 in this make and model, 190 as pilot in command, 20 in the last 90 days, 8 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 46 °F, dew point 37 °F - Altimeter: 29.95 inHg - Observed at: KLHW ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20171214023109A](https://openairdocs.org/incident/20171214023109A), Dec 14, 2017: Piper PA-32-300, Hanesville, GA, Destroyed. The pilot departed from metter, GA enroute to wright army airfield to pick up three passengers. While on final approach into wright, the pilot felt a shutter… ## Docket (6 files) The files NTSB released with the investigation on July 9, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96507. 15.4 MB in all. - Materials Laboratory Factual Report (item 1, .PDF, 8.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485207&FileExtension=.PDF&FileName=Materials%20Laboratory%20Factual%20Report-Master.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 2, .PDF, 1.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485208&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - FAA Inspector Statement (item 3, .PDF, 62 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485209&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement-Master.PDF - FAA Inspector Post-Accident Exam (item 4, .PDF, 77 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485210&FileExtension=.PDF&FileName=FAA%20Inspector%20Post-Accident%20Exam-Master.PDF - FAA Inspector Post-Accident Exam (item 5, .PDF, 359 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485211&FileExtension=.PDF&FileName=FAA%20Inspector%20Post-Accident%20Exam-Master.PDF - Photos (item 6, .PDF, 4.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485212&FileExtension=.PDF&FileName=Photos-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.