!! History Commons Alert, Exciting News

Context of 'Shortly After 9:21 a.m. September 11, 2001: NEADS Technicians Unable to Locate Flight 11 Following Incorrect Report It Is Still Airborne'

This is a scalable context timeline. It contains events related to the event Shortly After 9:21 a.m. September 11, 2001: NEADS Technicians Unable to Locate Flight 11 Following Incorrect Report It Is Still Airborne. 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.

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

Master Sergeant Maureen Dooley.Master Sergeant Maureen Dooley. [Source: ABC News]Rumors have started circulating through the civilian air traffic system that the plane that hit the World Trade Center was a small Cessna. There is increasing confusion on the operations floor at NORAD’s Northeast Air Defense Sector (NEADS) as to whether it was really Flight 11. ID tech Stacia Rountree is on the phone with Colin Scoggins, a civilian manager who is the military liaison at the FAA’s Boston Center. Scoggins initially seems to confirm that the plane was Flight 11, saying: “Yeah, he crashed into the World Trade Center.… [D]isregard the tail number [given earlier for American 11].” When Rountree asks, “He did crash into the World Trade Center?” Scoggins replies, “[T]hat’s what we believe, yes.” However, an unidentified male staff member at NEADS overhears, and queries: “I never heard them say American Airlines Flight 11 hit the World Trade Center. I heard it was a civilian aircraft.” Master Sergeant Maureen Dooley takes the phone from Rountree and asks Scoggins, “[A]re you giving confirmation that American 11 was the one?” Apparently contradicting what he’d previously said, Scoggins replies: “No, we’re not gonna confirm that at this time. We just know an aircraft crashed in.… The last [radar sighting] we have was about 15 miles east of JFK [International Airport in New York City], or eight miles east of JFK was our last primary hit. He did slow down in speed… and then we lost ‘em.” [Vanity Fair, 8/1/2006] This confusion will continue later on, when NEADS will be misinformed that Flight 11 is still airborne (see 9:21 a.m. September 11, 2001).

Entity Tags: Stacia Rountree, Colin Scoggins, Maureen Dooley, Northeast Air Defense Sector

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Tape recordings of the operations floor at NORAD’s Northeast Air Defense Sector (NEADS) in Rome, New York indicate that both NEADS and NORAD are experiencing significant problems communicating with other agencies:
bullet At 9:12 a.m., a member of staff at NEADS tells another military agency over the phone: “We’re trying to reach the military coordinator. We’re having a difficult time.” [North American Aerospace Defense Command, 9/11/2001]
bullet At 9:22 a.m., a women at NEADS calls what is apparently an American Airlines office in New York, to ask about a report NEADS has received that Flight 11 is still airborne and headed towards Washington (see 9:21 a.m. September 11, 2001). After being given a phone number she needs to call for more information, the woman at NEADS replies: “[D]o me a favor and have them call us? We cannot call out for some reason.” [North American Aerospace Defense Command, 9/11/2001]
bullet At around 10:31 a.m., someone from the 1st Fighter Wing, which is the host unit at Langley Air Force Base in Virginia, calls NEADS. During the conversation, they mention, “I tried to get a hold of NORAD… and their lines are all busy.” NEADS replies, “Yeah, I can believe it,” and adds, “Right now the circuits are so busy.” [North American Aerospace Defense Command, 9/11/2001]
bullet Around 11:50 a.m., someone with the New York Air National Guard’s 109th Airlift Wing is on the phone to NEADS. They mention, “We’re having a tough time getting hold of you guys.” NEADS responds, “We’re having problems with our phone lines as well.” [North American Aerospace Defense Command, 9/11/2001]
bullet At 11:57 a.m., a member of staff at NEADS complains: “They turned off all the goddamned lines to the outside.… No, local. So you can’t make outside phone calls.” [North American Aerospace Defense Command, 9/11/2001]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Having just received an incorrect report that Flight 11—which has already hit the World Trade Center—is still airborne and heading toward Washington (see 9:21 a.m. September 11, 2001), technicians at NORAD’s Northeast Air Defense Sector (NEADS) try, unsuccessfully, to locate the aircraft on their radar screens. [Spencer, 2008, pp. 137-139] At NEADS, Major James Anderson says the hijackers are “probably not squawking anything anyway,” meaning their plane’s transponder is not broadcasting a signal. He adds, “I mean, obviously these guys are in the cockpit.” Major Kevin Nasypany, the mission crew commander, replies, “These guys are smart.” Another member of staff adds, “Yeah, they knew exactly what they wanted to do.” [Vanity Fair, 8/1/2006] After giving the order to launch the F-16s kept on alert at Langley Air Force Base (see 9:23 a.m. September 11, 2001), Nasypany calls out, “I need more trackers!” He needs his technicians to locate the hijacked plane on radar so that his weapons team can pass on its coordinates to the Langley fighters. But the trackers are unable to find the transponder code for Flight 11 on their radar screens. They begin calling up, one at a time, the tracks on their screens that are in the airspace between New York and Washington, and attach a tag to each after it has been identified. One technician draws a line on a map between New York and Washington, showing the area across which Flight 11 would be traveling. It includes Philadelphia, Atlantic City, and Baltimore. He looks at his radar screen and sees there are hundreds of tracks in that area. [Spencer, 2008, pp. 138-139] Colin Scoggins, the military liaison at the FAA’s Boston Center, who gave NEADS the incorrect report about Flight 11, will later say he’d only heard the plane was still airborne and heading for Washington on a conference call between FAA centers. According to Vanity Fair, air traffic controllers “were never tracking an actual plane on the radar after losing American 11 near Manhattan, but if it had been flying low enough, the plane could have gone undetected.” [Vanity Fair, 8/1/2006]

