CEN19LA098 · Piper PA32R 300
Piper PA32R 300 · Accident: loss of engine power (total) en route
From Mobile Downtown Airport (BFM) to St Louis Downtown Airport (CPS)
Event
- NTSB case
- CEN19LA098
- 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 PA32R 300
- Aircraft type
- Piper PA32
- 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
- N750R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mobile Downtown Airport (BFM), Mobile, ALTo St Louis Downtown Airport (CPS), Cahokia, IL
- Aircraft age
- About 43 years (built 1976)
- 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 he heard a "horrible noise" and that the engine "immediately seized" about 10 minutes from the destination airport. Oil covered the windshield and obstructed his forward field of view. He executed a forced landing to a road by holding the airplane in a right crab so that he could see out of the left side window. The airplane came to rest inverted in the grass adjacent to the road and sustained damage to the fuselage and wings.
A postaccident engine examination revealed that the No. 4 and No. 6 connecting rods had fractured and separated from the crankshaft. Metallurgical examination was unable to determine the source of the initial failure due to secondary mechanical damage. The intact fracture surfaces that were available for examination exhibited features consistent with overstress.
Probable cause
The loss of engine power due to a connecting rod failure for reasons that could not be determined due to secondary mechanical damage, which resulted in a subsequent forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19LA098
- Event ID
- 20190312X02726
- Case number
- CEN19LA098
- 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: a070e6055c7af97cfc129097693313eed4fac6f0c24b916457dbfb5ab4294906; retrieved 2026-09-16T08:39:23.303Z.