NTSB investigations: Piper PA-28R-200, 2012

7 cases on aircraft the registry lists as Piper PA-28R-200. 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

19692026
NTSB investigations: Piper PA-28R-200, 2012 per year, 1969–2026: 794 cases
19695
197010
197111
197227
197337
197439
197539
197644
197750
197841
197925
198027
198125
198215
198320
198413
198511
198615
198715
198817
198915
199011
199114
199217
199313
199418
19958
19968
199718
199812
19999
200010
20016
20029
200311
20046
20057
20065
20077
20084
20098
20107
20113
20127
20135
20142
201510
20169
201711
20185
20198
20204
20215
20222
20233
20245
20255
20261

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 year(c.\"eventDate\") = 2012
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102811'))
  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 ERA13LA097Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Lock Haven, PAThe reinstallation of improper connecting rods at engine overhaul, which resulted in abnormal wear of the connecting rod bearings; while the bearings did not meet the manufacturer’s specifications, the use of the unapproved connecting rods more likely caused…Dec 23, 2012 · N2074T · Substantial damageNTSB CEN12CA671Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · Goldsby, OKThe commercial pilot did not attain the proper touchdown point during the landing, which resulted in a premature touchdown and an impact with the edge of the runway surface.Aug 29, 2012 · N7602C · Substantial damageNTSB WPR12LA377Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Everett, WAA hard landing likely made by the private pilot on a solo flight that preceded the dual instructional flight during which the wing damage became obvious.Aug 28, 2012 · N4922T · Substantial damageNTSB CEN12IA377Incident · No injuriesIncident investigationFinal reportPiper PA-28R-200 · Lacon, ILThe propeller blade’s failure due to a fatigue crack that originated from a surface gouge that resulted from foreign object damage to the propeller blade that occurred at an unknown time.Jun 18, 2012 · N4350T · Minor damageNTSB ERA12LA267Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Eastover, SCInadequate or loss of through bolt preload tension, which resulted in fretting between the engine halves, the subsequent failure of one cylinder through bolt, the loosening of additional cylinder retaining studs, and the fracture of the crankcase.…Apr 3, 2012 · N961JD · Substantial damageNTSB ERA12CA242Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · New Smyrna, FLThe pilot's improper flare, which resulted in a hard landing. Contributing to the accident was the flight instructor's inadequate remedial action.Mar 18, 2012 · N15764 · Substantial damageNTSB CEN12LA189Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Arcola, TXThe pilot did not maintain adequate crosswind correction during the landing flare and the flight instructor's delayed remedial action.Mar 18, 2012 · N56273 · Substantial damage