!! History Commons Alert, Exciting News

Context of '(9:04 a.m.) September 11, 2001: Flight 175 Crash Leads to Confusion at NEADS; Some Think It Is a Simulation'

This is a scalable context timeline. It contains events related to the event (9:04 a.m.) September 11, 2001: Flight 175 Crash Leads to Confusion at NEADS; Some Think It Is a Simulation. 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 modernization program of the 1st Air Force’s air operation centers, which include NORAD’s Northeast Air Defense Sector (NEADS), is started. Over the next several years, Litton Data Systems is tasked with computerizing the way the Air National Guard accomplishes its air sovereignty mission, which is the surveillance of US skies in coordination with the FAA. Until now, flight plans from the FAA have been “compiled in logs and have to be searched by hand to identify aircraft,” according to National Guard magazine. “The new system will mean fewer manual inquiries and phone contact with FAA officials about commercial aircraft. The FAA flight plan is now hooked up via computer with the new R/SAOCs [Regional/Sector Air Operation Centers] so operators can easily track friendly aircraft through our air space without having to get someone on the phone or thumb through written log books of flight plans. Composite air pictures are now shown in real time on the screen with no delay in transmission. Plans on the screen are shown as they are happening.” The software also allows computer simulations to be used for training purposes, so operators can “go through a situation at their terminals as if it were happening.” Col. Dan Navin, the special assistant to the commander of 1st Air Force, says, “It will enhance our ability to do what many say is the most important job of the Air Force, and that is air sovereignty.” The new systems should be fully operational in all seven 1st Air Force air operation centers by 2003. [National Guard, 9/1997] It is possible that this software is being used on the morning of 9/11, when a NORAD training exercise will include simulated information, known as “inject,” being shown on its radar screens (see (9:00 a.m.) September 11, 2001). [Toronto Star, 12/9/2001]

Entity Tags: Northeast Air Defense Sector, 1st Air Force, Air National Guard, Litton Data Systems

Timeline Tags: Complete 911 Timeline

The North American Aerospace Defense Command (NORAD) commences Northern Vigilance, a military operation that involves it deploying fighter jets to Alaska and Northern Canada to monitor a Russian Air Force training exercise. The Russian exercise is scheduled to take place over the North Atlantic, Pacific, and Arctic Oceans from September 10 to September 14 (see September 10, 2001), and the NORAD fighters are set to stay in Alaska and Northern Canada until it ends. [BBC, 2001, pp. 161; North American Aerospace Defense Command, 9/9/2001; Washington Times, 9/11/2001] As well as conducting this operation, NORAD is currently running a major exercise called Vigilant Guardian, which “postulated a bomber attack from the former Soviet Union,” according to the 9/11 Commission Report (see September 10, 2001, (6:30 a.m.) September 11, 2001, and (8:00 a.m.) September 11, 2001). [9/11 Commission, 2004; 9/11 Commission, 3/1/2004 pdf file; 9/11 Commission, 7/24/2004, pp. 458] The Russians will cancel their exercise on the morning of September 11 in response to the terrorist attacks in the United States (see (After 10:03 a.m.) September11, 2001), when they “knew NORAD would have its hands full,” according to the Toronto Star. [Toronto Star, 12/9/2001; Defense Video and Imagery Distribution System, 9/8/2011] It is unknown from which bases NORAD sends fighters for Northern Vigilance and how many US military personnel are involved. However, in December 2000, it took similar action—called Operation Northern Denial—in response to a “smaller scale” Russian “long-range aviation activity in northern Russia and the Arctic.” More than 350 American and Canadian military personnel were involved on that occasion. [Canadian Chief of Defense Staff, 5/30/2001, pp. 6 pdf file; North American Aerospace Defense Command, 9/9/2001]

Entity Tags: Operation Northern Vigilance, North American Aerospace Defense Command

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

