NTSB investigations: Piper PA-32-300

8 cases on aircraft the registry lists as Piper PA-32-300, where the sequence of events included Controlled flight into terr/obj (CFIT). 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

20082026
NTSB investigations: Piper PA-32-300 per year, 2008–2026: 8 cases
20081
20101
20111
20121
20131
20221
20231
20241

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 ('7103212')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '120' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
  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 ERA24FA120Accident · 3 fatalClass 3 · FieldFinal reportPiper PA32 · Jackson, OHThe non-instrument-rated pilot’s decision to depart under visual flight rules into instrument meteorological conditions, which resulted in an inflight collision with terrain while maneuvering.Feb 24, 2024 · N8963N · DestroyedNTSB ANC23FA045Accident · 2 fatalClass 3 · FieldFinal reportPiper PA-32-300 · Old Harbor, AKThe pilot’s failure to maintain clearance from rising terrain. Contributing to the accident was the pilot’s delayed decision to turn away from the terrain.Jul 2, 2023 · N1132Q · Substantial damageNTSB CEN22LA218Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-300 · Princeton, MNThe pilot’s failure to maintain proper approach glide path, which resulted in a collision with trees.May 27, 2022 · N2899N · Substantial damageNTSB WPR14LA007Accident · 3 fatalLimited investigationFinal reportPiper PA32 - 300 · Tinian IslandThe pilot’s failure to maintain terrain clearance while maneuvering at low altitude in dark night conditions.Oct 6, 2013 · N4089W · DestroyedNTSB WPR12FA255Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Mountain Home, IDThe noninstrument-rated pilot's continued visual flight into instrument meteorological conditions, which resulted in controlled flight into mountainous terrain.Jun 9, 2012 · N8990N · Substantial damageNTSB ERA11CA365Accident · Serious injuriesData collectionFinal reportPiper PA-32-300 · Bridgeport, CTThe pilot's failure to maintain clearance from a blast fence on final approach to land.Jun 26, 2011 · N600DK · Substantial damageNTSB WPR10FA107Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Honolulu, HIThe pilot's continued visual flight into instrument meteorological conditions at an altitude insufficient to ensure adequate terrain clearance. Contributing to the accident was the air traffic controller's failure to issue a safety alert after observing the…Jan 10, 2010 · N8934N · 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 · Destroyed