NTSB investigations: Piper PA-32-300, 2008
6 cases on aircraft the registry lists as Piper PA-32-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
| 1967 | 13 |
|---|---|
| 1968 | 13 |
| 1969 | 15 |
| 1970 | 24 |
| 1971 | 23 |
| 1972 | 22 |
| 1973 | 22 |
| 1974 | 29 |
| 1975 | 31 |
| 1976 | 29 |
| 1977 | 23 |
| 1978 | 34 |
| 1979 | 23 |
| 1980 | 28 |
| 1981 | 17 |
| 1982 | 20 |
| 1983 | 15 |
| 1984 | 11 |
| 1985 | 23 |
| 1986 | 10 |
| 1987 | 12 |
| 1988 | 19 |
| 1989 | 25 |
| 1990 | 8 |
| 1991 | 12 |
| 1992 | 13 |
| 1993 | 17 |
| 1994 | 11 |
| 1995 | 10 |
| 1996 | 10 |
| 1997 | 13 |
| 1998 | 11 |
| 1999 | 10 |
| 2000 | 12 |
| 2001 | 12 |
| 2002 | 11 |
| 2003 | 10 |
| 2004 | 5 |
| 2005 | 9 |
| 2006 | 9 |
| 2007 | 5 |
| 2008 | 6 |
| 2009 | 2 |
| 2010 | 2 |
| 2011 | 3 |
| 2012 | 7 |
| 2013 | 2 |
| 2014 | 4 |
| 2015 | 5 |
| 2016 | 4 |
| 2017 | 4 |
| 2018 | 11 |
| 2019 | 4 |
| 2020 | 7 |
| 2021 | 2 |
| 2022 | 12 |
| 2023 | 8 |
| 2024 | 9 |
| 2025 | 3 |
| 2026 | 3 |
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\") = 2008
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103212'))
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") = 2008
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103212'))
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 NYC08FA319Accident · 1 fatalField investigationFinal reportPiper PA-32 · Atlanta, GAA loss of aircraft control for undetermined reasons.NTSB NYC08CA272Accident · No injuriesData collectionFinal reportPiper PA32 · Charleston, SCThe pilot's failure to maintain aircraft control while landing. Contributing to the accident was the crosswind condition and a wind gust, as reported by the pilot.NTSB LAX08FA203Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Mount Charleston, NVThe pilot's failure to maintain clearance from mountainous terrain and his selection of a cruise altitude that provided inadequate terrain clearance. Contributing to the accident were the high density altitude and the rapidly rising terrain.NTSB DEN08LA082Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Houston, TXLoss of engine power for reasons undetermined. Contributing to the accident was a lack of suitable terrain for a forced landing.NTSB NYC08CA128Accident · No injuriesData collectionFinal reportPiper PA 32-300 · Apopka, FLThe pilot's failure to maintain clearance/altitude while on the final leg of the approach.NTSB MIA08CA039Accident · No injuriesData collectionFinal reportPiper PA-32-300 · Lapine, ALThe pilot's failure to attain the proper touchdown point.