NTSB investigations: Piper PA-34-200T, 1996

7 cases on aircraft the registry lists as Piper PA-34-200T. 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

19712026
NTSB investigations: Piper PA-34-200T, 1996 per year, 1971–2026: 278 cases
19711
19754
19765
19778
197810
19799
198017
198112
198214
198311
19848
198510
19869
19877
19889
19896
19906
19919
19925
19935
19944
19957
19967
19979
19985
19994
20004
20015
20026
20034
20042
20051
20065
20077
20086
20095
20103
20122
20134
20142
20151
20162
20173
20183
20192
20212
20221
20233
20243
20261

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\") = 1996
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103406'))
  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 MIA97FA040Accident · 3 fatalField investigationFinal reportPiper PA-34-200T · Birmingham, ALfailure of the pilot to follow emergency procedures and feather the malfunctioning engine, which led to a forced landing and subsequent collision with a chimney (residence) and the terrain. His lack of recent experience in make/model of aircraft was a related…Dec 16, 1996 · N872SD · DestroyedNTSB NYC97FA013Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Lehman Township, PAThe failure of the forward fuselage nose assembly for an undetermined reason, which resulted in an in-flight breakup of the airplane.Nov 6, 1996 · N5671V · DestroyedNTSB SEA97FA006Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Cle Elum, WAThe pilot's physical impairment of judgment and performance, his decision to fly while impaired, and his subsequent failure to maintain control of the aircraft which led to the aircraft's design stress limits being exceeded and inflight separation of the…Oct 8, 1996 · N666HL · Substantial damageNTSB SEA96LA127Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Aurora, ORinadvertent retraction of the landing gear by the pilot during landing.Jun 14, 1996 · N67SA · Substantial damageNTSB FTW96FA088Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Wichita Falls, TXThe inadvertent stall by the pilot in command. Factors were the impeded airplane takeoff performance, the rudder trim not corrected by the pilot, and the pilot's failure to comply with the checklist.Jan 13, 1996 · N8894E · DestroyedNTSB CHI96LA068Accident · Serious injuriesLimited investigationFinal reportPiper PA-34-200T · Des Moines, IAthe pilot not using the airplane's deice system which resulted in an accumulation of empennage ice and a tailplane stall. Factors relating to this accident were the pilot's intentional flight into known icing conditions, and the icing conditions.Jan 10, 1996 · N3679M · Substantial damageNTSB ATL96LA030Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Gulfport, MSinadequate preflight planning/preparation by the pilot, and inadequate supply of fuel in the airplane, which resulted in fuel exhaustion and subsequent ditching at sea.Jan 7, 1996 · N424WA · Substantial damage