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]
9:44 a.m.-9:51 a.m. September 11, 2001: Pittsburgh Airport Control Tower Evacuated due to Concerns over Approaching Flight 93
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 
; Pittsburgh Post-Gazette, 9/23/2001; Federal Aviation Administration, 3/21/2002, pp. 11-13; 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] 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 ; 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 ] 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 ; Federal Aviation Administration, 3/21/2002, pp. 12-13] 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]
Shortly After 9:44 a.m. September 11, 2001: Change of Course and Pilot’s Failure to Respond to Message Lead Cleveland Center to Again Suspect Delta 1989 Is Hijacked
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]
9:45 a.m. September 11, 2001: NEADS Tells FAA’s Cleveland Center that Delta 1989 Is a Confirmed Hijack, Controller Disagrees
The FAA’s Cleveland Center receives a call from NORAD’s Northeast Air Defense Sector (NEADS), incorrectly notifying it that Delta Air Lines Flight 1989 is a confirmed hijacking. A supervisor then rushes around the center, informing all the controllers and managers of this. [9/11 Commission, 10/2/2003 ; 9/11 Commission, 10/2/2003 ; 9/11 Commission, 2004]
Cleveland Realized Delta 1989 Not Hijacked – At around 9:30 a.m., Cleveland Center air traffic controllers heard the sounds from Flight 93 as it was being hijacked, but initially thought these came from Delta 1989 (see (9:28 a.m.-9:33 a.m.) September 11, 2001). [USA Today, 8/13/2002] Due to the Delta pilots’ normal responses to subsequent radio transmissions, John Werth—the controller monitoring both flights—concluded that the hijacked aircraft was in fact Flight 93. [9/11 Commission, 10/1/2003 ; USA Today, 9/11/2008] However, at around 9:39, the FAA’s Boston Center guessed that Delta 1989 might be hijacked and called NEADS to report the plane as a possible hijacking (see 9:39 a.m. September 11, 2001). [9/11 Commission, 2004; 9/11 Commission, 7/24/2004, pp. 28] NEADS then begins alerting FAA centers of this. [Vanity Fair, 8/1/2006]
NEADS Calls Cleveland Center – Greg Dukeman, the military operations specialist in the traffic management unit at Cleveland Center, receives a call from a female member of staff at NEADS, one of its ID technicians. He passes the call on to supervisor Kim Wernica. The caller says Delta 1989 is “a confirmed hijack.” Wernica then goes “running back and forth” around the center, informing controllers and managers of what she has been told. [North American Aerospace Defense Command, 9/11/2001; 9/11 Commission, 10/2/2003 ; 9/11 Commission, 10/2/2003 ; 9/11 Commission, 2004]
Controller Disputes NEADS’s Information – Wernica rushes up to John Werth and tells him, “It’s the Delta, it’s the Delta!” She says a military liaison on the phone has confirmed that the Delta jet has been hijacked. Werth responds that he is pretty sure that Flight 93, not Delta 1989, has been hijacked. When Wernica returns a few moments later, Werth tells her that Delta 1989 is “fine—at least for now.” Wernica consults again on the phone and then comes back, saying, “They said it’s a confirmed hijack and a bomb threat.” Werth thinks to himself that the bomb threats had come from Flight 93 (see (9:32 a.m.) September 11, 2001 and (9:39 a.m.) September 11, 2001), and is therefore convinced the caller must be confusing the two flights. He tells Wernica, “Tell them they’re full of it!” [9/11 Commission, 10/1/2003 ; USA Today, 9/11/2008]
9:53 a.m. September 11, 2001: Emergency Transmitter Goes Off, Indicating a Plane Crash in Michigan
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 ]
9:56 a.m. September 11, 2001: Air Traffic Controller Changes Flight 93’s Destination to Washington
An air traffic controller at the FAA’s Cleveland Center enters a new flight plan for Flight 93 into the FAA computer system, giving a new destination of Reagan National Airport in Washington, DC. Flight 93 is currently flying in the airspace covered by the Cleveland Center’s Imperial Sector radar position, which is being managed by controller Linda Justice. [Federal Aviation Administration, 9/11/2001; St. Petersburg Times, 9/12/2001; 9/11 Commission, 10/2/2003 ; Lynn Spencer, 2008]
Controller Enters New Flight Plan for Flight 93 – Justice changes the flight’s destination code from “SFO,” the code for San Francisco International Airport, to “DCA,” the code for Ronald Reagan Washington National Airport. [St. Petersburg Times, 9/12/2001] An FAA chronology will specify that she changes the flight plan “direct HGR [the code for Hagerstown Regional Airport in Maryland] to DCA.” [Federal Aviation Administration, 9/11/2001] Another FAA chronology will similarly state that Justice reroutes Flight 93 “direct to Hagerstown direct to Washington National.” [Federal Aviation Administration, 12/6/2001] Flight 93’s tag therefore now reads, “Hagerstown—National,” according to Justice. [9/11 Commission, 10/2/2003 ]
New Flight Plan Not Due to Communication with Pilot – The reason Justice enters a new flight plan for Flight 93 is unclear. A minute earlier, the hijacker pilot on Flight 93 reprogrammed the plane’s navigational system for the new destination of Reagan Airport (see 9:55 a.m. September 11, 2001). [Longman, 2002, pp. 182; 9/11 Commission, 7/24/2004, pp. 457] And according to the St. Petersburg Times, controllers typically only change a plane’s destination when this is requested by the pilots. [St. Petersburg Times, 9/12/2001] But one of the FAA chronologies will state that Justice’s change to the flight plan is “not a result of any communication with the pilot.” [Federal Aviation Administration, 9/11/2001]
Flight Plan Changed to Aid Handoff to Washington Controllers – Justice will later explain why she changes the flight plan. She will state that Flight 93 appears to be heading toward the airspace of the FAA’s Washington Center, and so, in “an attempt to expedite the situation,” she enters the change of routing to reflect Hagerstown Airport to Reagan Airport. She will say she does this “only to forward [the] information [about Flight 93] to the sectors the aircraft appeared to be tracking toward.” [Federal Aviation Administration, 9/12/2001 ] Justice will tell the 9/11 Commission that she changes the routing when she sees Flight 93 is heading eastbound. She will say, “The easiest way to do a handoff is to change the flight plan,” and also say she changes the flight plan “to show that Washington Center was the recipient.” According to Justice, the “controversial step” she takes is “putting in Hagerstown, because the misconception was that she had communicated with the plane and cleared it through.” [9/11 Commission, 10/2/2003 ] John Werth, another controller at the Cleveland Center, will tell the 9/11 Commission that Justice enters the new destination for Flight 93 “because she knew it would be easier to track the primary [radar track for the aircraft] when the computer has a flight plan to work with.” [9/11 Commission, 10/1/2003 ] After changing the flight plan, Justice calls the Potomac Sector radar position at the Washington Center and tells the controller there to “pull up the data block” for Flight 93. Justice will say it is clear to the Washington Center controller that she has created the new destination in order to make it easier to locate the plane. [Federal Aviation Administration, 9/12/2001 ; 9/11 Commission, 10/2/2003 ]
New Flight Plan Causes False Reports of Plane Approaching Washington – According to author Lynn Spencer, the new flight plan creates a “coast track” of Flight 93 on the traffic situation displays at air traffic control facilities. “A coast track,” Spencer will write, “differs from a radar track in that it is not supported by radar returns but rather by a computer-generated, projected course for the flight. Although this track did not appear on controller radar screens, its presence on their [traffic situation displays] allowed Washington controllers to monitor the flight’s progression toward Washington.” According to Spencer, the presence of this coast track leads to incorrect reports of an aircraft approaching Washington in the minutes after Flight 93 crashes. She will write, “A controller in Washington, unaware that the flight had crashed, was calling position reports for the coast track of United 93 to the White House (see (Between 10:10 a.m. and 10:18 a.m.) September 11, 2001)… as well as the FBI at the Pentagon (where firefighters were evacuated and the firefight suspended in anticipation of a second impact)” (see (10:15 a.m.-10:38 a.m.) September 11, 2001). [Lynn Spencer, 2008]
9:56 a.m.-10:29 a.m. September 11, 2001: Selfridge Jets Apparently Not Instructed to Intercept Suspicious Plane as NEADS Wants, Return to Base Instead
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 ; 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 ] 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 ; 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 ; 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 ] 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 ; Mount Clemens-Clinton-Harrison Journal, 9/6/2006]
10:02 a.m. September 11, 2001: Flight 93’s Transponder Briefly Comes Back On
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 ; 9/11 Commission, 10/2/2003 ]
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 ] 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]
10:05 a.m.-10:08 a.m. September 11, 2001: NEADS Alerted to Flight 93, Reportedly for the First Time
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 ; US Department of Defense, 6/1/2001 ]
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 ; 9/11 Commission, 1/23/2004 ] 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]
Before 10:07 a.m. September 11, 2001: Military Liaison Learns of Hijacking of Flight 93
The military liaison at the FAA’s Cleveland Center is informed that Flight 93 has been hijacked and is given information about its location. It is unclear when the liaison first receives this information, but it must happen before 10:07, as he telephones NORAD’s Northeast Air Defense Sector (NEADS) at this time to pass on the information (see 10:05 a.m.-10:08 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 30] Military liaison officers at the FAA’s Command Center are also said to be informed of the hijacking of Flight 93 (see After 9:34 a.m. September 11, 2001).
