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

Cessna A185F accident near Rushville, Nebraska, September 13, 2010

On September 13, 2010, a Cessna A185F, registered N714AL, was substantially damaged in an accident during takeoff near Rushville, Nebraska (Private Airsttrip airport). It was a personal flight under general aviation rules (Part 91). 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 pilot's failure to maintain directional control of the airplane during takeoff. Contributing to the accident was the loss of visual reference due to the sun glare.

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

What the record shows

Date
September 13, 2010
Place
Rushville, Nebraska · Private Airsttrip · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna A185F · all A185Fs on the register
Registration
N714AL · registry record · serial 18504384
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot was departing to the west from a grass airstrip during the late afternoon. As the airplane crested an upslope in the runway surface, the pilot lost visual reference with the ground due to the sun glare blinding him. The pilot could not maintain directional control and collided into a rut. The landing gear collapsed and the airplane came to rest on its belly, substantially damaging the firewall. The pilot reported no preimpact mechanical malfunctions with the airframe or engine that would have precluded normal operation.

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. Loss of visual reference during takeoff defining event
  2. Loss of control in flight during takeoff
  3. Collision with terrain or object (not controlled flight into terrain) during takeoff

The NTSB's findings

  • factor Environmental issues › Conditions/weather/phenomena › Light condition › Bright light › Effect on personnel
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,400 hours in all; 300 in this make and model
  • Last flight review: January 11, 2009
  • Medical certificate: Class 3 (with waivers/limitations)
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,622 hours
  • Last inspection: annual inspection, May 14, 2010
  • Seats: 6
  • Landing gear: fixed
  • Engine: Cont Motor IO 520 SERIES (piston); 0 hours total

The flight

  • Departed from: N/A Rushville NE
  • Destination: BFF Scottsbluff NE
  • Flight plan: none
  • Runway 27

Weather at the time

  • Light: daylight
  • Sky: clear
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

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.