FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11CA224 · Ayres Corporation S2R-T34

11 Mar 2011 · Swan Lake, AR, United States

Swan Lake Flying Service Ayres Corporation S2R-T34 · Accident: windshear or thunderstorm on approach

From Swan Lake, AR (private airstrip) to Swan Lake, AR (private airstrip)

Report a problem

Event

NTSB case
CEN11CA224
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Ayres Corporation S2R-T34

Aircraft type
Ayres S2
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N92KM
Onboard fatalities
Unknown
Route
From Swan Lake, AR (private airstrip)To Swan Lake, AR (private airstrip)
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 137: Agricultural
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Windshear or thunderstorm
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the pilot, he was approaching the airport to land when he encountered a gust of wind. The airplane collided with power lines and subsequently impacted the ground below, coming to rest inverted. The empennage was twisted and partially separated, and both wings were crushed. The pilot reported no preimpact mechanical anomalies with the airplane.

Probable cause

An in-flight collision with power lines following an encounter with a wind gust.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11CA224
Event ID
20110314X70137
Case number
CEN11CA224
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2011-03-12.
  • API snapshot SHA-256: 8848ca0bf6d32d6148a2290fd5210acd13f9c34bb668a64fa80ceef3962be4e1; retrieved 2026-09-15T15:54:31.824Z.