NTSB investigations: Piper PA-23-250, 1996
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\") = 1996
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") = 1996
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 MIA97WA044Accident · No injuriesForeign investigationPiper PA-23-250 · Walker Cay, BahamasNTSB LAX97FA070Accident · 4 fatalField investigationFinal reportPiper PA-23-250 · Lucerne Valley, CAthe pilot's failure to maintain an adequate airspeed after encountering turbulence, low level wind shear, and an open door.NTSB IAD97LA029Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-250 · Elyria, OHThe pilot's fuel mismanagement which led to fuel starvation to one engine, and the pilot's failure to maintain control of the airplane.NTSB FTW97LA040Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Plainview, TXthe pilot's continued descent below the minimum descent altitude (MDA). Factors relating to the accident were: darkness, the adverse weather conditions.NTSB FTW96GA365Accident · 2 fatalFinal reportPiper PA-23-250 · Jennings, LAThe pilot's failure to maintain clearance. Factors were the pilot's lack of recent experience in the make and model of airplane, the dark night, and fog.NTSB MIA96LA187Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · St Petersburg, FLa loss of engine power due to fuel contamination, which resulted in a forced landing (ditching) in water. Factors relating to the accident were: an inadquate annual inspection by maintenance personnel, and an inadequate preflight inspection by the pilot.NTSB IAD96LA105Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Harrisburg, PAFailure of the right engine due to a fatigue fracture of the crankshaft resultant from heat cracks from an undetermined source.NTSB ATL96FA095Accident · 5 fatalField investigationFinal reportPiper PA-23-250 · Clanton, ALcorrosion pitting of the number six cylinder on the left engine, and subsequent fatigue fracture and separation of the cylinder, which led to an engine compartment fire, wing fire, and an in-flight separation of the left wing.NTSB IAD96FA050Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Marion, VAthe pilot's failure to maintain adequate altitude/clearance during the instrument approach (FAF/Outer Marker to Threshold IFR), which resulted in the in-flight collision with trees. A related factor was the foggy weather conditions.NTSB NYC96FA073Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Bridgeport, WVThe pilot's inablility to maintain aircraft control due to a full nose down trim condition, which resulted in a loss of control and collision with terrain.NTSB FTW96LA141Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Sulphur Springs, TXthe pilot's failure to maintain terrain clearance. A factor was his diverted attention to the performance of the manual gear extension procedure.NTSB MIA96WA069Accident · No injuriesForeign investigationPiper PA-23-250 · North Caicos, Turks & Caicos Islands