!! History Commons Alert, Exciting News

Context of '9:06 a.m. September 11, 2001: Flight Controllers Nationwide Are Told Flight 11 Crash Caused by Hijacking'

This is a scalable context timeline. It contains events related to the event 9:06 a.m. September 11, 2001: Flight Controllers Nationwide Are Told Flight 11 Crash Caused by Hijacking. 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.

A military instruction is issued by the chairman of the Joint Chiefs of Staff, outlining the procedure for dealing with hijackings within the United States. The instruction, titled “Aircraft Piracy (Hijacking) and Destruction of Derelict Airborne Objects,” states that “the administrator, Federal Aviation Administration (FAA), has exclusive responsibility to direct law enforcement activity related to actual or attempted aircraft piracy (hijacking) in the ‘special aircraft jurisdiction’ of the United States. When requested by the administrator, Department of Defense will provide assistance to these law enforcement efforts.” It adds that the National Military Command Center (NMCC) within the Pentagon “is the focal point within Department of Defense for providing assistance. In the event of a hijacking, the NMCC will be notified by the most expeditious means by the FAA. The NMCC will, with the exception of immediate responses as authorized by reference d, forward requests for DOD assistance to the secretary of defense for approval.” [US Department of Defense, 6/1/2001 pdf file] Some will later assume that this requirement for defense secretary approval was new with this instruction. [New York Observer, 6/20/2004] But it has in fact been a requirement since 1997, when the previous instruction was issued, if not earlier. [US Department of Defense, 7/31/1997 pdf file] Although the defense secretary has this responsibility, the 9/11 Commission will conclude that, on the day of 9/11, the “secretary of defense did not enter the chain of command until the morning’s key events were over.” [9/11 Commission, 7/24/2004, pp. 15 pdf file] Secretary of Defense Donald Rumsfeld will later claim that, up to 9/11, terrorism and domestic hijackings were “a law enforcement issue.” [9/11 Commission, 3/23/2004; PBS, 3/25/2004; US Department of Defense, 6/14/2005]

Entity Tags: Donald Rumsfeld, Federal Aviation Administration, US Department of Defense, National Military Command Center

Timeline Tags: Complete 911 Timeline

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

Boston flight control begins notifying the chain of command that a suspected hijacking of Flight 11 is in progress. Those notified include the center’s own facility manager, the FAA’s New England Regional Operations Center (ROC) in Burlington, Massachusetts, and the FAA Command Center in Herndon, Virginia (see 8:28 a.m. September 11, 2001). [Federal Aviation Administration, 9/17/2001 pdf file; 9/11 Commission, 8/26/2004, pp. 11] According to the 9/11 Commission, this is consistent with FAA protocol: “From interviews of controllers at various FAA centers, we learned that an air traffic controller’s first response to an aircraft incident is to notify a supervisor, who then notifies the traffic management unit and the operations manager in charge. The FAA center next notifies the appropriate regional operations center (ROC), which in turn contacts FAA headquarters.” [9/11 Commission, 7/24/2004, pp. 458] But according to Ben Sliney, the national operations manager at the FAA’s Command Center, “the protocol was in place that the center that reported the hijacking would notify the military.… I go back to 1964, where I began my air traffic career, and they have always followed the same protocol.” [9/11 Commission, 6/17/2004] Yet Boston Center supposedly will not contact NORAD about Flight 11 until about 12 minutes later (see (8:37 a.m.) September 11, 2001). Already about ten minutes have passed since controllers first noticed a loss of contact with Flight 11 (see (8:15 a.m.) September 11, 2001). Boston reportedly also contacts several other air traffic control centers about the suspected hijacking at this time (see 8:25 a.m. September 11, 2001).

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The FAA Command Center, the center of daily management of the US air traffic system. On 9/11 it is managed by Ben Sliney (not pictured here).The FAA Command Center, the center of daily management of the US air traffic system. On 9/11 it is managed by Ben Sliney (not pictured here). [Source: CNN]The FAA’s Boston Center calls the FAA Command Center and says it believes Flight 11 has been hijacked and is heading toward the New York Center’s airspace. The Command Center immediately establishes a teleconference between the Boston, New York, and Cleveland air traffic control centers, so Boston can help the other centers understand what is happening, in case Flight 11 should enter their airspace. Minutes later, in line with the standard hijacking protocol, the Command Center will pass on word of the suspected hijacking to the FAA’s Washington headquarters (see 8:32 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 19; 9/11 Commission, 8/26/2004, pp. 11; Spencer, 2008, pp. 21]
National Operations Manager Learns of Hijacking - A supervisor at the Command Center promptly passes on the news of the possible hijacking to Ben Sliney, who is on his first day as the national operations manager there. The supervisor says the plane in question is “American Flight 11—a 767 out of Boston for Los Angeles.” According to author Lynn Spencer, “Sliney flashes back to the routine for dealing with hijackings from the days when they were more common.” The procedure is to “[k]eep other aircraft away from the errant plane. Give the pilots what they need. The plane will land somewhere, passengers will be traded for fuel, and difficult negotiations with authorities will begin. The incident should resolve itself peacefully, although the ones in the Middle East, he recalls, often had a more violent outcome.” Apparently not expecting anything worse to happen, Sliney continues to the conference room for the daily 8:30 staff meeting there (see 8:30 a.m.-8:40 a.m. September 11, 2001).
Command Center a 'Communications Powerhouse' - The FAA Command Center is located in Herndon, Virginia, 25 miles from Washington, DC. According to Spencer, it “is a communications powerhouse, modeled after NASA’s Mission Control. The operations floor is 50 feet wide and 120 feet long, packed with tiered rows of computer stations, and at the front, seven enormous display screens show flight trajectories and weather patterns.” The center has nearly 50 specialists working around the clock, planning and monitoring the flow of air traffic over the United States. These specialists work with airlines and air traffic control facilities to fix congestion problems and deal with weather systems. [Spencer, 2008, pp. 1 and 19-20]

Entity Tags: Federal Aviation Administration, Ben Sliney, New York Air Route Traffic Control Center, Boston Air Route Traffic Control Center, Cleveland Air Route Traffic Control Center

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Captain Charles Leidig. 
Captain Charles Leidig. [Source: US Navy]Brigadier General Montague Winfield, the deputy director for operations (DDO) in the National Military Command Center (NMCC) at the Pentagon, leaves his post to attend a pre-scheduled meeting, allowing a colleague, who only recently qualified to take over his position, to stand in for him, and not returning to his post until after the terrorist attacks have ended. [9/11 Commission, 7/21/2003 pdf file; 9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 6/17/2004]
Winfield Attends Air Force-Convened Meeting - Winfield leaves his post to attend what a 9/11 Commission memorandum will call “an unrelated, closed-door personnel meeting convened by the Air Force to discuss the rating of Air Force officers.” [9/11 Commission, 7/21/2003 pdf file] Another Commission memorandum will state that this meeting is a “session for general officers who rated Air Force officers.” It is unclear whether the meeting takes place somewhere in the NMCC or outside the center. The Commission memorandum will only say that it takes place “elsewhere in [Joint Chiefs of Staff] spaces.” At least one of the NMCC’s other qualified DDOs, Brigadier General Norman Seip, is also attending it.
Winfield Asked Colleague to Replace Him on Previous Day - Winfield is temporarily replaced as DDO by Captain Charles Leidig. Leidig only joined the operations directorate of the Joint Chiefs of Staff in July 2001, when he assumed duties as the deputy for Command Center operations. In that, his usual role, he is responsible for the maintenance, operation, and training of watch teams for the NMCC. He qualified to stand in as the DDO in the NMCC about a month ago, in August 2001. The previous afternoon, Winfield asked Leidig to relieve him for a portion of his duty this morning, and Leidig agreed to do so.
Leidig Takes Over as DDO - As arranged, Leidig takes over from Winfield as DDO at 8:30 a.m., allowing Winfield to attend his meeting. Upon arrival at the NMCC, Leidig receives the intelligence and other turn over briefings. After seeing the reports of the plane crashes in New York on television, he will be responsible for convening a significant event conference (see 9:29 a.m.-9:34 a.m. September 11, 2001), which he soon upgrades to an air threat conference (see 9:37 a.m.-9:39 a.m. September 11, 2001). [9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 6/17/2004 pdf file]
Winfield Does Not Resume Duties until Attacks Are Over - Even though it becomes obvious that a coordinated attack is under way when television shows the second plane hitting the World Trade Center at 9:03 a.m. (see 9:03 a.m. September 11, 2001), Winfield apparently remains in his meeting instead of resuming his duties as DDO (see (Shortly After 9:03 a.m.) September 11, 2001). He will only take over from Leidig as DDO after Flight 93 crashes in Pennsylvania, apparently at around 10:30 a.m. (see (10:30 a.m.) September 11, 2001). [9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 6/17/2004] In later interviews for television, Winfield will give the impression that he remained in charge of the NMCC throughout the 9/11 attacks, and make no mention of having allowed a stand-in to take his place during this most critical period of time. [CNN, 9/4/2002; ABC News, 9/11/2002]

Entity Tags: Montague Winfield, Norman R. Seip, Charles Leidig

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

