NTSB investigations: Piper PA-23-250, 2001
3 cases on aircraft the registry lists as Piper PA-23-250. 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 | 28 |
|---|---|
| 1965 | 40 |
| 1966 | 33 |
| 1967 | 41 |
| 1968 | 25 |
| 1969 | 34 |
| 1970 | 33 |
| 1971 | 27 |
| 1972 | 30 |
| 1973 | 32 |
| 1974 | 32 |
| 1975 | 20 |
| 1976 | 27 |
| 1977 | 24 |
| 1978 | 22 |
| 1979 | 29 |
| 1980 | 26 |
| 1981 | 13 |
| 1982 | 22 |
| 1983 | 17 |
| 1984 | 13 |
| 1985 | 20 |
| 1986 | 15 |
| 1987 | 15 |
| 1988 | 18 |
| 1989 | 8 |
| 1990 | 8 |
| 1991 | 15 |
| 1992 | 9 |
| 1993 | 12 |
| 1994 | 15 |
| 1995 | 17 |
| 1996 | 12 |
| 1997 | 8 |
| 1998 | 8 |
| 1999 | 6 |
| 2000 | 3 |
| 2001 | 3 |
| 2002 | 5 |
| 2003 | 7 |
| 2004 | 8 |
| 2005 | 12 |
| 2006 | 12 |
| 2007 | 3 |
| 2008 | 1 |
| 2009 | 1 |
| 2010 | 1 |
| 2011 | 2 |
| 2012 | 2 |
| 2013 | 6 |
| 2014 | 2 |
| 2015 | 1 |
| 2016 | 3 |
| 2017 | 4 |
| 2018 | 3 |
| 2019 | 6 |
| 2020 | 5 |
| 2021 | 1 |
| 2022 | 2 |
| 2023 | 5 |
| 2024 | 3 |
| 2025 | 2 |
| 2026 | 1 |
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\") = 2001
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102308'))
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") = 2001
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102308'))
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 FTW02LA052Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-250 · Duncan, OKThe pilot's descent below the minimum descent altitude, and his failure to maintain obstacle clearance. Contributing factors were the below approach/landing minimum weather, the dark night conditions, and the inoperative REIL's.NTSB CHI01LA076Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Fulton, MOthe pilot not maintaining altitude/clearance from the power line during the circling approach. Factors were the power transmission wire, the plowed field, and that the pilot's lookout was not possible through the built up ice on the windshield.NTSB CHI01TA063Accident · Serious injuriesFinal reportPiper PA-23 · Griffith, INThe unsuitable terrain for landing encountered by the pilot. Factors included the loss of power for undetermined reasons and the rough terrain.