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

Cessna R182 accident near Cooperstown, North Dakota, June 9, 2006

On June 9, 2006 at about 4:50 pm local time, a Cessna R182, registered N3360C, was substantially damaged in an accident near Cooperstown, North Dakota. It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's inability to gain sufficient altitude during the aborted landing. Factors associated with the accident were the tailwind, the pilot's selection of the runway used, the wet runway, the roadway, and the corn crop.

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

What the record shows

Date
June 9, 2006 · about 4:50 pm local time
Place
Cooperstown, North Dakota · map
Type
Accident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna R182 · all R182s on the register
Registration
N3360C · no longer on the register · serial R18200276
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The landing gear contacted a road during an aborted landing. The pilot reported that he made a normal crosswind landing on the first third of runway 31. He reported the runway was wet from recent rains and the airplane did not decelerate as he expected. He decided to perform an aborted landing when he determined the airplane was not going to stop on the remaining runway. He reported that he added full power and the airplane crossed the end of the runway at an altitude of about five feet above the ground. The pilot reported that almost immediately after crossing the end of the runway, he heard a sharp noise and determined the airplane had struck a road which was approximately 15 feet above the runway elevation. He reported he raised the landing gear and the airplane banked to the left which he corrected by applying aileron. The pilot reported that the airplane then slid to a stop in a cornfield. The winds reported at Jamestown, North Dakota, 49 miles from the accident airport, were from 090 degrees at 18 knots gusting to 23 knots.

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: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,129 hours in all; 401 in this make and model; 16 in the last 90 days; 13 in the last 30 days; 989 as pilot in command
  • Medical certificate: Class 3

The aircraft

  • Landing gear: retractable
  • Engine: Lycoming O-540-J3C5D (piston); 0 hours total

The flight

  • Departed from: RST Rochester MN at 2:40 pm
  • Destination: S32 Cooperstown ND
  • Flight plan: IFR

Weather at the time

  • Light: daylight
  • Wind: from 090° at 18 knots, gusting 23
  • Visibility: 10 statute miles
  • Sky: overcast at 7,500 ft
  • Temperature: 57°F (14°C), dew point 55°F (13°C)
  • Altimeter: 30.03 inHg
  • Observation at 11:56 am from JMS

Injuries

FatalSeriousMinorNone
Crew1
Passengers2

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.