NTSB investigations: Piper PA-22-135, 1992
5 cases on aircraft the registry lists as Piper PA-22-135. 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 | 43 |
|---|---|
| 1965 | 34 |
| 1966 | 36 |
| 1967 | 45 |
| 1968 | 26 |
| 1969 | 18 |
| 1970 | 15 |
| 1971 | 19 |
| 1972 | 13 |
| 1973 | 10 |
| 1974 | 12 |
| 1975 | 13 |
| 1976 | 12 |
| 1977 | 12 |
| 1978 | 15 |
| 1979 | 7 |
| 1980 | 7 |
| 1981 | 6 |
| 1982 | 2 |
| 1983 | 7 |
| 1984 | 6 |
| 1985 | 1 |
| 1986 | 1 |
| 1987 | 3 |
| 1988 | 7 |
| 1989 | 5 |
| 1990 | 3 |
| 1991 | 6 |
| 1992 | 5 |
| 1993 | 1 |
| 1994 | 2 |
| 1995 | 2 |
| 1996 | 5 |
| 1997 | 1 |
| 1998 | 3 |
| 1999 | 4 |
| 2000 | 3 |
| 2001 | 1 |
| 2002 | 3 |
| 2003 | 1 |
| 2004 | 2 |
| 2005 | 3 |
| 2006 | 1 |
| 2007 | 2 |
| 2008 | 6 |
| 2009 | 1 |
| 2010 | 2 |
| 2011 | 1 |
| 2012 | 3 |
| 2013 | 2 |
| 2015 | 3 |
| 2017 | 2 |
| 2018 | 2 |
| 2019 | 1 |
| 2020 | 6 |
| 2021 | 5 |
| 2022 | 2 |
| 2025 | 2 |
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\") = 1992
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102206'))
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") = 1992
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102206'))
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 CHI92LA296Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Plattsmouth, NEThe pilot-in-command's failure to adequately compensate for wind conditions, and his not maintaining directional control.NTSB ATL92LA182Accident · Minor injuriesLimited investigationFinal reportPiper PA-22 · Jasper, TNThe fractured valve which resulted in a total loss of engine power, while flying over terrain that was not suitable for a forced landing. A factor was the densely wooded, mountainous terrain.NTSB ATL92LA176Accident · No injuriesLimited investigationFinal reportPiper PA-22T · Headland, ALThe pilot's improper evaluation of wind conditions and selection of the wrong runway, which resulted in a loss of control during the landing roll. A factor to the accident was a gusting tail wind.NTSB SEA92LA186Accident · No injuriesLimited investigationFinal reportPiper PA-22-135 · Morgan, UTPoor inflight planning/decision by the pilot in command. Factors contributing to the accident were: the gravel/dirt bank, night environmental conditions, and runway lighting unavailable.NTSB ANC92LA070Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Twin Hills, AKDirectional control was not maintained. A factor to the accident was: a bird.