Alaska Airlines Flight 261

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Alaska Airlines Flight 261
N958AS MD-83 Alaska Al YVR 24AUG05 (6920119895).jpg
N958AS, an Alaska Airlines MD-83
similar to the accident aircraft
DateJanuary 31, 2000 (2000-01-31)
SummaryLoss of control caused by jackscrew failure due to improper maintenance[1]
SitePacific Ocean
near Anacapa Island, California, U.S.
34°03.5′N 119°20.8′W / 34.0583°N 119.3467°W / 34.0583; -119.3467Coordinates: 34°03.5′N 119°20.8′W / 34.0583°N 119.3467°W / 34.0583; -119.3467
Aircraft typeMcDonnell Douglas MD-83
OperatorAlaska Airlines
IATA flight No.AS261
ICAO flight No.ASA261
Call signALASKA 261
Flight originLicenciado Gustavo Díaz Ordaz International Airport
StopoverSan Francisco Int'l Airport
DestinationSeattle–Tacoma Int'l Airport

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 in Seattle, Washington, United States, with an intermediate stop at San Francisco International Airport in San Francisco, California.[1]:xii On January 31, 2000, the aircraft operating the route, a McDonnell Douglas MD-83, 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. 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 trapezoidal nut threads. The thread failure was caused by excessive wear resulting from Alaska Airlines' insufficient lubrication of the jackscrew assembly."[1]:xii



The aircraft involved in the accident was a McDonnell-Douglas MD-83, serial number 53077, and registered as N963AS. The aircraft was manufactured and delivered new to Alaska Airlines in 1992 and had logged 26,584 flight hours and 14,315 cycles before the crash.[2][3]


The pilots of Flight 261 were both highly experienced aviators.[4] Captain Edward (Ted) Thompson, 53, had accrued 17,750 flight hours, and had more than 4,000 hours experience flying MD-80s.[1]:10–11 First Officer William (Bill) Tansky, 57, had accumulated 8,140 total flight hours, including about 8,060 hours as first officer in the MD-80.[1]:11 Neither pilot had been involved in an accident or incident prior to the crash.[1] There were three Seattle-based flight attendants on board.[5]


The three flight attendants and 47 of the passengers on board the plane were bound for Seattle.[6] 32 passengers were traveling to San Francisco; three were bound for Eugene, Oregon; and three passengers were headed for Fairbanks, Alaska.[7] Of the passengers, one was Mexican and one was British, with all others being American citizens.[8]

At least 35 occupants of Flight 261 were connected in some manner with Alaska Airlines or its sister carrier Horizon Air, including twelve actual employees,[9] leading many of the airlines' personnel to mourn for those lost in the crash.[10] Alaska Airlines stated that it was commonplace, on less busy flights, for employees to fill seats that would otherwise have been left empty. Bouquets of flowers started arriving at the company's headquarters in SeaTac, Washington, the day after the crash.[11]

Accident flight[edit]

Initial flight segment[edit]

Final flight path of Alaska 261

Alaska 261 departed from Puerto Vallarta at 13:37 PST (21:37 UTC), and climbed to its intended cruising altitude of flight level 310 (31,000 feet or 9,400 meters). The plane was scheduled to land at San Francisco International Airport. Some time before 15:49 (23:49 UTC), the flight crew contacted the airline's dispatch and maintenance control facilities in SeaTac, Washington, on a company radio frequency shared with operations and maintenance facilities at Los Angeles International Airport (LAX), to discuss a jammed horizontal stabilizer and a possible diversion to LAX.[1] The jammed stabilizer prevented operation of the trim system, which would normally make slight adjustments to the flight control surfaces to keep the plane stable in flight. At their cruising altitude and speed, the position of the jammed stabilizer required the pilots to pull on their yokes with approximately 10 pounds (44 N) of force to keep level.[1] Neither the flight crew, nor company maintenance, could determine the cause of the jam.[1] Repeated attempts to overcome the jam with the primary and alternate trim systems were unsuccessful.[1]

