NTSB investigations: Piper PA-32R-300

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

19892026
NTSB investigations: Piper PA-32R-300 per year, 1989–2026: 8 cases
19891
19901
19961
19992
20031
20041
20071

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\" = 250))
  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 CHI08FA054Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Warrens, WIThe decision by the pilot to fly into known adverse weather, and the pilot's failure to maintain control of the airplane due to spatial disorientation. Contributing factors include the clouds and the night conditions.Dec 21, 2007 · N1919H · DestroyedNTSB FTW04FA235Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Rachel, TXThe total failure of the vacuum pump that resulted in an inoperative attitude gyro and spatial disorientation and a subsequent loss of aircraft control by the pilot. Factors were; the prevailing instrument meteorological conditions, and the dark night light…Sep 9, 2004 · N6209J · DestroyedNTSB SEA03FA173Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Warm Lake, IDThe pilot's failure to maintain adequate airspeed during final approach resulting in a stall/spin. Contributing factors were the rapidly rising terrain and trees.Aug 26, 2003 · N6126J · DestroyedNTSB LAX99LA254Accident · No injuriesLimited investigationFinal reportPiper PA32R-300 · Mammoth Lakes, CAThe pilot's failure to attain and maintain an adequate airspeed for the prevailing density altitude. The pilot's failure to abort the takeoff is also causal.Jul 17, 1999 · N1692H · Substantial damageNTSB FTW99FA060Accident · 1 fatalField investigationFinal reportPiper PA-32-300R · Smackover, ARThe pilot's spatial disorientation resulting in a loss of control of the airplane and the ensuing stall/spin. Factors were the low ceilings and the night condition.Jan 2, 1999 · N7676C · DestroyedNTSB LAX96FA226Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Goleta, CAfailure of the flying pilot to maintain control of the airplane, due to spatial disorientation, which resulted in an uncontrolled descent and collision with the water. Factors relating to the accident were: the lack of recent instrument experience by the…Jun 7, 1996 · N4303X · DestroyedNTSB ATL90FA115Accident · 6 fatalField investigationFinal reportPiper PA-32R-300 · Frankfort, KYThe pilot's failure to operate the aircraft within the center of gravity limitations of the aircraft.May 21, 1990 · N5661F · DestroyedNTSB BFO89LA061Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Blacksburg, VAFailure of the pilot to maintain control of the aircraft during the landing flare/touchdown. Factors related to the accident were: adverse wind conditions and the pilot's inadequate compensation for the wind.Jul 22, 1989 · N69WP · Substantial damage