NTSB investigations: Piper PA-24-260, 1991
9 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
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\") = 1991
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") = 1991
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 NYC92LA051Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-260C · Stratford, CTWater/ice in the fuel system, which resulted in fuel starvation and a loss of engine power. Factors related to the accident were: freezing temperatures and inadequate pre-flight preparation by the pilot.NTSB CHI92LA026Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Charles City, IAProper glide path not maintained. Factors in the accident are the premature landing gear extension and inadequate airspeed by the pilot in command.NTSB NYC92LA012Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-260 · Montgomery, NYFailure of the pilot-in-command to correctly position the fuel selector when the right main fuel tank was exhausted, resulting in fuel starvation to the engine.NTSB ATL92LA002Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-260 · Sanford, NCThe loss of engine power due to unknown reasons.NTSB LAX91LA395Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Tehachapi, CAFuel exhaustion due to improper inflight planning.NTSB ATL91LA135Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-260 · Springfield, TNThe PA-24 pilot's failure to maintain proper airspeed while executing a go-around, resulting in the stalling of the airplane. A factor in the accident was the PA-24 pilot's failure to visually detect the J-3 in a timely manner.NTSB CHI91LA218Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Flint, MIPropeller pitch change mechanism sheared. Factors related to the accident were powerplant vibration and proper touchdown point not possible.NTSB MIA91FAMS1Accident · 1 fatalMissing aircraftFinal reportPiper PA-24-260 · Missing, FLUndetermined.NTSB ATL91FA047Accident · 3 fatalField investigationFinal reportPiper PA-24-260 · Cordele, GAFailure of the pilot to attain proper runway alignment and to maintain proper altitude. Related factors were: darkness and the pilot becoming lost/disoriented.