NTSB investigations: Piper PA-32RT-300T

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

19822026

NTSB investigations: Piper PA-32RT-300T per year, 1982–2026: 7 cases
1982	2
1985	2
1989	1
2000	1
2007	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 ('7103216') 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 ('7103216')
      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 ('7103216')
    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 ATL07FA069Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300T · Andrews, NCThe pilot's misjudgment of distance and altitude during a night approach for landing, resulting in an in flight collision with wires and the ground.Apr 9, 2007 · N21423 · Destroyed NTSB ATL01FA008Accident · 1 fatalField investigationFinal reportPiper PA-32RT · Selmer, TNThe pilots inadequate preflight planning and preparation, that resulted in exceeding the designed weight and balance of the airplane. Factors were the pilot's use of inappropriate medications and the collision with trees.Oct 15, 2000 · N789CS · Destroyed NTSB NYC89LA208Accident · Minor injuriesLimited investigationFinal reportPiper PA-32RT-300T · Wolfeboro, NHInadequate compensation for wind conditions by the owner/pilot-in-command (PIC), his failue to maintain proper altitude on the approach, and failure of the other pilot (owner's instructor pilot) to take remedial action. Factors related to the accident were:…Aug 31, 1989 · N21353 · Destroyed NTSB BFO86FA002Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Gaithersburg, MDThe plt was clrd for a VOR rwy 14 apch. On apch, he rprtd at the sleet intxn (a fix on the NDB apch). The acft was then seen flying ovr the arpt on an easterly hdg. UNICOM operator said he then heard the plt call "turning final." However, bfr lndg, the acft…Oct 4, 1985 · N2106X · Destroyed NTSB FTW85LA273Accident · Serious injuriesLimited investigationFinal reportPiper PA-32RT-300T · Brownsville, TXWhile practicing touch-and-go landings the plt allowed the acft to descend below the proper glide slope while on final apch. The acft impacted a power line aprx 1000 ft short of the rwy and crashed on the side of a drainage ditch levee. The elevation of the…Jul 7, 1985 · N21698 · Substantial damage NTSB ATL83FLG02Accident · Serious injuriesFinal reportPiper 32RT-300T · Hilton Head, SCThe aircraft collided with trees after takeoff. The pilot stated he held 80 or 90 KTS indicated and started what he thought was a normal climb. During gear retraction, the aircraft hit the trees.Dec 5, 1982 · N36447 · Destroyed NTSB ATL82FKJ11Accident · Serious injuriesFinal reportPiper PA-32 · Muscle Shoals, ALDuring the approach the pilot stated that he could not extend the landing gear. At some point during the approach the aircraft broke out into VFR conditions. The pilot stated he had the airport in sight when the aircraft struck a 160,000 volt power line.…Jan 22, 1982 · N31937 · Destroyed