NTSB investigations: Piper PA-23-250, 2004
8 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
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 ('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") = 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 ('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 CHI05FA049Accident · 5 fatalField investigationFinal reportPiper PA-23-250 · Ironwood, MIFatigue fracture of an engine cylinder resulting in a loss of power on the left engine. Additional causes were the pilot's failure to maintain minimum control airspeed (Vmc), the resulting loss of aircraft control, and an inadvertent stall/spin. Contributing…NTSB CHI05FA024Accident · Serious injuriesField investigationFinal reportPiper PA-23-250 · Detroit, MIThe pilot's failure to feather the propeller and to maintain control of the airplane following the loss of engine power which resulted from undetermined reasons. Factors associated with the accident were the power lines and the house that the airplane…NTSB MIA05WA025Accident · Minor injuriesForeign investigationPiper PA-23-250 · Nassau, BahamasNTSB MIA05LA013Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · San Juan, PRThe pilot-in-command's failure to maintain airspeed while on base to final leg, which resulted in an inadvertent stall/mush and subsequent impact with the runway.NTSB ATL04LA177Accident · 2 fatalLimited investigationFinal reportPiper PA-23-250 · Lake Wales, FLThe pilot's inadequate preflight planning and preparation, and his inadequate visual lookout, which resulted in a collision with a television tower.NTSB MIA04FA100Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Baker, FLThe flight crew's inadvertent flight into thunderstorms resulting in the design limits of the airplane being exceeded, loss of aircraft control and subsequent in-flight breakup. A factor in the accident was the lack of required advisory by ATC about a radar…NTSB FTW04LA113Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Sweetwater, TXThe propeller overspeed for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.NTSB NYC04CA066Accident · No injuriesData collectionFinal reportPiper PA-23-250 · Grt. Barrington, MAThe pilot's misjudgment of the airplane's distance/speed and failure to obtain the proper touchdown point, which resulted in an overrun. A factor was the cross wind.