NTSB investigations: Ayres S2R-G6

8 cases on aircraft the registry lists as Ayres S2R-G6, where the sequence of events included Collision with terr/obj (non-CFIT). 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

20082026
NTSB investigations: Ayres S2R-G6 per year, 2008–2026: 8 cases
20082
20091
20112
20121
20211
20241

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 ('0970216')
      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\" = '470' 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 CEN24LA291Accident · No injuriesClass 3 · LimitedFinal reportAyres S2R-G6 · Antioch, NEA total loss of engine power due to fuel contamination from an undetermined source.Jul 26, 2024 · N6136Z · Substantial damageNTSB ERA21LA167Accident · No injuriesClass 4 · LimitedFinal reportAyres S2R-G6 · Vienna, GAThe pilot’s improper decision to attempt a takeoff with a quartering tailwind and his failure to reject the takeoff in a timely manner, which resulted in a runway excursion.Mar 31, 2021 · N3299X · DestroyedNTSB WPR12LA256Accident · No injuriesLimited investigationFinal reportAyres S2R-G6 · Riverton, WYAn engine overspeed shortly after takeoff for reasons that could not be determined because postaccident examination revealed no mechanical malfunctions or failures that would have precluded normal operation.Jun 11, 2012 · N70WY · Substantial damageNTSB CEN11CA545Accident · No injuriesData collectionFinal reportAyres S2R-G6 · Forest City, IAThe pilot's inadequate visual lookout during an aerial application run, which resulted in an in-flight collision with a windmill.Jul 28, 2011 · N331BF · Substantial damageNTSB CEN11LA460Accident · No injuriesLimited investigationFinal reportAyres S2R600 · Pine Bluff, ARThe use of an incorrect mounting bolt by maintenance persons to attach the engine torque sensor, which resulted in an internal failure of the torque sensor and subsequent loss of engine power due to fuel starvation.Jul 6, 2011 · N3101S · Substantial damageNTSB CEN09LA403Accident · Serious injuriesLimited investigationFinal reportAyres S2R-G6 · Ainsworth, IAA component failure of the fuel control unit, which resulted in a loss of engine power.Jul 1, 2009 · N60015 · Substantial damageNTSB CHI08CA193Accident · No injuriesData collectionFinal reportAyres S2R-G6 · Kilbourne, ILThe inadequate preflight planning and preparation and the aborted takeoff not performed by the pilot. Contributing to the accident were the trees and transmission wire.Jul 15, 2008 · N3105U · Substantial damageNTSB DEN08LA107Accident · No injuriesLimited investigationFinal reportAyres S2R-G6 · Pine Bluff, ARA total loss of engine power due to fuel starvation as a result of an electrical short in the wiring to the manual fuel switch that closed the fuel valves.Jun 20, 2008 · N61374 · Substantial damage