NTSB investigations: Piper PA-34-200T, TX
17 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
| 1975 | 1 |
|---|---|
| 1980 | 1 |
| 1981 | 3 |
| 1982 | 1 |
| 1983 | 1 |
| 1994 | 1 |
| 1996 | 1 |
| 1999 | 1 |
| 2004 | 1 |
| 2009 | 1 |
| 2010 | 1 |
| 2012 | 1 |
| 2017 | 1 |
| 2021 | 1 |
| 2024 | 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.\"eventStateOrRegion\" = 'TX' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'TX' AND c."eventCountry" = 'USA'
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 CEN24LA311Accident · No injuriesClass 3 · LimitedPreliminary reportPiper PA-34-200T · Wills Point, TXOn July 31, 2024, about 0836 central daylight time, a Piper PA-34-200T, N2106E, was substantially damaged when it was involved in an accident near Wills Point, Texas. The pilot and pilot-rated passenger were not injured. The airplane was operated as a Title…NTSB CEN21LA366Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-34-200T · Navasota, TXThe pilot’s failure to extend the landing gear before landing.NTSB GAA17CA233Accident · No injuriesData collectionFinal reportPiper PA 34 · Llano, TXThe pilot’s complacency during the en route phase of flight, which resulted in fuel mismanagement and a subsequent gear-up landing.NTSB CEN12LA229Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · San Marcos, TXThe pilot's failure to ensure that he was aware of the NOTAM describing the runway closure, which resulted in a landing on the closed runway and subsequent collision with a barrier. Contributing to the accident was the failure of air traffic control personnel…NTSB CEN11LA083Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Nocagdoches, TXA total loss of power in both engines for undetermined reasons.NTSB CEN10LA052Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Saginaw, TXThe pilot's inability to maintain control of the airplane due to a pinched trim system wire that resulted in a runaway nose-down pitch trim.NTSB FTW04LA142Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Cleveland, TXThe in-flight fire that resulted from an electrical arc in the main battery cable near the main power bus. The cause of the arcing event could not be determined.NTSB FTW99LA072Accident · Serious injuriesLimited investigationFinal reportPiper PA-34-200T · Wharton, TXThe pilot's failure to comply with the manufacturer's single engine landing checklist which resulted in the aircraft landing short of the runway.NTSB FTW96FA088Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Wichita Falls, TXThe inadvertent stall by the pilot in command. Factors were the impeded airplane takeoff performance, the rudder trim not corrected by the pilot, and the pilot's failure to comply with the checklist.NTSB FTW94LA068Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Dallas, TXThe pilot's failure to attain the proper touchdown point. A factor was the pilot's disorientation and dark night conditions.NTSB FTW84LA056Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Houston, TXSee FTW84LA056ANTSB FTW82DA311Accident · No injuriesFinal reportPiper PA-34-200T · Eagle Pass, TXThe pilot stated that he overflew the ranch strip and looked it over before landing. He stated that he touched down on the first 200 ft of the 2200 ft, asphalt runway, but each time the brakes were applied, the wheels would lock and skid due to loose gravel…NTSB FTW82FPD02Accident · No injuriesClosedPiper PA-34 · Henrietta, TXNTSB FTW81DRG46Accident · No injuriesClosedPiper PA-34 · Crystal City, TXNTSB FTW81FQG34Accident · No injuriesClosedPiper PA-34 · Amarillo, TXNTSB FTW80FQD04Accident · Serious injuriesClosedPiper PA-34 · El Paso, TXNTSB FTW76FPA10Accident · No injuriesClosedPiper PA-34 · Plano, TX