CEN14LA030 · Piper PA 32R-300
Baxter Flying Piper PA 32R-300 · Accident: loss of engine power (total) en route
From Drake Field (KFYV) to Tunica Municipal Airport (KUTA)
Event
- NTSB case
- CEN14LA030
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA 32R-300
- Aircraft type
- Piper PA-32
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N5605V
- Operator
- Baxter Flying
- Onboard fatalities
- Unknown
- Route
- From Drake Field (KFYV), Fayetteville, ARTo Tunica Municipal Airport (KUTA), Tunica, MS
- Aircraft age
- About 36 years (built 1977)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during climbout, he noticed that the engine was vibrating. After leveling off the airplane, the vibration worsened, and the engine subsequently experienced a total loss of power. The pilot executed a forced landing onto a road, and the airplane impacted a fence post.
Examination of the engine revealed that the crankshaft was fractured through the No. 8 cheek position between the Nos. 5 and 6 pistons. Fatigue cracking emanated from the connecting rod journal where the No. 5 connecting rod mates. The No. 6 piston cooling nozzle was not found in its position, and its pieces were found in the bottom of the sump; the pieces were more intact than would be expected if they had been ground between the crankshaft and connecting rod for an appreciable amount of time. Also, there was no evidence of a gouge or other mechanical damage on the No. 5 connecting rod journal. Based on this evidence, it is unlikely that the fatigue cracking was initiated by the No. 6 cooling nozzle being lodged against the crankshaft after falling out of position.
About 18 months before the accident, the engine was repaired and overhauled due to a propeller strike. Further, about 4 months before the accident, maintenance personnel performed a top overhaul of the engine, and, about 1 month before the accident, maintenance personnel replaced the No. 2 cylinder. The timing of the failure suggests that an imbalance could have been introduced to the engine during one or both of the maintenance procedures, which could have resulted in the initiation of the fatigue cracking and the subsequent falling out of the No. 6 cooling nozzle; however, the exact cause of the crankshaft fatigue cracking could not be determined.
Probable cause
An engine failure due to crankshaft fatigue cracking for reasons that could not be determined based on the available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14LA030
- Event ID
- 20131030X11216
- Case number
- CEN14LA030
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 80212de4b832badae1b95428bf6ada866d72c1f28f589d055ba1c42040e2bfd5; retrieved 2026-09-15T23:03:31.515Z.