FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20CA311 · Air Tractor AT 401 Undesignat

27 Jul 2020 · Burlington, CO, United States

Air Care Air Tractor AT 401 Undesignat · Accident: low altitude operation/event while maneuvering

From Kit Carson County Airport (ITR) to an unrecorded destination

Report a problem

Event

NTSB case
CEN20CA311
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 AT 401 Undesignat

Aircraft type
Air Tractor AT-401
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
N9190Q
Operator
Air Care
Onboard fatalities
Unknown
Route
From Kit Carson County Airport (ITR), Burlington, COTo not recorded
Aircraft age
About 31 years (built 1989)
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

  • Environmental issues › Physical environment
  • Personnel issues › Psychological

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

NTSB narrative

The pilot flew the agricultural airplane to the designated spray area. He made 3-4 passes on a corn field and surveyed the area for guy-wires (a tower was adjacent to the field). He flew multiple passes around the tower to look for guy-wires but he was not able to get an exact location on the tower’s guy-wires and started spraying the field from south to north, and then west to east. After spraying about 4 passes in the middle of the field and 3 passes on the west end of the field the airplane struck a guy-wire with the right wing. After the airplane hit the wire, the pilot had trouble maintaining altitude. The airplane collided through a single set of power lines and struck the ground, resulting in substantial damage to the wings, fuselage, and empennage.

Probable cause

The pilot’s failure to maintain clearance from guy-wires during low-altitude agricultural operations.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20CA311
Event ID
20200727X40311
Case number
CEN20CA311
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, 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: 90fdb6a1633b0b96406db87bedb667b4e9951262e5b63b27f90cb65188208764; retrieved 2026-09-16T12:17:19.375Z.