FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Alaska Airlines Flight 1866

4 Sept 1971 · Alexander Archipelago, Haines Borough, Alaska, United States

Boeing 727 · Controlled flight into terrain due to possible navigational error

From Ted Stevens Anchorage International Airport (ANC) to Seattle–Tacoma International Airport (SEA)

Report a problem

Event

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
Unknown
Event fatalities
111 · all aircraft and ground
Ground fatalities
0
Occupants
111
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
Airline
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

Boeing 727

Flight
AS1866
Aircraft type
Boeing 727
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
N2969G
Onboard fatalities
Unknown
Route
From Ted Stevens Anchorage International Airport (ANC)To Seattle–Tacoma International Airport (SEA)
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 121: Air carrier (scheduled domestic passenger service)
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
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 collision with ground/water
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

  • Miscellaneous › Written cause
  • Pilot in command › Failed to follow approved procedures, directives, etc.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

Alaska Airlines Flight 1866 was a regularly scheduled passenger flight operated by Alaska Airlines from Anchorage, Alaska, to Seattle, Washington, with several intermediate stops in southeast Alaska. The aircraft was a Boeing 727-100 with U.S. registry N2969G manufactured in 1966. On September 4, 1971, the aircraft operating the flight crashed into a mountain in Haines Borough, about 18 miles west of Juneau, Alaska, while on approach for landing. All 111 people aboard were killed. The subsequent investigation found that erroneous navigation readouts led the crew to descend prematurely. No definitive cause for the misleading data was found. It was the first fatal jet aircraft crash involving Alaska Airlines, and remained the deadliest single-aircraft accident in United States history until June 24, 1975, when Eastern Air Lines Flight 66 crashed. It is still, however, the worst air disaster in Alaska state history.

Flight crew

The captain of the flight was Richard C. Adams, age 41. Adams had 13,870 flight hours, including 2,688 hours on the Boeing 727. Piloting the aircraft at the time of the accident was First Officer Leonard D. Beach, age 32. Beach had 5,000 flight hours, with 2,100 of them on the Boeing 727. James J. Carson, age 30, was the Second Officer and had 2,850 flight hours, including about 2,600 hours on the Boeing 727. Beach and Carson were both hired by Alaska Airlines in 1966, and Adams had been with the airline since 1955. The National Transportation Safety Board (NTSB) later determined that all three flight crew members were current and qualified to operate the flight, and there was no evidence of any conditions which would have adversely affected the performance of their duties.

Accident flight

On September 4, 1971, Alaska Airlines Flight 1866 (Air Traffic Control call sign "Alaska 66") was scheduled to depart Anchorage, Alaska (ANC), with intermediate stops in Cordova (CDV), Yakutat (YAK), Juneau (JNU), and Sitka, Alaska (SIT) before continuing to Seattle, Washington (SEA). The flight departed ANC on time at 9:13 a.m. and the first stop at CDV was uneventful, apart from a minor issue with a cargo door which caused a short delay. The aircraft departed CDV at 10:34 and landed at YAK at 11:07. The next leg of the route to JNU, the accident flight, departed YAK at 11:35 a.m. with 104 passengers and 7 crew aboard.

At 11:46 the crew contacted Anchorage air traffic control and reported they were at Flight Level 230 (FL230 or 23,000 feet), 65 mi east of Yakutat. The controller issued a clearance to descend at pilots' discretion to cross the PLEASANT intersection at 10,000 feet, and gave them a clearance limit of HOWARD intersection. The controller then gave them the current altimeter setting at JNU and requested they report passing 11,000 feet in the descent.

At 11:51 the crew informed the controller they were leaving FL230 descending to be level at 10,000 feet at PLEASANT intersection.

At 11:54 the controller instructed the crew to stop their descent at 12,000 feet and changed the clearance limit to PLEASANT intersection where they could expect to hold. They reported level at 12,000 feet less than a minute later. The controller explained that he had to change the clearance due to another aircraft in the airspace near JNU. A Piper PA-23 Apache, N799Y, had departed JNU at 11:44 en route to Whitehorse and had reported in the vicinity of HOWARD intersection. The Piper's altitude was unknown and there was some confusion as to the route it was supposed to be flying. Flight 1866 acted as a communication relay between the controller and N799Y for several transmissions.

At 11:58 the flight reported passing PLEASANT and entering the holding pattern there. The controller acknowledged the report and re-cleared them to HOWARD intersection. He then asked them to confirm they were still level at 12,000 feet and asked if they were "on top" of the clouds at that altitude. The crew replied they were level at 12,000, but in the clouds and "on instruments".

At 12:00, the controller repeated the new clearance limit to hold at HOWARD, and told them they could expect to hold there until 12:10. At 12:01 the crew reported entering the holding pattern at HOWARD at 12,000 feet.

At 12:07, the controller asked for their current location in the holding pattern, and direction from HOWARD. The crew reported they were turning on the inbound leg of the hold, joining the localizer course inbound towards HOWARD. The controller then cleared the flight for the straight-in LDA approach to Runway 8 and instructed them to cross HOWARD inbound at or below 9,000 feet. The crew acknowledged the clearance and reported leaving 12,000 feet. The LDA approach consisted of a localizer providing horizontal guidance to the crew. Vertical guidance was provided by instructions on the approach chart; the procedure involved descending to various published altitudes upon crossing specific intersections between the localizer and a nearby VOR station. The localizer was not equipped with distance measuring equipment at the time of the accident.

