FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23FA412 · Air Tractor Inc AT-502B

19 Sept 2023 · New Rockford, ND, United States

Air Tractor Inc AT-502B · Accident: low altitude operation/event while maneuvering

From Carrington Municipal Airport (46D) to Carrington Municipal Airport (46D)

Report a problem

Event

NTSB case
CEN23FA412
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
1 · 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-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
N502NB
Operator
Larry J. Polries · private individual
Onboard fatalities
Unknown
Route
From Carrington Municipal Airport (46D), Carrington, NDTo Carrington Municipal Airport (46D), Carrington, ND
Aircraft age
About 11 years (built 2012)
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 › Action/decision

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 was conducting a low-level aerial application flight, spraying a field of sunflowers, when the accident occurred. Multiple witnesses reported that the airplane flew underneath power lines and then the top of the vertical stabilizer was sheared off by the power lines. The airplane continued to fly straight ahead, and about .25 miles west of the power lines, the airplane made a left-turning dive and subsequently impacted a cornfield. A postimpact fire partially consumed the accessory case area of the engine. The airplane sustained substantial damage to both wings, the fuselage, and the empennage. Postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation before the airplane impacted the power line. The torsional deformation observed on the engine’s exhaust duct case, combined with the propeller damage and evidence of propeller strikes on the terrain, indicates that the engine was producing power at impact. About 154-inches of the 165-ich wire deflector cable was not recovered. The separated ends of the cable sections attached to the fuselage and vertical stabilizer were consistent with tension overload separation. It is likely that the wire deflector cable’s impact with power line exceeded the cable’s minimum breaking strength. Toxicological testing indicated that the pilot had used a cannabis product and methamphetamine. However, neither delta-9-THC nor its psychoactive metabolite was detected in the tested specimens, and the non-psychoactive metabolite carboxy-delta-9-THC was not detected in blood. This indicates that it is unlikely that effects of the pilot’s cannabis use contributed to the accident. Toxicological results also indicated that the pilot likely had used methamphetamine and was experiencing some methamphetamine effects at the time of the accident. Details of his methamphetamine use and specific associated effects at the time of the accident are unknown. Such effects may have ranged from improved reaction time to impaired judgment, perception, reaction, and control. Whether effects of the pilot’s methamphetamine use contributed to the accident could not be determined. Based on the available evidence, the pilot likely misjudged the overhead clearance necessary to avoid the power lines. About 8 ft (about 4 ft on the top of the airplane and about 4 ft on the bottom of the airplane) clearance was available for the airplane to fly underneath the power lines and yet remain above the sunflowers.

Probable cause

The pilot’s failure to maintain clearance from overhead power lines during an aerial application flight. Contributing to the accident was the pilot’s decision to fly under the power lines with a small area of clearance available for the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23FA412
Event ID
20230919193099
Case number
CEN23FA412
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: 59ff4ce68f2cca0a82bcb43604132c5f3e4bd40f943c92e75556554cbd7d6ce5; retrieved 2026-09-15T08:06:02.109Z.