FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 24 · Embraer 120ER

16 Oct 2001 · Bethel, AK, United States

Embraer 120ER · Accident: in flight collision with terrain/water on approach

From Ted Stevens Anchorage International Airport (PANC) to Bethel Airport (PABE)

Report a problem

Event

NTSB case
ANC02LA002
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
Instrument Meteorological Cond

Embraer 120ER

Aircraft type
Embraer 120
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
N120AX
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ted Stevens Anchorage International Airport (PANC), Anchorage, AKTo Bethel Airport (PABE), Bethel, AK
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

  • Pilot in command › Minimum descent altitude, continued below

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The captain and first officer were conducting a localizer DME back course approach to runway 36 in a twin-engine turboprop airplane during a night cargo flight under IFR conditions. The minimum visibility for the approach was one mile, and the minimum descent altitude (MDA) was 460 feet msl (338 feet agl). Prior to leaving their cruise altitude, the first officer listened to the ATIS information which included an altimeter setting of 29.30 inHg. No other altimeter information was received until the crew reported they were inbound on the approach. At that time, tower personnel told the crew that the visibility was one mile in light snow, the wind was from 040 degrees at 22 knots, and the altimeter setting was 29.22 inHg. The crew did not reset the airplane altimeters from 29.30 to 29.22. At the final approach fix (5 miles from the runway), the captain began a descent to the MDA. Thirty-six seconds before impact, the first officer cautioned the captain about the airplane's high airspeed. Due to strong crosswinds, the captain disconnected the autopilot 22 seconds before impact. He said he pushed the altitude hold feature on the flight director at the MDA. Eighteen seconds before impact, the airplane leveled off about 471 feet indicated altitude, but then descended again 9 seconds later. The descent continued until the airplane collided with the ground, 3.5 miles from the runway. The crew said that neither the airport, or the snow-covered terrain, was observed before impact. The crew reported that the landing lights were off. The airplane was not equipped with a ground proximity warning system.

Probable cause

The captain's continued descent below the minimum descent altitude which resulted in impact with terrain during an instrument landing approach. Factors contributing to the accident were the flightcrew's failure to reset the altimeters to the correct altimeter setting, and meteorological conditions consisting of snow obscuration that limited visibility, and the ambient night light conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC02LA002
Event ID
20011217X02401
Case number
ANC02LA002
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2001-10-17.
  • API snapshot SHA-256: 9f02537e9672aed6c56da78cb4a65ea21a0814e960ea67e4b408d4d5244df7d0; retrieved 2026-09-18T16:08:50.608Z.