Fatal NTSB investigations: Piper PA-34-220T
21 cases on aircraft the registry lists as Piper PA-34-220T. 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
| 1981 | 1 |
|---|---|
| 1982 | 2 |
| 1984 | 1 |
| 1985 | 2 |
| 1986 | 1 |
| 1988 | 1 |
| 1993 | 1 |
| 1996 | 2 |
| 2001 | 2 |
| 2002 | 1 |
| 2003 | 1 |
| 2005 | 2 |
| 2006 | 1 |
| 2010 | 1 |
| 2023 | 1 |
| 2025 | 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 c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103420', '7103223'))
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 c."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103420', '7103223'))
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 GAA25WA082Accident · 1 fatalClass 5 · ForeignPiper PA-34-220T · Braunschweig, GermanyNTSB WPR23FA083Accident · 1 fatalClass 3 · FieldFinal reportPiper PA-34-220T · New Harmony, UTThe pilot’s decision to continue visual flight rules flight into instrument meteorological conditions, which resulted in a loss of airplane control due to spatial disorientation.NTSB WPR10FA273Accident · 2 fatalField investigationFinal reportPiper PA-34-220T · Lincoln, MTThe pilot’s decision to continue flight into an area of low ceilings and low visibility and his failure to maintain sufficient clearance from mountainous terrain.NTSB NYC06FA155Accident · 3 fatalField investigationFinal reportPiper PA-34-220T · Tafton, PAThe pilot's inadvertent encounter with a thunderstorm, which resulted in a loss of aircraft control, and a subsequent in-flight breakup.NTSB DFW06FA021Accident · 2 fatalField investigationFinal reportPiper PA-34-220T · Tomball, TXThe pilot's failure to maintain control of the aircraft while attempting to execute a missed approach procedure in weather that was below landing minimums. Contributing factors were the low ceiling, and the below approach landing minimums.NTSB DFW05FA178Accident · 1 fatalField investigationFinal reportPiper PA-34-220T · Norman, OKThe pilot's failure to maintain airspeed, which resulted in an inadvertent stall/spin. A contributing factor was the pilot's attempted aborted landing following a hard landing and propeller strike.NTSB SEA03FA042Accident · 4 fatalField investigationFinal reportPiper PA-34-220T · Rexburg, IDThe pilot's failure to maintain aircraft control while on final approach. High and gusting winds were a factor.NTSB FTW03FA051Accident · 5 fatalField investigationFinal reportPiper PA-34-220T · McAlester, OKThe pilot's failure to maintain the airplane's minimum controllable airspeed during a single-engine go-around which resulted in his loss of control. Contributing factors to the accident included the loss of power from the left engine as a result of…NTSB FTW01FA101Accident · 2 fatalField investigationFinal reportPiper PA-34-220T · Brackettville, TXthe pilot's intentional low flight and his poor judgment to intentionally fly into known adverse weather, which resulted in an in-flight collision with terrain. Contributing factors were the dark night conditions and the thunderstorm.NTSB MIA01WA063Accident · 4 fatalForeign investigationPiper PA-34-200T · Augeburg, GermanyNTSB IAD97FA022Accident · 2 fatalField investigationFinal reportPiper PA-34-220T · West Milton, OHThe pilot's inability to maintain aircraft control after an undetermined failure of the automatic flight control. A contributing factor was failure of the maintenance technician to have the airplane test flown prior to release.NTSB FTW96FA145Accident · 1 fatalField investigationFinal reportPiper PA-34-220T · Estes Park, CODescent into mountainous terrain for reasons undetermined.NTSB SEA93FA153Accident · 1 fatalField investigationFinal reportPiper PA-34-220T · Battleground, WAThe pilot in command's failure to maintain adequate altitude during his maneuver.NTSB FTW88FA161Accident · 5 fatalField investigationFinal reportPiper PA-34-220T · Carthage, TXDrg a night arrival, the plt rprtd he could make a visual apch. At 2341:37 CDT, the ARTCC controller informed him the destn arpt was straight ahead at 12 mi & requested that he rprt when the arpt was in sight. At 2343:30, he rprtd the rwyin sight & the…NTSB MIA87FA062Accident · 2 fatalField investigationFinal reportPiper PA-34 · Ft. Lauderdale, FLThe pvt plt had been cleared for 27R ILS apch and was on the localizer at 1,600 ft when the controller noticed the acft north of the localizer course and in a right turn headed east. The controller querried the plt as to his heading and the plt replied,…NTSB FTW85FA131Accident · 4 fatalField investigationFinal reportPiper PA-34-220T · Stigler, OKThe plt filed a VFR flt plan after the wx improved from IFR to VFR with a chance of thunderstorms en route. Ocnl mod turbulence below 5000 ft was forcast due to strong/gusty low lvl wnds. While the acft was en route, a gnd witness heard the engs rev up more…NTSB FTW85FA104Accident · 1 fatalField investigationFinal reportPiper PA-34-220T · Victoria, TXThe plt had rented the acft on January 28, 1985, with route of flt unknown. No reported contact was made with the acft. The acft impacted the surface during hours of darkness in instrument meteorological conditions and was demolished. The plt was fatally…NTSB NYC84FA247Accident · 2 fatalField investigationFinal reportPiper PA-34-220T · Newcomb, NYThe flight was operating in accordance with f.a.r. part 135.the plt filed a VFR flt plan and was cruising at an altitude of 5,500 ft when clouds were encountered. The plt attempted to descend to 3,500 but collided with the santanonimountain at an elevation of…NTSB FTW83FA298Accident · 4 fatalField investigationFinal reportPiper PA-34-200T · Canjilon, NMPrior to departing helena, mt at 1209, the plt received a wx briefing from the great falls fss. The dfw 021240Z area forecast, valid until 0700Z on 11/3/82, was not available. The fss briefer made this deficiency known to the plt & recommended that he receive…NTSB LAX82FA074Accident · 1 fatalField investigationFinal reportPiper PA-34 · Near Sonoma, CAThe pilot proceeded VFR toward a private strip after an instrument approach to napa county airport. The visibility was not good and the aircraft collided with a hillside while en route. About 5 mi north, the weather at the napa county airport was 500 ft…NTSB LAX82FA018Accident · 2 fatalClosedPiper PA-34 · Oceanside, CA