NTSB investigations: Piper PA-34-200T, 1998
5 cases on aircraft the registry lists as Piper PA-34-200T. 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
| 1971 | 1 |
|---|---|
| 1975 | 4 |
| 1976 | 5 |
| 1977 | 8 |
| 1978 | 10 |
| 1979 | 9 |
| 1980 | 17 |
| 1981 | 12 |
| 1982 | 14 |
| 1983 | 11 |
| 1984 | 8 |
| 1985 | 10 |
| 1986 | 9 |
| 1987 | 7 |
| 1988 | 9 |
| 1989 | 6 |
| 1990 | 6 |
| 1991 | 9 |
| 1992 | 5 |
| 1993 | 5 |
| 1994 | 4 |
| 1995 | 7 |
| 1996 | 7 |
| 1997 | 9 |
| 1998 | 5 |
| 1999 | 4 |
| 2000 | 4 |
| 2001 | 5 |
| 2002 | 6 |
| 2003 | 4 |
| 2004 | 2 |
| 2005 | 1 |
| 2006 | 5 |
| 2007 | 7 |
| 2008 | 6 |
| 2009 | 5 |
| 2010 | 3 |
| 2012 | 2 |
| 2013 | 4 |
| 2014 | 2 |
| 2015 | 1 |
| 2016 | 2 |
| 2017 | 3 |
| 2018 | 3 |
| 2019 | 2 |
| 2021 | 2 |
| 2022 | 1 |
| 2023 | 3 |
| 2024 | 3 |
| 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\") = 1998
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103406'))
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") = 1998
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103406'))
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 CHI98LA367Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-220T · Schofield, WIThe inadvertent deactivation of the fuel selector and the emergency procedure not followed by the pilot-in-command. The tree was a contributing factor.NTSB NYC98LA174Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Middlesboro, KYThe pilot's misjudgment of distance and speed, which resulted in runway overrun into a grass area where the gear collapsed. The tailwind was a contributing factor.NTSB FTW98LA369Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Blanding, UTThe pilot's inadequate landing flare, causing components of the nose wheel landing gear to fracture.NTSB MIA98LA125Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Fort Lauderdale, FLThe failure of the O-rings in the landing gear hydraulic cylinder.NTSB LAX98LA082Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Chinle, AZthe airport personnel's failure to provide an adequate perimeter barrier to prevent animals from entering the runway area. A factor in the accident was the dark night lighting conditions which hindered the pilot's ability to detect animals on the runway…