FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Alaska Central Express Beech 1900C accident

11 Feb 1999 · SAINT MARY'S, AK, United States

Beech 1900C · Accident: in flight collision with terrain/water on approach

From Ted Stevens Anchorage International Airport (ANC) to St Mary's Airport (KSM)

Report a problem

Event

NTSB case
ANC99FA028
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 1900C

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
N31240
Onboard fatalities
Unknown
Route
From Ted Stevens Anchorage International Airport (ANC), Anchorage, AKTo St Mary's Airport (KSM)
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
Approach · IFR final approach
First occurrenceThe 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
In flight collision with terrain/water
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airline transport pilot was cleared for the localizer approach. The airplane impacted the ground 3.2 nautical miles from the runway threshold. The minimum descent altitude (MDA) for the approach was 560 feet msl, which is 263 feet above touchdown. Night, instrument meteorological conditions prevailed at the time of the accident. The surrounding terrain was flat, snow-covered, and featureless. The reported weather was 200 feet overcast, 1 1/2 miles visibility in snow, and winds of 12 knots, gusting to 32 knots. The pilot reported he was established on the final approach course, descending to the MDA, and then woke up in the snow. He said he did not remember any problems with the airplane. No preaccident mechanical anomalies were discovered with the airplane during the investigation. The airport has high intensity runway lights, sequenced flashing lead-in lights, and visual approach slope indicator lights. All airport lights and navigation aids were functioning. The airplane was not equipped with an autopilot. Captains have the option of requesting a copilot, but, the captain's pay is reduced by a portion equal to one-half the copilot's pay. The pilot had returned from the previous nights trip at 0725. He had three rest periods, four hours, two hours, and five hours 15 minutes, since his previous nights flight. Each rest period was interrupted by contact with the company. The company indicated that it is the pilot's responsibility to tell the company if duty times are being exceeded. 14 CFR 135.267 states, in part: '(d) Each assignment ... must provide for at least 10 consecutive hours of rest during the 24 hours that precedes the planned completion of the assignment.'

Probable cause

The pilot's descent below the minimum descent altitude on the instrument approach. Factors were pilot fatigue resulting from the pilot's rest period being interrupted by scheduling discussions and the night weather conditions of low ceilings and whiteout.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC99FA028
Event ID
20001205X00118
Case number
ANC99FA028
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1999-02-12.
  • API snapshot SHA-256: 97f0306f17b34c9989bb7366d091e7845bcde86e22e93d1bfb8080d543c19e10; retrieved 2026-09-18T16:59:24.549Z.