NORAD’s war room in Cheyenne Mountain, ColoradoNORAD’s war room in Cheyenne Mountain, Colorado [Source: Val Gempis]Lieutenant Colonel Dawne Deskins and other day shift employees at NORAD’s Northeast Air Defense Sector (NEADS) in Rome, NY, start their workday. NORAD is conducting a week-long, large-scale exercise called Vigilant Guardian. [Newhouse News Service, 1/25/2002] Deskins is regional mission crew chief for the Vigilant Guardian exercise. [ABC News, 9/11/2002]
Exercise Includes Simulated Attack on the US - Vigilant Guardian is described as “an exercise that would pose an imaginary crisis to North American Air Defense outposts nationwide”; as a “simulated air war”; and as “an air defense exercise simulating an attack on the United States.” According to the 9/11 Commission, it “postulated a bomber attack from the former Soviet Union.” [Newhouse News Service, 1/25/2002; Filson, 2003, pp. 55 and 122; 9/11 Commission, 7/24/2004, pp. 458] Vigilant Guardian is described as being held annually, and is one of NORAD’s four major annual exercises. [Filson, 2003, pp. 41; Arkin, 2005, pp. 545; GlobalSecurity (.org), 4/27/2005] However, one report says it takes place semi-annually. [Aviation Week and Space Technology, 6/3/2002] Accounts by participants vary on whether 9/11 is the second, third, or fourth day of the exercise. [Code One Magazine, 1/2002; Newhouse News Service, 1/25/2002; Ottawa Citizen, 9/11/2002] Vigilant Guardian is a command post exercise (CPX), and in at least some previous years was conducted in conjunction with Stratcom’s Global Guardian exercise and a US Space Command exercise called Apollo Guardian. [US Congress, n.d.; Arkin, 2005, pp. 545; GlobalSecurity (.org), 4/27/2005] All of NORAD is participating in Vigilant Guardian on 9/11. [Aviation Week and Space Technology, 6/3/2002]
Exercise Includes Simulated Hijacking - Vanity Fair reports that the “day’s exercise” (presumably Vigilant Guardian) is “designed to run a range of scenarios, including a ‘traditional’ simulated hijack in which politically motivated perpetrators commandeer an aircraft, land on a Cuba-like island, and seek asylum.” [Vanity Fair, 8/1/2006] However, at NEADS, most of the dozen or so staff on the operations floor have no idea what the exercise is going to entail and are ready for anything. [Utica Observer-Dispatch, 8/5/2004]
NORAD Fully Staffed and Alert - NORAD is currently running a real-world operation named Operation Northern Vigilance (see September 9, 2001). It may also be conducting a field training exercise calling Amalgam Warrior on this morning (see 9:28 a.m. September 11, 2001). NORAD is thus fully staffed and alert, and senior officers are manning stations throughout the US. The entire chain of command will be in place and ready when the first hijacking is reported. An article later says, “In retrospect, the exercise would prove to be a serendipitous enabler of a rapid military response to terrorist attacks on September 11.” [Aviation Week and Space Technology, 6/3/2002; Bergen Record, 12/5/2003] Colonel Robert Marr, in charge of NEADS, will say: “We had the fighters with a little more gas on board. A few more weapons on board.” [ABC News, 9/11/2002] However, Deskins and other NORAD officials later are initially confused about whether the 9/11 attacks are real or part of the exercise (see (8:38 a.m.-8:43 a.m.) September 11, 2001).

Entity Tags: Northeast Air Defense Sector, Dawne Deskins, North American Aerospace Defense Command, Operation Northern Vigilance, Vigilant Guardian, Robert Marr

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

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

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

The air traffic controller at the FAA’s New York Center who is responsible for monitoring Flight 175 sees the now-hijacked plane on his radar screen making a sharp turn (see (8:50 a.m.) September 11, 2001), and is astonished as it rapidly climbs 3,000 feet. [National Transportation Safety Board, 2/19/2002 pdf file; The Learning Channel, 8/20/2006] Around this time, the controller, Dave Bottiglia, first notices that Flight 175’s transponder code has changed (see 8:51 a.m.-8:53 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 21] As he will later recall: “As I’m watching, United 175 makes a hard left-hand turn and starts climbing. Not only did he make a sharp turn, but he also climbed 3,000 feet in a matter of approximately one minute, which is a very fast rate of climb.” Bottiglia will add, “This is something that we have never seen before.” He immediately turns to the manager at the New York Center and says, “I believe I just lost United 175.” [The Learning Channel, 8/20/2006] Yet, according to the 9/11 Commission, the center does not alert NORAD’s Northeast Air Defense Sector (NEADS) to Flight 175 until 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, 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/13/2002]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

