NTSB investigations: Piper PA-34-200T, 2001
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\") = 2001
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") = 2001
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 CHI02LA011Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Ann Arbor, MIThe pilots failure to maintain directional control during the landing. Factors were the gusty crosswind and the terrain drop-off.NTSB NYC02LA007Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Philadelphia, PAThe collapse of the right main landing gear for undetermined reasons.NTSB CHI01LA322Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Petoskey, MIThe pilot's inadequate preflight planning, the pilot's improper in-flight decisions, and the unsuitable terrain for landing. A factor relating to this accident was fuel exhaustion.NTSB MIA01LA182Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Boca Raton, FLA loss of engine power, and the pilot unable to feather the propeller for undetermined reasons, which resulted in a forced landing on a highway, subsequent impact with a pole and vehicles.NTSB IAD01LA028Accident · No injuriesLimited investigationFinal reportPiper 34-200T · Bluefield, WVThe pilot's failure to enter the correct altimeter setting, which resulted in continued flight below the decision height and a subsequent collision with trees.