!! History Commons Alert, Exciting News

Context of '10:05 a.m.-10:08 a.m. September 11, 2001: NEADS Alerted to Flight 93, Reportedly for the First Time'

This is a scalable context timeline. It contains events related to the event 10:05 a.m.-10:08 a.m. September 11, 2001: NEADS Alerted to Flight 93, Reportedly for the First Time. You can narrow or broaden the context of this timeline by adjusting the zoom level. The lower the scale, the more relevant the items on average will be, while the higher the scale, the less relevant the items, on average, will be.

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

Jeff Ford.Jeff Ford. [Source: Thomas Doscher / US Air Force]Personnel in NORAD’s operations center in Cheyenne Mountain, Colorado, take part in a major Cold War-style training exercise called Vigilant Guardian, a war game in which the theoretical enemy is Russia. [9/11 Commission, 3/1/2004 pdf file; Denver Post, 8/28/2011; Colorado Springs Gazette, 9/10/2011] All of NORAD, including its subordinate units (see (6:30 a.m.) September 11, 2001), participates in the exercise. [Northeast Air Defense Sector, 8/23/2001; Canadian Broadcasting Corporation, 9/8/2011] More than 50 people in the NORAD Battle Management Center in Cheyenne Mountain take part. [Airman, 3/2002; Defense Video and Imagery Distribution System, 9/8/2011] Vigilant Guardian is an annual exercise and is scheduled to last two weeks. [Arkin, 2005, pp. 545; Canadian Broadcasting Corporation, 9/8/2011] It has been underway for several days. Those in the Cheyenne Mountain Operations Center (CMOC) have been participating in it “for at least three or four days,” according to Lieutenant Colonel Steven Armstrong, NORAD’s chief of plans and forces. [North American Aerospace Defense Command, 9/9/2011]
Vigilant Guardian Is a 'Full-Blown Nuclear War' Exercise - Vigilant Guardian is a “transition to wartime operations command post exercise,” according to an information page for its participants. [Northeast Air Defense Sector, 8/23/2001] The 1st Air Force’s book about 9/11 will describe it as a “simulated air war.” [Filson, 2003, pp. 55] Lieutenant Colonel William Glover, the commander of NORAD’s Air Warning Center, will later recall that it involves NORAD “simulating war.… You know, attacks coming from the outside, Soviet-style bombers coming in, cruise-missile attacks, that type of thing.” [Canadian Broadcasting Corporation, 9/8/2011] Ken Merchant, NORAD’s joint exercise design manager, will tell the 9/11 Commission that Vigilant Guardian is a “full-blown nuclear war” exercise, and includes bomber response and intercontinental ballistic missile response. [9/11 Commission, 3/4/2004]
Russia Is Imagined Enemy - The theoretical enemy in the exercise is Russia. [Denver Post, 8/28/2011] According to the 9/11 Commission Report, the exercise “postulated a bomber attack from the former Soviet Union.” [9/11 Commission, 7/24/2004, pp. 458] Merchant will explain that “NORAD must use Russia in its exercises at the strategic level since no other country poses a great enough threat to NORAD’s capabilities and responsibilities.” [9/11 Commission, 3/4/2004]
Personnel Updated on Exercise during Shift Change - Armstrong will later recall that today starts off “like any other day. We came in thinking it would be a normal day… we did a standard shift changeover in the morning and we were getting right into where we were at in relation to the exercise.” He will describe that in a shift change during the exercise, “We’d say, ‘Okay, here’s what happened during the night shift (or the day shift),’ and we’d give each other an update, and then we’d start planning for whatever was on the agenda for that day.” [North American Aerospace Defense Command, 9/9/2011] According to the Denver Post, after commencing his shift, Armstrong “mapped out strategy in a chess game of ever-escalating scenarios, from strained diplomacy to the outbreak of conventional warfare that headed inexorably toward nuclear conflict” with Russia. [Denver Post, 8/28/2011]
B-1 Bomber Scheduled to Fly out over Pacific Ocean - The “planned big event for the day” in the exercise is “supposed to be a B-1 bomber that was flying out of Fairchild Air Force Base [in Washington State] and going out over the Pacific,” according to Jeff Ford, an Air Force lieutenant colonel who is working in the CMOC. Ford will add that there are “other things going on as part of the exercise, air exercise events, and then some scripted inputs that we were reacting to there in the Air Warning Center, whether it be unknown aircraft that we scramble aircraft for to intercept—or whatever.” [Defense Video and Imagery Distribution System, 9/8/2011]
Exercise Posture Allegedly Helps Response to Attacks - Vigilant Guardian will reportedly end after 9:03 a.m., when the second plane hits the World Trade Center (see (Shortly After 9:03 a.m.) September 11, 2001), and the CMOC personnel participating in it will then become involved in responding to the real-world attacks. [Airman, 3/2002; Toronto Star, 11/11/2008] Glover will claim that the CMOC’s response to the terrorist attacks benefits from the position the operations center is in for the exercise. He will say NORAD is “lucky” because “all the directorates such as operations, logistics, security, all those folks were up in the [Cheyenne] Mountain on an exercise posture.” He will add that “these are the same folks that we would bring up in case of contingencies or in time of going to war. So, in reality, I had all the guys up into the NORAD Battle Management Center that I needed to conduct the exercise as well as the contingency operations that happened on 9/11.” [Defense Video and Imagery Distribution System, 9/8/2011]
NORAD Monitoring Russian Exercise - NORAD was created in 1958, during the Cold War, to protect North American airspace against nuclear attacks from the Soviet Union. [New York Times, 4/25/2004; Canadian Broadcasting Corporation, 8/6/2004; Legion Magazine, 11/2004] According to the Toronto Star, “Whether it’s a simulation or a real-world event, the role of the [CMOC] is to fuse every critical piece of information NORAD has into a concise and crystalline snapshot.” [Toronto Star, 12/9/2001] As well as the Vigilant Guardian exercise, NORAD is currently in the middle of an operation called Northern Vigilance, with its fighter jets deployed to Alaska and Northern Canada to monitor an exercise being run by the Russian Air Force (see September 9, 2001). [North American Aerospace Defense Command, 9/9/2001] The battle staff members in Cheyenne Mountain are positioned to deal with both this operation and the exercise. [9/11 Commission, 3/1/2004 pdf file]

Entity Tags: Jeff Ford, North American Aerospace Defense Command, Steven Armstrong, Vigilant Guardian, William Glover, Ken Merchant

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Pete Zalewski.Pete Zalewski. [Source: NBC]Because the talkback button on Flight 11 has been activated, Boston Center air traffic controllers can hear a hijacker on board say to the passengers: “We have some planes. Just stay quiet and you’ll be OK. We are returning to the airport.” [Boston Globe, 11/23/2001; 9/11 Commission, 7/24/2004, pp. 19] Air traffic controller Pete Zalewski recognizes this as a foreign, Middle Eastern-sounding voice, but does not make out the specific words “we have some planes.” He responds, “Who’s trying to call me?” Seconds later, in the next transmission, the hijacker continues: “Nobody move. Everything will be OK. If you try to make any moves you’ll endanger yourself and the airplane. Just stay quiet.” [New York Times, 10/16/2001; 9/11 Commission, 6/17/2004; MSNBC, 9/9/2006] Bill Peacock, the FAA director of air traffic services, later claims, “We didn’t know where the transmission came from, what was said and who said it.” David Canoles, the FAA’s manager of air traffic evaluations and investigations, adds: “The broadcast wasn’t attributed to a flight. Nobody gave a flight number.” [Washington Times, 9/11/2002] Similarly, an early FAA report will state that both these transmissions came from “an unknown origin.” [Federal Aviation Administration, 9/17/2001 pdf file] Zalewski asks for an assistant to help listen to the transmissions coming from the plane, and puts its frequency on speakers so others at Boston Center can hear. Because Zalewski didn’t understand the initial hijacker communication from Flight 11, the manager of Boston Center instructs the center’s quality assurance specialist to “pull the tape” of the transmission, listen to it carefully, and then report back. They do this, and by about 9:03 a.m. a Boston manager will report having deciphered what was said in the first hijacker transmission (see 9:03 a.m. September 11, 2001). [9/11 Commission, 6/17/2004; MSNBC, 9/9/2006] Fellow Boston controller Don Jeffroy also hears the tape of the hijacker transmissions, though he doesn’t state at what time. He says: “I heard exactly what Pete [Zalewski] heard. And we had to actually listen to it a couple of times just to make sure that we were hearing what we heard.” [MSNBC, 9/11/2002] At some point, Ben Sliney, the national operations manager at the FAA’s Herndon Command Center, gets word of the “We have some planes” message, and later says the phrase haunts him all morning. American Airlines Executive Vice President for Operations Gerard Arpey is also informed of the “strange transmissions from Flight 11” at some point prior to when it crashes at 8:46 a.m. [USA Today, 8/12/2002] Boston Center will receive a third transmission from Flight 11 about ten minutes later (see (8:34 a.m.) September 11, 2001).

Entity Tags: Bill Peacock, Boston Air Route Traffic Control Center, David Canoles, Pete Zalewski

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