A soldier monitors a NORAD radar screen.A soldier monitors a NORAD radar screen. [Source: National War College]NORAD has had fighter jets deployed to Alaska and Northern Canada for the past two days. They are there for a real-world maneuver called Operation Northern Vigilance, tasked with monitoring a Russian air force exercise being conducted in the Russian Arctic all this week (see September 9, 2001). [North American Aerospace Defense Command, 9/9/2001] At its operations center deep inside Cheyenne Mountain, Colorado, NORAD is also reportedly at “full ‘battle staff’ levels for a major annual exercise that tests every facet of the organization.” The operations center is now contacted by NORAD’s Northeast Air Defense Sector (NEADS), based in Rome, New York. NEADS says the FAA believes there is a hijacking in progress and is asking NORAD for support; this is not part of the exercise. As the Toronto Star will later report: “In a flash, Operation Northern Vigilance is called off. Any simulated information, what’s known as an ‘inject,’ is purged from the screens.” [Toronto Star, 12/9/2001] NORAD has the capacity to inject simulated material, including mass attacks, during exercises, “as though it was being sensed for the first time by a radar site.” [US Department of Defense, 1/15/1999] However, Northern Vigilance is a military operation, not a training exercise. [North American Aerospace Defense Command, 9/9/2001; US Congress, 3/11/2005] So presumably the “simulated information” is part of a NORAD exercise currently taking place, such as Vigilant Guardian (see (6:30 a.m.) September 11, 2001). Therefore, many minutes into the real 9/11 attacks, there may be false radar blips appearing on the screens of NORAD personnel. Additional details, such as whose radar screens have false blips and over what duration, are unclear. However, while the Toronto Star will indicate that the simulated material is removed from NORAD radar screens shortly before 9:03 a.m., when the second attack on the World Trade Center takes place, at 10:12 a.m. an officer at the operations center will call NEADS and ask it to “terminate all exercise inputs coming into Cheyenne Mountain” (see 10:12 a.m. September 11, 2001). [North American Aerospace Defense Command, 9/11/2001; Toronto Star, 12/9/2001] This would indicate that the NORAD operations center continues receiving simulated radar information for over an hour more, until after Flight 93 has crashed (see (10:06 a.m.) September 11, 2001) and the terrorist attacks have ended. The Russians, after seeing the attacks on New York and Washington on television, will quickly communicate that they are canceling their Russian Arctic exercise. [Toronto Star, 12/9/2001; National Post, 10/19/2002]

Entity Tags: Northeast Air Defense Sector, Vigilant Guardian, Operation Northern Vigilance, North American Aerospace Defense Command

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

NORAD’s Northeast Air Defense Sector (NEADS) in Rome, NY, has just received a phone call informing it of the hijacking of Flight 175 (see (9:03 a.m.) September 11, 2001), and several personnel have witnessed the plane crashing into the second World Trade Center tower live on CNN. There is considerable confusion on the operations floor over whether the plane seen on TV is the hijacking they have just been informed of. Tape recordings capture NEADS personnel in the background trying to make sense of things: “Is this explosion part of that that we’re lookin’ at now on TV?“… “And there’s a possible second hijack also—a United Airlines“… “Two planes?” Someone comments, “I think this is a damn input, to be honest.” [Vanity Fair, 8/1/2006] Another person replies, “Then this is a damned messed-up input!” [Spencer, 2008, pp. 84] “Input” refers to a simulations input, as part of a training exercise. [Vanity Fair, 8/1/2006] NORAD has the capacity to inject simulated material, including mass attacks, during exercises, “as though it was being sensed for the first time by a radar site.” [US Department of Defense, 1/15/1999] At least one military exercise this morning is reported to include simulated information injected onto radar screens (see (9:00 a.m.) September 11, 2001). [Toronto Star, 12/9/2001] At the current time, despite the earlier crash of Flight 11, NORAD has yet to cancel a major exercise it is in the middle of (see (Shortly After 9:03 a.m.) September 11, 2001). [Filson, 2003, pp. 59]

Entity Tags: Northeast Air Defense Sector

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

