!! 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.

Tech. Sgt. Jeremy Powell.Tech. Sgt. Jeremy Powell. [Source: Scott A. Gwilt/ Rome Sentinel]The FAA’s Boston Center calls NORAD’s Northeast Air Defense Sector (NEADS) in Rome, NY, to alert it to the suspected hijacking of Flight 11. According to the 9/11 Commission, this is “the first notification received by the military—at any level—that American 11 had been hijacked.” [9/11 Commission, 7/24/2004, pp. 20; 9/11 Commission, 8/26/2004, pp. 13 pdf file] The call is made by Joseph Cooper, an air traffic controller at the Boston Center, and answered by Jeremy Powell, a technical sergeant on the NEADS operations floor. [Vanity Fair, 8/1/2006; Spencer, 2008, pp. 25] Beginning the call, Cooper says: “Hi. Boston Center TMU [traffic management unit], we have a problem here. We have a hijacked aircraft headed towards New York, and we need you guys to, we need someone to scramble some F-16s or something up there, help us out.” Powell replies, “Is this real-world or exercise?” Cooper answers, “No, this is not an exercise, not a test.” [9/11 Commission, 7/24/2004, pp. 20] Shortly into the call, Powell passes the phone on to Lieutenant Colonel Dawne Deskins (see (8:38 a.m.) September 11, 2001). Deskins identifies herself to Cooper, and he tells her, “We have a hijacked aircraft and I need you to get some sort of fighters out here to help us out.” [Newhouse News Service, 1/25/2002; ABC News, 9/11/2002; Bamford, 2004, pp. 8; Spencer, 2008, pp. 26]
Military Claims Call Goes against Procedure - The 1st Air Force’s official history of the response to the 9/11 attacks will later suggest that Boston Center is not following normal procedures when it makes this call to NEADS. It states: “If normal procedures had taken place… Powell probably wouldn’t have taken that phone call. Normally, the FAA would have contacted officials at the Pentagon’s National Military Command Center who would have contacted the North American Aerospace Defense Command. The secretary of defense would have had to approve the use of military assets to assist in a hijacking, always considered a law enforcement issue.” The only explanation it gives for this departure from protocol is that “nothing was normal on Sept. 11, 2001, and many say the traditional chain of command went by the wayside to get the job done.” [Filson, 2003, pp. 51]
Accounts Conflict over Time of Call - There will be some conflict between different accounts, as to when this vital call from Boston Center to NEADS occurs. An ABC News documentary will indicate it is made as early as 8:31 a.m. [ABC News, 9/11/2002] Another ABC News report will state, “Shortly after 8:30 a.m., behind the scenes, word of a possible hijacking [reaches] various stations of NORAD.” [ABC News, 9/14/2002] NEADS logs indicate the call occurs at 8:40 a.m., and NORAD will report this as the time of the call in a press release on September 18, 2001. [Federal Aviation Administration, 9/17/2001 pdf file; North American Aerospace Defense Command, 9/18/2001] The 8:40 time will be widely reported in the media prior to the 9/11 Commission’s 2004 report. [Associated Press, 8/21/2002; BBC, 9/1/2002; Newsday, 9/10/2002; CNN, 9/11/2002] But tape recordings of the NEADS operations floor that are referred to in the 9/11 Commission Report place the call at 8:37 and 52 seconds. [9/11 Commission, 7/24/2004, pp. 20; Vanity Fair, 8/1/2006] If the 8:37 a.m. time is correct, this would mean that air traffic controllers have failed to successfully notify the military until approximately 12 minutes after they became certain that Flight 11 had been hijacked (see (8:25 a.m.) September 11, 2001), 16 minutes after Flight 11’s transponder signal was lost (see (Between 8:13 a.m. and 8:21 a.m.) September 11, 2001), and 24 minutes after the plane’s pilots made their last radio contact (see 8:13 a.m. September 11, 2001). [9/11 Commission, 6/17/2004] At 8:34, the Boston Center tried contacting the military through the FAA’s Cape Cod facility, which is located on Otis Air National Guard Base, but was told that it needed to call NEADS (see 8:34 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20; Spencer, 2008, pp. 22]

Entity Tags: Boston Air Route Traffic Control Center, Dawne Deskins, North American Aerospace Defense Command, Joseph Cooper, Northeast Air Defense Sector, Jeremy Powell

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

