NTSB investigations: Piper PA-32R-300, 1996
7 cases on aircraft the registry lists as Piper PA-32R-300. 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
| 1965 | 1 |
|---|---|
| 1975 | 1 |
| 1976 | 9 |
| 1977 | 15 |
| 1978 | 22 |
| 1979 | 13 |
| 1980 | 12 |
| 1981 | 12 |
| 1982 | 7 |
| 1983 | 9 |
| 1984 | 5 |
| 1985 | 4 |
| 1986 | 5 |
| 1987 | 7 |
| 1988 | 6 |
| 1989 | 10 |
| 1990 | 6 |
| 1991 | 7 |
| 1992 | 4 |
| 1993 | 8 |
| 1994 | 10 |
| 1995 | 6 |
| 1996 | 7 |
| 1997 | 7 |
| 1998 | 2 |
| 1999 | 7 |
| 2000 | 3 |
| 2001 | 7 |
| 2002 | 6 |
| 2003 | 2 |
| 2004 | 4 |
| 2005 | 1 |
| 2006 | 6 |
| 2007 | 1 |
| 2008 | 5 |
| 2009 | 6 |
| 2010 | 7 |
| 2011 | 3 |
| 2012 | 4 |
| 2013 | 3 |
| 2014 | 2 |
| 2015 | 3 |
| 2016 | 3 |
| 2017 | 4 |
| 2018 | 4 |
| 2019 | 6 |
| 2020 | 3 |
| 2021 | 3 |
| 2022 | 4 |
| 2023 | 3 |
| 2024 | 1 |
| 2025 | 3 |
| 2026 | 2 |
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\") = 1996
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103213'))
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") = 1996
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103213'))
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 CHI97LA042Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Garnett, KSthe pilot's improper in-flight planning/decision, including a delay in proceeding to an alternate airport after encountering fog during a night approach, which resulted in loss of engine power due to fuel exhaustion.NTSB FTW96LA369Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Salida, COtotal failure of the induction air control linkage (bolt), which allowed the alternate air door to close and starve the engine of air.NTSB CHI96FA314Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Medford, MNfailure of the pilot to maintain control of the airplane, due to spatial disorientation. Factors relating to the accident were: failure of the (primary) vacuum system and a restriction in the (standby) vacuum system.NTSB LAX96FA226Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Goleta, CAfailure of the flying pilot to maintain control of the airplane, due to spatial disorientation, which resulted in an uncontrolled descent and collision with the water. Factors relating to the accident were: the lack of recent instrument experience by the…NTSB CHI96LA118Accident · No injuriesLimited investigationFinal reportCessna 310R · Marshfield, WIthe failure of the pilot of the PA-32R, N1030Q, to obtain identification of the Cessna 310R, N1835E, visually, and his inadequate visual outlook. A factor was the failure of both pilots to hear communications from each other.NTSB MIA96LA066Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Smithville, TNThe pilot's improper in-flight planning/decision, which resulted in a heavy load of airframe ice, an inability to maintain altitude, and a subsequent emergency landing. Factors relating to the accident were: the adverse weather (icing) condition, which was…NTSB CHI96FA113Accident · 1 fatalField investigationFinal reportPiper PA-32 · Milwaukee, WIInadequate maintenance and inspection in that the Airworthiness Directive which applied to the fuel pump had not been complied with. A factor was the pilot was unable to reach land.