NASA’s KC-135 in parabolic flight.NASA’s KC-135 in parabolic flight. [Source: NASA]A special aircraft operated by NASA is in the air over western New York State at the time of the terrorist attacks and, at one point, a large aircraft, which those on board later learn is the hijacked Flight 93, flies less than 1,000 feet below it. [Space Center Roundup, 9/2002 pdf file] The plane, NASA 931, is a modified KC-135—a four-engine military aircraft similar to the Boeing 707. [National Aeronautics and Space Administration, 10/2000, pp. 28; National Aeronautics and Space Administration, 10/29/2004] It is used by NASA for reduced gravity research, and is known as the “Weightless Wonder” or sometimes the “Vomit Comet.” The aircraft creates weightless conditions for brief periods by flying up and down in large parabolic arcs. [NASAexplores, 1/30/2003] It is regularly operated from NASA’s Glenn Research Center in Cleveland, Ohio, next to Cleveland Hopkins International Airport, and usually flies four days a week. [National Aeronautics and Space Administration, 10/2000, pp. 140; National Journal's Technology Daily, 11/27/2002; National Aeronautics and Space Administration, 10/29/2004] A typical flight lasts two to three hours and consists of the plane flying 40 to 60 parabolas. [NASAexplores, 1/30/2003]
Scientists from Houston Conducting Microgravity Experiments - A team of scientists from NASA’s Johnson Space Center in Houston, Texas, has flown to Cleveland to conduct microgravity experiments on the KC-135. [Cleveland Free Times, 9/6/2006] Dominic Del Rosso, the test director on the plane, will later recall that the team is flying over western New York State when the terrorist attacks occur. During the routine mission, the KC-135 cruises back and forth along the New York shore of Lake Ontario, climbing and descending to create a freefall condition to simulate microgravity. Del Rosso will comment, “To think that this type of maneuver might ever seem threatening never crossed my mind until [September 11].” The plane’s crew members are notified at some point that a large plane is intersecting their flight path less than 1,000 feet below them, instead of the usual 2,000-foot minimum distance. They will later learn that this aircraft is the hijacked Flight 93, which crashes in Pennsylvania (see (10:06 a.m.) September 11, 2001). Del Rosso will recall, “After the unwanted flyby, we landed having no idea why or what was going on.” [Space Center Roundup, 9/2002 pdf file] The scientists are unable to return to Houston on this day, as scheduled, after the FAA orders all planes to land (see (9:45 a.m.) September 11, 2001), and so have to be put up in a hotel in Cleveland. [Cleveland Free Times, 9/6/2006]

Entity Tags: National Aeronautics and Space Administration, Dominic Del Rosso

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Tech. Sgt. Jeremy Powell.Tech. Sgt. Jeremy Powell. [Source: Scott A. Gwilt/ Rome Sentinel]The FAA’s Boston Center calls NORAD’s Northeast Air Defense Sector (NEADS) in Rome, NY, to alert it to the suspected hijacking of Flight 11. According to the 9/11 Commission, this is “the first notification received by the military—at any level—that American 11 had been hijacked.” [9/11 Commission, 7/24/2004, pp. 20; 9/11 Commission, 8/26/2004, pp. 13] The call is made by Joseph Cooper, an air traffic controller at the Boston Center, and answered by Jeremy Powell, a technical sergeant on the NEADS operations floor. [Vanity Fair, 8/1/2006; Spencer, 2008, pp. 25] Beginning the call, Cooper says: “Hi. Boston Center TMU [traffic management unit], we have a problem here. We have a hijacked aircraft headed towards New York, and we need you guys to, we need someone to scramble some F-16s or something up there, help us out.” Powell replies, “Is this real-world or exercise?” Cooper answers, “No, this is not an exercise, not a test.” [9/11 Commission, 7/24/2004, pp. 20] Shortly into the call, Powell passes the phone on to Lieutenant Colonel Dawne Deskins (see (8:38 a.m.) September 11, 2001). Deskins identifies herself to Cooper, and he tells her, “We have a hijacked aircraft and I need you to get some sort of fighters out here to help us out.” [Newhouse News Service, 1/25/2002; ABC News, 9/11/2002; Bamford, 2004, pp. 8; Spencer, 2008, pp. 26]
Military Claims Call Goes against Procedure - The 1st Air Force’s official history of the response to the 9/11 attacks will later suggest that Boston Center is not following normal procedures when it makes this call to NEADS. It states: “If normal procedures had taken place… Powell probably wouldn’t have taken that phone call. Normally, the FAA would have contacted officials at the Pentagon’s National Military Command Center who would have contacted the North American Aerospace Defense Command. The secretary of defense would have had to approve the use of military assets to assist in a hijacking, always considered a law enforcement issue.” The only explanation it gives for this departure from protocol is that “nothing was normal on Sept. 11, 2001, and many say the traditional chain of command went by the wayside to get the job done.” [Filson, 2003, pp. 51]
Accounts Conflict over Time of Call - There will be some conflict between different accounts, as to when this vital call from Boston Center to NEADS occurs. An ABC News documentary will indicate it is made as early as 8:31 a.m. [ABC News, 9/11/2002] Another ABC News report will state, “Shortly after 8:30 a.m., behind the scenes, word of a possible hijacking [reaches] various stations of NORAD.” [ABC News, 9/14/2002] NEADS logs indicate the call occurs at 8:40 a.m., and NORAD will report this as the time of the call in a press release on September 18, 2001. [Federal Aviation Administration, 9/17/2001 pdf file; North American Aerospace Defense Command, 9/18/2001] The 8:40 time will be widely reported in the media prior to the 9/11 Commission’s 2004 report. [Associated Press, 8/21/2002; BBC, 9/1/2002; Newsday, 9/10/2002; CNN, 9/11/2002] But tape recordings of the NEADS operations floor that are referred to in the 9/11 Commission Report place the call at 8:37 and 52 seconds. [9/11 Commission, 7/24/2004, pp. 20; Vanity Fair, 8/1/2006] If the 8:37 a.m. time is correct, this would mean that air traffic controllers have failed to successfully notify the military until approximately 12 minutes after they became certain that Flight 11 had been hijacked (see (8:25 a.m.) September 11, 2001), 16 minutes after Flight 11’s transponder signal was lost (see (Between 8:13 a.m. and 8:21 a.m.) September 11, 2001), and 24 minutes after the plane’s pilots made their last radio contact (see 8:13 a.m. September 11, 2001). [9/11 Commission, 6/17/2004] At 8:34, the Boston Center tried contacting the military through the FAA’s Cape Cod facility, which is located on Otis Air National Guard Base, but was told that it needed to call NEADS (see 8:34 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20; Spencer, 2008, pp. 22]

Entity Tags: Boston Air Route Traffic Control Center, Dawne Deskins, North American Aerospace Defense Command, Joseph Cooper, Northeast Air Defense Sector, Jeremy Powell

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The hole caused by the Flight 11 crash.The hole caused by the Flight 11 crash. [Source: Reuters]Flight 11 slams into the WTC North Tower (Building 1). Hijackers Mohamed Atta Waleed Alshehri, Wail Alshehri, Abdulaziz Alomari, and Satam Al Suqami presumably are killed instantly, and many more in the tower will die over the next few hours. Seismic records pinpoint the crash at 26 seconds after 8:46 a.m. [CNN, 9/12/2001; New York Times, 9/12/2001; North American Aerospace Defense Command, 9/18/2001; USA Today, 12/20/2001; Federal Emergency Management Agency, 5/1/2002, pp. 1-10; New York Times, 5/26/2002; USA Today, 8/12/2002; Associated Press, 8/21/2002; Newsday, 9/10/2002] The NIST report states the crash time to be 8:46:30. [National Institute of Standards and Technology, 9/2005, pp. 19] The 9/11 Commission Report states the crash time to be 8:46:40. [9/11 Commission, 7/24/2004, pp. 7] Investigators believe the plane still has about 10,000 gallons of fuel (see 8:57 a.m. September 11, 2001). [New York Times, 5/26/2002] The plane strikes the 93rd through 99th floors in the 110-story building. No one above the crash line survives; approximately 1,360 people die. Below the crash line, approximately 72 die and more than 4,000 survive. Both towers are slightly less than half full at the time of the attack, with between 5,000 to 7,000 people in each tower. This number is lower than expected. Many office workers have not yet shown up to work, and tourists to the observation deck opening at 9:30 A.M. have yet to arrive. [USA Today, 12/20/2001; National Institute of Standards and Technology, 9/2005, pp. 20-22] The impact severs some columns on the north side of the North Tower. Each tower is designed as a “tube-in-tube” structure and the steel columns which support its weight are arranged around the perimeter and in the core. The plane, which weighs 283,600 lb and is traveling at an estimated speed of around 430 mph (see October 2002-October 2005), severs 35 of the building’s 236 perimeter columns and damages another two. The damage to the South Tower’s perimeter will be similar (see 9:03 a.m. September 11, 2001). [National Institute of Standards and Technology, 9/2005, pp. 5-9, 20, 22] The perimeter columns bear about half of the tower’s weight, so this damage reduces its ability to bear gravity loads by about 7.5 percent. [National Institute of Standards and Technology, 9/2005, pp. 6] The actual damage to the 47 core columns is not known, as there are no photographs or videos of it, but there will be much speculation about this after 9/11. It will be suggested that some parts of the aircraft may have damaged the core even after crashing through the exterior wall. According to the National Institute of Standards and Technology (NIST): “Moving at 500 mph, an engine broke any exterior column it hit. If the engine missed the floor slab, the majority of the engine core remained intact and had enough residual momentum to sever a core column upon direct impact.” [National Institute of Standards and Technology, 9/2005, pp. 107] According to NIST’s base case computer model, three of the core columns are severed and another ten suffer some damage. [National Institute of Standards & Technology, 9/2005, pp. 189 pdf file] If this is accurate, it means that the impact damage to the core reduces the Tower’s strength by another approximately 7.5 percent, meaning that the building loses about 15 percent of its strength in total. This damage will be cited after 9/11 by NIST and others researchers as an event contributing to the building’s collapse (see October 23, 2002 and October 19, 2004). In addition, some of the fireproofing on the steel columns and trusses may be dislodged. The original fireproofing on the fire floors was mostly Blazeshield DC/F, but some of the fireproofing on the flooring has recently been upgraded to Blazeshield II, which is about 20 percent denser and 20 percent more adhesive. [National Institute of Standards & Technology, 9/2005, pp. xxxvi, 83 pdf file] Photographs and videos of the towers will not show the state of fireproofing inside the buildings, but NIST will estimate the damage to it using a computer model. Its severe case model (see (October 2002-October 2005)) will predict that 43 of the 47 core columns are stripped of their fireproofing on one or more floors and that fireproofing is stripped from trusses covering 60,000 ft2 of floor area, the equivalent of about one and a half floors. NIST will say that the loss of fireproofing is a major cause of the collapse (see April 5, 2005), but only performs 15 tests on fireproofing samples (see October 26, 2005). [National Institute of Standards and Technology, 9/2005, pp. 23] According to NIST, more fireproofing is stripped from the South Tower (see 9:03 a.m. September 11, 2001).

Entity Tags: Mohamed Atta, National Institute of Standards and Technology, Satam Al Suqami, Waleed Alshehri, Abdulaziz Alomari, World Trade Center, Wail Alshehri

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

A typical F-15.A typical F-15. [Source: US Air Force]Radar data will show that the two F-15s scrambled from Otis Air National Guard Base in Cape Cod, Massachusetts, are airborne by this time. [Washington Post, 9/15/2001; North American Aerospace Defense Command, 9/18/2001; 9/11 Commission, 7/24/2004, pp. 20] It is now eight minutes since the mission crew commander at NORAD’s Northeast Air Defense Sector (NEADS) ordered that the jets be launched (see 8:45 a.m. September 11, 2001). [Vanity Fair, 8/1/2006] It is 40 minutes since air traffic controllers had their last communication with Flight 11 (see 8:13 a.m. September 11, 2001), and 28 minutes since they became certain that the aircraft was hijacked (see (8:25 a.m.) September 11, 2001). Flight 11 crashed into the World Trade Center seven minutes ago (see 8:46 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 7, 19 and 459]
Commander Wants Fighters Sent to New York - In Rome, New York, NEADS has just received news of the plane hitting the WTC (see 8:51 a.m. September 11, 2001). Major Kevin Nasypany, the facility’s mission crew commander, is asked what to do with the Otis fighters. He responds: “Send ‘em to New York City still. Continue! Go! This is what I got. Possible news that a 737 just hit the World Trade Center. This is a real-world.… Continue taking the fighters down to the New York City area, JFK [International Airport] area, if you can. Make sure that the FAA clears it—your route all the way through.… Let’s press with this.” [Vanity Fair, 8/1/2006] Yet there will be conflicting reports of the fighters’ destination (see (8:53 a.m.-9:05 a.m.) September 11, 2001), with some accounts saying they are directed toward military-controlled airspace off the Long Island coast. [Filson, 2003, pp. 56-59; 9/11 Commission, 6/17/2004]

Entity Tags: Northeast Air Defense Sector, Robert Marr, Kevin Nasypany, Otis Air National Guard Base

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

In the NORAD operations center in Cheyenne Mountain, Colorado, workers see the second aircraft crashing into the World Trade Center live on television. [Gazette (Colorado Springs), 10/7/2001] Major General Rick Findley, NORAD’s director of operations, later says that he now realizes “it was not an accident but a coordinated attack.” Then, he recalls, “At about that moment in time, every phone in this cab, and every phone over in the command center, and every phone in all the centers in this building were ringing off the hook.” Master Corporal Daniel Milne, the emergency action controller in the operations center, will similarly recall, “The feeling was total disbelief. Then the phones started ringing like crazy.” [Canadian Broadcasting Corporation, 9/11/2002; Legion Magazine, 11/2004] It is unclear what causes all the phones to simultaneously ring. According to Aviation Week and Space Technology magazine, after the second tower is hit, “Calls from fighter units… started pouring into NORAD and sector operations centers, asking, ‘What can we do to help?’” (see (After 9:03 a.m.) September 11, 2001) [Aviation Week and Space Technology, 6/3/2002] So this could be one factor. Also, a 1996 article in Airman magazine had quoted Stacey Knott, a technician in the NORAD operations center. She’d said, “Things can be pretty quiet in here.” However, “One of the busiest times is during exercises. This room fills up.… The phones are ringing off the hook, and I’ve got phones in each hand.” [Airman, 1/1996] On this morning, those in Cheyenne Mountain are in fact participating in a major exercise called Vigilant Guardian. [Aviation Week and Space Technology, 6/3/2002; CNN, 9/11/2006] This is reportedly only canceled “shortly after” the second attack (see (Shortly After 9:03 a.m.) September 11, 2001) [Airman, 3/2002; Filson, 2003, pp. 59] So it is plausible that this is also a factor in causing all the phones to suddenly ring. A similar thing appears to occur in the National Military Command Center (NMCC) at the Pentagon. According to a news article based on the recollections of two officers who are there, after the second plane hits the WTC, “Phones in the center began ringing off the hook.” [American Forces Press Service, 9/7/2006] Rick Findley later suggests that all the ringing phones are not a hindrance for NORAD, claiming, “The good news is we had lots of people here and we already had an operational architecture. We already had the command and control, the network, the phones, the data links. Everything was already in place that enabled us to react to the situation.” [Canadian Broadcasting Corporation, 9/11/2002]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

A technician at NORAD’s Northeast Air Defense Sector (NEADS) tells a caller that the day’s training exercise has not yet been called off, despite the attacks in New York. [North American Aerospace Defense Command, 9/11/2001] All of NORAD, including NEADS, has been participating in a major exercise called Vigilant Guardian this morning (see (6:30 a.m.) September 11, 2001). [Aviation Week and Space Technology, 6/3/2002; Arkin, 2005, pp. 545] According to some accounts, 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] However, Sergeant Mark Jennings, a NEADS tracking technician, now answers a phone call, and the caller says he has been watching the coverage of the terrorist attacks on television “for about 10 minutes, and I said, ‘I wonder if they’re—did they suspend the exercise?’” Jennings informs the caller that the exercise has not yet been suspended, answering, “Not at this time, no.” He adds: “But I think they’re going to [suspend it]. I don’t know. Things look pretty horrific out there.” The caller acknowledges, “Alrighty, man.” [North American Aerospace Defense Command, 9/11/2001]

