NTSB investigations: Piper PA-32-300, 2022
12 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\") = 2022
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") = 2022
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 ERA23FA025Accident · 1 fatalClass 3 · FieldFinal reportPiper PA-32-300 · Brentwood, TNA total loss of engine power due to the catastrophic failure of the crankshaft resulting from the improper installation of the crankshaft for this application.NTSB CEN23LA012Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA-32-300 · Paola, KSThe pilot’s improper positioning of the fuel selector, which resulted in fuel starvation and a loss of engine power during a departure climb.NTSB ERA22FA418Accident · 1 fatalClass 3 · FieldFinal reportPiper PA32 · Afton, VAA catastrophic engine failure due to oil starvation, which resulted in a total loss of engine power at night over mountainous terrain.NTSB ERA22LA373Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-300 · Gardiner, NYThe pilot’s failure to go-around in a timely manner which resulted in a collision with a fence.NTSB WPR22LA296Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-32-300 · Corona, CAThe airplane’s partial loss of engine power during the landing for reasons that could not be determined based on the available evidence, which resulted in an off airport landing and subsequent fire.NTSB CEN22FA299Accident · 1 fatalClass 3 · FieldFinal reportPiper PA-32-300 · Mount Pleasant, TXThe pilot’s failure to maintain the proper glidepath while on final approach in night visual conditions, which resulted in a collision with trees.NTSB WPR22LA204Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-32-300 · Snohomish, WAThe total loss of engine power during takeoff due to fuel starvation and the pilot’s improper fuel tank selection and inadequate preflight inspection.NTSB CEN22LA218Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-300 · Princeton, MNThe pilot’s failure to maintain proper approach glide path, which resulted in a collision with trees.NTSB ERA22LA202Accident · No injuriesClass 4 · LimitedFinal reportPiper PA32 · Fountain Inn, SCThe pilot’s failure to obtain the proper touchdown point during landing, which resulted in a runway overrun and collision with a fence.NTSB ERA22LA195Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32 · Carlisle, PAThe pilot’s improper landing flare, which resulted in the airplane’s empennage impacting the runway surface during landing.NTSB GAA22WA306Accident · Minor injuriesClass 5 · ForeignPiper PA32 · Nassau, BahamasNTSB ERA22LA104Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-32-300 · Edisto Island, SCA loss of engine power due to the fatigue failure of the crankshaft counterweight retaining ring and the No. 6 connecting rod.