During this time, the flight crew had several discussions with the company dispatcher about whether to divert to Los Angeles, or continue on as planned to San Francisco. Ultimately the pilots chose to divert.[1] Later, the NTSB found that while "the flight crew's decision to divert the flight to Los Angeles [...] was prudent and appropriate", "Alaska Airlines dispatch personnel appear to have attempted to influence the flight crew to continue to San Francisco [...] instead of diverting to Los Angeles".[1]:137 Cockpit voice recorder (CVR) transcripts indicate that the dispatcher was concerned about the effect on the schedule ("flow"), should the flight divert.[1]:195–197

First dive and recovery[edit]

Video of path of flight

At 16:09 (00:09 UTC), the flight crew successfully unjammed the horizontal stabilizer with the primary trim system. However, upon being freed, it quickly moved to an extreme "nose-down" position, forcing the aircraft into an almost vertical nosedive. The plane dropped from about 31,500 ft (9,600 m) to between 23,000 and 24,000 ft (7,000 and 7,300 m) in around 80 seconds.[1] Both pilots struggled together to regain control of the aircraft, and only by pulling with 130 to 140 pounds (580 to 620 N) on the controls did the flight crew stop the 6,000 ft/min (1,800 m/min) descent of the aircraft and stabilize the MD-83 at approximately 24,400 ft (7,400 m).[1]

Alaska 261 informed air traffic control of their control problems. After the flight crew stated their intention to land at LAX, ATC asked whether they wanted to proceed to a lower altitude in preparation for approach.[1] The captain replied: "I need to get down to about ten, change my configuration, make sure I can control the jet and I'd like to do that out here over the bay if I may".[1]:8 Later, during the public hearings into the accident, the request by the pilot not to overfly populated areas was mentioned.[12]:6–9 During this time, the flight crew considered, and rejected, any further attempts to correct the runaway trim. They descended to a lower altitude and started to configure the aircraft for landing at LAX.[1]

Second dive and crash[edit]

Video of jackscrew failure sequence
ATC audio before crash

Beginning at 16:19 (00:19 UTC), the CVR recorded the sounds of at least four distinct "thumps" followed 17 seconds later by an "extremely loud noise", as the overstrained jackscrew assembly failed completely and the jackscrew separated from the acme nut holding it in place. As a result, the vertical stabilizer failed, and the aircraft rapidly pitched over into a dive.[1] The crippled aircraft had been given a block altitude,[13] and several aircraft in the vicinity had been alerted by ATC to maintain visual contact with the stricken jet. These immediately contacted the controller;[14] one pilot radioed: "that plane has just started to do a big huge plunge"; another reported: "Yes sir, ah, I concur he is, uh, definitely in a nose down, uh, position descending quite rapidly."[14] ATC then tried to contact the plane. The crew of a SkyWest airliner reported: "He's, uh, definitely out of control."[14] Although the CVR captured the co-pilot saying "mayday", no radio communications were received from the flight crew during the final event.[1]:9[14]

The CVR transcript reveals the pilots' continuous attempts for the duration of the dive to regain control of the aircraft.[1]:9 At one point, unable to raise the nose, they attempted to fly the aircraft upside-down in an effort to maintain control.[1] However, the aircraft was far beyond recovery; it descended inverted and nose-down about 18,000 feet (5,500 m) in 81 seconds (151 mph; 243 km/h). A few seconds before 16:22 (00:22 UTC), Flight 261 impacted the Pacific Ocean at high speed about 14 miles (23 kilometers; 12 nautical miles) offshore, between the coastal city of Port Hueneme, California, and Anacapa Island. At this time, pilots from aircraft flying in the same area reported in, with one SkyWest Airlines pilot saying: "and he's just hit the water". Another reported: "Ah, yes sir he ah, he ah, hit the water. He's ah down."[14][15] The aircraft was destroyed by the impact forces, and all occupants on board were killed by blunt force impact trauma.[1]


Wreckage recovery and analysis[edit]

