Alaska Airlines Flight 261

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Alaska Airlines Flight 261
N958AS MD-83 Alaska Al YVR 24AUG05 (6920119895).jpg
Alaska Airlines MD-83, similar to the accident aircraft
Accident summary
Date January 31, 2000 (2000-01-31)
Summary Jackscrew failure due to improper maintenance[1]
Site Pacific Ocean
near Anacapa Island, California
Passengers 83
Crew 5
Fatalities 88 (all)
Survivors 0
Aircraft type McDonnell Douglas MD-83
Operator Alaska Airlines
Registration N963AS
Flight origin Lic. Gustavo Díaz Ordaz Int'l Airport
Stopover San Francisco Int'l Airport
Destination Seattle-Tacoma Int'l Airport

Alaska Airlines Flight 261 was a scheduled international passenger flight on January 31, 2000 from Lic. 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 The aircraft, a McDonnell Douglas MD-83, crashed into the Pacific Ocean about 2.7 miles (4.3 km) north of Anacapa Island, California, after suffering a catastrophic loss of pitch control. The crash killed everyone aboard: two pilots, three cabin crewmembers, and 83 passengers.

The subsequent investigation by the National Transportation Safety Board 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. The thread failure was caused by excessive wear resulting from Alaska Airlines' insufficient lubrication of the jackscrew assembly".[1]:xii


The aircraft, manufactured in 1992, had more than 26,000 hours of flight before the crash.[2]

Accident flight[edit]


The pilots of Flight 261 were both highly experienced veterans. Captain Ted Thompson (53) had accrued 17,750 flight hours and he 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]


Fifty people on board were bound for Seattle, 47 passengers and the three flight attendants; 32 passengers aboard the plane had San Francisco as their final destination, three had Eugene, Oregon, as their final destination, and one passenger was headed for Fairbanks, Alaska.[3] Of the passengers, 1 was Mexican and 1 was British; the rest were American citizens.[4]

At least 35 occupants, including 12 employees,[5] were connected to Alaska Airlines or Horizon Air in some manner, leading many airline employees to mourn for those lost in the crash.[6] Alaska Airlines stated that, during slower traveling days, it was common for employees to fill seats that would otherwise have been empty. Bouquets of flowers started arriving at the company's headquarters in SeaTac, Washington, the day after the crash.[7]

Initial flight segment[edit]

Final flight path of Alaska 261

Alaska 261 departed from Puerto Vallarta at 13:37 PST, and climbed to its intended cruising altitude of flight level 310 (31,000 feet (9,400 m)). The plane was scheduled to land at San Francisco International Airport. Some time before 15:49, 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 controls 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", nonetheless "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, 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 feet to between 23,000 and 24,000 feet 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 foot-per minute descent of the aircraft and stabilize the MD-83 at approximately 24,400 feet.[1]

Alaska 261 informed air traffic control of their control problems. After the flight crew stated their intention to land at LAX, ATC asked if 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 specifically commended by NTSB board members.[8]:6–9[not in citation given] During this time, the flight crew considered, and rejected, any further attempts to correct the runaway trim. They proceeded to descend 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

Beginning at 16:19, the CVR recorded the sounds of at least four distinct "thumps" followed 17 seconds later by an "extremely loud noise" as the overstrained jackscrew failed completely and separated from the acme nut holding it in place. The aircraft rapidly pitched over into a dive.[1] The crippled aircraft had been given a block altitude, and several aircraft in the vicinity had been alerted by ATC to maintain visual contact with the stricken jet and they immediately contacted the controller.[9] 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."[9] ATC then tried to contact the plane. The crew of a Skywest airliner reported "He's, uh, definitely out of control".[9] Although the CVR captured the co-pilot saying "mayday", no radio communications were received from the flight crew during the final event.[1]:9[9]

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.[1]:9 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). Flight 261 impacted the Pacific Ocean at high speed between the coastal city of Port Hueneme, California, and Anacapa Island, a few seconds before 16:22. 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, "Yeah sir, he, uh, he, uh, hit the water, he's, uh, down."[9] The aircraft was destroyed by the impact forces, and all occupants onboard were killed instantly by blunt force impact trauma.[1]


Wreckage recovery and analysis[edit]

Recovered jackscrew – The spiral "wire" wound around the threaded portion is the remains of the acme nut internal screw thread that was stripped from the nut.
Deepak Joshi (left) of the National Transportation Safety Board and John Scarola of Alaska Airlines prepare the flight data recorder for Flight 261 for transport from the deck of the MV Kellie Chouest on February 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. In addition, both engines, as well as the Flight Data Recorder (FDR) and CVR were retrieved. All wreckage that was retrieved from the crash site was unloaded at 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 retrieved. As the jackscrew rotates it moves up or down through the (fixed) acme nut. This up and down motion moves the horizontal stabilizer for the trim system. Upon recovery from the crash site, and subsequent examination, the jackscrew was found with metallic filaments wrapped around it; these were later determined to be the threads from the acme nut.[1]