Entity Tags: North American Aerospace Defense Command, Northeast Air Defense Sector, Mark Jennings, Vigilant Guardian

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Major Brad Derrig.Major Brad Derrig. [Source: ABC]At Langley Air Force Base in Virginia, the pilots of three F-16s receive the order to scramble (i.e. take off immediately). A Klaxon horn sounds and the status lights in the hangars change from yellow to green, notifying them of the order. [Longman, 2002, pp. 65; Filson, 2003, pp. 63; Spencer, 2008, pp. 141] The fighter jets belong to the North Dakota Air National Guard’s 119th Fighter Wing. The wing has a small detachment at Langley that serves as one of NORAD’s seven “alert” sites around the US, responsible for defending the nation against attack. [Spencer, 2008, pp. 114] The jets are already at “battle stations,” with the pilots in the cockpits but the engines off (see (9:09 a.m.) September 11, 2001). [Filson, 2003, pp. 55; 9/11 Commission, 7/24/2004, pp. 24; Spencer, 2008, pp. 117-119] The scramble order has just been issued by NORAD’s Northeast Air Defense Sector (NEADS) (see 9:24 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 16]
Third Pilot Launched - The unit at Langley keeps two F-16s on “alert”—armed, fueled, and ready to take off within minutes if called upon. [Air Force Magazine, 2/2002; Bergen Record, 12/5/2003; 9/11 Commission, 7/24/2004, pp. 17] But NEADS has instructed it to launch as many aircraft as it can (see (Between 9:10 a.m. and 9:23 a.m.) September 11, 2001), and so the unit’s operations manager Captain Craig Borgstrom is also preparing to take off in a third jet. [Spencer, 2008, pp. 118-119] Major Dean Eckmann calls the other two pilots, saying, “Quit check,” indicating a radio check. Major Brad Derrig responds, “Two.” Borgstrom replies: “Three. I’m going with you!” This is news to Derrig. According to author Lynn Spencer, Derrig is “stunned.… [N]ot much surprises him, but this does.” Borgstrom joining them as a pilot will mean that, in the middle of this unprecedented crisis, their unit will be left without a commanding officer. [Spencer, 2008, pp. 142]
Only Two Jets Fully Armed - The two jets that are kept on alert are fully armed. As Eckmann will later recall, “We can carry M9 heat seekers, Sidewinders for the M7 Sparrow, plus we have an internal 20 mm Vulcan cannon, and we were pretty much armed with all that.” [BBC, 9/1/2002] However, Borgstrom’s jet has guns only, and though the six-barrel 20 mm gun can fire 6,000 rounds per minute, it requires close range.
Pilot Unqualified to Lead Three Jets - As the three aircraft taxi out to the runway, Eckmann is concerned that he has not yet qualified as a mission commander—a “four-ship”—and is therefore not authorized to lead more than one fighter jet. He calls the other pilots, saying, “Hey, I’m only a two-ship!” But Derrig, who is a full-time instructor pilot for the Air National Guard, urges him not to worry. He responds: “Press! I’m an instructor,” giving his approval for the flight to operate as a “three-ship” under Eckmann’s lead. [Spencer, 2008, pp. 142] The three jets will take off and be airborne by 9:30 a.m. (see (9:25 a.m.-9:30 a.m.) September 11, 2001). [9/11 Commission, 8/26/2004, pp. 16]

Entity Tags: Brad Derrig, 119th Fighter Wing, Craig Borgstrom, Dean Eckmann, Langley Air Force Base

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Captain Craig Borgstrom.Captain Craig Borgstrom. [Source: US Air Force / Austin Knox]The three F-16 fighter jets ordered to scramble from Langley Air Force Base in Virginia (see 9:24 a.m. September 11, 2001) take off and, radar data will show, are airborne by 9:30 a.m. [North American Aerospace Defense Command, 9/18/2001; Christian Science Monitor, 4/16/2002; 9/11 Commission, 7/24/2004, pp. 27]
Delayed during Launch - Major Dean Eckmann will recall that, after receiving the scramble order, he and the two other pilots have “a pretty quick response time. I believe it was four to five minutes we were airborne from that point.” [BBC, 9/1/2002] According to the 1st Air Force’s book about 9/11, the three fighters are “given highest priority over all other air traffic at Langley Air Force Base” as they are launching. [Filson, 2003, pp. 63] But, according to author Lynn Spencer, in spite of this, the jets are delayed. As Eckmann is approaching the runway, he calls the control tower for clearance to take off, but the tower controller tells him, “Hold for an air traffic delay.” Air traffic controllers at the FAA’s Washington Center “have not had time to clear airliners out of the way for the northerly heading. Dozens of aircraft at various altitudes fill the jets’ route.” After having to wait two minutes, Eckmann complains: “We’re an active air scramble. We need to go now!” Finally, the tower controller tells him, “Roger, Quit flight is cleared for takeoff, 090 for 60,” meaning the fighters are to fly due east for 60 miles (see (9:30 a.m.) September 11, 2001).
Taking Off - The three jets launch 15 seconds apart, with Eckmann in front and the two other jets following. [Spencer, 2008, pp. 143-144] Pilot Craig Borgstrom will later recall, “[W]e took off, the three of us, and basically the formation we always brief on alert, we’ll stay in a two- to three-mile trail from the guy in front.” [Filson, 2003, pp. 63] According to the BBC, the pilots get a signal over their planes’ transponders, indicating an emergency wartime situation. [BBC, 9/1/2002]
Could Reach Washington before Pentagon Attack - F-16s have a maximum speed of 1,500 mph at high altitude, or 915 mph at sea level, so the three fighters could plausibly travel the 130 miles from Langley Air Force Base to Washington in just minutes. [Chant, 1987, pp. 404; Associated Press, 6/16/2000; USA Today, 9/16/2001; Washington Post, 9/16/2001 pdf file; US Air Force, 10/2007] Major General Larry Arnold, the commanding general of NORAD’s Continental US Region, will tell the 9/11 Commission, “I think if those aircraft had gotten airborne immediately, if we were operating under something other than peacetime rules, where they could have turned immediately toward Washington, DC, and gone into burner, it is physically possible that they could have gotten over Washington” before 9:37, when the Pentagon is hit. [9/11 Commission, 5/23/2003] Yet according to the 9/11 Commission, the jets are redirected east over the Atlantic Ocean and will be 150 miles from the Pentagon when it is hit (see 9:30 a.m.-9:37 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 27]
Conflicting Times - Some early news reports after 9/11 will say the Langley jets take off at the later time of 9:35 a.m. [Washington Post, 9/12/2001; CNN, 9/14/2001; Washington Post, 9/15/2001; CNN, 9/17/2001] But according to Colonel Alan Scott, the former vice commander of the Continental US NORAD Region, though the jets are airborne at 9:30, the report of this does not come down until 9:35, so this fact may account for the conflicting times. [9/11 Commission, 5/23/2003]

Entity Tags: Brad Derrig, Alan Scott, Craig Borgstrom, Dean Eckmann, Langley Air Force Base, Larry Arnold

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

Entity Tags: John Werth

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

At the FAA’s Cleveland Center, an air traffic controller hears a transmission, presumably made by Flight 93 hijacker-pilot Ziad Jarrah, stating: “Ladies and gentlemen: Here the captain, please sit down, keep remaining sitting. We have a bomb on board. So, sit.” [9/11 Commission, 7/24/2004, pp. 12; 9/11 Commission, 8/26/2004, pp. 39] As the 9/11 Commission later notes, “Like [Mohamed] Atta on Flight 11, Jarrah apparently did not know how to operate the communication radios; thus his attempts to communicate with the passengers were broadcast on the [air traffic control] channel.” [9/11 Commission, 8/26/2004, pp. 98] While this communication is assumed to have come from Flight 93, an early FAA report states that it came “from an unknown origin.” [Federal Aviation Administration, 9/17/2001 pdf file] According to Newsweek, just prior to the communication, Cleveland Center controllers heard the sound of screaming from the flight. [Newsweek, 9/22/2001] The 9/11 Commission states that, around the time of the transmission, the plane’s cockpit voice recording indicates “that a woman, most likely a flight attendant, was being held captive in the cockpit. She struggled with one of the hijackers who killed or otherwise silenced her.” [9/11 Commission, 7/24/2004, pp. 12; 9/11 Commission, 8/26/2004, pp. 39] Though the Cleveland air traffic controller understands the hijacker’s communication, he responds to it: “Calling Cleveland Center, you’re unreadable. Say again, slowly.” He also notifies his supervisor who passes the information up the chain of command, and the FAA’s Command Center is subsequently informed, “United 93 may have a bomb on board.” At 9:34 the Command Center will relay this information to FAA headquarters (see 9:34 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 28]

