NTSB investigations: Piper PA-31-350, 1983
9 cases on aircraft the registry lists as Piper PA-31-350. 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
| 1974 | 1 |
|---|---|
| 1975 | 5 |
| 1976 | 4 |
| 1977 | 3 |
| 1978 | 10 |
| 1979 | 7 |
| 1980 | 5 |
| 1981 | 9 |
| 1982 | 11 |
| 1983 | 9 |
| 1984 | 5 |
| 1985 | 8 |
| 1986 | 7 |
| 1987 | 7 |
| 1988 | 3 |
| 1989 | 9 |
| 1990 | 11 |
| 1991 | 9 |
| 1992 | 4 |
| 1993 | 6 |
| 1994 | 7 |
| 1995 | 9 |
| 1996 | 8 |
| 1997 | 9 |
| 1998 | 11 |
| 1999 | 11 |
| 2000 | 10 |
| 2001 | 7 |
| 2002 | 8 |
| 2003 | 3 |
| 2004 | 9 |
| 2005 | 5 |
| 2006 | 4 |
| 2007 | 8 |
| 2008 | 6 |
| 2009 | 3 |
| 2010 | 5 |
| 2011 | 7 |
| 2012 | 3 |
| 2013 | 3 |
| 2014 | 2 |
| 2015 | 6 |
| 2016 | 1 |
| 2017 | 2 |
| 2018 | 2 |
| 2019 | 3 |
| 2020 | 3 |
| 2021 | 4 |
| 2022 | 1 |
| 2023 | 4 |
| 2024 | 2 |
| 2025 | 2 |
| 2026 | 1 |
Where
Open the mapLatest 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 year(c.\"eventDate\") = 1983
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103110', '7103125'))
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 year(c."eventDate") = 1983
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103110', '7103125'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun 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 DCA84AA013Accident · Serious injuriesFinal reportMcDonnell Douglas DC-10-30CF · Anchorage, AKA Piper PA-31, N35206, (south central air flt 59) was cleared to taxi to rwy 6L. The wx at that time was foggy with about 1/8 mi vsiibility, but the RVR was improving & the arpt was expected soon to be acceptable for takeoffs. The PA-31 crew taxied & waited…NTSB LAX84LA426Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · San Carlos, AZDuring a night landing on a road, the acft was damaged when it hit a berm. According to customs officials. The plt had circled while ground personnel placed rows of lights adjacent to the road, then he landed. There was evidence that illegal drugs had been…NTSB MKC84LA031Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Waterloo, IAAfter takeoff for an FAA part 135 check ride, the aircrew were unable to get a positive up indication for the landing gear. The gear was recycled & then the left main gear would not get a down & locked indication. Repeated attempts to extend the left main…NTSB MKC84LA006Accident · No injuriesLimited investigationFinal reportPiper PA31-350 · Chillicothe, MODuring arrival, the plt attempted to lower the gear, but only 2 of the 3 would indicate down & safe. The plt was unable to extend the left gear, so he continued flying for aprx 1 hr to burn down fuel, then intentionally landed with the gear up. The landing…NTSB NYC83FA241Accident · No injuriesField investigationFinal reportPiper PA-31-350 · Atlantic City, NJUpon landing on rwy 29 the plt became concerned with another acft landing on rwy 11. Although the landing was long the plt elected to remain on the ground due to uncertainty of the other acft's position. When he reached the end of the rwy he turned the acft…NTSB CHI83LA424Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Wheeling, ILThe acft went off the rwy and collapsed the landing gear after power loss during takeoff. Three of the passengers furnished statements and 2 seemed to think that the left engine quit. The acft turned to the right but the pilot did notknow which engine quit.…NTSB ATL83FA293Accident · Minor injuriesField investigationFinal reportPiper PA-31-350 · Richmond, VAThe plt made a forced landing following a power loss on an approach to Richmond, Virginia. The flt had been operating 4 hours, including 7 takeoffs, since refueling. After the accident both propellers were found in the feathered position. The right wing fuel…NTSB MKC83LA103Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-350 · Clinton, MOWhile cruising at 8,500 ft the pax in the right seat noticed that the oil filler access door on top of the right eng wasopen & oil was leaking. The plt checked the eng instruments & the only abnormal reading was a low manifold pressure reading on the left…NTSB DCA83AA019Accident · Serious injuriesFinal reportPiper PA-31-350-T1020 · Fort Belvoir, VAOn a flt from newark, NJ to richmond, VA, the departure time was delayed, and subsequently, the acft did not arrive at richmond until after the refueling facilities were closed. The plt decided there was sufficient fuel aboard to complete the next flt to the…