CEN12LA512 · Piper PA-30
Piper PA-30 · Accident: loss of engine power (total) en route
From Tri-State Airport / Milton J. Ferguson Field (HTS) to Kennett Memorial Airport (TKX)
Event
- NTSB case
- CEN12LA512
- 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-30
- Aircraft type
- Piper PA-30
- 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
- N8121Y
- Operator
- Clark David R
- Onboard fatalities
- Unknown
- Route
- From Tri-State Airport / Milton J. Ferguson Field (HTS), Huntington, WVTo Kennett Memorial Airport (TKX), Kennett, MO
- 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
- 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 systems
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said that the airplane's right engine stopped producing power in flight and that he was unable to maintain altitude. The pilot made a forced landing to a field with the landing gear up, which resulted in substantial damage to the fuselage. Postaccident examination of the right engine revealed that the b-nut from the engine-driven fuel pump to the fuel-metering unit was loose and leaking fuel. The pilot, who owned and maintained the airplane, had completed an annual inspection of the airplane about 10 flight hours before the accident occurred. He had also recently overhauled the airplane's entire fuel system. No other mechanical anomalies that would have precluded normal operation were noted.
Probable cause
The pilot's failure to properly tighten the b-nut from the engine-driven fuel pump to the fuel-metering unit during maintenance, which resulted in a total loss of engine power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12LA512
- Event ID
- 20120802X70303
- Case number
- CEN12LA512
- 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: a76ffca78f1100ccac6fa35d3b1be6bda8f41141fcdc705442a67a25d3c9a03c; retrieved 2026-09-15T19:12:46.292Z.