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

Air Tractor INC AT-802A accident near Miles City, Montana, May 9, 2011

On May 9, 2011 at about 3:15 pm local time, a Air Tractor INC AT-802A, registered N8523H, was substantially damaged in an accident during maneuvering near Miles City, Montana. It was a positioning flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot's continued visual flight rules flight into deteriorating weather conditions in an airplane not equipped for instrument flight, which resulted in a collision with terrain.

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

What the record shows

Date
May 9, 2011 · about 3:15 pm local time
Place
Miles City, Montana · map
Type
Accident
Injuries
1 person was killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Air Tractor INC AT-802A · all AT-802As on the register
Registration
N8523H · registry record · serial 802A-0162
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

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

The instrument-rated pilot departed to reposition the airplane, which was configured for visual flight rules (VFR) operations only, to its base of operation about 316 miles northwest of the departure airport. Weather conditions at the departure airport were VFR, however, the destination airport and throughout the western portion of the route had deteriorating weather conditions and low cloud ceilings. There was no record of the pilot obtaining a weather brief for the flight; however, while filing a VFR flight plan, the pilot informed the weather briefer that he already had weather information and declined any additional weather information offered by the briefer. A witness located near the accident site heard the sound of an airplane flying low and fast from the east to the west past her home. Shortly after hearing the airplane, she heard a "poof" sound and immediately looked outside for the airplane. The witness stated that she did not see the airplane or any smoke in the area; however, she observed a cloud layer covering the top of the mountain ridge where the accident site was later located. The global positioning system (GPS) track for the flight indicated that during the later portion of the flight, the airplane descended from an altitude of about 5,869 feet mean sea level (msl) to 3,054 feet msl, while conducting several course changes from the northwest to the southwest, most likely as a result of the pilot attempting to avoid or remain clear of the deteriorating weather conditions. The GPS data further showed a climb to an altitude of about 3,241 feet msl before turning left to a westerly heading. About 2 minutes later, the data showed a left turn to the southwest at an altitude of about 3,406 feet msl, where a descent was initiated. The last recorded data point was recorded at an altitude of about 3,284 feet msl. The accident site was located about 0.15 miles southwest of the last recorded GPS position at an elevation of about 3,077 feet msl. A weather report in the area of the accident showed a visibility of 2 miles, mist, overcast cloud layer at 700 feet, and a variable ceiling from 400 feet to 1,100 feet.

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. VFR encounter with IMC during maneuvering
  2. Controlled flight into terrain or object (CFIT) during maneuvering defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Personnel issues › Task performance › Planning/preparation › Weather planning › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Effect on operation
  • Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Not specified

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 18,824 hours in all; 60 in the last 90 days
  • Last flight review: March 8, 2010
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: ctr
  • Injury: fatal

The aircraft

  • Airframe total time: 1,407 hours
  • Last inspection: annual inspection, February 26, 2011
  • Maximum gross weight: 16,000 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: P&W PT6A-67AG (turboprop); 0 hours total
  • Operator: Taylor Aviation INC

The flight

  • Departed from: ABR Aberdeen SD at 12:52 pm
  • Destination: Miles City MT
  • Flight plan: VFR

Weather at the time

  • Light: daylight
  • Wind: from 050° at 11 knots
  • Visibility: 2 statute miles
  • Sky: overcast at 700 ft; ovct at 700 ft
  • Temperature: 54°F (12°C), dew point 52°F (11°C)
  • Altimeter: 29.62 inHg
  • Observation at 2:53 pm from KMLS, 11 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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.