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

Air Tractor AT-802A accident near Austin, Nevada, August 20, 2009

On August 20, 2009 at about 10:43 pm local time, a Air Tractor AT-802A, registered N807MA, was substantially damaged in an accident during maneuvering near Austin, Nevada (Battle Mountain airport). 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 failure to maintain a stabilized approach prior to the retardant drop and his subsequent failure to release the retardant load, resulting in a stall/mush and collision with terrain.

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

What the record shows

Date
August 20, 2009 · about 10:43 pm local time · cases in 2009
Place
Austin, Nevada · Battle Mountain · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Air Tractor AT-802A
Registration
N807MA · registry record · serial 802A-0145
Damage
Substantial damage
Flight
Firefighting flight · public-use (government) rules

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

The pilot was dropping fire retardant onto a saddle area located between the intersection of two perpendicular ridge lines. One of several witnesses reported that the airplane circled the area and then began a steep descent towards the intended drop point. The pilot did not release the load of retardant over the drop area. The witness observed the nose of the airplane pitch up and “mush through the flare.” The underside of the airplane then made contact with rising terrain within the saddle and continued uphill on its main landing gear toward a crest where the terrain dropped away. It then descended and collided with terrain in the valley below. Postaccident examination did not reveal any anomalies with the airplane, engine, or retardant dispersal system that would have prevented operation. The dispersal system’s operating procedures recommend that it be turned off during flight to prevent inadvertent dumping of the load. According to other pilots it is not uncommon to forget to re-engage the system prior to the drop. The dispersal system included an emergency manual release mechanism that could be used in the event of a primary system failure or an inadvertent oversight by the pilot to turn the system on; however, impact damage prevented an accurate determination of the system's armed status prior to impact. Global Positioning System (GPS) information revealed an excessive rate of descent just prior to the expected drop, which corroborated witness accounts. Analysis of the accident location, with respect to the GPS data, density altitude, airplane load, and witness statements, would indicate that the airplane probably encountered a stall/mush at the drop area. The high density altitude and the airplane's flap settings would have diminished the climb performance considerably in its retardant loaded state. The airplane's continued trajectory after initial impact, as well as propeller witness marks and internal engine damage, indicated that the engine was producing power at the time of the accident.

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. Abrupt maneuver during maneuvering defining event
  2. Aerodynamic stall/spin during maneuvering
  3. Collision with terrain or object (not controlled flight into terrain) during maneuvering

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • cause Aircraft › Aircraft systems › Equipment/furnishings › Agricultural/external load sys › Not used/operated other cases naming the cabin, seats and restraints
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 7,015 as pilot in command
  • Last flight review: December 12, 2007
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: sngl
  • Injury: fatal

The aircraft

  • Airframe total time: 2,798 hours
  • Last inspection: annual inspection, June 8, 2009; 8 hours since
  • Maximum gross weight: 16,000 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Pratt & Whitney Canada PT6A-67AG (turboprop); 0 hours total

The flight

  • Departed from: BAM Battle Mountain NV at 10:13 pm
  • Destination: BAM Battle Mountain NV
  • Runway 21, 7,299 ft by 150 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 104°F (40°C), dew point 21°F (-6°C)
  • Altimeter: 29.95 inHg
  • Observation at 10:53 pm from LOL, 54 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

34 documents, released by the NTSB on June 2, 2010. 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 Witness Statements PDF, 3 pages View Download
2 Wreckage Diagram PDF, 1 page View Download
3 GRVN2 Weather Observations PDF, 1 page View Download
4 Photograph 1: Accident Site Overview PDF, 1 page View Download
5 Photograph 2: Wind Direction After Accdident PDF, 1 page View Download
6 Photograph 3: View from Approximate Accident Flight Approach Path PDF, 1 page View Download
7 Photograph 4: Fuselage and Engine PDF, 1 page View Download
8 Photograph 5: 1ST Firegate Actuator PDF, 1 page View Download
9 Photograph 6: 2ND Firegate Actuator PDF, 1 page View Download
10 Photograph 7: Seperated Blade 1 PDF, 1 page View Download
11 Photograph 8: Seperated Blade 2 PDF, 1 page View Download
12 Photograph 9: Wings PDF, 1 page View Download
13 Photograph 10: Wreckage North View PDF, 1 page View Download
14 Photograph 11: Firegate Control Panel PDF, 1 page View Download
15 Image 1: Altitudes and Descent Rates PDF, 1 page View Download
16 Image 2: Retardant Drop Locations PDF, 1 page View Download
17 Image 3: Ground Scars PDF, 1 page View Download
18 Image 4: Wreckage Path PDF, 1 page View Download
19 Asm Supervisor Interview - Provided by Usdoi PDF, 1 page View Download
20 Airframe Examination Summary PDF, 3 pages View Download
21 Turbine Conversions Ltd. Report: Simulation of A Ruptured Emergency Accumulator Diaphragm PDF, 4 pages View Download
22 Pratt & Whitney Canada Corp Engine Exam Factual Notes PDF, 27 pages View Download
23 Toxicological Report PDF, 1 page View Download
24 Statement of Party Representatives to NTSB Investigation PDF, 2 pages View Download
25 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page View Download
26 Recorded GPS Flight Data data file Download
27 Aircraft Flight Manual Excerpts PDF, 6 pages View Download
28 Airframe Logbook Excerpts PDF, 6 pages View Download
29 Propeller Logbook Excerpts PDF, 2 pages View Download
30 Engine Logbook Excerpts PDF, 2 pages View Download
31 Fuel Receipt PDF, 1 page View Download
32 Weight and Balance Report PDF, 1 page View Download
33 Pilot Flight Experience Records Excerpts PDF, 5 pages View Download
34 Retardent Use Record PDF, 1 page View Download

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

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR09GA407.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.