NTSB investigations: Piper PA-31-350, 2000
10 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\") = 2000
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") = 2000
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 ANC01LA027Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-350 · Deadhorse, AKThe pilot's continued VFR flight into instrument meteorological conditions. Factors associated with the accident were clouds, fog, dusk light conditions, and the pilot's self-induced pressure to complete the flight prior to nightfall.NTSB DEN01LA005Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Grand Junction, COTotal failure of the right forward inboard landing gear door hinge pin for undetermined reasons.NTSB DEN00LA179Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Blanding, UTThe pilot's failure to follow the checklist and lower the landing gear for landing. A factor was diverted attention.NTSB ANC00LA133Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Emmonak, AKThe pilot's continued operation of the airplane on unsuitable terrain, and the subsequent failure of the main landing gear torque link. Factors in the accident were rough and uneven runways, and inadequate surveillance of airport facilities/runway conditions…NTSB LAX00FA310Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Hilo, HIDeterioration and failure of the oil filter converter plate gasket, which resulted in a loss of engine power and a subsequent in-flight fire.NTSB ATL00FA081Accident · 3 fatalField investigationFinal reportPiper PA-31-350 · Lumber City, GAPilot's failure to follow instrument procedures and descended below approach minimums and collided with trees. A factor was low clouds.NTSB DCA00MA080Accident · 11 fatalMajor investigationFinal reportPiper PA-31 Navajo · Burlington Twp., NJthe failure of the pilots of the two airplanes to see and avoid each other and maintain proper airspace separation during visual flight rules flight.NTSB LAX00LA277Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Boulder City, NVThe fatigue fracture and separation of the No. 6 cylinder fuel injector line due to the company maintenance personnel's failure to comply with an Airworthiness Directive. A factor in the accident was the company's decision to operate the aircraft in…NTSB DEN00FA102Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Kiowa, COthe flight instructor's failure to maintain aircraft control while practicing stall maneuvers, which resulted in an inadvertent spin.NTSB ANC00IA063Incident · No injuriesIncident investigationFinal reportPiper PA-31-350 · Tanana, AKAn in-flight oil leak due to the deterioration of oil filter adapter plate gasket material, and the supplier's distribution of inadequate material. A factor associated with the accident was the engine manufacturer's inadequate quality control.