Entity Tags: Kevin Nasypany, Colin Scoggins, James Anderson, Northeast Air Defense Sector

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Major Kevin Nasypany inside NEADSMajor Kevin Nasypany inside NEADS [Source: Mark Schafer/ Vanity Fair]According to the 9/11 Commission, NEADS has just been told that the hijacked Flight 11 is still in the air and heading toward Washington. Major Kevin Nasypany, the mission crew commander, says to NEADS Commander Robert Marr, “Okay, uh, American Airlines is still airborne. Eleven, the first guy, he’s heading towards Washington. Okay? I think we need to scramble Langley right now. And I’m gonna take the fighters from Otis, try to chase this guy down if I can find him.” After receiving approval to do so, Nasypany issues the order. “Okay… scramble Langley,” he says. “Head them towards the Washington area.” The Langley, Virginia, base gets the scramble order at 9:24 a.m. (see 9:24 a.m. September 11, 2001). NEADS keeps its fighters from the Otis base over New York City. In 2004 the 9/11 Commission will state, “this response to a phantom aircraft, American 11, is not recounted in a single public timeline or statement issued by FAA or [Defense Department]. Instead, since 9/11, the scramble of the Langley fighters has been described as a response to the reported hijacking of American 77, or United 93, or some combination of the two.” Yet the “report of American 11 heading south as the cause of the Langley scramble is reflected not just in taped conversations at NEADS, but in taped conversations at FAA centers, on chat logs compiled at NEADS, Continental Region headquarters, and NORAD, and in other records.” [9/11 Commission, 6/17/2004; Vanity Fair, 8/1/2006]

