NTSB investigations: Piper PA-36-300

8 cases on aircraft the registry lists as Piper PA-36-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-36-300 per year, 1984–2026: 8 cases
1984	1
1985	2
1986	1
1989	1
1993	1
1996	1
1998	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 ('7103612') 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 ('7103612')
      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 ('7103612')
    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 CHI98LA219Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Mobridge, SDThe pilot's failure to maintain clearance from the power lines. Factors associated with the accident were the power lines, and the separation of the vertical stabilizer and rudder which resulted in the pilot's inability to maintain directional control of the…Jun 25, 1998 · N3760E · Substantial damage NTSB FTW97LA029Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Stanton, TXPilot's failure to maintain clearance with a wire resulting in the separation of the rudder and a loss of aircraft control.Sep 8, 1996 · N57871 · Substantial damage NTSB CHI93LA185Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-400 · Elbow Lake, MNthe pilot's failure to maintain an adequate visual outlook during aerial application manuevers.May 31, 1993 · N2342Y · Substantial damage NTSB DEN89DTK01Accident · 1 fatalFinal reportPiper PA-36-300 · Agar, SDThe pilot's failure to maintain an adequate clearance with the powerlines. The powerline is considered to be a contributing factor to the accident.May 23, 1989 · N82644 · Destroyed NTSB FTW86LQG12Accident · No injuriesFinal reportPiper PA-36-300 · Muleshoe, TXThe ag acft was climbing after a pass to clear power lines at the north end of the field. The main lndg gear contacted the top wire as the acft started leveling off. The wire did not break and the acft descended to ground impact. The lndg gear snapped off and…Feb 28, 1986 · N57878 · Substantial damage NTSB FTW86LQG01Accident · No injuriesFinal reportPiper PA-36-300 · Fluvanna, TXThe acft contacted a cattle guard during an attempted takeoff for an aerial application flt. The plt reported the acft was overloaded for the length of rwy being used for the takeoff. He continued to report he was too late in dumping the chemical load. The…Oct 25, 1985 · N3671E · Substantial damage NTSB CHI85LA336Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-300 · Red Lake Falls, MNThe acft contacted wires during an aerial application flt. The plt stated he was maintaining extra alt to avoid tall weeds and the clearance below the wires was misjudged. The wires severed the vertical fin and rudder.Aug 6, 1985 · N2350Y · Substantial damage NTSB CHI84LA238Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Leroy, WIThe acft collided with trees while turning during an aerial application mission. The plt said that the acft started losing altitude in the turn and despite application of full power it continued to settle until trees were hit. The plt reported that during…Jun 15, 1984 · N59662 · Destroyed