At 8:26, Flight 11, which is already way off course, makes an unplanned 100-degree turn to the south over Albany, New York. A minute later, it turns right, to the south-southwest. Then, two minutes on, at 8:29, it turns left to the south-southeast. Boston air traffic controllers never lose sight of the flight, though they can no longer determine altitude as the transponder is turned off. Its last known altitude was 29,000 feet. [Christian Science Monitor, 9/13/2001; Federal Aviation Administration, 9/17/2001 
; National Transportation Safety Board, 2/19/2002 ; MSNBC, 9/11/2002] Before this turn, the FAA had tagged Flight 11’s radar dot for easy visibility and, at American Airlines’ System Operations Control (SOC) in Fort Worth, Texas, “All eyes watched as the plane headed south. On the screen, the plane showed a squiggly line after its turn near Albany, then it straightened.” [Wall Street Journal, 10/15/2001] Boston air traffic controller Mark Hodgkins later says, “I watched the target of American 11 the whole way down.” [ABC News, 9/6/2002] However, apparently, NORAD’s Northeast Air Defense Sector (NEADS) has different radar. When they are finally told about the flight, they cannot find it (see Shortly After 8:37 a.m. September 11, 2001). NEADS has to repeatedly phone the FAA, airlines, and others, for clues as to the plane’s location. NEADS will eventually focus on a radar blip they believe might be Flight 11, and watch it close in on New York. [Newhouse News Service, 1/25/2002; Aviation Week and Space Technology, 6/3/2002; ABC News, 9/11/2002]
8:28 a.m. September 11, 2001: FAA Command Center Informed of Flight 11 Hijacking, Establishes Teleconference between Air Traffic Control Centers
The FAA’s Boston Center calls the FAA Command Center and says it believes Flight 11 has been hijacked and is heading toward the New York Center’s airspace. The Command Center immediately establishes a teleconference between the Boston, New York, and Cleveland air traffic control centers, so Boston can help the other centers understand what is happening, in case Flight 11 should enter their airspace. Minutes later, in line with the standard hijacking protocol, the Command Center will pass on word of the suspected hijacking to the FAA’s Washington headquarters (see 8:32 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 19; 9/11 Commission, 8/26/2004, pp. 11; Spencer, 2008, pp. 21]
National Operations Manager Learns of Hijacking – A supervisor at the Command Center promptly passes on the news of the possible hijacking to Ben Sliney, who is on his first day as the national operations manager there. The supervisor says the plane in question is “American Flight 11—a 767 out of Boston for Los Angeles.” According to author Lynn Spencer, “Sliney flashes back to the routine for dealing with hijackings from the days when they were more common.” The procedure is to “[k]eep other aircraft away from the errant plane. Give the pilots what they need. The plane will land somewhere, passengers will be traded for fuel, and difficult negotiations with authorities will begin. The incident should resolve itself peacefully, although the ones in the Middle East, he recalls, often had a more violent outcome.” Apparently not expecting anything worse to happen, Sliney continues to the conference room for the daily 8:30 staff meeting there (see 8:30 a.m.-8:40 a.m. September 11, 2001).
Command Center a ‘Communications Powerhouse’ – The FAA Command Center is located in Herndon, Virginia, 25 miles from Washington, DC. According to Spencer, it “is a communications powerhouse, modeled after NASA’s Mission Control. The operations floor is 50 feet wide and 120 feet long, packed with tiered rows of computer stations, and at the front, seven enormous display screens show flight trajectories and weather patterns.” The center has nearly 50 specialists working around the clock, planning and monitoring the flow of air traffic over the United States. These specialists work with airlines and air traffic control facilities to fix congestion problems and deal with weather systems. [Spencer, 2008, pp. 1 and 19-20]
8:29 a.m. September 11, 2001: American Airlines Makes First Contact with FAA about Flight 11, Learns Details of Crisis
Bill Halleck, an air traffic control specialist at the American Airlines System Operations Control (SOC) center in Fort Worth, Texas, calls the FAA’s Boston Center to ask about the status of Flight 11 and is told that the plane has deviated from its flight path, air traffic controllers have lost communication with it and have lost its transponder signal, and they have heard a possible threat being made in the background over the radio. This call is American Airlines’ first contact with FAA controllers regarding Flight 11. [9/11 Commission, 3/25/2004, pp. 15; 9/11 Commission, 4/26/2004; 9/11 Commission, 4/26/2004 ]
Manager Told Halleck to Call FAA – At 8:21 a.m., Craig Marquis, the manager on duty at the SOC, received a call from a supervisor at the American Airlines Southeastern Reservations Office in North Carolina, alerting him to a call the office had received from Betty Ong, a flight attendant on Flight 11, reporting the emergency on her plane (see 8:21 a.m. September 11, 2001). Marquis had replied that he would get in touch with air traffic control about this. [9/11 Commission, 8/26/2004, pp. 9] He asked Halleck to contact the FAA’s Boston Center and find out what is happening with Flight 11. Immediately after receiving this request, Halleck calls the traffic management unit (TMU) at the Boston Center. [9/11 Commission, 1/8/2004 ; 9/11 Commission, 4/26/2004 ]
Boston Center Tells Halleck Details of Crisis – When the call is answered, Halleck introduces himself and then says, “[W]e’re trying to find out the status to what you know about our Flight 11.” The Boston Center controller replies that Flight 11’s last reported altitude was below 29,000 feet. He reports that the flight has altered course, saying, “He was heading west, but right now he’s pointed southwest of Albany.” Furthermore, he says, “we lost frequency with him,” meaning communication has been lost with the plane, and adds that the plane’s transponder has been turned off.
Controller Heard a ‘Threat in the Background’ on Flight 11 – The controller at the TMU also tells Halleck that the Boston Center controller dealing with Flight 11 “heard on the frequency a threat in the background, but that’s unconfirmed and we’re trying to pull the tape [recording of the radio communication] at this time.” Halleck asks for clarification that the controller handling Flight 11 “heard a background noise in the cockpit,” and is told: “Like a threat. Yes, sir.” The controller at the TMU adds that he has been told that it is believed the pilot’s microphone on Flight 11 was keyed, and so the controller handling the flight “heard in the background, like, yeah, ‘Return to an airport… or I’ll kill you,’ or something to that effect.” He also says the plane is not squawking any emergency transponder codes. Halleck says he is tracking Flight 11 on the aircraft situation display, and the controller replies that the Boston Center is currently tracking the plane with primary radar only. The controller ends by telling Halleck, “That is all we have.” [American Airlines, 9/11/2001, pp. 56-57; American Airlines, 9/11/2001, pp. 58; 9/11 Commission, 1/8/2004 ]
Halleck Does Not Pass On Information from Flight Attendant – With this call, Halleck is the first person at American Airlines to speak to FAA air traffic control personnel about Flight 11. [9/11 Commission, 4/26/2004; 9/11 Commission, 4/26/2004 ] During the call, he does not tell the Boston Center controller about the ongoing conversation between American Airlines and Ong, or what Marquis has learned from this conversation. [United States District Court for the Southern District of New York, 1/16/2009 ] Halleck will promptly pass on the information from the Boston Center to Marquis, and this will lead American Airlines to suspect that Flight 11 has been hijacked (see 8:33 a.m. September 11, 2001). [9/11 Commission, 8/26/2004, pp. 12]
8:30 a.m. September 11, 2001: Several Senior Members of FAA Staff Away From Base When Attacks Begin
A number of key senior FAA personnel happen to be away from their usual bases this morning, at the time of the attacks. 
Bill Peacock, the FAA director of air traffic services, is in New Orleans for a meeting with the National Air Traffic Controllers Association (NATCA). Among his many duties, Peacock is “the ultimate manager of all the air traffic controllers in the country’s system.” He will be transported from New Orleans later in the day in an FAA business jet, one of the few aircraft permitted to fly, and only arrive at FAA headquarters shortly after 5:00 p.m. [Freni, 2003, pp. 12 and 70] Jack Kies, the FAA’s manager of tactical operations, is in Nashua, New Hampshire for a meeting with representatives of the Canadian air traffic control organization. [Freni, 2003, pp. 65-66] Consequently Linda Schuessler, the deputy director of system operations, has to take his place in charge of the FAA Command Center in Herndon, Virginia. [Federal Aviation Administration, 5/18/2006] Tony Ferrante, the manager of the FAA’s air traffic investigation arm, is in Chicago to testify at a hearing. He will become frustrated later in the day about being stuck there, knowing he should he at his post in Washington gathering forensic data on the hijackings and crashes. [Freni, 2003, pp. 7, 19 and 47-48] Rick Hostetler, a member of the FAA’s planning and procedures organization, is at the dentist’s in Waldorf, Maryland when the attacks begin. His job includes acting as the FAA’s primary air traffic liaison for the Secret Service, the US Special Operations Command, and the Pentagon. After seeing the second WTC tower hit live on television, reportedly while sitting in the dentist’s chair, he will quickly set out for his duty station at the FAA Command Center. But due to the heavy traffic, his journey will take hours and the attacks will be over by the time he gets there. [Freni, 2003, pp. 27, 47 and 90] Mike Canavan, the director of the FAA’s Office of Civil Aviation Security, is visiting the airport in San Juan, Puerto Rico. He will only make it back to Washington in the evening, on a special Army flight. [9/11 Commission, 5/23/2003] As part of his job, Canavan is the FAA’s hijack coordinator, responsible for requesting military assistance in the event of a hijacking (see 8:30 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 17-18] FAA Administrator Jane Garvey is in a breakfast meeting at the Department of Transportation, in Washington, DC. She will quickly relocate to FAA headquarters soon after the first attack (see (8:48 a.m.-9:05 a.m.) September 11, 2001). [Freni, 2003, pp. 62-63]
Whether the absence of these senior personnel impairs the FAA’s ability to respond to the attacks is unknown.
8:30 a.m.-8:40 a.m. September 11, 2001: Managers at FAA Command Center Learn of Flight 11 Hijacking, but Continue with Staff Meeting
Managers at the FAA’s Command Center in Herndon, Virginia, learn of the apparent hijacking of Flight 11, but continue with a meeting they are in for several minutes, until being notified that one of the plane’s flight attendants may have been stabbed. The daily staff meeting among all the department heads at the Command Center begins at 8:30 a.m. Ben Sliney, who is on his first day as national operations manager there, has just been informed of the suspected hijacking of Flight 11 (see 8:28 a.m. September 11, 2001). He begins the meeting by announcing news of the hijacking to the other managers, but then continues with his normal briefing, about the outlook for the coming day’s operations. Sliney is interrupted, apparently at around 8:40 a.m., when a supervisor enters the conference room and whispers to him that the situation with the hijacking has deteriorated: American Airlines has just called, reporting that a flight attendant on the plane may have been stabbed. Deciding he should be on the center’s operations floor rather than in the meeting, Sliney announces to the other managers: “Look, this hijack situation has seriously escalated and I need to get back to the floor. There is an unconfirmed report indicating that a flight attendant may have been stabbed.” He then excuses himself. The meeting is quickly broken up before the first World Trade Center crash occurs at 8:46 a.m. The managers then head to their posts. Despite the “intuitive nature of this group of people,” none of them will initially consider the first WTC crash to be connected to the hijacking they have been informed of. According to Linda Schuessler, the deputy director of system operations at the Command Center, “something that seemed so bizarre as flying a hijacked plane full of people into a skyscraper didn’t seem possible.” [Aviation Week and Space Technology, 12/17/2001; Freni, 2003, pp. 63; Spencer, 2008, pp. 1 and 19-21]
8:32 a.m. September 11, 2001: FAA Headquarters Informed of Flight 11 Hijacking, but Does Not Contact the Pentagon to Request Assistance
Four minutes after it is informed of the suspected hijacking of Flight 11 (see 8:28 a.m. September 11, 2001), the FAA Command Center in Herndon, Virginia, passes on word of the hijacking to the operations center at FAA headquarters in Washington, DC. The headquarters is apparently already aware of the hijacking, as the duty officer who speaks with the Command Center responds that security personnel at the headquarters have just been discussing it on a conference call with the FAA’s New England regional office. [9/11 Commission, 7/24/2004, pp. 19; 9/11 Commission, 8/26/2004, pp. 11] According to the 9/11 Commission, “FAA headquarters is ultimately responsible for the management of the national airspace system,” and the operations center there “receives notifications of incidents, including accidents and hijackings.” FAA headquarters has a hijack coordinator, who is “the director of the FAA Office of Civil Aviation Security or his or her designate.” Procedures require that, if a hijacking is confirmed, the hijack coordinator on duty is “to contact the Pentagon’s National Military Command Center (NMCC) and to ask for a military escort aircraft to follow the flight, report anything unusual, and aid search and rescue in the event of an emergency.” Yet, the Commission will state, although “FAA headquarters began to follow the hijack protocol,” it does “not contact the NMCC to request a fighter escort.” [9/11 Commission, 7/24/2004, pp. 16-19] Mike Canavan, who would normally be the FAA’s hijack coordinator, is away in Puerto Rico this morning, and it is unclear who—if anyone—is standing in for him in this critical role (see 8:30 a.m. September 11, 2001). [9/11 Commission, 5/23/2003; 9/11 Commission, 7/24/2004, pp. 17]
Shortly After 8:37 a.m. September 11, 2001: NEADS Staff Unable to Locate Hijacked Planes on Radar Screens
Members of staff at NORAD’s Northeast Air Defense Sector (NEADS) have difficulty locating Flight 11 and other aircraft on their radar screens. Lt. Col. Dawne Deskins of NEADS will say that when the FAA first calls and reports the first hijacking (see (8:37 a.m.) September 11, 2001), “He [FAA] gave me the latitude and longitude of that track… [but] there was nothing there.” [Fox News, 9/8/2002] Colin Scoggins, the military liaison at the FAA’s Boston Center, later recalls: “I was giving NEADS accurate location information on at least five instances where AA 11 was, yet they could never identify him.… I originally gave them an F/R/D, which is a fix/radial/distance from a known location; they could not identify the target. They requested latitude/longitudes, which I gave them; they still could not identify the AA 11.… I gave them 20 [miles] south of Albany heading south at a high rate of speed, 600 knots, then another call at 50 south of Albany.” [Griffin, 2007, pp. 47] Master Sergeant Kevin Foster and Staff Sergeant Mark Rose, also working at NEADS this morning, later complain about their inability to locate the hijacked planes. After being informed of the first hijacking, reportedly: “As they had practiced countless times before, the NEADS team quickly began searching their [radar] screens for the plane. Because they had been informed its transponder was off, they knew to look for a tiny dash instead of the usual dot. But radar systems also use such lines to indicate weather patterns, so NEADS personnel began urgently clicking their computer cursors on each stray line to see if information indicating an aircraft would appear.” Yet, after receiving further calls indicating more hijackings, “the inability to find the hijacked planes on the radar, despite their best efforts, was difficult.” According to Foster, “We were trying to find the tracks, and not being able to was very frustrating.” [Utica Observer-Dispatch, 8/5/2004] NEADS Staff Sergeant Larry Thornton will recall: “Once we were called by the FAA, we could find split-second hits on what we thought we were looking for. But the area was so congested and it was incredibly difficult to find. We were looking for little dash marks in a pile of clutter and a pile of aircraft on a two-dimensional scope.” Each fluorescent green pulsating dot on their radar scopes represents an airplane, and there are thousands currently airborne, especially over the busy northeast US. [Filson, 2003, pp. 56]
Shortly After 8:37 a.m. September 11, 2001: Otis Commander Phones NEADS for Authorization to Launch Fighters
Following a call from the FAA’s Boston Center to the the FAA’s Cape Cod facility reporting the possible hijacking of Flight 11 (see 8:34 a.m. September 11, 2001), and a subsequent call from the Cape Cod facility to Otis Air National Guard Base (see (8:36 a.m.-8:41) September 11, 2001), Lt. Col. Jon Treacy, commander of the 101st Fighter Squadron at Otis, phones NORAD’s Northeast Air Defense Sector (NEADS) to report the FAA’s request for help and get authorization to launch fighters. By now though, the FAA has already gotten through to NEADS itself, and reported the hijacking (see (8:37 a.m.) September 11, 2001). [Filson, 2003, pp. 50]
8:40 a.m. September 11, 2001: FAA Manager Ben Sliney Begins Responding to Hijacking
At the FAA’s Herndon Command Center, the national operations manager, Ben Sliney, learns more details of the hijacking of Flight 11, and becomes involved with the emergency response to it. [Spencer, 2008, pp. 21] A supervisor at the Command Center informed Sliney of the suspected hijacking at just before 8:30 (see 8:28 a.m. September 11, 2001). Soon after, the supervisor interrupted a meeting Sliney was in, to tell him American Airlines had called to report the deteriorating situation on Flight 11 (see 8:30 a.m.-8:40 a.m. September 11, 2001).
Sliney Receives More Details – Sliney heads to the center’s operations floor, where the supervisor gives him further details of the call from American Airlines, including information about flight attendant Betty Ong’s phone call from Flight 11 (see 8:19 a.m. September 11, 2001). The supervisor says the plane’s transponder has been switched off (see (Between 8:13 a.m. and 8:21 a.m.) September 11, 2001), which means no flight data is showing on the screens of air traffic controllers, and the latest information from the FAA’s Boston Center is that Flight 11 has turned south, and is now 35 miles north of New York City. On one of the large screens at the front of the Command Center that shows flight trajectories, Sliney can see that the track for Flight 11 is in “ghost.” This means that, because no transponder data is being received, the computer is displaying track information based on previously stored track data.
Sliney Seeks Information, Requests Teleconference – Sliney instructs his staff to contact facilities along the path the flight appears to be on, to find if anyone is in contact with it or tracking it. [Spencer, 2008, pp. 1 and 19-21] He will later recall, “I figured we’d try to get the people on the ground, the towers in the area, the police departments, anyone we could get to give us information on where this flight was.” [Canadian Broadcasting Corporation, 9/10/2006] Sliney then requests a teleconference between the FAA’s Boston Center, New York Center, and FAA headquarters in Washington, so they can share information about the flight in real time. [Spencer, 2008, pp. 21] The Command Center has already initiated a teleconference between the Boston, New York, and Cleveland Centers, immediately after it was notified of the suspected Flight 11 hijacking. [9/11 Commission, 8/26/2004, pp. 11] However, Sliney apparently does not request military assistance. According to author Lynn Spencer, “The higher echelons at headquarters in Washington will make the determination as to the necessity of military assistance in dealing with the hijacking.” [Spencer, 2008, pp. 21]
After 8:41 a.m. September 11, 2001: Air Traffic Control, Unusually, Does Not Contact United Airlines about Communications with Flight 175
Senior United Airlines personnel are, unusually, not informed about air traffic control communications with Flight 175. At 8:41 a.m., the pilots of Flight 175 reported to air traffic controllers that they heard “a suspicious transmission” from another aircraft during their departure out of Boston (see 8:41 a.m.-8:42 a.m. September 11, 2001). Yet the details of this communication with Flight 175 are not passed on to personnel at the United Airlines System Operations Control (SOC) center, just outside Chicago. [9/11 Commission, 8/26/2004, pp. 20]
Manager Receives ‘No Relevant Information about the Hijackings’ – Rich Miles, the manager on duty at the SOC, will later tell the 9/11 Commission that “[w]hile his experience and expectation was that [FAA air traffic control] would communicate to him and to the SOC about ‘strange’ or unusual communications from the cockpit… he could not recall any such communications on 9/11.” He will say that although, “typically, he would receive relevant information from the [air traffic control] system,” he receives “no relevant information about the hijackings” on this day. [9/11 Commission, 11/21/2003 ]
Other Airline Personnel Unaware of Flight 175 Communications – None of the other senior United Airlines officials on duty at the SOC are told about the 8:41 a.m. report made by the pilots of Flight 175. [9/11 Commission, 8/26/2004, pp. 20] These officials will tell the 9/11 Commission that “the dispatchers and managers at the SOC” are in fact “not aware of any communications” between FAA controllers and Flight 175 this morning. [9/11 Commission, 11/20/2003 ] The 9/11 Commission will describe, “SOC personnel at United that we talked to had no idea of the extent of interaction of the [Flight 175] crew with the saga of [Flight 11].” The Commission will add, “We walked down a list of indicators,” but state, “Until we mentioned them, no one we talked to [at United Airlines] was aware of those occurrences.” [9/11 Commission, 11/17/2003 ]
Controllers Communicate with Pilots, Not Dispatchers – The United Airlines officials will say, however, that, “first and foremost,” FAA controllers “communicated directly with airline pilots, not the dispatchers” at the airline. [9/11 Commission, 11/20/2003 ] Ed Ballinger, the United Airlines dispatcher responsible for Flight 175, will comment that “he did not feel that [air traffic control] was under any obligation to share such information [as the details of the 8:41 a.m. communication] with him, because it didn’t apparently affect the safety of any of his flights.” [9/11 Commission, 4/14/2003 ]
Airline Not Advised to Notify Other Planes about Hijackings – The United Airlines officials who talk with the 9/11 Commission will also recall that “they never received any communication… from the FAA or the air traffic control system advising United to contact its aircraft about the hijackings.” The 9/11 Commission will not offer any explanation for the lack of communication between air traffic control and United Airlines. [9/11 Commission, 8/26/2004, pp. 20]
