FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12CA375 · Air Tractor Inc AT-502

15 Jun 2012 · Ipswich, SD, United States

Tri County Ag Service Air Tractor Inc AT-502 · Accident: runway excursion during takeoff

From TC Field (2SD9) to TC Field (2SD9)

Report a problem

Event

NTSB case
CEN12CA375
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

Air Tractor Inc AT-502

Aircraft type
Air Tractor AT-502
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
N45379
Onboard fatalities
Unknown
Route
From TC Field (2SD9), Ipswich, SDTo TC Field (2SD9), Ipswich, SD
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
Takeoff
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
Runway excursion
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

  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane was departing from a 2,400-foot asphalt runway on an aerial application flight. The airplane was loaded to its maximum gross takeoff weight and configured with 10 degrees of flaps prior to the takeoff roll. The pilot reported that a tall stand of trees at the southeast side of the departure end of the runway blocked the wind and seemed to “create a void in the air,” which resulted in an extended takeoff roll. Electing not to abort the takeoff, the pilot added more flaps in an attempt to get the airplane airborne; however, he was unsuccessful. The airplane went off the end of the runway, hit a ditch, and skidded across the road into a field. The landing gear separated from the airframe and the airplane’s fuselage and control surfaces sustained substantial damage. The pilot reported that there were no mechanical malfunctions or failures that would have precluded normal operation during the attempted takeoff.

Probable cause

The pilot's failure to abort the takeoff, which resulted in a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12CA375
Event ID
20120618X11856
Case number
CEN12CA375
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. 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: 2d54550bdd2a1815abdb4894c2c62816b7e9555e403e1274fa6a363e35ce4a5b; retrieved 2026-09-15T18:33:08.920Z.