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 “In flight collision with terrain/water”. 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

19822026

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\" = 230))
  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 DEN05FA087Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Telluride, COthe pilot's failure to maintain clearance from terrain. Contributing to the accident were the high, rising terrain and fatigue.Jun 9, 2005 · N81659 · DestroyedNTSB LAX04FA077Accident · 5 fatalField investigationFinal reportPiper PA-34-200T · Avalon, CAThe failure of both pilots to properly execute the published missed approach procedure.Dec 24, 2003 · N3747U · DestroyedNTSB FTW02FA130Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Alpine, UTThe pilot's failure to maintain clearance with terrain and continued flight into known adverse weather conditions. Contributing factors were the fog and rain weather conditions.Apr 27, 2002 · N132CP · DestroyedNTSB 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.Jan 20, 2001 · N99ED · Substantial damageNTSB DEN01LA007Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Fort Collins, COFailure by the pilot to follow instrument approach procedures and execute a missed approach when the runway environment was not in sight at decision height. A factor was low ceiling.Oct 28, 2000 · N238Z · Substantial damageNTSB ANC97LA019Accident · No injuriesLimited investigationFinal reportPiper PA-34 · Dillingham, AKthe pilot's failure to maintain sufficient altitude or clearance from terrain during a go-around. A factor related to the accident was: the dark, night condition.Jan 13, 1997 · N2491U · Substantial damageNTSB LAX92LA057Accident · 1 fatalLimited investigationFinal reportPiper PA-34-200T · Pine Valley, CAThe pilot's failure to monitor the proper altitude over obserable rising terrain. A contributing factor was the pilot's encounter with a strong downdraft.Dec 8, 1991 · N36506 · DestroyedNTSB LAX91LA067Accident · No injuriesLimited investigationFinal reportPiper PA 34-200T · Red Bluff, CAThe failure of the pilot in command to detect a descent below the minimum descent altitude for the approach in use.Jan 7, 1991 · N66SL · Substantial damageNTSB NYC88FA093Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Stratford, CTThe pilot and pilot-rated pax received vectors for multiple ILS approaches in deteriorating conditions. On the first attempt the aircraft passed over witnesses but was off course and not in a position to land. The second attempt was aborted before reaching…Feb 20, 1988 · N2469M · DestroyedNTSB MIA87FA086Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Oxford, MSThe acft struck an embankment about 5 feet below the crest & just short of the rwy while attempting to land at dusk & in reduced lighting conditions. The acft exploded & bounced out of the impact crater & came to rest about on the extended rwy centerline. An…Feb 19, 1987 · N3571X · DestroyedNTSB MKC85FA060Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Mena, ARThe pilot had been cleared for an instrument approach to themena, Arkansas intermountain regional airport. The airplane impacted a mountain side 8 1/2 miles off course.Feb 20, 1985 · N8658E · DestroyedNTSB 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…Apr 7, 1984 · N33569 · DestroyedNTSB NYC84FA042Accident · Serious injuriesField investigationFinal reportPiper PA-34-200T · Bennington, VTThe acft crashed into mountainous terrain at about the 1,800 ft level approximately 2 mi south of the arpt. The acft had been cleared for the vor-a approach. The missed approach point is the 6 DME point from the cambridge VOR on the 159 deg radial. Mda is…Nov 29, 1983 · N2958R · DestroyedNTSB LAX82FA038Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Near Las Vegas, NVThe aircraft, a Piper PA-34, was on a VFR flight to transport bank checks on a part 135 operation. Another company pilot in a Cessna 207 stated that he encountered instrument conditions at 9500 ft while he was flying from tonopah to las Vegas, NV. The Cessna…Jan 5, 1982 · N1956H · Destroyed