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

Beech 1900C accident near Aleknagik, Alaska, March 8, 2013

On March 8, 2013 at about 12:15 pm local time, a 1992 Beech 1900C, registered N116AX, was destroyed in an accident near Aleknagik, Alaska (Dillingham Airport). It was flown under charter and air-taxi rules (Part 135). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The flight crew's failure to maintain terrain clearance, which resulted in controlled flight into terrain in instrument meteorological conditions. Contributing to the accident were the flight crew's failure to correctly read back and interpret clearance altitudes issued by the air traffic controller, their failure to adhere to minimum altitudes depicted on the published instrument approach chart, and their failure to adhere to company checklists. Also contributing to the accident were the air traffic controller's issuance of an ambiguous clearance to the flight crew, which resulted in the airplane's premature descent, his failure to address the pilot's incorrect read back of the assigned clearance altitudes, and his failure to monitor the flight and address the altitude violations and issue terrain-based safety alerts.

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

What the record shows

Date
March 8, 2013 · about 12:15 pm local time · cases in 2013
Place
Aleknagik, Alaska · Dillingham Airport · cases near this airport · map
Type
Accident
Injuries
2 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Beech 1900C, built 1992 · all 1900Cs on the register
Registration
N116AX · no longer on the register · serial UC17
Damage
Destroyed
Flight
Flight · charter and air-taxi rules (Part 135)

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

The airplane was operating in instrument meteorological conditions and, as it approached the destination airport, the pilot requested the RNAV/GPS runway 19 approach and asked for routing directly to ZEDAG, the initial approach fix (IAF). At the time of the pilot's request, the airplane was about 30 miles southeast of the IAF at an altitude of about 5,900 feet mean sea level (msl). The air traffic controller cleared the airplane to fly directly to the IAF followed by the ZEDAG transition and the RNAV/GPS runway 19 approach, stating, "maintain at or above 2,000" feet until established on a published segment of the approach. The flight crewmembers repeated the clearance back to the controller as "maintain 2,000" feet until established, and they began descending the airplane toward the IAF. About 6 minutes later, the pilot requested to enter the holding pattern while they checked on runway conditions on another radio frequency, and the controller cleared them to hold "as published." At the time of the pilot's request, the airplane was at an altitude of about 2,200 feet msl. As depicted on the published instrument approach procedure, the terminal arrival area (TAA) minimum altitude when approaching the IAF from the southeast (the direction from which the accident flight approached) is 5,400 feet msl, and the published holding pattern at the IAF is 4,300 feet msl due to rising terrain in the area.Therefore, the flight crewmember's acceptance of what they believed to be a clearance to 2,000 feet, their descent to that altitude, and their initiation of a hold at that altitude indicates a lack of awareness of the information contained on the published procedure. Such a lack of awareness is inconsistent with pilot-in-command responsibilities and company procedures that require an instrument approach briefing during the descent and approach phases of flight. If the flight crewmembers had reviewed the published approach procedure and briefed it per the company's descent and approach checklist, they should have noticed that the minimum safe altitude in the TAA southeast of the IAF was 5,400 feet msl and that the minimum altitude for the hold was 4,300 feet msl. Examination of the wreckage and debris path evidence is consistent with the airplane having collided with rising terrain at 2,000 feet msl while flying in a wings-level attitude on the outbound leg of the holding pattern, which the flight crew should have flown at 4,300 feet msl. However, the air traffic controller did not adhere to guidance contained in Federal Aviation Administration Order 7110.65, and his approach clearance to "maintain at or above 2,000 feet" msl until established on a published segment of the approach was ambiguous. The controller's approach clearance should have instructed the pilot to "proceed direct to ZEDAG, enter the TAA at or above 5,400 feet, cleared RNAV runway 19 approach." Instead, he instructed the pilot without specifying the segment of the approach that should be flown at 2,000 feet. Further, the controller did not notice the pilot's incorrect readback of the clearance in which he indicated that he intended to "maintain 2,000 feet" until established on the approach. Further, he did not appropriately monitor the flight's progress and intervene when the airplane descended to 2,000 feet msl. As a result, the airplane was permitted to descend below the minimum instrument altitudes applicable to the route of flight and enter the holding pattern well below the published minimum holding altitude. Air traffic control (ATC) recorded automation data showed that the airplane's trajectory generated aural and visual minimum safe altitude warnings on the controller's radar display. However, the controller did not issue any terrain warnings or climb instructions to the flight crew. The controller said that he was not consciously aware of any such warnings from his display. These automated warnings should have been sufficient to prompt the controller to evaluate the airplane's position and altitude, provide a safety alert to the pilot in a timely manner, and instruct the pilot to climb to a safe altitude; it could not be determined why the controller was unaware of the warnings. The airplane was equipped with three pieces of navigation equipment that should have provided visual and aural terrain warnings to the flight crewmembers if they had not inhibited the function and if the units were operating properly. Damage precluded testing the equipment or determining the preaccident configuration of the units; however, the flight crew reported no equipment anomalies predeparture.

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. Enroute-holding (IFR) Controlled flight into terrain or object (CFIT) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Flight crew
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › ATC personnel
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Contributed to outcome

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 5,770 hours in all; 5,470 in this make and model; 390 in the last 90 days; 116 in the last 30 days; 1,820 as pilot in command
  • Last flight review: October 20, 2012
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

