NTSB investigations: Piper PA-32-260, 2008

9 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, 2008 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\") = 2008
    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 WPR09FA038Accident · 3 fatalField investigationFinal reportPiper PA-32-260 · Sedona, AZThe partial loss of engine power while maneuvering for undetermined reasons.Nov 13, 2008 · N3929W · DestroyedNTSB ERA09LA033Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Plymouth, NCThe Piper Dakota (PA-28-236) pilot's failure to see and avoid the Piper Cherokee (PA-32-260).Nov 1, 2008 · N3568W · 2 aircraft · Substantial damageNTSB NYC08LA299Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Cumberland, RIThe pilot's improper fuel management practices, which resulted in fuel starvation and a complete power loss. Contributing to the accident was the pilot's misdiagnosis of the situation, and his cessation of trouble-shooting to positively identify and correct…Sep 1, 2008 · N5529J · Substantial damageNTSB NYC08CA192Accident · Minor injuriesData collectionFinal reportPiper PA-32-260 · Millinocket, METhe pilot’s failure to properly monitor fuel consumption during the flight.May 24, 2008 · N4823S · Substantial damageNTSB NYC08FA180Accident · 2 fatalField investigationFinal reportPiper PA-32-260 · Cruso, NCThe pilot's inadequate preflight planning and inadvertent flight into instrument meteorological conditions with moderate to severe turbulence prevailing. Contributing to the accident were the instrument meteorological conditions and turbulence.May 12, 2008 · N64FP · DestroyedNTSB CHI08CA121Accident · No injuriesData collectionFinal reportPiper PA-32-260 · Vermillion, SDThe pilot's failure to adequately compensate for the crosswind condition. Contributing to the accident were the crosswind and the soft terrain.Apr 18, 2008 · N32394 · Substantial damageNTSB LAX08CA111Accident · No injuriesData collectionFinal reportPiper PA-32-260 · Grand Canyon, AZThe pilot's inadequate compensation for the wind conditions and delay in aborting the takeoff. Contributing to the accident were wind gusts and a crosswind.Mar 30, 2008 · N5521J · Substantial damageNTSB NYC08LA142Accident · No injuriesLimited investigationFinal reportPiper PA32 · New Albany, MSA loss of engine power for undetermined reasons.Mar 20, 2008 · N3304W · Substantial damageNTSB MIA08CA042Accident · No injuriesData collectionFinal reportPiper PA-32-260 · Atlanta, GAThe failure of the pilot-in-command to maintain directional control of the airplane during landing.Jan 14, 2008 · N3528W · Substantial damage