FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA155 · Piper PA-32-301

11 Apr 2024 · Sullivan, MO, United States

Piper PA-32-301 · Accident: loss of engine power (total) en route

From Rochester International Airport (RST) to Kirk Field (PGR)

Report a problem

Event

NTSB case
CEN24LA155
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
Event fatalities
Unknown
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-32-301

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
N651ED
Operator
Unknown
Onboard fatalities
Unknown
Route
From Rochester International Airport (RST), Rochester, MNTo Kirk Field (PGR), Paragould, AR
Aircraft age
About 44 years (built 1980)
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
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 from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot was conducting a cross-country flight when the engine rpm slightly decreased. He attempted to troubleshoot but the engine surged before it lost all power. The pilot then prepared for a forced landing to a field. During the landing roll, the airplane impacted trees at the edge of a down-sloping, wet field. The airplane came to rest upright and sustained substantial damage to the stabilator, fuselage, and both wings. Postaccident examination of the engine revealed that the engine crankshaft had fractured in two locations due to fatigue. The fatigue crack initiation sites were located near rotational wear bands. The inner diameter surfaces and edge faces of two sets of the main bearing journals exhibited severe gouging, cracking, and material spalling, consistent with rotational abrasive wear. Based on the damage, the degraded bearings likely prevented sufficient lubrication, leading to excessive heating and scoring that helped initiate fatigue cracking of the crankshaft. The engine was most recently overhauled about 28 years and 2,439 flight hours before the accident. The manufacturer’s recommended time between overhaul (TBO) interval was 2,000 flight hours or 12 years, whichever occurred first. Although not required for Part 91 operations, following the manufacturer’s recommended overhaul procedures likely would have prevented the bearing failure and subsequent loss of engine power.

Probable cause

A bearing failure that resulted in fatigue failure of the crankshaft and a subsequent total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA155
Event ID
20240411194074
Case number
CEN24LA155
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, coordinates, cause areas. 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: d58f6f58106b0b80e3c7ce50791b804faeef45b6a29706ecaf49bca63fc5f2fd; retrieved 2026-09-16T18:40:01.346Z.