FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW08CA182 · Ayres S2R

11 Jul 2008 · Baton Rouge, LA, United States

Ayres S2R · Accident: low altitude operation/event while maneuvering

From Erwinville, LA to an unrecorded destination

Report a problem

Event

NTSB case
DFW08CA182
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 S2R

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
N2068B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Erwinville, LATo not recorded
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
Maneuvering · low-altitude flying
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
Low altitude operation/event
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

  • Aircraft › Aircraft oper/perf/capability

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

NTSB narrative

A 26,090-hour commercial pilot maneuvered the airplane for an agricultural application pass when the airplane's landing gear contacted a transmission wire. The wire entangled with the airplane resulting in a loss of control and subsequent collision with terrain. The airplane was substantially damaged and the pilot was able to egress the airplane. The pilot reported that there were no malfunctions or mechanical failures prior to contact with the transmission wire.

Probable cause

The pilot's failure to maintain clearance from the transmission wire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW08CA182
Event ID
20080811X01213
Case number
DFW08CA182
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: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 07985f49b126413c4d7d6e20dc626851ef7231a27098f1cc830022aba859251a; retrieved 2026-09-15T10:02:28.930Z.