NTSB investigations: Piper PA-32-300, 2000
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
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\") = 2000
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") = 2000
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 NYC01FA001Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Seven Springs, PAThe pilot's improper recovery from a bounced landing.NTSB NYC00FA247Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Apple Creek, OHThe pilot's premature liftoff and failure to attain a proper climb rate. Factors related to the accident were the over-gross weight conditions, and the low cloud ceilings.NTSB NYC00LA242Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Nantucket, MAThe pilot's failure to maintain the proper glide path to the runway. Factors related to the accident were the fog conditions and the pilot’s fatigue.NTSB SEA00LA162Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Birkenfeld, ORThe pilot's delayed go-around, which resulted in the aircraft not clearing the fence posts. A contributing factor was the fence posts.NTSB MIA00LA219Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Washington, NCThe inadvertent stall by the pilot-in-command while returning for a precautionary landing. Contributing to the accident was the loose engine cowling.NTSB MIA00WA209Accident · Serious injuriesForeign investigationPiper PA32-300 · Staniel Cay, BahamasNTSB IAD00LA060Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Fitchburg, MApilot's inadequate compensation for the crosswind. A factor was the crosswind.NTSB SEA00FA080Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Fort Smith, MTThe pilot's failure to maintain clearance from the terrain. Factors include low ceilings, snow, rain, and rising, mountainous/hilly terrain.NTSB CHI00LA078Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Saginaw, MIthe pilots failure to maintain directional control of the aircraft. Factors were the icy runway and the snowbank.NTSB ATL00LA028Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Nashville, TNThe pilot's failure to maintain directional control during the landing roll.NTSB LAX00LA088Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Ukiah, CAfailure of the pilot to comply with the checklists in the Owner's Handbook, resulting in a total loss of engine power due to fuel exhaustion.NTSB FTW00LA059Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Sweeney, TXThe pilot's excessive flare resulting in a hard landing. Factors were the loss of engine power for undetermined reasons, the power lines on final approach and the dark night conditions.