Entity Tags: Northeast Air Defense Sector, Robert Marr, Kevin Nasypany

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Alan Scott.Alan Scott. [Source: United States Air Force]NORAD’s Northeast Air Defense Sector (NEADS) processes and transmits an order to Langley Air Force Base in Virginia, to scramble three of its F-16 fighter jets. [North American Aerospace Defense Command, 9/18/2001; Christian Science Monitor, 4/16/2002; 9/11 Commission, 8/26/2004, pp. 16] NEADS mission crew commander Major Kevin Nasypany instructed his personnel to issue this order one minute earlier (see 9:23 a.m. September 11, 2001). Although he’d originally wanted the Langley jets sent to the Washington area, he will soon adjust this heading to send them to the Baltimore area. [9/11 Commission, 7/24/2004, pp. 27]
NEADS Orders Jets North - A NEADS officer calls Langley Air Force Base and instructs: “Langley command post, this is Huntress with an active air defense scramble for Quit 2-5 and Quit 2-6.… Scramble immediately.… Scramble on a heading of 010, flight level 290.” This means the jets are to head in a direction just east of north, at an altitude of 29,000 feet. [9/11 Commission, 1/9/2004; 9/11 Commission, 8/26/2004, pp. 96; Spencer, 2008, pp. 142] At Langley Air Force Base, a Klaxon horn will sound, notifying the pilots of the scramble order (see 9:24 a.m. September 11, 2001), and they will be airborne by 9:30 (see (9:25 a.m.-9:30 a.m.) September 11, 2001). [Filson, 2003, pp. 63; 9/11 Commission, 8/26/2004, pp. 16; Spencer, 2008, pp. 141]
Fighters Launched in Response to Flight 77? - In later testimony, military officials will give contradictory explanations for why the Langley F-16s are scrambled. An early NORAD timeline will indicate the fighters are launched in response to NORAD being notified at 9:24 that Flight 77 has been hijacked (see (9:24 a.m.) September 11, 2001). [North American Aerospace Defense Command, 9/18/2001] Colonel Alan Scott, the former vice commander of the Continental US NORAD Region (CONR), will suggest the same, telling the 9/11 Commission: “At 9:24 the FAA reports a possible hijack of [Flight] 77.… And at that moment as well is when the Langley F-16s were scrambled out of Langley.” [9/11 Commission, 5/23/2003; 1st Air Force, 8/8/2006] And a timeline provided by senior Defense Department officials to CNN will state, “NORAD orders jets scrambled from Langley” in order to “head to intercept” Flight 77. [CNN, 9/17/2001]
In Response to Flight 93? - However, Major General Larry Arnold, the CONR commander, will give a different explanation. He will tell the 9/11 Commission, “we launched the aircraft out of Langley to put them over top of Washington, DC, not in response to American Airline 77, but really to put them in position in case United 93 were to head that way.” [9/11 Commission, 5/23/2003]
In Response to Incorrect Report about Flight 11? - In 2004, the 9/11 Commission will dispute both these previous explanations, and conclude that the Langley jets are scrambled in response to an incorrect report that Flight 11 is still airborne and heading toward Washington, DC (see 9:21 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 26-27; 9/11 Commission, 8/26/2004, pp. 15] Tape recordings of the NEADS operations floor will corroborate this account. [Vanity Fair, 8/1/2006] According to the 9/11 Commission, its conclusion is also confirmed by “taped conversations at FAA centers; contemporaneous logs compiled at NEADS, Continental Region headquarters, and NORAD; and other records.” [9/11 Commission, 7/24/2004, pp. 34] Major Nasypany will tell the Commission that the reason the Langley jets are directed toward the Baltimore area is to position them between the reportedly southbound Flight 11 and Washington, as a “barrier cap.” [9/11 Commission, 7/24/2004, pp. 27 and 461] John Farmer, senior counsel to the 9/11 Commission, will later suggest that NORAD deliberately misled Congress and the Commission by hiding the fact that the Langley scramble takes place in response to the erroneous report that Flight 11 is still airborne. He will write that the mistaken report “appears in more logs, and on more tapes, than any other single event that morning.… It was the reason for the Langley scramble; it had triggered the Air Threat Conference Call. Yet it had never been disclosed; it was, instead, talked around.” [Farmer, 2009, pp. 266-267]
Conflicting Times - Early news reports will put the time of the scramble order slightly later than the 9/11 Commission places it, between 9:25 and “about 9:27.” [Washington Post, 9/12/2001; CNN, 9/17/2001; CNN, 9/19/2001] But a NORAD timeline released a week after the attacks will give the same time as the Commission does, of 9:24. [North American Aerospace Defense Command, 9/18/2001; 9/11 Commission, 7/24/2004, pp. 27]

Entity Tags: 9/11 Commission, Kevin Nasypany, Alan Scott, Larry Arnold, North American Aerospace Defense Command, Langley Air Force Base, US Department of Defense, Northeast Air Defense Sector

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to the 9/11 Commission, by 9:30 a.m. American Airlines confirms that Flight 11 crashed into the World Trade Center. This is almost 45 minutes after the attack occurred. Earlier, at around 9:16, an American air traffic control specialist had only told the FAA that the airline “thought” the first plane to hit the WTC had been Flight 11 (see 9:16 a.m.-9:18 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 15-16] However, Colin Scoggins, a civilian manager at the FAA’s Boston Center, will later claim that American Airlines refused to confirm that its plane had hit the WTC for several hours afterwards. He will claim this lack of confirmation was a factor in his mistakenly reporting that Flight 11 was still airborne at 9:21 (see 9:21 a.m. September 11, 2001). He says, “When we phoned United [after the second tower was hit], they confirmed that United 175 was down, and I think they confirmed that within two or three minutes. With American Airlines, we could never confirm if it was down or not, so that left doubt in our minds.” [Vanity Fair, 8/1/2006] Yet American Airlines had the advantage over United that two of its flight attendants on Flight 11 had been in extensive contact by phone, up until a couple of minutes before their plane crashed. Amy Sweeney had been talking to Michael Woodward, a manager at the American Airlines flight services office at Boston’s Logan Airport (see 8:22 a.m.-8:24 a.m. September 11, 2001). And Betty Ong had been in contact with the airline’s Southeastern Reservations Office in North Carolina, with details of this call being continuously relayed to its System Operations Control (SOC) in Fort Worth, Texas (see 8:21 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 8-14]

