NTSB investigations: Piper PA-32-260, 2004
6 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
Latest 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\") = 2004
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") = 2004
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 ATL05LA022Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Chamblee, GAThe pilot's mismanagement of the fuel supply, which resulted in fuel starvation and the subsequent loss of engine power. .NTSB ATL04LA175Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Kennesaw, GAThe loss of engine power for undetermined reasons.NTSB DEN04FA115Accident · 2 fatalField investigationFinal reportPiper PA-32-260 · Mineral Wells, TXthe pilot's failure to maintain airspeed which resulted in a stall. A contributing factor was the low altitude.NTSB MIA04FA086Accident · 1 fatalField investigationFinal reportPiper PA-32-260 · Venice, FLFailure of the pilot to recover from an improper landing flare resulting in his failure to maintain airspeed (Vs), an inadvertant stall, loss of control, and inflight collision with terrain during an uncontrolled descent.NTSB ATL04LA117Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · New Bern, NCThe pilot's inadequate pre-flight planning which resulted in a loss of engine power due to fuel exhaustion.NTSB NYC04LA071Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Collegeville, PAThe pilot's failure to maintain clearance from trees during approach to the runway. Factors in the accident were the dark night and snowbank.