Recovered jackscrew – the spiral "wire" wrapped around the threaded portion is the remnants of the internal screw thread stripped from the acme nut
Deepak Joshi (left) of the NTSB and John Scarola of Alaska Airlines prepare the Flight Data Recorder for transport from the MV Kellie Chouest on Feb 3, 2000

Using side-scan sonar, remotely operated vehicles, and a commercial fishing trawler, workers recovered about 85% of the fuselage (including the tail section) and a majority of the wing components. [16] In addition, both engines, as well as the flight data recorder (FDR) and CVR were retrieved. All wreckage recovered from the crash site was unloaded at the Seabee's Naval Construction Battalion Center Port Hueneme, California, for examination and documentation by NTSB investigators.[1] Both the horizontal stabilizer trim system jackscrew (also referred to as "acme screw") and the corresponding acme nut, which the jackscrew turns through, were found. The jackscrew was constructed from case-hardened steel and is 22 inches (56 cm) long and 1.5 inches (3.8 cm) in diameter.[1][17] The acme nut was constructed from a softer copper alloy containing aluminum, nickel, and bronze.[17][1] As the jackscrew rotates, it moves up or down through the (fixed) acme nut, and this linear motion moves the horizontal stabilizer for the trim system. Upon subsequent examination, the jackscrew was found to have metallic filaments wrapped around it, which were later determined to be the remains of the acme-nut thread.[1]

Later analysis estimated that 90% of the thread in the acme nut had already worn away previously, and that it had finally stripped out during the flight while en route to San Francisco. Once the thread had failed, the horizontal stabilizer assembly was then subjected to aerodynamic forces that it was not designed to withstand, leading to complete failure of the overstressed stabilizer assembly.[1] Based on the time since the last inspection of the jackscrew assembly, the NTSB determined that the acme-nut thread had deteriorated at 0.012 inches (0.30 mm) per 1000 flight‑hours, much faster than the expected wear of 0.001 inches (0.025 mm) per 1000 flight‑hours.[1] Over the course of the investigation, the NTSB considered a number of potential reasons for the substantial amount of deterioration of the nut thread on the jackscrew assembly, including the substitution by Alaska Airlines (with the approval of the aircraft manufacturer McDonnell Douglas) of Aeroshell 33 grease instead of the previously approved lubricant, Mobilgrease 28. The use of Aeroshell 33 was found not to be a factor in this accident.[1] Insufficient lubrication of the components was also considered as a reason for the wear. Examination of the jackscrew and acme nut revealed that no effective lubrication was present on these components at the time of the accident.[18] Ultimately, the lack of lubrication of the acme-nut thread and the resultant excessive wear were determined to be the direct causes of the accident.[1]

Identification of passengers[edit]

Due to the extreme impact forces and subsequent loss of any occupiable space within the passenger cabin, only a few bodies were found intact,[4] and none were visually identifiable. All occupants were identified using fingerprints, dental records, tattoos, personal items, and anthropological examination.[19]

Inadequate lubrication and end-play checks[edit]

The investigation then proceeded to examine why scheduled maintenance had failed to adequately lubricate the jackscrew assembly. In interviews with the Alaska Airlines mechanic at San Francisco International Airport (SFO) who last performed the lubrication it was revealed that the task took about one hour, whereas the aircraft manufacturer estimated the task should take four hours.[1] This and other evidence suggested to the NTSB that "the SFO mechanic who was responsible for lubricating the jackscrew assembly in September 1999 did not adequately perform the task".[1] Laboratory tests indicated that the excessive wear of jackscrew assembly could not have accumulated in just the four-month period between the September 1999 maintenance and the accident flight.[1] Therefore, the NTSB concluded that "more than just the last lubrication was missed or inadequately performed".[1]

