Air Tractor INC AT-602 accident near Broseley, Missouri, June 14, 2024
On June 14, 2024 at about 12:00 pm local time, a 2011 Air Tractor INC AT-602, registered N115AA, was destroyed in an accident during maneuvering (low-alt flying) near Broseley, Missouri. It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s inflight loss of airplane control for reasons that could not be determined.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 14, 2024 · about 12:00 pm local time
- Place
- Broseley, Missouri · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Air Tractor INC AT-602, built 2011 · all AT-602s on the register
- Registration
- N115AA · no longer on the register · serial 602-1210
- Damage
- Destroyed
- Flight
- Aerial application (crop spraying) flight · agricultural flying rules (Part 137)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control in flight during maneuvering (low-alt flying) defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Not determined › Not determined › (general) › (general) › Unknown/Not determined
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 2,700 hours in all; 90 in the last 90 days
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: sngl
- Injury: fatal
The aircraft
- Airframe total time: 4,024.1 hours
- Last inspection: annual inspection, February 5, 2024
- Maximum gross weight: 12,500 lb
- Seats: 1
- Landing gear: fixed
- Engine: P&W Canada PT6A-65AG (turboprop); 4,147 hours total
- Fire on the ground
- Operator: Mccallister Aviation Rentals & Sales LLC
The flight
- Departed from: PVT Broseley MO at 11:00 am
- Destination: PVT Broseley MO
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 170° at 4 knots
- Visibility: 11 statute miles
- Sky: clear
- Temperature: 72°F (22°C), dew point 66°F (19°C)
- Altimeter: 29.93 inHg
- Observation at 6:53 am from KPOF, 8 miles away
Weather report (METAR): METAR KPOF 141153Z AUTO 17004KT 10SM CLR 22/19 A2993
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
14 documents, released by the NTSB on February 19, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
Other NTSB records under N115AA the same tail number, which may have belonged to a different aircraft at the time
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
