NTSB investigations: Piper PA-31-350, 1982
11 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
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 year(c.\"eventDate\") = 1982
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") = 1982
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 MKC83FA045Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Dubuque, IAAt 2015 the flt contacted ARTCC & requested Dubuque wx. They were advised that Dubuque was 500 ft indefinite ceiling, sky obscured, visibility 1/2 mi fog & they would be vectored for a back course rwy 13 apch. The flt then requested the front course apch to…NTSB MKC83IA042Incident · No injuriesIncident investigationFinal reportPiper PA31-350 · Waterloo, IAPrior to landing N600TS reportedly had an unsafe nose gear down indication. At landing touchdown, the nose gear collapsed. Examination revealed no evidence of mechanical malfunction however the bearing ends, p/n 452-412, showed evidence of overload failure.…NTSB LAX83FA055Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · 500 Nm E, Honolulu, HIThe acft departed oakland, CA at 1733 PST on a night flight to honolulu, HI. The flt proceeded without incident until aprx 0050 PST when the plt advised that the left eng was slowly losing oil pressure. At that time, the acft was at an alt of 6000 ft. at…NTSB ATL83AA029Accident · 1 fatalFinal reportPiper PA-31-350 · Brevard, NCAfter a missed approach at asheville the flt was cleared to the greenville-spartanburg arpt at greer,SC. Enroute to greer radar contact was lost. In response to a query from atlanta ARTCC the plt verified his position as being on the 235 deg radial of…NTSB LAX83LA032Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Alturas, CAThe aircraft was landed long on a wet runway, and after overrunning the departure end, it collided with a fence and a dirt bank.NTSB FTW83FA027Accident · 3 fatalField investigationFinal reportPiper PA-31-350 · Baton Rouge, LAThe aircraft crashed and burned shortly after taking off in darkness on an IFR flight plan. The weather was reported as indefinite ceiling, zero obscuration, visibility 1/4 mi with fog, wind 120 deg at 5 KTS. A number of witnesses heard the aircraft, both…NTSB MIA82AA177Accident · 2 fatalFinal reportPiper PA-31-350 · Near Lakeland, FLThe flt was conducting single-eng flt tests with the inboard gear doors removed & was being photographed by a chase acft. At the end of the tests the plt was unable to restart the left eng & returned for a single-eng landing. The plt overshot the landing…NTSB FTW82FA137Accident · 3 fatalField investigationFinal reportPiper PA-31-350 · San Antonio, TXThe pilot was trying to land after both engines failed during takeoff after the aircraft was refueled with jet fuel instead of gasoline. The weather was IFR with fog, low ceiling and rain. The aircraft collided with trees during a forced landing and was…NTSB MIA82IA110Incident · No injuriesIncident investigationFinal reportPiper PA-31-350 · Tallahassee, FLWhile cruising at 8000 feet, the right alternator light came on and the pilot accomplished the required procedures for an alternator failure. Shortly thereafter, he noticed an area of discoloration on the inboard nacelle of the right engine and saw flames…NTSB MIA82DA103Accident · No injuriesFinal reportPiper PA-31-350 · Miami, FLThe pilot was taxiing to gate H-2 to pick up a charter passenger when the aircraft and a vehicle collided. The pilot reported that about five seconds before impact, he saw the vehicle approaching from his ten o'clock position. He applied the brakes, but the…NTSB SEA82DA017Accident · No injuriesFinal reportPiper PA-31-350 · Spokane, WAAfter arriving in the Spokane area, a full ILS was commenced. It was terminated about 200 ft above the decision height with a missed approach. The aircraft was vectored for a second ILS. During the last 400 ft of this approach, about 3/4 to one inch of mixed…