NTSB investigations: Piper PA-32R-300

8 cases on aircraft the registry lists as Piper PA-32R-300, where the first occurrence was “Undershoot”. 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

19832026
NTSB investigations: Piper PA-32R-300 per year, 1983–2026: 8 cases
19832
19901
19943
19971
20001

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 ('7103213')
      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\" = 390))
  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 ANC00LA038Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Fairbanks, AKThe pilot's misjudgment of distance/altitude, and subsequent undershoot during landing. Factors in the accident were light snow precipitation, flat light conditions, snow-covered terrain, and the absence of a visual approach slope indicator.Mar 27, 2000 · N8540F · Substantial damageNTSB CHI97LA294Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Fargo, NDthe pilot's misjudgment of altitude and distance to the runway, while on final approach to land, and failure to attain the proper touchdown point on the runway during the landing. The exposed runway lip was a related factor.Sep 17, 1997 · N2680Q · Substantial damageNTSB BFO94LA070Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Bedford, PAThe pilot's failure to maintain the proper descent rate which resulted in an undershoot of the runway.Apr 18, 1994 · N4445X · Substantial damageNTSB BFO94LA046Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Berlin, NJThe pilot not maintaining clearance from obstacles (trees) during final approach which resulted in a collision with a tree and a subsequent uncontrolled descent until colliding with the ground.Feb 22, 1994 · N23AL · Substantial damageNTSB MIA94FA069Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Vicksburg, MSFailure of the pilot-in-command to maintain the proper glidepath while on a straight in approach resulting in the inflight collision with trees short of the runway. Contributing to the accident was the dark night condition.Feb 9, 1994 · N1645H · Substantial damageNTSB BFO91LA022Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Mitchellville, MDPilot failure to maintain altitude clearance above an obstacle after the aircraft encountered a downdraft.Dec 30, 1990 · N6945J · Substantial damageNTSB DEN84LA032Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Rawlins, WYThe plt stated that the approach into Rawlins was normal but while on short final he realized that the acft was too low. The acft was actually lower then the runway which is located on a plateau. He attempted to correct but lost airspeed and landed short. The…Nov 30, 1983 · N5802V · Substantial damageNTSB NYC83LA073Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Quakertown, PAThe acft touched down about 1 ft short of the rwy. The left gear & wing was damaged.Feb 28, 1983 · N38389 · Substantial damage