FTW04LA238 · Piper PA-31-350
Piper PA-31-350 · Accident: total loss of engine power (mechanical failure) en route
From T97 · Port Lavaca, TX to William P. Hobby Airport (HOU)
Event
- NTSB case
- FTW04LA238
- 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-31-350
- Aircraft type
- Piper PA-31
- 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
- N555MC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From T97 · Port Lavaca, TXTo William P. Hobby Airport (HOU), Houston, TX
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Total loss of engine power (mechanical failure)
- 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
- Engine assembly, crankshaft › Fractured
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 1,800-hour commercial pilot reported that while in cruise flight, the left engine stopped producing power and the left propeller fell forward approximately six inches. The pilot secured the engine and made a precautionary landing. The airplane sustained substantial damage during the forced landing to a field. A review of aircraft maintenance records revealed that the airplane experienced a gear-up landing in January 2002, which resulted in a propeller strike. The left engine was removed and inspected per the manufacturer's overhaul manual and returned to service. The engine had accrued approximately 440 hours since it was overhauled. Examination of the engine revealed that the entire three-bladed propeller assembly and the #1 cylinder had separated from the engine. The engine was disassembled and the crankshaft, along with an intact #3 connecting rod assembly and the fractured #2 connecting rod assembly were examined by a Safety Board Materials Engineer. The crankshaft was fractured in two places; one fracture was just forward of the #3 rod journal in the crank cheek, and the other fracture was in the aft crank cheek adjacent to the #2 main journal. The interior surface of the #1 and #2 main bearing halves exhibited significant rubbing and a portion of the bearing liner material was delaminated and was missing from the forward end of the bearing. On the oil slinger face, just forward of the #1 main journal, 360 degree rubbing damage was noted just outboard of the radius. In the rub region, metallic transfer was present with a color consistent with aluminum material. No evidence of radial cracks was observed in this area. An exact determination for the crankshaft failure could not be determined; however, evidence supported two possibilities that could have attributed to its demise. One possibility was that the crankshaft fracture initiated from rubbing damage between the crank cheek aft of the #2 main journal (thrust face) and the crankcase, with the other fatigue region being secondary. The exact cause for the rubbing was not clear, but one possibility was that the bearing liner delaminated and liberated a section causing a reduction in the clearance between the crankshaft and the crankcase as it was rubbing/exiting through the oil slinger. The other possibility was that the propeller strike caused the rubbing/cracking to occur, which was not detected during the subsequent overhaul/inspection.
Probable cause
The fracture failure of the left engine crankshaft for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW04LA238
- Event ID
- 20040927X01495
- Case number
- FTW04LA238
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 7e96d81e8ba504df3ec282cc150ed5d225484c07cfdb5b74059c61c8658d407b; retrieved 2026-09-22T06:43:26.816Z.