NTSB investigations: Piper PA-32-300, 2003
10 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
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\") = 2003
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") = 2003
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 CHI04LA034Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Superior, WIThe pilot's failure to maintain directional control of the airplane during the landing roll. Factors associated with the accident were the ditch that the airplane contacted.NTSB MIA04FAMS1Accident · 1 fatalMissing aircraftFinal reportPiper PA-32-300 · Missing, BahamasUndetermined.NTSB MIA04CA006Accident · No injuriesData collectionFinal reportPiper PA-32-300 · Everglades City, FLThe pilot's failure to maintain the proper glide path during the approach to land, which resulted in him undershooting the runway.NTSB IAD03FA070Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Factoryville, PAThe pilot's improper in-flight decision to descend below the published minimum descent altitude while executing a non-precision approach in instrument meteorological conditions, which resulted in collision with trees. A factor was the fog.NTSB ATL03LA108Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Fort Mill, SCThe pilot's mismanagement of the fuel supply, which resulted in fuel starvation and the subsequent loss of engine power.NTSB ATL03FA089Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Calhoun, GAThe pilot's failure to obtain a preflight weather briefing, which would have indicated that MVFR to IFR conditions prevailed over the route with embedded thunderstorms and rain, and his decision to continue VFR flight into instrument meteorological…NTSB ANC03LA044Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Kotzebue, AKThe pilot's failure to maintain adequate altitude/clearance, which resulted in an in-flight collision with terrain during cruise flight. Factors associated with the accident were flat light conditions, and snow-covered terrain.NTSB FTW03FA120Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Broken Arrow, OKFailure of the engine due to the blow-by condition in the number six cylinder for undetermined reasons, which resulted in oil starvation and eventual failure of the associated connecting rod end cap. Also causal was the pilot's failure to maintain airspeed…NTSB NYC03FA061Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Monterey, MAThe pilot's improper decision to attempt a visual flight rules (VFR) flight in marginal VFR weather conditions over mountainous terrain, which resulted in an in-flight collision with trees. Factors in this accident were clouds and night light conditions.NTSB ATL03FA049Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Sylvania, GAThe pilot's decision to conduct VFR flight into instrument meteorological conditions, and his failure to maintain obstacle clearance. Related factors were the guy wire and the fog.