Later analysis estimated that 90% of the threads in the acme nut had previously been worn away, and that they stripped out during the accident flight while en route to San Francisco. Once the threads stripped out, the horizontal stabilizer assembly was then subjected to aerodynamic forces it was not designed to withstand, and finally, the overstressed stabilizer assembly failed completely.[1] Based on the time since the last inspection of the jackscrew assembly, the NTSB determined that the nut threads had deteriorated at 0.012 inches (0.30 mm) per 1,000 flight‑hours, much faster than the expected wear of 0.001 inches (0.025 mm) per 1,000 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 threads on the acme screw, 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.[10] Ultimately, the lack of lubrication and resultant excessive wear of the acme nut threads were determined to be the direct causes of the accident.[1]

Identification of passengers[edit]

Due to the severity of the impact and the destruction of the passenger cabin, very few bodies were found intact. All occupants were identified using fingerprints, dental records, tattoos, personal items, and anthropological examination.[11]

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 San Francisco International Airport (SFO) mechanic 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 X 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.[12]

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 the work had not been completed. 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 its records. In August 1999 Alaska Airlines put Liotine on paid leave,[13] 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 aircraft involved in the accident be replaced.[14] 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.[13]


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 done by Swissair after the Swissair Flight 111 accident, as opposed to the manner that TWA handled the aftermath of TWA Flight 800; in other words, to provide timely information and compassion to the families of victims.[15]

The families of the victims approved the construction of a memorial sundial that was placed at Port Hueneme. The crash site is located 14 miles offshore, between the mainland at Port Hueneme and Anacapa Island. The names of each of the victims are engraved on individual bronze plates mounted on the perimeter of the dial.[16] The sundial was designed by Santa Barbara artist James "Bud" Bottoms to cast a shadow on a memorial plaque at 16:22 each January 31.[17]

For their actions during the emergency, Captain Thompson and First Officer Tansky were both awarded the Air Line Pilots Association Gold Medal for Heroism, the only time the award has been given posthumously.[18]

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.[19] 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."[5]

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.[20]

The Ted Thompson/Bill Tansky Scholarship Fund was named in memory of the two pilots who were both killed in the crash.[21]

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."[22] Many residents of the City of Seattle, Washington had been deeply affected by the disaster. As part of a memorial vigil in the year 2000, a column of light was beamed from the top of the Space Needle.[23] Students and faculty at the John Hay Elementary School in Queen Anne, Seattle held a memorial for four Hay students who were all killed in the crash.[24] 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.[25] The City of Seattle public park Soundview Terrace was renovated in honor of the four Pearson and six Clemetson family members who were all killed onboard Flight 261 from the same Seattle neighborhood of Queen Anne. The park's playground was named "Rachel's Playground" in the memory of six-year-old Rachel Pearson, who was on board the MD-83, was often seen playing at the park.[26]

The crash has appeared in various advance fee fraud ("419") email scams. In these scams, 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 money in a foreign bank account. The names of Morris Thompson and Ronald and Joyce Lake were used in schemes unrelated to them.[27][28]

As of November 2011, Flight 261 no longer exists. The flight route designation for this route is now Flight 221. Alaska Airlines continues to operate the Puerto Vallarta-San Francisco-Seattle/Tacoma route, and also operates the Puerto Vallarta-Seattle/Tacoma route nonstop as Flight 203. The airline retired the last of its MD-80s in 2008 and now operates all Boeing 737 aircraft.

Notable passengers[edit]

In popular culture[edit]

In 2004, Flight 261 was featured in an episode of Discovery Channel (Canada)'s Mayday television program (also known as Air Emergency or Air Disasters in the United States and known as Air Crash Investigation elsewhere), titled Cutting Corners or Fatal Error.

In 2012, the film drama Flight, directed and co-produced by Robert Zemeckis, featured an airplane crash of a craft resembling an MD-83 which flies inverted and ultimately 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 was 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 the film's featured crash was "loosely inspired" by the events of Flight 261.[32]


