FTW00LA057 · Piper PA-46-310P
Piper PA-46-310P · Accident: total loss of engine power (mechanical failure) en route
From Odessa Schlemeyer Field (ODO) to Clovis Municipal Airport (CVN)
Event
- NTSB case
- FTW00LA057
- 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
- 0
- 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-46-310P
- Aircraft type
- Piper PA-46
- 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
- N4389W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Odessa Schlemeyer Field (ODO), Odessa, TXTo Clovis Municipal Airport (CVN), Clovis, NM
- 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 · climb to 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, piston › Other
Approximate · Estimated position: the centre of Odessa, TX, the place the record names. Not the accident site.
NTSB narrative
The airplane was climbing through 9,000 feet, after departure, when the engine lost total power. The pilot attempted to restart the engine, but was unsuccessful and executed a forced landing north of the departure airport. Postaccident examination of the airplane revealed that there was a hole in the engine crankcase behind the #2 cylinder and the #1 piston pin had separated at its midpoint. Further, examination of the engine revealed that the #1 piston pin failed as a result of fatigue and the #1 connecting rod bushing (piston pin end) was found fragmented in the oil sump.
Probable cause
The separation of the #1 piston pin due to fatigue, which resulted in a total loss of engine power. A factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00LA057
- Event ID
- 20001212X20358
- Case number
- FTW00LA057
- 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. 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: 44df31cca9a2f029dbe02fd5fb9aefc3fcdc82f0cbf6c1c7eb18ea364e8ae46e; retrieved 2026-09-22T13:28:15.869Z.