NTSB investigations: Piper PA-23-250, 2005
12 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\") = 2005
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") = 2005
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 MIA06WA035Accident · 4 fatalForeign investigationPiper PA-23-250 · South Caicos, Turks & Caicos IslandsNTSB NYC06CA043Accident · No injuriesData collectionFinal reportPiper PA-23-250 · State College, PAThe pilot's failure to maintain directional control during the takeoff run. A factor was the snow-covered runway.NTSB DFW06CA033Accident · No injuriesData collectionFinal reportPiper PA-23-250 · Bixby, OKThe loss of engine power due to water contamination and corrosion in both gascolators due to improper maintenance. A factor was the lack of suitable terrain for the forced landing.NTSB NYC06FA034Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Burlington, VTThe pilot's failure to follow the published instrument flight procedure, which resulted in an in-flight collision with terrain. Factors in the accident were the local air traffic controller's inadequate monitoring of the MSAW system, and his delayed…NTSB IAD05LA123Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Smoketown, PAA loss of engine power during the climb for undetermined reasons, resulting in a forced landing.NTSB DFW05LA167Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Carizzo Springs, TXThe failure of the stabilator trim control rod due to internal corrosion. A contributing factor was the lack of suitable terrain for the forced landing.NTSB ATL05FAMS1Accident · 3 fatalMissing aircraftFinal reportPiper PA-23 · Ft Pierce, FLThe pilot's continued flight into known thunderstorm activity that resulted in the loss of control and the subsequent collision with water. A factor was the controller's failure to provide the pilot with convective intensity.NTSB LAX05LA168Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Seligman, AZthe pilot's fuel system mismanagement that led to a fuel starvation induced loss of power in the left engine. Also causal was the pilot's improper use of the emergency landing gear extension system.NTSB MIA05CA082Accident · No injuriesData collectionFinal reportPiper PA-23-250 · West Palm Beach, FLThe failure of the pilot to maintain proper alignment with the runway, his failure to perform a go around after recognizing the aircraft was not properly aligned for landing, and his intentionally landing on a taxiway which resulted in a landing overrun and…NTSB NYC05FA053Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Coatesville, PAThe pilot's inadequate remedial action during an engine failure, which resulted in a loss of airplane control. A factor was the pilot's improper fuel management, which resulted in fuel starvation to one engine, and its subsequent loss of engine power.NTSB DFW05LA081Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Westport, OKThe collapsing of the right main landing gear as a result of the failure of the scissors assembly.NTSB CHI05FA053Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Eureka Springs, ARThe pilot misjudged his distance/speed which resulted in the overrun and subsequent impact with trees. The wet turf runway and the trees were factors in the accident.