# NTSB MIA97LA243: Piper PA-32RT-300, N9385C, Oxford, NC, September 13, 1997 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: September 13, 1997, 12:15 local (16:15 UTC) - Place: Oxford, NC - Coordinates: 36.310565, -78.580696 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=36.3106&lon=-78.5807&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report December 31, 1998 - Report: Approved by Office Director - NTSB case key (mKey): 38334 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=MIA97LA243 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/38334/pdf - Page: https://openairdocs.org/ntsb/MIA97LA243 ## Probable cause fatigue failure of the No.4 connecting rod in an area where galling had occurred, which resulted in loss of engine power and a forced landing. Related factors were: the pilot's lack of communication by failing to select the proper UNICOM frequency; and his failure or inability to flare the airplane during the forced landing, while avoiding another airplane that was landing on the same runway. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power(total) - mech failure/malf, cruise - normal - engine assembly,connecting rod - fatigue (cause) - engine assembly,connecting rod - failure (cause) - Forced landing, emergency descent/landing - Hard landing, emergency landing - communications - not attained, pilot in command (contributing factor) - object - aircraft moving on ground - evasive maneuver - performed, pilot in command - flare - not attained, pilot in command (contributing factor) ## Analysis During cruise flight, the pilot felt a vibration, which continued. Subsequently, oil began covering the windshield, and the engine lost power. The flight was vectored toward a nearby airport, but the pilot did not communicate his intentions of a forced landing over the correct UNICOM frequency. Due to an airplane ahead, he landed hard on the displaced portion of the runway. Several holes were noted in the crankcase near the Nos. 1 and 4 cylinders. Examination of the engine revealed that the connecting rods for the Nos. 1 and 4 cylinders had failed. Metallurgical examination of the failed components revealed high stress low cycle fatigue on the No. 4 rod. Also, galling was noted in critical areas on the Nos. 1, 2, and 4 connecting rods and/or caps. A service bulletin indicated that galling in critical areas could cause failure of connecting rods, and galling could occur as a result of high loading such as during engine overspeed or operation with excessive manifold pressure. The engine had been overhauled by the manufacturer and had accumulated about 1,252 hours. ## Factual narrative On September 13, 1997, about 1215 eastern daylight time, a Piper PA-32RT-300, N9385C, co-registered to private individuals, landed hard during a forced landing at the Henderson-Oxford Airport, Oxford, North Carolina. Visual meteorological conditions prevailed at the time and an IFR flight plan was filed for the 14 CFR Part 91 personal flight. The airplane was substantially damaged and the commercial-rated pilot and 1 passenger were not injured. The flight originated about 1155 from the Raleigh-Durham International Airport, Raleigh, North Carolina. The pilot stated that before departure he added 1 quart of oil to the oil sump, which brought the oil quantity to about 10 quarts; the engine oil capacity is 12 quarts. He completed the remainder of the preflight, started the engine and performed an engine run-up before departure, with no discrepancies noted. The flight departed and while flying in VFR conditions at 5,000 feet mean sea level, at 22 inches manifold pressure and 2,400 rpm, he first felt a sudden vibration. He reduced power, increased the propeller blade angle, and turned on the boost pump which did not reduce the vibration. He advised the controller of the emergency and asked the location of the closest airport which the controller advised the pilot of. The pilot then advised the controller that the airport was in sight and he flew toward that location. He then secured the engine with the mixture control and simultaneously oil began covering the windshield. He was advised by the controller of the field elevation and runway length, but the controller did not provide him with the UNICOM frequency. He advised the controller that oil was covering the windshield and while descending, he asked his son, who is not a pilot, in part for the UNICOM frequency. His son did not know what he was asking for but he did select 122.7; the UNICOM frequency is 122.8. The flight continued toward the airport and while on a 1/8 to 1/4 mile final with the landing gear extended, he observed another airplane ahead on short final. He maneuvered the airplane to the right and the airplane touched down hard on the displaced threshold then bounced twice. The left main landing gear then collapsed and the airplane traveled off the left side of the runway coming to rest upright on grass. Examination of the engine by FAA airworthiness inspectors revealed a hole in the crankcase above the No. 4 cylinder, and the cylinder base nut for the upper aft, 3/8 inch diameter stud at that cylinder was not in place. Also, the upper forward 3/8 inch diameter stud for that same cylinder was extended from the crankcase but the nut was installed. A hole was also located above the No.1 cylinder, and a section of the crankcase beneath the No. 1 cylinder was missing. Disassembly of the engine revealed that the Nos. 1 and 4 cylinders connecting rods were failed. The failed components and associated hardware were sent to the NTSB materials laboratory for examination. Metallurgical examination of the failed connecting rod from the No.4 cylinder revealed high stress, low cycle fatigue. Most fractures had been severely damaged by post mechanical impacts. All undamaged fracture areas except the fatigue noted, exhibited evidence of overstress separation. Visual examination of the cylinder Nos. 1, 2, and 4 connecting rods and/or caps was accomplished. Ten separate areas of galling were noted on the No. 2 cylinder connecting rod and rod cap. All the areas were noted to be in critical areas, as described in Lycoming Service Bulletin No. 439A. With respect to the No. 4 cylinder failed connecting rod, galling was noted in the yoke area opposite the failed area. That area was also in a critical area. Examination of the No. 1 cylinder failed connecting rod revealed evidence of galling in one area. Review of the Service Bulletin revealed that the location of the galling determines if the rod is or is not likely to fail. The non-critical areas on the bearing bore of the connecting rod are directly under the I-beam of the rod. All other areas along the bearing bore are considered critical. The Service Bulletin also states that galling is caused by a movement between the surfaces of the bearing insert and the connecting rod during periods of high loading, such as produced during overspeed or excessive manifold pressure operation. Review of the maintenance records revealed that the engine was recorded as being overhauled/rebuilt by the manufacture on May 18, 1990. The engine was recorded as being installed in the accident airplane on August 2, 1990, at a tachometer time of 4,438 hours. The tachometer time at the time of the accident was 5,690.06 hours. According to overhaul records provided by the engine manufacturer, the connecting rods were reworked and during that process, an examination in part for fretting and galling was accomplished to the connecting rods and rod caps. The airplane, minus the retained engine components, was released to Mr. Mark Thompson of USAIG on November 24, 1997. The retained engine components were released to Mr. Mark Ash, the former co-owner, on June 19, 1998. ## Aircraft - Registration: [N9385C](https://openairdocs.org/aircraft/N9385C), registered now, S/N 32R-7885046 (OpenAirDocs) - Reported make and model: Piper PA-32RT-300 (PA-32RT-30) - Registry model: [Piper PA-32RT-300](https://openairdocs.org/model/piper-pa-32rt-300) (registry code 7103215) (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: 32R-7885046 - Airframe hours: 5382 - Engines: Lycoming IO-540-K1G5D 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: James Billings & Mark Ash - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 3, 1997, 120 hours before - Departed: RDU, RALEIGH, NC - Destination: W66, WARRINGTON, VA - Flight plan: IFR - Airport: HNZ, Henderson-Oxford, runway 6, 5,002 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 44; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 1,785 total, 700 in this make and model, 1,600 as pilot in command, 46 in the last 90 days, 5 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 60° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 77 °F, dew point 64 °F - Altimeter: 30.00 inHg - Observed at: RDU, 32 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 19970913030529A](https://openairdocs.org/incident/19970913030529A), Sep 13, 1997: Piper PA32RT300, Oxford, NC, Substantial damage. Engine failure due connecting rod galling. Landed hard bounced and left runway. Service bullitin prior to accident. (-23) on September 13, 1997, about 1215… ## Other investigations on N9385C (2) 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. - [NTSB ATL00LA053](https://openairdocs.org/ntsb/ATL00LA053), Apr 30, 2000: Piper PA-32RT-200 (N9385C), Mt. Pleasant, SC, substantial damage. Probable cause: The airplane collision with a deer during a night landing. - [NTSB ATL87LA202](https://openairdocs.org/ntsb/ATL87LA202), Jul 3, 1987: Piper PA-32RT-300 (N9385C), Liberty, NC, substantial damage 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.