NTSB investigations: Piper PA-22-160, 1998
5 cases on aircraft the registry lists as Piper PA-22-160. 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 | 36 |
|---|---|
| 1965 | 43 |
| 1966 | 29 |
| 1967 | 34 |
| 1968 | 20 |
| 1969 | 15 |
| 1970 | 19 |
| 1971 | 18 |
| 1972 | 13 |
| 1973 | 8 |
| 1974 | 12 |
| 1975 | 15 |
| 1976 | 13 |
| 1977 | 8 |
| 1978 | 10 |
| 1979 | 11 |
| 1980 | 4 |
| 1981 | 7 |
| 1982 | 8 |
| 1983 | 4 |
| 1984 | 4 |
| 1986 | 6 |
| 1987 | 5 |
| 1988 | 4 |
| 1989 | 10 |
| 1990 | 5 |
| 1991 | 5 |
| 1992 | 8 |
| 1993 | 3 |
| 1994 | 2 |
| 1995 | 4 |
| 1996 | 1 |
| 1997 | 5 |
| 1998 | 5 |
| 1999 | 2 |
| 2000 | 5 |
| 2001 | 5 |
| 2002 | 4 |
| 2003 | 3 |
| 2004 | 6 |
| 2005 | 3 |
| 2007 | 1 |
| 2008 | 3 |
| 2009 | 5 |
| 2010 | 5 |
| 2011 | 4 |
| 2012 | 5 |
| 2013 | 1 |
| 2014 | 1 |
| 2015 | 2 |
| 2016 | 2 |
| 2017 | 3 |
| 2018 | 1 |
| 2019 | 1 |
| 2021 | 2 |
| 2022 | 3 |
| 2023 | 2 |
| 2024 | 2 |
| 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\") = 1998
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102214'))
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") = 1998
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102214'))
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 ANC98LA133Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Arctic Village, AKThe pilot's delayed action to abort the landing. Factors associated with the accident were a tail wind, and rising terrain.NTSB SEA98LA137Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Pacific City, ORThe pilot's improper compensation for wind conditions (landing with a tail wind.) Related factors were tail wind conditions, a short runway, and diminished brake system effectiveness.NTSB FTW98LA308Accident · No injuriesLimited investigationFinal reportPiper PA-20-160 · Kemmerer, WYThe pilot's failure to maintain directional control of the airplane, resulting in a ground loop. A factor was the pilot's lack of experience in a conventional landing gear type of airplane.NTSB LAX98LA157Accident · Minor injuriesLimited investigationFinal reportPiper PA-22-160 · Clarksburg, CAA total loss of engine power for undetermined non-mechanical reasons. A contributing factor in the landing nose-over was the presence of the soft terrain.NTSB CHI98LA093Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Point Lookout, MOthe pilot's failure to maintain directional control on landing rollout.