Piper PA-32-300 accident near Brentwood, Tennessee, October 18, 2022
On October 18, 2022 at about 12:41 pm local time, a 1969 Piper PA-32-300, registered N600JG, was destroyed in an accident during enroute (cruise) near Brentwood, Tennessee. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A total loss of engine power due to the catastrophic failure of the crankshaft resulting from the improper installation of the crankshaft for this application.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 18, 2022 · about 12:41 pm local time
- Place
- Brentwood, Tennessee · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32-300, built 1969 · all PA-32-300s on the register
- Registration
- N600JG · registry record · serial 32-40726
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane was in cruise flight about 5,400 ft when the pilot declared an emergency due to a partial loss of engine power. The pilot and controller discussed options for the forced landing, but ultimately the pilot announced that the engine was “stopped,” and that the airplane was “heading down.” A witness described the airplane maneuvering about 75 ft above the ground before it impacted wires, crossed the road on which he was driving, and came to rest in trees on the opposite side of the road. He reported that there was no engine noise and that the airplane made only a “whistling” sound. After the airplane came to rest suspended in trees, the witness watched as it caught fire, “shifted,” then fell from the trees before it exploded and became engulfed in flames. Examination of the engine at the accident site revealed that the crankshaft could not be rotated by hand, and the oil suction screen was completely occluded with debris that comprised metallic particles and pieces of rubber material consistent in appearance with pieces of rubber magneto drive cushion (bumper). Further examination revealed that the crankshaft was fractured at the rear edge of the No. 6 connecting rod journal. The No. 6 connecting rod and rod cap were damaged, and the No. 6 rod bearing was extruded. Review of maintenance records indicated that the engine underwent a field overhaul about 10 years before the accident, during which the crankshaft was replaced. At the time of the accident, the engine had accrued about 101 hours since overhaul. Examination of the crankshaft fracture revealed a fatigue crack that initiated at the surface in the fillet radius between the No. 6 connecting rod journal and the forward cheek. Similar fatigue cracks were observed at the forward end of the connecting rod journal with features consistent with excessive loads induced during contact between the connecting rods and the engine case. The No. 6 rod bearing was likely destroyed due to interruption of the oil to the bearing from fatigue crack propagation. The crankshaft was made obsolete 30 years before the engine’s most recent overhaul, and although it was still authorized for use in multiple variants within this series of engines, it was not authorized for use in the accident engine model. Additionally, the connecting rod bearings installed on the accident engine were not authorized for use in the accident engine model. It is likely that the use of a crankshaft that was not approved for use in the accident engine make and model resulted in abnormal contact between the connecting rods and their journals, imparting stress to the crankshaft and resulting in its failure. It is possible that the renitriding of the crankshaft may have affected its ability to tolerate high loading and contributed to the failure. The observed nitride layer was thicker than the original specification, and the core hardness was lower than the specification. Combined, these factors increased the potential to generate cracks. While the oil filter screen was occluded with material consistent with a magneto bumper, there was no evidence of general oil starvation elsewhere within the engine, which would be consistent with an occluded screen; therefore, it is likely that the magneto bumper dropped into the engine due to large vibrations following the crankshaft failure, and broken pieces then became trapped in the oil screen. Further examination revealed that the connecting rod in the number 4 position was labeled 3, and the one in the number 3 position was labeled 4. Although this likely did not contribute to the accident, it is another indication of improper maintenance practices.
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
What happened, in order
- Powerplant sys/comp malf/fail during enroute (cruise) defining event
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Failure
- Personnel issues › Task performance › Maintenance › Installation › Maintenance personnel
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 505 hours in all; 105 in this make and model
- Medical certificate: BasicMed (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 3,623.3 hours
- Last inspection: annual inspection, October 4, 2022
- Maximum gross weight: 3,400 lb
- Seats: 6
- Landing gear: fixed
- Engine: Lycoming IO-540-K1A5 (piston); 3,623 hours total
- Fire on the ground
The flight
- Departed from: M91 Springfield TN at 12:17 pm
- Destination: KFYM Fayetteville TN
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 310° at 5 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 5,000 ft
- Temperature: 37°F (3°C), dew point 21°F (-6°C)
- Altimeter: 30.06 inHg
- Observation at 7:53 am from KBNA, 7 miles away
Weather report (METAR): KBNA 181253Z 31005KT 10SM FEW050 03/M06 A3006 RMK AO2 SLP182 T00281056 $
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
13 documents, released by the NTSB on June 26, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Witness | PDF, 2 pages | View Download |
| 2 | Memorandum for Record Mechanic | PDF, 2 pages | View Download |
| 3 | Fuel Discussion and Receipts | PDF, 3 pages | View Download |
| 4 | Maintenance Records Annual Inspection | PDF, 1 page | View Download |
| 5 | Maintenance Records Review (FAA) | PDF, 1 page | View Download |
| 6 | Maintenance Records Engine Overhaul | PDF, 1 page | View Download |
| 7 | Toxicological Report | PDF, 1 page | View Download |
| 8 | Materials Laboratory Factual Report 23-066 | PDF, 33 pages | View Download |
| 9 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 4 pages | View Download |
| 10 | Medical Factual Memorandum of Record | PDF, 4 pages | View Download |
| 11 | Photo Array | PDF, 4 pages | View Download |
| 12 | ADS-B Raw Data | data file | Download |
| 13 | Air Traffic Control Summary | PDF, 4 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
