NTSB investigations: Piper PA-22-160, 2009
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
Latest 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\") = 2009
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") = 2009
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 WPR10LA083Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · San Jose, CAA total loss of engine power due to water contamination in the fuel system as a result of the pilot's inadequate preflight inspection.NTSB ANC09CA095Accident · No injuriesData collectionFinal reportPiper PA-22-160 · Talkeetna, AKThe pilot's selection of an unsuitable landing/takeoff area, resulting in a nose over during takeoff.NTSB CEN09CA464Accident · No injuriesData collectionFinal reportPiper PA-22-160 · Fort Collins, COThe pilot's failure to maintain directional control while landing in gusty, crosswind conditions.NTSB CEN09CA237Accident · No injuriesData collectionFinal reportPiper PA-22-160 · North Little Rock, ARThe pilot's inadequate compensation for the wind conditions during takeoff.NTSB WPR09CA136Accident · No injuriesData collectionFinal reportPiper PA-22-160 · Ogden, UTThe loss of directional control during the landing roll due to the separation of the tailwheel spring retaining clip for unknown reasons.