Bering Air Raytheon Aircraft Company B200 accident
Raytheon Aircraft Company B200 · Accident: landing gear not configured
From Nome Airport (OME) to Ted Stevens Anchorage International Airport (ANC)
Event
- NTSB case
- ANC18LA005
- 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
- Unknown
- 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
- Visual Meteorological Cond
Raytheon Aircraft Company B200
- Aircraft type
- Beechcraft 200
- 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
- N363JH
- Operator
- Bering Air
- Onboard fatalities
- Unknown
- Route
- From Nome Airport (OME), Nome, AKTo Ted Stevens Anchorage International Airport (ANC), Anchorage, AK
- Aircraft age
- About 15 years (built 2002)
- 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
- 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
- Landing gear not configured
- 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
- 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
The pilot was conducting an air medical flight during early morning hours in dark night visual meteorological conditions and was flying an instrument approach to the destination airport. A review of air traffic control communications found that during the instrument approach, the pilot gave an incorrect readback twice to the terminal radar approach controller and flew through the approach course. The pilot reported that, before landing, he failed to visually check and confirm indications that the landing gear were down and locked; he also did not respond to warning tones that should have sounded to indicate this condition during the latter stages of the approach. Upon touchdown on the runway with the landing gear not extended, the airplane skidded on the underside of the fuselage and came to rest on the runway.
The airplane sustained substantial damage to the right engine mount. Although the landing gear switch was found in the down position, it could not be determined when it was placed in that position.
Evidence indicates that the accident occurred during the window of circadian low, and the pilot's sleep periods were fragmented in the days before the accident and he did not have a contiguous 8 hours of sleep that was typical of his sleep pattern when not working overnight periods; both of these factors likely contributed to the pilot being fatigued about the time of the accident. The pilot reported that he felt the effects of fatigue, including impaired judgment, as he approached the destination airport. The pilot's readback errors and his failure to extend the landing gear are consistent with performance degradation due to fatigue. The pilot cited being on a long duty period, failing to manage his rest, failing to manage the cockpit, and allowing complacency to set in as factors that affected his performance.
Probable cause
The pilot's failure to extend the landing gear before landing, which resulted in a gear-up landing. Contributing to the accident was the pilot's fatigue and complacency.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC18LA005
- Event ID
- 20171022X15558
- Case number
- ANC18LA005
- 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: d147022973e4dc168ebf972c49ca87a818dfb5832cdd78b7c9ebae0349207545; retrieved 2026-09-16T05:57:07.366Z.