!! History Commons Alert, Exciting News

Context of '9:40 a.m. September 11, 2001: Cleveland Center Notifies Regional Operations Center about Flight 93'

This is a scalable context timeline. It contains events related to the event 9:40 a.m. September 11, 2001: Cleveland Center Notifies Regional Operations Center about Flight 93. 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.

Personnel at United Airlines’ headquarters, near Chicago, are subjected to a surprise training exercise in which they are led to believe that one of their planes has crashed, and their experience with this exercise allegedly means they will be better able to respond to the 9/11 attacks. [USA Today, 8/12/2002; 9/11 Commission, 11/20/2003 pdf file; Studdert, 5/26/2015 pdf file; Dubuque Telegraph Herald, 11/12/2015]
Manager Is Concerned that the Airline Is Unprepared for an Accident - Andy Studdert, United Airlines’ chief operating officer, has been concerned that, since it hasn’t suffered a real accident in over 15 years, United Airlines is unprepared to respond properly should one occur now. “I was worried we’d become cocky,” he will later comment. “We thought it couldn’t happen to us.” Around March this year, therefore, he told the airline’s other managers, “One of these days, I’m gonna come in here and I’m gonna do a no-notice drill.” [Center for Values-Driven Leadership, 3/15/2012; Center for Values-Driven Leadership, 4/26/2012] A “no-notice” drill is an exercise that is conducted without its participants being given any formal advance notice of when it will occur. [US Department of Justice, 5/21/2000; Inglesby, Grossman, and O'Toole, 2/1/2001; Oak Ridge Institute for Science and Education, 10/15/2011]
Pilot Is Told to Pretend His Plane Is Experiencing an Emergency - Today, Studdert holds this no-notice exercise. Only a few people know about it in advance. Studdert tells a United Airlines employee who he will refer to as his “safety guy” to contact the pilot of a flight to Australia and give them some instructions. The pilot is therefore told he needs to call in during his flight and report an emergency. He should say there is an “uncontained number three engine failure, rapid descent, decompression,” but stop talking halfway through the word “decompression” and then go silent. He should also turn off the plane’s transponder. [Center for Values-Driven Leadership, 3/15/2012; Dubuque Telegraph Herald, 11/12/2015] (A transponder is a device that sends an aircraft’s identifying information, speed, and altitude to air traffic controllers’ radar screens. [Washington Post, 9/16/2001] )
Airline Personnel Think One of Their Planes Has Crashed - The simulated emergency takes places this afternoon. At around 2 o’clock, Studdert is interrupted by his secretary, Maryann Irving, who rushes into his office and tells him a Boeing 747 has lost contact while flying over the Pacific Ocean. In response, he runs to the airline’s operations center. [Wall Street Journal, 10/15/2001; Center for Values-Driven Leadership, 3/15/2012] Airline employees believe the apparently troubled aircraft has crashed. Some of them are upset and some become physically ill. [Dubuque Telegraph Herald, 11/12/2015] “There are people throwing up in the hall; there are people crying; there are people just staring out the windows,” Studdert will describe.
Personnel Think the Crisis Is Real for 30 Minutes - Since no one in the operations center is able to contact the apparently troubled aircraft, Studdert opens the airline’s crisis center. [Center for Values-Driven Leadership, 3/15/2012] The crisis center, according to journalist and author Jere Longman, is “a terraced, theater-like room that resembled NASA’s Mission Control.” [Longman, 2002, pp. 77] Opening it, according to Studdert, is a significant course of action. When this happens, everyone working for the airline becomes responsible either for running the airline or acting to support the management of the emergency. This means that “3,000 people are put on an immediate activation.” [Center for Values-Driven Leadership, 4/23/2012] United Airlines employees believe one of their planes has crashed for about 30 minutes and then Studdert reveals that the apparent catastrophe is just an exercise scenario. [USA Today, 8/12/2002] He gets on the crisis center’s communications link, which, he will say, “has got 170 stations and people all over the country, all over the world,” and announces, “This has been a no-notice drill; there is no event; everything’s fine.”
Employees Are Furious about the Exercise - The reaction to the exercise in the days after it takes place will be particularly bitter and Studdert will face severe criticism for running it. “I had the board members calling; I had the unions demanding I be fired; I had people telling me I’m the most evil person in the world,” he will recall. [Center for Values-Driven Leadership, 3/15/2012; Center for Values-Driven Leadership, 4/26/2012] Some employees “wanted to kill me,” he will say.
Exercise Has Similarities to the Situation Experienced on September 11 - It is unclear whether Studdert’s exercise has a beneficial or a detrimental effect on the ability of United Airlines to respond to the hijackings 12 days later, on September 11. Studdert will claim that it prepares employees to manage the events of September 11 and reveals weaknesses, such as outdated phone numbers, which are quickly corrected. [Center for Values-Driven Leadership, 4/26/2012; Dubuque Telegraph Herald, 11/12/2015] “It’s amazing, after 9/11… how many people came up to me and thanked me [for running the exercise], because we were ready,” he will say. [Center for Values-Driven Leadership, 3/15/2012] It is possible, however, that it will cause some United Airlines employees to initially think the reports about the terrorist attacks on September 11 are part of another exercise, although accounts are contradictory (see (8:50 a.m.-9:03 a.m.) September 11, 2001). [USA Today, 8/12/2002; Chicago Tribune, 7/16/2003] The scenario of Studdert’s exercise in fact has some similarities with the situation that operations center personnel have to deal with on September 11. On that day, communication with Flight 175—the first of the two United Airlines planes that are hijacked—will be lost (see 8:51 a.m.-8:53 a.m. September 11, 2001) and the plane will have its transponder code changed, although the transponder will not be turned off (see 8:46 a.m.-8:47 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 20-21] Communication will subsequently be lost with Flight 93—the second United Airlines plane to be hijacked (see 9:27 a.m. September 11, 2001 and (9:29 a.m.) September 11, 2001)—and that plane’s transponder will be turned off (see (9:40 a.m.) September 11, 2001). [9/11 Commission, 8/26/2004, pp. 38-39, 43]
Crisis Center Holds Quarterly Exercises - The United Airlines crisis center usually runs exercises four times a year. Most of these deal with safety issues, but security scenarios are also rehearsed, according to Ed Soliday, the airline’s vice president of safety and security. Typically, the 9/11 Commission will be told, these exercises “are scripted” and based around an act of bioterrorism or an international incident. United Airlines has also practiced hijacking scenarios, according to Soliday, although none of these dealt with the threat of an aircraft being used as a weapon. [9/11 Commission, 11/20/2003 pdf file; 9/11 Commission, 11/21/2003 pdf file]

Entity Tags: Andrew P. Studdert, Maryann Irving, United Airlines, Ed Soliday

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Shortly after air traffic controllers ask Flight 11 to climb to 35,000 feet, its transponder stops transmitting. A transponder is an electronic device that identifies a plane on a controller’s screen and gives its exact location and altitude. Among other vital functions, it is also used to transmit a four-digit emergency hijack code. Flight control manager Glenn Michael later says, “We considered it at that time to be a possible hijacking.” [Christian Science Monitor, 9/13/2001; MSNBC, 9/15/2001; Associated Press, 8/12/2002] Initial stories after 9/11 suggest the transponder is turned off around 8:13 a.m., but Pete Zalewski, the air traffic controller handling the flight, later says the transponder is turned off at 8:20 a.m. [MSNBC, 9/11/2002] The 9/11 Commission places it at 8:21 a.m. [9/11 Commission, 6/17/2004] Colonel Robert Marr, head of NEADS, claims the transponder is turned off some time after 8:30 a.m. where the Flight 11 hijack was first detected a.m. [ABC News, 9/11/2002]

Entity Tags: Pete Zalewski, Glenn Michael, Robert Marr

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to Terry Biggio, the operations manager at the FAA’s Boston Center, the center initially thought Flight 11 “was a catastrophic electrical failure and… was diverting to New York” (see (8:21 a.m.) September 11, 2001). [Federal Aviation Administration, 10/19/2002] However, at about 8:24 a.m., controllers heard two radio transmissions from it, with the voice of a hijacker declaring, “We have some planes” (see 8:24 a.m. September 11, 2001). Pete Zalewski, who is handling Flight 11, says that after the second of these: “I immediately knew something was very wrong. And I knew it was a hijack.” He alerts his supervisor. Lino Martins, another Boston air traffic controller, says, “the supervisor came over, and that’s when we realized something was serious.” [Christian Science Monitor, 9/13/2001; MSNBC, 9/11/2002; 9/11 Commission, 6/17/2004] However, two senior FAA officials—Bill Peacock and David Canoles—later say that the hijacker transmissions were not attributed to a flight, so controllers didn’t know their origin. [Washington Times, 9/11/2002] An early FAA report will similarly refer to them as having come “from an unknown origin.” But right away, the center begins notifying the chain of command that a suspected hijacking is taking place (see 8:25 a.m. September 11, 2001). [Federal Aviation Administration, 9/17/2001 pdf file] However, some reports claim that controllers decided Flight 11 was probably hijacked earlier than this, by about 8:20 a.m. (see (8:20 a.m.) September 11, 2001).

Entity Tags: Pete Zalewski, Lino Martins

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The air traffic control tower at Otis Air National Guard Base.The air traffic control tower at Otis Air National Guard Base. [Source: CapeCodFD.com]Daniel Bueno, a supervisor at the FAA’s Boston Center, calls the air traffic control tower at Otis Air National Guard Base to alert it to the problems with Flight 11 and request military assistance. [Filson, 2003, pp. 47; Spencer, 2008, pp. 22] Otis Air Base, at Cape Cod, Massachusetts, is one of NORAD’s seven alert sites in the continental United States, which keeps two armed fighter jets ready for immediate takeoff. [Filson, 2003, pp. 50; 9/11 Commission, 7/24/2004, pp. 17]
Supervisor Calls Otis, Violating Protocol - Bueno calls the control tower at Otis even though, according to author Lynn Spencer, he “knows it’s not standard operating procedure to call the military directly—that’s supposed to be done by FAA headquarters.” But he has “checked the FAA regulation manual, and in the back under section FAAO 7610.4J, Appendix 16, it states that fighters can be launched directly at FAA request, so he is going to make that happen. He may not be FAA headquarters, but he is FAA!” [Spencer, 2008, pp. 22]
Bueno Requests Fighters, Told to Call NEADS - Bueno tells the controller at the Otis tower that Flight 11 has lost its identification signal and appears to be headed toward Manhattan; it looks like a possible hijacking, and fighter jets are needed, fast. [Filson, 2003, pp. 47] But the controller tells Bueno that he must follow the protocol, which is to contact NORAD’s Northeast Air Defense Sector (NEADS). The controller says: “You’ve got to go through the proper channels. They’re the only ones with the authority to initiate a scramble order.” [Spencer, 2008, pp. 22] Bueno asks the controller for the telephone number for NEADS. [102nd Fighter Wing, 2001] Following this call, the tower controller will contact the Otis Air Base operations desk, to let it know that it might be receiving a call from NEADS (see (Between 8:31 a.m. and 8:40 a.m.) September 11, 2001). [Spencer, 2008, pp. 27]
Otis Pilots Critical of Bueno - The two alert pilots at Otis Air Base will later criticize Bueno for calling the base directly. One of them, Major Daniel Nash, will complain: “It sounds like the FAA didn’t have their [act] together at all when they were calling the [Otis] tower.… To me, it sounded like there was someone who didn’t know what they were doing.” [Boston Globe, 9/11/2005] Lieutenant Colonel Timothy Duffy, the other alert pilot, will comment: “It didn’t happen the way it was supposed to.… We were the ones who were contacted right away and knew about it before the air defense sector.” [Filson, 2003, pp. 50]
Time of Call Unclear - Bueno also calls the FAA’s Cape Terminal Radar Approach Control (TRACON), which is located on Otis Air Base, at 8:34 a.m. and requests that fighters be launched from Otis (see 8:34 a.m. September 11, 2001). [Federal Aviation Administration, 4/19/2002; 9/11 Commission, 9/22/2003 pdf file] Whether he makes that call before or after he calls the Otis tower is unstated. According to the 9/11 Commission Report, “the first notification received by the military—at any level—that American 11 had been hijacked” is when the FAA’s Boston Center calls NEADS just before 8:38 a.m. (see (8:37 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20] If that is correct, it would indicate that Bueno calls the Otis tower after he calls the Cape TRACON.

Entity Tags: Daniel Bueno, Boston Air Route Traffic Control Center, Daniel Nash, Otis Air National Guard Base, Timothy Duffy

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Lieutenant Colonel Timothy Duffy.Lieutenant Colonel Timothy Duffy. [Source: CBC]After being informed of the possible hijacking of Flight 11, an air traffic controller in the control tower at Otis Air National Guard Base calls the base’s operations desk to let it know that it might be receiving a call from NORAD’s Northeast Air Defense Sector (NEADS). [Spencer, 2008, pp. 27-28] Daniel Bueno, a supervisor at the FAA’s Boston Center, has just called the control tower at Otis Air Base, at Cape Cod, Massachusetts, alerting it to the problems with Flight 11 and requesting military assistance. The controller who took the call told Bueno he needed to call NEADS in order to get fighter jets launched (see (Between 8:30 a.m. and 8:40 a.m.) September 11, 2001). [Filson, 2003, pp. 47; Spencer, 2008, pp. 22]
Tower Controller Calls Operations Desk - According to author Lynn Spencer, the tower controller subsequently “figures a call [to Otis Air Base] will be coming from NEADS soon and a scramble order is likely. He knows the fighter pilots will appreciate the heads-up.” He therefore calls the Otis Air Base operations desk. According to Spencer, the phone is answered by Master Sergeant Mark Rose, who is the superintendent of aviation management, in charge of flight records and currency for the pilots of the 102nd Fighter Wing. [Spencer, 2008, pp. 27] But according to the 102nd Fighter Wing’s own history of the 9/11 attacks, the call is answered by a Technical Sergeant “Margie Woody.” [102nd Fighter Wing, 2001]
Controller Confuses Superintendent - Rose (or Woody, if the wing’s account is correct) is initially confused by the call. The tower controller does not identify himself or say where he is calling from, but instead begins by asking, “What do you have available?” As Spencer will describe, “For all [Rose] knows, this could be a wrong number or a crank call,” so rather than giving information about the base, Rose responds, “What are you talking about?” The controller then identifies himself and explains that he has just received a report about a hijacking. Rose realizes he needs to pass the call on to someone more appropriate.
Pilot Informed of Hijacking - Pilot Lieutenant Colonel Timothy Duffy, who is the director of operations for the 102nd Fighter Wing, is standing next to Rose by the operations desk. Rose tells him, “Duff, you got a phone call,” and then says the caller is “Otis tower—something about an apparent hijacking under way: American 11, a 767, out of Boston and headed for California.” [Spencer, 2008, pp. 27-28] Duffy will later recall his response to this news: “As soon as we heard there was something about a hijacking we got moving.” [Filson, 2003, pp. 50] On his handheld radio he calls Major Daniel Nash, who along with Duffy is an “alert” pilot on duty at this time, and instructs him to suit up ready for any scramble call. [Spencer, 2008, pp. 28] The two pilots will run to the nearby locker room, put on their G-suits and helmets, and then head out toward their jets (see (8:40 a.m.) September 11, 2001). [Cape Cod Times, 8/21/2002; Boston Globe, 9/11/2005] Meanwhile, a commander at Otis will phone NEADS to report the FAA’s request for military assistance (see Shortly After 8:37 a.m. September 11, 2001).
Call Is Not 'the First Notification Received by the Military' - The exact time the tower controller calls the operations desk at is unclear. Duffy will later guess that the call occurs “at about 8:30, 8:35.” [Filson, 10/22/2002; Filson, 2003, pp. 50] But according to the 9/11 Commission Report, “the first notification received by the military—at any level—that American 11 had been hijacked” is when the FAA’s Boston Center calls NEADS just before 8:38 a.m. (see (8:37 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20] According to the102nd Fighter Wing’s history of the 9/11 attacks, the call to the operations desk is made at 8:38 a.m. [102nd Fighter Wing, 2001] Bueno also called the FAA’s Cape Terminal Radar Approach Control (TRACON), which is located on Otis Air Base, at 8:34 a.m., to request that fighters be launched from Otis (see 8:34 a.m. September 11, 2001), and in response, the TRACON contacts the Otis tower and operations desk (see (8:36 a.m.-8:41) September 11, 2001). [Federal Aviation Administration, 4/19/2002; 9/11 Commission, 9/22/2003 pdf file; 9/11 Commission, 9/30/2003 pdf file]

Entity Tags: Timothy Duffy, Otis Air National Guard Base, Daniel Nash

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Cape TRACON.Cape TRACON. [Source: FAA]Daniel Bueno, a supervisor at the FAA’s Boston Center, contacts the FAA’s Cape Terminal Radar Approach Control (TRACON), located on Otis Air National Guard Base at Cape Cod, Massachusetts, to alert it to the possible hijacking of Flight 11 and request that it arrange for military assistance in response. [Federal Aviation Administration, 9/17/2001 pdf file; Federal Aviation Administration, 4/19/2002; 9/11 Commission, 2004; 9/11 Commission, 7/24/2004, pp. 20]
Bueno Requests Fighters - After his call is initially answered by an air traffic controller at the Cape TRACON, Bueno is quickly passed on to Tim Spence, an operational supervisor at the facility. Bueno says, “I have a situation with American 11, a possible hijack.” He adds that Flight 11 “departed Boston, going to LAX [Los Angeles International Airport]. Right now he’s south of Albany.” He says, “I’d like to scramble some fighters to go tail him.” Spence replies that he will contact Otis Air Base about the situation, and tells Bueno, “I’ll talk to these guys over here and see what we can do.” Bueno then adds that Flight 11 is currently airborne, is about 40 miles south of Albany, and is visible only on primary radar. [Federal Aviation Administration, 4/19/2002; 9/11 Commission, 9/30/2003 pdf file] Bueno also calls the air traffic control tower at Otis Air Base around this time, to alert it to Flight 11 and request military assistance (see (Between 8:30 a.m. and 8:40 a.m.) September 11, 2001). [Filson, 2003, pp. 47; Spencer, 2008, pp. 22] Whether he makes that call before or after he calls the Cape TRACON is unstated. Immediately after receiving the call from Bueno, Spence will call the Otis control tower to inform it of the situation, and he then calls the operations desk at Otis Air Base to let it know that it may be receiving orders (presumably from NEADS, NORAD’s Northeast Air Defense Sector) soon (see (8:36 a.m.-8:41) September 11, 2001). [9/11 Commission, 9/30/2003 pdf file]
Bueno Supposedly Violating Protocol - Bueno will say he decided to call the Cape TRACON based on his memory of a previous aircraft hijacking. [9/11 Commission, 9/22/2003 pdf file] But according to the 9/11 Commission Report, by trying to get military assistance through the TRACON, the “Boston Center did not follow the protocol in seeking military assistance through the prescribed chain of command.” [9/11 Commission, 7/24/2004, pp. 20] Indeed, Bueno will tell the 9/11 Commission that he knows his call should instead be to NEADS, “but due to the urgency of the circumstance [he] called directly to the FAA contact point for Otis.” [9/11 Commission, 9/22/2003 pdf file] And Spence will tell the Commission that arranging for fighters to be scrambled in response to a hijacking “is not the typical responsibility of an operations supervisor with the FAA,” like himself. He will also say that it is “unusual for the [air traffic control] centers to contact TRACON for information. Normally the FAA receives the call from the military for a scramble, but this time it went the other way around, and then the official order came back down from the military.” [9/11 Commission, 9/30/2003 pdf file]
Bueno Praised by Colleagues for Actions - However, according to the 9/11 Commission, “Bueno gets high marks” from the Boston Center personnel it interviews, “for instinctively calling FAA traffic approach personnel at the location where he knew the fighters to be—Otis [Air National Guard Base].” Even Colin Scoggins, the Boston Center’s military liaison, “who knew that the call had to go to NEADS, did not fault Bueno for trying to call the Air Force wing directly through other FAA personnel.” [9/11 Commission, 9/22/2003 pdf file]

Entity Tags: Cape Terminal Radar Approach Control, Daniel Bueno, Boston Air Route Traffic Control Center, Tim Spence

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Colin Scoggins, the military liaison at the FAA’s Boston Center, claims he makes his first call to NORAD’s Northeast Air Defense Sector (NEADS) regarding Flight 11. He later recalls that he informs NEADS that the aircraft is “20 [miles] south of Albany, heading south at a high rate of speed, 600 knots.” [Griffin, 2007, pp. 43] Flight 11 was over Albany at 8:26 (see (8:26 a.m.-8:29 a.m.) September 11, 2001). [Federal Aviation Administration, 9/17/2001 pdf file] At such a high speed, it would have reached 20 miles south of there around 8:28. However, Scoggins says he is quite certain he only arrives on the floor at Boston Center at around 8:35. He says that although he’d later tried to write up a chronology of events, he “couldn’t get a timeline that made any sense.” Furthermore, Scoggins claims that even before he’d arrived, Joseph Cooper, a Boston Center air traffic management specialist, had already phoned NEADS about the hijacking. [Griffin, 2007, pp. 43 and 335] The 9/11 Commission makes no mention of either call. It says “the first notification received by the military—at any level—that American 11 had been hijacked” is when Boston Center calls NEADS just before 8:38 a.m. (see (8:37 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20] However, a report by ABC News is more consistent with Scoggins’ claims, indicating that Boston Center contacts NEADS about the hijacking earlier, at around 8:31. [ABC News, 9/11/2002] (Boston Center also contacts the FAA’s Cape Cod facility at 8:34 and requests that it notify the military about Flight 11 (see 8:34 a.m. September 11, 2001). Apparently around the same time, it tries contacting a military unit at Atlantic City (see (8:34 a.m.) September 11, 2001).) Scoggins says he makes “about 40 phone calls to NEADS” in total on this day. [Griffin, 2007, pp. 43] NEADS Commander Robert Marr later comments that Scoggins “deserves a lot of credit because he was about the only one that was feeding us information. I don’t know exactly where he got it. But he was feeding us information as much as he could.” [Michael Bronner, 2006]

Entity Tags: Boston Air Route Traffic Control Center, Joseph Cooper, Colin Scoggins, Northeast Air Defense Sector, Robert Marr

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

After being informed of the hijacking of Flight 11, Tim Spence, an operational supervisor at the FAA’s Cape Terminal Radar Approach Control (TRACON), calls the air traffic control tower and then the operations desk at Otis Air National Guard Base, to let them know that they might soon be receiving an order to scramble the base’s fighter jets. [9/11 Commission, 9/30/2003 pdf file; 9/11 Commission, 2004] Daniel Bueno, a supervisor at the FAA’s Boston Center, has just called Spence at the Cape TRACON, which is located on Otis Air Base at Cape Cod, Massachusetts, and said he wanted fighter jets scrambled in response to Flight 11, which is a “possible hijack.” Spence told Bueno he would contact Otis Air Base and see what it could do to help (see 8:34 a.m. September 11, 2001). [Federal Aviation Administration, 4/19/2002; 9/11 Commission, 9/30/2003 pdf file; 9/11 Commission, 8/26/2004, pp. 12]
TRACON Supervisor Calls Otis Tower - Spence will later recall that in the five minutes following the call from Bueno, he makes “as many calls as possible.” He gets on the phone to the air traffic control tower at Otis Air Base, to notify the controllers there of the situation and receive information on who to call next, so as to facilitate Bueno’s request. Spence will recall that the Otis tower controller he speaks to gives him the telephone number for either Otis Air Base’s base operations or the supervisor of flying desk, which is the aviation section of the base operations desk. (He will be unable to recall exactly which number he is given.) Spence will say he “may have been given a second number” by the Otis tower controller, but he “does not recall directly.”
TRACON Supervisor Calls Operations Desk - Spence then calls Otis Air Base’s operations desk. He will later be unable to remember who he speaks with there. But, he will recall, the “general discussion” he has with them is “an introduction of his position, the relay of the information of a hijack from [the FAA’s Boston Center], and a request for information on how to get a fighter scramble.” During the call, Spence acknowledges that he has no authority to authorize a fighter scramble, but he advises those at the base to prepare to receive a scramble order (presumably from NEADS, NORAD’s Northeast Air Defense Sector), since such an order is “probably on its way.” The person at the operations desk gives Spence the phone number for NEADS.
Timing of Calls Unclear - The exact times when Spence calls the control tower and the operations desk at Otis Air Base are unclear. Spence will tell the 9/11 Commission that he makes the call to the control tower immediately after receiving the call from Bueno. [9/11 Commission, 9/30/2003 pdf file] That call ended just before 8:36 a.m. [Federal Aviation Administration, 4/19/2002] However, according to the 9/11 Commission Report, “the first notification received by the military—at any level—that American 11 had been hijacked” is when the FAA’s Boston Center calls NEADS just before 8:38 a.m. (see (8:37 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20] If correct, that would indicate Spence calls the Otis tower at 8:38 a.m. or after. Bueno also called the Otis tower directly, to request military assistance in response to Flight 11 (see (Between 8:30 a.m. and 8:40 a.m.) September 11, 2001), and the tower controller subsequently contacts the base’s operations desk to alert it to the possible hijacking (see (Between 8:31 a.m. and 8:40 a.m.) September 11, 2001). [Filson, 2003, pp. 47; Spencer, 2008, pp. 22, 27-28] It is unclear whether the tower controller calls the operations desk before or after Spence calls it, although Spence will suggest to the 9/11 Commission that Otis Air Base “may have just received a call themselves regarding the situation” when he makes his calls, “but he is not sure.” [9/11 Commission, 9/30/2003 pdf file]

Entity Tags: Tim Spence, Otis Air National Guard Base, Cape Terminal Radar Approach Control

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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] 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

National Guard troops stationed at NORAD’s Northeast Air Defense Sector (NEADS) in Rome, New York.National Guard troops stationed at NORAD’s Northeast Air Defense Sector (NEADS) in Rome, New York. [Source: Rome Sentinel]At NORAD’s Northeast Air Defense Sector (NEADS), a huddle of people is gathered around one of the radar scopes. NEADS Commander Robert Marr initially thinks this hubbub is due to the NORAD training exercise (presumably Vigilant Guardian) that is taking place on this day (see (6:30 a.m.) September 11, 2001). He will later recall: “I’ve seen many exercises… and as I saw that huddle I said, ‘There’s got to be something wrong, something is happening here.’ You usually see that whenever they find a track on the scope that looks unusual; it’s usually an indicator that something is getting ready to kick off.” [Filson, 2003, pp. 55] According to author Lynn Spencer, Marr thinks the day’s exercise “is kicking off with a lively, unexpected twist.… His bet is that his simulations team has started off the exercise by throwing out a ‘heart attack card’ to see how the troops respond to a first-aid call from a fellow soldier, testing their first responder training.” [Spencer, 2008, pp. 26] He sends Lieutenant Colonel Dawne Deskins, the regional mission crew commander for the exercise, to check out what is going on. [Filson, 2003, pp. 55] Deskins speaks briefly over the phone with the FAA’s Boston Center about the Flight 11 hijacking (see (8:37 a.m.) September 11, 2001). [Spencer, 2008, pp. 26] She then runs back to the “battle cab”—the glass-walled room that overlooks the NEADS operations floor—and speaks to Marr with urgency in her voice. [Filson, 2003, pp. 55] She tells him: “It’s a hijacking, and this is real life, not part of the exercise. And it appears that the plane is heading toward New York City.” Although Deskins has specifically stated, “not part of the exercise,” Marr reportedly thinks, “This is an interesting start to the exercise.” According to Spencer, he thinks “This ‘real-world’ mixed in with today’s simex [simulated exercise] will keep [his staff members] on their toes.” Regardless of whether the crisis is real or not, Marr decides to instruct that the two alert F-15s at Otis Air National Guard Base be ordered to battle stations (see (8:40 a.m.) September 11, 2001). [Spencer, 2008, pp. 26-27]

Entity Tags: Robert Marr, Northeast Air Defense Sector, Boston Air Route Traffic Control Center, Dawne Deskins, Vigilant Guardian

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

One of the ID technicians at NORAD’s Northeast Air Defense Sector (NEADS) calls the FAA’s Boston Center, and learns that there have been “threats in the cockpit” of Flight 11. The communications team at NEADS is currently trying to quickly find out all they can about the hijacked plane, such as its flight number, tail number, and where it is. ID tech Shelley Watson calls the management desk at the Boston Center, which had alerted NEADS to the hijacking minutes earlier (see (8:37 a.m.) September 11, 2001), wanting to make sure she has all the information that is available on Flight 11. Her call is answered by Boston Center’s military liaison, Colin Scoggins. Scoggins tells Watson: “He’s being hijacked. The pilot’s having a hard time talking to the… I mean, we don’t know. We don’t know where he’s goin’. He’s heading towards Kennedy [International Airport in New York City]. He’s… 35 miles north of Kennedy now at 367 knots. We have no idea where he’s goin’ or what his intentions are.” Scoggins says, “I guess there’s been some threats in the cockpit,” and adds, “We’ll call you right back as soon as we know more info.” Master Sergeant Maureen Dooley is standing over Watson, relaying any pertinent information she hears to Major Kevin Nasypany. She calls to him, “Okay, he said threat to the cockpit!” [Vanity Fair, 8/1/2006; Spencer, 2008, pp. 34]

Entity Tags: Shelley Watson, Northeast Air Defense Sector, Colin Scoggins, Kevin Nasypany, Boston Air Route Traffic Control Center, Maureen Dooley

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Two F-15 fighter jets are scrambled from Otis Air National Guard Base in Cape Cod, Massachusetts, which is 153 miles from New York City. The fighters are launched in response to the hijacked Flight 11, but this plane is already crashing into the World Trade Center at this time (see 8:46 a.m. September 11, 2001). [Washington Post, 9/15/2001; CNN, 9/17/2001; North American Aerospace Defense Command, 9/18/2001; 9/11 Commission, 6/17/2004]
Delay - The FAA’s Boston Center alerted NORAD’s Northeast Air Defense Sector (NEADS) to the hijacking of Flight 11 and requested that fighter jets be scrambled at just before 8:38 a.m. (see (8:37 a.m.) September 11, 2001), but the mission crew commander at NEADS only instructed the leader of his weapons team to launch the Otis fighters at 8:45 a.m. (see 8:45 a.m. September 11, 2001). [Vanity Fair, 8/1/2006]
Otis Aircraft Head to Runway - As soon as the pilots at Otis Air Base are strapped into their aircraft, the green light directing them to launch goes on. They start their engines and taxi out of the hangar to the nearest runway. One of the pilots, Lt. Col. Timothy Duffy, radios his command post for guidance, asking, “Do you have words?” The response he gets is, “Possible hijack, American Flight 11, 737, flight level 290 [29,000 feet], over JFK [International Airport in New York City].” (This flight information is partly incorrect, since American 11 is a 767, not a 737.) According to the Cape Cod Times, the jets will be up in the air before their radar kicks in. [Cape Cod Times, 8/21/2002; Spencer, 2008, pp. 42] The Otis pilots have already been preparing for the scramble order to come since learning of the hijacking from the FAA’s Cape Cod facility, some time shortly after 8:34 a.m. (see (8:36 a.m.-8:41) September 11, 2001). [BBC, 9/1/2002; Spencer, 2008, pp. 27-30] Their jets are reportedly not airborne until seven minutes after being scrambled, at 8:53 a.m. (see 8:53 a.m. September 11, 2001) and there will be conflicting accounts of what their original destination is (see (8:53 a.m.-9:05 a.m.) September 11, 2001). [9/11 Commission, 6/17/2004]

Entity Tags: Timothy Duffy, Otis Air National Guard Base, Daniel Nash

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

In the National Military Command Center (NMCC) at the Pentagon, personnel apparently become aware of the first attack on the World Trade Center from watching the reports on television. According to Steve Hahn, an operations officer there, “We monitor the television networks in the center, and along with the rest of America we saw the smoke pouring from the tower.” Dan Mangino, who is also an operations officer at the NMCC, says, “At first, we thought it was a terrible accident.” [American Forces Press Service, 9/7/2006] The 9/11 Commission later says, “Most federal agencies learned about the crash in New York from CNN.” [9/11 Commission, 7/24/2004, pp. 35] Whether the NMCC was already aware that a hijacking was underway is unclear. According to military instructions, the NMCC is “the focal point within Department of Defense for providing assistance” in response to hijackings in US airspace, and is supposed to be “notified by the most expeditious means by the FAA.” [US Department of Defense, 6/1/2001 pdf file] Boston Air Traffic Control Center started notifying the chain of command of the suspected hijacking of Flight 11 more than 20 minutes earlier (see 8:25 a.m. September 11, 2001). And at 8:32, the FAA’s Command Center in Herndon informed FAA headquarters of the possible hijacking (see 8:28 a.m. September 11, 2001). Yet, according to the 9/11 Commission, although the “FAA headquarters began to follow the hijack protocol,” it “did not contact the NMCC to request a fighter escort.” Supposedly, the first that the military learned of the hijacking was when Boston Air Traffic Control Center contacted NORAD’s Northeast Air Defense Sector (NEADS) about it, at around 8:37 a.m. (see (8:37 a.m.) September 11, 2001). The earliest time mentioned by the 9/11 Commission that the NMCC learns of the Flight 11 hijacking is 9 a.m. (see 9:00 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 19-20 and 35]

Entity Tags: Steve Hahn, Dan Mangino, National Military Command Center

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The National Military Joint Intelligence Center.The National Military Joint Intelligence Center. [Source: Joseph M. Juarez / Defense Intelligence Agency]Lieutenant Colonel Mark Stuart, an intelligence officer at NORAD’s Northeast Air Defense Sector (NEADS), calls the National Military Joint Intelligence Center (NMJIC) at the Pentagon regarding the hijacking of Flight 11, but the center is unable to provide him with any more information than he already has. [9/11 Commission, 10/30/2003 pdf file] NEADS was alerted to the hijacking of Flight 11 at 8:37 a.m. (see (8:37 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20] Stuart now calls the Air Force desk at the NMJIC about it. [9/11 Commission, 10/30/2003 pdf file] The NMJIC, located in the Joint Staff area of the Pentagon, constantly monitors worldwide developments for any looming crises that might require US involvement. [Washington Times, 9/25/1997; Joint Chiefs of Staff, 2/6/2006] It “forms the heart of timely intelligence support to national-level contingency operations,” according to James Clapper, a former director of the Defense Intelligence Agency. And during a crisis, it “serves as a clearinghouse for all requests for national-level intelligence information.” [Joint Forces Quarterly, 3/1994 pdf file] However, Stuart will later recall that the NMJIC can provide him with “no additional relevant information” on the hijacking. Stuart then calls Robert Del Toro, an intelligence officer with the 1st Air Force at Tyndall Air Force Base, Florida. But, Stuart will say, the 1st Air Force also has “no further information” about the hijacking. [9/11 Commission, 10/30/2003 pdf file]

Entity Tags: US Department of the Air Force, National Military Joint Intelligence Center, James R. Clapper Jr., 1st Air Force, Robert Del Toro, Mark E. Stuart

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

An intelligence officer at NORAD’s Northeast Air Defense Sector (NEADS) checks the SIPRNET—the Department of Defense’s classified version of the Internet—for information relating to the hijacking of Flight 11, but finds none. [Northeast Air Defense Sector, 9/11/2001; 9/11 Commission, 10/30/2003 pdf file] NEADS was alerted to the hijacking of Flight 11 at 8:37 a.m. (see (8:37 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20] Since then, Lieutenant Colonel Mark Stuart, an intelligence officer at NEADS, has contacted various facilities, in search of further information about it. He called the FBI’s Strategic Information and Operations Center (see (8:48 a.m.) September 11, 2001), the National Military Joint Intelligence Center at the Pentagon, and 1st Air Force headquarters in Florida (see (Shortly After 8:48 a.m.) September 11, 2001), but none of them had any additional information on the crisis. Stuart now informs Colonel Robert Marr, the battle commander at NEADS, of his efforts. He also directs a “Major Edick”—another intelligence officer at NEADS—to search the SIPRNET for information on the hijacking. However, Stuart will later say, Edick is unable to find any such information on the SIPRNET “that morning or afternoon.” [Northeast Air Defense Sector, 9/11/2001; 9/11 Commission, 10/30/2003 pdf file]

Entity Tags: Mark E. Stuart, Robert Marr, SIPRNET

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

A NORAD training exercise that is taking place this morning, presumably Vigilant Guardian (see (6:30 a.m.) September 11, 2001), is reportedly canceled shortly after 9:03, when the second World Trade Center tower is hit. [Airman, 3/2002] NORAD Commander Larry Arnold later says that after Flight 175 hits the South Tower, “I thought it might be prudent to pull out of the exercise, which we did.” [Filson, 2003, pp. 59] According to author Lynn Spencer: “The phone calls start flying between the various NORAD command centers. General Arnold calls Maj. Gen. Rick Findley” at NORAD’s operations center in Cheyenne Mountain, Colorado, “to give him the latest information and have him withdraw all forces from the simulated exercise.” [Spencer, 2008, pp. 86] Arnold will recall, “As we pulled out of the exercise we were getting calls about United Flight 93 and we were worried about that.” [Filson, 2003, pp. 59] Some early accounts say the military receives notification of the possible hijacking of Flight 93 at around 9:16 a.m. (see 9:16 a.m. September 11, 2001). [CNN, 9/17/2001; 9/11 Commission, 5/23/2003] However, the 9/11 Commission will later claim that NORAD’s Northeast Air Defense Sector (NEADS) first receives a call about Flight 93 at 10:07 a.m. (see 10:05 a.m.-10:08 a.m. September 11, 2001). [9/11 Commission, 6/17/2004] Arnold will add, “Then we had another call from Boston Center about a possible hijacking, but that turned out to be the airplane that had already hit the South Tower but we didn’t know that at the time.” [Filson, 2003, pp. 59]

Entity Tags: Larry Arnold, North American Aerospace Defense Command, Vigilant Guardian, Eric A. “Rick” Findley

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to an early timeline laid out to CNN by unnamed but “informed defense officials,” the FAA informs NORAD at this time that Flight 93 may have been hijacked. [CNN, 9/17/2001] In public testimony before the 9/11 Commission in 2003, NORAD officials will similarly claim that the FAA first reports the possible hijacking of Flight 93 at this time. [9/11 Commission, 5/23/2003] Yet this is 12 minutes before the hijacking is meant to have occurred (see (9:28 a.m.) September 11, 2001). [9/11 Commission, 8/26/2004, pp. 38] One explanation is put forward that could possibly help explain the discrepancy: There are media reports that “investigators had determined from the cockpit voice recorder from United Airlines Flight 93… that one of the four hijackers had been invited into the cockpit area before the flight took off from Newark, New Jersey.” Cockpit voice recordings indicate that the pilots believed their guest was a colleague “and was thereby extended the typical airline courtesy of allowing any pilot from any airline to join a flight by sitting in the jumpseat, the folded over extra seat located inside the cockpit.” [Fox News, 9/24/2001; Herald Sun (Melbourne), 9/25/2001] This would be consistent with passenger phone calls from the plane, describing only three hijackers on Flight 93 (see (9:27 a.m.-10:03 a.m.) September 11, 2001). [Longman, 2002, pp. 120] However, the reports will not be confirmed. The 9/11 Commission Report will dismiss the claim that NORAD was alerted at 9:16, stating, “In public testimony before this Commission in May 2003, NORAD officials stated that at 9:16, NEADS received hijack notification of United 93 from the FAA. This statement was incorrect. There was no hijack to report at 9:16. United 93 was proceeding normally at that time.” [9/11 Commission, 7/24/2004, pp. 34] No further explanations will be offered for the incorrect timelines. NORAD’s own initial timeline, released on September 18, 2001, will not give a time for when the FAA alerted it to Flight 93. It will only say that the FAA and its Northeast Air Defense Sector (NEADS) “established a line of open communication discussing AA Flt 77 and UA Flt 93.” [North American Aerospace Defense Command, 9/18/2001]

Entity Tags: Northeast Air Defense Sector, North American Aerospace Defense Command, Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Ed Ballinger, the United Airlines flight dispatcher monitoring Flight 93, sends a warning message to this flight, telling the pilots to beware of any cockpit intrusion. [9/11 Commission, 7/24/2004, pp. 11] At 9:21, United Airlines instructed its dispatchers to warn their flights to secure their cockpit doors (see 9:21 a.m. September 11, 2001), but Ballinger had already taken the initiative two minutes earlier to begin warning the 16 flights he is monitoring (see 9:19 a.m. September 11, 2001). His text message reads: “Beware any cockpit intrusion… Two aircraft in NY hit [World] Trade Center builds.” Because this message is sent out to Ballinger’s 16 aircraft in groups, it is not until 9:23 a.m. that it is transmitted to Flight 93. [9/11 Commission, 1/27/2004; 9/11 Commission, 8/26/2004, pp. 26 and 37] The warning is received in the plane’s cockpit one minute later. [9/11 Commission, 7/24/2004, pp. 11] Then, at 9:26, Flight 93 pilot Jason Dahl responds with the text message, “Ed confirm latest mssg plz [message please]—Jason.” Apart from a routine radio contact with the FAA’s Cleveland Center a minute later (see 9:27 a.m. September 11, 2001), this is the last normal communication made from Flight 93’s cockpit before the hijacking occurs. [9/11 Commission, 8/26/2004, pp. 38] Ballinger will later complain: “One of the things that upset me was that they knew 45 minutes before that American Airlines [Flight 11] had a problem. I put the story together myself [from news accounts]. Perhaps if I had the information sooner, I might have gotten the message to [Flight] 93 to bar the door.” [Chicago Daily Herald, 4/14/2004]

Entity Tags: Jason Dahl, Ed Ballinger

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The FAA’s Cleveland Center.The FAA’s Cleveland Center. [Source: FAA]Having entered the center’s airspace, Flight 93 establishes radio contact with the FAA’s Cleveland Center, a regional air traffic control center that guides long-range, high altitude flights. The pilot reports simply that his flight is experiencing intermittent light choppy air, and does not indicate there being any problems on board, saying, “Good morning Cleveland, United 93 with you at three-five-oh [35,000 feet], intermittent light chop.” The controller, John Werth, is busy with other flights, so does not initially respond. A minute later, Flight 93 radios again, “United 93 checking in three-five-oh.” Werth replies, “United 93, three-five-zero, roger.” [Gregor, 12/21/2001 pdf file; Longman, 2002, pp. 69; 9/11 Commission, 8/26/2004, pp. 37; CBS News, 9/10/2006] Two minutes later, Flight 93 will make its final radio communication before the hijacker takeover occurs (see 9:27 a.m. September 11, 2001).

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Flight 93 makes its last normal communication with air traffic control before being hijacked, acknowledging a routine radio transmission from the FAA’s Cleveland Center. [9/11 Commission, 7/24/2004, pp. 28] Flight 93 checked in with the Cleveland Center a couple of minutes earlier (see 9:24 a.m.-9:25 a.m. September 11, 2001). At 9:27, the Cleveland controller, John Werth, alerts it to another aircraft 12 miles away and to its right, at 37,000 feet: “United 93, that traffic for you is one o’clock, 12 miles east, bound three-seven-zero.” Seconds later, Flight 93 responds, “Negative contact, we’re looking, United 93.” Less than a minute after this, the hijackers appear to enter Flight 93’s cockpit (see (9:28 a.m.) September 11, 2001). [Gregor, 12/21/2001 pdf file; Longman, 2002, pp. 69; CBS News, 9/10/2006]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Jason Dahl.Jason Dahl. [Source: Publicity photo]According to the 9/11 Commission, less than a minute after Flight 93 acknowledged a routine radio transmission from the FAA’s Cleveland Center (see 9:27 a.m. September 11, 2001), John Werth—the controller handling the flight—and pilots of other aircraft in the vicinity of Flight 93 hear “a radio transmission of unintelligible sounds of possible screaming or a struggle from an unknown origin.” [Federal Aviation Administration, 9/11/2001; 9/11 Commission, 6/17/2004; CBS News, 9/10/2006] Someone, presumably Flight 93’s pilot Jason Dahl, is overheard by controllers as he shouts, “Mayday!” [New York Times, 7/22/2004] Seconds later, the controller responds, “Somebody call Cleveland?” Then there are more sounds of screaming and someone yelling, “Get out of here, get out of here.” [Toronto Sun, 9/16/2001; Newsweek, 9/22/2001; Observer, 12/2/2001; MSNBC, 7/30/2002; 9/11 Commission, 6/17/2004] Then the voices of the hijackers can be heard talking in Arabic. The words are later translated to show they are talking to each other, saying, “Everything is fine.” [Newsweek, 12/3/2001] Later, passenger phone calls will describe two dead or injured bodies just outside the cockpit; presumably these are the two pilots. [New York Times, 7/22/2004]

Entity Tags: Cleveland Air Route Traffic Control Center, John Werth, 9/11 Commission, Jason Dahl

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

John Werth.John Werth. [Source: CBS]Shortly after hearing strange noises from the cockpit of Flight 93, Cleveland air traffic controllers notice the plane has descended about 700 feet. John Werth, the controller who is handling the plane, tells the supervisor nearest to him, “I think we have another one [i.e., another hijacking].” He will repeatedly radio the cockpit over the next four minutes, asking the pilot to confirm the hijacking, but receive no response. At 9:30 a.m., Werth begins asking other nearby flights on his frequency if they’ve heard screaming; several say that they have. [Gregor, 12/21/2001 pdf file; 9/11 Commission, 7/24/2004, pp. 28; CBS News, 9/10/2006] The Cleveland Center immediately notifies United Airlines’ headquarters of the loss of communication with Flight 93 (see (9:30 a.m.) September 11, 2001). However, the FAA chain of command is apparently not also immediately informed. And the Cleveland Center will not contact NORAD’s Northeast Air Defense Sector (NEADS) about Flight 93 until 10:07 a.m. (see 10:05 a.m.-10:08 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 28 and 30]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Shortly before Flight 93 reverses direction and heads east, someone in its cockpit radios in and asks the FAA for a new flight plan, with a final destination of Washington, DC. [ABC News, 9/11/2001; ABC News, 9/14/2001] Jeff Krawczyk, the chief operating officer of a company that tracks aircraft movements, later comments, “We hardly ever get a flight plan change. Very unusual.” [Washington Business Journal, 9/11/2001] Who it is that makes this request is unclear. The hijacker takeover of Flight 93 occurred around 9:28 a.m. (see (9:28 a.m.) September 11, 2001) [9/11 Commission, 7/24/2004, pp. 11] , so it is presumably made by one of the hijackers. Twenty-five minutes later the pilot hijacker will also program a new destination into the plane’s navigational system (see 9:55 a.m. September 11, 2001).

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] 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] 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] 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

FAA Administrator Jane Garvey notifies the video conference chaired by counterterrorism “tsar” Richard Clarke that all aircraft have been ordered to land at the nearest field and reads a list of potential hijacks including Delta 1989 and United 93. [Clarke, 2004, pp. 5] Although, according to Clarke’s account, both General Richard Myers and Secretary of Defense Donald Rumsfeld are present at the conference at this point, the 9/11 Commission will later claim that the military was not notified about the hijacking of United 93 until over half an hour later (see 10:03 a.m. September 11, 2001).

Entity Tags: Richard B. Myers, Jane Garvey, Donald Rumsfeld, Richard A. Clarke

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to the 9/11 Commission, word of Flight 93’s hijacking reaches FAA headquarters. By this time, headquarters has established an open line of communication with the FAA Command Center at Herndon, Virginia. It had instructed the center to poll all flight control centers about suspect aircraft. So, at this time, the Command Center passes on Cleveland’s message: “United 93 may have a bomb on board.” The FAA headquarters apparently does not forward this information to the military, despite having the responsibility for doing so. Ben Sliney, the FAA’s national operations manager at its Herndon Command Center, will later recount, “I do know that all the information was being relayed to headquarters and, at least as far as we were concerned, it should have been. We thought it had been given to the military at each juncture.” The Command Center continually updates FAA headquarters on Flight 93 until it crashes. [9/11 Commission, 6/17/2004; CBC, 9/12/2006]

Entity Tags: Federal Aviation Administration, Ben Sliney

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Military officers at the FAA’s Command Center are informed of the hijacking of Flight 93, according to the FAA’s National Operations Manager Ben Sliney. If such notification is given, it is presumably shortly after the Command Center learns of the hijacking (see 9:34 a.m. September 11, 2001). Sliney will later tell the 9/11 Commission: “Available to us at the Command Center of course is the military cell, which was our liaison with the military services. They were present at all of the events that occurred on 9/11.” He will add, “The normal protocols for the events that were transpiring then—that is to say hijacked aircraft, which requires a notification to NORAD—those, at least I was given to understand, were made promptly—the notifications on each hijack.” The FAA’s acting Deputy Administrator Monte Belger will add: “[T]here were military people on duty at the FAA Command Center, as Mr. Sliney said. They were participating in what was going on. There were military people in the FAA’s Air Traffic Organization in a situation room. They were participating in what was going on.” [9/11 Commission, 6/17/2004] If the cell is notified, it is unclear what, if anything, the military liaison officers—Colonel John Czabaranek, Lieutenant Colonel Michael-Anne Cherry, and Major Kevin Bridges (see (Between 9:04 a.m. and 9:25 a.m.) September 11, 2001)—at the Command Center do with the information about Flight 93’s hijacking. The 9/11 Commission will say that the first notification to the military about Flight 93 comes at 10:07 a.m. (see 10:05 a.m.-10:08 a.m. September 11, 2001).

Entity Tags: Monte Belger, Kevin Bridges, John Czabaranek, Ben Sliney, Michael-Anne Cherry

Timeline Tags: Complete 911 Timeline

FAA’€™s Cleveland Center.FAA’€™s Cleveland Center. [Source: ABC News]According to the 9/11 Commission, at about this time Cleveland flight control specifically asks the FAA Command Center whether someone has requested the military to launch fighters toward Flight 93. Cleveland offers to contact a nearby military base. The Command Center replies that FAA personnel well above them in the chain of command have to make that decision and are working on the issue. [9/11 Commission, 6/17/2004] Cleveland overheard a hijacker say there was a “bomb on board” at 9:32 a.m. and passed the message to FAA higher ups (see (9:32 a.m.) September 11, 2001). According to John Werth, the Cleveland controller handling Flight 93, “Within three or four minutes, probably, of when [the hijacking] happened, I asked if the military was advised yet. Had anybody called the military? They said, ‘don’t worry. That’s been taken care of,’ which I think to them, meant they had called the command center in Washington.” [CBS News, 9/10/2006]

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

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]

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

Doug Davis.Doug Davis. [Source: Federal Aviation Administration]John White, a manager at the FAA’s Command Center, suggests to Doug Davis, the special assistant for technical operations in air traffic services at FAA headquarters, that fighter jets should be launched in response to Flight 93. However, FAA headquarters is apparently unable to act on this suggestion. [Federal Aviation Administration, 10/21/2002; 9/11 Commission, 7/24/2004, pp. 29; Canadian Broadcasting Corporation, 9/10/2006] In the last few minutes, the Command Center has warned headquarters that Flight 93 is “29 minutes out of Washington” and approaching the city (see 9:41 a.m.-9:48 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 44]
Command Center Asks about Launching Fighters - Davis now tells White, “They’re pulling Jeff [Griffith, the FAA’s deputy director of air traffic] away to go talk about United 93.” White asks, “Uh, do we want to think, uh, about scrambling aircraft?” Davis replies, “Oh, God, I don’t know.” White says, “Uh, that’s a decision somebody’s gonna have to make probably in the next 10 minutes.” However, Davis only responds, “Uh, ya know everybody just left the room.” [Federal Aviation Administration, 10/21/2002; 9/11 Commission, 7/24/2004, pp. 29] This conversation takes place 13 minutes after the FAA’s Cleveland Center asked the Command Center whether anyone had asked the military to launch fighter jets to intercept Flight 93 (see (9:36 a.m.) September 11, 2001). [9/11 Commission, 8/26/2004, pp. 40]
Person Who Could Request Fighters Is Unavailable - Apparently there is only one person at FAA headquarters who is authorized to request military assistance, and Ben Sliney, the Command Center’s national operations manager, is told that no one can find him. Sliney will later recount: “I said something like, ‘That’s incredible. There’s only one person. There must be someone designated or someone who will assume the responsibility of issuing an order, you know.’ We were becoming frustrated in our attempts to get some information. What was the military response?” [Canadian Broadcasting Corporation, 9/10/2006] This lack of response to Flight 93 contrasts with the FAA’s earlier reaction to Flight 11, when Boston Center air traffic controllers contacted NORAD’s Northeast Air Defense Sector (NEADS) themselves (see (8:37 a.m.) September 11, 2001), and even called military bases directly (see 8:34 a.m. September 11, 2001 and (8:34 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20]

Entity Tags: Ben Sliney, John White, Doug Davis, Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The hijacker pilot of Flight 93 (presumably Ziad Jarrah) reprograms the plane’s navigational system for a new destination. He dials in the navigational code for Washington’s Reagan National Airport, which is just four miles from the White House, and an arrival time of 10:28 a.m. The 9/11 Commission will say this further indicates that the plane’s intended target is the nation’s capital. [Longman, 2002, pp. 78, 182; 9/11 Commission, 7/24/2004, pp. 457; 9/11 Commission, 8/26/2004, pp. 45] A minute later, an air traffic controller at the FAA’s Cleveland Center will enter a revised flight plan for Flight 93 into the FAA computer system, giving a new destination of Reagan Airport, although the reason she does this is unclear (see 9:56 a.m. September 11, 2001). [Federal Aviation Administration, 9/11/2001; St. Petersburg Times, 9/12/2001; 9/11 Commission, 10/2/2003 pdf file] Twenty-five minutes earlier, at 9:30 a.m., someone in Flight 93’s cockpit had radioed in and requested a new flight plan from the FAA, with a final destination of Washington (see 9:30 a.m. September 11, 2001). [ABC News, 9/14/2001]

Entity Tags: Ziad Jarrah

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

United Airlines official Sandy Rogers calls Ellen King at the FAA’s Command Center to discuss Flight 93. The timing of the call is not known specifically, although it appears to be after the Pentagon was hit and could not be long after Flight 93 is thought to have crashed, which is shortly after 10:00 a.m. (see (10:03 a.m.-10:10 a.m.) September 11, 2001 and (10:06 a.m.) September 11, 2001). Rogers tells King that Flight 93 has been hijacked, and King responds, “Oh God… thank you,” indicating she was previously unaware of the hijacking. However, the FAA had been aware of the situation since a few minutes after the hijacking took place (see (9:33 a.m.) September 11, 2001 and 9:34 a.m. September 11, 2001). Rogers also says: “It’s over Hagerstown now and you’re not aware of it. It’s heading toward Washington, DC, and we are under a threat of a hijacking on board and this flight is out of our control now heading toward Washington, DC.” Rogers states that United Airlines is “advising the military” about the plane and King also says that the FAA will do the same. [Federal Aviation Administration, 10/14/2003, pp. 37-39 pdf file] However, there are no other reports of Flight 93 ever being over Hagerstown, which is in Maryland. Flight 93 is said to crash in Shanksville, Pennsylvania, and is thought never to reach Maryland. There will be some—apparently mistaken—reports that the plane is still airborne after it is thought to have crashed (see (Between 10:10 a.m. and 10:18 a.m.) September 11, 2001 and 10:10 a.m.-10:11 a.m. September 11, 2001), and this may be another such report.

Entity Tags: Federal Aviation Administration, Ellen King, United Airlines, Sandy Rogers

Timeline Tags: Complete 911 Timeline

Smoke rising, minutes after Flight 93 crashes in Pennsylvania.Smoke rising, minutes after Flight 93 crashes in Pennsylvania. [Source: CNN]Exactly when Flight 93 crashes is unclear. According to NORAD, Flight 93 crashes at 10:03 a.m. [North American Aerospace Defense Command, 9/18/2001] The 9/11 Commission gives an exact time of 11 seconds after 10:03 a.m. It will claim this “time is supported by evidence from the staff’s radar analysis, the flight data recorder, NTSB [National Transportation Safety Board] analysis, and infrared satellite data.” It does note that “[t]he precise crash time has been the subject of some dispute.” [9/11 Commission, 6/17/2004] However, a seismic study authorized by the US Army and drafted by scientists Won-Young Kim and Gerald Baum to determine when the plane crashed will conclude that the crash happened at 10:06:05 a.m. [Kim and Baum, 2002 pdf file; San Francisco Chronicle, 12/9/2002] The discrepancy is so puzzling that the Philadelphia Daily News will publish an article on the issue, titled “Three-Minute Discrepancy in Tape.” This notes that leading seismologists agree on the 10:06 a.m. time, give or take a couple of seconds. [Philadelphia Daily News, 9/16/2002] The New York Observer will note that, in addition to the seismology study, “The FAA gives a crash time of 10:07 a.m. In addition, the New York Times, drawing on flight controllers in more than one FAA facility, put the time at 10:10 a.m. Up to a seven-minute discrepancy? In terms of an air disaster, seven minutes is close to an eternity. The way our nation has historically treated any airline tragedy is to pair up recordings from the cockpit and air traffic control and parse the timeline down to the hundredths of a second. However, as [former Inspector General of the Transportation Department] Mary Schiavo points out, ‘We don’t have an NTSB (National Transportation Safety Board) investigation here, and they ordinarily dissect the timeline to the thousandth of a second.’” [New York Observer, 2/15/2004]

Entity Tags: 9/11 Commission, North American Aerospace Defense Command, Federal Aviation Administration, Won-Young Kim, Mary Schiavo, Gerald R. Baum

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The military liaison at the FAA’s Cleveland Center calls NORAD’s Northeast Air Defense Sector (NEADS) and alerts it to the hijacked Flight 93. According to the 9/11 Commission, this is the first notification NEADS receives about Flight 93, but it comes too late, since the plane has already crashed (see (10:06 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 30; 9/11 Commission, 8/26/2004, pp. 46]
'Bomb on Board' Flight 93 - At 10:05 a.m., the military liaison at the Cleveland Center, who is unaware that Flight 93 has just crashed, calls NEADS to inform it that Flight 93 is heading toward Washington, DC. Even though communicating with NEADS is not one of his responsibilities, he wants to make sure it is in the loop. [Spencer, 2008, pp. 224] At NEADS, the call is answered by Tech Sergeant Shelley Watson. Shortly into the call, at 10:07, the military liaison tells her: “We got a United 93 out here. Are you aware of that?” He continues, “That has a bomb on board.” Watson asks: “A bomb on board? And this is confirmed? You have a mode three [beacon code], sir?” The military liaison replies, “No, we lost his transponder” (see (9:40 a.m.) September 11, 2001). The news about Flight 93 is shouted out to Major Kevin Nasypany, the NEADS mission crew commander. Nasypany responds: “Gimme the call sign. Gimme the whole nine yards.… Let’s get some info, real quick. They got a bomb?”
Liaison Wants Fighters Sent toward Flight 93 - The military liaison continues, asking Watson if NEADS scrambled fighter jets in response to Delta 1989, an aircraft that was mistakenly reported as having been hijacked (see (9:28 a.m.-9:33 a.m.) September 11, 2001 and 9:39 a.m. September 11, 2001). Watson replies: “We did. Out of Selfridge and Toledo” (see (9:55 a.m.) September 11, 2001 and 10:01 a.m. September 11, 2001), and says these jets are airborne. When the military liaison asks if the fighters can be directed to where Flight 93 is, Watson asks him if the Cleveland Center has latitude and longitude coordinates for this aircraft. The military liaison replies that he has not got this information available right now. All he knows is that Flight 93 has “got a confirmed bomb on board… and right now, his last known position was in the Westmoreland area.… Which is… in the Pittsburgh, Pennsylvania, area.” [North American Aerospace Defense Command, 9/11/2001; Vanity Fair, 8/1/2006]
NEADS Searches on Radar - The news of a bomb on board Flight 93 spreads quickly at NEADS, and personnel there search for the aircraft’s primary return on their radar screens. But because the plane has already crashed, they will be unable to locate it. NEADS will only learn that Flight 93 has crashed at 10:15 a.m., during a call with the FAA’s Washington Center (see 10:15 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 30-31]
FAA Failed to Notify Military Earlier - The Cleveland Center’s notification to NEADS about Flight 93 comes 39 minutes after the plane was hijacked (see (9:28 a.m.) September 11, 2001) and 33 minutes after FAA headquarters was alerted to the hijacking (see 9:34 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 11, 28] At the time NEADS is alerted to Flight 93, NORAD is similarly uninformed about this aircraft, according to the 9/11 Commission. The Commission will state, “At 10:07, its representative on the air threat conference call stated that NORAD had ‘no indication of a hijack heading to DC at this time.’” According to the Commission, the National Military Command Center (NMCC) at the Pentagon learned about the Flight 93 hijacking slightly earlier on, at 10:03 a.m. (see 10:03 a.m. September 11, 2001). However, the NMCC was notified by the White House, not the FAA. [9/11 Commission, 7/24/2004, pp. 42] A former senior FAA executive, speaking on condition of anonymity, will later try to explain why it takes the FAA so long to alert NEADS to Flight 93. He will say, “Our whole procedures prior to 9/11 were that you turned everything [regarding a hijacking] over to the FBI.” [Vanity Fair, 8/1/2006] Yet military instructions contradict this, stating, “In the event of a hijacking, the NMCC will be notified by the most expeditious means by the FAA.” [US Department of Defense, 7/31/1997 pdf file; US Department of Defense, 6/1/2001 pdf file]
NORAD Commanders Claim Earlier Awareness of Flight 93 - Two senior NORAD officials will contradict the 9/11 Commission’s conclusion, and claim they were aware of Flight 93 well before it crashed (see Shortly Before 9:36 a.m. September 11, 2001 and (9:36 a.m.-10:06 a.m.) September 11, 2001). [Filson, 2003, pp. 68, 71-73] Colonel Robert Marr, the NEADS battle commander, will tell the Commission that, while the flight was still airborne, “his focus was on UAL 93, which was circling over Chicago,” and he “distinctly remembers watching the flight UAL 93 come west, and turn over Cleveland.” [9/11 Commission, 10/27/2003 pdf file; 9/11 Commission, 1/23/2004 pdf file] Major General Larry Arnold, the commander of the Continental US NORAD Region, will recall, “[W]e watched the [Flight] 93 track as it meandered around the Ohio-Pennsylvania area and started to turn south toward DC.” [Filson, 2003, pp. 71]

Entity Tags: Cleveland Air Route Traffic Control Center, Kevin Nasypany, North American Aerospace Defense Command, Northeast Air Defense Sector, Shelley Watson

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The military liaison at the FAA’s Cleveland Center is informed that Flight 93 has been hijacked and is given information about its location. It is unclear when the liaison first receives this information, but it must happen before 10:07, as he telephones NORAD’s Northeast Air Defense Sector (NEADS) at this time to pass on the information (see 10:05 a.m.-10:08 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 30] Military liaison officers at the FAA’s Command Center are also said to be informed of the hijacking of Flight 93 (see After 9:34 a.m. September 11, 2001).

Entity Tags: Cleveland Air Route Traffic Control Center

Timeline Tags: Complete 911 Timeline

Unaware the aircraft has crashed, United Airlines flight dispatcher Ed Ballinger instructs Flight 93 not to divert to Washington. At 10:10, he sends a text message to Flight 93, stating: “Don’t divert to DC. Not an option.” A minute later, he resends this same message to it. [9/11 Commission, 1/27/2004; 9/11 Commission, 8/26/2004, pp. 46] Someone on Flight 93 had contacted the FAA at 9:30, requesting a new flight plan with the destination of Washington (see 9:30 a.m. September 11, 2001), and at 9:55 the pilot hijacker reprogrammed the plane’s navigational system for the new destination of Washington’s Reagan National Airport (see 9:55 a.m. September 11, 2001). United Airlines will not confirm that Flight 93 has crashed until around 10:15 (see (10:07 a.m.-10:15 a.m.) September 11, 2001), and will notify its employees of this at 10:17 (see 10:17 a.m. September 11, 2001).

Entity Tags: Ed Ballinger

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to the 9/11 Commission, NEADS calls Washington flight control at this time. Asked about Flight 93, flight control responds, “He’s down.” It is clarified that the plane crashed “somewhere up northeast of Camp David.… That’s the last report. They don’t know exactly where.” [9/11 Commission, 6/17/2004] The crash site is in fact about 85 miles northwest of Camp David. [Associated Press, 9/11/2001]

Entity Tags: Northeast Air Defense Sector

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The Federal Aviation Administration (FAA) produces a chronology of the events of September 11, which it uses when it briefs the White House today, but the document fails to mention when NORAD’s Northeast Air Defense Sector (NEADS) was alerted to two of the hijacked planes. The FAA’s chronology, titled “Summary of Air Traffic Hijack Events,” incorporates “information contained in the NEADS logs, which had been forwarded, and on transcripts obtained from the FAA’s Cleveland Center, among others,” according to John Farmer, the senior counsel to the 9/11 Commission.
Document Includes Notification Times for First Two Hijacked Flights - The chronology refers “accurately to the times shown in NEADS logs for the initial notifications from FAA about the hijacking of American 11 and the possible hijacking of United 175,” according to the 9/11 Commission. It gives 8:40 a.m. as the time at which the FAA alerted NEADS to Flight 11, the first plane to be hijacked (see (8:37 a.m.) September 11, 2001), and 9:05 a.m. as the time when the FAA alerted NEADS to Flight 175, the second plane to be hijacked (see (9:03 a.m.) September 11, 2001). However, it makes no mention of when the FAA alerted NEADS to Flight 77 and Flight 93, the third and fourth planes to be hijacked. The FAA’s omission of these two notification times is “suspicious,” according to the 9/11 Commission, “because these are the two flights where FAA’s notification to NEADS was significantly delayed.”
Document Omits Notification Times for Flights 77 and 93 - The chronology, as Farmer will later point out, “makes no mention… of the notification to NEADS at 9:33 that American 77 was ‘lost’ (see 9:34 a.m. September 11, 2001) or of the notification to NEADS at 9:34 of an unidentified large plane six miles southwest of the White House (see 9:36 a.m. September 11, 2001), both of which are in the NEADS logs that the FAA reviewed” when it was putting together the timeline. It also fails to mention the call made by the FAA’s Cleveland Center to NEADS in which, at 10:07 a.m., the caller alerted NEADS to Flight 93 and said there was a “bomb on board” the plane (see 10:05 a.m.-10:08 a.m. September 11, 2001), even though this information was also “duly noted in the NEADS logs” that the FAA has reviewed.
Chronology Omits Other Key Information - The chronology, Farmer will write, reflects “a time at which the FAA was notified that the Otis [Air National Guard Base] fighters were scrambled” in response to the hijacking of Flight 11 (see 8:46 a.m. September 11, 2001), but it gives “no account of the scramble of the fighters from Langley Air Force Base” (see 9:24 a.m. September 11, 2001). It also fails to mention the report that NEADS received after Flight 11 crashed, in which it was incorrectly told the plane was still airborne and heading toward Washington, DC (see 9:21 a.m. September 11, 2001). Despite lacking information about the times when the FAA alerted NEADS to Flights 77 and 93, the FAA’s chronology is one of the documents used to brief the White House about the 9/11 attacks today (see September 17, 2001).
Investigators Were Told to Determine Exact Notification Times - The chronology is the product of investigations that began promptly in response to the 9/11 attacks. According to senior FAA officials, FAA Administrator Jane Garvey and Deputy Administrator Monte Belger “instructed a group of FAA employees (an ‘after-action group’) to reconstruct the events of 9/11.” This group, according to the 9/11 Commission, “began its work immediately after 9/11 and reviewed tape recordings, transcripts, handwritten notes, logs, and other documents in an effort to create an FAA chronology of events.” The group, according to one witness, “was specifically asked to determine exactly when the FAA notified the military that each of the four planes had been hijacked,” and “[s]everal people worked on determining correct times for FAA notifications to the military.” [Federal Aviation Administration, 9/17/2001 pdf file; 9/11 Commission, 7/29/2004; Farmer, 2009, pp. 245-247] NORAD will release a timeline of the events of September 11 and its response to the attacks a day after the FAA chronology is published (see September 18, 2001). [North American Aerospace Defense Command, 9/18/2001; 9/11 Commission, 7/29/2004]

Entity Tags: Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The North American Aerospace Defense Command (NORAD) releases a chronology of the events of September 11 and its response to the terrorist attacks that day, but the accuracy of this account will later be challenged by the 9/11 Commission. [North American Aerospace Defense Command, 9/18/2001; 9/11 Commission, 7/24/2004, pp. 34; 9/11 Commission, 7/29/2004]
NORAD Learned of First Hijackings Too Late to Defend the WTC - The chronology provides the times at which NORAD’s Northeast Air Defense Sector (NEADS) was alerted to the hijackings and when fighter jets were scrambled in response to the hijackings. It states that the Federal Aviation Administration (FAA) notified NEADS about Flight 11, the first hijacked aircraft, at 8:40 a.m. In response, the order was given to scramble two F-15 fighters from Otis Air National Guard Base in Cape Cod, Massachusetts, at 8:46 a.m. (see 8:46 a.m. September 11, 2001), the same time that Flight 11 crashed into the World Trade Center (see 8:46 a.m. September 11, 2001), and the fighters were airborne at 8:52 a.m. (see 8:53 a.m. September 11, 2001). The FAA notified NEADS about Flight 175, the second hijacked aircraft, at 8:43 a.m., according to the chronology. When Flight 175 crashed into the WTC at 9:03 a.m. (see 9:03 a.m. September 11, 2001), the chronology states, the Otis fighters were 71 miles away from New York.
Fighters Were Scrambled in Response to Flight 77 Hijacking - NEADS was alerted to Flight 77, the third hijacked aircraft, at 9:24 a.m., according to the chronology. In response, the order was given to scramble two F-16 fighters from Langley Air Force Base in Virginia (see 9:24 a.m. September 11, 2001) and these were airborne at 9:30 a.m. (see (9:25 a.m.-9:30 a.m.) September 11, 2001). But the F-16s were 105 miles from the Pentagon when it was hit at 9:37 a.m. (see 9:37 a.m. September 11, 2001). Regarding the fourth hijacked aircraft, Flight 93, the chronology gives “N/A” as the time the FAA alerted NEADS, but it also states that the FAA and NEADS discussed the flight on “a line of open communication.” At 10:03 a.m., when Flight 93 crashed in Pennsylvania (see (10:03 a.m.-10:10 a.m.) September 11, 2001 and (10:06 a.m.) September 11, 2001), the chronology states, the F-16s launched from Langley Air Force Base in response to the hijacking of Flight 77 were “in place to protect DC.” [North American Aerospace Defense Command, 9/18/2001]
9/11 Commission Disputes NORAD's Account - The 9/11 Commission Report, released in 2004, will highlight what it says are inaccuracies in NORAD’s timeline of the events of September 11. It will state that NORAD’s claim that NEADS was alerted to Flight 77 at 9:24 a.m. was incorrect. The notice NEADS received at that time, according to the report, was the incorrect claim that Flight 11 “had not hit the World Trade Center and was heading for Washington, DC” (see 9:21 a.m. September 11, 2001). “NEADS never received notice that American 77 was hijacked,” the report will state. “It was notified at 9:34 that American 77 was lost (see 9:34 a.m. September 11, 2001). Then, minutes later, NEADS was told that an unknown plane was six miles southwest of the White House” (see 9:36 a.m. September 11, 2001). The report will state that NORAD’s claim that the Langley fighters were scrambled in response to the notification about Flight 77 is also incorrect. Instead, it will state, the fighters were scrambled in response to the incorrect report that Flight 11 was still airborne and heading south. [9/11 Commission, 7/24/2004, pp. 34]
9/11 Commission Disputes NORAD's Account regarding Flights 175 and 93 - Furthermore, whereas NORAD’s chronology claims that NEADS discussed Flight 93 with the FAA on “a line of open communication,” the 9/11 Commission Report will state that NEADS “first received a call about United 93 from the military liaison at [the FAA’s] Cleveland Center at 10:07,” by which time the plane “had already crashed” (see 10:05 a.m.-10:08 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 30] And while NORAD states that the FAA notified NEADS about Flight 175 at 8:43 a.m., according to the report, the first notification came “in a phone call from [the FAA’s] New York Center to NEADS at 9:03” (see (9:03 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 23]
Military Has Been Slow to Provide Details of Its Response on September 11 - US military officials, according to the Washington Post, “have been slow to respond to press inquiries for a timeline that would establish the exact times that civil aviation authorities became aware of the hijackings, when US military commanders were notified, and when US fighter jets took to the air.” [Washington Post, 9/15/2001] On September 13, Air Force General Richard Myers was questioned about the military’s response to the 9/11 attacks before the Senate Armed Services Committee, but his answers were vague and confused (see September 13, 2001). [US Congress, 9/13/2001; Farmer, 2009, pp. 241-242] A day later, Major General Paul Weaver, director of the Air National Guard, provided reporters with details of the military’s response to the hijackings in an “impromptu hallway interview” at the Pentagon (see September 14, 2001). [Dallas Morning News, 9/14/2001]

Entity Tags: North American Aerospace Defense Command

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Wayne Allard.Wayne Allard. [Source: Publicity photo]General Ralph Eberhart, the commander of the North American Aerospace Defense Command (NORAD), appears before the Senate Armed Services Committee and gives NORAD’s account of the events of September 11 and the military’s response to the terrorist attacks that day, but the 9/11 Commission will later find that some of the information he provides is incorrect. [US Congress. Senate, 10/25/2001; 9/11 Commission, 7/29/2004; Farmer, 2009, pp. 248] Eberhart was at NORAD headquarters at Peterson Air Force Base, Colorado, and then went to NORAD’s operations center in Cheyenne Mountain when the 9/11 attacks were taking place. [9/11 Commission, 3/1/2004 pdf file; 9/11 Commission, 3/1/2004] NORAD released a timeline of its response to the hijackings on September 18 (see September 18, 2001) and Eberhart’s testimony is consistent with that account. [North American Aerospace Defense Command, 9/18/2001]
Eberhart Says Fighters Were Scrambled in Response to First Hijacking - During the hearing, Eberhart tells Senator Wayne Allard (R-CO) that after the Federal Aviation Administration (FAA) alerted NORAD to the first hijacking, of Flight 11 (see (8:37 a.m.) September 11, 2001), NORAD ordered two F-15 fighter jets to take off from Otis Air National Guard Base in Cape Cod, Massachusetts (see 8:46 a.m. September 11, 2001), “almost simultaneously to the first crash” at the World Trade Center (see 8:46 a.m. September 11, 2001). Eberhart says that after he learned a plane had hit the WTC, he was initially unsure if that plane was Flight 11. “I’m sitting there hoping that someone has made a mistake; there has been an accident; that this isn’t the hijacked airplane [that hit the WTC], because there is confusion,” he recalls. He says he was informed that “it was a light commuter airplane” that hit the WTC, although, he says, it “didn’t look like that was caused by a light commuter airplane.”
Fighters Didn't Have Enough Time to Stop Second Crash - Eberhart says the FAA notified NORAD that there was “a second hijacked plane”—referring to Flight 175—“somewhere in there,” but although the Otis fighters were “flying toward New York” after being scrambled, they were still eight minutes away from the city when Flight 175 crashed into the WTC at 9:03 a.m. (see 9:03 a.m. September 11, 2001). “Tragically, there was just too much distance between Otis and New York City to get there in time,” Eberhart comments.
Eberhart Says NORAD Learned Flight 77 Was Hijacked before It Crashed - Eberhart says the first documented instance NORAD has of the FAA notifying it about Flight 77, the third aircraft to be hijacked, was at 9:24 a.m. After the hearing, in responses submitted for the record, Eberhart adds that the FAA notified NORAD’s Northeast Air Defense Sector (NEADS) that Flight 77 “was headed towards Washington, DC.” NEADS, he states, “then passed this information to NORAD’s Air Warning Center and Command Center in Cheyenne Mountain, and to the Continental US NORAD Region’s Regional Air Operations Center.”
Fighters Were Scrambled Too Late to Prevent the Pentagon Attack - Eberhart says NORAD launched two F-16 fighters from Langley Air Force Base in Virginia “as soon as” the FAA alerted it to the hijacking of Flight 77 (see 9:24 a.m. September 11, 2001). However, he says, these fighters were still “approximately 13 minutes away from Washington, DC, when that tragic crash [at the Pentagon] occurred.”
Eberhart Is Unaware of Reason for FAA's Delay in Contacting NORAD - Senator Carl Levin (D-MI) tells Eberhart: “The timeline that we’ve been given is that at 8:55 on September 11, American Airlines Flight 77 began turning east, away from its intended course. And at 9:10, Flight 77 was detected by the FAA radar over West Virginia heading east. That was after the two planes had struck the World Trade Center towers. Then 15 minutes later, at 9:25, the FAA notified NORAD that Flight 77 was headed toward Washington.” In light of this, he asks, “[D]o you know why it took 15 minutes for the FAA to notify NORAD?” Eberhart replies: “I do not know, sir, why it took that amount of time for FAA. I hate to say it, but you’ll have to ask FAA.” Senator John Warner (R-VA), who has an extensive military background, tells Eberhart he is “a little bit stunned that you don’t know why that delay occurred.” He continues, saying, “I would have thought by now all of you in this chain would have gone back, rehearsed these things, figured out what happened, what went wrong, so that we ensure it won’t happen again.” In his responses submitted for the record, Eberhart suggests possible reasons for the delay, stating that after the FAA lost radar contact with Flight 77, it “began to receive calls from outside agencies with reports of a possible downed aircraft. Additionally, the loss of radio contact with the aircraft added to the confusion.” Consequently, he states, “I believe the FAA was faced with conflicting information, which hindered them from making an accurate assessment of the actual location of the aircraft.”
Eberhart Says NORAD Was Following Flight 93 before It Crashed - Eberhart says NORAD was aware of the problems with Flight 93, the fourth hijacked plane, before it crashed in Pennsylvania (see (10:03 a.m.-10:10 a.m.) September 11, 2001 and (10:06 a.m.) September 11, 2001). He tells Allard that the FAA “knew before it deviated its flight pattern” that Flight 93 “was hijacked.” He says NORAD had been “trying to decide, initially, if that flight was going to continue west and if there was some other target for that flight. Was it Chicago? Was it St. Louis? And what might we do to launch an aircraft to intercept it.” But he says that after the FAA reacquired Flight 93 on radar, NORAD thought the plane “was headed probably for Washington, DC, but maybe New York.” He says NORAD decided at that time to keep the Otis and Langley fighters in place over New York and Washington. If another suspicious plane was approaching, he says, “our intent was to go out and meet that aircraft and destroy it if we needed to, if it entered either Washington, DC, or New York City airspace.” However, in his responses submitted for the record, Eberhart states that the “data/log entries received by NORAD from the FAA [after September 11] do not show a time or entry indicating the FAA specifically notified the Pentagon that United Airlines Flight 93 was hijacked.” He also states that NORAD “did not notify” the National Military Command Center (NMCC) at the Pentagon that Flight 93 had been hijacked.
9/11 Commission Disputes Some of Eberhart's Claims - Several claims Eberhart makes in the hearing will be contradicted by evidence uncovered by the 9/11 Commission during its investigation of the terrorist attacks. Whereas Eberhart says the military was first notified about the hijacking of Flight 77 at 9:24 a.m. and implies that this notification prompted the scrambling of fighters from Langley Air Force Base, according to John Farmer, the senior counsel to the 9/11 Commission, “[T]he first notification regarding American 77 occurred at 9:34, when it was reported ‘lost’” (see 9:34 a.m. September 11, 2001). [US Congress. Senate, 10/25/2001; Farmer, 2009, pp. 248-254] The notice NEADS received at 9:24 a.m., according to the 9/11 Commission Report, was the incorrect claim that Flight 11 “had not hit the World Trade Center and was heading for Washington, DC” (see 9:21 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 34] Consequently, Farmer will write, “the scramble of the Langley fighters did occur as an immediate reaction to a notification about hijacking, but that notification was not, as [Eberhart’s] testimony implies, a report that American 77 was hijacked, but the report that American 11 was still airborne and heading for Washington.” And while Eberhart claims the FAA told NEADS that Flight 77 was heading toward Washington, according to Farmer: “The FAA never notified NEADS that American 77 was heading for Washington, DC. There is no such notification recorded on any tape or in any log maintained at NEADS or at NORAD.” Furthermore, while Eberhart claims the military was following Flight 93 on radar before it crashed and was in position to shoot it down if it approached Washington, Farmer will write that “in fact, NEADS never located United 93 on radar, because the plane had already crashed by the time NEADS was notified.” [Farmer, 2009, pp. 251, 254-255]

Entity Tags: John W. Warner, Carl Levin, Ralph Eberhart, North American Aerospace Defense Command, Senate Armed Services Committee, Wayne Allard

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