|
|
| Line 1: |
Line 1: |
| − | {{Infobox Airliner accident|name=Alaska Airlines Flight 261|
| |
| − | Crash image=Airplane animation 261 still lg.PNG|400px|Image caption=Frame from NTSB animation of Alaska Airlines Flight 261 |
| |
| − | Date=January 31, 2000 |
| |
| − | Type=Mechanical failure |
| |
| − | Site=Pacific Ocean near [[Anacapa Island, California]] |
| |
| − | Fatalities=88 |
| |
| − | Aircraft Type=[[McDonnell Douglas MD-83]] |
| |
| − | Origin=[[Lic. Gustavo Díaz Ordaz International Airport]] |
| |
| − | Stopover=[[San Francisco International Airport]] |
| |
| − | Destination=[[Seattle-Tacoma International Airport]] |
| |
| − | Operator=[[Alaska Airlines]] |
| |
| − | Tail Number=N963AS |
| |
| − | Passengers=83 |
| |
| − | Crew=5 |
| |
| − | Survivors = 0 |
| |
| − | }}
| |
| | | | |
| − | '''[[Alaska Airlines]] Flight 261''', a [[McDonnell Douglas MD-83]] aircraft, crashed on [[January 31]], [[2000]] in the [[Pacific Ocean]] about 2.7 miles (4.3 km) north of [[Anacapa Island]], [[California]]. The two pilots, three cabin crewmembers, and 83 passengers on board were killed, and the airplane was destroyed. Alaska 261 was a scheduled international passenger flight from [[Lic. Gustavo Díaz Ordaz International Airport]] (PVR), [[Puerto Vallarta]], [[Mexico]], to [[Seattle-Tacoma International Airport]] (SEA), with an intermediate stop planned at [[San Francisco International Airport]] (SFO).<ref name="NTSB summary">[http://www.ntsb.gov/publictn/2002/AAR0201.htm NTSB Abstract AAR-02/01<!-- Bot generated title -->]</ref>
| |
| − |
| |
| − | The subsequent investigation by the [[NTSB|National Transportation Safety Board]] determined that inadequate maintenance led to excessive wear and catastrophic failure of a critical [[Flight controls|flight control system]] during flight. The probable cause was stated to be "a loss of airplane [[Pitch (flight)|pitch]] control resulting from the in-flight failure of the [[Tailplane|horizontal stabilizer]] [[Trim tab|trim]] system [[jackscrew]] assembly’s [[Acme thread form|acme]] [[Screw thread|nut]] threads. The thread failure was caused by excessive wear resulting from [[Alaska Airlines|Alaska Airlines’]] insufficient lubrication of the jackscrew assembly."<ref name="NTSB summary"/>
| |
| − |
| |
| − | <div style="overflow:auto;height:1px;">
| |
| − | [[Date:=2000-01-31]]
| |
| − | [[Aircraft_Type:=MD83]]
| |
| − | [[Airline:=Alaska Airlines]]
| |
| − | [[Airline_Code:=AS]]
| |
| − | [[State_Code:=CA]]
| |
| − | [[Airport_Code:=SFO]]
| |
| − | [[Accident_Cause:=Mechanical (jackscrews)]]
| |
| − | [[Miles_Traveled:=1320]]
| |
| − | [[Fatalities:=88]]
| |
| − | [[Survivors:=0]]
| |
| − | </div>
| |
| − |
| |
| − | ==The accident flight==
| |
| − | ===Passengers===
| |
| − | 47 of the passengers were bound for Seattle and 3 of the crew members were based in Seattle. Most of the other passengers were bound for San Francisco <ref>[http://www.historylink.org/essays/output.cfm?file_id=2958 HistoryLink Essay: Alaska Flight 261 bound for Seattle crashes into the Pacific Ocean on January 31, 2000<!-- Bot generated title -->]</ref>.
| |
| − |
| |
| − | Of the occupants, at least 35, including 12 employees<ref>"[http://seattlepi.nwsource.com/local/alas311.shtml The anger and the grief linger one year later]," ''[[Seattle Post-Intelligencer]]''</ref>, were connected to Alaska Airlines or [[Horizon Air]] in some manner <ref>[http://query.nytimes.com/gst/fullpage.html?res=990CE5DD153FF931A35751C0A9669C8B63&sec=&spon=&pagewanted=print Fate Leads An Airline To Grieve For Itself - New York Times<!-- Bot generated title -->]</ref>, leading many airline employees to mourn for the losses in the crash.
| |
| − |
| |
| − | ====Notable passengers====
| |
| − | *[[Morris Thompson]], Commissioner of the [[Bureau of Indian Affairs]] in the late [[1960s]] and early [[1970s]], died with his wife and daughter. <ref>"[http://query.nytimes.com/gst/fullpage.html?res=990CE5DD153FF931A35751C0A9669C8B63&sec=&spon=&pagewanted=print Fate Leads An Airline To Grieve For Itself]," ''[[The New York Times]]''</ref>
| |
| − | *Tom Stockley, wine writer for the ''[[Seattle Post-Intelligencer]]''.
| |
| − | *Cynthia Oti, a financial talk show host at San Francisco's KSFO-AM.
| |
| − |
| |
| − | ===Initial flight segment===
| |
| − |
| |
| − | Alaska 261 departed from PVR at 1:37 p.m. [[Pacific standard time|PST]], and climbed to its intended cruising altitude of [[flight level]] 310 (31,000 feet). Approximately 2 hours into the flight, the flight crew, consisting of captain Ted Thompson and first officer William "Bill" Tansky, first contacted the airline's dispatch and maintenance control facilities in SEA, and on a shared company radio with operations and maintenance facilities at [[Los Angeles International Airport]] (LAX) discussed a jammed horizontal stabilizer and a possible diversion to LAX.<ref name="NTSB Final">[http://www.ntsb.gov/publictn/2002/AAR0201.pdf Loss of Control and Impact with Pacific Ocean Alaska Airlines Flight 261<!-- Bot generated title -->]</ref> The jammed stabilizer prevented operation of the trim system, which normally would 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 [[Yoke (aircraft)|controls]] with approximately 10 pounds of force to keep level.<ref name="NTSB Final"/> Neither the flight crew, nor company maintenance, were able to determine the cause of the jam.<ref name="NTSB Final"/> Repeated attempts to overcome the jam with the primary and alternate trim systems were unsuccessful<ref name="NTSB Final"/>
| |
| − |
| |
| − | During this time the flight crew had several discussions with the company [[Flight dispatcher|dispatcher]] about whether to divert to LAX, or continue on as planned to SFO. Ultimately the pilots chose to divert.<ref name="NTSB Final"/> 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."<ref name="NTSB Final"/> [[Cockpit Voice Recorder]] (CVR) transcripts indicate that the dispatcher was concerned about the effect on the schedule ("flow") should the flight divert.<ref name="CVR transcript">[http://aviation-safety.net/investigation/cvr/transcripts/cvr_asa261.pdf National Transportation Safety Board<!-- Bot generated title -->]</ref>
| |
| − |
| |
| − | [[Image:Alaska Airlines Flight 261 path.PNG|thumb|Final flight path of Alaska 261]]
| |
| − |
| |
| − | ===First dive and recovery===
| |
| − |
| |
| − | At 4:09 p.m., the flight crew were able to unjam 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 a dive. Alaska 261 went from about 31,500 feet to between 23,000 and 24,000 feet in around 80 seconds.<ref name="NTSB Final"/> Both pilots struggled together to regain control of the aircraft, and only by exerting a pulling force of 130 to 140 pounds on the controls were the flight crew able to arrest the descent of the aircraft and stabilize themselves at approximately 24,400 feet.<ref name="NTSB Final"/>
| |
| − |
| |
| − | Alaska 261 informed [[Air traffic control|Air Traffic Control]] (ATC) of their control problems. After the flight crew stated their intention to land at LAX, ATC inquired if they wanted to proceed to a lower altitude in preparation for approach.<ref name="CVR transcript"/> 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."<ref name="CVR transcript"/> 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.<ref name="NTSB Public">[http://www.ntsb.gov/Events/2000/Aka261/AKA261_board_mtg_transcript.pdf NTSB Board Meeting Transcript 12/10/2002 - Alaska Airlines 261<!-- Bot generated title -->]</ref> 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 start to configure the aircraft for landing at LAX.<ref name="NTSB Final"/>
| |
| − |
| |
| − | ===Second dive and crash===
| |
| − |
| |
| − | ''NTSB Animation: [http://www.ntsb.gov/Events/2000/Aka261/animations/airplane_animation_261.wmv Final pitch-over and initial portion of the dive (.wmv file)]''
| |
| − |
| |
| − | Beginning at 4:19 p.m., the CVR recorded the sounds of at least four distinct "thumps", followed 17 seconds later by an "extremely loud noise". The aircraft rapidly pitched over into a dive.<ref name="NTSB Final"/> Several aircraft in the vicinity had been alerted by ATC to maintain visual contact with the stricken jet and they immediately contacted the controller.<ref name="ATC transcript">[http://aviation-safety.net/investigation/cvr/transcripts/atc_asa261.php Aviation Safety Network > Accident investigation > CVR / FDR > Transcripts > Alaska Airlines Flight 261 - 31 JAN 2000<!-- Bot generated title -->]</ref> 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".<ref name="ATC transcript"/> ATC then tried to contact Alaska 261. Although the CVR captured the co-pilot saying "[[Mayday (distress signal)|Mayday]]", no radio communications were received from the flight crew during the final event.<ref name="CVR transcript"/><ref name="ATC transcript"/>
| |
| − |
| |
| − | The CVR transcript shows the pilots' continuous attempts for the duration of the dive to regain control of the aircraft.<ref name="CVR transcript"/> At one point, unable to raise the nose, they attempted to fly the aircraft "upside-down".<ref name="CVR transcript"/> However the aircraft was beyond recovery, and fell approximately 18,000 feet nose-down and inverted for 1 minute, 21 seconds before impacting the ocean at high speed. At this time, pilots from aircraft in the area reported in, one [[SkyWest]] pilot saying "and he's just hit the water", meaning the plane had plunged into the ocean. Another reported, saying, "Yeah sir he uh he-uh hit the water, he's uh down". Everyone on board died instantly, and the aircraft was destroyed upon impact.<ref name="NTSB Final"/>
| |
| − |
| |
| − | ==The investigation==
| |
| − | ===Wreckage recovery and analysis===
| |
| − |
| |
| − | [[Image:Screwshavings2 sm.PNG|thumbnail|left|155px|Recovered [[jackscrew]]]]
| |
| − |
| |
| − | Using [[side-scan sonar]], [[Remotely operated vehicle|remotely operated vehicles]], and a commercial fishing trawler, workers recovered about 85% of the fuselage (including the tail section) and a majority of the wings. In addition, both engines, as well as the [[Flight Data Recorder]] (FDR) and CVR were retrieved. All wreckage was unloaded at [[Port Hueneme]], California for examination and documentation.<ref name="NTSB Final"/> 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. The jackscrew was found with metallic filaments wrapped around it; these were later determined to be remnants of the threads from the acme nut.<ref name="NTSB Final"/>
| |
| − |
| |
| − | Later analysis estimated that 90% of the threads in the acme nut had been previously worn away, and that they were then completely sheared off during the accident flight. Once the threads failed, the horizontal stabilizer assembly was then subject to aerodynamic forces that it could not withstand, and ultimately failed.<ref name="NTSB Final"/> Based on the time since the last inspection of the jackscrew assembly, the NTSB determined that the wear had occurred at a much faster than average rate (0.012 inch per 1,000 flight hours, when the expected wear was 0.001 inch per 1,000 flight hours).<ref name="NTSB Final"/> The NTSB considered a number of potential reasons for this excessive wear, including the substitution by Alaska Airlines (with the approval of the aircraft manufacturer [[Boeing]]) of Aeroshell 33 grease instead of the previously approved lubricant, Mobilgrease 28. The use of Aeroshell 33 was found not be a factor in this accident.<ref name="NTSB Final"/> 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. Ultimately the lack of lubrication, and resulting excessive wear of the threads, were determined to be the direct causes of the accident.<ref name="NTSB Final"/>
| |
| − |
| |
| − | ''NTSB Animation: [http://www.ntsb.gov/Events/2000/Aka261/animations/jackscrew_261.wmv Longitudinal Trim System Description and Failure Sequence (.wmv file)]''
| |
| − |
| |
| − | ===Identification of passengers===
| |
| − | The following indicators were used to identify crash victims: <ref>"[http://archives.cnn.com/2000/US/02/14/alaska.airlines.03/ Alaska Airlines maintenance records raise new questions]," ''[[CNN]]''</ref>
| |
| − | * Fingerprints
| |
| − | * Dental records
| |
| − | * Tattoos
| |
| − | * Personal items
| |
| − | * Anthropology examinations
| |
| − |
| |
| − | ===Inadequate lubrication and end play checks===
| |
| − |
| |
| − | The investigation then proceeded to examine why scheduled maintenance had failed to adequately lubricate the jackscrew assembly. In interviews with the Alaska Airlines SFO mechanic who last performed the lubrication it was revealed that the task took about 1 hour, whereas the aircraft manufacturer estimated the task should take 4 hours.<ref name="NTSB Final"/> 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."<ref name="NTSB Final"/> Laboratory tests indicated that the excessive wear of jackscrew assembly could not have accumulated in just the 4 months period between the September 1999 maintenance and the accident flight.<ref name="NTSB Final"/> Therefore, the NTSB concluded that "more that just the last lubrication was missed or inadequately performed."<ref name="NTSB Final"/>
| |
| − |
| |
| − | In order to monitor wear on the jackscrew assembly a periodic maintenance inspection called an "end play check" was used. 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.<ref name="NTSB Final"/> 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 for the replacement of the affected components.<ref name="NTSB Final"/>
| |
| − |
| |
| − | ===Extension of maintenance intervals===
| |
| − | Between 1985 and 1996 Alaska Airlines progressively increased the period in between jackscrew lubrication as well as end play checks with the approval of the [[Federal Aviation Administration]] (FAA).<ref name="NTSB Final"/> 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 was not able to determine what information, if any, was presented by Alaska Airlines to the FAA prior to 1996.<ref name="NTSB Final"/> Testimony from a FAA inspector regarding an extension granted in 1996 was that Alaska Airlines submitted documentation from Boeing as justification for their extension.<ref name="NTSB Final"/>
| |
| − |
| |
| − | 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 5 sample airplanes 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.<ref name="NTSB Final"/> 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."<ref name="NTSB Final"/>
| |
| − |
| |
| − | ===FAA oversight===
| |
| − | A special inspection conducted by the FAA in April 2000 of Alaska Airlines uncovered widespread significant deficiencies that "the FAA should have uncovered earlier."<ref name="NTSB Final"/> The investigation concluded that "FAA surveillance of Alaska Airlines had been deficient for at least several years."<ref name="NTSB Final"/> 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."<ref name="NTSB Final"/>
| |
| − |
| |
| − | Systematic 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.<ref name="NTSB Final"/>
| |
| − |
| |
| − | ===Aircraft design and certification issues===
| |
| − | The jackscrew assembly was designed with 2 independent threads, each of which was strong enough to withstand the forces placed on it.<ref name="NTSB Final"/> 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.
| |
| − |
| |
| − | In order for this design component to be approved ("certified") by the FAA without any fail-safe provision, it had to be considered "extremely improbable". This was defined as "having a probability on the order of 1 x 10<sup>-9</sup> or less each flight hour."<ref name="NTSB Final"/> However 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."<ref name="NTSB Final"/>
| |
| − |
| |
| − | ===Jackscrew design improvement===
| |
| − | 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 promise to make progressive failures easy to see and thus complete failures of a jackscrew almost impossible. <ref name="The Failsafe Jackscrew Design">[http://www.iasa.com.au/folders/Safety_Issues/FAA_Inaction/fsjackscrew-1.html The FailSafe Jackscrew Design<!-- Bot generated title -->]</ref>
| |
| − |
| |
| − | ==Conclusions==
| |
| − |
| |
| − | In addition to the probable cause, the NTSB found the following contributing factors:<ref name="NTSB Final"/>
| |
| − | *Alaska Airlines' extended lubrication interval and the FAA's approval of that extension, which increased the likelihood that a missed or inadequate lubrication would result in excessive wear of the acme nut threads
| |
| − | *Alaska Airlines' extended end play check interval and the FAA's approval of that extension, which allowed the excessive wear of the acme nut threads to progress to 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
| |
| − |
| |
| − | [[Image:Routine maintenance on a MD-80 tailplane.PNG|thumbnail|right|250px|Routine maintenance of the tail section 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 a total of 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.<ref name="NTSB Final"/> 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.<ref name="NTSB Final"/>
| |
| − |
| |
| − | In NTSB board member John J. Goglia's statement for the final report, which was concurred with by all three other board members,<ref name="NTSB Final"/> he wrote:
| |
| − |
| |
| − | {{Blockquote|"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."<ref name="NTSB Final"/> '''
| |
| − | }}
| |
| − |
| |
| − | ==Aftermath==
| |
| − | [[Image:Sundial.jpg|left|thumb|Memorial Sundial]]
| |
| − | The families of the victims approved the construction of a memorial [[sundial]] that was placed at [[Port Hueneme]]. The sundial was designed by Santa Barbara artist Bud Bottoms to cast a shadow on a memorial plaque at 4:22 p.m. each January 31st.<ref name="SeattlePI memorial">[http://seattlepi.nwsource.com/local/56506_alaska31.shtml Memorials quieter today, but Flight 261 grief still hurts<!-- Bot generated title -->]</ref>
| |
| − |
| |
| − | For their actions during the emergency, Captain Ted Thompson and First Officer Bill Tansky were awarded the [[Airline Pilots Association]] Gold Medal for Heroism, the only time the award has been given posthumously.<ref name="PI pilot award article">[http://seattlepi.nwsource.com/local/air01.shtml Pilots honored for heroism during crisis<!-- Bot generated title -->]</ref>
| |
| − |
| |
| − | Both Boeing and Alaska Airlines eventually conceded 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.<ref name="SeattlePI lawsuits">[http://seattlepi.nwsource.com/business/129473_alaska04.html All but one suit settled in Flight 261 crash<!-- Bot generated title -->]</ref> Two victims from Alaska 261 were falsely accused of being the fathers of children in Guatemala in an attempt to gain insurance and settlement money. DNA testing revealed these allegations to be false.<ref name="SeattlePI hoax">[http://seattlepi.nwsource.com/hatcher/36075_candy22.shtml Quest for truth proves lawyer's integrity<!-- Bot generated title -->]</ref>
| |
| − |
| |
| − | This crash was featured in a 2004 episode of [[National Geographic Channel]]'s ''[[Mayday (TV series)|Air Crash Investigation]]'' television program (originally known as ''Mayday'' and also known as ''Air Emergency''), titled ''Cutting Corners'' or ''Fatal Error''.
| |
| − |
| |
| − | ''[[Seattle Post-Intelligencer]]'', ''[[Snopes]]'', and ''[[About.com]]'' state that an [[urban legend]] stating that a pastor's wife led the passengers in prayer is false. <ref>"[http://www.snopes.com/glurge/alaska.asp The Plane Gospel Truth]," ''[[Snopes]]''</ref> <ref>"[http://urbanlegends.about.com/library/blflight261.htm Miracle Aboard Flight 261]," ''[[About.com]]''</ref> <ref>"[http://seattlepi.nwsource.com/local/voic031.shtml Flight 261 prayer story spreads via e-mail]," ''[[Seattle Post-Intelligencer]]''</ref>
| |
| − |
| |
| − | The [http://alaskasworld.com/news/2004/06/images/TanskyThompsonForm.pdf Ted Thompson/Bill Tansky Scholarship Fund] was named after the two flight crew members.
| |
| − |
| |
| − | The death of passenger Rodney "Rod" Pearson with his wife Sarah (an Alaska Airlines flight attendant) and their two daughters may have been a critical factor in the demise of the popular Seattle-area restaurant chain Six Degrees, which he co-founded.<ref name="Six Degrees legal action articld">"[http://www.seattleweekly.com/2001-07-18/news/troubled-order.php Troubled order]," ''[[Seattle Weekly]]''</ref>
| |
| − |
| |
| − | The Alaska Airlines flight 261 crash has appeared in various [[Advance fee fraud|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.<ref>"[http://www.law.state.ak.us/pdf/consumer/121305-thompson-cp-alert%20.pdf Nigerian Advance Fee Scam Customized for Alaska: Morris Thompson variation could be taste of ploys to come]." ''State of Alaska Department of Law''.</ref><ref>"[http://blog.seattlepi.nwsource.com/consumersmarts/archives/125509.asp Latest e-mail uses Alaska Airlines crash victims to scam]," ''[[Seattle Post-Intelligencer]]''</ref>
| |
| − |
| |
| − | == References ==
| |
| − | {{reflist|2}}
| |
| − |
| |
| − | ==External links==
| |
| − | * [http://www.ntsb.gov/Events/2000/Aka261/default.htm Main NTSB Alaska Airlines Flight 261 investigation page]
| |
| − | * [http://www.ntsb.gov/publictn/2002/AAR0201.htm NTSB Publication on the Alaska Airlines Flight 261 disaster - Executive Summary]
| |
| − | * [http://www.ntsb.gov/publictn/2002/AAR0201.pdf The NTSB's full report]
| |
| − | * [http://www.ntsb.gov/Events/2000/Aka261/presentations/presentations.htm NTSB investigation presentation material, including animated accident reconstruction]
| |
| − | * [http://www.ntsb.gov/Events/2000/Aka261/jackscrew.htm Photographs of recovered jackscrew]
| |
| − | * [http://lessons.air.mmac.faa.gov/l2/Alaska/ Applying Lessons Learned from Accidents, Alaska Airlines Flight 261] - Informative analysis at faa.gov, with technical diagrams and photos
| |
| − | * [http://seattlepi.nwsource.com/flight261/ ''Seattle Post-Intelligencer'' special report]
| |
| − | * "[http://www.time.com/time/magazine/article/0,9171,38815,00.html?iid=chix-sphere The Fall of Flight 261]," ''[[TIME (magazine)|TIME]]''
| |
| − | *[http://web.archive.org/web/20010212073412/http://www.alaskaair.com/E_latest.asp Archive of Alaska Airlines news reports about 261]
| |
| − | *[http://seattlepi.nwsource.com/local/alas251.shtml A calm 'thank you,' then Alaska 261 fell toward the sea] - Seattlepi.com story about Alaska 261
| |
| − | *[http://archives.cnn.com/2000/US/02/01/alaska.airlines.list/ Names of those aboard Alaska Airlines Flight 261] - ''CNN'' Article with names of victims
| |
| − | *[http://seattlepi.nwsource.com/local/skul02.shtml A child's dream of 'snow every day' is lost - Seattlepi.com] - The story is about the loss of John Hay Elementary School students on Alaska 261
| |
| − | *[http://archives.cnn.com/2000/US/12/13/alaska.airlines.02/index.html Alaska Airlines pilots struggled to save plane] - ''CNN''
| |
| − | *[http://www.cbsnews.com/stories/2000/02/01/national/main155348.shtml The Lives That Were Lost] ''[[CBS News]]''
| |
| − | *[http://seattlepi.nwsource.com/local/past01.shtml The faces of Flight 261's victims]
| |
| − | *[http://www.cbsnews.com/htdocs/plane_crashes/alaska_airlines/framesource.html Alaska Airlines Flight 261], ''[[CBS News]]''
| |
| − | *[http://query.nytimes.com/gst/fullpage.html?res=9F07E3DE133AF93AA25750C0A9669C8B63 Alaska Airlines Center in Turmoil After Complaint by Mechanics] ''[[The New York Times]]''
| |
| − | *[http://www.historylink.org/essays/output.cfm?file_id=2958 Alaska Flight 261 bound for Seattle crashes into the Pacific Ocean on January 31, 2000] - Historylink.org
| |
| − | *[http://seattlepi.nwsource.com/local/hay11.shtml Hay school family' remembers its own]
| |
| − | *[http://www.boston.com/news/daily/01/crash_victim_bios.htm The victims of Flight 261], ''[[The Boston Globe]]''
| |
| − | *[http://www.cbc.ca/world/story/2000/08/04/airlinesafety000804.html Alaska Airlines grounds 18 planes], ''[[CBC News|CBC]]''
| |
| − | *[http://query.nytimes.com/gst/fullpage.html?res=9D05E7DC163EF936A25751C1A9669C8B63&n=Top/Reference/Times%20Topics/Subjects/D/Design Alaska Airlines Crash Hearing Looks at Aircraft Parts Design], ''[[The New York Times]]''
| |
| − | *"[http://web.archive.org/web/20050519085638/http://www.chinfo.navy.mil/navpalib/news/news_stories/alaskaair261.html Navy expands search for debris at Alaska Airlines Flight 261 crash scene]," ''[[United States Navy]]''
| |
| − | *"[http://findarticles.com/p/articles/mi_m0UBT/is_28_14/ai_63302355 Crash Shows Impact of Safety Shortcomings on Bottom Line] ''Air Safety Week''
| |
| − | *"[http://www.sfgate.com/cgi-bin/article.cgi?file=/c/a/2000/02/01/MN54928.DTL&type=printable S.F.-BOUND JET PLUNGES INTO SEA -- 88 FEARED DEAD]
| |
| − | *[http://members.aol.com/colleenmine/collage.htm Memorial site for Colleen Whorley and Monte Donaldson], passengers of Alaska 261
| |
| − | *[http://www.behavioralsafetynow.com/library/powerpoints/HumErrorMawhinn%20BSN%2007.pdf Error Sequence and the loss of 88 souls on Alaska Flight 261]
| |
| − | *[http://www.airliners.net/search/photo.search?&s=1&keywords=N963AS Pre-crash pictures of N963AS]
| |
| − | {{coor title dm|34|03.5|N|119|20.8|W|region:US-CA_type:landmark_scale:1000000}}
| |
| − | [[Category:Airliner crashes caused by maintenance errors]]
| |
| − | [[Category:Accidents and incidents on commercial airliners in the United States]]
| |
| − | [[Category:Aviation accidents and incidents in 2000]]
| |
| − | [[Category:2000 in the United States]]
| |
| − | [[Category:Disasters in California]]
| |
| − |
| |
| − | [[fr:Vol 261 Alaska Airlines]]
| |
| − | [[ja:アラスカ航空261便墜落事故]]
| |
| − | [[fi:Alaska Airlinesin lennon 261 onnettomuus]]
| |
| − | [[zh:阿拉斯加航空261號班機]]
| |
