FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10CA445 · Air Tractor Inc AT-502B

28 Jul 2010 · Zwingle, IA, United States

Klinkenborg Aerial Spraying & Seeding Air Tractor Inc AT-502B · Accident: low altitude operation/event while maneuvering

From Zwingle, IA to Zwingle, IA

Report a problem

Event

NTSB case
CEN10CA445
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-502B

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
N6030U
Onboard fatalities
Unknown
Route
From Zwingle, IATo Zwingle, IA
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

  • Personnel issues › Psychological

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

NTSB narrative

The pilot reported that he was conducting agricutural spraying operations in the airplane when the accident occurred. He stated that he had completed a spray pass and made a turn for another pass. As he came out of the turn the airplane was heading west into the afternoon sun. The pilot stated that he misjudged the height of the top wire of poles along the edge of the field. After striking the wire he noted that he had almost no elevator control and executed a landing in a field. The airplane subsequently nosed over. The pilot made no mention of control difficulties prior to striking the wire.

Probable cause

The pilot's failure to maintain clearance from wires during the agricultural flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10CA445
Event ID
20100730X21508
Case number
CEN10CA445
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: f71a48c7fd175172488bcabb368223f00c6ddc4b08e19b6830afd49f5a9cfd45; retrieved 2026-09-15T14:46:34.387Z.