FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24FA220 · Air Tractor Inc AT-602

14 Jun 2024 · Broseley, MO, United States

Mccallister Aviation Rentals & Sales Air Tractor Inc AT-602 · Accident: loss of control in flight while maneuvering

From Broseley, MO (private airstrip) to Broseley, MO (private airstrip)

Report a problem

Event

NTSB case
CEN24FA220
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
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-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
N115AA
Onboard fatalities
Unknown
Route
From Broseley, MO (private airstrip)To Broseley, MO (private airstrip)
Aircraft age
About 13 years (built 2011)
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
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

  • Aircraft › Aircraft oper/perf/capability
  • Not determined › Not determined
  • Personnel issues › Task performance

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

NTSB narrative

The operator reported that the pilot departed to apply fertilizer to a field about 4 miles north of the airstrip. An individual about 2 miles from the accident site reported hearing what he believed was the accident airplane for a total of about 15 minutes. The pilot seemed to be flying in the vicinity of the accident site, and for most of that time the sound of the engine seemed normal. However, toward the end of that time the pitch of the engine increased slightly for about 3 or 4 seconds before the sound then completely faded away. He did not hear the airplane again nor did he hear the impact. The flight was reported overdue about 90 minutes after takeoff when the pilot had not returned. A search subsequently located the accident site about 3 miles from the departure airstrip: the airplane impacted a wooded area adjacent to a soybean field and a postimpact fire ensued. There were no power lines, towers, or guy wires observed in the immediate vicinity of the accident site. The owner of the field reported that the pilot was scheduled to apply fertilizer to three of his fields that day. A visual examination of the field that morning by the farmer’s employees found that the pilot likely made one application pass on the field. No evidence of multiple application passes was observed. Multiple tree propeller cuts and tree breaks were present in the immediate vicinity of the wreckage. Detailed airframe, engine, and propeller examinations did not reveal any anomalies associated with a preimpact failure or malfunction, including an inflight structural failure or flight control system anomaly. The examinations determined that the engine was operating and the propeller blades were rotating under power at the time of impact. Day visual meteorological conditions prevailed at the time of the accident. There was nothing in the results of the autopsy or toxicology to suggest pilot impairment or incapacitation. Because no airplane position data for the accident flight was available, an airplane performance analysis could not be conducted. The confined area of the wreckage and the limited tree damage outside of the immediate vicinity of the accident site suggested a high angle of descent such as found following an inadvertent aerodynamic stall. However, without any additional data, the reason for the pilot’s inflight loss of control could not be determined.

Probable cause

The pilot’s inflight loss of airplane control for reasons that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24FA220
Event ID
20240614194469
Case number
CEN24FA220
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: b97d6d054ccc4e1e9e497d192c8d040ed182a7add1e70d1354319b2fe31d286f; retrieved 2026-09-15T08:18:05.766Z.