NTSB investigations: Piper PA-22-108, 1998
3 cases on aircraft the registry lists as Piper PA-22-108. 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 | 118 |
|---|---|
| 1965 | 114 |
| 1966 | 68 |
| 1967 | 57 |
| 1968 | 52 |
| 1969 | 32 |
| 1970 | 22 |
| 1971 | 23 |
| 1972 | 17 |
| 1973 | 17 |
| 1974 | 8 |
| 1975 | 17 |
| 1976 | 13 |
| 1977 | 12 |
| 1978 | 10 |
| 1979 | 5 |
| 1980 | 5 |
| 1981 | 6 |
| 1982 | 3 |
| 1983 | 6 |
| 1984 | 4 |
| 1985 | 3 |
| 1986 | 5 |
| 1987 | 4 |
| 1988 | 5 |
| 1989 | 3 |
| 1990 | 2 |
| 1991 | 3 |
| 1992 | 4 |
| 1993 | 4 |
| 1994 | 3 |
| 1995 | 3 |
| 1996 | 2 |
| 1997 | 6 |
| 1998 | 3 |
| 1999 | 7 |
| 2000 | 2 |
| 2001 | 4 |
| 2002 | 3 |
| 2003 | 1 |
| 2004 | 2 |
| 2005 | 3 |
| 2006 | 1 |
| 2007 | 1 |
| 2008 | 3 |
| 2011 | 4 |
| 2012 | 1 |
| 2013 | 2 |
| 2014 | 1 |
| 2015 | 1 |
| 2016 | 6 |
| 2017 | 2 |
| 2018 | 2 |
| 2020 | 2 |
| 2025 | 1 |
| 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\") = 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 ('7102204'))
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 ('7102204'))
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 CHI98LA350Accident · No injuriesLimited investigationFinal reportPiper PA-22-108 · Janesville, WIthe pilot's failure to land the airplane at a proper touchdown point on the runway. A factor was the excessive rate of descent which developed on final approach.NTSB CHI98LA235Accident · 1 fatalLimited investigationFinal reportPiper PA-22-108 · Spearfish, SDthe pilots improper preflight planning, which failed to detect the fuel selector positioned on the left fuel tank, which had insufficient fuel, resulting in fuel starvation, and the loss of engine power.NTSB FTW98LA124Accident · No injuriesLimited investigationFinal reportPiper PA-22-108 · Frederick, OKThe loss of wheel brakes due to the failure of the brake actuating cable. A factor was the tailwind.