NTSB investigations: Piper PA-22-150, 2000

9 cases on aircraft the registry lists as Piper PA-22-150. 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-22-150, 2000 per year, 1964–2026: 1,313 cases
1964114
1965108
196696
196778
196869
196955
197052
197147
197235
197332
197421
197527
197640
197733
197831
197928
198019
198117
198212
198320
198415
198512
198620
198714
198817
198918
199012
199118
199215
19938
199411
19957
199610
199710
199810
19999
20009
200110
20025
20036
20045
200511
20067
20077
20087
20097
20107
20116
20128
20133
20143
20152
20162
20178
20184
201912
20207
20215
20229
20234
20248
20255
20266

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 ('7102210'))
  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 LAX00LA351Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · North Las Vegas, NVThe pilot's inadequate compensation for the gusty and variable crosswind conditions. Factors were the variable and gusty crosswinds.Sep 23, 2000 · N2963P · Substantial damageNTSB ANC00LA122Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Dillingham, AKA malfunctioning main landing gear brake, which precipitated a ground-loop.Sep 13, 2000 · N8DG · Substantial damageNTSB NYC00LA228Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Columbus, OHThe pilot's improper recovery from a bounced landing.Aug 14, 2000 · N2968Z · Substantial damageNTSB FTW00LA218Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Calico Rock, ARthe pilot's inability to maintain airplane control during the landing roll due to the airplane hydroplaning on the wet runway.Jul 29, 2000 · N3514P · Substantial damageNTSB CHI00FA184Accident · 2 fatalField investigationFinal reportPiper PA-22-150 · Quincy, ILThe pilots failure to maintain control of the aircraft and his continued flight into adverse weather. Factors were the fog, and the crops.Jul 6, 2000 · N1783P · DestroyedNTSB ANC00LA064Accident · Minor injuriesLimited investigationFinal reportPiper PA-22 · Gakona, AKThe loss of engine power for an undetermined reason.Jun 5, 2000 · N1724P · Substantial damageNTSB CHI00LA150Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Salem, INthe inadequate compensation for the wind conditions and the failure of the pilot to maintain directional control. A factor to the accident was the crosswind condition.Jun 3, 2000 · N1686P · Substantial damageNTSB MIA00LA154Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Highlands, NCTotal loss of engine power due to the obstruction (insect larva) of the left wing aft fuel system line resulting in a forced landing to non suitable terrain.May 14, 2000 · N6860B · Substantial damageNTSB NYC00LA132Accident · Minor injuriesLimited investigationFinal reportPiper PA-22 · Moneta, VALoss of power for undetermined reasons.May 13, 2000 · N6841B · Substantial damage