NTSB investigations: Piper PA-44-180

6 cases on aircraft the registry lists as Piper PA-44-180, 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

19842026
NTSB investigations: Piper PA-44-180 per year, 1984–2026: 6 cases
19841
19931
19951
20001
20031
20071

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 ('7104402', '7104406')
      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 CHI08FA027Accident · 2 fatalField investigationFinal reportPiper PA-44-180 · Browerville, MNAn in-flight collision with at least one Canada goose, and the resulting damage to the left stabilator that caused the airplane to become uncontrollable. Contributing to the accident was the night lighting condition, which precluded any possibility of the…Oct 24, 2007 · N327ND · Substantial damageNTSB LAX03LA172Accident · No injuriesLimited investigationFinal reportPiper PA-44-180 · Livermore, CAthe pilots acceptance of a clearance meant for another aircraft. Contributing to the accident was the failure of departure controller to detect the pilot's incorrect read back and the controllers improper radio technique, which increased the chances of call…May 30, 2003 · N3060K · Substantial damageNTSB MIA01LA017Accident · No injuriesLimited investigationFinal reportPiper PA-44-180 · Daytona Beach, FLan inadvertent inflight collision with a bird during cruise flight that resulted in substantial damage to the airplane.Oct 21, 2000 · N928ER · Substantial damageNTSB ATL95FA174Accident · 2 fatalField investigationFinal reportPiper PA-44-180 · Columbia, SCthe pilot's improper IFR procedure by allowing the airplane to descend below the ILS glideslope and by continued descent below the decision height. Factors relating to the accident were: darkness, low ceiling, and fog.Sep 27, 1995 · N2160E · DestroyedNTSB NYC94LA030Accident · No injuriesLimited investigationFinal reportPiper PA-44-180 · Hopkinsville, KYthe pilot's improper IFR procedure by conducting flight below minimum descent altitude (MDA) without visual referece which resulted in an inflight collision with wires. A factor was the wire.Dec 3, 1993 · N39595 · Substantial damageNTSB SEA85FA028Accident · 1 fatalField investigationFinal reportPiper PA-44-180 · Gig Harbor, WAThe plt departed in the early morning hours from salem, OR, destined for Gig Harbor. Upon arrival in the destination area the plt was in radio contact with seattle apcon. The plt reported he was unable to aquire visual contact with the arpt. Vectors were…Dec 9, 1984 · N2104D · Destroyed