WPR20LA246 · Air Tractor AT802 A
Air Tractor AT802 A and M & M Air Service Of Beaumont Air Tractor AT802 A · Accident: midair collision en route
Event
- NTSB case
- WPR20LA246
- 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
- 2 · 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
- Government
- 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
Aircraft 1 · Air Tractor AT802 A
- Aircraft type
- Air Tractor AT802
- 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
- N8510M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mesquite Airport (67L), Mesquite, NVTo Mesquite Airport (67L), Mesquite, NV
- Aircraft age
- About 17 years (built 2003)
- 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
- Public Aircraft
- 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
- En route
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · Air Tractor AT802 A
- Aircraft type
- Air Tractor AT802
- 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
- N1558W
- Operator
- M & M Air Service Of Beaumont
- Onboard fatalities
- Unknown
- Route
- From Mesquite Airport (67L), Mesquite, NVTo Mesquite Airport (67L), Mesquite, NV
- Aircraft age
- About 27 years (built 1993)
- 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
- Public Aircraft
- 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
- En route
- 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
- Midair collision
- 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
- Environmental issues › Physical environment
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilots for both airplanes departed on an approximate 30-minute flight to a fire traffic area (FTA) under contract with the Department of the Interior (DOI) to extend a fire retardant line near a wildland fire for the third time that day. One airplane was flying as the lead, and the other airplane was in trail. After they received permission to enter the FTA and instructions with the drop heading, the pilots of both airplanes followed a third airplane to the drop area on a path that resembled an airport traffic pattern.
The pilot in trail had maintained about 1,500 ft distance from the lead airplane for most of the flight until they were on the final leg of the drop when the trail airplane started to encroach on the lead. The trail airplane was about 500 ft behind and 100 ft below the lead airplane about 5 seconds prior to the drop. After deploying the retardant, the lead airplane began a climb while the trail airplane flew through the lead airplane’s retardant plume. The pilot of the trail airplane announced over the radio that he had retardant on his windshield, was executing a go-around, and possibly performing an emergency dump of his load, as well. The trail pilot then dumped his load and immediately entered a climb. At this point, he was 50 ft behind and 125 ft below the lead airplane. The airplane in trail then collided with the lead airplane from below and they subsequently impacted the ground. Both airplanes were destroyed by postcrash fire.
Postaccident examination of the trail airplane did not reveal any preimpact mechanical anomalies. Portions of the lead airplane’s flight control system had either been destroyed by fire or were missing; however, the airplane’s flightpath and climb were consistent with a controlled flight and do not indicate the airplane experienced any preimpact anomalies. The propeller blades for both airplanes displayed signatures consistent with high power settings at the time of impact. Two of the lead airplane’s propeller blades displayed yellow paint transfer marks consistent with the mechanical cuts observed on the trail airplane forward of the engine firewall. The orientation and position of the cuts, along with rubber marks on the cockpit step suggests the trail airplane impacted the lead airplane from below, slightly ahead, and 20° left of the lead airplane’s heading.
Both pilots were qualified to fly the airplanes by regulatory standards and their contractual obligations with DOI. However, there was no record either pilot had received overrun procedures training in the 4 years prior to the accident.
A video of the trail airplane’s go-around maneuver showed the airplane in a controlled climb; however, the direction was not consistent with the exit procedures that had been briefed prior to the retardant deployment. Had the pilot executed a left turn and climbed as prescribed by the brief, he would have likely remained clear of the lead airplane.
The amount of retardant that contacted the trail pilot’s windshield could not be determined for lack of evidence. However, the pilot’s radio call indicated he had retardant on his windscreen and that he was performing an emergency procedure to go-around and dump the retardant indicated the pilot was concerned about the loss of visibility.
The wildland fire procedures stated that the pilot in trail would have been responsible for maintaining separation from the lead airplane. The pilot in trail had at least one reported event that captured him flying too close to a lead airplane during another flight. However, the investigation was unable to confirm if there were other events and an established pattern of this behavior. The available evidence is consistent with the trailing pilot’s failure to maintain separation from the lead airplane during a fire retardant deployment, which resulted in his flying through a plume of retardant that likely obscured his view through the airplane’s windshield and led to a collision with the lead airplane.
Probable cause
The trailing pilot’s failure to maintain separation from the lead airplane during a fire retardant deployment flight, which resulted in the trailing airplane flying through a plume of retardant and the trailing pilot’s subsequent loss of visibility that led to a collision with the lead airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20LA246
- Event ID
- 20200730X91205
- Case number
- WPR20LA246
- 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: 30ae9d85f8c4725e69f165cc98689ecb747fcdde2bf797ee71a62da395386a6c; retrieved 2026-09-13T18:10:45.225Z.