NORAD’s air defence computer system, the AN/FYQ-93.NORAD’s air defence computer system, the AN/FYQ-93. [Source: Federation of American Scientists]A technician at NORAD’s Northeast Air Defense Sector (NEADS) instructs personnel on the NEADS operations floor to turn off their “sim switches,” apparently so as to remove from their radar screens simulated information for a training exercise that was being conducted this morning. [Northeast Air Defense Sector, 8/23/2001; North American Aerospace Defense Command, 9/11/2001; 9/11 Commission, 2004]
Staffer Complained, 'Let's Get Rid of This Goddamn Sim' - A few minutes earlier, at 9:30 a.m., a member of staff on the operations floor complained about simulated information—presumably false tracks—appearing on NEADS radar screens. He said: “You know what, let’s get rid of this godd_mn sim. Turn your sim switches off. Let’s get rid of that crap.” [North American Aerospace Defense Command, 9/11/2001; North American Aerospace Defense Command, 9/11/2001] (A “sim switch” presumably allows simulated material on radar scopes to be turned on or off.)
Technician Instructs, 'Turn Off Your Sim Switches' - Now a member of NEADS staff, who according to a 9/11 Commission document is Technical Sergeant Jeffrey Richmond, gives an instruction to the NEADS surveillance technicians, “All surveillance, turn off your sim switches.” Seconds later, apparently in response to this instruction, someone on the operations floor tells a colleague, “You got your sim switches down.” [North American Aerospace Defense Command, 9/11/2001; 9/11 Commission, 2004]
Sim Switches Turned On for Day's Exercise - Simulated material (“sim”) is apparently appearing on NEADS radar screens because of the NORAD training exercise, Vigilant Guardian, that was being conducted this morning (see (6:30 a.m.) September 11, 2001). Former Deputy Secretary of Defense John Hamre has revealed that NORAD has the capacity to inject simulated material into the system, “as though it was being sensed for the first time by a radar site.” In a training exercise in December 1998, for example, NORAD ran “30 different simulations, some of them being mass attacks, some of them being single missiles.” An information page on the current exercise stated, “All of NEADS, operations personnel are to have their sim switches turned ‘on’ starting at 1400Z 6 Sept. 01 till endex [the end date of the exercise].” Since Vigilant Guardian was originally scheduled to continue until September 13, this would mean NEADS personnel had their sim switches turned on this morning. [US Department of Defense, 1/15/1999; Northeast Air Defense Sector, 8/23/2001]
Radar Equipment Set to Display 'Sim Tracks' - A memo outlining special instructions for Vigilant Guardian participants further detailed how NORAD equipment needed to be set to display simulated material during the exercise. It stated: “The exercise will be conducted sim over live on the air sovereignty string. The Q-93 must be placed in the mixed mode to allow the telling [i.e. the communicating of information between facilities] of sim tracks.” [Northeast Air Defense Sector, 8/23/2001] The Q-93 is a piece of equipment used by NORAD, which is described as “a suite of computers and peripheral equipment configured to receive plot data from ground radar systems,” and which “performs track processing.” [General Accounting Office, 12/24/1992 pdf file; Federation of American Scientists, 4/23/2000] The Q-93 also “receives flight plans from the FAA, and has bi-directional communications with NORAD headquarters and a real-time link to AWACS [Airborne Warning and Control System planes].” [Satterthwaite, Corman, and Herm, 6/2002]
Exercise Supposedly Canceled Earlier On - While NEADS radar scopes are still displaying simulated material as late as 9:34 a.m., some accounts will claim the Vigilant Guardian exercise was canceled shortly after 9:03 a.m., when the second World Trade Center tower was hit (see (Shortly After 9:03 a.m.) September 11, 2001). [Airman, 3/2002; Filson, 2003, pp. 59] And according to a report in the Toronto Star, “Any simulated information” for the exercise was “purged from the [radar] screens” at NORAD’s operations center in Cheyenne Mountain, Colorado, shortly before the second WTC tower was hit (see (9:00 a.m.) September 11, 2001). [Toronto Star, 12/9/2001] However, NEADS will receive a phone call from the operations center at 10:12 a.m. in which the caller asks it to “terminate all exercise inputs coming into Cheyenne Mountain” (see 10:12 a.m. September 11, 2001). [North American Aerospace Defense Command, 9/11/2001]

Entity Tags: Jeffrey Richmond, Northeast Air Defense Sector, Vigilant Guardian, John J. Hamre

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

