Context of '9:24 a.m.-9:25 a.m. September 11, 2001: Flight 93 Checks in with Cleveland Air Traffic Control, Mentions No Problems'

This is a scalable context timeline. It contains events related to the event 9:24 a.m.-9:25 a.m. September 11, 2001: Flight 93 Checks in with Cleveland Air Traffic Control, Mentions No Problems. 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.

Melodie Homer.Melodie Homer. [Source: Jim Varhegyi]The United Airlines Operations Center at JFK Airport in New York sends a text message to LeRoy Homer, the co-pilot of Flight 93, but receives no response from him. [9/11 Commission, 8/26/2004, pp. 37 pdf file] At 9:10, Melodie Homer, the wife of LeRoy Homer, contacts the operations center after seeing the second plane hitting the World Trade Center on television. Knowing her husband is flying, she requests that a message be sent to him, stating, “Your wife just wants to make sure you’re okay.” [Pittsburgh Channel, 9/19/2001; Longman, 2002, pp. 78; New York Observer, 2/15/2004; Discovery Channel, 2005] Melodie is told, “If you want to hang on, we’ll get a message back in a couple of minutes.” According to journalist and author Jere Longman, after no response is received, a second text message is sent. Although Melodie Homer’s message is later determined to have been received by the flight, there is still no reply. [Longman, 2002, pp. 81-82] However, the 9/11 Commission will only describe one message—not two—being sent to Homer, which it says happens at 9:22. [9/11 Commission, 7/24/2004, pp. 456; 9/11 Commission, 8/26/2004, pp. 37 pdf file] The hijacking of Flight 93 is believed to take place at 9:28 (see (9:28 a.m.) September 11, 2001). [9/11 Commission, 7/24/2004, pp. 11] A text message sent by an airline dispatcher to Flight 93’s pilot Jason Dahl shortly before the hijacking will receive a response from him three minutes later (see 9:23 a.m.-9:26 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 37-38 pdf file]

Entity Tags: United Airlines, Melodie Homer, LeRoy Homer

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 pdf file] 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

Shortly after he learns a second plane has hit the World Trade Center, United Airlines flight dispatcher Ed Ballinger takes the initiative to begin sending a warning message to the flights he is monitoring, including Flight 93 and Flight 175 (although this aircraft has already crashed). [9/11 Commission, 7/24/2004, pp. 11; 9/11 Commission, 8/26/2004, pp. 26 and 37 pdf file] Ballinger is responsible for monitoring United’s aircraft flying from the East Coast to the West Coast. He has 16 such flights he is in charge of. [Chicago Daily Herald, 4/14/2004] He sends out a text message to his airborne flights: “Beware any cockpit intrusion… Two aircraft in NY hit [World] Trade Center builds.” [9/11 Commission, 7/24/2004, pp. 11; 9/11 Commission, 8/26/2004, pp. 26 pdf file] Although United Airlines has suspected Flight 175 as being hijacked since around 9:00 a.m. (see Shortly Before 9:00 a.m. September 11, 2001), Ballinger is still responsible for multiple flights. (In contrast to United, American Airlines has a policy that flight dispatchers should only manage the hijacked flight, and be relieved of responsibility for their other flights.) [9/11 Commission, 7/24/2004, pp. 455-456] Ballinger’s warning is therefore sent out to his aircraft in groups, and will not be sent to Flight 93 until 9:23 a.m. (see 9:23 a.m.-9:26 a.m. September 11, 2001). Unaware that it was the second plane that hit the WTC, Ballinger will also send the message to Flight 175 (see 9:23 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 26 and 37 pdf file] Ballinger begins sending out these warnings two minutes before United Airlines instructs its dispatchers to warn their flights to secure their cockpit doors (see 9:21 a.m. September 11, 2001). [9/11 Commission, 1/27/2004; 9/11 Commission, 7/24/2004, pp. 455] According to the 9/11 Commission, his text message represents “the first occasion on 9/11 when either American or United sent out such a warning to their airborne aircraft.” [9/11 Commission, 8/26/2004, pp. 37 pdf file] Ballinger will later recall: “As soon as I had a grasp of what was going on… I sent [the warning] out immediately. It was before [Transportation Secretary Norman] Mineta, and even before the airlines told us to alert the crews.” [Chicago Daily Herald, 4/14/2004]

Entity Tags: Ed Ballinger

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

