NTSB investigations: Piper PA-24-250, 2000

7 cases on aircraft the registry lists as Piper PA-24-250. 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

19642026
NTSB investigations: Piper PA-24-250, 2000 per year, 1964–2026: 1,523 cases
1964152
1965130
1966124
1967137
196863
196960
197052
197155
197254
197343
197441
197536
197634
197743
197827
197924
198025
198116
198219
198313
198411
198519
19868
198716
198815
198914
199014
199115
19924
199312
199415
19958
199613
199714
19983
199913
20007
200113
200210
20036
20048
20056
20068
20078
20085
20095
20104
20119
20128
20135
20148
20155
20166
20171
201810
20197
20204
20214
20228
20236
20247
20255
20268

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 ('7102404'))
  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 DEN01FA021Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Antimony, UTthe pilot's failure to maintain aircraft control while maneuvering. Contributing factors were the pilot's failure to obtain a preflight weather briefing, his VFR flight into IMC, lack of instrument certification, spatial disorientation, low ceiling, and snow.Dec 8, 2000 · N8245P · DestroyedNTSB CHI01LA012Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · Manhattan, KSthe inadequate soft field takeoff procedure by the pilot and his failure to abort the takeoff. Factors were the high grass on the runway, the pilots disregard for the runway conditions, his lack of total experience in the aircraft, the trees, and the pilots…Oct 14, 2000 · N6107P · DestroyedNTSB SEA01WA005Accident · 3 fatalForeign investigationPiper PA 24-250 · Kelowna, CanadaOct 13, 2000 · N6917P · Substantial damageNTSB NYC00FA245Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Lexington, VAThe pilot's attempted VFR flight into instrument meteorological conditions that resulted in spatial disorientation. A factor in this accident was the pilot's inadequate preflight planning.Aug 30, 2000 · N6411P · DestroyedNTSB IAD00FA067Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Bluffton, OHPilot's improper fuel calculations, which resulted in fuel exhaustion. Also causal, was his abrupt maneuver during the forced landing, which resulted in an inadvertent stall.Jul 30, 2000 · N5271P · Substantial damageNTSB MIA00LA218Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · Immokalee, FLThe inadequate supervision of the pilot rated student by the CFI for her failure to note that the fuel selector was positioned to an empty fuel tank. Also, failure of the CFI to attain the proper rate of descent at touchdown resulting in a hard landing.…Jul 16, 2000 · N980AC · Substantial damageNTSB FTW00LA081Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · College Station, TXThe loss of engine power due to fuel system contamination. A factor was the lack of suitable terrain for the forced landing.Feb 13, 2000 · N7878P · Substantial damage