Alaska Central Express Flight 51
Beech 1900C · Controlled flight into terrain
From King Salmon Airport (PAKN) to Dillingham Airport (PADL)
Event
- NTSB case
- ANC13FA030
- 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
- Event fatalities
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 2
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0 serious · 0 minor (NTSB)
- 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 1900C
- Flight
- AER51
- Aircraft type
- Beechcraft 1900
- 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
- N116AX
- Operator
- Alaska Central Express
- Onboard fatalities
- Unknown
- Route
- From King Salmon Airport (PAKN), King Salmon, AKTo Dillingham Airport (PADL), Dillingham, AK
- Aircraft age
- About 21 years (built 1992)
- 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
- En route · holding (IFR)
- 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
- Controlled flight into terrain/object (CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
From the Wikipedia article
Alaska Central Express Flight 51 was an Alaska Central Express flight from Anchorage to King Salmon and Dillingham, Alaska. On 8 March 2013, the Beechcraft 1900C-1 serving the flight crashed into a mountain on approach to Dillingham Airport, killing both crew members on board.
Accident
The flight had originally taken off from Anchorage International Airport at approximately 5:44 Alaska Standard Time, making a scheduled stop at King Salmon and continuing to Dillingham. En route to Dillingham, the crew requested a RNAV GPS 19 instrument approach, which was granted by the on-duty controller who directed the crew to maintain an altitude at or above 2000 ft. Roughly six minutes later, the crew requested permission to enter into a holding pattern to contact the flight service station for a report on the condition of the runway, which was subsequently granted. The controllers later attempted to contact the aircraft, but were unsuccessful and soon lost radar track of the aircraft, which had crashed at Muklung Hills.
Investigation and cause
Investigation
The accident was investigated by the National Transportation Safety Board (NTSB) who concluded that the plane crashed due to the flight crew's failure to maintain terrain clearance, which resulted in controlled flight into terrain in instrument meteorological conditions.
Text from the Wikipedia article “Alaska Central Express Flight 51” (revision 1361303475, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
Wikipedia article: Alaska Central Express Flight 51
- Revision
- 1361303475 · 2026-06-27 · retrieved 2026-09-18
- Wikidata
- Q24229378
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record ANC13FA030
- Event ID
- 20130308X64149
- Case number
- ANC13FA030
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- Wikipedia article "Alaska Central Express Flight 51" (page 49934131, revision 1361303475); merged with NTSB case ANC13FA030 (events / aircraft)
- Date
- NTSB record ANC13FA030: NTSB narrative opening date, consistent with the API date and time (local date)
- Place and country
- Wikipedia infobox: site; country from NTSB record ANC13FA030
- Map position
- NTSB record ANC13FA030: NTSB API eventLatitude/eventLongitude
- Aircraft, operator and route
- NTSB record ANC13FA030: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record ANC13FA030: operated under Part 135: Air Taxi & Commuter
- Fatalities
- NTSB record ANC13FA030: NTSB API totalFatal
- Ground fatalities
- NTSB record ANC13FA030: events.inj_f_grnd
- Summary
- Wikipedia infobox: summary
Source notes (3)
- One occurrence in two sources, merged: the Wikipedia article "Alaska Central Express Flight 51" and NTSB case ANC13FA030, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- 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.