United Airlines issues a companywide order for its flight dispatchers to warn their flights to secure their cockpit doors. [9/11 Commission, 1/27/2004; 9/11 Commission, 7/24/2004, pp. 455] The airline’s air traffic control coordinator sends a message to all of the airline’s dispatchers, telling them: “There may be addnl [additional] hijackings in progress. You may want to advise your flts [flights] to stay on alert and shut down all cockpit access inflt [in flight]. Sandy per Mgmt.” United Airlines dispatchers began notifying their aircraft that planes had crashed into the World Trade Center at 9:03 (see 9:03 a.m. and After September 11, 2001). However, with the exception of one dispatcher (see 9:19 a.m. September 11, 2001), the airline has so far not sent any warnings to its aircraft. [9/11 Commission, 8/26/2004, pp. 36-37 pdf file] United Airlines did not initially realize the second plane to hit the WTC was one of its own (see Between 9:10 a.m. and 9:20 a.m. September 11, 2001), and it is not until 9:22 that it notifies its dispatchers that UAL Flight 175 has been involved in “an accident” in New York (see 9:22 a.m. September 11, 2001).

Entity Tags: United Airlines

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Ed Ballinger, the United Airlines flight dispatcher monitoring Flight 93, sends a warning message to this flight, telling the pilots to beware of any cockpit intrusion. [9/11 Commission, 7/24/2004, pp. 11] At 9:21, United Airlines instructed its dispatchers to warn their flights to secure their cockpit doors (see 9:21 a.m. September 11, 2001), but Ballinger had already taken the initiative two minutes earlier to begin warning the 16 flights he is monitoring (see 9:19 a.m. September 11, 2001). His text message reads: “Beware any cockpit intrusion… Two aircraft in NY hit [World] Trade Center builds.” Because this message is sent out to Ballinger’s 16 aircraft in groups, it is not until 9:23 a.m. that it is transmitted to Flight 93. [9/11 Commission, 1/27/2004; 9/11 Commission, 8/26/2004, pp. 26 and 37 pdf file] The warning is received in the plane’s cockpit one minute later. [9/11 Commission, 7/24/2004, pp. 11] Then, at 9:26, Flight 93 pilot Jason Dahl responds with the text message, “Ed confirm latest mssg plz [message please]—Jason.” Apart from a routine radio contact with the FAA’s Cleveland Center a minute later (see 9:27 a.m. September 11, 2001), this is the last normal communication made from Flight 93’s cockpit before the hijacking occurs. [9/11 Commission, 8/26/2004, pp. 38 pdf file] Ballinger will later complain: “One of the things that upset me was that they knew 45 minutes before that American Airlines [Flight 11] had a problem. I put the story together myself [from news accounts]. Perhaps if I had the information sooner, I might have gotten the message to [Flight] 93 to bar the door.” [Chicago Daily Herald, 4/14/2004]

Entity Tags: Jason Dahl, Ed Ballinger

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Having entered the center’s airspace, Flight 93 establishes radio contact with the FAA’s Cleveland Center, a regional air traffic control center that guides long-range, high altitude flights. The pilot reports simply that his flight is experiencing intermittent light choppy air, and does not indicate there being any problems on board, saying, “Good morning Cleveland, United 93 with you at three-five-oh [35,000 feet], intermittent light chop.” The controller, John Werth, is busy with other flights, so does not initially respond. A minute later, Flight 93 radios again, “United 93 checking in three-five-oh.” Werth replies, “United 93, three-five-zero, roger.” [Gregor, 12/21/2001 pdf file; Longman, 2002, pp. 69; 9/11 Commission, 8/26/2004, pp. 37 pdf file; CBS News, 9/10/2006] Two minutes later, Flight 93 will make its final radio communication before the hijacker takeover occurs (see 9:27 a.m. September 11, 2001).

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Flight 93 makes its last normal communication with air traffic control before being hijacked, acknowledging a routine radio transmission from the FAA’s Cleveland Center. [9/11 Commission, 7/24/2004, pp. 28] Flight 93 checked in with the Cleveland Center a couple of minutes earlier (see 9:24 a.m.-9:25 a.m. September 11, 2001). At 9:27, the Cleveland controller, John Werth, alerts it to another aircraft 12 miles away and to its right, at 37,000 feet: “United 93, that traffic for you is one o’clock, 12 miles east, bound three-seven-zero.” Seconds later, Flight 93 responds, “Negative contact, we’re looking, United 93.” Less than a minute after this, the hijackers appear to enter Flight 93’s cockpit (see (9:28 a.m.) September 11, 2001). [Gregor, 12/21/2001 pdf file; Longman, 2002, pp. 69; CBS News, 9/10/2006]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Jason Dahl.Jason Dahl. [Source: Publicity photo]According to the 9/11 Commission, less than a minute after Flight 93 acknowledged a routine radio transmission from the FAA’s Cleveland Center (see 9:27 a.m. September 11, 2001), John Werth—the controller handling the flight—and pilots of other aircraft in the vicinity of Flight 93 hear “a radio transmission of unintelligible sounds of possible screaming or a struggle from an unknown origin.” [Federal Aviation Administration, 9/11/2001; 9/11 Commission, 6/17/2004; CBS News, 9/10/2006] Someone, presumably Flight 93’s pilot Jason Dahl, is overheard by controllers as he shouts, “Mayday!” [New York Times, 7/22/2004] Seconds later, the controller responds, “Somebody call Cleveland?” Then there are more sounds of screaming and someone yelling, “Get out of here, get out of here.” [Toronto Sun, 9/16/2001; Newsweek, 9/22/2001; Observer, 12/2/2001; MSNBC, 7/30/2002; 9/11 Commission, 6/17/2004] Then the voices of the hijackers can be heard talking in Arabic. The words are later translated to show they are talking to each other, saying, “Everything is fine.” [Newsweek, 12/3/2001] Later, passenger phone calls will describe two dead or injured bodies just outside the cockpit; presumably these are the two pilots. [New York Times, 7/22/2004]

