NTSB investigations: Piper PA-46-310P

6 cases on aircraft the registry lists as Piper PA-46-310P, where the first occurrence was “Loss of engine power(total) - mech failure/malf”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.

Cases per year

19862026
NTSB investigations: Piper PA-46-310P per year, 1986–2026: 6 cases
19861
19921
19951
20001
20041
20071

Latest cases

Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
  FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
  WHERE c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7104605', '7104611', '7104624')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 351))
  ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"

Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.

NTSB DEN08IA044Incident · No injuriesIncident investigationFinal reportPiper PA-46-310P · Aspen, COThe failure of the crankshaft due to fatigue. The fatigue crack initiation was not determined.Dec 26, 2007 · N47BC · Minor damageNTSB NYC04LA105Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Taylor, PAThe failure of the number 2 connecting rod, after a main bearing shift, which resulted in a catastrophic engine failure.Apr 13, 2004 · N861DD · Substantial damageNTSB FTW00LA057Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Odessa, TXThe separation of the #1 piston pin due to fatigue, which resulted in a total loss of engine power. A factor was the lack of suitable terrain for the forced landing.Jan 2, 2000 · N4389W · Substantial damageNTSB MIA96FA049Accident · Serious injuriesField investigationFinal reportPiper PA-46-310P · Ocala, FLoil starvation resulting in connecting rod failure in three of the six cylinders due to lack of lubrication. Contributing to the accident was the failure of the pilot to adhere to a ATC vector toward the nearest airport following engine failure which resulted…Dec 27, 1995 · N800SJ · Substantial damageNTSB BFO92LA028Accident · No injuriesLimited investigationFinal reportPiper PA-46 · Baltimore, MDThe failure of the fuel line, for undetermined reasons, resulting in a fuel leak causing an engine fire and total power loss.Jan 30, 1992 · N9103Q · Substantial damageNTSB SEA86IA080Incident · No injuriesIncident investigationFinal reportPiper PA-46-310P · Reno, NVAt FL250 the engine ceased operating due to a failed fuel pump. A restart was successful at 10,000 feet m.s.l. with an uneventful landing. This fuel pump (a model g) had a total time of three hours. It was a replacement for a model c fuel pump which had…Mar 18, 1986 · N4360V · No damage