FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11LA461 · Piper PA-46-310P

6 Aug 2011 · Elizabethtown, NC, United States

Marking Aviation Piper PA-46-310P · Accident: powerplant system/component malfunction/failure during initial climb

From Curtis L Brown Jr Field (EYF) to Curtis L Brown Jr Field (EYF)

Report a problem

Event

NTSB case
ERA11LA461
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-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
N469CC
Onboard fatalities
Unknown
Route
From Curtis L Brown Jr Field (EYF), Elizabethtown, NCTo Curtis L Brown Jr Field (EYF), Elizabethtown, NC
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
Initial climb
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
Powerplant system/component malfunction/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

  • Aircraft › Aircraft power plant
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot, after takeoff and about 1,100 feet altitude, when turning from the crosswind leg to the downwind leg in the traffic pattern, the engine started to make a noise. The pilot said that he turned back to the runway. He said that the engine was "cutting off" and that the airplane was "sinking fast." He then feathered the propeller and kept the landing gear in the up position in order to extend his glide. He then put the gear handle down when he knew he would reach the runway, but the landing gear did not extend completely before the airplane's belly made contact with the pavement.

About 9 months before the accident, the airplane had incurred a propeller strike while being taxied over a portion of uneven pavement. As a result, it underwent maintenance that required removal of the propeller and engine, disassembly and reassembly of the engine, remounting of the propeller and engine, and rigging. This was accomplished over a 4-month period by multiple maintenance personnel and required safety-ing of multiple engine components. Safety-ing, when done correctly, should never result in nicked, kinked, mutilated, or overstressed safety wire, as it will result in the safety wire breaking under vibrations if twisted too tightly. Postaccident examination of the engine revealed that the power turbine control (Py) line propeller governor fitting lockwire was fractured at the loop through the “B” nut lockwire hole. The nut was found to be backed off about 1/3 to 1/2 turn, and the line could be moved by hand. Functional tests with the "B" nut in its as-found configuration revealed that the engine would stay at sub-idle and would not respond to power lever movement. Macroscopic inspection of the fracture showed features characteristic of overload fracture in tension and torsion at the location of a pre-existing nick. It is likely that the improper securing of the “B” nut on the power turbine control line resulted in the loss of engine power.

However, the pilot could have restored power to the engine by using the manual fuel override switch, which he did not attempt to use. Review of the pilot's operating handbook (POH) revealed that the POH contained guidance regarding the use of the manual fuel override, although all conditions for which it could be used were not clearly stated. Regardless, the pilot should have been aware of the guidance contained in the POH. Since the accident, the manufacturer has updated the POH with more details on the use of the manual fuel override system.

Probable cause

The improper securing of a “B” nut on the power turbine control (Py) line by unknown maintenance personnel, which resulted in a total loss of engine power. Contributing to the accident was the pilot's failure to use the manual fuel override switch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11LA461
Event ID
20110818X95615
Case number
ERA11LA461
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: cc777720313622381a5fb643c19788dea5fdc233c0078ed3a2de5fa203b57d5b; retrieved 2026-09-15T16:38:12.691Z.