NTSB investigations: Piper PA-46-310P

7 cases on aircraft the registry lists as Piper PA-46-310P, where the first occurrence was “In flight collision with terrain/water”. 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

19922026
NTSB investigations: Piper PA-46-310P per year, 1992–2026: 7 cases
19921
19931
19951
19961
20012
20061

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\" = 230))
  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 NYC07FA009Accident · 2 fatalField investigationFinal reportPiper PA-46-310P · Odenton, MDThe pilot's failure to maintain adequate clearance from terrain during the approach. Contributing was the pilot's self-induced pressure to land the airplane after being informed by air traffic control that he was not operating in compliance with the ADIZ…Oct 19, 2006 · N9130N · DestroyedNTSB FTW01LA191Accident · 1 fatalLimited investigationFinal reportPiper PA-46-310P · Bulverde, TXthe pilot's failure to obtain airspeed after rotation, which resulted in a stall/mush. Contributing factors were the tailwind condition, high density altitude, and upsloping runway.Aug 23, 2001 · N4362A · DestroyedNTSB NYC01LA174Accident · Serious injuriesLimited investigationFinal reportPiper PA-46-310P · Stow, MAThe pilot's failure to maintain airplane control during a go-around.Jul 16, 2001 · N9133D · DestroyedNTSB LAX96LA313Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Redlands, CAthe pilot's improper weather evaluation. The uphill runway condition and weather associated with thunderstorm(s) were related factors.Aug 23, 1996 · N9130N · Substantial damageNTSB BFO95FA033Accident · 1 fatalField investigationFinal reportPiper PA-46-310P · Cambridge, MDthe commercial/instrument rated pilot's failure to obtain/maintain adequate altitude/clearance during the initial climb after takeoff. Related factors are the pilot's poor planning/decision making, and the fog.Mar 15, 1995 · N166CP · DestroyedNTSB SEA94FA034Accident · 1 fatalField investigationFinal reportPiper PA-46-310P · Mountain Home, IDThe pilot's intentional suicide and impairment from consumption of alcohol.Nov 22, 1993 · N84PM · DestroyedNTSB SEA93LA036Accident · Minor injuriesLimited investigationFinal reportPiper PA-46 · Twin Falls, IDThe pilot's failure to maintain the ILS glide path.Dec 12, 1992 · N856M · Substantial damage