Piper PA46 500TP incident near Denver, Colorado, July 7, 2014
On July 7, 2014 at about 4:38 pm local time, a 2001 Piper PA46 500TP, registered N406CD, suffered minor damage in an incident during taxi (into takeoff position) near Denver, Colorado (Centennial airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilots' incorrect activation of the Manual Override Lever, during ground operation, in an attempt to correct a sub-idle speed condition of the engine, resulting in an over-temperature of the CT blades, their subsequent distress and failure of the engine. Contributing to the incident was: The incorrect guidance of the Piper Meridian Pilots' Operating Handbook which, contrary to the engine manufacturer's recommendation, allowed the operation of the Manual Over ride Lever during ground operation.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 7, 2014 · about 4:38 pm local time
- Place
- Denver, Colorado · Centennial · map
- Type
- Incident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA46 500TP 500TP, built 2001 · all PA46 500TPs on the register
- Registration
- N406CD · registry record · serial 4697046
- Damage
- Minor damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
AIRFRAME ENGINE CONTROLS Before the engine was removed, an examination of the aircraft after the event revealed that all FCU control pressure (Py and P3) lines were intact, secured and leak-free. Additionally, the FCU control linkage and cabling from cockpit quadrant to the power lever (PLA) and the MOR lever were connected and operated smoothly and with full range of travel. The MOR linkage was further examined and no rigging errors were detected. Findings: No engine control rigging errors on the airframe were detected. ENGINE On September 16-18, 2014, the engine was examined at the P&WC facility in Montreal, Canada. Findings: Examination of the engine and accessory components revealed no anomalies that would have contributed to the reported event. GARMIN DATA A review of the data from the Garmin onboard readout device revealed that during the last taxi, the engine was allowed to decay to a sub-idle condition with gas generator speed (Ng) approximately 39% (normal idle Ng is 64%) and ITT 830° Celsius (°C) when Ng increased to approximately 47% and the ITT almost to 1300° C, corresponding to the activation of the MOR. According to the P&WC manuals, the maximum operating turbine temperature limit for takeoff is 800°C while the maximum allowable transient (limited to only 5 seconds) temperature during starting is 1000 °C. Turbine engines, at idle, require a minimum speed to operate. When operating below this speed, the compressor is operating in an inefficient manner, and cannot supply enough cooling air to the core components, causing a hot condition. When, in this already hot condition, an acceleration demand is made of the engine, excess fuel is injected into the combustor, further heating the core components, causing an overtemperature. High bleed air demands from the engine at idle can cause a decaying rpm condition. During this event, a hot day caused the pilot to increase air conditioning in the cabin which took considerable bleed air from the engine, which may have caused a decrease in RPM. To correct this decrease, the pilot must simply increase the power lever until idle speed is maintained. If the pilot does not pay attention to the idle RPM, and allows it to go to a sub-idle condition, a 'bog-down' may result and the fuel control will sense this and refuse to accelerate. The only option for the pilot is to shut the engine down and re-start. If the MOR is used at this time, an engine overtemperature and failure will likely result. Findings: The pilot did not pay attention to the engine indications and allowed the engine to 'bog down'. His subsequent use of the MOR caused the overtemperature and failure of the engine. Based on the pilots' statement, the Garmin readout data, and the lack of any anomalies in any of the engine accessories, it was concluded that the cause of the fire from the exhaust was due to the sudden introduction of fuel by the activation of the MOR, which along with the sub-idle speed condition of the engine at the time of the activation, resulted in a significant high temperature exposure of the CT blades, and their subsequent distress and failure of the engine. PIPER MERIDIAN POH MOR GUIDANCE The pilot stated that he believed that his use of the MOR was in accordance with the Piper pilot's operating handbook (POH). A review of the Piper POH Section 4 - Normal Procedures (Reference: Piper Report: VB-1689 – Revision June 4, 2013) revealed that the Piper guidance was contrary to the P&WC recommendations, which states "the emergency manual override system which is intended to be used in the event of a loss of Power Lever (PLA) control due to loss of air pressure to the Fuel Control Unit (FCU) during flight.", Piper guidance allows pilots to use the MOR on the ground, even at sub-idle RPM conditions, and further, gives the impression that reverting to the MOR is a normal procedure rather than an emergency procedure. Findings: A review of the Piper POH revealed an error in the guidance for MOR operation.
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
- Fire/smoke (non-impact) during taxi (into takeoff position) defining event
- Powerplant sys/comp malf/fail during taxi (into takeoff position)
The NTSB's findings
- Organizational issues › Management › Communication (organizational) › Between groups/organizations › Manufacturer
- cause Organizational issues › Management › Communication (organizational) › Between groups/organizations › Manufacturer
The aircraft
- Landing gear: fixed
- Engine: P&W PT6A SER (turboprop); 0 hours total
- Fire on the ground
- Operator: Lavinia Aircraft Leasing LLC
The flight
- Departed from: APA Denver CO
- Destination: Phoenix AZ
- Flight plan: none
Weather at the time
- Light: daylight
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
