eFlight
Accidents · NTSB CEN13CA129 · Final report

Beech 65-B80 accident near Alexandria, Minnesota, January 11, 2013

On January 11, 2013 at about 2:30 pm local time, a Beech 65-B80, registered N110BA, was substantially damaged in an accident during landing (landing roll) near Alexandria, Minnesota (Alexindria Municipal Airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 1 person was on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot’s failure to stop the airplane on the downsloping, ice-contaminated runway after landing with a tailwind. Contributing to the accident was the pilot’s failure to account for the wind conditions and failure to obtain runway conditions.

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

What the record shows

Date
January 11, 2013 · about 2:30 pm local time · cases in 2013
Place
Alexandria, Minnesota · Alexindria Municipal Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Beech 65-B80 · all 65-B80s on the register
Registration
N110BA · registry record · serial LD-279
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

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

About 35 miles southeast of the destination airport, the pilot obtained the local weather information and requested the instrument landing system approach (ILS) to runway 31. Upon descending to the decision height, the pilot saw the runway end identifier lights and continued the approach. The pilot then saw the visual approach slope indicator lights and the runway lights and decided to land. The airplane touched down about 1,000 feet down the 5,100-foot-long runway. The pilot reported that when the tires came in contact with the runway, the brakes alternately skidded then "grabbed" the runway surface. The pilot decided not to go around and to remain on the runway and attempt to stop the airplane. The airplane traveled into the snow-covered terrain off the departure end of the runway where it contacted an ILS antenna pylon, resulting in substantial damage to the left wing spar. The pilot reported that the downsloping runway was ice covered and that he landed with an approximate 8-knot tailwind. He reported no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation. He also stated he had no prior knowledge of what the braking action on the runway would be.

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. Abnormal runway contact during landing (landing roll)
  2. Runway excursion during landing (landing roll) defining event
  3. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • cause Environmental issues › Physical environment › Runway/land/takeoff/taxi surfa › Snow/slush/ice covered › Effect on operation
  • factor Environmental issues › Physical environment › Runway/land/takeoff/taxi surfa › Snow/slush/ice covered › Awareness of condition
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Effect on operation
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Aircraft capability › Braking capability › Incorrect use/operation

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 4,630 hours in all; 1,200 in this make and model; 91 in the last 90 days; 35 in the last 30 days; 4,085 as pilot in command; 230 on instruments
  • Last flight review: December 26, 2012
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Seats: 9
  • Landing gear: fixed
  • Engine 1: Lycoming IO-720 (piston); 0 hours total
  • Engine 2: (piston); 0 hours total
  • Operator: Bemidji Aviation Services INC

The flight

  • Departed from: MSP Minneapolis MN at 1:12 pm
  • Destination: AXN Alexandria MN
  • Flight plan: IFR
  • Runway 31, 5,100 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 180° at 7 knots
  • Visibility: 1 statute miles
  • Sky: overcast at 200 ft; not recorded
  • Temperature: 34°F (1°C), dew point 34°F (1°C)
  • Altimeter: 29.47 inHg
  • Observation at 2:11 pm from AXN

Injuries

FatalSeriousMinorNone
Flight crew1

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

1 document, released by the NTSB on May 8, 2013. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN13CA129.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.