NTSB investigations: Piper PA-32-260, 2002
4 cases on aircraft the registry lists as Piper PA-32-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
| 1965 | 4 |
|---|---|
| 1966 | 28 |
| 1967 | 32 |
| 1968 | 38 |
| 1969 | 34 |
| 1970 | 29 |
| 1971 | 37 |
| 1972 | 24 |
| 1973 | 26 |
| 1974 | 32 |
| 1975 | 24 |
| 1976 | 26 |
| 1977 | 27 |
| 1978 | 14 |
| 1979 | 18 |
| 1980 | 14 |
| 1981 | 13 |
| 1982 | 7 |
| 1983 | 17 |
| 1984 | 10 |
| 1985 | 4 |
| 1986 | 7 |
| 1987 | 11 |
| 1988 | 11 |
| 1989 | 12 |
| 1990 | 9 |
| 1991 | 7 |
| 1992 | 9 |
| 1993 | 7 |
| 1994 | 11 |
| 1995 | 9 |
| 1996 | 8 |
| 1997 | 7 |
| 1998 | 5 |
| 1999 | 7 |
| 2000 | 5 |
| 2001 | 6 |
| 2002 | 4 |
| 2003 | 6 |
| 2004 | 6 |
| 2005 | 2 |
| 2006 | 5 |
| 2007 | 4 |
| 2008 | 9 |
| 2009 | 2 |
| 2010 | 1 |
| 2011 | 5 |
| 2012 | 2 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 3 |
| 2016 | 1 |
| 2017 | 4 |
| 2018 | 1 |
| 2019 | 10 |
| 2020 | 5 |
| 2021 | 9 |
| 2022 | 5 |
| 2023 | 6 |
| 2024 | 4 |
| 2025 | 3 |
| 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\") = 2002
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103206'))
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") = 2002
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103206'))
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 ANC02LA095Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Red Devil, AKA partial loss of engine power for an undetermined reason during the initial climb after takeoff that resulted in a collision with trees. A contributing factor in the accident was rising terrain which was unsuitable for a forced landing.NTSB DEN02LA090Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Victor, COthe pilot's failure to refuel, resulting in fuel exhaustion and a subsequent loss of engine power. Contributing factors were the pilot's use of inappropriate medication, and the unsuitable terrain on which to make a forced landing.NTSB FTW02LA181Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Pecos, TXThe pilot misjudged the landing flare resulting in a hard landing. A contributing factor was the dark night conditions.NTSB IAD02LA044Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Louisville, KYThe pilot's inadvertent selection of an empty fuel tank, which resulted in fuel starvation of the engine.