Wikipedia

Alaska Airlines Flight 261

(Redirected from Tom Stockley)

Alaska Airlines Flight 261 was an Alaska Airlines flight of a McDonnell Douglas MD-80 series aircraft that crashed into the Pacific Ocean on January 31, 2000, roughly 2.7 miles (4.3 km; 2.3 nmi) north of Anacapa Island, California, following a catastrophic loss of pitch control, killing all 88 on board: 5 crew and 83 passengers. The flight 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 near San Francisco, California.

Alaska Airlines Flight 261
N963AS, the Alaska Airlines MD-83 aircraft involved in the accident, seen in 1992
Accident
DateJanuary 31, 2000 (January 31, 2000)
SummaryLoss of control following jackscrew failure due to improper maintenance
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.3467
Aircraft
Aircraft typeMcDonnell Douglas MD-83
OperatorAlaska Airlines
IATA flight No.AS261
ICAO flight No.ASA261
Call signALASKA 261
RegistrationN963AS
Flight originPuerto Vallarta Int'l Airport, Puerto Vallarta, Mexico
StopoverSan Francisco Int'l Airport, San Mateo, California, United States
DestinationSeattle–Tacoma International Airport, Seattle, Washington, United States
Occupants88
Passengers83
Crew5
Fatalities88
Survivors0

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."[1] For their efforts to save the plane, both pilots were posthumously awarded the Air Line Pilots Association Gold Medal for Heroism.

Background

edit

Aircraft

edit

