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

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, 2010 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\") = 2010
    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 ERA11CA052Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · Cambridge, MDThe commercial pilot’s inadequate flare during landing and the certificated flight instructor's delayed remedial action, which resulted in a hard landing.Oct 23, 2010 · N56101 · Substantial damageNTSB ERA10LA486Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Barnwell, SCThe failure of the No. 1 connecting rod end cap for undetermined reasons, which resulted in a total loss of engine power.Sep 19, 2010 · N799SQ · Substantial damageNTSB CEN10CA522Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · Berrien Springs, MIThe flight instructor's delayed remedial action, which resulted in a hard landing.Sep 6, 2010 · N404SE · Substantial damageNTSB ERA10LA370Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · New Bern, NCInadequate quality control at the fuel servo overhaul facility, which resulted in contamination of the fuel servo and a subsequent loss of engine power due to fuel starvation.Jul 20, 2010 · N8900E · Substantial damageNTSB CEN10CA318Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · Brookshire, TXThe pilot's failure to maintain directional control during the landing roll.Jun 7, 2010 · N55208 · Substantial damageNTSB WPR10CA266Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · St. George, UTThe pilot's inadequate compensation for the crosswind conditions and failure to maintain directional control during landing.May 26, 2010 · N40800 · Substantial damageNTSB WPR10LA165Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Eliza Island, WAThe total loss of engine power during cruise flight due to the failure of maintenance personnel to tighten a fitting on the propeller governor oil line, which resulted in a loss of engine oil and catastrophic engine failure.Mar 17, 2010 · N1KU · Substantial damage