FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26LA177 · Air Tractor Inc AT-602

5 May 2026 · El Campo, TX, United States

Sug-Air Air Tractor Inc AT-602 · Accident: loss of control in flight during takeoff

From Tradewind Agricultural Airport (8TE8) to an unrecorded destination

Report a problem

Event

NTSB case
CEN26LA177
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
0
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-602

Aircraft type
Air Tractor AT-602
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
N422TW
Operator
Sug-Air
Onboard fatalities
Unknown
Route
From Tradewind Agricultural Airport (8TE8), El Campo, TXTo not recorded
Aircraft age
About 10 years (built 2016)
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • 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, during the takeoff and initial climb to the south, the airplane encountered a “wind disturbance” which resulted in an uncommanded roll to the left. The left wing subsequently dropped and contacted a small wooden shed. The airplane yawed to the left, crossed a road, and impacted in an adjacent cornfield where it came to rest inverted. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation, and he should have climbed higher to avoid downdrafts from structures located near the runway. The pilot reported the winds were 15 to 20 knots from an unknown direction.

Probable cause

The pilot’s failure to maintain aircraft control during takeoff resulting in a collision with a building during takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN26LA177
Event ID
20260506202939
Case number
CEN26LA177
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, cause areas. 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: e3e455e3c41870d4c81275f02cbabc1e610d1da0726af3907411bfb5d4acd204; retrieved 2026-09-16T21:24:00.473Z.