NTSB investigations: Piper PA-22-150, 1999

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, 1999 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\") = 1999
    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 MIA00LA018Accident · Serious injuriesLimited investigationFinal reportPiper PA-22-150 · Newberry, SCa fire in the cockpit caused by the exhaust muffler, which resulted in a forced landing in a field, and subsequent impact with a berm.Oct 29, 1999 · N2648P · Substantial damageNTSB NYC99FA236Accident · 2 fatalField investigationFinal reportPiper PA 22-150 · Goshen, KYA loss of engine power for undetermined reasons which resulted in a forced landing and subsequent collision with terrain. A factor in this accident was the down-sloping terrain.Sep 25, 1999 · N2381P · DestroyedNTSB NYC99LA233Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Minerva, OHThe pilot's failure to maintain directional control.Sep 19, 1999 · N5959D · Substantial damageNTSB LAX99FA301Accident · 1 fatalField investigationFinal reportPiper PA-22-150 · Strathmore, CAThe failure of the pilot to maintain an adequate terrain and obstacle clearance altitude, which resulted in a collision with power transmission wires.Sep 9, 1999 · N1775P · DestroyedNTSB DEN99LA128Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Limon, COThe pilot's selection of the wrong runway for takeoff. Factors were a direct tailwind and high density altitude that deteriorated the airplane's climb capability, and unsuitable terrain on which to make a forced landing.Jul 24, 1999 · N4540A · Substantial damageNTSB DEN99FA120Accident · 4 fatalField investigationFinal reportPiper PA-22-150 · Roy, UTThe pilot inadvertently allowing the aircraft to enter a stall during initial climb following takeoff. Factors were high density altitude and gross weight which exceeded the maximum.Jul 11, 1999 · N7729D · DestroyedNTSB CHI99LA218Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Rogers City, MIThe pilot's inadequate compensation for the crosswind.Jul 7, 1999 · N9964D · Substantial damageNTSB DEN99FA119Accident · 2 fatalField investigationFinal reportPiper PA-22-150 · Coaldale, COThe pilot's failure to maintain control of the airplane for reasons for reasons undetermined.Jul 3, 1999 · N4753A · DestroyedNTSB NYC99LA105Accident · Serious injuriesLimited investigationFinal reportPiper PA-22-150 · Oswego, NYThe pilot's inadequate fuel management which resulted in fuel starvation and subsequent loss of engine power.May 3, 1999 · N2716P · Substantial damage