At 12:08, the Anchorage controller asked them to report their current altitude and the crew responded, "...leaving five thousand five... four thousand five hundred." The crew was then instructed to contact Juneau Tower. The crew acknowledged the transmission and changed to the tower frequency. The flight checked on to the tower frequency, reporting over BARLOW intersection. The tower controller replied, "Alaska 66, understand...I didn't copy the intersection...," and continued his transmission, giving them the current weather conditions and runway in use, and asked them to report over BARLOW. Part of this transmission was recorded on the CVR of the flight, however the recording ended partway through the transmission. There were no further transmissions from Flight 1866.

At approximately 12:15 the aircraft struck the eastern slope of a canyon in the Chilkat Range of the Tongass National Forest at the 2500 ft level, 18.5 mi west of Juneau. The aircraft exploded on impact. According to the CVR and FDR, there was not even "a last-second awareness" among the crew that a collision with terrain was imminent.

When the crew stopped responding, JNU tower notified local authorities in Juneau, who immediately began a search for the aircraft. A few hours later, the wreckage was located on the eastern slope of the Chilkat ridge, west of Juneau airport at the coordinates. There were no survivors.

Two witnesses in the area of the Chilkat Mountains stated that they heard a low-flying jet aircraft, but could not see it because of clouds and low visibility, which they estimated at 200 – 300 feet. They described the sound of the engines as normal. A short time later they heard an explosion. A third witness in the area saw a low flying plane disappear into the clouds, but did not report hearing any sound.

Investigation and cause

Investigation

The U.S. NTSB investigated the accident. The cockpit voice recorder (CVR) and flight data recorder (FDR) were recovered from the crash site and read out. The wreckage was inspected, and pertinent items were removed for further study by both the NTSB and the various manufacturers. After determining that there were no apparent issues with the crew's qualifications or the aircraft, their investigation focused on the navigational equipment and techniques used for the approach. Both navigation radio receivers on the aircraft were found to be in good working order, and all ground-based navigation stations were likewise operating properly. From the CVR recording it was determined that the crew did not use the audio identification features of the navigation radios. Further, they did not use all available navigational aids to help determine their position, though it is noted that the approach they were performing did not specifically require the use of those facilities. In addition the NTSB found there was potentially a lack of crew coordination between the two pilots in their navigation radio tuning procedures. Based on the crew's conversation and the flight's erroneous position report over BARLOW intersection, the NTSB noted that the captain's navigation radio had apparently presented the crew with consistently false information at several points along the approach path. No reason for the false indications could be determined. The NTSB also found that ATC had used proper procedures in handling Flight 1866. The small aircraft that entered the airspace during their descent might have been a distraction for both the controller and the pilots.

The NTSB Final Report was released on October 11, 1972. The investigation found that the following factors contributed to the accident:

Text from the Wikipedia article “Alaska Airlines Flight 1866” (revision 1373011411, 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 remarks

CREW DIDNT USE ALL NAV AIDS OR IDENTIFY NAV STA.EQUIP-MISLEADING NAV INFO DISPLAY FOR UNDET REASON

NTSB's remark from its 1962–1981 archive, as recorded (abbreviated, at most 98 characters): the archive has no narrative

Sources

Wikipedia article: Alaska Airlines Flight 1866
Article
Alaska Airlines Flight 1866
Revision
1373011411 · 2026-09-03 · retrieved 2026-09-18
Wikidata
Q4708491
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record
Event ID
19710904P038567
Case number
Unknown
Dataset
historical-pre1982
Source SHA-256
abe1a933b4b73583d61684309f7f0610c281e3c1de3537c6471bf2a98ba6481d
Where each value comes from
Record
Wikipedia article "Alaska Airlines Flight 1866" (page 13247932, revision 1373011411); merged with NTSB case NTSB19710904P038567 (PRE1982 tblFirstHalf (one row per aircraft, grouped by date, place and time))
Date
NTSB record NTSB19710904P038567: PRE1982 DATE_OCCURRENCE
Place and country
Wikipedia infobox: site; country from NTSB record NTSB19710904P038567
Map position
Wikipedia: Wikipedia article coordinates
Aircraft, operator and route
NTSB record NTSB19710904P038567: PRE1982 REGIST_NO, ACFT_MAKE, ACFT_MODEL; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record NTSB19710904P038567: operated under Part 121: Air carrier (scheduled domestic passg.svc)
Fatalities
NTSB record NTSB19710904P038567: PRE1982 TOTAL_ABRD_FATAL of each aircraft, plus people on the ground and others outside the aircraft
Ground fatalities
NTSB record NTSB19710904P038567: events.inj_f_grnd
Summary
Wikipedia infobox: summary
Source notes (4)
  • One occurrence in two sources, merged: the Wikipedia article "Alaska Airlines Flight 1866" and NTSB case NTSB19710904P038567, 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.
  • From NTSB's 1962-1981 archive (PRE1982), which holds at most a short remark (98 characters, abbreviated) instead of a narrative; the accident type, phase of flight, causes and conditions are NTSB's codes, decoded as the archive defines them.
  • Reviewed means this record passed the site's consistency check, not that it was checked against a narrative or report - there is none to check against.
  • The operation category is mapped from the archive's operator and operation codes and has not been reviewed.