NTSB investigations: Piper PA-31-350, 1998
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
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\") = 1998
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") = 1998
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 CHI99FA047Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Waterford, MIthe pilot's descent below the decision height for the instrument approach.NTSB ANC99LA014Accident · No injuriesLimited investigationFinal reportPiper PA-31 · Point Lay, AKFailure of the pilot to maintain a proper glidepath. Factors associated with this accident were the airport not having a VASI system installed, and the lack of visual perception for the pilot.NTSB DEN99FA016Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Hayden, COThe pilot not following instrument procedures and subsequently descended to minimums prematurely. Factors were the mountainous terrain and the falling snow.NTSB NYC99LA005Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Ravenna, OHThe pilot's improper decision to continue to operate the airplane with inoperative equipment which resulted in fuel exhaustion. Factors were the inoperative fuel quantity gauges, and the night conditions.NTSB ANC98LA167Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Noorvik, AKA failure of the pilot to follow the aircraft checklist, and an inadvertent wheels up landing.NTSB ANC98LA143Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Homer, AKA total loss of power in the right engine for undetermined reasons.NTSB FTW98IA361Incident · No injuriesIncident investigationFinal reportPiper PA-31-350 · Denver, COA hydraulic failure due to a ruptured hydraulic line, preventing the extension of the nose and right main landing gear.NTSB ANC98LA120Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Fort Yukon, AKThe pilot's failure to follow the pre-landing checklist. A factor associated with the accident was the pilot's diverted attention.NTSB LAX98FA106Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Novato, CAthe pilot's failure to maintain adequate terrain clearance after initiating a descent over mountainous terrain at night and under marginal VFR conditions. The pilot's self-induced pressure to arrive at class with enough time remaining to take the final…NTSB ANC98LA020Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Nome, AKThe pilot's poor in-flight planning/decision which led to fuel exhaustion and subsequent loss of engine power.NTSB LAX98WA073Accident · No injuriesForeign investigationPiper PA-31 · Philippines