FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR20LA315 · Air Tractor AT-802A

22 Sept 2020 · Emmett, ID, United States

Aero Seat Air Tractor AT-802A · Accident: low altitude operation/event while maneuvering

From Ontario Municipal Airport (ONO) to an unrecorded destination

Report a problem

Event

NTSB case
WPR20LA315
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
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

Air Tractor AT-802A

Aircraft type
Air Tractor AT-802
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
N836MM
Operator
Aero Seat
Onboard fatalities
Unknown
Route
From Ontario Municipal Airport (ONO), Ontario, ORTo not recorded
Aircraft age
Built the same year (2020)
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
Maneuvering
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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

A flight of three airplanes departed to conduct firefighting operations; the accident airplane was number two. After establishing contact with the Air Tactical Group Supervisor (ATGS), the pilots were briefed on the target description and identified the steepness of the drop and the rising terrain on the exit. After the first airplane completed its pass, the ATGS requested that the accident airplane adjust his flightpath to the left to reinforce the line closer to the burned vegetation. The accident pilot confirmed his gate was armed, on the correct line and was subsequently cleared to proceed and drop the fire retardant. Witnesses reported that the airplane crossed over the intended target ridge, descended into the valley, and passed the proposed drop area without releasing any retardant. No mechanical failures or malfunctions were revealed with the firegate system, and it was undetermined why the accident pilot did not accomplish the retardant release. The accident airplane initiated a climb; however, it impacted terrain about 40 ft below the opposing ridge line.

A video provided by a witness showed the accident airplane descend into the valley, without releasing any retardant. The airplane did not begin its climb out of the valley until 3 seconds before impact with rising terrain. The NTSB’s performance study determined that there was an insufficient amount of time and distance for the airplane to gain enough attitude to clear the rising terrain.

The pilot had orbited the area at least 3 times from about 2,000 ft above the ground before initiating the drop run. This would have provided an opportunity to assess ground features, including terrain, that could aid in conducting the run. However, environmental conditions in the area at the time may have made terrain features more difficult to discern from the lower altitude of the drop run because of the uniformity of the vegetation on the ridges and flat light conditions; and would have made accurate assessment of height above and distance from terrain more difficult. This may have led the pilot to believe he had greater clearance from terrain than what was available. Had the pilot initiated a climb at the GPS point prior to the impact location, there would have been sufficient altitude to clear the rising terrain. However, the airplane continued to descend into the valley and the pilot initiated the climb too late for the airplane to clear terrain. Postaccident examination of the recovered airframe and engine did not reveal evidence of any mechanical anomalies that would have precluded normal operation.

Probable cause

The pilot’s descent below surrounding terrain and his delayed decision to initiate a climb which resulted in impact with terrain. Contributing to the accident were terrain and lighting conditions that affected the pilot’s ability to accurately assess terrain clearance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR20LA315
Event ID
20200922X35434
Case number
WPR20LA315
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: local date, investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2020-09-23.
  • API snapshot SHA-256: fb7b89144cfca0f583e00d7ff3c2f5c7882ac2d542de1c3325a984e9b9a6400a; retrieved 2026-09-15T07:20:19.680Z.