!! History Commons Alert, Exciting News

Context of '(9:39 a.m.) September 11, 2001: Flight 93 Hijacker Again Warns of Bomb on Board, Flight Controllers Again Overhear; NORAD Still Not Notified'

This is a scalable context timeline. It contains events related to the event (9:39 a.m.) September 11, 2001: Flight 93 Hijacker Again Warns of Bomb on Board, Flight Controllers Again Overhear; NORAD Still Not Notified. You can narrow or broaden the context of this timeline by adjusting the zoom level. The lower the scale, the more relevant the items on average will be, while the higher the scale, the less relevant the items, on average, will be.

The Federal Aviation Administration (FAA) holds a training exercise based on the scenario of an aircraft hijacking, which involves a real plane playing the part of the hijacked aircraft. The exercise will be described to the 9/11 Commission in 2004 by Major Paul Goddard, who is the chief of live exercises for the North American Aerospace Defense Command (NORAD) at the time of the 9/11 attacks. According to Goddard, the exercise, held in 1995, is called “Twin Star” and the FAA invites NORAD to participate in it, “since a real commercial airliner was to be shadowed by a fighter intercept.” Goddard will tell the 9/11 Commission his understanding is that the exercise involves the entire FAA system, and the National Military Command Center (NMCC) at the Pentagon also participates in it. [9/11 Commission, 3/4/2004] Colin Scoggins, the military operations specialist at the FAA’s Boston Center on 9/11, will describe what is apparently this exercise when he is interviewed by the 9/11 Commission in 2003. He will say he believes the exercise is “joint FAA/military” and is conducted “in 1995 or 1996.” According to Scoggins, the exercise involves “a military scramble to escort a hijacked aircraft,” but the fighter jets taking part are “unable to intercept” the mock hijacked plane. [9/11 Commission, 9/22/2003 pdf file] Apparently describing the same exercise in a documentary film, Scoggins will say, “We had run a hijack test years before [9/11] and the fighters never got off on the appropriate heading, and it took them forever to catch up.” [Michael Bronner, 2006]

Entity Tags: North American Aerospace Defense Command, Colin Scoggins, National Military Command Center, Twin Star, Paul Goddard, Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

A Delta Air Lines Boeing 767, the same kind of aircraft as Delta 1989.A Delta Air Lines Boeing 767, the same kind of aircraft as Delta 1989. [Source: Public domain]The FAA’s Cleveland Center incorrectly concludes that Delta Air Lines Flight 1989 has been hijacked, but accounts will conflict over how it comes to this conclusion. [USA Today, 8/13/2002; Spencer, 2008, pp. 167] Delta 1989, a Boeing 767, is currently in the sector of airspace being monitored by Cleveland Center air traffic controller John Werth. [9/11 Commission, 10/2/2003 pdf file; USA Today, 9/11/2008] It is flying west over Pennsylvania, approaching the Ohio border, and is about 25 miles behind Flight 93. FBI agents suspected Delta 1989 might be the next plane to be hijacked and called the Cleveland Center after the second attack on the World Trade Center, with the warning to watch this flight (see Shortly After 9:03 a.m. September 11, 2001). [USA Today, 8/13/2002] A supervisor at the center told Werth to keep an eye on the flight because, as Werth will later recall, “he was a suspected hijacking because he had taken off from Boston at approximately the same time as” the first two hijacked aircraft, Flights 11 and 175. [9/11 Commission, 10/1/2003 pdf file; USA Today, 9/11/2008]
Controllers Hear Suspicious Communications - When, at 9:28, Werth hears the sound of screaming (subsequently determined to have come from Flight 93) over the radio (see (9:28 a.m.) September 11, 2001), he is unsure which of seven or eight possible aircraft it is coming from. The radio frequency is put on the speaker so other controllers can hear it, and they subsequently make out the words, “get out of here.” [9/11 Commission, 10/1/2003 pdf file; 9/11 Commission, 7/24/2004, pp. 11, 28]
Controllers Think Delta 1989 Is Hijacked - According to USA Today, when Cleveland Center controllers then hear a voice with a heavy accent over the radio, saying “Ladies and gentlemen: Here the captain.… We have a bomb on board” (see (9:32 a.m.) September 11, 2001), they mistakenly think it is coming from Delta 1989, not Flight 93. They suspect the flight has been hijacked, and start informing their chain of command. “Officials at Cleveland Center rush word to Washington: Hijackers have another flight. At the Federal Aviation Administration’s Command Center in Herndon, Virginia, Delta Flight 1989 joins a growing list of suspicious jets.” [USA Today, 8/13/2002; 9/11 Commission, 7/24/2004, pp. 12]
Werth Decides Hijacked Aircraft Is Flight 93 - Werth then calls all of the aircraft in his sector, and Flight 93 is the only one that does not respond. He also sees Flight 93 go into a quick descent and then come back up again. Werth therefore concludes that it is Flight 93, not Delta 1989, that has been hijacked, and instructs his supervisor to “tell Washington” of this. [9/11 Commission, 10/1/2003 pdf file; 9/11 Commission, 10/2/2003 pdf file] However, events in the following minutes will cause Cleveland Center controllers to remain suspicious of Delta 1989 (see (Shortly After 9:44 a.m.) September 11, 2001 and 9:45 a.m. September 11, 2001). [USA Today, 8/13/2002; 9/11 Commission, 10/2/2003 pdf file; Spencer, 2008, pp. 168; USA Today, 9/11/2008]
Book Gives Alternative Account - In a book published in 2008, author Lynn Spencer will give a different explanation for why Cleveland Center becomes suspicious of Delta 1989. According to her account, after hearing a later radio transmission where a hijacker again says “There is a bomb on board” (see (9:39 a.m.) September 11, 2001), Werth begins to hand off his flights to other controllers so he can devote his full attention to Flight 93. “In the distraction of the emergency, the crew of Delta 1989 misses the hand-off to the new frequency. The new sector controller for Delta 1989 calls out to the plane several times and gets no response.” As a result, “News travels fast,” and “Soon, word on the FAA’s open teleconference call is that a fifth aircraft is out of radio contact: Delta 1989… is added to the list of suspect aircraft.” [Spencer, 2008, pp. 167] At 9:39 a.m., even though it is not responsible for handling Delta 1989, the FAA’s Boston Center will call NORAD’s Northeast Air Defense Sector (NEADS) and incorrectly tell it that Delta 1989 is another possible hijack (see 9:39 a.m. September 11, 2001). [9/11 Commission, 2004; Vanity Fair, 8/1/2006]