The locations of the crash and the airports
Puerto Vallarta
Puerto Vallarta
San Francisco
San Francisco
Crash site
Crash site
Location of the crash and the airports
Crash site is located in California
Crash site
Crash site
Crash site in California

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 "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. ^ "HistoryLink Essay: Alaska Flight 261 bound for Seattle crashes into the Pacific Ocean on 31 January 2000." HistoryLink. Retrieved May 31, 2009.
  4. ^ "Flight 261 Special Report." Alaska Airlines. February 12, 2001. Retrieved May 31, 2009.
  5. ^ a b Hatcher, Candy. "The anger and the grief linger one year later." Seattle Post-Intelligencer. Wednesday January 31, 2001. Retrieved November 23, 2009.
  6. ^ a b Verhovek, Sam Howe. "Fate Leads An Airline To Grieve For Itself." The New York Times. February 2, 2000. Retrieved November 23, 2009.
  7. ^ Holmes, Stanley and Jeff Leeds. "THE CRASH OF FLIGHT 261; For Airline, Loss Feels Like Deaths in Family." Los Angeles Times. February 20, 2000. A23. Retrieved December 14, 2009.
  8. ^ "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. Archived from the original (PDF) on June 4, 2011. 
  9. ^ a b c d e Aviation Safety Network > Accident investigation > CVR / FDR > Transcripts > Alaska Airlines Flight 261 – 31 JAN 2000
  10. ^ 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. 
  11. ^ "Alaska Airlines maintenance records raise new questions." CNN. February 14, 2000. Retrieved September 28, 2009.
  12. ^ The FailSafe Jackscrew Design
  13. ^ a b "No criminal charges against Alaska; airline settles with whistle-blower" (Archive). The Seattle Times. Thursday December 20, 2001. Retrieved March 28, 2015.
  14. ^ "Whistle-Blower Sues Alaska Airlines." Associated Press at the Los Angeles Times. September 24, 2000. Retrieved March 28, 2015.
  15. ^ Song, Kyung M. "Alaska Airlines copes with 'saddest, most tragic day'." The Seattle Times. Wednesday, February 2, 2000. Retrieved December 17, 2009.
  16. ^ "Port Hueneme, CA – Official Website – Alaska Air Flight 261 Memorial Sundial". Port Hueneme, CA. Retrieved 14 May 2016. 
  17. ^ Denn, Rebekah. "Memorials quieter today, but Flight 261 grief still hurts." Seattle Post-Intelligencer. Thursday, January 31, 2002. Retrieved February 23, 2009.
  18. ^ Porterfield, Elaine and Hector Castro. "Pilots honored for heroism during crisis." Seattle Post-Intelligencer. Thursday, February 1, 2001. Retrieved February 23, 2009.
  19. ^ Kravets, David. "All but one suit settled in Flight 261 crash." Associated Press at Seattle Post-Intelligencer. Friday, July 4, 2003. Retrieved December 17, 2009.
  20. ^ Hatcher, Candy. "Quest for truth proves lawyer's integrity." Seattle Post-Intelligencer. Wednesday, August 22, 2001. Retrieved February 23, 2009.
  21. ^ "Ted Thompson/Bill Tansky Scholarship Fund." Alaska Airlines. Retrieved February 23, 2009.
  22. ^ Miletich, Steve (2003-07-04). "Father settles lawsuit in Alaska Air crash to avert playing of tape". Seattle Times. Retrieved 2017-01-07. 
  23. ^ Jamieson, Robert L. (2000-02-08). "Seattle still struggling to make sense of the Flight 261 tragedy". Seattle Post-Intelligencer. Retrieved 2009-11-23. 
  24. ^ Harrell, Debera Carlton (2001-02-11). "Hay school family' remembers its own". Seattle Post-Intelligencer. Retrieved 2009-12-17. 
  25. ^ Official John Hay Elementary Web Site. "[1]." Retrieved on November 15, 2010.
  26. ^ Denn, Rebekah (2001-01-31). "A park from Rachel, with love". Seattle Post-Intelligencer. 
  27. ^ "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.
  28. ^ Le, Phuong Cat. "Latest e-mail uses Alaska Airlines crash victims to scam." Seattle Post-Intelligencer. November 9, 2007. Retrieved February 23, 2009.
  29. ^ "Seven Mile Lake (Hardcover)." Retrieved October 31, 2008.
  30. ^ "Names of those aboard Alaska Airlines Flight 261." CNN. February 4, 2000. Retrieved December 17, 2009.
  31. ^ a b c d "The Lives That Were Lost." CBS News. 2000. Retrieved November 23, 2009.
  32. ^ Horn, John (October 21, 2012). "How the movie 'Flight' became airborne". Los Angeles Times. Retrieved October 23, 2012. 

External links[edit]

External image's Photo gallery of N963AS

Coordinates: 34°03.5′N 119°20.8′W / 34.0583°N 119.3467°W / 34.0583; -119.3467