NTSB investigations: Piper PA-28-160

7 cases on aircraft the registry lists as Piper PA-28-160, where the first occurrence was “In flight collision with object”. 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

19822026
NTSB investigations: Piper PA-28-160 per year, 1982–2026: 7 cases
19821
19881
19933
19952

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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102806')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
  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 SEA95LA151Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Kent, WAThe pilot's failure to maintain clear of the trees. The dark night light condition was a factor.Jul 15, 1995 · N5040W · Substantial damageNTSB CHI95LA150Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-160 · East Gull Lake, MNthe pilot's failure to maintain clearance from the trees. Factors in the accident were the crosswind and gusts.May 14, 1995 · N5528W · DestroyedNTSB MIA93FA160Accident · 4 fatalField investigationFinal reportPiper PA-28 · Morriston, FLVFR flight by the pilot(s) into instrument meteorological conditions (IMC) and failure to maintain adequate altitude (or clearance) from the tower. The proximity of the tower/guy wires and weather condition were related factors.Jul 21, 1993 · N5096W · DestroyedNTSB CHI93LA244Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-160 · California, MOThe pilot in command's failure to maintain adequate airspeed.Jul 7, 1993 · N5638W · Substantial damageNTSB CHI93LA148Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-160 · Yankton, SDThe pilot in command's failure to maintain proper clearance. Gusty wind conditions were a factor.Apr 24, 1993 · N5548W · DestroyedNTSB MKC88FA120Accident · 1 fatalField investigationFinal reportPiper PA-28-160 · Beedeville, ARIntentional buzzing performed, visual outlook not maintained and over confidence in personal ability by the pilot in command.Jul 2, 1988 · N5517W · Substantial damageNTSB FTW82DA289Accident · No injuriesFinal reportPiper PA-28-160 · Quinlan, TXWhile the pilot was inspecting a power line, the aircraft struck a feeder line that was located perpendicular to the line being checked. The line snapped, but the plane contacted the ground and sheared off the right gear. The aircraft became airborne again.…Jun 24, 1982 · N5514W · Substantial damage