NTSB investigations: Piper PA-20, 2000
5 cases on aircraft the registry lists as Piper PA-20. 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
| 1964 | 25 |
|---|---|
| 1965 | 26 |
| 1966 | 23 |
| 1967 | 15 |
| 1968 | 16 |
| 1969 | 15 |
| 1970 | 14 |
| 1971 | 14 |
| 1972 | 11 |
| 1973 | 11 |
| 1974 | 9 |
| 1975 | 13 |
| 1976 | 6 |
| 1977 | 12 |
| 1978 | 7 |
| 1979 | 4 |
| 1980 | 3 |
| 1981 | 2 |
| 1982 | 6 |
| 1983 | 7 |
| 1984 | 3 |
| 1985 | 10 |
| 1986 | 1 |
| 1987 | 3 |
| 1988 | 3 |
| 1989 | 4 |
| 1990 | 1 |
| 1991 | 9 |
| 1992 | 5 |
| 1993 | 3 |
| 1994 | 2 |
| 1995 | 4 |
| 1996 | 3 |
| 1997 | 1 |
| 1998 | 5 |
| 2000 | 5 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 5 |
| 2004 | 5 |
| 2005 | 4 |
| 2006 | 2 |
| 2007 | 1 |
| 2008 | 3 |
| 2009 | 5 |
| 2010 | 4 |
| 2011 | 2 |
| 2012 | 2 |
| 2013 | 2 |
| 2014 | 1 |
| 2015 | 2 |
| 2016 | 1 |
| 2017 | 1 |
| 2018 | 2 |
| 2019 | 2 |
| 2020 | 2 |
| 2021 | 2 |
| 2022 | 2 |
| 2025 | 2 |
| 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 ('7102002'))
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 ('7102002'))
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 SEA01LA018Accident · No injuriesLimited investigationFinal reportPiper PA-20 · Great Falls, MTThe pilot's improper decision to land on unsuitable terrain. Factors include snow covered terrain.NTSB SEA01LA016Accident · No injuriesLimited investigationFinal reportPiper PA-20 · Hood River, ORThe pilot's failure to maintain directional control during landing.NTSB CHI00LA231Accident · No injuriesLimited investigationFinal reportPiper PA-20 · Kirksville, MOthe pilot failed to maintain directional control during landing.NTSB LAX00LA224Accident · No injuriesLimited investigationFinal reportPiper PA-20 · Quincy, CAThe fracture and failure of the main landing gear strut to shock absorber attachment fitting.NTSB SEA00LA098Accident · No injuriesLimited investigationFinal reportPiper PA-20 · Quinault, WAFuel starvation due to the pilot's failure to position the fuel selector valve to the proper/correct position while switching fuel tanks. Factors include unreliable fuel selector valve position detents, having no suitable terrain in which to execute a forced…