OpenAirDocs.org

NTSB investigations: Piper PA-34-200T

14 cases on aircraft the registry lists as Piper PA-34-200T, where the first occurrence was “Overrun”. 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

19832026

Where

Open the map

Latest 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103406')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 340))
  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.

NTSB LAX07CA243Accident · No injuriesData collectionFinal reportPiper PA-34-200T · Big Creek, IDThe pilot's misjudgment of distance and speed, which led to a long landing, and his delayed application of brakes that resulted in long landing and a runway overrun.Aug 4, 2007 · N9356K · Substantial damageNTSB NYC06CA206Accident · No injuriesData collectionFinal reportPiper PA-34-200T · Lincoln Park, NJThe pilot's misjudged distance/speed which resulted in an overrun. A factor in the accident was the soft terrain.Aug 20, 2006 · N19TP · Substantial damageNTSB SEA06LA075Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Bullfrog Basin, UTA high airspeed at touchdown resulting in a high ground speed during the landing roll. Downhill sloping runway, a tailwind, the pilot's delayed remedial action and rough terrain off the end of the runway were factors.Apr 13, 2006 · N2227W · Substantial damageNTSB CHI02LA257Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Kenmare, NDThe pilot's misjudgment of distance and speed. Factors associated with the accident were the sudden wind shift which resulted in a tailwind condition and the rough terrain encountered during the overrun landing.Aug 26, 2002 · N9696C · Substantial damageNTSB 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.Aug 24, 1998 · N525WA · Substantial damageNTSB CHI93LA370Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · New Lenox, ILSelection of the wrong runway by the pilot after misreading the wind sock. The resultant tailwind was a related factor.Sep 19, 1993 · N8753E · Substantial damageNTSB BFO93LA072Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Simsbury, CTLack of braking action from the right brake. The pilot's failure to attain the proper touchdown point was a related factor.May 8, 1993 · N47448 · Substantial damageNTSB LAX93LA146Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Avalon, CAThe pilot's poorly planned approach, excessive airspeed, and failure to attain the proper touchdown point. The pilot's lack of familiarity with the airport is a factor in this accident.Mar 11, 1993 · N1808H · Substantial damageNTSB DEN89LA169Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Salt Lake City, UTThe pilot's improper use of the parking brake and his delay in aborting the takeoff. Factors related to the accident were: the fence & vehicle.Jul 14, 1989 · N6144H · Substantial damageNTSB NYC87LA112Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Rutland, VTDrg arrival, the plt was cleared for an lda/ndb apch to rwy 19. When she 'went visual' on the apch, a check of the VASI showed she was hi, so she slipped the acft to lose alt. The winds were rprtd as light & variable, but plt rprtd that drgthe lndg, there was…Mar 21, 1987 · N2083K · DestroyedNTSB ATL86LLT08Incident · No injuriesFinal reportPiper PA-34 · Smithville, TNThe acft ran off the departure end of the rwy during landing. The acft reportedly landed 1/2 way down the 3400 ft rwy. The plt stated in a post acc interview that he was 'too high too fast and too long.'Mar 25, 1986 · N3951X · Minor damageNTSB LAX86LA067Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Glendale, AZAfter completing a LCL flight the plt returned to his home base arpt & proceeded to land on the 2400 ft long rwy. The plt reported that he was unable to stop at its end and collided with barricades and a fence. A witness reported that the acft skidded on the…Dec 14, 1985 · N3885F · Substantial damageNTSB 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.Oct 18, 1984 · N500JT · Substantial damageNTSB NYC83LA213Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Rangeley, METhe pilot stated that a downdraft was encountered on the approach and in adding power to counteract, the airspeed increased over the threshold as the downdraft subsided. The acft floated 1/3 down the 2700 ft rwy and the remaining 1800FT was insufficient to…Aug 15, 1983 · N39934 · Substantial damage