NTSB investigations: Piper PA-22-160, 2004

6 cases on aircraft the registry lists as Piper PA-22-160. 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-160, 2004 per year, 1964–2026: 471 cases
196436
196543
196629
196734
196820
196915
197019
197118
197213
19738
197412
197515
197613
19778
197810
197911
19804
19817
19828
19834
19844
19866
19875
19884
198910
19905
19915
19928
19933
19942
19954
19961
19975
19985
19992
20005
20015
20024
20033
20046
20053
20071
20083
20095
20105
20114
20125
20131
20141
20152
20162
20173
20181
20191
20212
20223
20232
20242
20253
20263

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\") = 2004
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102214'))
  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 LAX05LA040Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Prescott, AZthe pilot's failure to maintain directional control during landing rollout. A contributing factor in the accident was the pilot's unfamiliarity with the airplane.Nov 24, 2004 · N9827D · Substantial damageNTSB LAX05CA019Accident · No injuriesData collectionFinal reportPiper PA-22-160 · Vacaville, CAthe pilot's failure to maintain directional control during the landing rollout.Oct 30, 2004 · N8158D · Substantial damageNTSB SEA05CA003Accident · No injuriesData collectionFinal reportPiper PA-22/20 · Medford, ORThe pilot's inadequate compensation for crosswind conditions during landing, resulting in his failure to maintain directional control. Factors include the presence of crosswinds.Oct 2, 2004 · N2849Z · Substantial damageNTSB ANC04LA118Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Kenai, AKThe pilot's selection of an unsuitable landing/takeoff site, which resulted in a loss of control and a nose over during an aborted takeoff. Factors in the accident were soft terrain, and the pilot's failure to maintain directional control.Sep 6, 2004 · N9028D · Substantial damageNTSB ANC04LA072Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Beluga, AKThe pilot's selection of an unsuitable area for landing, which resulted in an on ground encounter with rocks during the landing roll, and the collapse of the left main landing gear.Jun 29, 2004 · N9038D · Substantial damageNTSB LAX04LA109Accident · No injuriesLimited investigationFinal reportPiper PA 22-160 · Carefree, AZThe pilot's inadequate fuel management by his failure to switch the fuel tank selector position, which resulted in fuel starvation, a loss of engine power.Jan 17, 2004 · N8718D · Substantial damage