NTSB investigations: Piper PA-18, 2005
4 cases on aircraft the registry lists as Piper PA-18. 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 | 47 |
|---|---|
| 1965 | 31 |
| 1966 | 21 |
| 1967 | 20 |
| 1968 | 18 |
| 1969 | 14 |
| 1970 | 23 |
| 1971 | 15 |
| 1972 | 15 |
| 1973 | 11 |
| 1974 | 19 |
| 1975 | 13 |
| 1976 | 11 |
| 1977 | 10 |
| 1978 | 8 |
| 1979 | 7 |
| 1980 | 10 |
| 1981 | 7 |
| 1982 | 9 |
| 1983 | 4 |
| 1984 | 5 |
| 1985 | 9 |
| 1986 | 7 |
| 1987 | 4 |
| 1988 | 3 |
| 1989 | 6 |
| 1990 | 9 |
| 1991 | 7 |
| 1992 | 3 |
| 1993 | 4 |
| 1994 | 6 |
| 1995 | 5 |
| 1996 | 5 |
| 1997 | 2 |
| 1998 | 4 |
| 1999 | 6 |
| 2000 | 6 |
| 2001 | 1 |
| 2002 | 7 |
| 2003 | 4 |
| 2004 | 2 |
| 2005 | 4 |
| 2006 | 2 |
| 2007 | 4 |
| 2008 | 4 |
| 2009 | 3 |
| 2010 | 2 |
| 2011 | 4 |
| 2012 | 4 |
| 2013 | 1 |
| 2014 | 2 |
| 2015 | 2 |
| 2016 | 2 |
| 2017 | 1 |
| 2018 | 1 |
| 2019 | 3 |
| 2020 | 4 |
| 2021 | 3 |
| 2022 | 4 |
| 2023 | 4 |
| 2025 | 2 |
| 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\") = 2005
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7101802'))
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") = 2005
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7101802'))
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 ANC06CA013Accident · No injuriesData collectionFinal reportPiper PA-18 · Skwentna, AKThe pilot's selection of an unsuitable landing area, which resulted in an on ground collision with trees during the landing roll. Factors associated with the accident were the icy and snow-covered terrain.NTSB DEN05CA129Accident · No injuriesData collectionFinal reportPiper PA-18A-135 · Cedaredge, COthe pilot's failure to maintain aircraft control, and the pilot's improper in-flight planning. Contributing to the accident was the wind shift, resultant tailwind, and the inadvertent stall.NTSB ANC05CA115Accident · No injuriesData collectionFinal reportPiper PA-18 · Port Heiden, AKThe pilot's misjudged distance/altitude during final approach, which resulted in an undershoot and an in-flight collision with terrain.NTSB ANC05CA080Accident · No injuriesData collectionFinal reportPiper PA-18 · Delta Junction, AKThe pilot's selection of unsuitable terrain for landing, which resulted in an overrun. A factor contributing to the accident was rough and uneven terrain.