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

Ayres S2R-G6 accident near Esmond, North Dakota, July 17, 2003

On July 17, 2003, a Ayres S2R-G6, registered N3105U, was substantially damaged in an accident near Esmond, North Dakota (Private airport). It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The obstruction of the windshield by the application chemical restricting the pilot's visual lookout, and the pilot's failure to perform an aborted takeoff. Factors contributing to the accident were the leak in the hopper lid and the drainage ditch.

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

What the record shows

Date
July 17, 2003
Place
Esmond, North Dakota · Private · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Ayres S2R-G6
Registration
N3105U · registry record · serial 108
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 agricultural airplane impacted a drainage ditch during takeoff from a private grass airstrip. The pilot reported the spray hopper was jarred during takeoff by a bump in the runway and some mist stuck to the windshield. The pilot stated the mist obstructed his vision and he was unable to distinguish between the grass runway and the soybean fields to either side. The pilot reported the airplane drifted first to the left and then to the right of the crown of the runway before lifting off in ground effect. The pilot reported the airplane landed and skidded sideways into a drainage ditch. The pilot reported he noticed the spray hopper lid was latched during his pre-flight inspection, but it had a tendency to seep" a little around the lid.

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: commercial pilot
  • Ratings: single-engine land
  • Flight time: 2,667 hours in all; 1,060 in this make and model; 200 in the last 90 days; 150 in the last 30 days
  • Last flight review: April 19, 2002
  • Medical certificate: Class 2 (valid medical--no waivers/lim.)
  • Seat: frt
  • Injury: no injuries

The aircraft

  • Last inspection: annual inspection
  • Maximum gross weight: 6,000 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Allied Signal G-6 (turboprop); 0 hours total

The flight

  • Departed from: PVT Esmond ND
  • Flight plan: none
  • Runway 36, 3,900 ft by 40 ft

Weather at the time

  • Light: daylight
  • Wind: from 050° at 15 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 75°F (24°C), dew point 61°F (16°C)
  • Altimeter: 30.11 inHg

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.

Other NTSB records under N3105U the same tail number, which may have belonged to a different aircraft at the time

2008-07-15CHI08CA193 · accident near Kilbourne, IL · substantial damage · no injuries

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.