NTSB investigations: Piper PA-32RT-300

7 cases on aircraft the registry lists as Piper PA-32RT-300, 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

19842026

NTSB investigations: Piper PA-32RT-300 per year, 1984–2026: 7 cases
1984	4
1990	1
2004	1
2005	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 ('7103215') 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 ('7103215')
      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 ('7103215')
    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 CHI05LA160Accident · Minor injuriesLimited investigationFinal reportPiper PA-32RT-300 · Kansas City, MOThe pilot not maintaining climb airspeed leading to the airplane's impact with the fence and terrain during takeoff. Factors in the accident were the pilot's inaccurate preflight planning calculations, the fence, and the levee.Jun 30, 2005 · N21835 · Destroyed NTSB CHI04LA052Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Fishers, INThe pilot not maintaining altitude/clearance from the trees during the circling approach, his continued descent below minimum descent altitude, and the pilot not performing a missed approach. A factor was the trees the pilot impacted during the circling…Jan 2, 2004 · N21992 · Substantial damage NTSB CHI91FA031Accident · 4 fatalField investigationFinal reportPiper PA-32-RT300 · Gaylord, MIThe pilot's failure to maintain adequate terrain clearance. Factors which contributed to the accident were: the dark night, adverse weather conditions, and the pilot's overconfidence in continuing VFR flight into these conditions.Nov 22, 1990 · N9800K · Destroyed NTSB CHI84FA315Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300 · Sandwich, ILPilot attempted to takeoff with 7 passengers in a six place acft. The acft was 187 lbs over gross wt and 1.54 inches out of aft c.g. the pilot tookoff downwind and collided with trees at the end of the rwy. There was a post crash fire.Jul 28, 1984 · N36219 · Destroyed NTSB LAX84LA303Accident · Serious injuriesLimited investigationFinal reportPiper PA-32RT-300 · Avalon, CAThe plt flew to catalina island, then flew northwest along the north side of the island. He stated that he then made a climbing left turn over the island from about 500 ft MSL, but encountered a downdraft at 1000 ft MSL, which slowed the acft below the…May 20, 1984 · N30298 · Substantial damage NTSB ATL84FA083Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300 · Attalla, ALDuring a VOR approach to land in IMC wx, the acft collided with a tree. The non-instrument rated plt had filed an IFR flt plan on this and other occasions even though he was not qualified. During this approach, the descent was continued past the mda of 960…Jan 16, 1984 · N31844 · Destroyed NTSB ATL84FA080Accident · Serious injuriesField investigationFinal reportPiper PA-32RT-300 · Basye, VAAfter the acft landed, slush was observed to have accumulated under the wings & lower aft fuselage & was freezing. The acft was parked with the tail facing the sun, but none of the arpt personnel noticed whether the sun had melted the ice. The plt indicated…Jan 12, 1984 · N36791 · Destroyed