CHI05FA162 · Piper PA-46-310P
Piper PA-46-310P · Accident: loss of engine power during takeoff
From Grand Rapids Itasca Co-Gordon Newstrom field (GPZ) to Flying Cloud Airport (FCM)
Event
- NTSB case
- CHI05FA162
- 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
- 1 · 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
- N4386G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Grand Rapids Itasca Co-Gordon Newstrom field (GPZ), Grand Rapids, MNTo Flying Cloud Airport (FCM), Minneapolis, MN
- 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
- Takeoff
- 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
- Loss of engine power
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Exhaust system, wastegate › Jammed
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Procedures/directives, not followed
- Pilot in command › Stall, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was destroyed on impact with terrain during a forced landing following an observed in-flight loss of engine power after takeoff. A witness observed the takeoff and stated that the airplane took off from the end of runway 34. About halfway down the runway the airplane emitted a sound like a rapid misfire, a pop, and then no more audible engine sounds. The airplane was about 300 to 400 feet above ground level at that point. He said that the airplane turned right then turned left to a bank where the wing was straight down. The airplane's wings then leveled, the airplane descended, and it impacted terrain. He stated that the time from the sounds to the impact was about two to three seconds. An on-scene examination revealed no airframe pre-impact anomalies. An engine examination revealed a cracked crankshaft propeller flange. The engine without the turbochargers and with the original crankshaft was test run up to 2,100 RPM. A propeller and governor inspection revealed no anomalies. Examination of the turbocharger system's exhaust bypass valve assembly revealed its butterfly valve was stuck (bound) in the extended closed position. The engine's cracked crankshaft was removed and a serviceable crankshaft was installed. The engine was test run again with a serviceable exhaust bypass valve assembly. The engine produced rated power. The original exhaust bypass valve assembly was reinstalled. The exhaust bypass valve assembly's wastegate bound again during an engine run and a loss of engine power was observed. Sectioning of the bypass valve assembly revealed a bent wastegate shaft. The valve assembly lever arm was bent and exhibited pre-impact toolmarks consistent with pliers loosening a bound wastegate shaft. The airplane's pilot operating handbook and Federal Aviation Administration (FAA) approved airplane flight manual (POH), in part, stated, "ENGINE POWER LOSS DURING TAKEOFF If sufficient runway remains for a normal landing, leave gear down and land straight ahead." The engine manufacturer's maintenance and operator's manual stated that the wastegate is required to be checked for operation and condition during 100 hour inspections. The manual did not specify a procedure for maintenance personnel on how to check the wastegate's operation and its acceptable condition. National Transportation Safety Board Recommendation A-94-081, issued to the FAA in 1994, stated, "Require the amendment of pilot operating handbooks and airplane flight manuals applicable to aircraft equipped with engine turbochargers by including in the 'Emergency Procedures' section information regarding turbocharger failure. The information should include procedures to minimize potential hazards relating to fire in flight and/or loss of engine power." The airplane's POH latest revision was dated October 14, 2002 and review of the emergency procedures section showed that the POH did not contain information, procedures, or amplified procedures on turbocharger failures. The airplane accumulated 8.7 hours of operation since the last annual inspection.
Probable cause
An observed loss of engine power due to the bound/jammed turbocharger wastegate during takeoff, the pilot not maintaining airplane control, and the stall he inadvertently encountered. A factor was the maintenance personnel not replacing the turbocharger wastegate bypass valve assembly during the last annual inspection 8.7 hours of operation prior to the accident. An additional factor was the manufacturer's insufficiently defined inspection conditions for the bypass valve's proper operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05FA162
- Event ID
- 20050711X00980
- Case number
- CHI05FA162
- 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, coordinates. 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: df3581282dca777dc4b9a7c0c4d21f9ff22261f3fafe991cc97b0c5820e9a9c4; retrieved 2026-09-20T17:59:18.558Z.