NTSB investigations: Piper PA-32-300, 2004

5 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, 2004 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\") = 2004
    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 NYC04CA205Accident · No injuriesData collectionFinal reportPiper PA32-300 · Montauk, NYThe pilot's failure to maintain altitude\clearance while landing. A factor in this accident was the gusty wind conditions.Sep 5, 2004 · N1351H · Substantial damageNTSB FTW04FA208Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Burnet, TXThe pilot's continued flight into known adverse weather, VFR flight into instrument meteorological conditions, and his failure to maintain control of the airplane due to spatial disorientation. A contributing factor was the cloudy weather.Aug 7, 2004 · N927RP · DestroyedNTSB CHI04FA205Accident · 5 fatalField investigationFinal reportPiper PA-32-300 · Point Lookout, MOThe pilot's failure attain adequate flying speed and his delay in aborting the takeoff which resulted in premature liftoff and an overrun of the runway. Contributing factors were the descending embankment, trees and ravine.Aug 2, 2004 · N4230R · DestroyedNTSB FTW04FA172Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Hot Springs, ARThe pilot's failure to fly a stabilized, published instrument approach procedure, which resulted in a collision with mountainous terrain. Factors were the clouds and the air traffic controllers' failure to provide known information that may have assisted the…Jul 2, 2004 · N4123R · Substantial damageNTSB NYC04FA136Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Leominster, MAThe pilot's failure to follow instrument flight procedures resulting in a collision with trees. A factor related to the accident was the low cloud ceiling, and dark night.Jun 2, 2004 · N21072 · Destroyed