NTSB investigations: Piper PA-22, 1989
5 cases on aircraft the registry lists as Piper PA-22. 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 | 35 |
|---|---|
| 1965 | 44 |
| 1966 | 36 |
| 1967 | 22 |
| 1968 | 30 |
| 1969 | 20 |
| 1970 | 15 |
| 1971 | 22 |
| 1972 | 13 |
| 1973 | 17 |
| 1974 | 11 |
| 1975 | 5 |
| 1976 | 9 |
| 1977 | 5 |
| 1978 | 8 |
| 1979 | 8 |
| 1980 | 4 |
| 1981 | 2 |
| 1982 | 4 |
| 1983 | 5 |
| 1984 | 3 |
| 1985 | 5 |
| 1986 | 2 |
| 1987 | 1 |
| 1988 | 5 |
| 1989 | 5 |
| 1990 | 4 |
| 1991 | 1 |
| 1992 | 2 |
| 1993 | 1 |
| 1994 | 3 |
| 1995 | 4 |
| 1996 | 2 |
| 1997 | 1 |
| 1998 | 7 |
| 1999 | 3 |
| 2001 | 1 |
| 2002 | 4 |
| 2003 | 2 |
| 2005 | 3 |
| 2006 | 1 |
| 2007 | 2 |
| 2008 | 3 |
| 2009 | 3 |
| 2011 | 1 |
| 2012 | 2 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 2 |
| 2017 | 1 |
| 2018 | 1 |
| 2019 | 1 |
| 2020 | 1 |
| 2021 | 1 |
| 2023 | 3 |
| 2024 | 1 |
| 2025 | 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\") = 1989
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102202'))
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") = 1989
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102202'))
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 FTW89FA171Accident · 1 fatalField investigationFinal reportPiper PA-22-150 · Elgin, TXThe pilot's inadvertent closure (deactivation) of the mixture control, which resulted in a loss of engine power, and his failure to maintain sufficient airspeed, which resulted in an inadvertent stall. Factors related to the accident were: the gusty wind, and…NTSB SEA89LA137Accident · Minor injuriesLimited investigationFinal reportPiper PA-22 · Meridian, IDThe pilot's failure to properly position the fuel selector, which resulted in fuel starvation, his failure to follow the emergency procedure, and his inadequate visual lookout (failure to see & avoid obstructions). The power line was a related factor.NTSB FTW89LA111Accident · Minor injuriesLimited investigationFinal reportPiper PA-22 · Austin, TXThe failure of the aircraft brake system. Factors include high tail wind.NTSB ANC89LA079Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Anchorage, AKA crack on the left side of the engine crankcase which resulted in a loss of lubricating oil and which forced the pilot to land on a gravel bar which resulted in a nose over during landing.NTSB LAX89LA171Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Truckee, CAThe improper installation of fuel lines by maintenance personnel who installed the engine.