Co-pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 470 hours in all; 250 in this make and model; 250 in the last 90 days; 80 in the last 30 days; 90 as pilot in command
  • Last flight review: December 1, 2012
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: fatal

The aircraft

  • Airframe total time: 29,824 hours
  • Last inspection: continuous airworthiness programme, March 7, 2013; 188 hours since
  • Maximum gross weight: 17,600 lb
  • Seats: 19
  • Landing gear: retractable
  • Engine 1: Pratt&Whitney PT6A-65B (turboprop); 42,555 hours total
  • Engine 2: Pratt Whittney PT6A-65b (turboprop); 2,566 hours total
  • Operator: Alaska Central Express INC

The flight

  • Departed from: PAKN King Salmon AK at 11:50 am
  • Destination: PADL Dillingham AK
  • Flight plan: IFR
  • Runway 19, 6,400 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 100° at 17 knots, gusting 30
  • Visibility: 7 statute miles
  • Sky: overcast at 1,500 ft
  • Temperature: 34°F (1°C), dew point 34°F (1°C)
  • Altimeter: 29.09 inHg
  • Observation at 11:45 am from PADL, 20 miles away

Injuries

FatalSeriousMinorNone
Flight crew2

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

38 documents, released by the NTSB on August 11, 2014. 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.

#DocumentWhat it is
1 Operations - Factual Report of Group Chairman PDF, 12 pages View Download
2 Operations - Attachment 1 - Captain Master Training Records PDF, 15 pages View Download
3 Operations - Attachment 2 - Captain Check Ride Form PDF, 2 pages View Download
4 Operations - Attachment 3 - Captain Flight and Duty Records PDF, 4 pages View Download
5 Operations - Attachment 4 - F/o Master Training Records PDF, 7 pages View Download
6 Operations - Attachment 5 - F/o Check Ride Form PDF, 2 pages View Download
7 Operations - Attachment 6 - F/o Flight and Duty Records PDF, 4 pages View Download
8 Operations - Attachment 7 - Gom Chapter 4, Page 4-1 PDF, 2 pages View Download
9 Operations - Attachment 8 - Ops Spec Paragraph A008 PDF, 7 pages View Download
10 Photo 1. Annotated Image, Arial View of the Debris Field. PDF, 1 page View Download
11 Photo 2. Annotated Image of the Debris Field from the Point of Impact. PDF, 1 page View Download
12 Photo 3. Major Wreckage Components. PDF, 1 page View Download
13 Photo 4. Aircraft Cockpit PDF, 1 page View Download
14 ATC 3 - Factual Report of Group Chairman PDF, 23 pages View Download
15 ATC 3 - FAA Accident Package PDF, 66 pages View Download
16 ATC 3 - Anchorage Center "Lessons Learned" Briefing PDF, 14 pages View Download
17 ATC 3 - Anchorage Center Aural Alarm Default Values PDF, 1 page View Download
18 ATC 3 - FAA Msaw Adaptation Briefing PDF, 23 pages View Download
19 ATC 3 - Aural Alarm Records Sector 13 PDF, 1 page View Download
20 ATC 3 - radar Data AER51 text file View Download
21 ATC 3 - Performance Record of Conference - Wicks/zimmermann PDF, 2 pages View Download
22 ATC 3 - Initial Facility Briefing on Accident PDF, 7 pages View Download
23 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 9 pages View Download
24 Maps or Charts of Accident Area PDF, 1 page View Download
25 Topo Chart PDF, 1 page View Download
26 Anchorage Center SOP PDF, 108 pages View Download
27 Cockpit Checklist PDF, 1 page View Download
28 Terrain Warning Equipment Email PDF, 1 page View Download
29 Annotated Instrument Approach Diagram PDF, 1 page View Download
30 Initial Approach Point Chart PDF, 1 page View Download
31 3D View of Approach Holding Area PDF, 1 page View Download
32 Ace Aircraft Checklist PDF, 2 pages View Download
33 2D PIC Showing radar Contact Lost PDF, 1 page View Download
34 3D PIC of radar Contact Lost PDF, 1 page View Download
35 Statement of Party Representatives to NTSB Investigation PDF, 1 page View Download
36 Statement of Party Representatives to NTSB Investigation PDF, 1 page View Download
37 Toxicological Report PDF, 1 page View Download
38 Toxicological Report PDF, 1 page View Download

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/ANC13FA030.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.