The U.S. aircraft register, updated daily
Accidents · NTSB WPR20LA315 · Final report

Air Tractor AT-802A accident near Emmett, Idaho, September 23, 2020

On September 23, 2020, a 2020 Air Tractor AT-802A, registered N836MM, was substantially damaged in an accident during maneuvering near Emmett, Idaho. It was a firefighting flight under public-use (government) rules. 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 23, 2020
Place
Emmett, Idaho · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Air Tractor AT-802A, built 2020
Registration
N836MM · no longer on the register · serial 802A-0836
Damage
Substantial damage
Flight
Firefighting flight · public-use (government) rules

The NTSB's narrative final · quoted from the NTSB record

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.

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

  1. Low altitude operation/event during maneuvering defining event
  2. Collision with terrain or object (not controlled flight into terrain) during maneuvering (low-alt flying)

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Climb rate › Not attained/maintained
  • Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Contributed to outcome
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained
  • Personnel issues › Psychological › Attention/monitoring › Monitoring environment › Pilot
  • Environmental issues › Conditions/weather/phenomena › Light condition › (general) › Effect on operation

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 22,905 hours in all; 1,800 in this make and model; 60 in the last 90 days; 50 in the last 30 days; 22,850 as pilot in command
  • Last flight review: February 25, 2020
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: sngl
  • Injury: fatal

The aircraft

  • Maximum gross weight: 16,000 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Pratt & Whitney PT6A-67AG (turboprop); 0 hours total
  • Not recorded
  • Operator: Aero Seat Inc.

The flight

  • Departed from: ONO Ontario OR

Weather at the time

  • Light: daylight
  • Visibility: 9 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 41°F (5°C)
  • Altimeter: 29.94 inHg

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

20 documents, released by the NTSB on July 7, 2022. 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.

#DocumentWhat it is
1 Aircraft Performance Study PDF, 8 pages View Download
2 Data Recording Devices - Specialist's Factual Report PDF, 14 pages View Download
3 Attachment 1 to Data Recording Devices - Specialist's Factual Report - Aera 660 Tabular Data data file Download
4 Attachment 2 to Data Recording Devices - Specialist's Factual Report - Mvp 50T Tabular Data data file Download
5 Personal Electronic Devices - Specialist's Factual Report PDF, 3 pages View Download
6 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 9 pages View Download
7 Operator Statement and Witness Statement PDF, 17 pages View Download
8 Air Tactical Group Supervisor Statement PDF, 1 page View Download
9 Witness Statements PDF, 9 pages View Download
10 Record of E-mail Correspondence (Oas) PDF, 1 page View Download
11 AT-802/802A Frds Gen III AFM Supplement PDF, 11 pages View Download
12 Airframe Examination PDF, 12 pages View Download
13 Air Tractor Field Notes PDF, 5 pages View Download
14 Toxicological Report PDF, 1 page View Download
15 Memo for Record Autopsy PDF, 1 page View Download
16 Evidence Control Form PDF, 4 pages View Download
17 Statement of Party Representatives to NTSB Investigation PDF, 6 pages View Download
18 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page View Download
19 Accident Photos PDF, 4 pages View Download
20 Accident Video video View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

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.