Bemidji Aviation Services Beech 65-B80 accident
Beech 65-B80 · Accident: runway excursion during landing
From Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP) to Chandler Field (AXN)
Event
- NTSB case
- CEN13CA129
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Beech 65-B80
- Aircraft type
- Beechcraft 65
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N110BA
- Operator
- Bemidji Aviation Services
- Onboard fatalities
- Unknown
- Route
- From Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP), Minneapolis, MNTo Chandler Field (AXN), Alexandria, MN
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 135: Air Taxi & Commuter
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13CA129
- Event ID
- 20130111X94242
- Case number
- CEN13CA129
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: e19769b1f54c1e916893786448f23755d77ed2f42b224a9a26ebe81f7bc72758; retrieved 2026-09-15T20:44:17.409Z.