NTSB investigations: Piper PA-28R-180, 2001
7 cases on aircraft the registry lists as Piper PA-28R-180. 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
| 1968 | 24 |
|---|---|
| 1969 | 36 |
| 1970 | 34 |
| 1971 | 24 |
| 1972 | 27 |
| 1973 | 19 |
| 1974 | 6 |
| 1975 | 12 |
| 1976 | 15 |
| 1977 | 14 |
| 1978 | 13 |
| 1979 | 6 |
| 1980 | 10 |
| 1981 | 10 |
| 1982 | 7 |
| 1983 | 5 |
| 1984 | 2 |
| 1985 | 4 |
| 1986 | 5 |
| 1987 | 6 |
| 1988 | 2 |
| 1989 | 5 |
| 1990 | 4 |
| 1991 | 5 |
| 1992 | 5 |
| 1993 | 2 |
| 1994 | 4 |
| 1995 | 5 |
| 1996 | 1 |
| 1997 | 6 |
| 1998 | 2 |
| 1999 | 3 |
| 2000 | 3 |
| 2001 | 7 |
| 2002 | 1 |
| 2003 | 5 |
| 2004 | 8 |
| 2005 | 4 |
| 2006 | 3 |
| 2007 | 1 |
| 2008 | 1 |
| 2009 | 2 |
| 2010 | 3 |
| 2011 | 1 |
| 2012 | 4 |
| 2013 | 5 |
| 2014 | 2 |
| 2015 | 3 |
| 2016 | 1 |
| 2017 | 2 |
| 2018 | 2 |
| 2019 | 5 |
| 2020 | 3 |
| 2021 | 1 |
| 2022 | 3 |
| 2023 | 1 |
| 2024 | 2 |
| 2026 | 1 |
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\") = 2001
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102809'))
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") = 2001
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102809'))
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 IAD02FA024Accident · 1 fatalField investigationFinal reportPiper PA-28R-180 · Milford, CTThe pilot's failure to follow the published IFR approach procedure, which resulted in a premature descent and subsequent impact with water. A factor was the night, overwater visual conditions.NTSB CHI01LA176Accident · No injuriesLimited investigationFinal reportPiper PA-28R-180 · Green Bay, WIThe pilot not performing the pre-landing checklist, and the wheels-up landing made by the pilot.NTSB DEN01LA107Accident · Minor injuriesLimited investigationFinal reportPiper PA-28R-180 · Albuquerque, NMthe pilot's diminished visual lookout, resulting in the wire strike. Contributing factors were the total mechanical failure of the cylinder, dusk, and the power transmission line.NTSB IAD01FA053Accident · 1 fatalField investigationFinal reportPiper PA-28R-180 · Afton, VAThe pilot's loss of consciousness due to a medical condition, which resulted in his failure to maintain control of the airplane and subsequent impact with rising terrain.NTSB CHI01LA118Accident · No injuriesLimited investigationFinal reportPiper PA-28R-180 · Saint Cloud, MNThe inadvertent wheels-up landing by the pilot. A factor was the pilots failure to follow the before landing checklist.NTSB NYC01LA092Accident · No injuriesLimited investigationFinal reportPiper PA-28R-180 · Lexington, VAThe pilot's inadequate compensation for the runway conditions. Factors included the soggy runway conditions, and the lack of available takeoff performance data in the owners manual.NTSB MIA01FA060Accident · 2 fatalField investigationFinal reportPiper PA-28R-180 · Bethel, NCthe pilot's failure to maintain control of the airplane due to spatial disorientation, which resulted in an in-flight collision with power lines and the subsequent impact with terrain. A factor in this accident was: the pilot's lack of recent instrument…