NTSB investigations: Piper PA-32-300, 2008

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

19672026
NTSB investigations: Piper PA-32-300, 2008 per year, 1967–2026: 767 cases
196713
196813
196915
197024
197123
197222
197322
197429
197531
197629
197723
197834
197923
198028
198117
198220
198315
198411
198523
198610
198712
198819
198925
19908
199112
199213
199317
199411
199510
199610
199713
199811
199910
200012
200112
200211
200310
20045
20059
20069
20075
20086
20092
20102
20113
20127
20132
20144
20155
20164
20174
201811
20194
20207
20212
202212
20238
20249
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 ('7103212'))
  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 NYC08FA319Accident · 1 fatalField investigationFinal reportPiper PA-32 · Atlanta, GAA loss of aircraft control for undetermined reasons.Sep 23, 2008 · N3029Y · Substantial damageNTSB NYC08CA272Accident · No injuriesData collectionFinal reportPiper PA32 · Charleston, SCThe pilot's failure to maintain aircraft control while landing. Contributing to the accident was the crosswind condition and a wind gust, as reported by the pilot.Aug 3, 2008 · N4376X · Substantial damageNTSB LAX08FA203Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Mount Charleston, NVThe pilot's failure to maintain clearance from mountainous terrain and his selection of a cruise altitude that provided inadequate terrain clearance. Contributing to the accident were the high density altitude and the rapidly rising terrain.Jun 28, 2008 · N4063W · DestroyedNTSB DEN08LA082Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Houston, TXLoss of engine power for reasons undetermined. Contributing to the accident was a lack of suitable terrain for a forced landing.Apr 30, 2008 · N303TE · Substantial damageNTSB NYC08CA128Accident · No injuriesData collectionFinal reportPiper PA 32-300 · Apopka, FLThe pilot's failure to maintain clearance/altitude while on the final leg of the approach.Feb 25, 2008 · N812WM · Substantial damageNTSB MIA08CA039Accident · No injuriesData collectionFinal reportPiper PA-32-300 · Lapine, ALThe pilot's failure to attain the proper touchdown point.Jan 12, 2008 · N84JC · Substantial damage