Entity Tags: Cleveland Air Route Traffic Control Center, 9/11 Commission, Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

Entity Tags: Federal Aviation Administration, Ben Sliney

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to the later claims of several senior officials, the US military is tracking Flight 93 as it heads east and is ready to shoot it down if necessary.
bullet According to Brigadier General Montague Winfield, the Pentagon’s National Military Command Center (NMCC) has “received the report from the FAA that Flight 93 had turned off its transponder, had turned, and was now heading towards Washington, DC.” Winfield will add, “The decision was made to try to go intercept Flight 93.” [ABC News, 9/11/2002]
bullet General Richard Myers, the acting chairman of the Joint Chiefs of Staff, will write that in the NMCC, “We learned that there was apparently a fourth hijacked aircraft, United Airlines Flight 93 out of Newark, bound nonstop for San Francisco. Like the other planes, it had switched off its transponder, making it much harder if not impossible to track on ground radar.” [Myers, 2009, pp. 152]
bullet Major General Larry Arnold, the commander of the Continental United States NORAD Region, will say, “I was personally anxious to see what 93 was going to do, and our intent was to intercept it.” Three fighters have taken off from Langley Air Force Base in Virginia (see (9:25 a.m.-9:30 a.m.) September 11, 2001). According to Arnold, “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] He says, “as we discussed it in the conference call, we decided not to move fighters toward 93 until it was closer because there could have been other aircraft coming in,” but adds, “I had every intention of shooting down United 93 if it continued to progress toward Washington, DC… whether we had authority or not.” [Filson, 2003, pp. 73]
bullet Colonel Robert Marr, the battle commander at NORAD’s Northeast Air Defense Sector (NEADS), is reportedly “focused on United Flight 93, headed straight toward Washington.” He will concur with Arnold, saying: “United Airlines Flight 93 would not have hit Washington, DC. He would have been engaged and shot down before he got there.” [Filson, 2003, pp. 73] Marr and Arnold will both say they were tracking Flight 93 even earlier on, while it was still heading west (see Shortly Before 9:36 a.m. September 11, 2001).
Yet, contradicting these claims, the 9/11 Commission will conclude that the military only learns about Flight 93 around the time it crashes. It says the NMCC learns of the hijacking at 10:03 a.m. (see 10:03 a.m. September 11, 2001). Based upon official records, including recordings of the NEADS operations floor, it says NEADS never follows Flight 93 on radar and is first alerted to it at 10:07 a.m. (see 10:05 a.m.-10:08 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 30-31, 34 and 42; Washington Post, 4/30/2006; Vanity Fair, 8/1/2006]

Entity Tags: National Military Command Center, Montague Winfield, Richard B. Myers, Robert Marr, Larry Arnold

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The Pentagon explodes. 
The Pentagon explodes. [Source: Donley/ Sipa]Flight 77 crashes into the Pentagon. All 64 people on the plane are killed. A hundred-and-twenty-four people working in the building are killed, and a further victim will die in hospital several days later. Hijackers Hani Hanjour, Khalid Almihdhar, Majed Moqed, Nawaf Alhazmi, and Salem Alhazmi presumably are killed instantly. (Typically, they are not included in the death counts.) [CNN, 9/17/2001; North American Aerospace Defense Command, 9/18/2001; Guardian, 10/17/2001; Washington Post, 11/21/2001; USA Today, 8/12/2002; Associated Press, 8/21/2002; MSNBC, 9/3/2002; ABC News, 9/11/2002; CBS, 9/11/2002] Flight 77 hits the first floor of the Pentagon’s west wall. The impact and the resulting explosion heavily damage the building’s three outer rings. The path of destruction cuts through Army accounting offices on the outer E Ring, the Navy Command Center on the D Ring, and the Defense Intelligence Agency’s comptroller’s office on the C Ring. [Vogel, 2007, pp. 431 and 449] Flight 77 strikes the only side of the Pentagon that had recently been renovated—it was “within days of being totally [renovated].” [US Department of Defense, 9/15/2001] “It was the only area of the Pentagon with a sprinkler system, and it had been reconstructed with a web of steel columns and bars to withstand bomb blasts. The area struck by the plane also had blast-resistant windows—two inches thick and 2,500 pounds each—that stayed intact during the crash and fire. While perhaps, 4,500 people normally would have been working in the hardest-hit areas, because of the renovation work only about 800 were there.” More than 25,000 people work at the Pentagon. [Los Angeles Times, 9/16/2001] Furthermore, the plane hits an area that has no basement. As journalist Steve Vogel later points out, “If there had been one under the first floor, its occupants could easily have been trapped by fire and killed when the upper floors collapsed.” [Vogel, 2007, pp. 450]

Entity Tags: Hani Hanjour, Khalid Almihdhar, Nawaf Alhazmi, US Department of Defense, Salem Alhazmi, Majed Moqed, Pentagon

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Firefighter Timothy Brown, a supervisor at New York City’s Office of Emergency Management, is told that a suspicious plane that was reportedly flying toward New York has crashed. [Firehouse, 1/31/2003] After the second hijacked plane crashed into the World Trade Center, at 9:03 a.m. (see 9:03 a.m. September 11, 2001), Brown went to the lobby of the South Tower to help open a command post. [Project Rebirth, 6/30/2002 pdf file; TEDx Talks, 10/7/2015] While there, he heard over his radio that another suspicious aircraft, in addition to the planes that hit the Twin Towers, was heading toward New York (see (9:30 a.m.) September 11, 2001). Since then, he has talked to the New York State Emergency Management Office about getting fighter jets to protect New York (see (Shortly After 9:37 a.m.) September 11, 2001). [Firehouse, 1/31/2003] He then told people at the command post they should “be prepared to be hit again.” [Project Rebirth, 6/30/2002 pdf file] However, he now hears over his radio that “the third plane was no longer inbound, that it had crashed.” This news “gave us a sigh of relief,” he will later comment. [Firehouse, 1/31/2003] The identity of this third suspicious plane is unclear. Brown will say it turned out to be “the one that crashed in Pennsylvania,” meaning Flight 93. [Project Rebirth, 6/30/2002 pdf file] However, this is apparently impossible, since Brown will describe hearing it has crashed before 9:59 a.m., when the South Tower collapses (see 9:59 a.m. September 11, 2001), but Flight 93 will reportedly crash later on, at 10:03 a.m. (see (10:03 a.m.-10:10 a.m.) September 11, 2001 and (10:06 a.m.) September 11, 2001). [Firehouse, 1/31/2003; 9/11 Commission, 7/24/2004, pp. 30]

Entity Tags: Timothy Brown

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 transponder signal from Flight 93 ceases. [CNN, 9/17/2001; MSNBC, 9/3/2002; MSNBC, 9/11/2002; 9/11 Commission, 6/17/2004] However, the plane can be—and is—tracked using primary radar by Cleveland flight controllers and at United headquarters. Altitude can no longer be determined, except by visual sightings from other aircraft. The plane’s speed begins to vary wildly, fluctuating between 600 and 400 mph before eventually settling around 400 mph. [Longman, 2002, pp. 77, 214; 9/11 Commission, 6/17/2004]

Entity Tags: United Airlines, Cleveland Air Route Traffic Control Center

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

After learning that Delta flight 1989 may have been hijacked from Boston flight control (see 9:39 a.m. September 11, 2001), NEADS calls Cleveland flight control, which is handling the flight, to discuss this. [9/11 Commission, 7/24/2004, pp. 14] Although Cleveland flight control has been aware that United 93 has been hijacked since before 9:30, it apparently fails to mention this to NEADS. According to the 9/11 Commission, the NMCC is not notified of United 93’s hijacking until 10:03 (see 10:03 a.m. September 11, 2001).

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The air traffic control tower at Pittsburgh International Airport is evacuated, because of concerns that Flight 93, which is heading in the direction of the airport, could crash into it. [Federal Aviation Administration, 9/17/2001 pdf file; Pittsburgh Post-Gazette, 9/23/2001; Federal Aviation Administration, 3/21/2002, pp. 11-13 pdf file; Lancaster New Era, 11/3/2006]
Cleveland Center Notifies Pittsburgh Tower - At 9:44 a.m., an air traffic controller at the FAA’s Cleveland Center calls the Pittsburgh Airport control tower and notifies it of the loss of radio contact with Flight 93, and the loss of a secondary radar return from that aircraft (see (9:40 a.m.) September 11, 2001). The Cleveland Center controller also says Flight 93 has made an unanticipated turn (see (9:36 a.m.) September 11, 2001), and its flight path will take it close to Pittsburgh Airport, if not directly over it. [Federal Aviation Administration, 3/21/2002, pp. 11-12 pdf file] The controller at the Pittsburgh tower who answers the call, apparently Paul Delfine, begins tracking Flight 93’s primary target on radar, and calls over his operations supervisor, Mal Fuller. [Federal Aviation Administration, 9/17/2001 pdf file; Lancaster New Era, 11/3/2006]
Supervisor Orders Evacuation - Delfine points to a plane—which Fuller only later learns is Flight 93—on a radar scope. He tells Fuller it was hijacked over Cleveland, and controllers don’t know where it is heading. Fuller will later recall: “In two sweeps of the radar, I could tell it was going very fast. It was headed directly for the control tower.” Fuller is aware of the attacks on the World Trade Center and the Pentagon, and, at 9:49, gives the order, “Evacuate the facility.” [Pittsburgh Post-Gazette, 9/23/2001; Lancaster New Era, 11/3/2006] By 9:51, the facility has been evacuated. [Federal Aviation Administration, 9/17/2001 pdf file] However, one controller refuses to leave his post and remains in the tower. [Spencer, 2008, pp. 193-194]
Employees Do Not See Flight 93 Overhead - Some of the evacuated employees are so upset that they immediately head home. Others mill around in a parking lot. Fuller will later guess that Flight 93 passed directly overhead as he was heading outside, but he assumes it was too high for anyone to see it. He will recall: “We watched and watched and watched. We never saw anything.” [Lancaster New Era, 11/3/2006]
Controllers Return to Facility - Minutes after evacuating, at 9:56 a small number of tower controllers will volunteer to return to their facility. Once back inside, they find that Flight 93’s track is no longer visible on their radar screens. At 10:05 a.m., tower personnel will contact the FAA’s Herndon Command Center to explain why they evacuated. They say they did so because there had been an aircraft, thought to be Flight 93, which appeared to be on a collision course with the tower, and this aircraft allegedly had a bomb on board. [Federal Aviation Administration, 9/17/2001 pdf file; Federal Aviation Administration, 3/21/2002, pp. 12-13 pdf file] Around the time the Pittsburgh Airport control tower evacuates, while Flight 93 is heading east, NEADS battle commander Colonel Robert Marr hears that the FAA’s Cleveland Center is being evacuated (see (10:17 a.m.) September 11, 2001). [Filson, 2003, pp. 73]

