NTSB investigations: Piper PA-32-301

8 cases on aircraft the registry lists as Piper PA-32-301, where the first occurrence was “In flight collision with terrain/water”. 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

19842026
NTSB investigations: Piper PA-32-301 per year, 1984–2026: 8 cases
19841
19924
19941
19991
20041

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 ('7103207')
      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\" = 230))
  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 CHI04CA250Accident · No injuriesData collectionFinal reportPiper PA-32-301 · Crivitz, WIThe proper touchdown point not attained by the pilot during landing. The road and tailwind were contributing factors.Sep 2, 2004 · N8173J · Substantial damageNTSB ANC99LA039Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Chefornak, AKThe pilot's selection of an unsuitable landing site. A factor associated with the accident was rough and uneven terrain.Mar 27, 1999 · N81844 · Substantial damageNTSB ANC94FA080Accident · 3 fatalField investigationFinal reportPiper PA-32-301 · Portage Creek, AKThe pilot's inadequate preflight planning and preparation, and his failure to ensure that the airplane was within its gross weight and center-of-gravity limits, which resulted in an inability to obtain sufficient airspeed for sustained flight and a resultant…Jul 11, 1994 · N8297X · Substantial damageNTSB ANC93LA019Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Scammon Bay, AKThe pilots VFR flight into IMC conditions, and his failure to maintain sufficient altitude while maneuvering. Contributing to the accident were the whiteout snow and fog conditions.Dec 4, 1992 · N8374T · Substantial damageNTSB ANC92LA140Accident · No injuriesLimited investigationFinal reportPiper PA-32 · Togiak, AKThe pilot's improper preflight planning/decision, and his delay in aborting the takeoff. Contributing factors were the berm and the standing water on the runway.Aug 22, 1992 · N8402S · Substantial damageNTSB LAX92FA201Accident · 3 fatalField investigationFinal reportPiper PA-32-301 · Camarillo, CAThe pilot's failure to follow the published instrument missed approach procedure, and his failure to initiate a timely climb after being given a low altitude alert. Factors contributing to the accident were: the controller's failure to take positive action…May 6, 1992 · N8408V · DestroyedNTSB MIA92LA068Accident · 3 fatalLimited investigationFinal reportPiper PA-32-301 · Atlantic Ocean (Atlantic Ocean)Undetermined. The airplane crashed in the Atlantic Ocean and was not located.Jan 23, 1992 · N8300X · DestroyedNTSB LAX84FA504Accident · 4 fatalField investigationFinal reportPiper PA-32R-301T · Tucson, AZcontrolled flight into terrain that resulted from the pilot's failure to ensure a safe VFR altitude. The dark night, which restricted the pilot's view of terrain, was a factor in this accident.Aug 30, 1984 · N4575L · Destroyed