Piper PA-46-310P accident near Elizabethtown, North Carolina, August 6, 2011
On August 6, 2011 at about 9:00 pm local time, a Piper PA-46-310P, registered N469CC, was substantially damaged in an accident during initial climb near Elizabethtown, North Carolina (Curtis L. Brown Field Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 6, 2011 · about 9:00 pm local time · cases in 2011
- Place
- Elizabethtown, North Carolina · Curtis L. Brown Field Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-46-310P · all PA-46-310Ps on the register
- Registration
- N469CC · registry record · serial 46-8408049
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Aircraft maintenance event during prior to flight
- Powerplant sys/comp malf/fail during initial climb defining event
- Loss of engine power (total) during initial climb
- Off-field or emergency landing during emergency descent
- Landing gear not configured during landing (flare/touchdown)
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine fuel and control › Fuel controlling system › Malfunction other cases naming the engine
- cause Personnel issues › Task performance › Maintenance › Installation › Maintenance personnel
- Aircraft › Aircraft power plant › Engine fuel and control › Fuel controlling system › Related operating info other cases naming the engine
- factor Personnel issues › Experience/knowledge › Knowledge › Knowledge of procedures › Pilot
- factor Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › Pilot
- factor Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
Pilot
- Certificate: airline transport pilot, flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; single-engine sea; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 4,930 hours in all; 326 in this make and model; 65 in the last 90 days; 25 in the last 30 days; 3,067 as pilot in command; 1,375 on instruments
- Last flight review: January 10, 2011
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 5,696 hours
- Last inspection: annual inspection, March 24, 2011
- Maximum gross weight: 4,300 lb
- Seats: 6
- Landing gear: retractable
- Engine: Pratt & Whitney Canada PT6A-34 (turboprop); 0 hours total
- Operator: Marking Aviation LLC
The flight
- Departed from: EYF Elizabethtown NC at 9:00 pm
- Destination: EYF Elizabethtown NC
- Flight plan: none
- Runway 15, 4,998 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 190° at 8 knots
- Visibility: 10 statute miles
- Sky: scat at 3,200 ft
- Temperature: 90°F (32°C), dew point 73°F (23°C)
- Altimeter: 29.90 inHg
- Observation at 8:55 pm from EYF
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
20 documents, released by the NTSB on October 19, 2012. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N469CC on the register today · the tail number may have moved to another aircraft since
- Piper PA-46 Malibu, Mirage, Matrix and M-Class 1,695 registered today · the model family and its accident history
- Piper 44,843 aircraft on the register
- Engine: Pratt & Whitney Canada PT6A-34 234 aircraft carry this series today · as the NTSB recorded it
- Curtis L Brown JR Field · nearest airport
- Accidents and incidents in North Carolina 1,762 since 1982 · 304 in the last ten years
- North Carolina 7,130 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA11LA461.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
