NTSB investigations: Piper PA-32-260, 1996

8 cases on aircraft the registry lists as Piper PA-32-260. 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

19652026
NTSB investigations: Piper PA-32-260, 1996 per year, 1965–2026: 693 cases
19654
196628
196732
196838
196934
197029
197137
197224
197326
197432
197524
197626
197727
197814
197918
198014
198113
19827
198317
198410
19854
19867
198711
198811
198912
19909
19917
19929
19937
199411
19959
19968
19977
19985
19997
20005
20016
20024
20036
20046
20052
20065
20074
20089
20092
20101
20115
20122
20132
20142
20153
20161
20174
20181
201910
20205
20219
20225
20236
20244
20253
20263

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 ('7103206'))
  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 IAD97LA027Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Claverack, NYloss of engine power for undetermined reasons.Dec 4, 1996 · N3324W · Substantial damageNTSB NYC97FA025Accident · 1 fatalField investigationFinal reportPiper PA-32-260 · Felton, PAThe pilot's inadequate preflight planning and preparation, and his failure to refuel which resulted in fuel exhaustion and the subsequent collision with trees during the forced landing.Dec 3, 1996 · N5538J · DestroyedNTSB CHI97LA012Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Mancelona, MIthe worn fuel system pump (actuator arm). A factor was the unsuitable terrain encountered by the pilot.Oct 20, 1996 · N56155 · Substantial damageNTSB NYC96LA171Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Coatsville, PAloss of engine power for undetermined reason(s). Factors relating to the accident were: darkness, and the lack of suitable landing areas.Aug 23, 1996 · N3868W · DestroyedNTSB IAD96LA130Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Gaithersburg, MDthe unexpected appearance of a deer on the runway.Aug 9, 1996 · N1439T · Substantial damageNTSB MIA96LA202Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Live Oak, FLfailure of the pilot to use carburetor heat during the approach to land, which resulted in loss of engine power due to carburetor ice. The weather (carburetor icing condition) was a related factor.Aug 4, 1996 · N3399W · Substantial damageNTSB CHI96LA174Accident · No injuriesLimited investigationFinal reportPiper PA-32 · Osage Beach, MOa partial loss of power for undetermined reasons.May 25, 1996 · N40933 · Substantial damageNTSB CHI96LA137Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Aitkin, MNthe pilot's improper planning/decision, which resulted in his failure (or inability) to adequately compensation for wind conditions. Factors relating to the accident were: the gusty crosswind condition and the snowbank.Apr 22, 1996 · N4883S · Substantial damage