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

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, 2005 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\") = 2005
    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 DFW05LA183Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Pollock, LAThe loss of engine power due to a loose engine lubrication system component in the crankcase. A contributing factor was the lack of suitable terrain for the forced landing.Jul 16, 2005 · N33720 · Substantial damageNTSB ATL05CA114Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · Daytona Beach, FLThe private pilots improper landing flare. Factors were flight instructors inadequate supervision, and landing crosswind.Jun 19, 2005 · N4313X · Substantial damageNTSB LAX05LA214Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Happy Jack, AZThe fracture/separation of an engine intake valve during cruise flight, which resulted in a partial loss of engine power and a forced landing.Jun 16, 2005 · N5229T · Substantial damageNTSB LAX05CA181Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · Tucson, AZthe improper flare by an undetermined crewmember, which resulted in a hard landing.May 15, 2005 · N55069 · Substantial damageNTSB DFW05FA099Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Jefferson, TXThe pilot's failure to maintain clearance from an unmarked transmission line. A contributing factor was the low altitude flight.Apr 10, 2005 · N2981R · DestroyedNTSB CHI05FA081Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · West Lafayette, INThe pilot's inadvertent flight into instrument conditions and his not maintaining control of the complex airplane during initial climb. Factors in the accident were the low ceiling, the early dawn condition, and the pilots intentional unauthorized use of the…Mar 26, 2005 · N999SK · DestroyedNTSB LAX05LA227Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Phoenix, AZsubstantial damage to the airplane during an unknown phase of flight for undetermined reasons.Mar 11, 2005 · N2882R · Substantial damage