NTSB investigations: Piper PA-23-250, 2006
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\") = 2006
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") = 2006
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 MIA07WA001Accident · Serious injuriesForeign investigationPiper PA-23-250 · Arklins Island, BahamasNTSB CHI07LA002Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Marshall, MNThe failure of the nose gear to properly extend for undetermined reasons, which resulted in damage to the forward fuselage during landing.NTSB DEN06GA128Accident · 2 fatalFinal reportPiper PA-23-250 · Fort Meade, FLA loss of power in the right engine while manuevering for reasons undetermined, and failure to maintain aircraft control which resulted in an inadvertent stall. Contributing factors were the airspeed below Vmc, and an altitude too low to afford a safe…NTSB DFW06LA207Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Newton, MSThe total loss of engine power due to fuel contamination. A factor was the pilot's inadequate preflight inspection.NTSB CHI06FA232Accident · 4 fatalField investigationFinal reportPiper PA-23-250 · Sault Ste Marie, MIThe pilot's failure to maintain aircraft control during the circling approach and his failure to perform a missed approach when the airplane was no longer in a position to land using normal flight maneuvers. Contributing to the accident was the pilot's…NTSB SEA06CA171Accident · No injuriesData collectionFinal reportPiper PA-23-250 · Greenacres, WAThe pilot's selection of an unsuitable landing runway which resulted in a runway overrun and collision with a fence. A contributing factor was the wet runway condition.NTSB ANC06LA078Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Borinquen, PRFuel starvation/exhaustion for an undetermined reason during cruise flight, which resulted in a complete loss of engine power to both engines and a ditching in the ocean.NTSB CHI06LA146Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Faribault, MNDirectional control not obtained/maintained by the pilot during landing. A contributing factor was the ditch.NTSB DFW06CA153Accident · No injuriesData collectionFinal reportPiper PA-23-250 · Mena, ARThe pilot's improper landing flare resulting in a hard landing and his improper recovery procedures for a bounced landing.NTSB MIA06LA106Accident · 2 fatalLimited investigationFinal reportPiper PA-23-250 · Caribbean SeaThe failure of the pilot to maintain control of the airplane. A contributing factor in the accident was the spatial disorientation of the pilot, resulting in the in-flight loss of control.NTSB NYC06CA080Accident · Serious injuriesData collectionFinal reportPiper PA23-250 · Morristown, NJThe pilot's premature shutdown of both engines, which resulted in a forced landing short of the runway. A factor was a landing gear malfunction indication for undetermined reasons.NTSB DEN06LA050Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-250 · Emporia, KSthe pilot's attempted flight into adverse weather conditions and improper in-flight planning which resulted in loss of control and subsequent impact with trees. Contributing factors were the pilot's delayed remedial action, the icing and dark night conditions.