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

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

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

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

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

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

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

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

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

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

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

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

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

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