Entity Tags: American Airlines

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

In answer to a question from a weapons controller at NORAD’s Northeast Air Defense Sector (NEADS), one of the pilots that took off in response to Flight 11 confirms that he would be willing to shoot down a hijacked aircraft. [Spencer, 2008, pp. 153] Major Kevin Nasypany, the NEADS mission crew commander, has already checked that his section heads and weapons technicians are prepared to order the shooting down of a civilian aircraft (see (9:19 a.m.) September 11, 2001). At 9:32, after NEADS received a report of a hijacked plane approaching Washington (see 9:21 a.m. September 11, 2001), Major James Anderson asked Nasypany what would happen if they located that aircraft, saying, “Are we gonna shoot him down if they got passengers on board?” [Vanity Fair, 8/1/2006]
Duffy Says He Would Shoot down a Plane - Nasypany wants to be sure that his pilots are willing to follow a shootdown order, should one be issued. He therefore directs his weapons controller who is dealing with the fighter jets launched from Otis Air National Guard Base (see 8:46 a.m. September 11, 2001) to check this. The weapons controller radios Otis pilot Lt. Col. Timothy Duffy and tells him, “If we get another hijack track, you’re going to be ordered to shoot it down.” He then asks, “Do you have a problem with that?” Somewhat startled by the question, Duffy replies, “No—no problem with that.” He reportedly thinks to himself, “If I have a problem with that order, I am in the wrong seat.” According to author Lynn Spencer, Duffy is “doing what he’s been trained to do.… [I]f he gets a legal, lawful order to take out an airliner, then that’s what he’s going to do. He knows every other fighter pilot would do the same.” Duffy and the other Otis pilot that launched with him, Major Daniel Nash, are “confident no plane will get past them: they’ll do what it takes, and follow any order, to protect New York.” [Spencer, 2008, pp. 153] Duffy will later tell the Boston Globe: “[P]eople have said, ‘Would you have done it [i.e. shot down a hostile airliner]?’ Absolutely, that’s my job.” [Boston Globe, 9/11/2005]
No Shootdown Order Issued - However, according to the 9/11 Commission, NEADS personnel will only learn that NORAD has been cleared to shoot down threatening aircraft at 10:31 a.m. (see 10:31 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 42] And, according to most accounts, the two Otis pilots never receive an order from the military to shoot down an airliner (see (After 9:35 a.m.) September 11, 2001). [Cape Cod Times, 8/21/2002; Boston Globe, 9/11/2005] Duffy and Nash will also be contacted by a civilian air traffic controller regarding the possibility of shooting down a hijacked aircraft (see (9:59 a.m.) September 11, 2001). [BBC, 9/1/2002]

