FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24FA078 · Piper Aircraft Inc PA46R-350T

31 Dec 2023 · Mooresville, NC, United States

Piper Aircraft Inc PA46R-350T · Accident: powerplant system/component malfunction/failure en route

Report a problem

Event

NTSB case
ERA24FA078
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
0
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 Aircraft Inc PA46R-350T

Aircraft type
Piper PA46
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
N539MA
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 13 years (built 2010)
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
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

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

NTSB narrative

The pilot departed his home airport for a short local flight. According to ADS-B data, the airplane flew for about 10 minutes before it began a return to the departure airport. About 8 minutes after turning back toward the airport, the airplane had a sudden decrease in groundspeed and began a descent. At the airplane’s last ADS-B position, it was at an altitude of 60 ft above ground level (agl) and less than 1 nautical mile (nm) from the threshold of the airport’s runway. The airplane subsequently struck trees about 40 ft agl, which separated the left elevator, and the airplane came to rest about 58 ft from the trees. A witness near the accident site reported hearing no engine noise from the airplane before impact. A sound spectrum study of audio captured by a security camera near the accident site revealed that, just before impact, the airplane’s propeller was rotating at a rate near 1,100 rpm, which was consistent with the engine at idle or windmilling. A postaccident examination of the airframe and engine revealed that an induction clamp was missing that connected the induction hose to the left side intercooler, and the induction hose coupling was displaced from the intercooler inlet. The induction clamp was not observed during any of the postaccident examinations. All spark plugs were carbon fouled, which was consistent with the engine operating with an overly rich fuel/air mixture. Although the fuel servo testing revealed that the servo was slightly rich at two test points, this small amount of excess fuel flow would not have precluded normal operation of the engine. Testing of the fuel pump revealed that it operated normally at all tested conditions except for the 650 rpm setting, which resulted in a low flow rate of 2 lbs per hour (below the specified 9 lbs per hour). However, the flow rate at 1,100 rpm was 90 lbs per hour, which would have been sufficient flow to support engine operation at idle rpm in flight. No other anomaly was found. Generally, when an induction hose that is downstream of a turbocharger compressor is disconnected from the rest of the induction system, the engine potentially loses a significant amount of manifold pressure. Based on the available information, it is likely that, due to the missing clamp, the induction hose coupling became disconnected from the left side intercooler, which resulted in an imbalance in the intake system, and the fuel mixture becoming overly rich. This would subsequently result in a loss of engine power. The reason the clamp was missing could not be determined as the clamp was not recovered. The postaccident toxicological testing results for samples from the pilot indicated that he had used the medication diphenhydramine, which has a potential to cause sedation and impairing effects. Although the pilot may have been experiencing impairing effects of the medication at the time of the accident, no more specific conclusions about his impairment could be drawn. Additionally, his autopsy report indicated cardiovascular disease, which is associated with increased risk of experiencing a sudden impairing or incapacitating cardiovascular event, such as heart attack or stroke. There was no autopsy evidence that such an event occurred; however, such an event does not leave reliable autopsy evidence if it occurs immediately before death.

Probable cause

A missing induction clamp, which allowed the induction hose to the left side intercooler to become disconnected, resulting in a total loss of engine power due to an overly rich fuel/air mixture.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24FA078
Event ID
20231231193581
Case number
ERA24FA078
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, cause areas. 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: 2c2cd393d072578d69ee8bc56a62b48fa1310451619a438c53aa469db13afa94; retrieved 2026-09-15T08:09:47.730Z.