# NTSB CEN13LA233: Piper PA-32-301, N82723, Paris, TX, April 19, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: April 19, 2013, 12:00 local (17:00 UTC) - Place: Paris, TX - Coordinates: 33.63639, -95.450553 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.6364&lon=-95.4506&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-cruise: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report June 2, 2014 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 86693 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN13LA233 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/86693/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=86693 - Page: https://openairdocs.org/ntsb/CEN13LA233 ## Probable cause The improper installation of the connecting rod bolts, which resulted in an engine failure. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Engine (reciprocating): recip engine power section](https://openairdocs.org/ntsb-findings/01058520): Aircraft › Aircraft power plant · Incorrect service/maintenance (probable cause); cases with it: [Piper PA-32-301, 1 case](https://openairdocs.org/ntsb-findings/01058520/cases.md?model=7103207), [All aircraft, 233 cases](https://openairdocs.org/ntsb-findings/01058520/cases.md) - [Engine (reciprocating)](https://openairdocs.org/ntsb-findings/01058500): Aircraft › Aircraft power plant · Failure (probable cause); cases with it: [Piper PA-32-301, 2 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md?model=7103207), [All aircraft, 497 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Piper PA-32-301, 4 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7103207), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Emergency descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32-301, 3 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103207), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis While in cruise flight, the engine lost power and oil immediately covered the windscreen. The pilot initiated a forced landing to a field. During the forced landing, the airplane impacted terrain and sustained substantial damage to the right wing. Disassembly of the engine showed multiple failures of the connecting rod assemblies. Metallurgical examination of the connecting rod assemblies revealed that the connecting rods likely failed due to insufficient clamping force at the split lines at the crankshaft end of the connecting rods. The pieces showed evidence of the nuts backing off from at least 3 of the connecting rod bolts. Fatigue of the connecting rod bolt and connecting rod straps was secondary to the loss of clamping force at the split lines. It is likely that the connecting rod bolts were not installed properly during the last overhaul. ## Factual narrative On April 19, 2013, approximately 1200 central daylight time, a Piper PA-32-301 single-engine airplane, N82723, impacted terrain following a loss of engine power during cruise flight near Paris, Texas. The commercial pilot was not injured. The airplane was registered to Galaxy Travellaire Inc, and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, which was on a visual flight rules flight plan. The flight originated from Parsons, Kansas, at 1030. According to the pilot, while in cruise flight at 7,500 mean sea level, the engine lost power and oil immediately covered the windscreen. The pilot initiated a forced landing to a field. During the forced landing, the airplane impacted terrain and came to rest upright. Examination of the airplane showed substantial damage to the right wing, firewall, and the nose gear was separated. A review of the maintenance records showed that the Lycoming IO-540-K1G5 engine (serial number L-15708-48A) had accumulated 4,683 total hours and 1,086 hours since major overhaul at the time of the accident. The engine's major overhaul was completed on November 3, 2008. The most recent annual inspection was completed on April 4, 2013, at an engine time of 1,080.7 hours since overhaul. On November 14, 2013, at the facilities of Air Salvage of Dallas (ASOD), Lancaster, Texas, the engine was disassembled under the supervision of a Federal Aviation Administration inspector and ASOD mechanics. Visual examination showed the crankcase sustained an uncontained failure near the number 2, 4, and 6 cylinders. The right side of the crankcase was cracked near the number 1 cylinder. Disassembly of the engine showed metal debris throughout the engine. The oil pickup tube was 3/4 full of metal debris. The oil sump contained metal debris and sections of connecting rod bolts, bearings, and connecting rods. Sections of all 6 connecting rods were retained and submitted to the NTSB Materials Laboratory for further metallurgical examination.The number 3 connecting rod was bent adjacent to the fracture surface, and the fracture features were irregular and rough, consistent with overstress failure. One of the strap fractures on the number 2 connecting rod showed flat features with curving crack arrest lines, features consistent with fatigue. The fatigue features emanated from origin areas at the connecting rod bolt head cut out and from the bearing face. The fatigue regions were relatively rough with multiple origins and step features, consistent with low cycle fatigue. Fracture surfaces on the opposite strap for the number 2 connecting rod and one of the fractures in the strap for connecting rod number 4 also showed crack arrest features consistent with fatigue. The nuts on two of the connecting rod bolt pieces were displaced toward the end of the bolt, and thread peaks between the nut and the grip were flattened. One nut was receivedseparated from the bolt, and the final 2 threads on the nut were damaged consistent with bolt pullout, and the remaining threads were intact. The fracture surfaces on one bolt showed curving crack arrest lines consistent with fatigue and were emanating from one side of the bolt. ## Aircraft - Registration: [N82723](https://openairdocs.org/aircraft/N82723), registered now, S/N 32-8306002, built 1982 (OpenAirDocs) - Reported make and model: PIPER PA-32-301 - Registry model: [Piper PA-32-301](https://openairdocs.org/model/piper-pa-32-301) (registry code 7103207) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 32-8306002 - Engines: LYCOMING IO-540-K1G5 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 4, 2013, 6 hours before - Departed: PPF, Parsons, KS - Destination: CXO, Conroe, TX - Flight plan: VFR ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 60; injuries: none; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review February 10, 2013; seat: left; flight hours: 9,128 total, 3,847 in this make and model, 8,747 as pilot in command, 28 in the last 90 days, 9 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 320° at 12 knots - Visibility: 10 statute miles - Lowest ceiling: none - Altimeter: 30.23 inHg ## 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 20130419008009A](https://openairdocs.org/incident/20130419008009A), Apr 19, 2013: Piper PA-32-301, Sulphur Bluff, TX, Substantial damage. On April 19, 2013, at 1150 central daylight time, a Piper PA-32-301 single-engine airplane, N82723, impacted terrain following a loss of engine power during… ## Docket (3 files) The files NTSB released with the investigation on March 14, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=86693. 3.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40410632&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - NTSB Materials Lab Factual Report (item 2, .PDF, 987 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40410633&FileExtension=.PDF&FileName=NTSB%20Materials%20Lab%20Factual%20Report-Master.PDF - Excerpts of Engine Logbooks (item 3, .PDF, 644 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40410635&FileExtension=.PDF&FileName=Excerpts%20of%20Engine%20Logbooks-Redacted.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.