At the FAA’s Cleveland Center, an air traffic controller hears a transmission, presumably made by Flight 93 hijacker-pilot Ziad Jarrah, stating: “Ladies and gentlemen: Here the captain, please sit down, keep remaining sitting. We have a bomb on board. So, sit.” [9/11 Commission, 7/24/2004, pp. 12; 9/11 Commission, 8/26/2004, pp. 39 pdf file] As the 9/11 Commission later notes, “Like [Mohamed] Atta on Flight 11, Jarrah apparently did not know how to operate the communication radios; thus his attempts to communicate with the passengers were broadcast on the [air traffic control] channel.” [9/11 Commission, 8/26/2004, pp. 98 pdf file] While this communication is assumed to have come from Flight 93, an early FAA report states that it came “from an unknown origin.” [Federal Aviation Administration, 9/17/2001 pdf file] According to Newsweek, just prior to the communication, Cleveland Center controllers heard the sound of screaming from the flight. [Newsweek, 9/22/2001] The 9/11 Commission states that, around the time of the transmission, the plane’s cockpit voice recording indicates “that a woman, most likely a flight attendant, was being held captive in the cockpit. She struggled with one of the hijackers who killed or otherwise silenced her.” [9/11 Commission, 7/24/2004, pp. 12; 9/11 Commission, 8/26/2004, pp. 39 pdf file] Though the Cleveland air traffic controller understands the hijacker’s communication, he responds to it: “Calling Cleveland Center, you’re unreadable. Say again, slowly.” He also notifies his supervisor who passes the information up the chain of command, and the FAA’s Command Center is subsequently informed, “United 93 may have a bomb on board.” At 9:34 the Command Center will relay this information to FAA headquarters (see 9:34 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 28]

Entity Tags: Cleveland Air Route Traffic Control Center, 9/11 Commission, 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

The FAA’s Cleveland Center notifies the FAA’s Great Lakes Regional Operations Center about the screams and statements it heard from an unknown origin, but that are believed to have come from Flight 93. These transmissions were heard between 9:28 and 9:39 (see (9:28 a.m.) September 11, 2001, (9:32 a.m.) September 11, 2001 and (9:39 a.m.) September 11, 2001). [Federal Aviation Administration, 9/17/2001 pdf file] The FAA’s Herndon Command Center and Washington headquarters were alerted to Flight 93 several minutes earlier (see 9:34 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 39 pdf file]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The FAA’s Cleveland Center receives a call from NORAD’s Northeast Air Defense Sector (NEADS), incorrectly notifying it that Delta Air Lines Flight 1989 is a confirmed hijacking. A supervisor then rushes around the center, informing all the controllers and managers of this. [9/11 Commission, 10/2/2003 pdf file; 9/11 Commission, 10/2/2003 pdf file; 9/11 Commission, 2004]
Cleveland Realized Delta 1989 Not Hijacked - At around 9:30 a.m., Cleveland Center air traffic controllers heard the sounds from Flight 93 as it was being hijacked, but initially thought these came from Delta 1989 (see (9:28 a.m.-9:33 a.m.) September 11, 2001). [USA Today, 8/13/2002] Due to the Delta pilots’ normal responses to subsequent radio transmissions, John Werth—the controller monitoring both flights—concluded that the hijacked aircraft was in fact Flight 93. [9/11 Commission, 10/1/2003 pdf file; USA Today, 9/11/2008] However, at around 9:39, the FAA’s Boston Center guessed that Delta 1989 might be hijacked and called NEADS to report the plane as a possible hijacking (see 9:39 a.m. September 11, 2001). [9/11 Commission, 2004; 9/11 Commission, 7/24/2004, pp. 28] NEADS then begins alerting FAA centers of this. [Vanity Fair, 8/1/2006]
NEADS Calls Cleveland Center - Greg Dukeman, the military operations specialist in the traffic management unit at Cleveland Center, receives a call from a female member of staff at NEADS, one of its ID technicians. He passes the call on to supervisor Kim Wernica. The caller says Delta 1989 is “a confirmed hijack.” Wernica then goes “running back and forth” around the center, informing controllers and managers of what she has been told. [North American Aerospace Defense Command, 9/11/2001; 9/11 Commission, 10/2/2003 pdf file; 9/11 Commission, 10/2/2003 pdf file; 9/11 Commission, 2004]
Controller Disputes NEADS's Information - Wernica rushes up to John Werth and tells him, “It’s the Delta, it’s the Delta!” She says a military liaison on the phone has confirmed that the Delta jet has been hijacked. Werth responds that he is pretty sure that Flight 93, not Delta 1989, has been hijacked. When Wernica returns a few moments later, Werth tells her that Delta 1989 is “fine—at least for now.” Wernica consults again on the phone and then comes back, saying, “They said it’s a confirmed hijack and a bomb threat.” Werth thinks to himself that the bomb threats had come from Flight 93 (see (9:32 a.m.) September 11, 2001 and (9:39 a.m.) September 11, 2001), and is therefore convinced the caller must be confusing the two flights. He tells Wernica, “Tell them they’re full of it!” [9/11 Commission, 10/1/2003 pdf file; USA Today, 9/11/2008]

Entity Tags: John Werth, Kim Wernica, Greg Dukeman, Northeast Air Defense Sector, Cleveland Air Route Traffic Control Center

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