NTSB investigations: Piper PA-24-260, 2009
4 cases on aircraft the registry lists as Piper PA-24-260. 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 | 1 |
|---|---|
| 1965 | 17 |
| 1966 | 27 |
| 1967 | 35 |
| 1968 | 29 |
| 1969 | 29 |
| 1970 | 28 |
| 1971 | 32 |
| 1972 | 17 |
| 1973 | 22 |
| 1974 | 28 |
| 1975 | 14 |
| 1976 | 19 |
| 1977 | 18 |
| 1978 | 8 |
| 1979 | 6 |
| 1980 | 12 |
| 1981 | 10 |
| 1982 | 5 |
| 1983 | 5 |
| 1984 | 8 |
| 1985 | 5 |
| 1986 | 4 |
| 1987 | 5 |
| 1988 | 8 |
| 1989 | 3 |
| 1990 | 4 |
| 1991 | 9 |
| 1992 | 5 |
| 1993 | 3 |
| 1994 | 6 |
| 1995 | 3 |
| 1996 | 3 |
| 1997 | 6 |
| 1999 | 3 |
| 2000 | 3 |
| 2001 | 1 |
| 2002 | 5 |
| 2003 | 4 |
| 2004 | 2 |
| 2005 | 2 |
| 2006 | 6 |
| 2007 | 1 |
| 2008 | 3 |
| 2009 | 4 |
| 2010 | 4 |
| 2011 | 1 |
| 2012 | 3 |
| 2013 | 2 |
| 2014 | 1 |
| 2015 | 2 |
| 2016 | 4 |
| 2017 | 1 |
| 2018 | 2 |
| 2019 | 1 |
| 2021 | 2 |
| 2022 | 4 |
| 2023 | 3 |
| 2024 | 1 |
| 2025 | 2 |
| 2026 | 4 |
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\") = 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 ('7102406'))
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 ('7102406'))
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 ERA10CA002Accident · No injuriesData collectionFinal reportPiper PA-24-260 · Highgate, VTThe pilot’s improper fuel management which resulted in loss of engine power due to fuel starvation.NTSB WPR09LA412Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Santa Barbara, CAA loss of power during approach due to fuel exhaustion for undetermined reasonsNTSB WPR09CA120Accident · No injuriesData collectionFinal reportPiper PA-24-260 · Lincoln, CAThe pilot's failure to extend the landing gear for landing. Contributing to the accident was the pilot's diverted attention due to an open door and the airport's pilot activated runway lights turning off.NTSB WPR09FA116Accident · 1 fatalField investigationFinal reportPiper PA-24-260 · Hagerman, IDThe student pilot's spatial disorientation, which resulted in a loss of aircraft control and subsequent in-flight breakup. Contributing to the accident was the pilot's mental condition which could have contributed to the inappropriate decision to fly the…