The aircraft involved in the accident was a McDonnell Douglas MD-83, serial number 53077, and registered as N963AS.[2] The MD-83 was a longer-range version of the original MD-80 (itself 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.[3][4]

Crew

edit

The pilots of Flight 261 were both highly experienced.[5] Captain Ted Thompson, 53, had accrued 17,750 flight hours, and had more than 4,000 hours experience flying MD-80s.[6]: 10–11  First Officer William "Bill" Tansky, 57, had accumulated 8,140 hours as first officer on the MD-80.[6]: 11  Thompson had flown for Alaska Airlines for 18 years and Tansky for 15; neither pilot had been involved in an accident or incident prior to the crash.[6] Both pilots lived in Greater Los Angeles area and had previous military experience — Thompson in the U.S. Air Force and Tansky in the U.S. Navy.[7] Three Seattle-based flight attendants were also on board, completing the five-person crew.[8][9]

Passengers

edit

The five crew members and 47 of the passengers on board the plane were bound for Seattle.[10] Of the remaining passengers, 30 were traveling to San Francisco; three were bound for Eugene, Oregon; and three passengers were headed for Fairbanks, Alaska.[11] Of the passengers, one was Mexican and one was British, with all others being U.S. citizens.[12]

At least 35 occupants of Flight 261 were connected in some manner with Alaska Airlines or its sister carrier Horizon Air, including 12 people directly employed by the company.[13][14] As is common practice among airlines, employees can sit in seats that would otherwise have been left empty. Employees can also grant the same privilege to their family members or friends. Bouquets of flowers started arriving at the company's headquarters in SeaTac, Washington, the day after the crash.[15]

Notable passengers

edit
  • Jean Gandesbery, author of the book Seven Mile Lake: Scenes from a Minnesota Life,[16] died alongside her husband, Robert.[17][18]
  • Cynthia Oti, an investment broker and financial talk show host at San Francisco's KSFO-AM, was killed.[18]
  • Tom Stockley, wine columnist for The Seattle Times, died alongside his wife Margaret.[18]
  • Morris Thompson, commissioner of the Bureau of Indian Affairs in Alaska from 1973 to 1976, died alongside his wife Thelma and daughter Sheryl.[14][18]

Accident flight

edit
 
Final flight path of Alaska 261

Alaska Airlines Flight 261 departed from Puerto Vallarta's Licenciado Gustavo Díaz Ordaz International Airport at 13:37 PST (21:37 UTC), and climbed to its intended cruising altitude of flight level 310 (31,000 feet or 9,400 m). The plane was scheduled to land at San Francisco International Airport (SFO) less than 4 hours later. Sometime 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. The jammed stabilizer prevented the 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 about 10 lbf (44 N) of force to keep level. Neither the flight crew nor company maintenance could determine the cause of the jam. Repeated attempts to overcome the jam with the primary and alternate trim systems were unsuccessful.[6]

During this time, the flight crew had several discussions with the company dispatcher about whether to divert to LAX or continue on as planned to SFO. Ultimately, the pilots chose to divert. 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". Cockpit voice recorder (CVR) transcripts indicate that the dispatcher was concerned about the effect on the schedule ("flow"), should the flight divert.[6]: 195–197 

Video animation of flight path

At 16:09 (00:09 UTC), the flight crew successfully used the primary trim system to unjam the stuck horizontal stabilizer. Upon being freed, however, 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. Both pilots struggled together to regain control of the aircraft, and only by pulling with 130 to 140 lb (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 roughly 24,400 ft (7,400 m).[6]

Alaska 261 informed air traffic control (ATC) 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 the approach.[6] 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."[6]: 8  Later, during the public hearings into the accident, the request by the pilot not to fly over populated areas was mentioned.[19]: 170–171  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.[6]

Video of jackscrew failure sequence
ATC audio before and after the 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 horizontal stabilizer failed at 17,800 feet (5,400 m)[6]: 6  and the aircraft rapidly pitched over into a dive while rolling to the left.[6]: 9  The crippled plane had been given a block altitude,[20] and several aircraft in the vicinity had been alerted by ATC to maintain visual contact with the stricken jet. These aircraft immediately contacted the controller.[21] 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."[21] ATC then tried to contact the plane. The crew of a SkyWest airliner reported, "He's, uh, definitely out of control."[21] Although the CVR captured the co-pilot saying "mayday", no radio communications were received from the flight crew during the final event.[6]: 9 [21]

The CVR transcript reveals the pilots' constant attempts for the duration of the dive to regain control of the aircraft. After the jackscrew failed, the plane pitched -70° and was rolling over to the left. Performing an upset recovery maneuver, the captain commanded to "push and roll, push and roll," managing to increase the pitch to -28°, he stated, "ok, we are inverted...and now we gotta get it."[6]: 9  Over the next minute, completely inverted and still diving at a -9 degree pitch, the crew struggled to roll the plane, with the captain calling to "push push push...push the blue side up," "ok now let's kick rudder...left rudder left rudder", to which the copilot responded, "I can't reach it".[6] The captain then replied, "ok right rudder...right rudder," followed 18 seconds later by "gotta get it over again...at least upside down we're flying."[6]

Despite the attempt to fly the plane inverted, which almost entirely arrested its descent, the aircraft had lost too much altitude in the dive and was far beyond recovery. A few seconds before 16:21 (00:21 UTC),[6] Flight 261 hit the Pacific Ocean at high speed between the coastal city of Port Hueneme, California, and Anacapa Island. At this time, pilots from aircraft flying in the vicinity reported in, with one 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."[21][22] The aircraft was destroyed by the impact forces, and all occupants on board were killed by blunt-force impact trauma.[6]

Investigation

edit

Wreckage recovery and analysis

edit
 
Recovered jackscrew: The spiral "wire" wrapped around the threaded portion is the remnant of the internal screw thread stripped from the acme nut.

The USS Cleveland (LPD-7) assisted in recovery operations.[23]

 
Preparation of the flight data recorder for transport from 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.[24] 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 Seabees' Naval Construction Battalion Center Port Hueneme, California, for examination and documentation by NTSB investigators. Both the horizontal stabilizer trim system jackscrew (also referred to as "acme screw") and the corresponding acme nut, through which the jackscrew turns, were found. The jackscrew was constructed from case-hardened steel and is 22 in (56 cm) long and 1.5 in (3.8 cm) in diameter. The acme nut was constructed from a softer copper alloy containing aluminum, nickel, and bronze. 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.[6][25]

The 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 subjected to aerodynamic forces that it was not designed to withstand, leading to the complete failure of the stabilizer assembly. 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 1,000 flight hours, much faster than the expected wear of 0.001 inches (0.025 mm) per 1,000 flight‑hours. 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 to be not a factor in this accident.[6] 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.[26] 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. Both of these circumstances resulted from Alaska Airlines' attempts to cut costs.[6]

Identification of passengers

edit

Due to the extreme impact forces, only a few bodies were found intact,[5] and none were visually identifiable. All passengers were identified using fingerprints, dental records, tattoos, personal items, and anthropological examination.[27]

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 SFO, who last performed the lubrication, the task was shown to take about one hour, whereas the aircraft manufacturer estimated the task should take four hours. 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." Laboratory tests indicated that the excessive wear of the jackscrew assembly could not have accumulated in just the four-month period between the September 1999 maintenance and the accident flight. Therefore, the NTSB concluded, "more than just the last lubrication was missed or inadequately performed."[6]

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. Testing revealed that the nonstandard tools ("restraining fixtures") used by Alaska Airlines could result in inaccurate measurements and that if accurate measurements had been obtained at the time of the last inspection, these measurements possibly would have indicated the excessive wear and the need to replace the affected components.[6]

Extension of maintenance intervals

edit

Between 1985 and 1996, Alaska Airlines progressively increased the period between both jackscrew lubrication and end-play checks, with the approval of the Federal Aviation Administration (FAA). 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. 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.[6]

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. The NTSB found, "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."[6]

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." The investigation concluded, "FAA surveillance of Alaska Airlines had been deficient for at least several years." 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."[6]

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

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.[6] 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.[6]: 162–165 

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

Jackscrew design improvement

edit

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

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 FAA 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,[29] 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.[30] 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.[29]

Conclusions

edit

In addition to the probable cause, the NTSB found these contributing factors:[6]

  • Alaska Airlines extended its lubrication interval for its McDonnell Douglas MD-80 horizontal stabilizer components based on McDonnell Douglas's recommendation, and the FAA approved the extended schedule. This increased the likelihood that a missed or inadequate lubrication would result in the near complete deterioration of the jackscrew-assembly acme-nut threads. The extended lubrication interval was a direct cause of the excessive wear and contributed to the Alaska Airlines Flight 261 accident.
  • Alaska Airlines extended the end-play check interval and the FAA approved the change. This 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. 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.[6]

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

This is a maintenance accident. Alaska Airlines' maintenance and inspection of its horizontal stabilizer activation system were 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.[6]: 188–189 

Aftermath

edit

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, TWA's failure to provide timely information and compassion to the families of the victims.[31]

Steve Miletich of The Seattle Times wrote that the western portion of Washington, "had never before experienced such a loss from a plane crash".[32]

Liability

edit

Both Boeing (who had acquired McDonnell Douglas through a merger in 1997) 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.[33] While the financial terms of settlements had not been officially disclosed, The Seattle Times reported the total amount to be in excess of US$300 million, covered entirely by insurance.[34] According to other sources, the individual settlements were "anywhere from a couple million dollars up to $20 million", purportedly "among the largest ever in an air disaster".[35] Candy Hatcher of the Seattle Post-Intelligencer wrote: "Many lost faith in Alaska Airlines, a homegrown company that had taken pride in its safety record and billed itself as a family airline."[13]

Flight number

edit

As of 2023, 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 nonstop with Flights 1380 and 1411 and Puerto Vallarta—San Francisco nonstop with Flights 1369 and 1370.[36][37] The airline retired the last of its MD-80s in 2008 and now uses Boeing 737s for these routes.[38]

Memorials

edit

Captain Thompson and First Officer Tansky were both posthumously 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.[39] The Ted Thompson/Bill Tansky Scholarship Fund was named in memory of the two pilots.[40]

 
Memorial sundial in Port Hueneme, California

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.[41] The sundial casts a shadow on a memorial plaque at 16:22 each January 31.[42][43]

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.[44] 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.[45] In April 2001, John Hay Elementary dedicated the "John Hay Pathway Garden" as a permanent memorial to the students and their families who were killed on Flight 261.[46] 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[18] and who was often seen playing at the park.[47]

Attempted fraud

edit

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

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.[49][50]

edit
  • In the Canadian TV series Mayday, the flight was featured in the season-one (2003) "Cutting Corners" episode[51] (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-six (2007) Science of Disaster special titled "Fatal Flaw",[52] which was called "Fatal Fix" in the United Kingdom, Australia, and Asia.[53] The crash was covered again (with an entirely new cast) in season 22, episode 5 of Mayday, titled "Pacific Plunge".[54]
  • The film drama Flight (2012) 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 indicates 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.[55]

Maps

edit
 
 
Puerto Vallarta
 
San Francisco
 
Crash site
 
Seattle
class=notpageimage|
Location of crash and airports in North America
 
 
Crash site
class=notpageimage|
Crash site off the Southern California coast

See also

edit

References

edit
  1. ^ "FAA". December 16, 2022.
  2. ^ Ranter, Harro. "Alaska Airlines MD83". Archived from the original on January 31, 2021. Retrieved February 3, 2021.
  3. ^ "Alaska Airlines Flight 261: Searchers Hold Out Hope for Possible Survivors; Crash Takes Heavy Toll on Airlines Employees' Families". CNN International. February 1, 2000. Archived from the original on December 24, 2013. 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.
  4. ^ Wilson, Jeff (February 12, 2000). "Alaska Airlines jet crashes into Pacific". The Spokesman-Review. Associated Press. p. A1.
  5. ^ a b Wilson, Jeff (February 2, 2000). "Six minutes of struggle". The Spokesman-Review. Associated Press. p. A1.
  6. ^ 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 "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. Archived (PDF) from the original on June 15, 2016. Retrieved September 9, 2016.
  7. ^ "Who was on board". The Seattle Times. February 1, 2000.
  8. ^ "Passengers and Crew Members on Alaska Airlines Flight 261". The New York Times. Associated Press. February 3, 2000. ISSN 0362-4331. Archived from the original on November 11, 2020. Retrieved May 22, 2020.
  9. ^ "Las Vegas woman was among crew members". Las Vegas Sun. February 3, 2000. Archived from the original on February 8, 2022. Retrieved February 7, 2022.
  10. ^ Goodman, Chris; Long, Priscilla (January 28, 2001). "(Essay 2958) Alaska Flight 261 bound for Seattle crashes into the Pacific Ocean on January 31, 2000". HistoryLink.org. Archived from the original on September 18, 2016. Retrieved May 31, 2009.
  11. ^ McGroarty, Erin (January 31, 2020). "Remembering Morris Thompson 20 years later". Fairbanks Daily News-Miner. Archived from the original on February 4, 2020. Retrieved February 4, 2020.
  12. ^ "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)
  13. ^ 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.
  14. ^ a b Verhovek, Sam Howe (February 2, 2000). "Fate Leads An Airline To Grieve For Itself". The New York Times. Archived from the original on May 30, 2018. Retrieved November 23, 2009.
  15. ^ Holmes, Stanley; Leeds, Jeff (February 2, 2000). "The Crash of Flight 261: For Airline, Loss Feels Like Deaths in Family". Los Angeles Times. Archived from the original on July 15, 2012. Alt URL
  16. ^ Gandesbery, Jean (December 1999). Seven Mile Lake: Scenes from a Minnesota Life. Minerva Press. ISBN 978-0-7541-0844-3. OCLC 43673989. Archived from the original on May 29, 2018. Retrieved May 29, 2018.
  17. ^ "Names of those aboard Alaska Airlines Flight 261". CNN. February 4, 2000. Archived from the original on July 15, 2008. Retrieved December 17, 2009.
  18. ^ a b c d e "The Lives That Were Lost". CBS News. February 1, 2000. Archived from the original on May 4, 2014. Retrieved November 23, 2009.
  19. ^ "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. Retrieved June 29, 2020.
  20. ^ A block of altitudes assigned by ATC to allow altitude deviations. See "Block altitude". Aviation Glossary. October 21, 2009. Archived from the original on January 22, 2019. Retrieved January 22, 2019.
  21. ^ a b c d e "Alaska Airlines Flight 261 – 31 JAN 2000 – Relevant parts of ATC transcript". Aviation Safety Network. October 16, 2004. Archived from the original on September 29, 2007. Retrieved April 24, 2007.
  22. ^ Phillips, Don (May 25, 2000). "Tape replays plane's last chilling minutes". The Spokesman-Review. The Washington Post. p. A2.
  23. ^ Ship command operation reports navy.mil
  24. ^ "Retrieving The Wreckage". www.govtech.com. August 12, 2010. Archived from the original on February 3, 2020. Retrieved December 22, 2020.
  25. ^ Wallace, James (December 11, 2002). "NASA says it has a better jackscrew; others aren't convinced". Seattle Post-Intelligencer. Archived from the original on March 14, 2018. Retrieved March 14, 2018.
  26. ^ 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. 2 (2). Pontificia Universidade Catolica do Rio Grande do Sul: 21–39. Archived (PDF) from the original on November 13, 2013. Retrieved November 13, 2013.
  27. ^ "Alaska Airlines maintenance records raise new questions". CNN. February 14, 2000. Retrieved September 28, 2009.
  28. ^ The FailSafe Jackscrew Design Archived November 20, 2007, at the Wayback Machine. IASA.
  29. ^ a b "No criminal charges against Alaska; airline settles with whistle-blower". The Seattle Times. December 20, 2001. Archived from the original on April 2, 2015. Retrieved March 28, 2015.
  30. ^ "Whistle-Blower Sues Alaska Airlines". Los Angeles Times. Associated Press. September 24, 2000. Archived from the original on September 14, 2017. Retrieved March 28, 2015.
  31. ^ 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.
  32. ^ Miletich, Steve (July 4, 2003). "Father settles lawsuit in Alaska Air crash to avert playing of tape". The Seattle Times. Archived from the original on January 8, 2017. Retrieved January 7, 2017.
  33. ^ Kravets, David (July 4, 2003). "All but one suit settled in Flight 261 crash". Seattle Post-Intelligencer. Associated Press. Archived from the original on July 13, 2019. Retrieved December 17, 2009.
  34. ^ Miletich, Steve (July 4, 2003). "Father settles lawsuit in Alaska Air crash to avert playing of tape". The Seattle Times. Retrieved December 25, 2022.
  35. ^ Kravets, David (July 3, 2003). "All but one suit settled in Flight 261 crash". Seattle Post-Intelligencer.
  36. ^ "AS127 (ASA127) Alaska Airlines Flight Tracking and History". FlightAware. Retrieved May 22, 2022.
  37. ^ "AS1273 (ASA1273) Alaska Airlines Flight Tracking and History". FlightAware. Retrieved May 22, 2022.
  38. ^ "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.
  39. ^ Dodd, Chris; Writer, Staff (March 1, 2001). "Alaska Flight 261 Pilots Awarded ALPA Gold Medal". Retrieved August 4, 2023.
  40. ^ "Ted Thompson/Bill Tansky Scholarship Fund" (PDF). Alaska Airlines. Archived (PDF) from the original on March 26, 2009. Retrieved February 23, 2009.
  41. ^ "Port Hueneme, CA – Official Website – Alaska Air Flight 261 Memorial Sundial". www.ci.port-hueneme.ca.us. Port Hueneme, CA. Archived from the original on May 30, 2016. Retrieved May 14, 2016.
  42. ^ Denn, Rebekah (January 31, 2002). "Memorials quieter today, but Flight 261 grief still hurts". Seattle Post-Intelligencer. Archived from the original on July 13, 2019. Retrieved February 23, 2009.
  43. ^ Childs, Jeremy (February 1, 2020). "20 years after Alaska Airlines Flight 261 crash, loved ones still gather to grieve". Ventura County Star. Archived from the original on February 2, 2020. Retrieved February 2, 2020.
  44. ^ Clarridge, Christine (February 2, 2010). "10th anniversary of Alaska Flight 261". Seattle Times. Retrieved September 12, 2023.
  45. ^ Harrell, Debera Carlton (February 11, 2001). "Hay school family' remembers its own". Seattle Post-Intelligencer. Retrieved December 17, 2009.[permanent dead link‍]
  46. ^ "In Memoriam". hayes.seattleschools.org. John Hay Elementary School. Archived from the original on October 8, 2015. Retrieved November 15, 2010.
  47. ^ Rebekah, Denn (January 31, 2001). "A park from Rachel, with love". Seattle Post-Intelligencer.
  48. ^ Hatcher, Candy (August 22, 2001). "Quest for truth proves lawyer's integrity". Seattle Post-Intelligencer. Archived from the original on March 5, 2021. Retrieved February 23, 2009.
  49. ^ "Nigerian Advance Fee Scam Customized for Alaska: Morris Thompson variation could be taste of ploys to come". law.alaska.gov. State of Alaska Department of Law. December 13, 2005. Archived from the original on April 9, 2010. Retrieved February 23, 2009.
  50. ^ Le, Phuong Cat (November 9, 2007). "Latest e-mail uses Alaska Airlines crash victims to scam". Seattle Post-Intelligencer. Archived from the original on December 24, 2008. Retrieved February 23, 2009.
  51. ^ "Cutting Corners". Mayday. Season 1. Episode 5. 2003. Discovery Channel Canada / National Geographic Channel.
  52. ^ "Fatal Flaw". Mayday. Season 6. Episode 2. 2007. Discovery Channel Canada / National Geographic Channel.
  53. ^ "Fatal Fix". Mayday. Season 6. Episode 2. 2007. Discovery Channel Canada / National Geographic Channel.
  54. ^ "Alaska Airlines Flight 261 on IMDb". IMDb.
  55. ^ Horn, John (October 21, 2012). "How the movie 'Flight' became airborne". Los Angeles Times. Archived from the original on December 25, 2018. Retrieved October 23, 2012.
edit
 
Wikimedia Commons has media related to Alaska Airlines Flight 261.
External images
  Photos of N963AS at Airliners.net

Retrieved from "https://en.wikipedia.org/w/index.php?title=Alaska_Airlines_Flight_261&oldid=1257072017"