A periodic maintenance inspection called an "end-play check" was used to monitor wear on the jackscrew assembly. The NTSB examined why the last end-play check on the accident aircraft in September 1997 did not uncover excessive wear. The investigation found that Alaska Airlines had fabricated tools to be used in the end-play check that did not meet the manufacturer's requirements.[1] Testing revealed that the non-standard tools ("restraining fixtures") used by Alaska Airlines could result in inaccurate measurements, and that it was possible that if accurate measurements had been obtained at the time of the last inspection, these measurements would have indicated the excessive wear and the need to replace the affected components.[1]

Extension of maintenance intervals[edit]

Between 1985 and 1996, Alaska Airlines progressively increased the period in between both jackscrew lubrication and end-play checks, with the approval of the Federal Aviation Administration (FAA).[1] Since each lubrication or end-play check subsequently not conducted had represented an opportunity to adequately lubricate the jackscrew or detect excessive wear, the NTSB examined the justification of these extensions. In the case of extended lubrication intervals, the investigation could not determine what information, if any, was presented by Alaska Airlines to the FAA prior to 1996.[1] Testimony from an FAA inspector regarding an extension granted in 1996 was that Alaska Airlines submitted documentation from McDonnell Douglas as justification for their extension.[1]

End-play checks were conducted during a periodic comprehensive airframe overhaul process called a C‑check. Testimony from the director of reliability and maintenance programs of Alaska Airlines was that a data-analysis package based on the maintenance history of five sample aircraft was submitted to the FAA to justify the extended period between C-checks. Individual maintenance tasks (such as the end-play check) were not separately considered in this extension.[1] The NTSB found that "Alaska Airlines' end play check interval extension should have been, but was not, supported by adequate technical data to demonstrate that the extension would not present a potential hazard".[1]

FAA oversight[edit]

A special inspection conducted by the NTSB in April 2000 of Alaska Airlines uncovered widespread significant deficiencies that "the FAA should have uncovered earlier".[1] The investigation concluded that "FAA surveillance of Alaska Airlines had been deficient for at least several years".[1] The NTSB noted that in July 2001, an FAA panel determined that Alaska Airlines had corrected the previously identified deficiencies. However, several factors led the Board to question "the depth and effectiveness of Alaska Airlines corrective actions" and "the overall adequacy of Alaska Airlines' maintenance program".[1]

Systemic problems were identified by the investigation in the FAA's oversight of maintenance programs, including inadequate staffing, its approval process of maintenance interval extensions, and the aircraft certification requirements.[1]

Aircraft design and certification issues[edit]

The jackscrew assembly was designed with two independent threads, each of which was strong enough to withstand the forces placed on it.[1] Maintenance procedures such as lubrication and end-play checks were to catch any excessive wear before it progressed to a point of failure of the system. The aircraft designers assumed that at least one set of threads would always be present to carry the loads placed on it, therefore the effects of catastrophic failure of this system were not considered, and no "fail-safe" provisions were needed.

For this design component to be approved ("certified") by the FAA without any fail-safe provision, a failure had to be considered "extremely improbable". This was defined as "having a probability on the order of 1×10−9 or less each flight hour".[1] The accident showed that certain wear mechanisms could affect both sets of threads, and that the wear might not be detected. The NTSB determined that the design of "the horizontal stabilizer jackscrew assembly did not account for the loss of the acme nut threads as a catastrophic single-point failure mode".[1]

Jackscrew design improvement[edit]

In 2001, NASA recognized the risk to its hardware (such as the Space Shuttle) attendant upon use of similar jackscrews. An engineering fix developed by engineers of NASA and United Space Alliance promises to make progressive failures easy to see and thus complete failures of a jackscrew less likely.[20]

John Liotine[edit]

In 1998, an Alaska Airlines mechanic named John Liotine, who worked in the Alaska Airlines maintenance center in Oakland, California, told the Federal Aviation Administration that supervisors were approving records of maintenance that they were not allowed to approve or that indicated work had been completed when, in fact, it had not. Liotine began working with federal investigators by secretly audio recording his supervisors. On December 22, 1998, federal authorities raided an Alaska Airlines property and seized maintenance records. In August 1999, Alaska Airlines put Liotine on paid leave,[21] and in 2000, Liotine filed a libel suit against the airline. The crash of AS261 became a part of the federal investigation against Alaska Airlines because in 1997, Liotine had recommended that the jackscrew and gimbal nut of the accident aircraft be replaced, but had been overruled by another supervisor.[22] In December 2001, federal prosecutors stated that they were not going to file criminal charges against Alaska Airlines. Around that time, Alaska Airlines agreed to settle the libel suit by paying about $500,000; as part of the settlement, Liotine resigned.[21]


