CACrown ArchivesThe cinema collection
Menu
Research dossier · Places & Architecture

Alaska Airlines Flight 261

fatal aviation accident that occurred on January 31, 2000 over the Pacific Ocean

Architectural plans, a scale model, maps and brass measuring instruments
Places and architectureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionSep 16, 2026
Entity authorityQ770935
Source-derived summary

Alaska Airlines Flight 261 was a scheduled international passenger flight from Licenciado Gustavo Díaz Ordaz International Airport in Puerto Vallarta, Jalisco, Mexico, to Seattle–Tacoma International Airport near Seattle, Washington, United States, with an intermediate stop at San Francisco International Airport in San Francisco, California. On January 31, 2000, the McDonnell Douglas MD-83 operating the flight crashed into the Pacific Ocean roughly 2.7 miles (4.3 km; 2.3 nmi) north of Anacapa Island, California, following a catastrophic loss of pitch control, while attempting to divert to Los Angeles International Airport. The accident killed all 88 on board – two pilots, three cabin crew members, and 83 passengers.

The subsequent investigation by the National Transportation Safety Board (NTSB) determined that inadequate maintenance led to excessive wear and eventual failure of a critical flight control system during flight. The probable cause was stated to be "a loss of airplane pitch control resulting from the in-flight failure of the horizontal stabilizer trim system jackscrew assembly's Acme nut threads." For their efforts to save the plane, both pilots were posthumously awarded the Air Line Pilots Association Gold Medal for Heroism.

Background

Aircraft

The aircraft involved in the accident was a McDonnell Douglas MD-80, serial number 53077, and registered with the tail number N963AS. The MD-83 was a longer-range version of the original MD-80 (an improved version of the DC-9), with higher weight allowances, increased fuel capacity, and more powerful Pratt & Whitney JT8D-219 engines. The aircraft had logged 26,584 flight hours and 14,315 cycles since it was delivered in 1992.

Crew

The pilots of Flight 261 were both highly experienced pilots. Captain Ted Thompson, 53, had accrued 17,750 flight hours, and had more than 4,000 hours experience as pilot-in-command in MD-80s. First Officer William "Bill" Tansky, 57, had accumulated 8,060 hours as first officer on the MD-80.

Editorial summary

The public source identifies “Alaska Airlines Flight 261” as fatal aviation accident that occurred on January 31, 2000 over the Pacific Ocean. This brief keeps that definition visible, then builds a research path around Alaska, Airlines and Flight.

Editorial reviewA strong orientation record where physical form, institutional use and historical geography need to be read together. The current lead gives the account dated anchors—2000, 1992—that can be checked directly. The selected authority fields contribute no independent date. Its value is orientation rather than verdict, with Alaska, Airlines and Flight providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “Alaska Airlines Flight 261”, the useful work is to connect “fatal aviation accident that occurred on January 31, 2000 over the Pacific Ocean” to the records capable of establishing context and consequence.

Evidence profile

The strongest evidence will usually combine a dated visual record with documents produced by the authority responsible for the place. The source revision retrieved here is dated Sep 16, 2026. The linked authority identifier is Q770935. Authority coordinates are 34.058, -119.347. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2000 and 1992.

Critical limits

Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.

Best used for
  • Historic place names
  • Jurisdictional context
  • Routes into maps and plans
Verify next

Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.

Three-step research path

  1. Establish the record: confirm the title “Alaska Airlines Flight 261”, its source revision and the description used here.
  2. Expand the search: follow Alaska Airlines Flight 261 primary sources, Alaska Airlines Flight 261 archive and Alaska research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Alaska Airlines Flight 261”?
  2. What physical evidence or contemporary plan supports the description?
  3. Which earlier names or jurisdictions may reveal additional records?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Alaska Airlines Flight 261” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.