NORAD fails to notify the National Military Command Center (NMCC) at the Pentagon that aircraft have been hijacked before the NMCC initiates a significant event conference in response to the terrorist attacks. [9/11 Commission, 6/9/2004] NORAD’s Northeast Air Defense Sector (NEADS) was alerted to the first hijacking, of Flight 11, at 8:37 a.m. (see (8:37 a.m.) September 11, 2001) and it is alerted to the second hijacking, of Flight 175, at 9:03 a.m. (see (9:03 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20, 23] And yet, according to an after-action report produced by the NMCC, NORAD does not contact the NMCC to alert it to these incidents before the significant event conference commences, at 9:29 a.m. (see 9:29 a.m.-9:34 a.m. September 11, 2001). [9/11 Commission, 6/9/2004]
NORAD Does Not Provide Information to Deputy Director - Captain Charles Leidig, the acting deputy director for operations in the NMCC, will later say that he “does not remember getting a lot of information from NORAD” before the significant event conference begins. [9/11 Commission, 4/29/2004 pdf file] NMCC personnel apparently learn that an aircraft has been hijacked when an officer in the center calls the FAA at 9:00 a.m. (see 9:00 a.m. September 11, 2001). [9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 5/5/2004; 9/11 Commission, 7/24/2004, pp. 35]
NORAD First Mentions a Hijacking at 9:33 a.m. - NORAD will apparently talk to the NMCC about a hijacking for the first time at around 9:33 a.m., when its representative on the significant event conference states that they “concur that [a] hijacked aircraft is still airborne [and] heading towards Washington, DC.” [US Department of Defense, 9/11/2001; US Department of Defense, 9/11/2001 pdf file] (They will presumably be referring to the incorrect information that Flight 11 is still in the air after it has crashed into the World Trade Center (see 9:21 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 26] )
NORAD Does Not Request a Conference - Additionally, according to the NMCC’s after-action report, NORAD “does not request any conference at [National Command Authority] level” prior to the commencement of the significant event conference. [9/11 Commission, 6/9/2004] The significant event conference is actually initiated by Leidig. The NMCC has an important role to play in an emergency like the current crisis. Its job under these circumstances “is to gather the relevant parties and establish the chain of command between the National Command Authority—the president and the secretary of defense—and those who need to carry out their orders,” according to the 9/11 Commission Report. [9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 7/24/2004, pp. 37] It is also “the focal point within [the] Department of Defense for providing assistance” when there is a hijacking in US airspace, according to a recent military instruction (see June 1, 2001). [US Department of Defense, 6/1/2001 pdf file]

Entity Tags: National Military Command Center, North American Aerospace Defense Command, Charles Leidig

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Flight 175 passes from the airspace of the FAA’s Boston Center to the airspace of the New York Center, which is in Ronkonkoma, New York. [9/11 Commission, 8/26/2004, pp. 20] New York Center air traffic controller Dave Bottiglia takes over monitoring the flight from Boston Center controller John Hartling (see (8:34 a.m.) September 11, 2001). Flight 175 waits nearly 45 seconds to check in with Bottiglia. According to author Lynn Spencer, this is “rather long, and Bottiglia is just about to call the plane.” But then Captain Victor Saracini, the pilot of Flight 175, makes radio contact, saying, “New York, United 175 heavy.” [Gregor, 12/21/2001 pdf file; Spencer, 2008, pp. 36]

Entity Tags: Dave Bottiglia, New York Air Route Traffic Control Center, Victor Saracini

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Victor Saracini.Victor Saracini. [Source: Family photo]Just after Flight 175 enters the airspace of the FAA’s New York Center (see 8:40 a.m. September 11, 2001), its pilot reports to the air traffic controller now managing the flight a suspicious transmission he had heard on departing Boston’s Logan Airport. The pilot, Captain Victor Saracini, tells the controller, Dave Bottiglia: “We figured we’d wait to go to your center. Ah, we heard a suspicious transmission on our departure out of Boston, ah, with someone, ah, it sounded like someone keyed the mikes and said, ah, ‘Everyone, ah, stay in your seats.’” [New York Times, 10/16/2001; 9/11 Commission, 7/24/2004, pp. 21; Spencer, 2008, pp. 36] Saracini is presumably referring to one of the three radio transmissions from Flight 11, where the voice of a hijacker could be heard (see 8:24 a.m. September 11, 2001 and (8:34 a.m.) September 11, 2001). However, none of these had included the hijacker telling people to stay in their seats, as Saracini describes, although the second and third transmissions included the hijacker telling the passengers, “Nobody move.” [9/11 Commission, 7/24/2004, pp. 19] Bottiglia responds: “Oh, okay. I’ll pass that along.” Referring to the fact that this was the end of the transmission he heard, Saracini adds, “It cut out,” and then asks Bottiglia, “Did you copy that?” [Gregor, 12/21/2001 pdf file; Spencer, 2008, pp. 36-37] This is the last radio transmission from Flight 175. The 9/11 Commission will conclude that the plane is hijacked within the next four minutes (see (Between 8:42 a.m. and 8:46 a.m.) September 11, 2001). [9/11 Commission, 8/26/2004, pp. 20] According to author Lynn Spencer, since controllers are only given information on a need-to-know basis, Bottiglia was unaware there were problems with Flight 11, which has not yet entered his airspace. He touches his computer screen to connect to the hotline for his sector controller, and then reports: “UAL 175 just came on my frequency and he said he heard a suspicious transmission when they were leaving Boston. ‘Everybody stay in your seats’—that’s what he heard… just to let you know.” [New York Times, 10/16/2001; Spencer, 2008, pp. 36-37]

Entity Tags: New York Air Route Traffic Control Center, Victor Saracini, Dave Bottiglia

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Dave Bottiglia.Dave Bottiglia. [Source: ABC News]After Flight 11 appears on his radar screen, Dave Bottiglia, an air traffic controller at the FAA’s New York Center, is informed that this aircraft is suspected of having been hijacked. Flight 175 entered Bottiglia’s airspace not long before this (see 8:40 a.m. September 11, 2001). [MSNBC, 9/11/2002; 9/11 Commission, 8/26/2004, pp. 20] Its pilot has just told Bottiglia about the “suspicious transmission” (presumably from Flight 11) he heard while departing Boston airport (see 8:41 a.m.-8:42 a.m. September 11, 2001). [Gregor, 12/21/2001 pdf file] Seconds later, Flight 11 also enters the area Bottiglia is monitoring and its target appears on his radar screen. The controller sitting next to Bottiglia gets up and points to the radar blip. He says: “You see this target here? This is American 11. Boston Center thinks it’s a hijack.” Bottiglia will later recall that his initial thought about Flight 11, based on this information, is that the hijackers “were probably going to Cuba.” As its transponder has been turned off (see (Between 8:13 a.m. and 8:21 a.m.) September 11, 2001), he has no altitude information for Flight 11, but can tell from the radar scope that it appears to be descending. According to author Lynn Spencer: “Even without a transponder, controller radars calculate ground speed for all radar targets, and when a plane is descending, the ground speed decreases. The flight had been ‘grounding’ 600 knots, and now it has decreased to 320.” Bottiglia follows Flight 11’s target on his radar screen until it disappears over New York City. [MSNBC, 9/11/2002; Spencer, 2008, pp. 37] Because he is focused on Flight 11, Bottiglia will not notice when Flight 175’s transponder code changes at 8:47 (see 8:46 a.m.-8:47 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 21; 9/11 Commission, 8/26/2004, pp. 21] The New York Center was first notified of Flight 11’s hijacking at 8:25 a.m. (see 8:25 a.m. September 11, 2001), though this information was not passed on to Bottiglia. [Federal Aviation Administration, 9/17/2001 pdf file; Spencer, 2008, pp. 36-37]

Entity Tags: Dave Bottiglia, New York Air Route Traffic Control Center

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

After 9/11, NORAD and other sources will claim that NORAD’s Northeast Air Defense Sector (NEADS) is notified at this time that Flight 175 has been hijacked. [Washington Post, 9/12/2001; CNN, 9/17/2001; North American Aerospace Defense Command, 9/18/2001; Associated Press, 8/19/2002; Newsday, 9/10/2002] However, the FAA’s New York Center, which is handling Flight 175, first alerts its military liaison about the hijacking at around 9:01 (see 9:01 a.m.-9:02 a.m. September 11, 2001). In addition, according to the 9/11 Commission, NEADS is not informed until two minutes later (see (9:03 a.m.) September 11, 2001). [9/11 Commission, 6/17/2004] According to the Commission, the first “operational evidence” that there is something wrong on Flight 175 is not until 8:47, when its transponder code changes (see 8:46 a.m.-8:47 a.m. September 11, 2001), and it is not until 8:53 that the air traffic controller handling it concludes that Flight 175 may be hijacked (see 8:51 a.m.-8:53 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 7, 21-22]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Flight 175 stops transmitting its transponder signal. It is currently flying near the New Jersey-Pennsylvania border. [Guardian, 10/17/2001; Newsday, 9/10/2002; 9/11 Commission, 6/17/2004] However, the transponder is turned off for only about 30 seconds, and then comes back on as a signal that is not designated for any plane on this day. Then, within the space of a minute, it is changed to another new code. But New York Center air traffic computers do not correlate either of these new transponder codes with Flight 175. Consequently, according to an early FAA report, “the secondary radar return (transponder) indicating aircraft speed, altitude, and flight information began to coast and was no longer associated with the primary radar return.” Therefore, while controllers are able “to track the intruder easily… they couldn’t identify it.” However, Dave Bottiglia, the New York Center air traffic controller responsible for Flight 175, is currently trying to locate the already-crashed Flight 11, and therefore supposedly does not notice the transponder code changes on Flight 175 until 8:51 a.m. (see 8:51 a.m.-8:53 a.m. September 11, 2001). [Federal Aviation Administration, 9/17/2001 pdf file; Washington Post, 9/17/2001; 9/11 Commission, 8/26/2004, pp. 21] According to a “Flight Path Study” by the National Transportation Safety Board, the change of Flight 175’s transponder code is the “first indication of deviation from normal routine.” [National Transportation Safety Board, 2/19/2002 pdf file]

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Curt Applegate sitting next to his air traffic control terminal.Curt Applegate sitting next to his air traffic control terminal. [Source: NBC News]After being focused on Flight 11, Dave Bottiglia, an air traffic controller at the FAA’s New York Center, first notices problems with Flight 175. [MSNBC, 9/11/2002; 9/11 Commission, 7/24/2004, pp. 21] Both Flight 11 and Flight 175 have been in the airspace that Bottiglia is responsible for monitoring (see 8:40 a.m. September 11, 2001 and (8:42 a.m.-8:46 a.m.) September 11, 2001). Bottiglia has just watched Flight 11’s radar blip disappear, which means the plane has dipped below his radar’s coverage area, so is below 2,000 feet. But he does not yet realize it has crashed. He says aloud, “Well, we know he’s not high altitude anymore.” [MSNBC, 9/11/2002; Spencer, 2008, pp. 37] Around this time, Flight 175’s transponder changes twice in the space of a minute (see 8:46 a.m.-8:47 a.m. September 11, 2001).
Conflicting Accounts - According to MSNBC, “within seconds” of losing Flight 11’s blip, “Bottiglia has another unexpected problem.” While looking for Flight 11, he realizes that Flight 175 is also missing, and “instinctively… knows the two [planes] are somehow related.” He asks another controller to take over all of his other planes. [MSNBC, 9/11/2002] But according to the 9/11 Commission’s account, Bottiglia is still trying to locate Flight 11 after it crashes, and so it is not until 8:51 a.m. that he notices the problem with Flight 175 (see 8:51 a.m.-8:53 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 21]
'An Intruder over Allentown' - Around the time Flight 175 changes its transponder code, air traffic controller Curt Applegate, who is sitting at the radar bank next to Bottiglia’s, sees a blip that might be the missing Flight 11. He shouts out: “Look. There’s an intruder over Allentown.” According to the Washington Post, “In air traffic jargon, an ‘intruder’ is a plane with an operating transponder that has entered restricted airspace without permission.” In fact, it is the missing Flight 175. [Washington Post, 9/17/2001; MSNBC, 9/11/2002] However, these accounts make no mention of NORAD being notified about the problems with Flight 175 at this time. But according to a NORAD timeline released shortly after 9/11, NORAD’s Northeast Air Defense Sector (NEADS) was alerted about Flight 175 by the FAA several minutes earlier, at 8:43 a.m. (see 8:43 a.m. September 11, 2001). [North American Aerospace Defense Command, 9/18/2001]

Entity Tags: Dave Bottiglia, Curt Applegate, New York Air Route Traffic Control Center

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

Officers in the National Military Command Center (NMCC) at the Pentagon begin notifying senior Pentagon officials about the plane crashing into the World Trade Center after learning of this from television, but they are apparently unaware of the hijacking of Flight 11. [9/11 Commission, 7/21/2003 pdf file; 9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 7/24/2004, pp. 35] The NMCC’s three main missions are monitoring worldwide events for the Joint Chiefs of Staff (JCS), maintaining a strategic watch component, and maintaining a crisis response component. The NMCC has live feeds from numerous television stations, and the operations team on duty there learned from CNN that an aircraft had hit the WTC (see (8:48 a.m.) September 11, 2001).
NMCC Directors Notify Senior Pentagon Officials of Crash - In response, members of the operations team monitor media reports and begin making notifications up the chain of command. [9/11 Commission, 7/21/2003 pdf file; 9/11 Commission, 4/29/2004 pdf file] Captain Charles Leidig, who is currently standing in temporarily as deputy director for operations in the NMCC (see 8:30 a.m. September 11, 2001), will later recall, “Initially… the National Military Command Center was primarily a means to notify senior leadership that, in fact, an event had occurred.” [9/11 Commission, 6/17/2004] Leidig and Commander Patrick Gardner, the assistant deputy director for operations, start notifying those on the internal JCS notification list, including the office of the chairman of the Joint Chiefs of Staff, about the crash. They also notify the office of the secretary of defense. Based on incorrect information being reported on television, Leidig tells the senior Pentagon officials that a small airplane has crashed into one of the towers of the WTC. [9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 7/24/2004, pp. 35]
NMCC Unaware of Flight 11 Hijacking - According to military instructions, “the NMCC is the focal point within [the] Department of Defense for providing assistance” in response to aircraft hijackings in US airspace, and, “In the event of a hijacking, the NMCC will be notified by the most expeditious means by the FAA” (see June 1, 2001). [US Department of Defense, 6/1/2001 pdf file] However, while details of the hijacking of Flight 11 have been circulating within the FAA, the 9/11 Commission will say it “found no evidence that the hijacking was reported to any other agency in Washington before 8:46.” The NMCC apparently learns of the hijacking for the first time when one of its officers calls the FAA at 9:00 a.m. (see 9:00 a.m. September 11, 2001). Leidig will recall that, before the second plane hits the WTC at 9:03 a.m., he and Gardner think it is “something unusual… that a light plane had crashed into the WTC and that there was a report of a hijacking.” [9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 7/24/2004, pp. 35, 462]

Entity Tags: Charles Leidig, Patrick Gardner, National Military Command Center

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Scott Fry.Scott Fry. [Source: NATO]Vice Admiral Scott Fry, a top official at the Pentagon with important responsibilities, goes to a dental appointment and only becomes involved with the response to the attacks after the second crash in New York. [Creed and Newman, 2008, pp. 4-6] Fry is the director of operations of the Joint Staff, a post he has held since 1998. [US Department of Defense, 9/23/1998; Stars and Stripes, 10/4/2001] In this position, he is responsible for running the National Military Command Center (NMCC)—“the Pentagon’s highly secure nerve center”—and the Executive Support Center (ESC)—a suite of rooms at the Pentagon “where the secretary of defense, the Joint Chiefs of Staff, and other senior officials would meet to discuss urgent matters.” [Creed and Newman, 2008, pp. 5-6] He is due to leave shortly for Italy, where he is to take up an important Navy command. [Department of Defense, 9/4/2001; Stars and Stripes, 10/4/2001; Creed and Newman, 2008, pp. 4-5] Fry is anxious to go to the dentist before leaving for Italy. As he is about to leave his office for a 9:00 a.m. appointment, his executive assistant draws his attention to the television coverage of the first attack in New York. Reportedly believing the crash was “probably just a freak accident,” instead of heading to the NMCC or the ESC, Fry continues to the clinic (which is presumably within the Pentagon), and is in the dentist’s chair when the second attack occurs. His assistant then calls him on his cell phone to alert him to this. Fry reportedly concludes: “One airplane hitting a skyscraper, that was damned suspicious. But two… there was no doubt about it. It had to be a terrorist attack.” He promptly cancels his appointment and hurries to the NMCC. From there, he goes upstairs to the ESC, where a group is already assembling (see Shortly After 9:03 a.m. September 11, 2001). In the ESC, a “video teleconference link could connect them to the White House, the State Department, the CIA, and military commanders throughout the world.” There, Fry discusses events in New York with Defense Secretary Donald Rumsfeld’s aide Stephen Cambone. But, reportedly, what the men know is “not much, except what they could see on TV.” [Creed and Newman, 2008, pp. 4-6] Only a few months previously, on June 1, 2001, a new Defense Department directive on dealing with domestic hijackings was issued under Fry’s signature (see June 1, 2001). [US Department of Defense, 6/1/2001 pdf file]

Entity Tags: National Military Command Center, Scott Fry, Executive Support Center, Stephen A. Cambone

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to the 9/11 Commission, Dave Bottiglia, the air traffic controller handling Flight 175, only notices now that this flight’s transponder signal has changed (see 8:46 a.m.-8:47 a.m. September 11, 2001). Bottiglia asks Flight 175 to return to its proper transponder code. There is no response. Beginning at 8:52 a.m., he makes repeated attempts to contact it, but there is still no response. Bottiglia contacts another controller at 8:53 a.m., and says: “We may have a hijack. We have some problems over here right now.… I can’t get a hold of UAL 175 at all right now and I don’t know where he went to.” [New York Times, 10/16/2001; 9/11 Commission, 6/17/2004; Spencer, 2008, pp. 48] This account apparently conflicts with earlier accounts that claim NORAD’s Northeast Air Defense Sector (NEADS) was notified at 8:43 a.m. that Flight 175 had been hijacked (see 8:43 a.m. September 11, 2001). [North American Aerospace Defense Command, 9/18/2001]

Entity Tags: Dave Bottiglia

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Mike McCormick.Mike McCormick. [Source: Associated Press]Mike McCormick, the head of the FAA’s New York Center, sees the coverage of the first World Trade Center attack on CNN. He assumes that Flight 175, which he is tracking on his radar screen, is also headed into the WTC. He will recall: “Probably one of the most difficult moments of my life was the 11 minutes from the point I watched that aircraft, when we first lost communications until the point that aircraft hit the World Trade Center. For those 11 minutes, I knew, we knew, what was going to happen, and that was difficult.” [CNN, 8/12/2002] Yet, according to the 9/11 Commission, the New York Center will not notify NORAD’s Northeast Air Defense Sector (NEADS) about Flight 175 until around the time it crashes, at 9:03 a.m. (see (9:03 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 23]

Entity Tags: New York Air Route Traffic Control Center, Mike McCormick

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Adam AriasAdam Arias [Source: US Air Force]Major Don Arias, the public affairs officer for NORAD, has just learned of the first WTC crash from television and a phone call from NEADS (see (8:38 a.m.-8:52 a.m.) September 11, 2001). Alarmed because his younger brother works at the WTC, he calls him immediately. Adam Arias works for an investment company on the 84th floor of the South Tower. According to some accounts, Don Arias tells his brother that the aircraft that crashed into the North Tower was likely a hijacked plane that he has been informed of, and orders him to “Get out of there. Go home.” [Florida State Times, 11/2001; Newhouse News Service, 1/25/2002; Airman, 9/2002] But according to Newsday, Don Arias tells his brother he has heard there is “another hijacked airliner and might be another attack.” [Newsday, 10/30/2001] This would be consistent with an early NORAD timeline, which had the agency receiving notification of the second hijacking at 8:43 a.m. (see 8:43 a.m. September 11, 2001). However, later accounts, including the 9/11 Commission Report, will claim NORAD only hears of it around the time the plane hits the South Tower (see (9:03 a.m.) September 11, 2001). Adam Arias reacts to his brother’s call with urgency, going around the floor exhorting people to leave, and physically throwing one woman out of her office. Several survivors will later credit him with saving their lives. [Newhouse News Service, 1/25/2002; Airman, 9/2002; Filson, 2003, pp. 124] Adam Arias will be killed when the South Tower collapses. [Seattle Post-Intelligencer, 9/9/2003]

Entity Tags: Don Arias

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The head air traffic controller at the FAA’s New York Center notifies a manager at the facility that she believes Flight 175 has been hijacked. The manager tries to notify regional managers about this, but cannot reach them because they are discussing the hijacking of Flight 11 and refuse to be disturbed. However, even though the controller managing Flight 175 said, “we may have a hijack” at 8:53 a.m. (see 8:51 a.m.-8:53 a.m. September 11, 2001), the 9/11 Commission will conclude that NORAD’s Northeast Air Defense Sector (NEADS) is not notified about the aircraft until 9:03 a.m. (see (9:03 a.m.) September 11, 2001). [9/11 Commission, 6/17/2004] The Commission’s account will conflict with previous accounts that state that NEADS was notified of the Flight 175 hijacking at 8:43 a.m. (see 8:43 a.m. September 11, 2001). The head of the New York Center, Mike McCormick, has already decided at 8:52 a.m. that Flight 175 has been hijacked and is on a suicide run to New York City (see (8:52 a.m.) September 11, 2001). [CNN, 8/12/2002]

Entity Tags: New York Air Route Traffic Control Center, Mike McCormick

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

About a half-dozen air traffic controllers at the FAA’s New York Center in Ronkonkoma, NY, watch Flight 175 on the radar screen in its final minutes, as it approaches Manhattan. [National Transportation Safety Board, 2/19/2002 pdf file; Vanity Fair, 8/1/2006] Flight 175 is marked on the screen with the letter “I” for “intruder.” Initially, those at the center think it might be heading for Newark Airport, maybe for an emergency landing there. But controller Jim Bohleber says, “No, he’s too fast and low, he’ll never make Newark.” [Newsday, 9/10/2002] The controllers start speculating what Flight 175 is aiming for, with one of them guessing the Statue of Liberty. [Vanity Fair, 8/1/2006] They are astonished at the extraordinary rate at which it is descending (see (8:58 a.m.-9:03 a.m.) September 11, 2001). A controller counts down its altitude, “Eight, six, four” thousand feet, and then says, “My god, he’s in the ground in the next step.” But someone else at the center says, “No, that’s the Trade Center right there.” [The Learning Channel, 8/20/2006] But, according to the 9/11 Commission, the New York Center does not notify NORAD’s Northeast Air Defense Sector (NEADS) about Flight 175 until 9:03 a.m., the same time as it crashes into the South Tower (see (9:03 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 23] Workers at the crisis center at United Airlines’ headquarters outside Chicago, also closely watch Flight 175 head into New York City on radar. [USA Today, 8/12/2002]

Entity Tags: New York Air Route Traffic Control Center, Jim Bohleber

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Ryan Gonsalves.Ryan Gonsalves. [Source: Institute for the Study of War]An officer in the National Military Command Center (NMCC) at the Pentagon learns, during a phone call to the FAA, of the hijacking of Flight 11, but the FAA tells him it does not need any help dealing with this, as everything seems to be under control. [9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 7/24/2004, pp. 35]
NMCC Officer Calls FAA for Information - After those in the NMCC learned from television that an aircraft had crashed into the World Trade Center (see (8:48 a.m.) September 11, 2001), Lieutenant Colonel Ryan Gonsalves, the senior operations officer there, began gathering up as much information as he could on the crisis. One of the phone calls he makes is to the FAA operations center at the agency’s Washington, DC, headquarters. The employee at the operations center who answers the call tells Gonsalves that the FAA has had a report of a hijacking on a plane that departed Boston. [9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 5/5/2004]
FAA Says It Does Not Need Help - The FAA employee apparently does not connect the plane crashing into the WTC with the hijacked Flight 11, which they claim is still airborne and heading for New York’s JFK International Airport. The entry in the senior operations officer’s log about the call will state: “9:00 NMCC called FAA, briefed of explosion at WTC possibly from aircraft crash. Also, hijacking of American Flight 11 from Boston to LA, now en route to Kennedy.” [9/11 Commission, 7/24/2004, pp. 462] Furthermore, when Gonsalves asks if the FAA needs any assistance dealing with the hijacking, the operations center employee replies, “No,” and says the pilot “had called in and said everything was under control, and he was going to land at New York shortly.” [9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 5/5/2004] The possibility of scrambling fighter jets is not discussed during the phone call. Even though military instructions state that the NMCC is to be “notified by the most expeditious means by the FAA” in response to aircraft hijackings in US airspace (see June 1, 2001), this call, according to the 9/11 Commission Report, appears to be the first time the FAA informs the NMCC of the hijacking of Flight 11. [US Department of Defense, 6/1/2001 pdf file; 9/11 Commission, 7/24/2004, pp. 35]

Entity Tags: National Military Command Center, Federal Aviation Administration, Ryan Gonsalves

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The military liaison at the FAA’s New York Center is reportedly told that Flight 175 has been hijacked. The information is passed on to the liaison by New York Center manager Peter Mulligan. In an apparent reference to the hijacking on a phone bridge with other air traffic control facilities, Mulligan first says the situation is escalating (see (9:01 a.m.) September 11, 2001) and adds, “Just get me somebody who has the authority to get military in the air now.” Mulligan then drops out of the teleconference for a short while, but returns and says: “It’s OK. I’ve got it taken care of over here. I got… my military guy. We got some interceptors in the air.” [Federal Aviation Administration, 10/14/2003, pp. 15-17 pdf file] According to the 9/11 Commission Report, Mulligan says this between 9:01 and 9:02. [9/11 Commission, 7/24/2004, pp. 22] A person at the New York Center then calls NEADS at 9:03 (see (9:03 a.m.) September 11, 2001). Presumably, this is the military liaison Mulligan just informed of the hijacking.

Entity Tags: Peter Mulligan

Timeline Tags: Complete 911 Timeline

Moments before Flight 175 crashes into the World Trade Center, Colin Scoggins, the military liaison at the FAA’s Boston Center, calls NORAD’s Northeast Air Defense Sector (NEADS) to notify it that there is a second hijacked aircraft over the US. Scoggins learned of the second hijacking on the FAA headquarters’ hijack teleconference (see (Shortly Before 9:02 a.m.) September 11, 2001) and senses that he should call NEADS with this latest information. According to author Lynn Spencer, Scoggins “imagines that he must be one of dozens of FAA facilities flooding [NEADS] with phone calls. What he doesn’t know is that his is in fact the only one giving them information about the flights this morning, other than the coverage on CNN.” [Spencer, 2008, pp. 82] However, the 9/11 Commission will say that NEADS also learns of the second hijacking around this time from the FAA’s New York Center, stating, “The first indication that the NORAD air defenders had of the second hijacked aircraft, United 175, came in a phone call from New York Center to NEADS at 9:03” (see (9:03 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 23] Just after Scoggins reports the second hijacking to NEADS, those on the NEADS operations floor see the live television coverage of Flight 175 hitting the South Tower on a screen at the front of the room. [Spencer, 2008, pp. 82] Apparently, Scoggins’s phone call continues for several minutes: According to the 9/11 Commission, “Between 9:04 a.m. and 9:07 a.m., the NEADS identification technicians were on the phone with FAA Boston Center seeking further information on Flight 175 when Boston Center confirmed a second crash at the World Trade Center.” [9/11 Commission, 8/26/2004, pp. 24]

Entity Tags: Boston Air Route Traffic Control Center, Colin Scoggins, Northeast Air Defense Sector

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The 9/11 Commission will later conclude that the FAA’s New York Center tells NORAD’s Northeast Air Defense Sector (NEADS) that Flight 175 has been hijacked at this time. The Commission will refer to this as “the first indication that the NORAD air defenders had of the second hijacked aircraft.” The notification is apparently received from the military liaison at the New York Center (see 9:01 a.m.-9:02 a.m. September 11, 2001). [9/11 Commission, 6/17/2004]
NEADS Technician Announces 'Second Possible Hijack' - Tape recordings of the NEADS operations floor will reveal ID tech Stacia Rountree answering the call from the New York Center, and saying out loud, “They have a second possible hijack!” [Vanity Fair, 8/1/2006] Colonel Robert Marr, the NEADS battle commander, will claim he first learns that an aircraft other than Flight 11 has been hijacked when he sees Flight 175 crash into the World Trade Center on television. [Aviation Week and Space Technology, 6/3/2002] Lieutenant Colonel Dawne Deskins will claim that when she sees Flight 175 hitting the South Tower on television, “we didn’t even know there was a second hijack.” [Filson, 2003, pp. 59]
Conflicting Accounts - However, these accounts contradict NORAD’s claim that it makes shortly after 9/11 that NEADS was first notified about Flight 175 at 8:43 a.m. (see 8:43 a.m. September 11, 2001). [North American Aerospace Defense Command, 9/18/2001] Additionally, as Flight 175 crashes into the WTC, Canadian Captain Mike Jellinek, who is working at NORAD’s Cheyenne Mountain, Colorado operations center, is on the phone with NEADS. He sees the crash live on television and asks NEADS, “Was that the hijacked aircraft you were dealing with?” The reply is yes. (However, it is unclear whether Jellinek is referring to Flight 175 or to the smoke coming from the crash of Flight 11.) [Toronto Star, 12/9/2001] If the 9/11 Commission’s account is correct, several questions remain unanswered. Flight 175 lost radio contact at 8:42 a.m. (see 8:41 a.m.-8:42 a.m. September 11, 2001) and changed transponder signals at 8:47 a.m. (see 8:46 a.m.-8:47 a.m. September 11, 2001); an air traffic controller declared it possibly hijacked sometime between 8:46 a.m. and 8:53 a.m. (see (Shortly After 8:46 a.m.) September 11, 2001); and an air traffic control manager called it hijacked at 8:55 a.m.(see (8:55 a.m.) September 11, 2001). The Commission will not explain why the New York Center waits 10 to 16 minutes before warning NEADS that Flight 175 is possibly hijacked. [9/11 Commission, 6/17/2004]

Entity Tags: Stacia Rountree, Northeast Air Defense Sector, North American Aerospace Defense Command, Robert Marr, Michael H. Jellinek, New York Air Route Traffic Control Center

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Shortly after the second attack on the World Trade Center, FBI agents call the FAA’s Cleveland Center and warn air traffic controllers there to keep an eye on Delta Air Lines Flight 1989. According to USA Today, controllers at the Cleveland Center, which is tracking Delta 1989, have already been watching this flight, and, like the FBI, suspect “that terrorists plan to hijack [it] next.” Although Delta 1989 is not showing any signs of being hijacked, the reason for their suspicion is that it has many similarities to the two aircraft that hit the World Trade Center: it is also a Boeing 767, heavy with fuel, and had taken off from Boston’s Logan Airport around the same time as they did. [USA Today, 8/13/2002] At 9:27 a.m., the FAA’s Boston Center will—apparently mistakenly—report that Delta 1989 is missing (see 9:27 a.m. September 11, 2001). [9/11 Commission, 5/23/2003] And at around 9:30 a.m., Cleveland Center controllers will mistakenly conclude that it has been hijacked (see (9:28 a.m.-9:33 a.m.) September 11, 2001). [USA Today, 8/13/2002]

Entity Tags: Cleveland Air Route Traffic Control Center, Federal Bureau of Investigation

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

All flight control facilities nationwide are notified that the Flight 11 crash into the WTC was probably a hijacking. [US Congress. House. Committee On Transportation And Infrastructure, 9/21/2001; Newsday, 9/23/2001]

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

NEADS commander Robert Marr.NEADS commander Robert Marr. [Source: Dick Blume]Numerous reports incorrectly claiming that aircraft have been hijacked are received while the terrorist attacks are taking place and into the afternoon. [Code One Magazine, 1/2002; Newhouse News Service, 3/31/2005; Politico Magazine, 9/9/2016] There are “multiple erroneous reports of hijacked aircraft” during the morning, according to the 9/11 Commission Report. [9/11 Commission, 7/24/2004, pp. 28] At around 9:09 a.m., the FAA Command Center reports that 11 aircraft are either not communicating with FAA facilities or flying unexpected routes. [Aviation Week and Space Technology, 6/3/2002] Major General Larry Arnold, the commander of the Continental United States NORAD Region, will later claim that during the “four-hour ordeal” of the attacks, a total of 21 planes are identified as possible hijackings. [Filson, 2002; Code One Magazine, 1/2002; Filson, 2003, pp. 71] Colonel Robert Marr, the battle commander at NORAD’s Northeast Air Defense Sector (NEADS), will say, “At one time I was told that across the nation there were some 29 different reports of hijackings.” [Newhouse News Service, 3/31/2005] Secret Service agent Dave Wilkinson, who travels with President Bush on Air Force One after it leaves Sarasota, Florida (see 9:54 a.m. September 11, 2001), will recall that by the time the plane reaches Offutt Air Force Base in Nebraska, at 2:50 p.m. (see 2:50 p.m. September 11, 2001), “there were like 15 to 20 planes still unaccounted for” nationwide. “For everything we knew, they were all hijacked,” he will say. [Politico Magazine, 9/9/2016] Officials will claim that these false reports cause considerable confusion. Arnold will recall that particularly during the time between the Pentagon being hit at, 9:37 a.m., and Flight 93 going down, at around 10:03 a.m., “a number of aircraft are being called possibly hijacked.… There was a lot of confusion, as you can imagine.” [Filson, 2003, pp. 71-73] He will say: “We were receiving many reports of hijacked aircraft. When we received those calls, we might not know from where the aircraft had departed. We also didn’t know the location of the airplane.” [Code One Magazine, 1/2002] Marr will comment: “There were a number of false reports out there. What was valid? What was a guess? We just didn’t know.” [Filson, 2003, pp. 73] Assistant Secretary of Defense for Public Affairs Victoria Clarke, who is in the Pentagon during the attacks and for most of the rest of the day, will recall: “There were lots of false signals out there. There were false hijack squawks, and a great part of the challenge was sorting through what was a legitimate threat and what wasn’t.” [CNN, 6/17/2004; Clarke, 2006, pp. 215-231]

Entity Tags: Federal Aviation Administration, Robert Marr, Dave Wilkinson, Victoria (“Torie”) Clarke, Larry Arnold

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The FAA Command Center in Herndon, Virginia.The FAA Command Center in Herndon, Virginia. [Source: Federal Aviation Administration]Ben Sliney, the national operations manager at the FAA’s Herndon Command Center, puts the word out that he wants all air traffic control facilities around the US to inform him of anything unusual that occurs with the flights they are handling. In response, news of suspicious activity quickly starts coming in to the Command Center. [Spencer, 2008, pp. 125-126]
Command Center Calls Field Facilities - Sliney wants air traffic control facilities to notify him of anything out of the ordinary, such as a radar target disappearing from the radar scope, loss of communication with an aircraft, or an aircraft making an unauthorized change of course. He also wants to know immediately of any glitches that occur, even if these are common, everyday problems, such as a flight deviating from its course, missing a frequency change, overlooking a radio call, or getting a transponder code wrong. The center’s controllers at each regional desk therefore start calling their field facilities, and ask them to report any unusual occurrences. [9/11 Commission, 7/22/2003 pdf file; Spencer, 2008, pp. 125] The Command Center has telecommunications lines to all the major air traffic control facilities in the US, which enables it to reach out to those facilities and establish the big picture about aircraft activity. [Freni, 2003, pp. 64]
'More and More' Responses Received - Following the call for information, numerous reports of suspicious activity are received from the air traffic control facilities. [Spencer, 2008, pp. 125-126] Linda Schuessler, the deputy director of system operations at the Command Center, will later recall, “[W]e started getting more and more calls about bomb threats, about aircraft that we had lost communication or radar identification with.” [Aviation Week and Space Technology, 12/17/2001]
Center Lists Suspect Aircraft - Sliney wants a list compiled of the reportedly suspicious aircraft. A dry-erase board is set up in the middle of the room. On it a manager keeps track of the reports that are coming in, writing down where each suspect aircraft was last seen, who was working it, where the flight originated, and where it is going. Another person contacts the field facilities to follow up on the reports. [9/11 Commission, 7/22/2003 pdf file; Spencer, 2008, pp. 126]
Two Dozen Suspicious Flights - Author Pamela Freni will later describe, “[F]or the next several hours the call signs and status” of every suspicious aircraft will be recorded. Command Center personnel call “airline operations centers, trying to determine any crises on each flight. Only when each plane landed or was found safe did its identification information disappear from the board. Upward to two dozen were listed at one time, but ultimately the number was whittled to 11 highly suspicious cases” (see (9:09 a.m. and After) September 11, 2001). “Nine of those airplanes would land safely. Two of them—AA 77 and UA 93—would not.” [Freni, 2003, pp. 64-65]

Entity Tags: Linda Schuessler, Ben Sliney, Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Daniel Bueno.Daniel Bueno. [Source: Discovery Channel]At “approximately 9:15 a.m.,” according to the 9/11 Commission, Daniel Bueno, a supervisor at the FAA’s Boston Center, asks the FAA’s Herndon Command Center to contact all the FAA centers nationwide and instruct them to issue an alert, informing all airborne aircraft of the events unfolding in New York and advising them to heighten their cockpit security. Boston Center air traffic controllers have recently issued a similar alert to all aircraft in their airspace (see 9:09 a.m.-9:10 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 25-26] However, the 9/11 Commission will conclude, “We have found no evidence to suggest that the Command Center acted on this request or issued any type of cockpit security alert.” [9/11 Commission, 7/24/2004, pp. 23] According to author Lynn Spencer, “The request never makes it to Ben Sliney,” the national operations manager at the Command Center. “Tragically, it is lost in the confusion and never gets past the staff person monitoring Sliney’s desk as events rapidly spiral out of control.” [Spencer, 2008, pp. 99] But Ellen King, a Command Center manager, offers a different explanation. She will tell the 9/11 Commission that the FAA culture and mindset on 9/11 are such that the FAA “would never have relayed this message directly to all pilots.… [T]he FAA would pass situational awareness to the airline company representatives who, in turn, would determine if such action was necessary.” [9/11 Commission, 8/26/2004, pp. 26 and 92]

Entity Tags: Daniel Bueno, Ellen King, Ben Sliney, Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The FAA’s New England regional office calls the FAA’s Herndon Command Center, and asks it to tell Cleveland Center to contact Delta Air Lines Flight 1989 and advise it to use extra cockpit security. The reason the New England regional office makes this request is unclear. [9/11 Commission, 7/24/2004, pp. 10] As the 9/11 Commission will describe, apparently in response to the request, “[A]t 9:19 the FAA… Command Center in Herndon ordered controllers to send a cockpit warning to Delta 1989 because, like American 11 and United 175, it was a transcontinental flight departing Boston’s Logan Airport.” [9/11 Commission, 7/24/2004, pp. 455] Minutes earlier, the FAA’s Boston Center asked the Command Center to contact the nation’s FAA centers and instruct them to tell all airborne aircraft to increase their cockpit security (see (9:15 a.m.) September 11, 2001). The Command Center’s instruction to air traffic controllers about Delta 1989 is apparently an exception, as the 9/11 Commission will say it found “no evidence to suggest that the Command Center acted on this request.” [9/11 Commission, 7/24/2004, pp. 23; 9/11 Commission, 8/26/2004, pp. 25-26] Delta 1989 will subsequently be 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). [USA Today, 8/13/2002; Vanity Fair, 8/1/2006]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to the 9/11 Commission, NEADS is contacted by the FAA’s Boston Center. Colin Scoggins, Boston Center’s military liaison, tells it: “I just had a report that American 11 is still in the air, and it’s on its way towards—heading towards Washington.… That was another—it was evidently another aircraft that hit the tower. That’s the latest report we have.… I’m going to try to confirm an ID for you, but I would assume he’s somewhere over, uh, either New Jersey or somewhere further south.” The NEADS official asks: “He—American 11 is a hijack?… And he’s heading into Washington?” Scoggins answers yes both times and adds, “This could be a third aircraft.” Somehow Boston Center has been told by FAA headquarters that Flight 11 is still airborne, but the 9/11 Commission will say it hasn’t been able to find where this mistaken information came from.
Scoggins Makes Error - Vanity Fair magazine will later add, “In Boston, it is Colin Scoggins who has made the mistaken call.” Scoggins will explain why he believes he made this error: “With American Airlines, we could never confirm if [Flight 11] was down or not, so that left doubt in our minds.” He says he was monitoring a conference call between FAA centers (see 8:28 a.m. September 11, 2001), “when the word came across—from whom or where isn’t clear—that American 11 was thought to be headed for Washington.” However, Boston Center was never tracking Flight 11 on radar after losing sight of it near Manhattan: “The plane’s course, had it continued south past New York in the direction it was flying before it dipped below radar coverage, would have had it headed on a straight course toward DC. This was all controllers were going on.” Scoggins says, “After talking to a supervisor, I made the call and said [American 11] is still in the air.” [Northeast Air Defense Sector, 9/11/2001; 9/11 Commission, 6/17/2004; Vanity Fair, 8/1/2006]
Myers Refers to Mistaken Report - In the hours following the attacks, acting Chairman of the Joint Chiefs of Staff Richard Myers will apparently refer to this erroneous report that Flight 11 is still airborne and heading toward Washington, telling the Associated Press that “prior to the crash into the Pentagon, military officials had been notified that another hijacked plane had been heading from the New York area to Washington.” Myers will say “he assumed that hijacked plane was the one that hit the Pentagon, though he couldn’t be sure.” [Associated Press, 9/11/2001]

Entity Tags: Richard B. Myers, Northeast Air Defense Sector, Federal Aviation Administration, Boston Air Route Traffic Control Center, Colin Scoggins

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The FAA’s Boston Center contacts NORAD’s Northeast Air Defense Sector (NEADS) and reports that another aircraft, Delta Air Lines Flight 1989, is missing. [9/11 Commission, 5/23/2003; 9/11 Commission, 6/17/2003; 9/11 Commission, 2004] Why the Boston Center does this is unclear, since Delta 1989 is currently being handled by the FAA’s Cleveland Center, not the Boston Center. [USA Today, 8/13/2002; 9/11 Commission, 7/24/2004, pp. 10] And, according to the 9/11 Commission, Delta 1989 “never turned off its transponder,” so it should still be clearly visible on radar. [9/11 Commission, 7/24/2004, pp. 16, 28] Twelve minutes later, at 9:39, Boston Center will call NEADS and incorrectly tell it that Delta 1989 is a possible hijack (see 9:39 a.m. September 11, 2001). [9/11 Commission, 2004; Vanity Fair, 8/1/2006]

Entity Tags: Boston Air Route Traffic Control Center, Northeast Air Defense Sector

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The National Miilitary Command Center, inside the Pentagon.The National Miilitary Command Center, inside the Pentagon. [Source: US Department of Defense]The National Military Command Center (NMCC) at the Pentagon finally commences and runs a “significant event conference” in response to the ongoing crisis, 26 minutes after the second plane hit the World Trade Center and officers in the NMCC realized the US was under terrorist attack. [9/11 Commission, 6/17/2004 pdf file; 9/11 Commission, 7/24/2004, pp. 37; American Forces Press Service, 9/7/2006]
NMCC Directors Decided to Establish Conference - After those in the NMCC saw Flight 175 hitting the WTC live on television at 9:03 a.m. (see 9:03 a.m. September 11, 2001), Captain Charles Leidig, the acting deputy director for operations (DDO) in the center throughout the attacks, and Commander Pat Gardner, the assistant DDO, talked about the need to convene a significant event conference so there could be a discussion of what actions were to be taken in response. The DDO and the assistant DDO are the two officers responsible for deciding what type of conference the NMCC should convene, and when it should do so. Because there is no specific procedure for dealing with terrorist attacks, Leidig and Gardner decided a significant event conference would most suit their needs, because it would have the flexibility of allowing more people to be added in as required. They also discussed who would need to be on this conference. [9/11 Commission, 4/29/2004 pdf file] But Major Charles Chambers, who is currently on duty in the NMCC, will give a slightly different account. According to Chambers, Staff Sergeant Val Harrison had a phone in her hand and said NORAD was asking for a significant event conference. Leidig had agreed, and so Harrison started establishing the conference.
Conference Begins with Recap of Situation - According to Chambers, “The computer does a mass dialing to connect to those command centers that are always included” in an NMCC conference call, but Harrison also had to manually call the civilian agencies that were going to be included in the conference, such as the FAA, the FBI, and the Federal Emergency Management Agency (FEMA). [US Department of Defense, 9/2001] The conference then begins at 9:29 a.m. with a brief recap: Two aircraft have hit the WTC, there is a confirmed hijacking of Flight 11, and fighter jets have been scrambled from Otis Air National Guard Base in Massachusetts (see 8:46 a.m. September 11, 2001). The FAA is asked to provide an update, but its line is silent as the agency has not yet been added to the call (see (9:29 a.m.-12:00 p.m.) September 11, 2001). A minute later, Leidig states that it has just been confirmed that Flight 11 is still airborne and is heading toward Washington, DC. (This incorrect information apparently arose minutes earlier during a conference call between FAA centers (see 9:21 a.m. September 11, 2001).) [9/11 Commission, 7/24/2004, pp. 37] NMCC conference calls are moderated by the DDO. [9/11 Commission, 7/21/2003 pdf file] Leidig will tell the 9/11 Commission that they are conducted over “a special phone circuit, and it’s classified to be able to pass information, relay information between very senior leadership all the way over to the White House.” [9/11 Commission, 6/17/2004]
NMCC Struggled to Convene Conference - Some officers currently on duty in the NMCC will later complain about circumstances that delayed the establishing of the significant event conference. Chambers will recall that the conference took “much longer than expected to bring up.” [US Department of Defense, 9/2001] Gardner will tell the 9/11 Commission that the NMCC had been “struggling to build the conference,” which “didn’t get off as quickly as hoped.” [9/11 Commission, 5/5/2004] He will describe his “frustration that it wasn’t brought up more quickly.” [9/11 Commission, 5/12/2004]
Other Conference and Connection Problems Delayed Call - Preparations for the conference were disrupted as a result of the CIA convening a National Operations and Intelligence Watch Officer Network (NOIWON) conference call between government agencies in the Washington area, reportedly at sometime between 9:16 a.m. and 9:25 a.m. (see (Between 9:16 a.m. and 9:25 a.m.) September 11, 2001). According to a 9/11 Commission memorandum, the NMCC had “abandoned its attempt to convene a [significant event conference] so its watch officers could participate in the NOIWON conference.” [Federal Aviation Administration, 9/11/2001; Federal Aviation Administration, 9/11/2001; 9/11 Commission, 7/21/2003 pdf file] Another factor that slowed attempts to convene the significant event conference was a problem with connecting some agencies to it. According to Chambers, “A couple of the civil agencies couldn’t be reached and others kept dropping off moments after connecting.” He will recall, “We finally decided to proceed without those agencies that were having phone problems.” [US Department of Defense, 9/2001] Leidig had announced that the NMCC would have to start without those agencies and add them to the conference later on. [9/11 Commission, 5/12/2004]
Call Ends after Five Minutes - The significant event conference ends after only a few minutes, following a recommendation by NORAD that it be reconvened as an “air threat conference.” It is brought to an end at around 9:34 a.m., and will resume as an air threat conference at 9:37 a.m. (see 9:37 a.m.-9:39 a.m. September 11, 2001). [9/11 Commission, 4/29/2004 pdf file; 9/11 Commission, 7/24/2004, pp. 37]

Entity Tags: Charles Leidig, Federal Aviation Administration, Val Harrison, Patrick Gardner, Charles Chambers, North American Aerospace Defense Command, National Military Command Center

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

John Werth, the air traffic controller at the FAA’s Cleveland Center who is monitoring the now-hijacked Flight 93, has to move Delta Air Lines Flight 1989 and several other aircraft, in order to get them out of Flight 93’s path and avoid a midair collision. [9/11 Commission, 8/26/2004, pp. 39; USA Today, 9/11/2008]
Controller Begins Moving Aircraft - At 9:30 a.m., Werth begins moving other aircraft away from Flight 93 due to the hijacked flight’s failure to acknowledge his radio transmissions. [Federal Aviation Administration, 9/17/2001 pdf file] Furthermore, as USA Today will describe, Flight 93 “became erratic. It sped up and started gaining on another United [Airlines] flight. Werth commanded the second jet to turn right. Seconds later, Flight 93 turned to the right, too.” [USA Today, 9/11/2008]
Controller Worried about Possible Collision - Then, between 9:34 a.m. and 9:38 a.m., Flight 93 climbs from 35,000 feet up to 41,000 feet (see (9:35 a.m.) September 11, 2001), and during this period it reverses course and heads back east (see (9:36 a.m.) September 11, 2001). [National Transportation Safety Board, 2/19/2002 pdf file; 9/11 Commission, 8/26/2004, pp. 39, 41] Werth becomes concerned about the possibility of a midair collision. [9/11 Commission, 10/1/2003 pdf file]
Delta 1989 Turns Several Times - As Flight 93 climbs, Werth instructs Delta 1989, which is also in the airspace he is monitoring, to turn right, so as to get away from the hijacked jet. As Flight 93 continues its turn back toward the east, Werth has to move Delta 1989 out of its path. In all, he has to turn the Delta flight several times. [USA Today, 9/11/2008] Minutes earlier, Cleveland Center concluded incorrectly that Delta 1989, not Flight 93, was the aircraft being hijacked (see (9:28 a.m.-9:33 a.m.) September 11, 2001). [USA Today, 8/13/2002] The Delta pilots’ normal responses to his instructions reassure Werth that it is a “safe bet that the Delta flight hadn’t been hijacked.” [USA Today, 9/11/2008]
Other Aircraft Moved out of Path - According to the 9/11 Commission, while Flight 93 is ascending to 41,000 feet, Werth has to move “several aircraft out of its way,” acting “decisively to clear the other flights in his sector from Flight 93’s path.” [9/11 Commission, 8/26/2004, pp. 39]

Entity Tags: John Werth

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

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

Personnel at NORAD’s Northeast Air Defense Sector (NEADS) are following Flight 93 while it is still flying west and before it reverses course, according to the accounts of some NEADS and NORAD officials, but their claims will be disputed by the 9/11 Commission. [Filson, 2003, pp. 68, 71; 9/11 Commission, 10/30/2003 pdf file; 9/11 Commission, 8/26/2004, pp. 100-101]
NEADS Watches Flight 93 Heading West - Colonel Robert Marr, the battle commander at NEADS, will later recall that around this time, “his focus” is on Flight 93, which, he will say, is “circling over Chicago.” [9/11 Commission, 10/27/2003 pdf file] Marr will tell author Leslie Filson that the flight is being monitored by NEADS personnel while it is still flying west. He will describe: “We don’t have fighters that way and we think [Flight 93 is] headed toward Detroit or Chicago. I’m thinking Chicago is the target.” Marr will say NEADS contacts an Air National Guard base in the area, “so they [can] head off 93 at the pass” (see (9:55 a.m.) September 11, 2001). [Filson, 2003, pp. 68]
NORAD Watching Flight 93 When It Changes Course - Lieutenant Colonel Mark Stuart, an intelligence officer who is in the NEADS battle cab with Marr, will give a similar account. He will say that when the Flight 93 “incident began to unfold,” it was his “professional judgment that the plane was going to strike the Sears Tower in Chicago, and he passed that judgment to Colonel Marr.” [9/11 Commission, 10/30/2003 pdf file] And Major General Larry Arnold, the commander of the Continental United States NORAD Region, will say that NORAD personnel are already following Flight 93 at 9:36 a.m., when it reverses course and heads back east (see (9:36 a.m.) September 11, 2001). He will tell Filson, “[W]e watched the 93 track as it meandered around the Ohio-Pennsylvania area and started to turn south toward [Washington,] DC.” [National Transportation Safety Board, 2/19/2002 pdf file; Filson, 2003, pp. 71; 9/11 Commission, 8/26/2004, pp. 41] Marr will similarly say “that he distinctly remembers watching [Flight 93] come west and turn over Cleveland.” [9/11 Commission, 1/23/2004 pdf file]
9/11 Commission Says No One at NORAD Watches Flight 93 - However, the 9/11 Commission will dispute these accounts. It will state: “The record demonstrates… that no one at any level in NORAD… ever ‘watched the 93 track’ start to turn south towards Washington, DC. In fact, the military never saw Flight 93 at all.” [9/11 Commission, 8/26/2004, pp. 101] NEADS will first be alerted to Flight 93 significantly later, at 10:07 a.m., according to the 9/11 Commission (see 10:05 a.m.-10:08 a.m. September 11, 2001).
Officer May Have Confused Flight 93 with Delta 1989 - The 9/11 Commission will suggest to Marr that he was mistaking Flight 93 for Delta Air Lines Flight 1989, an aircraft that is incorrectly reported as having been hijacked around this time (see (9:28 a.m.-9:33 a.m.) September 11, 2001 and 9:39 a.m. September 11, 2001). Marr will respond that he may have confused Flight 93 with Delta 1989, but say that “he believes the last point at which he saw Flight 93 was when it was over Ohio, before it turned off its transponder,” which happens at 9:41 a.m. (see (9:40 a.m.) September 11, 2001). [9/11 Commission, 1/23/2004 pdf file; 9/11 Commission, 7/24/2004, pp. 27-30] Senior officials, including Marr and Arnold, will claim that the US military continues following Flight 93 after it reverses course and is heading toward Washington (see (9:36 a.m.-10:06 a.m.) September 11, 2001). [Filson, 2003, pp. 71, 73] Stuart will say that after Flight 93 changes course, he “and other NEADS people knew it was headed to DC.” [9/11 Commission, 10/30/2003 pdf file]

Entity Tags: North American Aerospace Defense Command, Northeast Air Defense Sector, Larry Arnold, Mark E. Stuart, Robert Marr

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to a book about the FAA’s response to the 9/11 attacks, Cleveland Center air traffic controllers follow Flight 93 as it turns south and reverses course (see (9:36 a.m.) September 11, 2001). But, “bomb threats called in concerning four other planes focused their attention onto what they believed to be more critical maneuvers.” [Freni, 2003, pp. 40] One of these four planes is presumably Delta Flight 1989, which is mistakenly thought to be hijacked and to have a bomb aboard (see (9:28 a.m.-9:33 a.m.) September 11, 2001). [WKYC, 9/11/2006] The identities of the other three planes are unknown. By this time, Cleveland Center has already overheard a radio transmission from Flight 93 stating, “We have a bomb on board” (see (9:32 a.m.) September 11, 2001), and has acknowledged this, reporting, “United 93 may have a bomb on board,” so it seems unlikely that other threatened aircraft would be regarded as “more critical maneuvers.” [9/11 Commission, 6/17/2004]

Entity Tags: 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 Delta Air Lines operations control center in Atlanta, Georgia.The Delta Air Lines operations control center in Atlanta, Georgia. [Source: Public domain]Delta Air Lines instructs one of its aircraft, Flight 1989, to land at Cleveland Hopkins Airport, but the FAA’s Cleveland Center, which is handling the aircraft, is not notified of this. [USA Today, 8/13/2002; Associated Press, 8/15/2002]
Pilots Instructed to Land - The pilots of Delta 1989 receive an ACARS text message from their airline’s dispatch office in Atlanta, Georgia, instructing them to “Land immediately in Cleveland.” [Spencer, 2008, pp. 167] According to USA Today, “Since early reports that a bomb, then hijackers, might be aboard” Delta 1989, Delta Air Lines’ headquarters in Atlanta has been tracking the flight, and receiving reports on it every five minutes. [USA Today, 8/13/2002] The plane’s pilot, Captain Paul Werner, quickly types a response to the message, “ok.” But, a couple of minutes later, he receives another ACARS message from the airline. It says: “Confirm landing in Cleveland. Use correct phraseology.” Werner and First Officer David Dunlap are puzzled. According to author Lynn Spencer: “There’s such a thing as correct phraseology on the radio, but there is no such thing when typing back and forth with dispatch on ACARS. Those messages are usually casual.” Werner carefully types a response: “Roger. Affirmative. Delta 1989 is diverting to Cleveland.” He calls the Cleveland Center at 9:44 a.m. and requests a diversion to Cleveland Airport. [Spencer, 2008, pp. 167-168; USA Today, 9/11/2008]
Cleveland Center Not Informed - About 15 minutes earlier, Cleveland Center heard the sounds from Flight 93 as it was being hijacked, but initially thought these came from Delta 1989, and mistakenly believed the Delta flight was being taken over (see (9:28 a.m.-9:33 a.m.) September 11, 2001). [USA Today, 8/13/2002] But the Delta pilots’ normal responses to radio transmissions soon led air traffic controller John Werth, who is handling Delta 1989, to conclude that this aircraft was fine. [USA Today, 9/11/2008] However, controllers at the Cleveland Center are unaware that Delta Air Lines has instructed Flight 1989 to land, and so Werner’s request for a change of course will make them suspicious of it again (see (Shortly After 9:44 a.m.) September 11, 2001). [USA Today, 8/13/2002]

Entity Tags: David Dunlap, Delta Airlines, Cleveland Air Route Traffic Control Center, Paul Werner

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Having earlier concluded that it was not hijacked, air traffic controllers at the FAA’s Cleveland Center again become suspicious of Delta Air Lines Flight 1989, after its pilot requests a change of course and then fails to respond to a message.
Pilot Requests Diversion - Cleveland Center controllers initially thought the sounds from Flight 93 as it was being hijacked had come from Delta 1989, but soon decided they had come from Flight 93 (see (9:28 a.m.-9:33 a.m.) September 11, 2001). [USA Today, 8/13/2002] However, without notifying the Cleveland Center, Delta Air Lines has just instructed Delta 1989 to land at Cleveland Hopkins Airport (see (9:42 a.m.) September 11, 2001). After the plane’s pilot, Captain Paul Werner, calls the Cleveland Center at 9:44 a.m., requesting an immediate diversion, controllers there become suspicious. [Spencer, 2008, pp. 167-168; USA Today, 9/11/2008]
Supervisor Reports Concerns over Teleconference - USA Today will later describe: “The Delta flight wants to land in Cleveland? And the captain’s request comes before he can know that the FAA wants every flight down. On this day, the fact that the pilot requests to be rerouted before he is ordered to land seems suspicious. Why the urgency? Controllers don’t know that Delta officials, also concerned about the flight, have ordered Werner to land in Cleveland.” After Delta 1989 makes an abrupt 30-degree turn back toward Cleveland Airport, a supervisor at the Cleveland Center announces the apparently suspicious development on an FAA teleconference.
Coded Message Confirms No Hijacking - As Delta 1989 begins its descent toward Cleveland, a Cleveland Center controller radios Werner with a coded message to check whether his plane has been hijacked. The controller says, “Delta 1989, I hear you’re ‘late’ today.” (The controller is using the code word for a hijack, which has been replaced with the word ‘late’ in subsequent accounts of this incident, for security reasons. Pilots can use this code word to alert controllers to their situation if they are unable to do so openly because hijackers are in the cockpit.) Werner reassures the controller that all is okay, saying: “Negative. Delta 1989 is not a ‘late.’”
Lack of Response Causes More Suspicion - Then, as the plane descends, it receives another message from the Cleveland Center. But Werner, who is busy, fails to respond to it. This arouses further suspicion. According to USA Today: “On the ground, controllers in Cleveland Center grow alarmed. Why didn’t he respond? Have both jets—the United [Flight 93] and the Delta flights—been hijacked?” [USA Today, 8/13/2002; Spencer, 2008, pp. 168-169]

Entity Tags: Paul Werner, Cleveland Air Route Traffic Control Center

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Leo Mullin.Leo Mullin. [Source: Publicity photo]Leo Mullin, the CEO of Delta Air Lines, calls FAA Administrator Jane Garvey at FAA headquarters in Washington, DC, and reports that four Delta aircraft are missing. Mullin, who is at his company’s headquarters in Atlanta, Georgia, tells Garvey: “We can’t find four of our planes. Four of our transponders are off.” [USA Today, 8/13/2002; Spencer, 2008, pp. 186] The identities of these aircraft are unstated. Whether they include Delta Flight 1989, which FAA air traffic controllers have mistakenly reported as being a possible hijacking (see (9:28 a.m.-9:33 a.m.) September 11, 2001 and 9:39 a.m. September 11, 2001), is unclear. At 9:27 a.m., the FAA’s Boston Center reported that this plane was missing (see 9:27 a.m. September 11, 2001). [North American Aerospace Defense Command, 9/11/2001; 9/11 Commission, 5/23/2003] But, according to the 9/11 Commission, Delta 1989 “never turned off its transponder.” [9/11 Commission, 7/24/2004, pp. 28] USA Today will report that, after “early reports that a bomb, then hijackers, might be aboard, Delta CEO Leo Mullin, 58, had nervously tracked [Delta 1989] from the company’s headquarters in Atlanta. Every five minutes, a new report came in. None seemed clear.” [USA Today, 8/13/2002]

Entity Tags: Leo Mullin, Jane Garvey, Delta Airlines

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Air Force One departs Sarasota.Air Force One departs Sarasota. [Source: Associated Press]Air Force One takes off from off from Sarasota-Bradenton International Airport in Florida with President Bush on board. [USA Today, 9/11/2001; Washington Post, 1/27/2002; 9/11 Commission, 7/24/2004, pp. 39] The plane takes off without any fighter jets protecting it. “The object seemed to be simply to get the president airborne and out of the way,” an administration official will later say. [Daily Telegraph, 12/16/2001] There are still 3,520 planes in the air over the US. [USA Today, 8/13/2002] About half of the planes in the Florida region where Bush’s plane is are still airborne. [St. Petersburg Times, 9/7/2002] Apparently, fighters don’t meet up with Air Force One until over an hour and a half later (see (11:29 a.m.) September 11, 2001). Counterterrorism “tsar” Richard Clarke will claim to have heard at around 9:50 a.m. from the White House bunker containing Vice President Dick Cheney that a fighter escort had been authorized. [Clarke, 2004, pp. 8-9]

Entity Tags: George W. Bush

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

F-16 Fighting Falcons from the 127th Wing at Selfridge Air National Guard Base.F-16 Fighting Falcons from the 127th Wing at Selfridge Air National Guard Base. [Source: John S. Swanson / US Air Force]NORAD’s Northeast Air Defense Sector (NEADS) contacts Selfridge Air National Guard Base in Michigan to arrange for two of its F-16 fighter jets that are out on a training mission to intercept a suspicious aircraft. Accounts will conflict over whether this aircraft is Flight 93 or Delta Air Lines Flight 1989, which is wrongly thought to have been hijacked. [Associated Press, 8/30/2002; ABC News, 9/11/2002; Vanity Fair, 8/1/2006; Spencer, 2008, pp. 178] Delta 1989 was flying about 25 miles behind Flight 93 when air traffic controllers mistakenly suspected it might be hijacked (see (9:28 a.m.-9:33 a.m.) September 11, 2001), and since then it has been instructed to land at Cleveland Hopkins Airport in Ohio (see (9:42 a.m.) September 11, 2001). [USA Today, 8/13/2002; USA Today, 9/11/2008] Flight 93 is currently flying east across Pennsylvania. [National Transportation Safety Board, 2/19/2002 pdf file] NEADS has already tried getting fighter jets from a unit in Duluth, Minnesota, sent after Delta 1989, but the unit was unable to respond (see (Shortly After 9:41 a.m.) September 11, 2001). [9/11 Commission, 1/22/2004 pdf file; 9/11 Commission, 1/23/2004 pdf file]
NEADS Calls Selfridge Base - A NEADS weapons technician now calls the 127th Wing at Selfridge Air National Guard Base. He knows the unit has two F-16s in the air on a training mission. Although these jets are unarmed and only have a limited amount of fuel remaining, the commander at the Selfridge base agrees to turn them over to NEADS. [Spencer, 2008, pp. 178] The commander says: “[H]ere’s what we can do. At a minimum, we can keep our guys airborne. I mean, they don’t have—they don’t have any guns or missiles or anything on board.” The NEADS technician replies, “It’s a presence, though.” [Vanity Fair, 8/1/2006]
Fighters May Have to Crash into Hijacked Plane - Military commanders realize that, without weapons, the Selfridge fighter pilots might have to slam their jets into a hijacked plane to stop it in its tracks. Colonel Robert Marr, the NEADS battle commander, will later reflect, “As a military man, there are times that you have to make sacrifices that you have to make.” [ABC News, 8/30/2002; ABC News, 9/11/2002] However, the Selfridge jets never have to intercept either of the two suspect aircraft, and instead are able to head back to base. [Filson, 2003, pp. 70; Wolverine Guard, 9/2006 pdf file]
Selfridge Called due to Concerns about Delta 1989? - According to author Lynn Spencer, the NEADS weapons technician’s call to the Selfridge unit is made in response to a report NEADS received about the possible hijacking of Delta 1989 (see 9:39 a.m. September 11, 2001). [Spencer, 2008, pp. 178] Vanity Fair magazine and the 9/11 Commission will also say NEADS calls the Selfridge unit in response to this report about Delta 1989. [9/11 Commission, 7/24/2004, pp. 28; Vanity Fair, 8/1/2006]
NORAD Commander Gives Different Account - However, Larry Arnold, the commander of the Continental United States NORAD Region, will suggest the Selfridge unit is called due to concerns about both Delta 1989 and Flight 93. He will say: “We were concerned about Flight 93 and this Delta aircraft [Flight 1989] and were trying to find aircraft in the vicinity to help out. We didn’t know where it was going to go. We were concerned about Detroit… and the fighters up there were out of gas with no armament.” [Filson, 2003, pp. 71]
NEADS Commander Claims Fighters Sent toward Flight 93 - Robert Marr will give another different account. He will claim that NEADS contacts the Selfridge base solely because of its concerns over Flight 93. He tells author Leslie Filson that before Flight 93 reversed course and headed back east (see (9:36 a.m.) September 11, 2001), NEADS thought it was “headed toward Detroit or Chicago. I’m thinking Chicago is the target and know that Selfridge Air National Guard Base has F-16s in the air.” NEADS contacts “them so they could head off 93 at the pass.” [Filson, 2003, pp. 68] Marr will tell the 9/11 Commission that the Selfridge F-16s are going to be “too far from Cleveland to do any good,” and so he believes NEADS directs them to intercept Flight 93. [9/11 Commission, 1/23/2004 pdf file] (Presumably, he means the jets cannot be responding to Delta 1989, which has been told to land in Cleveland [USA Today, 9/11/2008] )
9/11 Commission Disputes Arnold's and Marr's Accounts - The 9/11 Commission will reject Arnold’s and Marr’s accounts. It will state, “The record demonstrates, however, that… the military never saw Flight 93 at all” before it crashes, and conclude, “The Selfridge base was contacted by NEADS not regarding Flight 93, but in response to another commercial aircraft in the area that was reported hijacked (Delta Flight 1989, which ultimately was resolved as not hijacked).” [9/11 Commission, 8/26/2004, pp. 101] Lt. Col. Doug Champagne, the pilot of one of the Selfridge F-16s, will recall that “he and his colleague never received orders to intercept [Flight 93] in any way.” [Mount Clemens-Clinton-Harrison Journal, 9/6/2006] Reports based on interviews with the two Selfridge pilots will make no mention of the jets being directed to intercept Delta 1989 either (see (9:56 a.m.-10:29 a.m.) September 11, 2001). [Filson, 2003, pp. 68-70; Wolverine Guard, 9/2006 pdf file; Mount Clemens-Clinton-Harrison Journal, 9/6/2006]

Entity Tags: Larry Arnold, 127th Wing, Doug Champagne, Northeast Air Defense Sector, Robert Marr, Selfridge Air National Guard Base

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Douglas Champagne.Douglas Champagne. [Source: David Kujawa / US Air Force]Although NORAD’s Northeast Air Defense Sector (NEADS) has contacted Selfridge Air National Guard Base in Michigan, reportedly to arrange that two of its F-16s be diverted from a training mission to intercept either Flight 93 or Delta Air Lines Flight 1989 (accounts conflict over which aircraft is concerned), the pilots of those jets apparently never receive an order to intercept a plane, and so return directly to their base. [Filson, 2003, pp. 68, 71; Wolverine Guard, 9/2006 pdf file; Mount Clemens-Clinton-Harrison Journal, 9/6/2006; Spencer, 2008, pp. 178] However, some accounts will claim the pilots are indeed ordered to intercept the suspect aircraft. [ABC News, 8/30/2002; Associated Press, 8/30/2002; Post-Standard (Syracuse), 3/27/2005; Spencer, 2008, pp. 188]
Jets Returning from Training Mission - The F-16s, piloted by Lieutenant Colonel Tom Froling and Major Douglas Champagne of the 127th Wing, had taken off from Selfridge Air National Guard Base at around 8:50 a.m. for a routine training mission at Grayling Range in central northern Michigan. The two pilots were oblivious to the attacks taking place in New York and Washington. [Filson, 2003, pp. 68; GlobalSecurity (.org), 4/26/2005; Wolverine Guard, 9/2006 pdf file] When they started heading back to Selfridge after completing their training mission, they began hearing “unusual radio traffic” as air traffic controllers began diverting flights from their original destinations. [Mount Clemens-Clinton-Harrison Journal, 9/6/2006]
Pilots Learn of Plane Hitting Pentagon - Froling will later recall: “Something strange was occurring and I couldn’t put my finger on what was happening. I could hear [the FAA’s] Cleveland Center talking to the airlines and I started putting things together and knew something was up.” [Filson, 2003, pp. 68-70] Champagne hears an air traffic controller stating that a plane has crashed at the Pentagon. He then hears the Cleveland Center announcing a “demon watch,” which means pilots have to contact their operations center for more information.
Commander Asks if Pilots Have Used up Their Ammunition - When Champagne calls the Selfridge base, his operations group commander, General Michael Peplinski, wants to know if he and Froling have used up their ammunition during the training mission. Champagne will recall: “[Peplinski] asked if we had expended all our munitions and specifically asked if we had strafed. We replied that all ordnance was gone. I assumed we had strafed without clearance and had injured someone down range. We had no idea what was happening on the Eastern seaboard.” [Wolverine Guard, 9/2006 pdf file; Mount Clemens-Clinton-Harrison Journal, 9/6/2006]
Pilots Directed to Return to Base - According to author Lynn Spencer, because a commander with the 127th Wing agreed to turn the two F-16s over to NEADS (see (9:55 a.m.) September 11, 2001), Champagne and Froling are instructed to call NEADS. When they do so, they are ordered to intercept Delta 1989. [Spencer, 2008, pp. 178, 180, 188] But according to other accounts, they are “ordered south in case United Airlines 93 was targeting Chicago.” [ABC News, 9/11/2002; Post-Standard (Syracuse), 3/27/2005] However, according to two reports based on interviews with Champagne, Peplinski only instructs the two pilots to return to their base and land on its auxiliary runway.
Pilots Apparently Not Ordered to Intercept Aircraft - Accounts based on interviews with the pilots will make no mention of the jets being directed to intercept Delta 1989 or Flight 93. According to Champagne, the air traffic controller’s announcement that an aircraft hit the Pentagon “was the only indication we received that other aircraft and buildings were involved.” Champagne will say that “he and his colleague never received orders to intercept [Flight 93] in any way.” The two pilots “had no ammunition… and only an hour’s worth of fuel remaining. And as they approached Selfridge amid the puzzling radio transmissions, they still were oblivious to what was transpiring.” [Filson, 2003, pp. 68-70; Wolverine Guard, 9/2006 pdf file; Mount Clemens-Clinton-Harrison Journal, 9/6/2006]
Jets Land at Base - The two F-16s land back at Selfridge Air National Guard Base at 10:29 a.m. [9/11 Commission, 10/27/2003 pdf file] As Champagne pulls in his aircraft, his friend Captain Sean Campbell approaches and mouths the words to him: “It’s bad. It’s really, really bad.” [Wolverine Guard, 9/2006 pdf file; Mount Clemens-Clinton-Harrison Journal, 9/6/2006]

Entity Tags: Doug Champagne, Cleveland Air Route Traffic Control Center, Tom Froling, 127th Wing, Sean Campbell, Michael Peplinski, Selfridge Air National Guard Base, Northeast Air Defense Sector

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

NORAD’s Northeast Air Defense Sector (NEADS) receives a call from a NORAD unit in Canada, reporting another suspected hijacked aircraft that is heading south from Canada, across the border toward Washington, DC. [Vanity Fair, 8/1/2006]
Aircraft Reported on Chat System - A member of staff at NEADS relays to their colleagues that the aircraft is from an “unknown departure airport, heading towards Washington,” but they do not “know any codes or anything” else about it. [North American Aerospace Defense Command, 9/11/2001] Another member of staff at NEADS calls the Canadian unit for more information. A Lance Corporal Nicholson there says only that he has seen “something on the chat” about a “possible” aircraft. [North American Aerospace Defense Command, 9/11/2001; North American Aerospace Defense Command, 9/11/2001] (Nicholson is presumably referring to NORAD’s computer chat system. [Spencer, 2008, pp. 139] )
Fighter Unit Contacted - According to author Lynn Spencer, NEADS battle commander Colonel Robert Marr contacts a military unit in Syracuse, New York, to get fighter jets sent after the suspicious flight. [Spencer, 2008, pp. 223] However, the first jets to launch from Syracuse will not take off until 10:42 a.m. (see 10:42 a.m. September 11, 2001). [Post-Standard (Syracuse), 9/12/2001]
Report Is a False Alarm - The suspected hijacking is soon revealed to be a false alarm. Nicholson will call from Canada and tell NEADS: “Be advised… that our [intelligence team] is not assessing that there is an actual aircraft problem. It’s just that there could be problems from our area.… There’s no actual aircraft that we suspect as being a danger.” He will add that his intelligence people “haven’t got any particular aircraft in mind.” [North American Aerospace Defense Command, 9/11/2001; Vanity Fair, 8/1/2006]
Numerous Erroneous Reports - This is one of the numerous mistaken reports of hijackings received during the course of the morning (see (9:09 a.m. and After) September 11, 2001). According to Vanity Fair: “In the barrage of information and misinformation, it becomes increasingly difficult for the controllers [at NEADS] to keep count of how many suspected hijackings are pending. So far, it is known that three have hit buildings, but given the uncertainty about the fates of American 11 and American 77—no one knows yet that this is the plane that hit the Pentagon—the sense at NEADS is that there are possibly three hijacked jets still out there, and who knows how many more yet to be reported.” At the time NEADS is informed of the suspicious aircraft coming in from Canada, “no one on the military side is aware that United 93 has been hijacked.” [Vanity Fair, 8/1/2006]

Entity Tags: Robert Marr, Northeast Air Defense Sector, North American Aerospace Defense Command

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Air traffic controllers at the Cleveland Terminal Radar Approach Control (TRACON) remain suspicious of Delta Air Lines Flight 1989 as it is coming in to land at Cleveland Hopkins Airport, due to the pilot’s failure to use an important standard term in his communications with them. [Federal Aviation Administration, 9/16/2001] A TRACON is an FAA facility that guides aircraft approaching or departing an airport. Flights coming in to land will subsequently be passed on to the airport’s air traffic control tower once they are within five miles of the airport and below 2,500 feet. [Federal Aviation Administration, 3/24/2006] The Cleveland TRACON is in contact with Delta 1989 as it descends from 9,000 feet down to 3,000 feet. [Federal Aviation Administration, 9/16/2001] Delta 1989, a Boeing 767 out of Boston, is mistakenly suspected of being hijacked (see 9:39 a.m. September 11, 2001 and (Shortly After 9:44 a.m.) September 11, 2001) and has been instructed to land as soon as possible in Cleveland (see (9:42 a.m.) September 11, 2001). [USA Today, 8/13/2002; 9/11 Commission, 7/24/2004, pp. 27-28; Spencer, 2008, pp. 167-168; USA Today, 9/11/2008]
Pilot Does Not Use Term 'Heavy' - A detailed timeline provided by the Cleveland Airport control tower shortly after 9/11 will describe, “One anomaly that perpetuated concern by approach controllers in the face of constant information that there was nothing going on with [Delta 1989] was that the pilot never used the HEAVY designator in his communications.” [Federal Aviation Administration, 9/16/2001] The term “heavy” alerts controllers to provide extra spacing behind very large aircraft, which are above a certain weight, because these aircraft generate significant wake turbulence. [USA Today, 6/1/2005; USA Today, 5/22/2006]
Controllers Skeptical of Delta 1989's Security - While the TRACON controllers use the “heavy” designator, “the pilot [of Delta 1989] did not respond with it.” The control tower’s timeline will state that, while this detail “may seem minor,” it “should not be overlooked. The use of HEAVY in the terminal environment is of the highest importance. Increased separation standards are required, and misapplication of separation standards can be disastrous. For pilots, not referring to a heavy aircraft as HEAVY is tantamount to calling a doctor ‘Mister.’” As a result, “This omission, along with all of the other information flying around, kept everyone alert and skeptical of the security of the flight.” [Federal Aviation Administration, 9/16/2001]

Entity Tags: Cleveland Terminal Radar Approach Control, Paul Werner

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to the 9/11 Commission, the NMCC learns about the Flight 93 hijacking at this time. Since the FAA has not yet been patched in to the NMCC’s conference call, the news comes from the White House. The White House learned about it from the Secret Service, and the Secret Service learned about it from the FAA. NORAD apparently is still unaware. Four minutes later, a NORAD representative on the conference call states, “NORAD has no indication of a hijack heading to Washington, D.C., at this time.” [9/11 Commission, 6/17/2004]

Entity Tags: US Secret Service, Federal Aviation Administration, National Military Command Center

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

Flight 93 crashed in the Pennsylvania countryside. Resue vehicles arrive in the distance.Flight 93 crashed in the Pennsylvania countryside. Resue vehicles arrive in the distance. [Source: Keith Srakocic/ Associated Press]Flight 93 crashes into an empty field just north of the Somerset County Airport, about 80 miles southeast of Pittsburgh, 124 miles or 15 minutes from Washington, D.C. Presumably, hijackers Ziad Jarrah, Ahmed Alhaznawi, Ahmed Alnami, Saeed Alghamdi, and all the plane’s passengers are killed instantly. [CNN, 9/12/2001; North American Aerospace Defense Command, 9/18/2001; Guardian, 10/17/2001; Pittsburgh Post-Gazette, 10/28/2001; USA Today, 8/12/2002; Associated Press, 8/21/2002; MSNBC, 9/3/2002] The point of impact is a reclaimed coal mine, known locally as the Diamond T Mine, that was reportedly abandoned in 1996. [Pittsburgh Tribune-Review, 9/12/2001; St. Petersburg Times, 9/12/2001; Pittsburgh Tribune-Review, 9/11/2002] Being “reclaimed” means the earth had been excavated down to the coal seam, the coal removed, and then the earth replaced and planted over. [Kashurba, 2002, pp. 121] A US Army authorized seismic study times the crash at five seconds after 10:06 a.m. [Kim and Baum, 2002 pdf file; San Francisco Chronicle, 12/9/2002] As mentioned previously, the timing of this crash is disputed and it may well occur at 10:03 a.m., 10:07 a.m., or 10:10 a.m.

Entity Tags: San Francisco Chronicle, Ziad Jarrah, Ahmed Alhaznawi, Saeed Alghamdi, NBC, Ahmed Alnami

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

An aircraft at Cleveland Hopkins International Airport.An aircraft at Cleveland Hopkins International Airport. [Source: Cleveland Plain Dealer]Delta Air Lines Flight 1989, a Boeing 767 out of Boston that is wrongly suspected of being hijacked (see 9:39 a.m. September 11, 2001 and (Shortly After 9:44 a.m.) September 11, 2001), lands at Cleveland Hopkins Airport in Ohio, and is directed to a remote area of the airport. [Federal Aviation Administration, 9/16/2001; USA Today, 8/13/2002; 9/11 Commission, 7/24/2004, pp. 27-28; WKYC, 9/11/2006]
Plane Flies Long Path toward Airport - Delta Air Lines had been concerned about Flight 1989, and ordered it to land as soon as possible in Cleveland (see (9:42 a.m.) September 11, 2001). [Spencer, 2008, pp. 167; USA Today, 9/11/2008] As it was heading in to land, air traffic controllers instructed Delta 1989 to follow a trajectory that initially took it far past Cleveland Airport. Unknown to the plane’s pilots, the controllers incorrectly believe the flight has been hijacked and contains a bomb, and they were therefore making time to evacuate the airport before the plane landed (see (9:50 a.m. and After) September 11, 2001). [Spencer, 2008, pp. 191]
Plane Directed to Remote Area - Once Delta 1989 is on the ground, the Cleveland Terminal Radar Approach Control (TRACON) informs the FAA’s Cleveland Center that Delta 1989 is “on the ground at 1418,” where “1418” means 10:18 a.m. Cleveland Center asks, “Very safely too, I hope?” The TRACON responds that the plane is being taken to the bomb area to check. [Federal Aviation Administration, 9/16/2001] Delta 1989 is directed to “taxi left onto taxiway Bravo and wait there.” This taxiway leads to a remote part of the airport that is far away from the terminal. The pilot does as instructed. [Spencer, 2008, pp. 229]
Passengers Not Allowed Off - The pilots radio the airport’s air traffic control tower and say: “Just to make sure we don’t have any misunderstandings here, our flaps are up, we are landing only as a precaution at the company’s request. You understand that?” They ask if they are going to get to their gate soon, but the controller responds that city authorities are in charge and he believes people will be coming to search the aircraft. The controller advises that city authorities have said to keep the plane’s passengers on the aircraft for now. [Federal Aviation Administration, 9/16/2001] The passengers and crew will have to remain on board for perhaps a couple of hours, until FBI agents allow them off (see 11:28 a.m.-12:23 p.m. September 11, 2001). [WKYC, 9/11/2006; Spencer, 2008, pp. 270-271]
Conflicting Reports of Landing Time - Subsequent accounts will give conflicting times for when Delta 1989 lands at Cleveland Airport. According to a detailed timeline provided by the airport’s control tower, the aircraft is “on the ground” at 10:18 a.m. [Federal Aviation Administration, 9/16/2001] Several accounts will give similar landing times of between 10:05 a.m. and 10:10 a.m. [Federal Aviation Administration, 1/2/2002; USA Today, 8/13/2002] But a NORAD official will tell the 9/11 Commission that Delta 1989 landed at 9:47 a.m. [9/11 Commission, 5/23/2003] Other accounts will say it lands at between 10:33 a.m. and 10:45 a.m. [Associated Press, 9/11/2001; Associated Press, 9/11/2001; Federal Aviation Administration, 9/17/2001 pdf file]

Entity Tags: Cleveland Air Route Traffic Control Center, Cleveland Terminal Radar Approach Control, Cleveland Hopkins International Airport, David Dunlap, Paul Werner

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Personnel in the White House Situation Room learn of a plane supposedly flying toward the United States from Europe that appears to be hijacked, but it is subsequently determined that the alleged flight does not exist. Those in the Situation Room receive word confirming that a suspicious Northwest Airlines flight from Portugal to Philadelphia is heading toward Washington, DC. The plane is not responding to radio calls and its transponder is squawking the code for a hijacking. White House counterterrorism chief Richard Clarke gives orders for someone to find out more about the flight and what assets the US military has available to intercept it at the coast. Meanwhile, the FAA searches its data for information about the flight and officials try to contact Northwest Airlines to find out more. Those participating in Clarke’s video teleconference (see (9:10 a.m.) September 11, 2001 and 9:25 a.m. September 11, 2001) grow increasingly anxious, since no action can be taken until more details about the flight are found. Then Timothy Flanigan, the deputy White House counsel, who is in the Situation Room, has an idea. He leaves the room and finds an unsecure computer. On this, he searches travel websites for details of the suspicious flight, but finds nothing. He then checks on the Northwest Airlines website and again finds no reference to the flight. He quickly jots down everything he can find about Northwest Airlines flights from Europe and then goes to pass on his findings. After taking a seat at the conference table, he addresses Clarke, who is still searching for information about the plane. “I’ve checked and there’s no such flight,” he says. Astonished at this news, Clarke asks, “How did you check?” “I looked on their website,” Flanigan replies. Clarke then passes on the news to the other participants in the video teleconference. “I have information that there is no such flight,” he says and adds, “Check that again.” [Eichenwald, 2012, pp. 36-37] The 9/11 Commission Report will later note that there are “multiple erroneous reports of hijacked aircraft” this morning (see (9:09 a.m. and After) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 28]

Entity Tags: Richard A. Clarke, Northwest Airlines, Timothy E. Flanigan, Federal Aviation Administration

Timeline Tags: Complete 911 Timeline

The entrance to Offutt Air Force Base’s bunker.The entrance to Offutt Air Force Base’s bunker. [Source: CBC]Air Force One, with President Bush on board, lands at Offutt Air Force Base near Omaha, Nebraska, accompanied by two F-16 fighter jets. [Salon, 9/12/2001; Bamford, 2004, pp. 89; 9/11 Commission, 7/24/2004, pp. 326] Offutt is the home of the US Strategic Command (Stratcom), which controls America’s nuclear weapons. [Associated Press, 9/11/2001; US Air Force, 9/6/2011] The large base is one of the most heavily defended in the US. [Daily Telegraph, 12/16/2001] Personnel there were told earlier in the day that the president might come to Offutt during the crisis but they only received confirmation that he would be landing at the base about 20 to 30 minutes ago. [Omaha World-Herald, 2/27/2002; Omaha World-Herald, 9/8/2002; Omaha World-Herald, 9/9/2016] They have, however, taken the initiative to start preparing for his arrival. “There were pretty wide-scale preparations going on anticipating that the president might come, without knowing for sure, even before we got notice that he was coming,” Admiral Richard Mies, commander in chief of Stratcom, will later recall. “We’d started to evacuate the main quarters that could be used for VIPs and install some of the protection there that’d be needed in case [Bush] needed to spend the night,” Mies will say. [NET News, 12/27/2011; Politico Magazine, 9/9/2016] Journalists on Air Force One were not told they would be landing at Offutt. However, they learned what was happening when they saw a local television channel showing the plane arriving at the base (see (2:50 p.m.) September 11, 2001). [Gilbert et al., 2002, pp. 198; Sammon, 2002, pp. 120-121; Sylvester and Huffman, 2002, pp. 138] Bush will get off the plane about 10 minutes after it lands and then be taken to an underground command center (see (3:00 p.m.-3:10 p.m.) September 11, 2001). [Salon, 9/12/2001; Bamford, 2004, pp. 89] He will conduct a meeting of the National Security Council in a secure video teleconference while he is at the base (see (3:15 p.m.) September 11, 2001). [Washington Times, 10/8/2002; 9/11 Commission, 7/24/2004, pp. 326] Personnel at Offutt were the middle of a major training exercise called Global Guardian when America came under attack this morning (see 8:30 a.m. September 11, 2001 and Before 9:00 a.m. September 11, 2001), although the exercise has now been canceled (see (10:44 a.m.) September 11, 2001). [Omaha World-Herald, 9/8/2002; Schmitt and Shanker, 2011, pp. 22]

Entity Tags: Offutt Air Force Base, George W. Bush, Richard Mies

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

A US Airways airliner.A US Airways airliner. [Source: Public domain]A US Airways plane that is flying to the United States from Madrid, Spain, is incorrectly suspected of being hijacked. [Federal Aviation Administration, 9/11/2001; White House, 10/24/2001] It is stated over an FAA teleconference that the White House has reported this suspicious aircraft, which is heading to Philadelphia International Airport, and the military is scrambling fighter jets in response to it. [Federal Aviation Administration, 1/2/2002] NORAD’s Northeast Air Defense Sector (NEADS) was alerted to the plane by US Customs and the FBI, according to a NORAD representative on the Pentagon’s air threat conference call (see 9:37 a.m.-9:39 a.m. September 11, 2001). NORAD has been unable to locate the aircraft on radar, according to the NORAD representative. [US Department of Defense, 9/11/2001] Accounts conflict over whether the plane is US Airways Flight 930 or Flight 937. [Federal Aviation Administration, 9/2001; Federal Aviation Administration, 9/11/2001; Federal Aviation Administration, 1/2/2002]
Plane Is Reportedly Transmitting the Hijack Signal - Lewis Libby, Vice President Dick Cheney’s chief of staff, who is in the Presidential Emergency Operations Center (PEOC) below the White House, will later recall that when those in the PEOC learn of the suspect flight, “we got word that it was only 30 minutes or so outside of US airspace.” According to Libby, the plane’s transponder is transmitting the code for a hijacking: He will say it is reported that the flight has been “showing hijacking through some electronic signal.” [White House, 11/14/2001] However, according to the NORAD representative on the air threat conference call, the plane’s transponder has not been “squawking” the code for a hijacking. “We do not have squawk indication at this point,” he has said.
Plane Is Reportedly Diverted to Pittsburgh - An FAA representative on the air threat conference call apparently says an e-mail has been sent from the suspicious aircraft, stating that the plane is being diverted to Pittsburgh, although the FAA representative’s communications are distorted and therefore unclear. [US Department of Defense, 9/11/2001]
President Says Fighters Can Shoot Down the Plane - President Bush discusses the suspicious US Airways flight with Secretary of Defense Donald Rumsfeld over the air threat conference call after landing at Offutt Air Force Base in Nebraska (see 2:50 p.m. September 11, 2001) and Major General Larry Arnold, the commander of the Continental United States NORAD Region (CONR), listens in. [Filson, 2003, pp. 87-88] Rumsfeld wants Bush to confirm that fighters are authorized to shoot down the plane if it is considered a threat to a city in the US. “The reason I called… was just to verify that your authorization for the use of force would apply as well in this situation,” he says. Bush replies, “It does, but let us make sure that the fighters and you on the ground get all the facts.” [US Department of Defense, 9/11/2001]
Plane Is on the Ground in Spain - After a time, it will be found that the plane is not a threat and is on the ground in Spain. Arnold will be called by Colonel Robert Marr, the battle commander at NEADS, and told, “We just talked to the airline and that aircraft is back on the ground in Madrid.” [Filson, 2003, pp. 88] According to Libby, “It turned out that, I think, it was only 35 minutes out of Spanish airspace, not out of our airspace.” [White House, 11/14/2001] Reggie Settles, the FAA representative at NORAD’s Cheyenne Mountain Operations Center in Colorado, will be informed by US Airways that Flight 937 in fact never existed. However, he will be told, there is a US Airways Flight 911, which “took off from Madrid,” but “has turned back and returned to Madrid,” and “is not en route to the United States.” [US Department of Defense, 9/11/2001]
President Decides to Leave Offutt after the Concerns Are Resolved - After he learns that the suspicious plane is back in Spain, Arnold will pick up the hot line and tell Bush: “Mr. President, this is the CONR commander.… No problem with Madrid.” According to Arnold, Bush will reply, “Okay, then I’m getting airborne.” [Filson, 2003, pp. 88] Bush will take off from Offutt aboard Air Force One at around 4:30 p.m. (see (4:33 p.m.) September 11, 2001). [CNN, 9/12/2001] Numerous aircraft are incorrectly suspected of being hijacked on this day (see (9:09 a.m. and After) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 28; Newhouse News Service, 3/31/2005] The US Airways flight from Madrid is the last of these, according to Arnold. [Code One Magazine, 1/2002]

Entity Tags: Larry Arnold, Federal Aviation Administration, Federal Bureau of Investigation, George W. Bush, Donald Rumsfeld, North American Aerospace Defense Command, US Airways, Robert Marr, Reggie Settles, White House, Lewis (“Scooter”) Libby, Northeast Air Defense Sector, US Customs Service

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

A report is secretly delivered to Congress by the Pentagon’s Office of Inspector General, regarding the inaccuracy of statements made by Defense Department officials on the military’s response to the September 11 hijackings. The 9/11 Commission made a formal request in summer 2004 for the inspector general to investigate the matter, because military officials had given testimony that was later proved to have been false (see Shortly before July 22, 2004). For example, they claimed that NORAD had been tracking Flight 93 on 9/11 and was ready to shoot it down if it threatened Washington (see Shortly Before 9:36 a.m. September 11, 2001 and (9:36 a.m.-10:06 a.m.) September 11, 2001). Yet audiotapes obtained under subpoena showed NORAD was unaware of this flight until after it crashed. In its report, the inspector general’s office states that it found “the inaccuracies, in part, resulted because of inadequate forensic capabilities.” It says that commanders found it difficult to create an accurate timeline of the events of 9/11 due to the lack of a well-coordinated system in logging information about air defense operations. At the time, air defense watch centers had used handwritten logs, and these could be unreliable. Following the attacks, the report claims, commanders failed to press hard enough for an accurate timeline to be produced for the benefit of investigations, like the 9/11 Commission. Yet, as some of the Commission’s staff will later point out, the military had already reviewed the NORAD audiotapes chronicling the events of 9/11 prior to its officials giving their incorrect testimonies. In response to a freedom of information request by the New York Times, the inspector general’s report will be publicly released in August 2006, but the equivalent of several pages will be blacked out on national security grounds. [Vanity Fair, 8/1/2006; Washington Post, 8/2/2006; New York Times, 8/5/2006; Reuters, 8/5/2006; US Department of Defense, 9/12/2006 pdf file]
9/11 Staff Member Criticizes Report - In his 2009 book The Ground Truth, John Farmer, who served as senior counsel to the 9/11 Commission, will criticize the inspector general’s report. Farmer says the report mischaracterizes the 9/11 Commission’s referral by saying the Commission had alleged officials knowingly made false statements, when instead it had simply “documented the facts concerning what occurred on 9/11, the disparity between those facts and what the government had been telling the public with total assurance since 9/11, and the relative ease with which anyone looking could have uncovered those facts.” He faults the inspector general for interpreting the issue narrowly, by focusing on statements made to the 9/11 Commission; ignoring the larger context in which the events of 9/11 were extremely significant and so it should have been extremely important for the military to understand the truth of what happened, in order to correct any problems, as well as to be able to present an accurate account to the White House and to the public; and failing to address the question of whether the false accounts had served anyone’s interests. The inspector general’s report affirms the claims of top NORAD commanders that, in Farmer’s words, they had been “simply too busy fixing the system and fighting the war on terror to concern themselves with piecing together the facts of 9/11.” Farmer will ask, “[H]ow… could the Department of Defense identify and correct operational weaknesses without knowing precisely what had occurred that morning?” He will question the report’s determination that the Defense Department lacked the forensic capabilities for maintaining logs, video and audio recordings, and storing radar information, and had not coordinated with the FAA on reconstructing the events of 9/11, as the Commission had documented evidence that the two agencies had indeed coordinated while developing their reconstructions of events. Farmer will write that “it is impossible to conclude honestly, from the two inspector general reports, that the official version of the events of 9/11 was the result of mere administrative incompetence; too many questions remain unanswered.” He will add, “History should record that whether through unprecedented administrative incompetence or orchestrated mendacity, the American people were misled about the nation’s response to the 9/11 attacks.” [Farmer, 2009, pp. 283-289]

Entity Tags: US Department of Defense, Office of the Inspector General (DoD), John Farmer

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