In addition to the probable cause, the NTSB found the following contributing factors:[1]

  • Alaska Airlines' extension of its lubrication interval for its McDonnell Douglas MD-80 horizontal stabilizer components, and the FAA's approval of that extension, the last of which was based on McDonnell Douglas's extension of the recommended lubrication interval, increased the likelihood that a missed or inadequate lubrication would result in the near complete deterioration of the jackscrew-assembly acme-nut threads and, therefore, was a direct cause of the excessive wear and contributed to the Alaska Airlines Flight 261 accident.
  • Alaska Airlines's extended end-play check interval and the FAA's approval of that extension, which allowed the acme-nut threads to deteriorate to the point of failure without the opportunity for detection.
  • The absence on the McDonnell Douglas MD-80 of a fail-safe mechanism to prevent the catastrophic effects of total acme nut loss.
Routine maintenance of the tail section of a Northwest Airlines Douglas DC-9, the predecessor to the MD-80

During the course of the investigation, and later in its final report, the NTSB issued 24 safety recommendations, covering maintenance, regulatory oversight, and aircraft design issues. More than half of these were directly related to jackscrew lubrication and end-play measurement.[1] Also included was a recommendation that pilots were to be instructed that in the event of a flight control system malfunction they should not attempt corrective procedures beyond those specified in the checklist procedures, and in particular in the event of a horizontal stabilizer trim control system malfunction the primary and alternate trim motors should not be activated, and if unable to correct the problem through the checklists they should land at the nearest suitable airport.[1]

In NTSB board member John J. Goglia's statement for the final report, which was concurred with by the other three board members, he wrote:

This is a maintenance accident. Alaska Airlines' maintenance and inspection of its horizontal stabilizer activation system was poorly conceived and woefully executed. The failure was compounded by poor oversight... Had any of the managers, mechanics, inspectors, supervisors or FAA overseers whose job it was to protect this mechanism done their job conscientiously, this accident cannot happen... NTSB has made several specific maintenance recommendations, some already accomplished, that will, if followed, prevent the recurrence of this particular accident. But maintenance, poorly done, will find a way to bite somewhere else.[1]:188–189


Memorial sundial in Port Hueneme, California

After the crash, Alaska Airlines management said that it hoped to handle the aftermath in a manner similar to that conducted by Swissair after the Swissair Flight 111 accident. They wished to avoid the mistakes made by Trans World Airlines in the aftermath of the TWA Flight 800 accident; in other words, to provide timely information and compassion to the families of the victims.[23]

The victims' families approved the construction of a memorial sundial, designed by Santa Barbara artist James "Bud" Bottoms, which was placed at Port Hueneme on the California coast. The names of each of the victims are engraved on individual bronze plates mounted on the perimeter of the dial.[24] The sundial casts a shadow on a memorial plaque at 16:22 each January 31.[25][26]

Captain Thompson and First Officer Tansky were both awarded the Air Line Pilots Association Gold Medal for Heroism, in recognition of their actions during the emergency. This is the only time the award has ever been given posthumously.[27] The Ted Thompson/Bill Tansky Scholarship Fund was named in memory of the two pilots.[28]

Both McDonnell Douglas and Alaska Airlines eventually accepted liability for the crash, and all but one of the lawsuits brought by surviving family members were settled out of court before going to trial.[29] Candy Hatcher of the Seattle Post-Intelligencer said: "Many lost faith in Alaska Airlines, a homegrown company that had taken pride in its safety record and billed itself as a family airline."[9]

