NTSB investigations: Piper PA-32-260, 1992
9 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\") = 1992
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") = 1992
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 NYC93FA012Accident · 2 fatalField investigationFinal reportPiper PA-32-260 · Pulaski, VAThe improper decision by the non-instrument-rated pilot to continue VFR flight into known instrument meteorological conditions resulting in spatial disorientation and loss of control of the airplane. Factors which contributed to the accident were the actions…NTSB CHI92LA265Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Moran, MIThe pilot-in-command's improper selection of fuel tank resulting in fuel starvation. A factor was the pilot-in-command's encounter with unsuitable terrain.NTSB NYC92LA173Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Newburyport, MAThe loss of engine power for undetermined reasons.NTSB FTW92WA236Accident · No injuriesForeign investigationPiper PA-32-260 · Punta China, MexicoNTSB MIA92LA162Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Randleman, NCThe failure of the pilot-in-command to switch the fuel selector to a tank with fuel, after the engine failed due to fuel starvation.NTSB BFO92LA107Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Norwalk, OHLoss of engine power due to undetermined reasons and the lack of suitable terrain for a forced landing.NTSB ATL92FA102Accident · 6 fatalField investigationFinal reportPiper PA-32-260 · Greenville, NCFailure of the pilot to maintain a proper climb rate after takeoff after becoming spatially disoriented. Factors related to the accident were: the adverse weather conditions, the pilot's self-induced pressure to make the flight, and his lack of total…NTSB CHI92LA135Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Sidney, NEWas an inadvertent stall/mush during landing by the pilot. A factor related to the accident was lack of recent total experience.NTSB MIA92LA083Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Kissimmee, FLThe pilot-in-command's failure to attain the proper touchdown point due to landing before the displaced threshold on the rwy.