Entity Tags: Daniel Nash, Northeast Air Defense Sector, Kevin Nasypany, Timothy Duffy

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Government buildings in Washington, DC, are not evacuated prior to the attack on the Pentagon at 9:37 a.m. As CNN will describe, even after the attacks on the World Trade Center and the FAA’s warning to the military of a hijacked aircraft apparently heading toward Washington (see 9:21 a.m. September 11, 2001 and (9:24 a.m.) September 11, 2001), “the federal government failed to make any move to evacuate the White House, Capitol, State Department, or the Pentagon.” [CNN, 9/16/2001] Although a slow evacuation of the White House begins around 9:20 a.m. (see (9:20 a.m.) September 11, 2001), it is not until 9:45 that the Secret Service orders people to run from there (see (9:45 a.m.) September 11, 2001). [CNN, 9/11/2001; CNN, 9/12/2001; ABC News, 9/11/2002] Other government buildings, including the Capitol (see 9:48 a.m. September 11, 2001), the Justice Department, the State Department, and the Supreme Court, will not be evacuated until between 9:45 and 10:45 a.m. [US News and World Report, 9/14/2001; US Department of State, 8/15/2002] Robert Bonner, who was recently nominated as Commissioner of Customs, will later estimate that he was evacuated from the Treasury Department at “about 9:35 a.m.” [9/11 Commission, 1/26/2004; US Department of Homeland Security, 9/20/2004] But other accounts say the Treasury Department is not evacuated until after the Pentagon attack. [Associated Press, 9/11/2001; Reuters, 9/11/2001; US Department of State, 9/11/2002] Furthermore, journalist and author Robert Draper will describe that, even after the State and Treasury departments have been evacuated: “no agents thought to take charge of the Commerce Department, which housed 5,000 employees. Eventually, Secretary [of Commerce] Don Evans got tired of waiting for orders and had someone drive him to his home in McLean, where he sat for hours until he finally made contact with the Secret Service.” [Draper, 2007, pp. 143] According to CNN, prior to the Pentagon attack, “neither the FAA, NORAD, nor any other federal government organ made any effort to evacuate the buildings in Washington. Officials at the Pentagon said that no mechanism existed within the US government to notify various departments and agencies under such circumstances [as occur on 9/11].” [CNN, 9/16/2001]

