OpenAirDocs.org

NTSB investigations: Piper PA-30

13 cases on aircraft the registry lists as Piper PA-30, where the first occurrence was “In flight collision with terrain/water”. 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 ('7103002')
      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\" = 230))
  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 CHI98LA072Accident · 1 fatalLimited investigationFinal reportPiper PA-30/A · Hastings, NEThe pilot's improper IFR procedure, by which he failed to maintain minimum descent altitude. Fog, a low ceiling, and night condition were a contributing factor.Dec 24, 1997 · N9WG · DestroyedNTSB FTW96LA403Accident · Minor injuriesLimited investigationFinal reportPiper PA-30 · Watkins, COthe pilot-in-command's failure to use proper procedures and engage the turbochargers for takeoff from a high altitude airport. A factor was the high density altitude.Sep 28, 1996 · N37P · Substantial damageNTSB MIA96LA085Accident · Minor injuriesLimited investigationFinal reportPiper PA-30-160 · St. Petersburg, FLthe pilot's failure to maintain the glide slope and becoming distracted by a passenger.Feb 21, 1996 · N8740Y · Substantial damageNTSB CHI91FA108Accident · 4 fatalField investigationFinal reportPiper PA-30 · Thief River Fls, MNImproper IFR procedure of the pilot, while intercepting the ILS localizer, by not maintianing the minimum descent altitude (mda) for that segment of the approach.Mar 18, 1991 · N8290Y · DestroyedNTSB CHI87LA024Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Minneapolis, MNThe pilot flew for an hour trying to get the gear extended, but was unable. After making a gear up landing, an exam revealed the centering cam on the left side of the nose gear was bent and broken. This could have caused the gear to jam and not extend.Nov 13, 1986 · N7668Y · Substantial damageNTSB ATL86FA039Accident · 1 fatalField investigationFinal reportPiper PA-30 · Corning, NYDuring ILS runway 6 approach acft hit high terrain short of the outer marker. When on downwind for approach pilot said he was not receiving the localizer and asked for a surveillance approach. Controller said he could not provide. When cleared for the ILS…Dec 11, 1985 · N7770Y · DestroyedNTSB ANC85FA146Accident · 2 fatalField investigationFinal reportPiper PA-30 · Kodiak, AKDuring a wx briefing at 0719 adt, the plt was advised that VFR flt was not recommended. Later, at 0827. He called the fss to update his wx & filed an IFR clearance. At 0938, the acft departed anchorage. During arrival at Kodiak, the acft was cleared for an…Aug 5, 1985 · N7811Y · DestroyedNTSB MKC85LA138Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Manhattan, KSThe plt said he put the landing gear selector switch to the down position and thought that he observed a green, down andlocked indicator light; however, the acft landed with the gear retracted. Examination of the acft after the accident revealed that the…Jun 23, 1985 · N7012Y · Substantial damageNTSB MIA85FA022Accident · Serious injuriesField investigationFinal reportPiper PA-30 · Jasper, FLDue to a low fuel state the plt elected to make a precautionary landing on a road. Power lines and poles forced the plt to land in unimproved terrain next to the road. During touch down the left wing struck a dirt bank. Exam of the wreckage revealed that 3…Nov 3, 1984 · N777WM · DestroyedNTSB ATL84FA099Accident · 1 fatalField investigationFinal reportPiper PA-30-160 · Massies Mill, VAWhile en route, the plt was progressing northbound when he contacted the Washington fss at 2134 EST for updated wx info. At that time, he described his position as north of lynchburg, VA. The fss briefer noted that his voice was normal, his manner was calm &…Feb 13, 1984 · N8742Y · DestroyedNTSB LAX83LA431Accident · No injuriesLimited investigationFinal reportPiper PA-30B · Marysville, CABoth aircrew members were multiengine rated. One was a multiengine instructor pilot (CFI) & was providing instruction for the other to be upgraded as a multiengine instructor. During a landing, the acft touched down with the gear retracted. Neither pilot…Sep 8, 1983 · N8211Y · Substantial damageNTSB SEA83LA092Accident · No injuriesLimited investigationFinal reportPiper PA-30B · Lakeview, ORThe acft had landed earlier at redmond in what was described as a hard landing. The plt stated the only problem noted was a 'loud squeeking brake' during the rollout. The next leg of the flight was to terminate at reno, but the plt landedat Lakeview to wait…Apr 27, 1983 · N7946Y · Substantial damageNTSB NYC82DA229Accident · No injuriesFinal reportPiper PA-30F · Dubois, PAThe pilot stated that shortly after takeoff the radio master circuit breaker tripped. He repositioned the switch but it tripped again. As the flight returned to the airport the landing gear and flap trim failed to respond. The pilot confirmed a complete loss…Sep 20, 1982 · N330CP · Substantial damage