!! History Commons Alert, Exciting News

Context of '10:10 a.m.-10:11 a.m. September 11, 2001: Dispatcher Tells Flight 93 Not to Divert to Washington'

This is a scalable context timeline. It contains events related to the event 10:10 a.m.-10:11 a.m. September 11, 2001: Dispatcher Tells Flight 93 Not to Divert to Washington. 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.

Shortly before Flight 93 reverses direction and heads east, someone in its cockpit radios in and asks the FAA for a new flight plan, with a final destination of Washington, DC. [ABC News, 9/11/2001; ABC News, 9/14/2001] Jeff Krawczyk, the chief operating officer of a company that tracks aircraft movements, later comments, “We hardly ever get a flight plan change. Very unusual.” [Washington Business Journal, 9/11/2001] Who it is that makes this request is unclear. The hijacker takeover of Flight 93 occurred around 9:28 a.m. (see (9:28 a.m.) September 11, 2001) [9/11 Commission, 7/24/2004, pp. 11] , so it is presumably made by one of the hijackers. Twenty-five minutes later the pilot hijacker will also program a new destination into the plane’s navigational system (see 9:55 a.m. September 11, 2001).

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

The hijacker pilot of Flight 93 (presumably Ziad Jarrah) reprograms the plane’s navigational system for a new destination. He dials in the navigational code for Washington’s Reagan National Airport, which is just four miles from the White House, and an arrival time of 10:28 a.m. The 9/11 Commission will say this further indicates that the plane’s intended target is the nation’s capital. [Longman, 2002, pp. 78, 182; 9/11 Commission, 7/24/2004, pp. 457; 9/11 Commission, 8/26/2004, pp. 45] A minute later, an air traffic controller at the FAA’s Cleveland Center will enter a revised flight plan for Flight 93 into the FAA computer system, giving a new destination of Reagan Airport, although the reason she does this is unclear (see 9:56 a.m. September 11, 2001). [Federal Aviation Administration, 9/11/2001; St. Petersburg Times, 9/12/2001; 9/11 Commission, 10/2/2003 pdf file] Twenty-five minutes earlier, at 9:30 a.m., someone in Flight 93’s cockpit had radioed in and requested a new flight plan from the FAA, with a final destination of Washington (see 9:30 a.m. September 11, 2001). [ABC News, 9/14/2001]

Entity Tags: Ziad Jarrah

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

United Airlines official Sandy Rogers calls Ellen King at the FAA’s Command Center to discuss Flight 93. The timing of the call is not known specifically, although it appears to be after the Pentagon was hit and could not be long after Flight 93 is thought to have crashed, which is 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). Rogers tells King that Flight 93 has been hijacked, and King responds, “Oh God… thank you,” indicating she was previously unaware of the hijacking. However, the FAA had been aware of the situation since a few minutes after the hijacking took place (see (9:33 a.m.) September 11, 2001 and 9:34 a.m. September 11, 2001). Rogers also says: “It’s over Hagerstown now and you’re not aware of it. It’s heading toward Washington, DC, and we are under a threat of a hijacking on board and this flight is out of our control now heading toward Washington, DC.” Rogers states that United Airlines is “advising the military” about the plane and King also says that the FAA will do the same. [Federal Aviation Administration, 10/14/2003, pp. 37-39 pdf file] However, there are no other reports of Flight 93 ever being over Hagerstown, which is in Maryland. Flight 93 is said to crash in Shanksville, Pennsylvania, and is thought never to reach Maryland. There will be some—apparently mistaken—reports that the plane is still airborne after it is thought to have crashed (see (Between 10:10 a.m. and 10:15 a.m.) September 11, 2001 and 10:10 a.m.-10:11 a.m. September 11, 2001), and this may be another such report.

Entity Tags: Federal Aviation Administration, Ellen King, United Airlines, Sandy Rogers

Timeline Tags: Complete 911 Timeline

Hank Krakowski.Hank Krakowski. [Source: Unisys]After seeing Flight 93’s radar track stopping over Pennsylvania, a senior United Airlines official contacts an airport in that area and receives confirmation of what appears to be an airplane crash nearby. Along with other United Airlines managers, Hank Krakowski, United’s director of flight operations, has just been watching Flight 93 on a large screen in the crisis center at the airline’s headquarters, outside Chicago (see (9:36 a.m.-10:06 a.m.) September 11, 2001). A dispatcher has determined the plane’s last position was south of Johnstown, Pennsylvania, so Krakowski tries phoning the Johnstown airport. However, due to an apparent power failure, there is no reply. He has to call the airport manager’s cell phone number. He asks the manager: “We might have a plane down in your area there. See anything unusual?” The manager reports a black smoke plume visible about 30 miles to the south of the airport. Krakowski thinks, “We just watched one of our airplanes crash.” [Longman, 2002, pp. 214; USA Today, 8/13/2002] Therefore, by 10:15 a.m. according to the 9/11 Commission, United Airlines headquarters has “confirmed that an aircraft [has] crashed near Johnstown, Pennsylvania, and [it] believed that this was Flight 93.” [9/11 Commission, 8/26/2004, pp. 47]

Entity Tags: United Airlines, Hank Krakowski

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Unaware the aircraft has crashed, United Airlines flight dispatcher Ed Ballinger instructs Flight 93 not to divert to Washington. At 10:10, he sends a text message to Flight 93, stating: “Don’t divert to DC. Not an option.” A minute later, he resends this same message to it. [9/11 Commission, 1/27/2004; 9/11 Commission, 8/26/2004, pp. 46] Someone on Flight 93 had contacted the FAA at 9:30, requesting a new flight plan with the destination of Washington (see 9:30 a.m. September 11, 2001), and at 9:55 the pilot hijacker reprogrammed the plane’s navigational system for the new destination of Washington’s Reagan National Airport (see 9:55 a.m. September 11, 2001). United Airlines will not confirm that Flight 93 has crashed until around 10:15 (see (10:07 a.m.-10:15 a.m.) September 11, 2001), and will notify its employees of this at 10:17 (see 10:17 a.m. September 11, 2001).

Entity Tags: Ed Ballinger

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Andy Studdert, the chief operating officer of United Airlines, sends out an operational alert message to the airline’s personnel, informing them of the crash of Flight 93. The message states: “UAL 93-11 EWR-SFO has been involved in an accident. Crisis center has been activated.” [9/11 Commission, 8/26/2004, pp. 47] Along with other United Airlines managers, Studdert watched Flight 93’s radar track as it came to a halt on a screen in the airline’s crisis center, at its headquarters outside Chicago (see (9:36 a.m.-10:06 a.m.) September 11, 2001). By 10:15, United had learned from the manager of the Johnstown airport in Pennsylvania of a plume of smoke rising up in the area where Flight 93 crashed (see (10:07 a.m.-10:15 a.m.) September 11, 2001). [Longman, 2002, pp. 77 and 214]

Entity Tags: Andrew P. Studdert, United Airlines

Timeline Tags: Complete 911 Timeline, 9/11 Timeline


Time period

Email Updates

Receive weekly email updates summarizing what contributors have added to the History Commons database


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


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