NTSB investigations: Piper PA-32-260, 1989
12 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\") = 1989
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") = 1989
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 FTW90LA048Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Clinton, OKPilots failure to correctly maintain the proper glidepath, which caused him to impact short of the runway.NTSB NYC90FA036Accident · 1 fatalField investigationFinal reportPiper PA-32-260 · Coventry, CTThe non-instrument rated pilot initiating VFR flight into IMC on a dark night which resulted in spatial disorientation and uncontrolled flight into the ground. Contributing factor(s) was: the adverse weather existing at the time of the accident and the…NTSB ANC90LA014Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Eek, AKThe pilot's inadequate preflight planning/preparation and his failure to assure the removal of ice or frost from the wings. The excess gross weight and uneven terrain were considered to be contributing factors.NTSB CHI90LA025Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Mcleansboro, ILThe pilot-in-command's failure to maintain control of the aircraft while recovering from a bounced landing.NTSB SEA89LA178Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Portland, ORThe pilot's poor inflight planning. Contributing to the accident was the wake turbulence and remedial action not possible.NTSB DEN89FA209Accident · 2 fatalField investigationFinal reportPiper PA-32-260 · Lk Havasu City, CAPilot's attention diverted outside the airplane. This diversion resulted in the pilot failing to monitor his altitude while in a descending turn and inadvertently flying the airplane into the water.NTSB MKC89LA185Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Leon, IABlockage of the engine air induction system by a field mouse nest. The nest was positioned so that it could not be seen during the pre-flight inspection. It became dislodged during the takeoff roll on the rough runway.NTSB BFO89FA064Accident · Serious injuriesField investigationFinal reportPiper PA-32-260 · Bradshaw, MDAn engine power loss due to fuel starvation for unknown reasons.NTSB BFO89FA028Accident · 3 fatalField investigationFinal reportPiper PA-32-260B · Richmond, VAEngine lost power because of induction icing. Contributing factors are conditions conduvice to induction icing and unsuitable terrain.NTSB ATL89LA110Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Kershaw, SCFatigue failure of the crankshaft dowel pin. Factors related to the accident were: failure of maintenance personnel to follow the applicable service bulletin and darkness.NTSB SEA89LA056Accident · No injuriesLimited investigationFinal reportPiper PA-32 · Seabeck, WAA fatigue failure of the engine crankshaft. Contributing to the accident was the lack of suitable landing area.NTSB FTW89LA051Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Conroe, TXFailure of the engine crankshaft due to fatigue. The low ceiling, dark night, and trees in the emergency landing area were factors.