An officer at NORAD’s operations center in Cheyenne Mountain, Colorado, calls NORAD’s Northeast Air Defense Sector (NEADS) and asks it to stop “exercise inputs” being sent to the operations center.
NORAD Calls Chief of Exercises at NEADS - The NORAD officer, a “Captain Taylor,” calls NEADS, where the phone is answered by Captain Brian Nagel. [North American Aerospace Defense Command, 9/11/2001] Nagel is chief of NEADS live exercises. [Filson, 2003, pp. 74] After introducing himself, Taylor says, “What we need you to do right now is to terminate all exercise inputs coming into Cheyenne Mountain.” Nagel gives Taylor an extension number and suggests that he call it to get the exercise inputs stopped. Taylor replies, “I’ll do that.” [North American Aerospace Defense Command, 9/11/2001] According to an article in Vanity Fair, “inputs” are simulated scenarios that are put into play for training exercises. [Vanity Fair, 8/1/2006] NORAD has been conducting a major exercise this morning called Vigilant Guardian (see (6:30 a.m.) September 11, 2001). [Arkin, 2005, pp. 545]
Exercise Includes Simulated Radar Information - Taylor is presumably referring specifically to false tracks that have been transmitted onto NORAD radar screens for the exercise. NORAD has the capability to inject simulated material, including mass attacks, into the system during exercises, “as though it was being sensed for the first time by a radar site.” [US Department of Defense, 1/15/1999] All of the operations personnel at NEADS have been instructed to “have their sim switches turned ‘on’” (presumably to allow simulated information to appear on their radar screens) from September 6 until the end of Vigilant Guardian, on September 13. An information page on the exercise stated that a “sim test track will be in place and forward told [i.e. transferred to a higher level of command] to both NORAD and CONR,” NORAD’s Continental United States Region. [Northeast Air Defense Sector, 8/23/2001]
Exercise Supposedly Called Off Earlier - More than 50 members of the battle staff at the NORAD operations center have been participating in Vigilant Guardian this morning. [Airman, 3/2002; 9/11 Commission, 3/1/2004 pdf file] Some accounts will claim this exercise was canceled shortly after 9:03 a.m., when the second World Trade Center tower was hit (see (Shortly After 9:03 a.m.) September 11, 2001). [Airman, 3/2002; Filson, 2003, pp. 59] And a report in the Toronto Star will state, “Any simulated information” for the exercise was “purged from the [radar] screens” at the operations center shortly before the second tower was hit (see (9:00 a.m.) September 11, 2001). [Toronto Star, 12/9/2001] But a member of staff at NEADS complained at 9:30 a.m. about simulated material still appearing on radar screens there, and at 9:34 a.m. the NEADS surveillance technicians were instructed to turn off their “sim switches” (see 9:34 a.m. September 11, 2001). [North American Aerospace Defense Command, 9/11/2001; North American Aerospace Defense Command, 9/11/2001; 9/11 Commission, 2004]

Entity Tags: Vigilant Guardian, Brian Nagel, Northeast Air Defense Sector, North American Aerospace Defense Command

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

Author Mike Ruppert.Author Mike Ruppert. [Source: From the Wilderness]Mike Ruppert, a former detective with the Los Angeles Police Department, publishes Crossing the Rubicon, in which he argues that al-Qaeda lauched the 9/11 attacks, but certain individuals within the Bush administration, the US Secret Service, and the CIA not only failed to stop the attacks but prevented others within government from stopping them. In contrast to other prominent skeptic literature (see, for example, November 8, 2005 and March 20, 2006), Ruppert focuses on non-physical evidence. He believes that those responsible for the attacks intended to use it as a pretext for war in the Middle East with the intention to gain control of a large amount of the planet’s oil reserves, which he thinks will soon start to run out, forcing prices higher. He also discusses the various war games on 9/11 (see (9:00 a.m.) September 11, 2001 and (9:40 a.m.) September 11, 2001), allegations of insider trading before the attacks (see Early September 2001), whether the CIA had a hand in thwarting the Moussaoui investigation (see August 20-September 11, 2001), and US relations with Pakistan and Saudi Arabia (see October 7, 2001 and January 2000)). [Ruppert, 2004]

Entity Tags: Michael Ruppert

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