Steve Miletich of the Seattle Times wrote that the western portion of Washington State "had never before experienced such a loss from a plane crash".[30] Many residents of Seattle had been deeply affected by the disaster. As part of a memorial vigil in 2000, a column of light was beamed from the top of the Space Needle.[31] Students and faculty at the John Hay Elementary School in Queen Anne, Seattle held a memorial for four Hay students who were killed in the crash.[32] In April 2001, John Hay Elementary dedicated the "John Hay Pathway Garden" as a permanent memorial to the students and their families who were all killed on Flight 261.[33] The City of Seattle public park Soundview Terrace was renovated in honor of the four Pearson and six Clemetson family members who were killed on board Flight 261 from the same Seattle neighborhood of Queen Anne. The park's playground was named "Rachel's Playground" in memory of six-year-old Rachel Pearson, who was on board the MD-83[34] and who was often seen playing at the park.[35]

Two victims were falsely named in paternity suits as the fathers of children in Guatemala in an attempt to gain insurance and settlement money. Subsequent DNA testing proved these claims to be false.[36]

The crash has appeared in various advance fee fraud ("419") email scams, in which a scammer uses the name of someone who died in the crash to lure unsuspecting victims into sending money to the scammer by claiming the crash victim left huge amounts of unclaimed funds in a foreign bank account. The names of Morris Thompson and Ronald and Joyce Lake were used in schemes unrelated to them.[37][38]

As of November 2020, Flight 261 no longer exists, and Alaska Airlines no longer operates the Puerto Vallarta–San Francisco–Seattle/Tacoma route. Alaska Airlines now flies from Puerto Vallarta–Seattle/Tacoma non-stop with Flight 203 and Puerto Vallarta-San Francisco non-stop with Flight 373.[39][40] The airline retired the last of its MD-80s in 2008 and now uses Boeing 737s for these routes.[41]

Notable passengers[edit]

In popular culture[edit]

  • In the Canadian TV series Mayday, the flight was featured in the Season 1 (2003) Cutting Corners episode[44] (called Air Emergency and Air Disasters in the U.S. and Air Crash Investigation in the UK and elsewhere around the world). The dramatization was broadcast in the United States with the title "Fatal Error". The flight was also included in a Mayday Season 6 (2007) Science of Disaster special titled "Fatal Flaw",[45] which was called "Fatal Fix" in the United Kingdom, Australia and Asia.
  • The film drama Flight (2012), directed and co-produced by Robert Zemeckis, featured an airplane crash of an aircraft resembling an MD-83 which flies inverted and ultimately crash-lands, though the film's version recorded just six fatalities (four passengers, two crew) of the 102 persons aboard. In the film, NTSB investigators determine the probable cause of this crash to be the fatigue of a jackscrew due to excess wear and poor maintenance. The final seconds of the CVR of Flight 261 indicate the plane stabilized and was flying inverted shortly before the crash, an event depicted in the film. Screenwriter John Gatins later explained that the film's featured crash was "loosely inspired" by the events of Flight 261.[46]


The locations of the crash and the airports
Puerto Vallarta
Puerto Vallarta
San Francisco
San Francisco
Crash site
Crash site
Location of crash and airports in North America
Crash site is located in California
Crash site
Crash site
Crash site; off of southern California coast