Entity Tags: Cleveland Air Route Traffic Control Center, John Werth, 9/11 Commission, Jason Dahl

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

The FAA’s Cleveland Center notifies United Airlines’ headquarters, near Chicago, that Flight 93 is not responding to attempted radio contacts. [9/11 Commission, 8/26/2004, pp. 39 pdf file] Cleveland Center made its last normal communication with Flight 93 at 9:27 (see 9:27 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 28] After the hijacking began at around 9:28, the controller handling Flight 93, John Werth, tried unsuccessfully to re-establish contact with it. [Gregor, 12/21/2001 pdf file; CBS News, 9/10/2006] The lack of response from Flight 93, combined with the plane’s turning to the east (see (9:36 a.m.) September 11, 2001), will lead United to believe, by 9:36 a.m., that it has been hijacked. [9/11 Commission, 7/24/2004, pp. 456]

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

After United Airlines learns that Flight 93 is not responding to air traffic controllers, it notifies its flight dispatchers of this, and two of its employees try to contact the flight. At about 9:30, the FAA’s Cleveland Center informed the United Airlines headquarters, near Chicago, that Flight 93 was not responding to attempted radio contacts (see (9:30 a.m.) September 11, 2001). At 9:31, officials at the headquarters inform the airline’s dispatchers—who are responsible for monitoring aircraft in flight—that there is a potential problem with Flight 93. Over the next minute, United’s air traffic control coordinator and another of its employees each send a text message to Flight 93, stating, “ATC looking for you on 133.37.” Flight 93 does not respond to these or any subsequent text messages. [9/11 Commission, 1/27/2004; 9/11 Commission, 8/26/2004, pp. 39 pdf file]

Entity Tags: United Airlines

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Having followed a seemingly normal course until now, after reaching the Cleveland area, Flight 93 suddenly makes a sharp turn to the south. It then makes another turn back eastward, cutting through West Virginia’s Northern Panhandle before re-entering Pennsylvania. [Washington Post, 9/12/2001; Pittsburgh Post-Gazette, 9/13/2001; 9/11 Commission, 8/26/2004, pp. 41 pdf file] Having thus turned 180 degrees, it now heads toward Washington, DC. [CNN, 9/13/2001]

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

United Airlines flight dispatcher Ed Ballinger sends two messages to Flight 93, which he is monitoring, warning its pilots (who in fact are no longer in control of the plane) to secure the cockpit. At 9:40, he sends the text message to Flight 93: “High security alert. Secure cockpit. Two airliner hit NY Trade Center. And 1 aircraft in IAD missing. And one in EWR missing… too. UAL 175/93 missing.” A minute later, he again sends this message to Flight 93, but with “UAL 175/93 found” added at the end. [9/11 Commission, 8/26/2004, pp. 43 pdf file] “IAD” is the code for Washington’s Dulles International Airport, from where Flight 77 took off, while “EWR” is the code for Newark Airport, from where Flight 93 took off, so presumably it is these missing aircraft that Ballinger is referring to. [Federal Aviation Administration, 9/17/2001 pdf file] Ballinger sent previous warning messages to Flight 93 earlier on, telling it to “Beware any cockpit intrusion” at 9:23 (see 9:23 a.m.-9:26 a.m. September 11, 2001), and to “Secure cockpit” at 9:33 (see 9:32 a.m.-9:33 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 37 and 39 pdf file]

Entity Tags: Ed Ballinger

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