# NTSB CEN13LA431: Schweizer 269C, N7507A, Gary, SD, July 23, 2013 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: July 23, 2013, 15:20 local (20:20 UTC) - Place: Gary, SD - Coordinates: 44.793056, -96.457496 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.7931&lon=-96.4575&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach: Powerplant sys/comp malf/fail](https://openairdocs.org/ntsb-events/340) - Highest injury: Minor injuries - Injuries: 1 minor, 2 uninjured - Status: Completed, report October 27, 2014 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 87559 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN13LA431 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/87559/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=87559 - Page: https://openairdocs.org/ntsb/CEN13LA431 ## Probable cause The failure of the engine connecting rod due to fatigue. ## 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 · Failure (probable cause); cases with it: [Schweizer 269C, 1 case](https://openairdocs.org/ntsb-findings/01058520/cases.md?model=8059502), [All aircraft, 233 cases](https://openairdocs.org/ntsb-findings/01058520/cases.md) - [Terrain: sloped/uneven terrain](https://openairdocs.org/ntsb-findings/03021017): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Schweizer 269C, 3 cases](https://openairdocs.org/ntsb-findings/03021017/cases.md?model=8059502), [All aircraft, 270 cases](https://openairdocs.org/ntsb-findings/03021017/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach: Powerplant sys/comp malf/fail](https://openairdocs.org/ntsb-events/340) (defining event); cases with it: [Schweizer 269C, 1 case](https://openairdocs.org/ntsb-events/340/sequence.md?model=8059502), [All aircraft, 820 cases](https://openairdocs.org/ntsb-events/340/sequence.md) - [Autorotation: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Schweizer 269C, 11 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=8059502), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot was descending the helicopter from about 1,000 feet above ground level (agl) and setting up for a landing at an off-airport location. At 300 to 500 feet agl, the pilot felt a major vibration in the helicopter. He immediately initiated an autorotation and landed the helicopter. During the forced landing, the helicopter rolled over on its right side and sustained substantial damage. Examination of the engine revealed that the No. 3 connecting rod had failed. Material examination of the connecting rod showed the rod failed due to multiple fatigue cracks. ## Factual narrative On July 23, 2013, at 1520 central daylight time, a Schweizer 269C helicopter, N7507A, impacted terrain during a forced landing near Gary, South Dakota. The pilot and one passenger were not injured, and one passenger sustained minor injuries. The helicopter sustained substantial damage to the fuselage and main rotor system. The helicopter was registered to Novne Aviation LLC, 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 not operated on a flight plan. The local flight originated from Canby, Minnesota, at 1500.According to the pilot, he was descending from approximately 1,000 feet above ground level (agl) and setting up for a landing at an off airport location. At 300 to 500 feet agl, the pilot felt a major vibration with the helicopter. He immediately initiated an autorotation and landed the helicopter. During the forced landing, the helicopter rolled over on its right side and sustained substantial damage. On September 18, 2013, under the supervision of a Federal Aviation Administration inspector, the Lycoming HIO-360-D1A engine, serial number L-11954-51A, and helicopter were examined. Visual examination of the engine revealed a hole in the crankcase near the number 3 cylinder. Prior to engine disassembly, the inspector attempted to rotate the engine crankshaft by hand; however, the crankshaft was unable to rotate. The engine was then disassembled. Disassembly of the engine revealed the number 3 connecting rod was fractured into multiple sections. The connecting rod and associated hardware were retained for further examination. No evidence of fretting was noted on the base of the cylinders or engine crankcase mating surfaces. The number 3 crankshaft journal displayed dark discoloration. No evidence of oil starvation was noted on the crankshaft bearings. Extensive damage, consistent with the failure of the number 3 connecting rod, was noted throughout the engine. A review of the airframe and engine logbooks revealed that a major overhaul on the engine was completed on April 20, 1998. The most recent annual inspection was completed on the engine on October 29, 2012, at 881.9 hours since major overhaul. During the annual inspection, all four engine cylinders were removed and overhauled. On May 14, 2013, at 893 hours since major overhaul, the engine oil was changed with no anomalies noted. At the time of the accident, the engine had accumulated 899 hours since major overhaul. The National Transportation Safety Board's Materials Laboratory examined the engine's number 3 connecting rod and associated hardware. According to the examination, the connecting rod and cap had fractured in multiple locations, and the head of one of the connecting rod bolts had fractured. A fracture surface located on one of the connecting rod yokes exhibited crack arrest and ratchet marks, consistent with progressive crack growth and failure.More than any of the other fractures, this fracture exhibited the largest percentage of progressive fracture relative to overstress features. A thin middle portion of the fracture surface exhibited a morphology consistent with overstress. This overstress area was bounded on the opposite side by progressive cracking that had initiated and grown from the inner bearing surface and bolt hole inner bore of the connecting rod yoke. The inside bore of the connecting rod bolt hole where the main progressive cracking had initiated exhibited relatively deep grooves. Several of the crack initiation sites corresponded with these grooves on the inside bore. A fracture surface located in the connecting rod cap exhibited several thumbnail-shaped features indicative of progressive crack growth on the inner bearing surface. These cracks were not located along the same plane and were staggered in location, while being oriented parallel to each other. The inside surface of the rod cap exhibited multiple cracks less than 0.25 inches in length, perpendicular to the rotational direction of the rod. These cracks were consistent with fatigue that typically occurs in heavy wear during contact between mating surfaces. Fatigue cracking was found emanating from both the connecting rod bolt hole inner bore, as well as from the inside bearing surface. The existence of ratchet marks near the start of the fatigue crack was consistent with multiple crack initiation sites. A thin section of the fracture surface between the fatigue cracks exhibited dimple rupture, indicative of failure from tensile overstress. This fracture pattern was consistent with the final remaining cross section failing from overstress after the fatigue cracks had progressed deep enough. Inspection of the connecting rod found the chemical composition to be consistent with an American Iron and Steel Institute (AISI) 4XXX or 8XXX series alloy steel. To determine the nature of the cracks on the inner bearing surface of the connecting rod cap, the largest one was backcut and intentionally overstressed to expose the crack faces. Three small thumbnail-shaped cracks were revealed; these cracks exhibited features consistent with fatigue. ## Aircraft - Registration: [N7507A](https://openairdocs.org/deregistered/N7507A-2018-05-31), registration cancelled 2018-05-31, S/N S1297, built 1987 (OpenAirDocs) - Reported make and model: SCHWEIZER 269C - Registry model: [Schweizer 269C](https://openairdocs.org/model/schweizer-269c) (registry code 8059502) (OpenAirDocs) - Registry engine: [Lycoming HIO-360 series](https://openairdocs.org/engine/lycoming-hio-360-series) (registry code 41524, reciprocating) (OpenAirDocs) - Category: Helicopter - Serial number: S1297 - Airframe hours: 3891 - Engines: LYCOMING HIO-360-D1A 190 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 29, 2012, 15 hours before - Departed: CNB, Canby, MN - Destination: CNB, Canby, MN ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 46; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; seat: left; flight hours: 1,095 total, 250 in this make and model, 37 in the last 90 days, 15 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F - Altimeter: 30.00 inHg - Observed at: CNB, 10 nm away ## 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 20130723013379A](https://openairdocs.org/incident/20130723013379A), Jul 23, 2013: Schweizer 269C, Gary, SD, Substantial damage. On July 23, 2014 a pilot and 2 passengers departed in a Schweizer 269C helicopter from the canby, MN airport at approximately 1500 hours local for some local… ## Docket (6 files) The files NTSB released with the investigation on September 29, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=87559. 7.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 451 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416972&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Materials Lab Factual Report (item 2, .PDF, 6.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416973&FileExtension=.PDF&FileName=Materials%20Lab%20Factual%20Report-Master.PDF - FAA Engine Notes (item 3, .PDF, 646 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416974&FileExtension=.PDF&FileName=FAA%20Engine%20Notes-Redacted.PDF - Engine Examination Notes (item 4, .PDF, 18 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416975&FileExtension=.PDF&FileName=Engine%20Examination%20Notes-Master.PDF - Excerpt of Engine Logbook (item 5, .PDF, 151 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416976&FileExtension=.PDF&FileName=Excerpt%20of%20Engine%20Logbook-Redacted.PDF - Excerpt of Engine and Airframe Logbook (item 6, .PDF, 143 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416977&FileExtension=.PDF&FileName=Excerpt%20of%20Engine%20and%20Airframe%20Logbook-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.