See also[edit]


  1. ^ a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae af ag ah ai aj ak al am an ao ap aq ar as at au av aw ax ay az ba "Aircraft Accident Report, Loss of Control and Impact with Pacific Ocean Alaska Airlines Flight 261 McDonnell Douglas MD-83, N963AS About 2.7 Miles [4.3 km] North of Anacapa Island, California, January 31, 2000" (PDF). National Transportation Safety Board. December 30, 2002. NTSB/AAR-02/01. Retrieved September 9, 2016.
  2. ^ "Alaska Airlines Flight 261: Searchers Hold Out Hope for Possible Survivors; Crash Takes Heavy Toll on Airlines Employees' Families." CNN International. February 1, 2000. Retrieved February 16, 2010. "This is 1995 video of the plane. The MD-83 was manufactured in 1992 and had more than 26,000 of hours in flight."
  3. ^ Wilson, Jeff (February 1, 2000). "Alaska Airlines jet crashes into Pacific". Spokesman-Review. Associated Press. p. A1.
  4. ^ a b Wilson, Jeff (February 2, 2000). "Six minutes of struggle". Spokesman-Review. Associated Press. p. A1.
  5. ^ "Passengers and Crew Members on Alaska Airlines Flight 261". The New York Times. Associated Press. February 3, 2000. ISSN 0362-4331. Retrieved May 22, 2020.
  6. ^ Goodman, Chris; Long, Priscilla (January 28, 2001). "(Essay 2958) Alaska Flight 261 bound for Seattle crashes into the Pacific Ocean on January 31, 2000". Retrieved May 31, 2009.
  7. ^, Erin McGroarty. "Remembering Morris Thompson 20 years later". Fairbanks Daily News-Miner. Retrieved February 4, 2020.
  8. ^ "Flight 261 Special Report: Alaska Airlines Names Aviation Experts To Conduct Safety Audit". Alaska Airlines. March 24, 2000. Archived from the original on February 12, 2001. Retrieved May 29, 2018. Latest version of rolling report (originally retrieved May 31, 2009)
  9. ^ a b Hatcher, Candy (January 31, 2001). "The anger and the grief linger one year later". Seattle Post-Intelligencer. Archived from the original on September 4, 2002. Retrieved November 23, 2009.
  10. ^ a b Verhovek, Sam Howe (February 2, 2000). "Fate Leads An Airline To Grieve For Itself". The New York Times. Retrieved November 23, 2009.
  11. ^ Holmes, Stanley; Leeds, Jeff (February 2, 2000). "THE CRASH OF FLIGHT 261: For Airline, Loss Feels Like Deaths in Family". Archived from the original on July 15, 2012. Alt URL
  12. ^ "Transcript of Proceedings: Abstract of Aviation Accident Report: Alaska Airlines Flight 261, MD‑83, N963AS, Pacific Ocean about 2.7 Miles [4.3 km ] North of Anacapa Island, California, January 31, 2000, NTSB/AAR‑02/01" (PDF). Washington, DC: National Transportation Safety Board. December 10, 2002. pp. 1–292.
  13. ^ A block of altitudes assigned by ATC to allow altitude deviations. See "Block altitude". Aviation Glossary.
  14. ^ a b c d e "Alaska Airlines Flight 261 – 31 JAN 2000 – Relevant parts of ATC transcript". Aviation Safety Network. October 16, 2004. Retrieved April 24, 2007.
  15. ^ Phillips, Don (May 25, 2000). "Tape replays plane's last chilling minutes". Spokesman-Review. (Washington Post). p. A2.
  16. ^ {{cite|url=
  17. ^ a b Wallace, James (December 11, 2002). "NASA says it has a better jackscrew; others aren't convinced". Seattle Post-Intelligencer.
  18. ^ Dekker, Sidney W. A. (2011). "Systems Thinking 1.0 and Systems Thinking 2.0: Complexity science and a new conception of "cause"" (PDF). Aviation in Focus. Pontificia Universidade Catolica do Rio Grande do Sul. 2 (2): 21–39. Retrieved November 13, 2013.
  19. ^ "Alaska Airlines maintenance records raise new questions". CNN. February 14, 2000. Retrieved September 28, 2009.
  20. ^ The FailSafe Jackscrew Design. IASA.
  21. ^ a b "No criminal charges against Alaska; airline settles with whistle-blower" (Archive). The Seattle Times. Thursday December 20, 2001. Retrieved March 28, 2015.
  22. ^ "Whistle-Blower Sues Alaska Airlines". Associated Press at the Los Angeles Times. September 24, 2000. Retrieved March 28, 2015.
  23. ^ Song, Kyung M. (February 2, 2000). "Alaska Airlines copes with 'saddest, most tragic day'". The Seattle Times. Archived from the original on August 17, 2000. Retrieved December 17, 2009.
  24. ^ "Port Hueneme, CA – Official Website – Alaska Air Flight 261 Memorial Sundial". Port Hueneme, CA. Retrieved May 14, 2016.
  25. ^ Denn, Rebekah (January 31, 2002). "Memorials quieter today, but Flight 261 grief still hurts". Seattle Post-Intelligencer. Retrieved February 23, 2009.
  26. ^ Childs, Jeremy (February 1, 2020). "20 years after Alaska Airlines Flight 261 crash, loved ones still gather to grieve". Ventura County Star. Retrieved February 2, 2020.
  27. ^ Porterfield, Elaine; Castro, Hector (February 1, 2001). "Pilots honored for heroism during crisis". Seattle Post-Intelligencer. Retrieved February 23, 2009.
  28. ^ "Ted Thompson/Bill Tansky Scholarship Fund" (PDF). Alaska Airlines. Retrieved February 23, 2009.
  29. ^ Kravets, David (July 4, 2003). "All but one suit settled in Flight 261 crash". Seattle Post-Intelligencer. Associated Press. Retrieved December 17, 2009.
  30. ^ Miletich, Steve (July 4, 2003). "Father settles lawsuit in Alaska Air crash to avert playing of tape". Seattle Times. Retrieved January 7, 2017.
  31. ^ Jamieson, Robert L. (February 8, 2000). "Seattle still struggling to make sense of the Flight 261 tragedy". Seattle Post-Intelligencer. Retrieved November 23, 2009.
  32. ^ Harrell, Debera Carlton (February 11, 2001). "Hay school family' remembers its own". Seattle Post-Intelligencer. Retrieved December 17, 2009.
  33. ^ "In Memoriam". John Hay Elementary School. Archived from the original on October 8, 2015. Retrieved November 15, 2010.
  34. ^ a b c d e "The Lives That Were Lost". CBS News. February 1, 2000. Retrieved November 23, 2009.
  35. ^ Rebekah, Denn (January 31, 2001). "A park from Rachel, with love". Seattle Post-Intelligencer.
  36. ^ Hatcher, Candy (August 22, 2001). "Quest for truth proves lawyer's integrity". Seattle Post-Intelligencer. Retrieved February 23, 2009.
  37. ^ "Nigerian Advance Fee Scam Customized for Alaska: Morris Thompson variation could be taste of ploys to come". State of Alaska Department of Law. December 13, 2005. Retrieved February 23, 2009.
  38. ^ Le, Phuong Cat (November 9, 2007). "Latest e-mail uses Alaska Airlines crash victims to scam". Seattle Post-Intelligencer. Retrieved February 23, 2009.
  39. ^ "AS203 (ASA203) Alaska Airlines Flight Tracking and History". FlightAware. Retrieved November 25, 2020.
  40. ^ "AS373 (ASA373) Alaska Airlines Flight Tracking and History". FlightAware. Retrieved November 25, 2020.
  41. ^ "Alaska Airlines Completes Transition To All-Boeing Fleet". Alaska Airlines. August 28, 2008. Archived from the original on June 27, 2012. Retrieved November 25, 2020.
  42. ^ Gandesbery, Jean (December 1999). Seven Mile Lake: Scenes from a Minnesota Life. Minerva Press. ISBN 978-0-7541-0844-3.
  43. ^ "Names of those aboard Alaska Airlines Flight 261". CNN. February 4, 2000. Archived from the original on July 15, 2008. Retrieved December 17, 2009.
  44. ^ "Cutting Corners". Mayday. Season 1. Episode 5. 2003. Discovery Channel Canada / National Geographic Channel.
  45. ^ "Fatal Flaw". Mayday. Season 6. Episode 2. 2007. Discovery Channel Canada / National Geographic Channel.
  46. ^ Horn, John (October 21, 2012). "How the movie 'Flight' became airborne". Los Angeles Times. Retrieved October 23, 2012.

External links[edit]

External images
image icon Photos of N963AS at