NTSB investigations: Piper PA-18A 150, 2003
4 cases on aircraft the registry lists as Piper PA-18A 150. 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 | 30 |
|---|---|
| 1965 | 31 |
| 1966 | 24 |
| 1967 | 17 |
| 1968 | 19 |
| 1969 | 20 |
| 1970 | 19 |
| 1971 | 12 |
| 1972 | 16 |
| 1973 | 19 |
| 1974 | 11 |
| 1975 | 10 |
| 1976 | 12 |
| 1977 | 6 |
| 1978 | 8 |
| 1979 | 7 |
| 1980 | 6 |
| 1981 | 6 |
| 1982 | 4 |
| 1983 | 5 |
| 1984 | 7 |
| 1985 | 5 |
| 1986 | 5 |
| 1987 | 3 |
| 1988 | 2 |
| 1989 | 8 |
| 1990 | 4 |
| 1991 | 5 |
| 1992 | 6 |
| 1993 | 7 |
| 1994 | 3 |
| 1995 | 6 |
| 1996 | 4 |
| 1997 | 4 |
| 1998 | 2 |
| 1999 | 4 |
| 2000 | 5 |
| 2001 | 5 |
| 2002 | 5 |
| 2003 | 4 |
| 2004 | 3 |
| 2005 | 4 |
| 2006 | 4 |
| 2008 | 1 |
| 2011 | 4 |
| 2012 | 6 |
| 2013 | 1 |
| 2014 | 4 |
| 2015 | 4 |
| 2016 | 3 |
| 2017 | 1 |
| 2018 | 2 |
| 2019 | 2 |
| 2020 | 4 |
| 2021 | 1 |
| 2023 | 2 |
| 2024 | 3 |
| 2025 | 1 |
| 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\") = 2003
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7101837'))
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") = 2003
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7101837'))
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 ANC04LA002Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Ketchikan, AKThe pilot's failure to maintain adequate airspeed after an aborted landing, which resulted in an inadvertent stall and a ground loop. A factor contributing to the accident was the loss of directional control on the ground.NTSB SEA03LA099Accident · No injuriesLimited investigationFinal reportPiper PA-18A-150 · Laurel, MTAircraft control was not maintained during the landing roll. The aircraft subsequently nosed over.NTSB FTW03LA143Accident · Minor injuriesLimited investigationFinal reportPiper PA-18A-150 · Roanoke, TXThe flight instructor's inadequate in-flight planning/decision resulting in fuel starvation and the loss of engine power. A contributing factor was the lack of suitable terrain for the forced landing.NTSB DEN03LA061Accident · Serious injuriesLimited investigationFinal reportPiper PA-18A-150 · Newcastle, WYthe pilot's failure to maintain clearance from the terrain. Contributing factors include inadequate in-flight planning and decision making by the pilot, and the ground.