NTSB investigations: Piper PA-24-250, 2006

8 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, 2006 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\") = 2006
    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 DFW07CA034Accident · No injuriesData collectionFinal reportPiper PA-24-250 · Jacksboro, TXThe pilot's improper fuel calculations, which resulted in a loss of engine power due to fuel exhaustion. A factor was the unsuitable terrain encountered during the emergency landing.Dec 3, 2006 · N5697P · Substantial damageNTSB CHI07IA017Incident · No injuriesIncident investigationFinal reportPiper PA-24-250 · Sherman, ILThe loose connecting rod bolt due to a loss of torque and subsequent failure of the connecting rod during cruise flight.Oct 24, 2006 · N6090P · No damageNTSB NYC07LA001Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Hammonton, NJDisplacement of the idler gear assembly, which resulted in a loss of camshaft timing, and a subsequent engine failure. Contributing to the accident was the swampy terrain condition.Oct 3, 2006 · N5097P · Substantial damageNTSB SEA06LA166Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Auburn, WAThe failure of the landing gear's normal retraction/extension assembly due to an overload condition.Aug 19, 2006 · N6249P · Substantial damageNTSB DEN06CA101Accident · No injuriesData collectionFinal reportPiper PA-24-250 · Olathe, KSthe pilot's failure to extend the landing gear prior to landing.Jul 16, 2006 · N6955P · DestroyedNTSB ATL06LA094Accident · 1 fatalLimited investigationFinal reportPiper PA-24-250 · Wilkesboro, NCThe pilot's improper fuel consumption calculations and improper in-flight planning/decision which resulted in a total loss of engine power due to fuel exhaustion, a forced landing, and collision with terrain.Jun 20, 2006 · N5626P · Substantial damageNTSB LAX06CA176Accident · No injuriesData collectionFinal reportPiper PA-24-250 · Carson City, NVThe loss of engine power due to the pilot's inadequate fuel system management, which resulted in fuel starvation and the loss of engine power.May 19, 2006 · N7857P · Substantial damageNTSB ANC06LA041Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Mammoth Lake, CAThe collapse of the right main landing gear during landing, which resulted in a loss of directional control and an on-ground encounter with a snowbank. A factor associated with the accident was other maintenance personnel's inadequate inspection of the…Mar 30, 2006 · N6744P · Substantial damage