NTSB investigations: Piper PA-34-200T, 1984
8 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\") = 1984
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") = 1984
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 DEN85LA023Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Denver, COAccording to the pilot, the acft was taxiing to park when a small truck was seen approaching from the right about 50 ft away. After realizing that the vehicle driver did not see the acft the pilot reduced power to idle and applied the brakes. The truck driver…NTSB CHI85LA019Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Compton, ILThe plt stated that he landed aprx 1/4 way down the wet sod rwy which is 2590 ft long. The braking action was nil. The acft ran off the end of the rwy & collided with a 3 ft embankment.NTSB CHI84LA325Accident · No injuriesLimited investigationFinal reportCessna 182-C · Akron, OHA Cessna 182 on takeoff on rwy 19 collided with a Piper PA34 landing on rwy 25. Each plts view of the other was obstructed by airport parking at one point during the mishap. The airport tower was closed. The pilot of the Cessna left the UNICOM frequency for…NTSB MKC84LA230Accident · No injuriesLimited investigationFinal reportMooney M20C · Hannibal, MON7702M experienced an electrical failure en route & diverted to Hannibal. Plt stated he circled the arpt, saw no traffic& decided to land to the south. N38455 had just landed to the north and was on the rwy when the plt saw N7702M attempting to land in the…NTSB NYC84LA205Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Teterboro, NJA Piper PA-34-200T, N33086 & a Piper Aerostar 600, N8208T, were involved in an on-ground collision at night. IFR flt plans had been filed for both acft & the plts of both acft had begun taxiing for takeoff. According to the PA-34 plt, he had been cleared to…NTSB NYC84FA135Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Johnstown, PAThe acft took off with a center of gravity bet 95.45 & 95.71 inches aft of the datum & aprx 98 lbs below the max allowable gross weight. The max aft CG limit for all weights was 94.6 inches. Wx at the aprx time of the accident was 400 ft ceiling, light…NTSB ATL84IA137Incident · 2 fatalIncident investigationFinal reportPiper PA-34-200T · Parkersburg, WVAfter an unscheduled landing due to the condition of a patient aboard the acft, the acft turned off a taxiway into the grass and stopped. Rescue personnel found the plt incapacitated from a heart attack and collapsed over the controls and the nurse…NTSB ATL84FA126Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Fletcher, NCDuring takeoff the left eng lost power shortly after the landing gear was retracted. The plt stated that he felt the loss of power at about the same time that he turned off the landing lights. With the left eng manifold pressure gauge reading 25 inches hg,…