Piper PA-32RT-300 accident near Oxford, North Carolina, September 13, 1997
On September 13, 1997 at about 4:15 pm local time, a Piper PA-32RT-300, registered N9385C, was substantially damaged in an accident near Oxford, North Carolina (Henderson-Oxford airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 13, 1997 · about 4:15 pm local time
- Place
- Oxford, North Carolina · Henderson-Oxford · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32RT-300 PA-32RT-30 · all PA-32RT-300s on the register
- Registration
- N9385C · registry record · serial 32R-7885046
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land; instrument: airplane
- Flight time: 1,785 hours in all; 700 in this make and model; 46 in the last 90 days; 5 in the last 30 days; 1,600 as pilot in command
- Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
- Seat: left
The aircraft
- Airframe total time: 5,382 hours
- Last inspection: annual inspection, January 3, 1997; 120 hours since
- Maximum gross weight: 3,600 lb
- Seats: 6
- Landing gear: retractable
- Engine: Lycoming IO-540-K1G5D (piston); 0 hours total
The flight
- Departed from: RDU Raleigh NC at 3:55 pm
- Destination: W66 Warrington VA
- Flight plan: IFR
- Runway 6, 5,002 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 060° at 7 knots
- Visibility: 10 statute miles
- Sky: scat at 15,000 ft
- Temperature: 77°F (25°C), dew point 64°F (18°C)
- Altimeter: 30.00 inHg
- Observation at 3:51 pm from RDU, 32 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 1 |
Other NTSB records under N9385C the same tail number, which may have belonged to a different aircraft at the time
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number MIA97LA243.