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

Raytheon Aircraft Company B200 accident near Anchorage, Alaska, October 21, 2017

On October 21, 2017 at about 1:30 pm local time, a 2002 Raytheon Aircraft Company B200, registered N363JH, was substantially damaged in an accident during landing near Anchorage, Alaska (Ted Stevens Anchorage Intl airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

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

What the record shows

Date
October 21, 2017 · about 1:30 pm local time
Place
Anchorage, Alaska · Ted Stevens Anchorage Intl · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Raytheon Aircraft Company B200, built 2002
Registration
N363JH · registry record · serial BB-1799
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

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

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.

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. Miscellaneous/other during prior to flight
  2. Landing gear not configured during landing defining event

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Configuration › Incorrect use/operation
  • factor Personnel issues › Physical › Alertness/Fatigue › (general) › Pilot
  • factor Personnel issues › Psychological › Personality/attitude › Complacency › Pilot

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 23,121 hours in all; 662 in this make and model; 208 in the last 90 days; 58 in the last 30 days; 14,746 as pilot in command
  • Last flight review: April 21, 2017
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,182 hours
  • Last inspection: continuous airworthiness programme, October 4, 2017
  • Maximum gross weight: 12,500 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine 1: Pratt & Whitney Canada PT6A-41 (turboprop); 218 hours total
  • Engine 2: Pratt & Whitney Canada PT6A-41 (turboprop); 218 hours total
  • Operator: Bering Air, Inc.

The flight

  • Departed from: OME Nome AK
  • Destination: ANC Anchorage AK
  • Flight plan: IFR
  • Runway 07R, 12,400 ft by 200 ft

Weather at the time

  • Light: night, dark
  • Wind: from 360° at 7 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 7,500 ft; a few clouds at 5,500 ft
  • Temperature: 23°F (-5°C), dew point 10°F (-12°C)
  • Altimeter: 29.28 inHg
  • Observation at 1:53 pm from PANC, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew3
Passengers1

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

13 documents, released by the NTSB on May 4, 2020. 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.

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.