OpenAirDocs.org

NTSB investigations: Piper PA-36-375

7 cases on aircraft the registry lists as Piper PA-36-375, 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.

Cases per year

19822026

Where

Open the map

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 ('7103620')
      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.

NTSB CHI98LA216Accident · Serious injuriesLimited investigationFinal reportPiper PA-36-375 · Stephen, MNthe visual lookout not being maintained by the pilot. A factor to the accident was the transmission wire.Jun 23, 1998 · N82585 · Substantial damageNTSB FTW97LA105Accident · No injuriesLimited investigationFinal reportPiper PA-36-375 · Danevang, TXThe utility's company failure to notify affected parties of the downed line, and the pilot's failure to maintain clearance with the downed wire. A factor was the downed wire.Feb 18, 1997 · N7167E · Substantial damageNTSB CHI92DCD03Accident · Minor injuriesFinal reportPiper PA-36-375 · Deloit, IAInadequate visual lookout by the pilot in command while performing aerial application maneuvers. A factor in the accident is the pilot's diverted attention.Apr 29, 1992 · N3986E · Substantial damageNTSB CHI86LA153Accident · No injuriesLimited investigationFinal reportPiper PA-36-375 · Breckenridge, MNAircraft collided with a truck while engaged in aerial application work. Pilot was unable to maintain control and the aircraft collided with terrain after an uncontrolled descent. Investigation revealed that the aileron had separated due to the collision.Jun 13, 1986 · N6184A · Substantial damageNTSB DEN85LA137Accident · Minor injuriesLimited investigationFinal reportPiper PA-36 · Claire City, SDThe acft collided with power lines during an aerial application flt. The power lines were located in the middle of the field being sprayed and during the last spray run, while flying into the sun, the acft contacted the lines.May 21, 1985 · N2382Y · Substantial damageNTSB MKC84LA176Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-375 · Storm Lake, IAWhile on the 2nd swath run, the plt maneuvered the acft to cross under power lines bordering the edge of the corn field. He said he misjudged the distance to clear the power lines. The vertical stabilizer & rudder struck the lines & were torn from the acft.…Jun 19, 1984 · N3953E · Substantial damageNTSB FTW82FRJ12Accident · 1 fatalFinal reportPiper PA-36-375 · Wildsville, LAThe pilot took off on a local flight to spray a bean field. About 1000 ft from the end of the field was a 300 ft radio tower. The aircraft was observed to circle the bean field and circle the radio tower twice. During a procedure turn, the aircraft struck the…Jun 21, 1982 · N90297 · Destroyed