NTSB investigations: Piper PA-34-200

8 cases on aircraft the registry lists as Piper PA-34-200, 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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19822026

NTSB investigations: Piper PA-34-200 per year, 1982–2026: 8 cases
1982	1
1985	1
1986	1
1989	1
1991	1
1995	2
1998	1

Where

Open the map

Latest cases

Query with SQL

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 ('7103405') 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

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 ('7103405')
      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.

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 ('7103405')
    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

Run 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 NYC99LA019Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-R200 · Caldwell, NJThe failure of both the normal and emergency brake systems.Oct 9, 1998 · N800JK · Destroyed NTSB MIA95LA209Accident · No injuriesLimited investigationFinal reportPiper PA-34-200 · Kissimmee, FLThe pilot-in-command's decision to allow the student to land long and not use all the available runway and his delay in aborting the takeoff resulting in a runway overrun.Aug 20, 1995 · N1496T · Substantial damage NTSB LAX95LA230Accident · No injuriesLimited investigationFinal reportPiper PA-34-200 · Avalon, CAcomplete brake failure due to improper replacement and service of the brakes by company maintenance personnel.Jun 24, 1995 · N56484 · Substantial damage NTSB NYC91LA233Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200 · Easton, PAAn overrun after the pilot-in-command landed long on a short, wet runway. A factor related to the accident was the failure of the pilot to make a go-around.Sep 10, 1991 · N55145 · Substantial damage NTSB MIA89LA209Accident · No injuriesLimited investigationFinal reportPiper PA-34 · Ackerman, MSThe pilot's selection of the wrong runway and his improper inflight planning/decision which resulted in a situation from which he could neither go-around nor stop on the remaining runway. The thunderstorms, inoperative (disrepaired) wind sock, and rough…Jul 29, 1989 · N711DL · Substantial damage NTSB MIA86LA248Accident · No injuriesLimited investigationFinal reportPiper PA-34-200 · Miami, FLThe plt stated that his landing apch was high. The acft touched down too fast and the plt veered the acft off the left side of the rwy to avoid contacting a fence at the end of the rwy. The acft traveled into soft dirt and the landing gear collapsed.Sep 13, 1986 · N1421T · Substantial damage NTSB ATL85LA129Accident · No injuriesLimited investigationFinal reportPiper PA-34-200 · Concord, NCThe plt reported that the pvt arpt at the destination had a unidirectional strip with hi obstructions on both ends. Obstacles, rwy slope & noise abatement considerations required that rwy 4 be used for landings. At 1351 EST, the wind at charlotte, NC was from…Apr 4, 1985 · N1071U · Substantial damage NTSB NYC82DA055Accident · No injuriesFinal reportPiper PA-34-200 · Atlantic City, NJThe pilot reported that he elected to fly his IFR approach to the runway with a 10 kt quartering tail wind. He reported encountering hydroplaning conditions after landing within the first quarter of the runway. By the time he considered a go-around, there was…Mar 12, 1982 · N1519T · Substantial damage