NTSB investigations: Piper PA-46-310P, 2000

7 cases on aircraft the registry lists as Piper PA-46-310P. 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

19842026
NTSB investigations: Piper PA-46-310P, 2000 per year, 1984–2026: 115 cases
19841
19851
19864
19872
19892
19902
19915
19925
19933
19943
19954
19964
19982
19991
20007
20014
20024
20032
20043
20053
20062
20075
20084
20092
20106
20111
20121
20132
20143
20153
20163
20171
20181
20193
20204
20212
20221
20233
20243
20252
20261

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 year(c.\"eventDate\") = 2000
    AND 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'))
  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 LAX00FA322Accident · 4 fatalField investigationFinal reportPiper PA-46-310P · So. Lake Tahoe, CAThe pilot's in-flight loss of control in the takeoff initial climb for undetermined reasons.Sep 1, 2000 · N88AM · DestroyedNTSB ATL00LA084Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Vero Beach, FLThe pilot's inability to control the aircraft after landing due to a loss of engine power and landing gear failure for undetermined reasons. A factor in the severity of the accident was the impact with the airport marker lights.Aug 18, 2000 · N4380S · Substantial damageNTSB LAX00FA208Accident · 3 fatalField investigationFinal reportPiper PA-46-310P · Hawthorne, CAA partial loss of power due to water contamination in the fuel system and the pilot's inadequate preflight inspection, which failed to detect the water. The pilot's failure to perform an engine run-up before takeoff is also causal. Additional causes are the…May 28, 2000 · N567YV · DestroyedNTSB LAX00LA117Accident · No injuriesLimited investigationFinal reportPiper PA-46-310 · Palo Alto, CAThe pilot's failure to obtain/maintain the proper visual glide path resulting in an undershoot and collision with the runway edge.Mar 5, 2000 · N43412 · Substantial damageNTSB NYC00LA066Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Bradford, PAThe pilot's inadequate ice/frost removal from the aircraft.Jan 11, 2000 · N9103N · Substantial damageNTSB FTW00LA067Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Corning, ARThe loss of engine power for an undetermined reason. A factor was the dark night light condition.Jan 3, 2000 · N87NF · 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 damage