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

Ayres S2R-G10 accident near Stanfield, Arizona, August 24, 1999

On August 24, 1999 at about 8:30 am local time, a Ayres S2R-G10, registered N20523, was substantially damaged in an accident near Stanfield, Arizona (AG Airstrip airport). It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's delay in aborting the takeoff after noting sluggish acceleration during the takeoff roll, which resulted in a runway overrun.

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

What the record shows

Date
August 24, 1999 · about 8:30 am local time
Place
Stanfield, Arizona · AG Airstrip
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Ayres S2R-G10
Registration
N20523 · registry record · serial G10-147
Damage
Substantial damage
Flight
Aerial application (crop spraying) flight · agricultural flying rules (Part 137)

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

The pilot said that the engine temperature reached red line earlier than usual during the takeoff ground roll on the 2,200-foot-long runway, and that he reduced the throttle somewhat to keep from exceeding takeoff limitations. He reported that the acceleration seemed sluggish and the airplane overran the runway end and collided with a berm. The pilot reported that the airplane was becoming airborne right at the time of impact. Three ground crewmembers that witnessed the accident reported that they didn't notice any unusual noises from the engine, but they noted that it seemed like a 'slow acceleration.' The pilot stated that he had not experienced any mechanical problems with the aircraft prior to the accident, and reported that the engine sounded normal during the takeoff roll. He further reported that the accident could have been prevented by taking off with a lighter load.

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

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: glider; instrument: airplane; rotorcraft: glider
  • Flight time: 7,600 hours in all; 600 in this make and model; 300 in the last 90 days; 100 in the last 30 days; 7,380 as pilot in command
  • Medical certificate: Class 2 (valid medical--no waivers/lim.)
  • Seat: ctr

The aircraft

  • Airframe total time: 674 hours
  • Last inspection: 100-hour inspection, August 6, 1999; 68 hours since
  • Maximum gross weight: 6,000 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Garrett TPE331-10 (turboprop); 0 hours total

The flight

  • Flight plan: none
  • Runway 36, 2,200 ft by 80 ft

Weather at the time

  • Light: night, bright
  • Wind: from 050° at 6 knots
  • Visibility: 10 statute miles
  • Sky: not recorded; clear
  • Temperature: 90°F (32°C), dew point 55°F (13°C)
  • Altimeter: 29.00 inHg
  • Observation at 8:55 am from CGZ, 13 miles away

Injuries

FatalSeriousMinorNone
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.