The U.S. aircraft register, updated daily
Accidents · NTSB MIA97LA243 · Final report

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).

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 November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 13, 1997 · about 4:15 pm local time · cases in 1997
Place
Oxford, North Carolina · Henderson-Oxford · cases near this airport · 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

FatalSeriousMinorNone
Crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Other NTSB records under N9385C the same tail number, which may have belonged to a different aircraft at the time

2000-04-30ATL00LA053 · accident near Mt. Pleasant, SC · substantial damage · no injuries
1987-07-03ATL87LA202 · accident near Liberty, NC · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/MIA97LA243.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.