NTSB investigations: Piper PA-34-200T

8 cases on aircraft the registry lists as Piper PA-34-200T, where the first occurrence was “Airframe/component/system failure/malfunction”. 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

19902026
NTSB investigations: Piper PA-34-200T per year, 1990–2026: 8 cases
19901
19911
19921
19951
19961
19971
20041
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 ('7103406')
      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\" = 130))
  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 DEN07CA046Accident · No injuriesData collectionFinal reportPiper PA-34-200T · Walden, COThe pilot experiencing lateral flight control stiffness for undetermined reasons and the pilot's intentional wheels up landing. Factors were the snow covered and rough/uneven terrain.Jan 1, 2007 · N821GS · Substantial damageNTSB IAD05LA001Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Robbinsville, NJThe repair station's improper installation of the stabilator trim tab. A factor was the pilot's inadequate preflight inspection of the airplane.Oct 2, 2004 · N5507V · Substantial damageNTSB FTW98FA044Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Myton, UTThe pilot exceeded the design stress limits of the airplane which resulted in an in-flight airframe overload failure. A related factor was the dark night.Nov 7, 1997 · N2119D · 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 ATL95FA078Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Covington, TNThe pilot exceeded the design stress limits of the aircraft and subsequent overload failures of the stabilator and wing spars.Apr 8, 1995 · N6390C · DestroyedNTSB DEN92IA072Incident · No injuriesIncident investigationFinal reportPiper PA-34-200T · Lamar, COFractured nose landing gear bolt due to fatigue.Jul 8, 1992 · N3030K · Minor damageNTSB SEA91FA099Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Ravensdale, WAThe in-flight breakup of the airplane as a result of the pilot exceeding the speed and stress limits for the airplane. A factor relating to the accident was the center of gravity loading that exceeded the aft limits.May 7, 1991 · N2859M · DestroyedNTSB NYC90LA049Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Messena, NYThe airplane striking a light pole during an off airport landing on a road, due to a double power loss for unknown reasons. Factors related to the accident were: the pilots unfamiliarity with the airplane.Jan 11, 1990 · N1506X · Substantial damage