NTSB investigations: Piper PA-28-140

6 cases on aircraft the registry lists as Piper PA-28-140, where the sequence of events included Landing area overshoot. 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

20112026
NTSB investigations: Piper PA-28-140 per year, 2011–2026: 6 cases
20111
20131
20171
20181
20191
20221

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 ('7102802')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '380' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
  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 ANC23LA014Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-28-140 · Anchorage, AKThe pilot’s failure to maintain directional control of the airplane during landing.Nov 27, 2022 · N5626U · Substantial damageNTSB ERA20CA111Accident · No injuriesClass 4 · Data collectionFinal reportPiper PA28 · Hanson, MAThe flight instructor's delayed remedial action, which resulted in his decision to perform an off field landing and the airplane's subsequent impact with terrain.Dec 23, 2019 · N5792U · Substantial damageNTSB WPR18LA173Accident · No injuriesClass 3 · LimitedFinal reportPiper PA 28-140 · Hartford, CTA loss of engine power for undetermined reasons because postaccident examination of the engine and fuel system did not reveal any anomalies that would have precluded normal operation, which led to the pilot’s forced landing and subsequent runway overshoot and…Jun 16, 2018 · N1782J · Substantial damageNTSB CEN17FA139Accident · 1 fatalField investigationFinal reportPiper PA-28-140 · Stonewall, TXThe pilot's failure to attain a proper touchdown point following a loss of engine power and his inability to stop the airplane on the short, soft runway. Contributing to the accident was the inadequate maintenance of the airplane by the owner and the mechanic…Mar 25, 2017 · N4329T · Substantial damageNTSB WPR13CA273Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Coolin, IDThe pilot’s failure to maintain an adequate glide path, which led to a runway excursion and collision with objects.Jun 16, 2013 · N199 · Substantial damageNTSB CEN11LA426Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · New Philadelphia, OHThe pilot's incorrect identification of the wind direction before landing, which resulted in a tailwind landing and subsequent runway excursion.Jun 25, 2011 · N6980W · Substantial damage