Entity Tags: Pentagon, US Supreme Court, Robert Bonner, US Department of Commerce, US Department of Justice, Federal Aviation Administration, US Department of the Treasury, US Department of State, White House, US Capitol building, Donald L. Evans

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Stacia Rountree.Stacia Rountree. [Source: Vanity Fair]Colin Scoggins, the military liaison at the FAA’s Boston Center, contacts NORAD’s Northeast Air Defense Sector (NEADS) and incorrectly notifies it that another aircraft, Delta Air Lines Flight 1989, is a possible hijacking. [9/11 Commission, 2004; Vanity Fair, 8/1/2006] Boston Center previously called NEADS at 9:27 and said that Delta 1989 was missing (see 9:27 a.m. September 11, 2001). [North American Aerospace Defense Command, 9/11/2001; 9/11 Commission, 5/23/2003]
NEADS Technicians Respond - At NEADS, Stacia Rountree, the ID technician who takes Scoggins’s call, announces to her colleagues: “Delta ‘89, that’s the hijack. They think it’s possible hijack.… South of Cleveland.” The plane’s transponder is still on, and she adds, “We have a code on him now.” Rountree’s team leader, Master Sergeant Maureen Dooley, instructs: “Pick it up! Find it!” The NEADS technicians quickly locate Delta 1989 on their radar screens, just south of Toledo, Ohio, and start alerting other FAA centers to it. [Vanity Fair, 8/1/2006; Spencer, 2008, pp. 177] NEADS mission crew commander Major Kevin Nasypany will be notified by his staff of the suspected hijacking at about 9:41 or 9:42 a.m. [9/11 Commission, 1/22/2004 pdf file] NEADS never loses track of Delta 1989. It will follow it on radar as it reverses course over Toledo, heads east, and then lands in Cleveland (see (10:18 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 28] It will order Air National Guard fighter jets from Selfridge and Toledo to intercept the flight (see (9:55 a.m.) September 11, 2001 and 10:01 a.m. September 11, 2001). [Spencer, 2008, pp. 178-179] But it will soon learn that Delta 1989 is not in fact hijacked. [9/11 Commission, 7/24/2004, pp. 28]
Cleveland Center, Not Boston, Handling Delta 1989 - Although Boston Center notifies NEADS of the suspected hijacking, Delta 1989 is in fact being handled by the FAA’s Cleveland Center. [USA Today, 8/13/2002; 9/11 Commission, 7/24/2004, pp. 10-12] Cleveland Center air traffic controllers suspected that Delta 1989 had been hijacked at around 9:30 a.m. (see (9:28 a.m.-9:33 a.m.) September 11, 2001), but apparently only informed the FAA’s Command Center, and not NEADS, of this. [USA Today, 8/13/2002] To explain why Boston Center alerts NEADS to the flight, the 9/11 Commission will later comment that, “Remembering the ‘we have some planes’ remark” (see 8:24 a.m. September 11, 2001), the Boston Center simply “guessed that Delta 1989 might also be hijacked.”
Similar to First Two Hijacked Planes - Like Flights 11 and 175, the two aircraft that have crashed into the World Trade Center (see 8:46 a.m. September 11, 2001 and 9:03 a.m. September 11, 2001), Delta 1989 took off from Boston’s Logan Airport. [9/11 Commission, 7/24/2004, pp. 27-28] According to the New York Times, it left there at about the same time as Flights 11 and 175 did, meaning around 8:00 to 8:15 a.m. [New York Times, 10/18/2001; 9/11 Commission, 7/24/2004, pp. 32] Like those two aircraft, it is a Boeing 767. [USA Today, 8/13/2002; 9/11 Commission, 7/24/2004, pp. 27-28] But, unlike those flights, its transponder has not been turned off, and so it is still transmitting a beacon code. [9/11 Commission, 7/24/2004, pp. 28; Vanity Fair, 8/1/2006] It is unclear what Delta 1989’s intended destination is. According to some accounts, like Flights 11 and 175 were, it is bound for Los Angeles. [Associated Press, 9/11/2001; New York Times, 10/18/2001; USA Today, 8/13/2002; Arizona Daily Star, 9/24/2007; Spencer, 2008, pp. 167] Other accounts will say that its destination is Las Vegas. [9/11 Commission, 7/24/2004, pp. 28; Vanity Fair, 8/1/2006] Personnel at NEADS are apparently informed that Las Vegas is the intended destination. Around this time, one member of staff there tells her colleagues that the flight is “supposed to go to Vegas.” [North American Aerospace Defense Command, 9/11/2001]
One of Numerous Incorrect Reports - The 9/11 Commission will comment: “During the course of the morning, there were multiple erroneous reports of hijacked aircraft (see (9:09 a.m. and After) September 11, 2001). The report of American 11 heading south was the first (see 9:21 a.m. September 11, 2001); Delta 1989 was the second.” [9/11 Commission, 7/24/2004, pp. 28]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

Entity Tags: Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

Entity Tags: North American Aerospace Defense Command

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The 9/11 Commission holds a public hearing at which it takes testimony from military officials about the timeline of events on the day of 9/11. The key witness is retired Air Force General Larry Arnold, who commanded NORAD’s Continental US Region on the day of 9/11. Under questioning from commissioner Richard Ben-Veniste, Arnold says, “I believe that to be a fact: that 9:24 was the first time that we had been advised of American 77 as a possible hijacked airplane.” However, the Commission will later conclude that the military was not notified of the hijacking at this time, although it had been mistakenly advised Flight 11 was inbound to Washington three minutes previously (see 9:21 a.m. September 11, 2001 and (9:24 a.m.) September 11, 2001). Arnold adds that if the military was slow in responding to Flight 77, it was because “our focus—you have got to remember that there’s a lot of other things going on simultaneously here—was on United 93.” However, Flight 93 was not hijacked until a few minutes after 9:24 (see (9:28 a.m.) September 11, 2001). Arnold adds: “It was our intent to intercept United Flight 93. And in fact, my own staff, we were orbiting now over Washington, DC, by this time, and I was personally anxious to see what 93 was going to do, and our intent was to intercept it.” However, the Commission will later conclude that the military did not learn that Flight 93 had been hijacked until around 10:00 a.m. (see 10:03 a.m. September 11, 2001). Prior to the hearing, the Commission’s staff had been concerned about the inaccuracy of timelines offered by the military. Author Philip Shenon will write: “It seemed all the more remarkable to [Commission staffer John Farmer] that the Pentagon could not establish a clear chronology of how it responded to an attack on the Pentagon building itself. Wouldn’t the generals and admirals want to know why their own offices—their own lives—had been put at risk that morning?” Therefore, Farmer thought that the hearing should clear things up, but, according to Shenon, he and his colleagues are “astonished” when they analyze what Arnold says, although he is not under oath on this day. Shenon will add, “It would later be determined that almost every one of those assertions by General Arnold in May 2003 was flat wrong.” [Shenon, 2008, pp. 119-121]

Entity Tags: John Farmer, 9/11 Commission, Philip Shenon, Richard Ben-Veniste, Larry Arnold

Timeline Tags: Complete 911 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