Entity Tags: John Werth, Cleveland Air Route Traffic Control Center, Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The Flight 93 hijackers (probably inadvertently) transmit over the radio: “Hi, this is the captain. We’d like you all to remain seated. There is a bomb on board. And we are going to turn back to the airport. And they had our demands, so please remain quiet.” [Boston Globe, 11/23/2001; Longman, 2002, pp. 209; MSNBC, 9/3/2002; 9/11 Commission, 6/17/2004] The controller responds, “United 93, understand you have a bomb on board. Go ahead,” but there is no response. There was a very similar “bomb on board” warning from the same flight at 9:32 a.m. (see (9:32 a.m.) September 11, 2001). The 9/11 Commission indicates that these are separate incidents. [9/11 Commission, 6/17/2004] Cleveland flight control apparently continues to wait for FAA superiors to notify NORAD. Earlier in the morning, Boston flight control directly contacted NORAD (see (8:37 a.m.) September 11, 2001) and local air force bases when they determined Flight 11 was hijacked.

Entity Tags: North American Aerospace Defense Command, Cleveland Air Route Traffic Control Center, Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

On the evening of September 11, the Federal Aviation Administration (FAA) and the military decline to comment on whether fighter jets were launched to intercept any of the hijacked aircraft earlier in the day. Laura Brown, an FAA spokeswoman, refuses to say whether the agency requested military intercepts. Major Barry Venable, a spokesman for the North American Aerospace Defense Command (NORAD), similarly says he does not know whether the FAA asked NORAD to send up jets to intercept the errant aircraft. Lt. Col. Margaret Quenneville, a spokeswoman for the 102nd Fighter Wing of the Massachusetts Air National Guard, which operates from Otis Air National Guard Base at Cape Cod, refuses to comment on whether the fighter wing was requested to intercept the hijacked airliners. [Cape Cod Times, 9/12/2001; Cape Cod Times, 9/12/2001] Several days later, it will be revealed that two F-15s were indeed launched from Otis around the time the first WTC tower was hit, and three F-16s were launched from Langley Air Force Base in Virginia shortly before the time the Pentagon was hit (see September 14, 2001). [CBS News, 9/14/2001; Cape Cod Times, 9/16/2001; North American Aerospace Defense Command, 9/18/2001] But as late as September 15, the New York Times is reporting, “The Federal Aviation Administration has officially refused to discuss its procedures or the sequence of events on Tuesday morning, saying these are part of the Federal Bureau of Investigation’s inquiry.” [New York Times, 9/15/2001]

Entity Tags: Federal Aviation Administration, Margaret Quenneville, Barry Venable, North American Aerospace Defense Command, Laura Brown

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Ordering 

Time period


Email Updates

Receive weekly email updates summarizing what contributors have added to the History Commons database

 
Donate

Developing and maintaining this site is very labor intensive. If you find it useful, please give us a hand and donate what you can.
Donate Now

Volunteer

If you would like to help us with this effort, please contact us. We need help with programming (Java, JDO, mysql, and xml), design, networking, and publicity. If you want to contribute information to this site, click the register link at the top of the page, and start contributing.
Contact Us

Creative Commons License Except where otherwise noted, the textual content of each timeline is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike