NTSB investigations: Piper PA-32R-301

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

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19832026

NTSB investigations: Piper PA-32R-301 per year, 1983–2026: 7 cases
1983	1
1984	1
1985	1
1998	1
2000	1
2001	1
2004	1

Where

Open the map

Latest cases

Query with SQL

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 ('7103218') 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" = 220)) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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 ('7103218')
      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\" = 220))
  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.

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 ('7103218')
    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" = 220))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.

NTSB FTW04FA054Accident · 2 fatalField investigationFinal reportPiper PA-32R-301 · Beaumont, TXThe flight instructor's failure to maintain clearance with a static line. Contributing factors were the low cloud ceiling weather conditions and night light conditions.Jan 3, 2004 · N396HP · Destroyed NTSB IAD01FA070Accident · 1 fatalField investigationFinal reportPiper PA-32R-301 · Greenwich, CTThe pilot's failure to maintain control of the airplane while maneuvering in instrument meteorological conditions, due to spatial disorientation. Factors in the accident were the fog, and the pilot's use of a sedating medication.Jun 22, 2001 · N13VH · Destroyed NTSB FTW00LA123Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Rocksprings, TXThe pilot's failure to maintain proper glidepath. A factor was the dark night light conditions.Apr 12, 2000 · N789CA · Destroyed NTSB MIA99FA034Accident · 2 fatalField investigationFinal reportPiper PA-32R-301 · Olive Branch, MSThe pilot's failure to follow IFR procedures when he descended below the published minimum descent altitude.Nov 15, 1998 · N83396 · Destroyed NTSB ATL85LA145Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Columbia, SCThe plt stated that during takeoff the right main gear struck a large dog which ran onto the rwy. The takeoff was continued & the plt circled the arpt for 2 hrs to burn off excess fuel before performing a ldg with the nose gear & the left main ldg gear…Apr 20, 1985 · N8047P · Substantial damage NTSB BFO85FA002Accident · 4 fatalField investigationFinal reportPiper PA-32R-301 · Salisbury, MDAfter contacting millville fss 4 times for wx info the acft departed lincoln park, NY, at 1858 EDT with destination listed on the IFR flt plan as easton, MD. En route the plt diverted to Salisbury, MD, due to wx. After being cleared forthe rwy 32 ILS the acft…Oct 25, 1984 · N81752 · Destroyed NTSB MIA83LA056Accident · No injuriesLimited investigationFinal reportPiper PA-32-301R · Near Vero Beach, FLThe acft collided with tree tops during a night flight but the pilot was able to maintain control and land at a nearby airport. According to the pilot he was on approach to fort pierce airport when the accident occurred. However according to some witnesses…Jan 3, 1983 · N35590 · Substantial damage