Entity Tags: Paul Delfine, Pittsburgh International Airport, Cleveland Air Route Traffic Control Center, Mal Fuller

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

Entity Tags: Leo Mullin, Jane Garvey, Delta Airlines

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

A radio transmitter carried by aircraft that is designed to go off automatically if a plane crashes is activated in the vicinity of the city of Ann Arbor in southeast Michigan, although the distress signal is presumably a false alarm. Details of the distress signal will be described when an unidentified individual calls the FAA’s Cleveland Center at around 10:19 a.m. and tells an air traffic controller there, “I’ve got an ELT reported over Ann Arbor.” [Federal Aviation Administration, 9/11/2001; Federal Aviation Administration, 10/14/2003] An “ELT” is an emergency locator transmitter, a device carried on most general aviation aircraft in the US that is designed to automatically begin transmitting a distress signal if a plane should crash, so as to help search and rescue efforts in locating the downed aircraft. [Federal Aviation Administration, 3/23/1990; Federal Aviation Administration, 7/12/2001; Aircraft Owners and Pilots Association, 1/22/2009] The caller will not say who reported the ELT signal to him. But he will say the signal “started at 13:53” Zulu time, which is 9:53 a.m. Eastern time. Presumably realizing the signal was therefore activated over 25 minutes earlier, the caller will add, “Wait a minute, that don’t make any sense.” But the Cleveland Center controller will tell him: “Yeah, it does. It might have been late to be…” The caller will then say, “Okay, well I’ve got an ELT reported over Ann Arbor,” before the call ends. [Federal Aviation Administration, 9/11/2001] Further details of the ELT signal and what might have caused it are unknown. Flight 93 will crash in rural Pennsylvania about 10 minutes after the signal over Ann Arbor is activated (see (10:03 a.m.-10:10 a.m.) September 11, 2001 and (10:06 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 30] However, apparently no ELT signal will go off when it crashes (see 10:07 a.m. September 11, 2001). [Federal Aviation Administration, 9/11/2001] According to Major Allan Knox, who works at the Air Force Rescue Coordination Center at Langley Air Force Base in Virginia, most ELT signals are false alarms. [9/11 Commission, 10/6/2003 pdf file]

Entity Tags: Allan Knox, Cleveland Air Route Traffic Control Center

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

NORAD’s Northeast Air Defense Sector (NEADS) contacts an Air National Guard unit in Toledo, Ohio, and requests that it launch two fighter jets in response to the attacks. [WTOL, 9/11/2006; Lynn Spencer, 2008; Spencer, 2008, pp. 178]
First Time that Unit Has Answered a NORAD Request - The 180th Fighter Wing of the Ohio Air National Guard is based at Toledo Express Airport. It has 20 F-16 fighter jets and about three dozen pilots. [Toledo Blade, 12/9/2001] Its “primary mission” is “to provide combat ready F-16C and support units capable of deploying worldwide in minimum response time.” [180th Fighter Wing, 9/19/2001; GlobalSecurity (.org.), 10/21/2001] The unit is not one of NORAD’s seven alert facilities around the US, and this is believed to be the first time it has ever answered a request for help from NORAD. [Airman, 12/1999; Toledo Blade, 12/9/2001]
Call due to Concern over Delta 1989 - According to author Lynn Spencer, a weapons technician at NEADS makes the call to the 180th FW due to concerns about Delta Air Lines Flight 1989, which is incorrectly thought to have been hijacked (see 9:39 a.m. September 11, 2001). [Spencer, 2008, pp. 177-178] NEADS has already contacted units in Minnesota and Michigan about this aircraft (see (Shortly After 9:41 a.m.) September 11, 2001 and (9:55 a.m.) September 11, 2001). [9/11 Commission, 1/23/2004 pdf file; Vanity Fair, 8/1/2006] The weapons technician calls the Toledo unit after Master Sergeant Joe McCain gives an update across the NEADS operations floor: “Delta [19]89! Hard right turn!” According to Spencer, the weapons technician knows the 180th FW is much better positioned than the Selfridge unit’s fighters are to reach Delta 1989. [Spencer, 2008, pp. 178]
NORAD Commander Gives Different Explanation - But according to Larry Arnold, the commander of the Continental United States NORAD Region, the weapons technician’s call might also be in response to concerns over Flight 93. Arnold will say that NEADS calls the 180th FW “because we thought [Flight] 93 or Delta Flight 1989 might be headed toward Chicago.” [Filson, 2003, pp. 71] Two Toledo pilots who initially answer the call from NEADS appear to believe the call is a joke, but their wing commander then picks up the line and responds appropriately (see 10:01 a.m. September 11, 2001). [Spencer, 2008, pp. 178-179]
Unit Prepared for Crisis Like This - Although it is not one of NORAD’s alert facilities, Lt. Col. Gary Chudzinski, a former commander of the 180th FW, will later comment that the Toledo unit has always been aware that it could be alerted to crises such as the current one, “but you just don’t expect it.” According to General Paul Sullivan, who heads all Ohio Air National Guard units, the 180th FW’s pilots practice “air interception,” but a typical mission focuses on either a plane ferrying drugs or enemy fighters approaching America’s coasts. [Airman, 12/1999; Toledo Blade, 12/9/2001] Two 180th FW jets will take off from the Toledo unit at 10:17 a.m. (see 10:17 a.m. September 11, 2001). [Toledo Blade, 12/9/2001; WTOL, 9/11/2006]

Entity Tags: Gary Chudzinski, Joe McCain, Larry Arnold, 180th Fighter Wing, Northeast Air Defense Sector, Paul Sullivan

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Flight 93’s transponder, which was switched off after Flight 93 was hijacked, is turned back on just before the plane crashes, thereby revealing the plane’s altitude to air traffic controllers at the FAA’s Cleveland Center. [Federal Bureau of Investigation, 9/11/2001; MSNBC, 9/11/2002] A transponder is a device that sends a plane’s identifying information, speed, and altitude to controllers’ radar screens. [Washington Post, 9/16/2001] Flight 93’s transponder was switched off at around 9:40 a.m. (see (9:40 a.m.) September 11, 2001), although Cleveland Center controllers have still been able to follow Flight 93 on “primary radar,” which shows less information about a flight (see (9:41 a.m.-10:06 a.m.) September 11, 2001). [Federal Bureau of Investigation, 1/8/2002; 9/11 Commission, 7/24/2004, pp. 29; Cleveland Plain Dealer, 7/3/2011]
Plane Shown to Be Flying at 8,200 Feet - Flight 93’s transponder is reactivated at 10:02 a.m. and 50 seconds, and then stays on for “approximately 20 seconds,” according to “information from the flight data” provided to the FBI later today by Rick Kettell, the manager of the Cleveland Center. After the transponder is turned back on, Flight 93’s radar track is observed by Cleveland Center controllers Linda Justice and Stacey Taylor. The information from the transponder shows them that Flight 93 is at an altitude of 8,200 feet. [Federal Bureau of Investigation, 9/11/2001; Federal Aviation Administration, 9/16/2001 pdf file; 9/11 Commission, 10/2/2003 pdf file]
Plane Soon Disappears from Radar Screens - Flight 93 will crash into the ground at 10:03 a.m. and 11 seconds, according to the 9/11 Commission Report, less than 30 seconds after the transponder is reactivated (see (10:03 a.m.-10:10 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 30] Cleveland Center controllers will see the plane completely disappear from their radar screens around that time. [MSNBC, 9/11/2002] A Cleveland Center controller will then report, apparently over an FAA teleconference, that Flight 93’s transponder “came on briefly and then it went back off with the primary, and now we’ve lost him completely.” [Federal Aviation Administration, 9/11/2001] “I had two radar hits on [Flight 93],” Taylor will recall, adding that she then “lost the primary target on [Flight 93] and we suspected it had gone down.” [Federal Aviation Administration, 9/16/2001 pdf file] The reason Flight 93’s transponder is switched back on just before the plane crashes is unclear. Taylor will comment, a year after 9/11: “That’s something we’ve always wanted to know. Why did the transponder come back on?” She will say Cleveland Center controllers wondered this because they believed that “the hijackers had shut it off so that they couldn’t be tracked.” [MSNBC, 9/11/2002]

Entity Tags: Stacey Taylor, Cleveland Air Route Traffic Control Center, Linda Justice

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

In response to the terrorist attacks in the United States, the Russian military cancels a major training exercise it has been holding, turning back its bomber aircraft and calling off planned missile testing. [Toronto Star, 12/9/2001; Defense Video and Imagery Distribution System, 9/8/2011] The Russian Air Force began the exercise—which was being conducted over the North Atlantic, Pacific, and Arctic Oceans—on September 10 (see September 10, 2001), and had planned for it to continue until September 14. NORAD has deployed fighter jets to Alaska and Northern Canada to monitor the exercise (see September 9, 2001).
Russians Cancel Exercise to Avoid Confusion - The Russians now call off their exercise, “to avoid misunderstandings, since US defenses were now on high alert in case of further possible terrorist attacks,” according to BBC correspondent Bridget Kendall. [BBC, 2001, pp. 161; North American Aerospace Defense Command, 9/9/2001; Washington Times, 9/11/2001] “The Russians knew NORAD would have its hands full,” the Toronto Star will report. Lieutenant Colonel William Glover, the commander of NORAD’s Air Warning Center, will say the Russians stop their exercise “because they understood the magnitude of what had happened to us in the United States. They didn’t want any questions; they didn’t want us worrying about what they would be doing or entering our Air Defense Identification Zone.”
Russia Tells US about Canceling Exercise - The Russians notify the US of their actions. Captain Michael Jellinek, the director of plans, requirements, and readiness at NORAD’s Cheyenne Mountain Operations Center in Colorado, will later recall: “They sent the message to the State Department clearly and unambiguously: ‘Don’t worry about our movements, we’re going to stay down for a while.’”
Russia's Actions Are 'Very Helpful' to US - It is unclear when exactly the Russians call off their exercise. According to the Toronto Star, they “immediately” cancel it “on seeing the attacks in New York and Washington.” Glover will say the Russians notify the US that they are stopping their exercise “after the United Flight 93 went into Shanksville” (see (10:03 a.m.-10:10 a.m.) September 11, 2001 and (10:06 a.m.) September 11, 2001). Jellinek will call the Russians’ actions in canceling their exercise “[v]ery, very useful. Very helpful.” Glover will comment, “[T]hat was amazing to me, personally, the fact that they stopped their exercise and… that they told us that they were going to stop the exercise.” [Toronto Star, 12/9/2001; Defense Video and Imagery Distribution System, 9/8/2011] Russian President Vladimir Putin will contact the White House and inform National Security Adviser Condoleezza Rice that the Russians are voluntarily canceling their exercise (see Between 10:32 a.m. and 11:45 a.m. September 11, 2001). [Washington Post, 1/27/2002]

Entity Tags: Michael H. Jellinek, Russian Air Force, North American Aerospace Defense Command, US Department of State, William Glover

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Entity Tags: Northeast Air Defense Sector

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

F-16 Fighting Falcon aircraft at the 180th Fighter Wing.F-16 Fighting Falcon aircraft at the 180th Fighter Wing. [Source: Jodi Joice / US Air Force]Two F-16 fighter jets take off from a military unit in Toledo, Ohio, in response to the morning’s attacks, but accounts will conflict over what their mission is and who the pilots are. [Toledo Blade, 12/9/2001; Filson, 2003, pp. 71; WTOL, 9/11/2006] The 180th Fighter Wing of the Ohio Air National Guard is based at Toledo Express Airport. Although the unit is not one of NORAD’s seven alert facilities around the US, it has recently received a call from NORAD’s Northeast Air Defense Sector (NEADS), requesting that it launch two of its fighters (see 10:01 a.m. September 11, 2001). [Airman, 12/1999; Toledo Blade, 12/9/2001; WTOL, 9/11/2006; Spencer, 2008, pp. 178-179] The 180th Maintenance Squadron, which is responsible for maintaining the unit’s aircraft and equipment, was also contacted, and has loaded the F-16s’ guns with 500 rounds of 20-caliber ammunition. [180th Fighter Wing, 9/19/2001; WTOL, 9/11/2006]
Jets Head East - The two F-16s, which were being set up for training missions, now take off and head east. [Toledo Blade, 12/9/2001] According to author Lynn Spencer, they are piloted by Scott Reed and Ed Rinke. [Spencer, 2008, pp. 179] However, a local television station will report that the pilots are Scott Reed and Keith Newell. [WTOL, 9/11/2006]
Mission Unclear - It is unclear what role the two jets play in defending the nation. Toledo Air National Guard officials will later refuse to talk about this morning’s events, even in the general terms permitted by the military. [Toledo Blade, 12/9/2001] According to Spencer, NEADS wanted the 180th FW jets to respond to Delta Air Lines Flight 1989, which is incorrectly thought to have been hijacked and will land in Cleveland at around 10:18 (see (10:18 a.m.) September 11, 2001). The 9/11 Commission will similarly say the Toledo jets are ordered to intercept Delta 1989. [Federal Aviation Administration, 9/16/2001; 9/11 Commission, 7/24/2004, pp. 27-28; Spencer, 2008, pp. 177-178] But Larry Arnold, the commander of the Continental United States NORAD Region, will say the 180th FW was contacted “because we thought [Flight] 93 or Delta Flight 1989 might be headed toward Chicago.” [Filson, 2003, pp. 71] NEADS battle commander Colonel Robert Marr will say the two F-16s “never had a track close enough that they were directed to engage. [But] if a valid direction had come from the appropriate level to engage a target, or shoot down a target at some time, they could have done that.”
Response Is 'Very Quick' - Marr will describe the 180th FW’s response to NEADS’s request for assistance as “very, very, very quick.” [Toledo Blade, 12/9/2001] However, the fourth hijacked aircraft, Flight 93, has already crashed by the time the two jets take off (see (10:06 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 30]

Entity Tags: Ed Rinke, Keith Newell, 180th Fighter Wing, Robert Marr, Scott Reed, Larry Arnold

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

United Airlines contacts American Airlines and notifies it of the crash of Flight 93. [9/11 Commission, 8/26/2004, pp. 47] Flight 93 crashed in Pennsylvania shortly after 10:00 a.m. (see (10:06 a.m.) September 11, 2001). United Airlines received confirmation of this by 10:15 (see (10:07 a.m.-10:15 a.m.) September 11, 2001).

Entity Tags: United Airlines, American Airlines

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Brigadier General David Wherley, the commander of the District of Columbia Air National Guard (DCANG) at Andrews Air Force Base, near Washington, wants his fighter jets to intercept a suspicious aircraft coming down the Potomac River toward the capital, which is apparently thought to be Flight 93, although that plane has already crashed (see (10:06 a.m.) September 11, 2001). [Washington Post, 4/8/2002; Filson, 2003, pp. 79-81; 9/11 Commission, 8/28/2003]
Numerous Suspicious Aircraft - According to the Washington Post, the DCANG has learned there are “about a half-dozen suspicious aircraft in the air across the country, among them hijacked United Airlines Flight 93, on a path toward Washington.” Wherley will add: “Nobody knew it had crashed. We just knew there was an airplane out there that could be coming to Washington. We knew the threat was real.”
Fighters Launched due to False Report - The first three DCANG fighters to take off in response to the attacks are ordered to go after this alleged inbound aircraft. [Washington Post, 4/8/2002] Lieutenant Colonel Phil Thompson, the chief of safety for the DC Air National Guard, will later recall: “We had something coming down the Potomac at low altitude. Brigadier General Wherley is standing here, and we’ve got the tower with the Secret Service agent, and they want us to launch anything we’ve got. And the general said, ‘Do it.’” [Filson, 2003, pp. 81] DCANG pilot Billy Hutchison, who takes off at 10:38 a.m. (see (10:38 a.m.) September 11, 2001), will describe, “There was an aircraft coming down the Potomac that they needed me in the air for” that had to “be prevented from reaching the DC area.” He is told this aircraft is “coming from Pennsylvania.” [9/11 Commission, 2/27/2004] And pilot Marc Sasseville, who, along with Heather Penney Garcia, takes off at 10:42 a.m. (see 10:42 a.m. September 11, 2001), later says: “We all realized we were looking for an airliner—a big airplane. That was Flight 93; the track looked like it was headed toward DC at that time.” [Aviation Week and Space Technology, 9/9/2002; Vogel, 2007, pp. 446]
Incorrect Report Comes from Secret Service - According to Major David McNulty, the senior intelligence officer of the DCANG, his understanding is that “the information about the plane coming down the river” came from the Secret Service’s White House Joint Operations Center. [9/11 Commission, 3/11/2004 pdf file] FAA personnel are also receiving similar information from the Secret Service. At 10:32, an FAA employee tells John White, a manager at the FAA’s Herndon Command Center, “Secret Service is reporting one unknown eight miles out, flying inbound.” Two minutes later, this employee says they are “[t]rying to tell [the] Secret Service about [Flight] 93,” because the Secret Service is “a little bit behind, still getting reports.” They then tell White, “Secret Service is saying the aircraft they are talking is coming up the Potomac right now.” [9/11 Commission, 11/4/2003] Fire and rescue workers are evacuated away from the Pentagon site around this time, in response to a report from the FBI of a hijacked aircraft flying toward Washington (see (10:15 a.m.-10:38 a.m.) September 11, 2001). This may be the same alleged plane that the DCANG and FAA learn of. [US Department of Health and Human Services, 7/2002, pp. A30 pdf file; Fire Engineering, 11/2002]
Aircraft Supposedly a Helicopter - The incoming aircraft is apparently a false alarm. [9/11 Commission, 8/28/2003] After searching for it, Hutchison will be instructed to fly back toward Washington because, he will say, “the plane had been lost.” [9/11 Commission, 2/27/2004] According to a 9/11 Commission memorandum, “FAA tapes and transcripts” reveal the aircraft to be “an Army National Guard helicopter based out of Davison Field, Fort Belvoir, Virginia, which had become isolated in Maryland as events unfolded and which wanted to return to its home field.” [9/11 Commission, 3/11/2004 pdf file]
Secret Service Thinks Plane Crashed at Camp David - However, at 10:36, the FAA employee relays that the “Secret Service is saying they believe United 93 hit Camp David.” Seconds later, they add that the Secret Service is “confirming that UA 93 did go into Camp David.” [9/11 Commission, 11/4/2003] Even President Bush is given an incorrect report of a plane going down near Camp David around this time (see (10:37 a.m.-11:09 a.m.) September 11, 2001). [Sammon, 2002, pp. 108] So this erroneous information may be what leads to Hutchison being informed that the aircraft he was sent after has been lost. [9/11 Commission, 2/27/2004]

Entity Tags: US Secret Service, David Wherley, Billy Hutchison, Phil Thompson, David McNulty, John White, Marc Sasseville, District of Columbia Air National Guard, Heather Penney Garcia, Federal Aviation Administration

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Two F-15s take off from Otis Air National Guard Base in Massachusetts, becoming the second pair of fighter jets to take off from the base after NORAD’s Northeast Air Defense Sector (NEADS) ordered it to launch all of its available aircraft. [9/11 Commission, 10/14/2003 pdf file; Spencer, 2008, pp. 245-246; Richard, 2010, pp. 18] The fighters belong to the 102nd Fighter Wing, which is based at Otis Air Base, and are piloted by Major Martin Richard and Major Robert Martyn. [102nd Fighter Wing, 2001; Cape Cod Times, 9/11/2006] The 102nd Fighter Wing launched its two F-15s that are kept on “alert”—ready for immediate takeoff—at 8:46 a.m., in response to the hijacked Flight 11 (see 8:46 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 20] Another two of the unit’s F-15s have just taken off (see (10:30 a.m.) September 11, 2001). [Spencer, 2008, pp. 245-246] Richard is one of several 102nd Fighter Wing pilots who were out for a training mission over the Atlantic Ocean earlier this morning (see (9:00 a.m.-9:24 a.m.) September 11, 2001). The pilots were called back to their base following the attacks in New York (see (9:25 a.m.-9:45 a.m.) September 11, 2001). It is unclear whether Martyn also participated in the training. [Cape Cod Times, 9/11/2006]
Pilot Doesn't Know What Is Going On - After landing back at Otis Air Base, Richard headed into the operations building and phoned his wife. He told her, “I don’t know what’s going on, but I am going flying.” Richard will later recall: “My feelings were of trepidation. I didn’t know what was going on and didn’t know what the two scrambled aircraft [i.e. the two fighters launched from his base in response to Flight 11] were doing.” Richard and Martyn had then been called to the operations desk, where Lieutenant Colonel Jon Treacy, their unit’s supervisor of flying, told them they would be flying two of the first four fighters to be subsequently taking off from the base. [102nd Fighter Wing, 2001; Richard, 2010, pp. 14-15] Around that time, NEADS called the unit and instructed it to launch all of its available fighters, and the pilots had then been sent out to their aircraft (see (10:20 a.m.) September 11, 2001). [Spencer, 2008, pp. 245]
Fighter Only Has One Missile Loaded - When he arrived at his fighter, Richard found Technical Sergeant Matthew Jackson loading the second of two AIM-9 heat-seeking missiles onto it. Dennis Mills, the crew chief, told Richard that his plane was fueled up and had a “hot gun with bullets,” meaning the 20mm gun was loaded and armed for use. Richard, who was impatient to get airborne, instructed Jackson to not bother loading the second missile onto his aircraft.
Intelligence Officer Warns of Eight Suspicious Aircraft - Then, Sergeant Joe Kelleher, the unit’s intelligence specialist, arrived, out of breath. Kelleher said: “There are up to eight airliners airborne with bombs on board. We know of an American [Airlines] jet out of Dulles [International Airport] and a United [Airlines] jet. I think you are going after the United jet.” The United Airlines aircraft he referred to, according to Richard, was Flight 93. [Richard, 2010, pp. 15-16] However, this plane crashed in Pennsylvania shortly after 10:00 a.m. (see (10:03 a.m.-10:10 a.m.) September 11, 2001 and (10:06 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 30] Richard will comment, “We were finding out real-time what the actual air picture was, and the information was not accurate.” Kelleher continued: “They are turning jets away from Europe and the rumor is some have crashed because they’ve run out of fuel. It’s friggin’ chaos!”
Fighters Take Off from Base - In their fighters, Richard and Martyn now taxi to the runway and take off from Otis Air Base. While climbing to altitude, Richard keeps his fighter’s engines in afterburner so as to gather the most speed he can. [Richard, 2010, pp. 16, 18] Richard and Martyn will be directed to intercept a C-130 military cargo plane (see (After 10:35 a.m.) September 11, 2001), and will subsequently be sent over New York to intercept and identify aircraft there (see (11:00 a.m.-6:00 p.m.) September 11, 2001). [102nd Fighter Wing, 2001; Cape Cod Times, 9/11/2006; Airman, 9/3/2011]

Entity Tags: 102nd Fighter Wing, Dennis Mills, Joe Kelleher, Robert Martyn, Jonathan T. Treacy, Matthew Jackson, Martin Richard, Otis Air National Guard Base

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The press incorrectly reports that an airliner has crashed on or near Camp David. [Daily Record (Baltimore), 9/12/2001; US Department of Transportation, 3/2002] Camp David is the presidential retreat, located about 70 miles north of Washington, DC, in the Catoctin Mountains of Maryland. [Federation of American Scientists, 10/2/2000; Associated Press, 7/30/2007] On Air Force One, at 10:37, White House chief of staff Andrew Card relays to the president the incorrect report of the crash. [Sammon, 2002, pp. 108] At around 11:09, CBS News reports that “a plane apparently has crashed at or near Camp David.” [Broadcasting and Cable, 8/26/2002] An early article by Forbes states, “There are reports of a fourth airliner [having] been brought down near Camp David… by US military fighters.” [Forbes, 9/11/2001] And an early report by the Northwestern Chronicle similarly states, “Air Force officials say an airliner has been forced down by F-16 fighter jets near Camp David.” [Northwestern Chronicle, 9/11/2001] Theresa Hahn, the catering manager for a restaurant in the Camp David area, hears the erroneous report. She subsequently describes, “Lots of fire trucks were on the road and no one can get up there.” But J. Mel Poole, the Catoctin Mountain Park superintendent, states there has been “no crash at Camp David.” [Daily Record (Baltimore), 9/12/2001] At some point, the FAA calls the military to confirm the crash, and is reassured that no crash occurred at Camp David. [Freni, 2003, pp. 42] The actual Flight 93 crash site is about 85 miles northwest of Camp David. [PBS, 9/11/2001] The Secret Service reportedly tells the White House that Flight 93 may have been on a course for Camp David. [Pittsburgh Channel, 9/11/2001] And, following a military briefing, Representative James Moran (D-VA) tells reporters that Flight 93 was apparently heading for Camp David. [Associated Press, 9/11/2001; Wall Street Journal, 9/12/2001] (However, the 9/11 Commission will later state that its intended target was either the White House or the Capitol building. [9/11 Commission, 7/24/2004, pp. 14] ) The source of the incorrect report of the Camp David crash is unclear. However, when the FAA’s Washington Center first informed NEADS that Flight 93 had crashed, at 10:15, it simply reported that it had gone down “somewhere up northeast of Camp David” (see 10:15 a.m. September 11, 2001), so this may have created some of the confusion. [Vanity Fair, 8/1/2006] There are also numerous false reports of terrorist attacks having taken place in Washington, DC around this time (see (Between 9:50-10:40 a.m.) September 11, 2001). Some commentators make the connection that the 9/11 attacks come 23 years after the signing of the Camp David accords—a peace agreement between Israel and Egypt—on September 17, 1978. [Forbes, 9/11/2001; Village Voice, 9/11/2001; Daily Record (Baltimore), 9/12/2001] WCBS reports, “[T]here is speculation that perhaps, perhaps, this may be in retaliation for those accords.” [Broadcasting and Cable, 8/26/2002]

Entity Tags: Federal Aviation Administration, J. Mel Poole, Andrew Card, James Moran, Theresa Hahn, US Secret Service

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Having taken off after returning from a training mission, a pilot with the District of Columbia Air National Guard (DCANG) flies two loops up the Potomac River, reversing course near Georgetown and the Pentagon, but is unable to locate a suspicious approaching aircraft, and heads back to base less than 10 minutes after launching. [Aviation Week and Space Technology, 9/9/2002; 9/11 Commission, 2/17/2004; 9/11 Commission, 2/27/2004; 9/11 Commission, 3/11/2004 pdf file; Spencer, 2008, pp. 219-221]
No Rules of Engagement - Major Billy Hutchison, a pilot with the 121st Fighter Squadron of the DCANG, had landed back at Andrews Air Force Base, 10 miles from Washington, but was ordered to take off again immediately (see (10:38 a.m.) September 11, 2001). [Aviation Week and Space Technology, 9/9/2002] His plane has no missiles, and only training ammunition, and he has been given no specific rules of engagement other than being told to identify an aircraft that is coming down the river. [Washington Post, 4/8/2002; 9/11 Commission, 3/11/2004 pdf file; Vogel, 2007, pp. 446] Because the DCANG is not in the communication and command loops of NORAD or its Northeast Air Defense Sector (NEADS), Hutchison is unaware that three fighter jets NEADS ordered into the air from Langley Air Force Base (see 9:24 a.m. September 11, 2001) are also flying over Washington, albeit at a much higher altitude than he is. [Washington Post, 4/8/2002; Aviation Week and Space Technology, 9/9/2002; 9/11 Commission, 2/27/2004]
Controller Directs Hutchison - Hutchison calls the Terminal Radar Approach Control (TRACON) at Washington’s Reagan National Airport. He says, “Bully 1 [his call sign] is looking for a contact.” Victor Padgett, the operations supervisor at the TRACON, replies, “We have an intercept for you northwest of here and coming down the Potomac.” [Spencer, 2008, pp. 219] Hutchison knows he is meant to be searching for a civilian aircraft, and will later recall that he is told it is coming from Pennsylvania. [9/11 Commission, 2/27/2004] In order to conserve fuel and gain airspeed, he flies low over the White House and Georgetown, reportedly staying between 500 and 1,000 feet above ground level. [Aviation Week and Space Technology, 9/9/2002; Spencer, 2008, pp. 219] After Padgett gives him details of the approaching aircraft’s location, Hutchison spots it on his jet’s radar screen, but it quickly disappears. The aircraft reappears a minute later, but then both Hutchison and Padgett lose sight of it.
Aircraft Claimed to Be Flight 93 - Some accounts will suggest the approaching aircraft is thought to be Flight 93 (see (10:30 a.m.-10:40 a.m.) September 11, 2001), even though that plane has already crashed (see (10:06 a.m.) September 11, 2001). [Washington Post, 4/8/2002; Spencer, 2008, pp. 219-221] Hutchison will later recall that the TRACON at Reagan Airport is “frantic with what they seem to think are aircraft coming their way.… There is another aircraft, and it’s United Flight 93. They… apparently have been given information that it’s coming their way.” [Filson, 2003, pp. 81] Major David McNulty, the senior intelligence officer of the DCANG, will recall, “[I]t wasn’t until later that they realized the plane [coming down the river] might be UAL 93.” [9/11 Commission, 3/11/2004 pdf file] However, John Farmer, John Azzarello, and Miles Kara, who are all staff members of the 9/11 Commission, subsequently rebut this claim. They will write: “[R]adar records of the day [of 9/11] indicate that Major Hutchison did not take off until more than a half-hour after United 93 had crashed near Shanksville, PA, and a good 20 minutes after the wreckage had been located. He could not have seen United 93 on his scope, and could not have intercepted it.” [New York Times, 9/13/2008]
Told to Investigate Other Aircraft - After the aircraft disappears off Hutchison’s radar screen, Dan Creedon, an air traffic controller at the TRACON at Reagan Airport, is concerned about planes and helicopters that are taking off and landing across Washington, and tells Hutchison, “We have more contacts!” Hutchison confirms that he will investigate the targets Creedon alerts him to, but he keeps losing them among the ground clutter on his radar screen. According to author Lynn Spencer, “The flights are too close to the surface and, from what he can see, appear to be mostly helicopters flying medevac from the Pentagon.”
Flies over the Pentagon - Hutchison, who’d noticed the burning Pentagon before he landed at Andrews Air Force Base (see (9:50 a.m.) September 11, 2001), then decides he should investigate it. He descends and flies a steep turn over the Pentagon. [Spencer, 2008, pp. 234-235] He will later recall: “I circled at a couple of hundred feet at the most just to, one, investigate, and two, give the people on the ground some semblance of security of an American fighter coming by. And apparently it changed the mood for a lot of people when they saw that” (see (10:40 a.m.) September 11, 2001).
Running out of Fuel - By now, Hutchison is almost out of fuel. He will recall, “After that point, I’m emergency fuel, the lowest I’ve ever been in an F-16, and tell [the FAA’s] Washington Center I must leave, and they say I’m cleared to return to base and that two more aircraft are coming out of Andrews.” [Filson, 2003, pp. 81-82] Hutchison will land at Andrews at 10:47 a.m. (see 10:47 a.m. September 11, 2001). [9/11 Commission, 2004; 9/11 Commission, 2/17/2004]

Entity Tags: Victor Padgett, Dan Creedon, Billy Hutchison, Ronald Reagan Washington National Airport, Pentagon, 121st Fighter Squadron, John Farmer, Miles Kara, David McNulty, John Azzarello, District of Columbia Air National Guard

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

United Airlines issues a press release confirming that Flight 93 has crashed. Flight 93 went down in Pennsylvania shortly after 10:00 a.m. (see (10:06 a.m.) September 11, 2001). The release states: “United Airlines has confirmed one of its flights has crashed near Pittsburgh, Pennsylvania. United Flight 93, a Boeing 757 aircraft, is the flight number involved. The flight originated in Newark and was bound for San Francisco.” The release adds, “United is deeply concerned about a further flight, United Flight 175, a Boeing 767, which was bound from Boston to Los Angeles.” [United Airlines, 9/11/2001] Although Flight 175 hit the World Trade Center at 9:03 (see 9:03 a.m. September 11, 2001), United Airlines will not publicly confirm it has crashed until 11:53 a.m. (see 11:53 a.m. September 11, 2001).

Entity Tags: United Airlines

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Carl Levin.Carl Levin. [Source: Publicity photo]Air Force General Richard Myers is questioned about the US military’s response to the 9/11 attacks when he appears before the Senate Armed Services Committee for his confirmation hearing as chairman of the Joint Chiefs of Staff, but his answers are vague and confused, and he claims, incorrectly, that no fighter jets were scrambled in response to the hijackings until after the Pentagon was hit. [Shenon, 2008, pp. 119; Farmer, 2009, pp. 241-243] Myers has been the vice chairman of the Joint Chiefs of Staff since March 2000. [US Air Force, 9/2005] With General Henry Shelton, the chairman of the Joint Chiefs of Staff, flying toward Europe on the morning of September 11 (see (8:50 a.m.-10:00 a.m.) September 11, 2001), he served as the acting chairman of the Joint Chiefs of Staff during the 9/11 attacks. [Myers, 2009, pp. 10; Shelton, Levinson, and McConnell, 2010, pp. 431-433]
Myers Says Fighters Were Only Scrambled after the Pentagon Attack - During the hearing, Senator Carl Levin (D-MI) asks if the Department of Defense was contacted by “the FAA or the FBI or any other agency” after the first two hijacked aircraft crashed into the World Trade Center, at 8:46 a.m. and 9:03 a.m. (see 8:46 a.m. September 11, 2001 and 9:03 a.m. September 11, 2001), but before 9:37 a.m., when the Pentagon was hit (see 9:37 a.m. September 11, 2001). Myers replies, “I don’t know the answer to that question.” Levin then asks if the military was “asked to take action against any specific aircraft” during the attacks. Myers answers, “When it became clear what the threat was, we did scramble fighter aircraft, AWACS, radar aircraft, and tanker aircraft to begin to establish orbits in case other aircraft showed up in the FAA system that were hijacked.” Myers elaborates later in the hearing, telling Senator Bill Nelson (D-FL): “[A]fter the second tower was hit, I spoke to the commander of NORAD, General [Ralph] Eberhart (see (9:37 a.m.) September 11, 2001). And at that point, I think the decision was at that point to start launching aircraft.” But he tells Levin that “to the best of my knowledge,” the order to scramble fighters was only given “after the Pentagon was struck.”
Flight 93 Was Not Shot Down, Myers Says - Myers addresses the military’s response to Flight 93, the fourth hijacked plane, which crashed in a field in Pennsylvania (see (10:03 a.m.-10:10 a.m.) September 11, 2001 and (10:06 a.m.) September 11, 2001). He says: “[I]f my memory serves me… we had launched on the one that eventually crashed in Pennsylvania. I mean, we had gotten somebody close to it, as I recall.” However, he adds, “I’ll have to check that out.” When Levin mentions that there have been “statements that the aircraft that crashed in Pennsylvania was shot down,” Myers responds, “[T]he armed forces did not shoot down any aircraft.” He says, “[W]e never actually had to use force.” Although Myers appears unclear about when the North American Aerospace Defense Command (NORAD) launched fighters in response to the hijackings, he is more confident when he states: “At the time of the first impact on the World Trade Center, we stood up our Crisis Action Team. That was done immediately. So we stood it up. And we started talking to the federal agencies.” [US Congress, 9/13/2001]
NORAD and the 9/11 Commission Contradict Myers's Account - Myers’s claim that fighters were only launched in response to the hijackings after the Pentagon was hit will later be contradicted by the accounts of NORAD and the 9/11 Commission, which state that fighters were ordered to take off from Otis Air National Guard Base in Cape Cod, Massachusetts, at 8:46 a.m. (see 8:46 a.m. September 11, 2001) and from Langley Air Force Base in Virginia at 9:24 a.m. (see 9:24 a.m. September 11, 2001). [North American Aerospace Defense Command, 9/18/2001; 9/11 Commission, 7/24/2004, pp. 20, 27] The 9/11 Commission will also contradict Myers’s claim that the military launched fighters in response to Flight 93 and “had gotten somebody close to it.” “By the time the military learned about the flight,” the 9/11 Commission Report will state, “it had crashed.” [9/11 Commission, 7/24/2004, pp. 34]
Myers's Testimony Prompts Criticism in the Media - Journalist and author Philip Shenon will question why Myers, a veteran Air Force fighter pilot, would give such an inaccurate account of the military’s response to the 9/11 attacks during the hearing. “It seemed obvious that Myers, of all people at the Pentagon, would want to know—would demand to know—how jet fighters under NORAD’s control had responded on the morning of September 11 to the threat in the skies,” he will write. [US Congress, 9/13/2001; Shenon, 2008, pp. 119] John Farmer, the senior counsel to the 9/11 Commission, will comment that “Myers’s evident confusion about precisely what had occurred prompted criticism in the media and a quick, if contradictory, response from the administration.” [Farmer, 2009, pp. 243] Major General Paul Weaver, director of the Air National Guard, will provide a more detailed account of the military’s response to the hijackings in an “impromptu hallway interview” at the Pentagon on September 14 (see September 14, 2001). [Dallas Morning News, 9/14/2001] And four days later, NORAD will release a timeline of its response to the hijackings (see September 18, 2001). [North American Aerospace Defense Command, 9/18/2001]

Entity Tags: Richard B. Myers, Senate Armed Services Committee, Carl Levin, Clarence W. (“Bill”) Nelson

Timeline Tags: Complete 911 Timeline

Major General Paul Weaver, director of the Air National Guard, provides reporters with details of the 9/11 attacks and the US military’s response to the hijackings. Speaking at the Pentagon, Weaver gives reporters a detailed account of what happened on September 11. He says Air National Guard planes responded to the hijackings on orders from NORAD’s Northeast Air Defense Sector (NEADS), which was alerted to the hijackings by the Federal Aviation Administration (FAA).
Fighters Took Off Too Late to Catch Flight 175 - Weaver says that at 8:53 a.m., seven minutes after Flight 11 crashed into the North Tower of the World Trade Center (see 8:46 a.m. September 11, 2001), two F-15 fighter jets took off from Otis Air National Guard Base in Cape Cod, Massachusetts, in pursuit of Flight 175, the second plane to be hijacked (see 8:46 a.m. September 11, 2001 and 8:53 a.m. September 11, 2001). However, Weaver says, the FAA had only told NEADS that “there was an airplane that had a problem,” and at that time it was unclear if Flight 175 had been hijacked. He says that although the fighters flew at over 500 miles per hour, they were unable to catch up with Flight 175 before it hit the South Tower of the WTC at 9:03 a.m. (see 9:03 a.m. September 11, 2001).
More Fighters Were Launched Just before Pentagon Was Hit - Weaver says Flight 77, the third aircraft to be hijacked, flew west for 45 minutes and then turned east, and its transponder was turned off. He does not claim that the military received notice that it had been hijacked, but says NEADS scrambled F-16 fighters that were on alert at Langley Air Force Base in Virginia at 9:35 a.m. (see 9:24 a.m. September 11, 2001 and (9:25 a.m.-9:30 a.m.) September 11, 2001). Two minutes later, at 9:37 a.m., the Pentagon was hit (see 9:37 a.m. September 11, 2001). The F-16s, he says, subsequently remained on patrol over the Pentagon.
No Fighters Took Off to Intercept Flight 93 - Weaver says no fighters were scrambled to chase after Flight 93, the fourth hijacked plane, which crashed in a field in Pennsylvania (see (10:03 a.m.-10:10 a.m.) September 11, 2001 and (10:06 a.m.) September 11, 2001). “There was no notification for us to launch airplanes,” he tells the reporters. “We weren’t even close.” [Dallas Morning News, 9/14/2001; Farmer, 2009, pp. 244] (However, also on this day, Deputy Defense Secretary Paul Wolfowitz contradicts Weaver’s claim. He tells PBS’s NewsHour, “[W]e were already tracking in on that plane that crashed in Pennsylvania,” and adds, “[T]he Air Force was in a position to do so [i.e. shoot Flight 93 down] if we had had to.” [NewsHour with Jim Lehrer, 9/14/2001; Farmer, 2009, pp. 245] ) Weaver says that even if fighters had caught up with the hijacked planes, they may have been unable to stop them reaching their targets. “You’re not going to get an American pilot shooting down an American airliner,” he says. “We don’t have permission to do that.” According to Weaver, only the president can issue an order to shoot down an American airliner. [Dallas Morning News, 9/14/2001]
Weaver's Account Is the 'Most Accurate' Prior to the 9/11 Commission's Investigation - The account he gives to reporters today, according to John Farmer, the senior counsel to the 9/11 Commission, will be “the last public statement uttered by General Weaver on the subject and proved to be the most accurate account of events issued until the 9/11 Commission’s investigation.” [Farmer, 2009, pp. 245] Apparently after Weaver issues his statement to the reporters, an Air Force spokesman, speaking on condition of anonymity, adds that no regular Air Force planes were scrambled during the 9/11 attacks, “because continental air defense is the mission of the Air National Guard.” He says regular Air Force fighters “have air superiority as their mission,” which means they train “to deploy somewhere where we are engaged in hostile action and secure the skies.” These fighters, according to the spokesman, “ordinarily are not ready to fly on short notice and their pilots are not on standby to defend the United States.” [Dallas Morning News, 9/14/2001]
Pentagon Has Been Slow to Answer Questions about Response to Hijackings - The Washington Post will comment, “Questions about the time it took US military planes to respond to the threat of several hijacked aircraft speeding toward the nation’s financial and military centers have dogged the Pentagon since the attacks.” It will add, “Top Pentagon officials 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] The previous day, Air Force General Richard Myers was questioned about the military’s response to the 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] NORAD will release its own timeline of the events of September 11 and its response to the hijackings on September 18 (see September 18, 2001). [North American Aerospace Defense Command, 9/18/2001; 9/11 Commission, 7/29/2004]

Entity Tags: US Department of the Air Force, Paul Wolfowitz, Paul Weaver

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

David Brant, the head of the Naval Criminal Investigative Service (NCIS), learns of the horrific abuse of a Saudi detainee, Mohamed al-Khatani (sometimes spelled “al-Qahtani”—see February 11, 2008), currently detained at Guantanamo Bay. Al-Khatani is one of several terror suspects dubbed the “missing 20th hijacker”; according to the FBI, al-Khatani was supposed to be on board the hijacked aircraft that crashed in a Pennsylvania field on 9/11 (see (10:06 a.m.) September 11, 2001). Al-Khatani was apprehended in Afghanistan a few months after the terrorist attacks. He is one of the examples of prisoner abuse (see August 8, 2002-January 15, 2003) that Brant takes to Naval General Counsel Alberto Mora (see December 17-18, 2002). In 2006, Brant will say that he believes the Army’s interrogation of al-Khatani was unlawful. If any NCIS agent had engaged in such abuse, he will say, “we would have relieved, removed, and taken internal disciplinary action against the individual—let alone whether outside charges would have been brought.” Brant fears that such extreme methods will taint the cases to be brought against the detainees and undermine any efforts to prosecute them in military or civilian courts. Confessions elicited by such tactics are unreliable. And, Brant will say, “it just ain’t right.” [New Yorker, 2/27/2006]

Entity Tags: David Brant, Alberto Mora, Naval Criminal Investigative Service, Federal Bureau of Investigation, Mohamed al-Khatani

Timeline Tags: Torture of US Captives, Civil Liberties

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

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

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The cockpit voice recorder tape from United 93, which crashed in Shanksville, Pennsylvania (see (10:06 a.m.) September 11, 2001), is played at the trial of Zacarias Moussaoui (see March 6-May 4, 2006) just before the prosecution rests its case. Translations are displayed on a screen along with information taken from the plane’s flight data recorder, such as speed, altitude, and steering yoke position. [Associated Press, 4/12/2006; London Times, 4/12/2006] The recording is sealed by the judge and a transcript is made available to the public. [US District Court for the Eastern District of Virginia, Alexandria Division, 7/31/2006] This is a big media event and it receives lots of coverage. CNN, for example, calls it “an absolutely spellbinding, unforgettable day in court.” Many of the passages are unintelligible, but the recording seems to indicate that the hijackers murdered a flight attendant. [CNN, 4/12/2006; US District Court for the Eastern District of Virginia, Alexandria Division, 7/31/2006 pdf file] Some of the victims’ relatives previously heard the recording at a private meeting (see April 18, 2002).

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