!! History Commons Alert, Exciting News

Context of 'October 25, 2001: NORAD Commander Gives Inaccurate Account of Military’s Response to the 9/11 Attacks during Hearing'

This is a scalable context timeline. It contains events related to the event October 25, 2001: NORAD Commander Gives Inaccurate Account of Military’s Response to the 9/11 Attacks during Hearing. 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.

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

Two F-15 fighter jets are scrambled from Otis Air National Guard Base in Cape Cod, Massachusetts, which is 153 miles from New York City. The fighters are launched in response to the hijacked Flight 11, but this plane is already crashing into the World Trade Center at this time (see 8:46 a.m. September 11, 2001). [Washington Post, 9/15/2001; CNN, 9/17/2001; North American Aerospace Defense Command, 9/18/2001; 9/11 Commission, 6/17/2004]
Delay - The FAA’s Boston Center alerted NORAD’s Northeast Air Defense Sector (NEADS) to the hijacking of Flight 11 and requested that fighter jets be scrambled at just before 8:38 a.m. (see (8:37 a.m.) September 11, 2001), but the mission crew commander at NEADS only instructed the leader of his weapons team to launch the Otis fighters at 8:45 a.m. (see 8:45 a.m. September 11, 2001). [Vanity Fair, 8/1/2006]
Otis Aircraft Head to Runway - As soon as the pilots at Otis Air Base are strapped into their aircraft, the green light directing them to launch goes on. They start their engines and taxi out of the hangar to the nearest runway. One of the pilots, Lt. Col. Timothy Duffy, radios his command post for guidance, asking, “Do you have words?” The response he gets is, “Possible hijack, American Flight 11, 737, flight level 290 [29,000 feet], over JFK [International Airport in New York City].” (This flight information is partly incorrect, since American 11 is a 767, not a 737.) According to the Cape Cod Times, the jets will be up in the air before their radar kicks in. [Cape Cod Times, 8/21/2002; Spencer, 2008, pp. 42] The Otis pilots have already been preparing for the scramble order to come since learning of the hijacking from the FAA’s Cape Cod facility, some time shortly after 8:34 a.m. (see (8:36 a.m.-8:41) September 11, 2001). [BBC, 9/1/2002; Spencer, 2008, pp. 27-30] Their jets are reportedly not airborne until seven minutes after being scrambled, at 8:53 a.m. (see 8:53 a.m. September 11, 2001) and there will be conflicting accounts of what their original destination is (see (8:53 a.m.-9:05 a.m.) September 11, 2001). [9/11 Commission, 6/17/2004]

Entity Tags: Timothy Duffy, Otis Air National Guard Base, Daniel Nash

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Flight 175 hits the WTC South Tower. The picture was taken from a traffic helicopter.Flight 175 hits the WTC South Tower. The picture was taken from a traffic helicopter. [Source: WABC 7/ Salient Stills]Flight 175 hits the South Tower of the World Trade Center (Tower Two). Seismic records pinpoint the time at six seconds before 9:03 a.m. (rounded to 9:03 a.m.). Hijackers Marwan Alshehhi, Fayez Ahmed Banihammad, Mohand Alshehri, Hamza Alghamdi, and Ahmed Alghamdi presumably are killed instantly, and many more in the tower will die over the next few hours. [New York Times, 9/12/2001; CNN, 9/12/2001; CNN, 9/17/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; Associated Press, 8/21/2002; USA Today, 9/2/2002] According to the NIST report, the crash time is 9:02:59. [National Institute of Standards and Technology, 9/2005, pp. 38] According to the 9/11 Commission Report, the crash time is 9:03:11. [9/11 Commission, 7/24/2004, pp. 8] Millions watch the crash live on television. The plane strikes the 77th through 85th floors in the 110-story building. Approximately 100 people are killed or injured in the initial impact; 600 people in the tower eventually die. The death toll is far lower than in the North Tower because about two-thirds of the South Tower’s occupants have evacuated the building in the 17 minutes since the first tower was struck. [USA Today, 12/20/2001; National Institute of Standards and Technology, 9/2005, pp. 5-9, 41] The combined death toll from the two towers is estimated at 2,819, not including the hijackers. [Associated Press, 8/21/2002] The impact severs some columns on the south side of the South Tower. Each of the Twin Towers 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 is traveling at an estimated speed of around 500 mph (see October 2002-October 2005), severs 33 of the building’s 236 perimeter columns and damages another one. [National Institute of Standards and Technology, 9/2005, pp. 39] The perimeter columns bear about half of the tower’s weight, so the damage to them reduces the tower’s ability to bear gravity loads by about 7.1 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 be able to damage the core even after crashing through the exterior wall (see 8:46 a.m. September 11, 2001). [National Institute of Standards and Technology, 9/2005, pp. 107] According to NIST’s base case model, five of the core columns are severed and another five suffer some damage. [National Institute of Standards & Technology, 9/2005, pp. 235 pdf file] This may reduce the tower’s ability to bear loads by a further approximately 8 percent, meaning that the aircraft impact accounted for a loss of about 15 percent of the building’s strength. This damage will be cited as an event contributing to the building’s collapse after 9/11 (see October 23, 2002 and October 19, 2004). NIST’s base case estimate of damage to the North Tower’s core will be similar, even though the aircraft impact there was dissimilar (see 8:46 a.m. September 11, 2001). Flight 11 hit the North Tower’s core head on, whereas Flight 175 only hits the corner of the South Tower’s core. [National Institute of Standards and Technology, 9/2005, pp. 20-23, 38-41] In addition, some of the fireproofing on the steel columns and trusses may be dislodged (see 8:46 a.m. September 11, 2001). [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 the National Institute of Standards and Technology (NIST) will try to estimate the damage to fireproofing using a series of computer models. Its severe case model (see (October 2002-October 2005)) will predict that 39 of the 47 core columns are stripped of their fireproofing on one or more floors and that fireproofing is stripped from trusses covering 80,000 ft2 of floor area, the equivalent of about two 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. 41] According to NIST, less fireproofing is stripped from the North Tower (see 8:46 a.m. September 11, 2001).

Entity Tags: World Trade Center, Marwan Alshehhi, Fayez Ahmed Banihammad, Hamza Alghamdi, National Institute of Standards and Technology, Ahmed Alghamdi, Mohand Alshehri

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

Alan Scott.Alan Scott. [Source: United States Air Force]NORAD’s Northeast Air Defense Sector (NEADS) processes and transmits an order to Langley Air Force Base in Virginia, to scramble three of its F-16 fighter jets. [North American Aerospace Defense Command, 9/18/2001; Christian Science Monitor, 4/16/2002; 9/11 Commission, 8/26/2004, pp. 16] NEADS mission crew commander Major Kevin Nasypany instructed his personnel to issue this order one minute earlier (see 9:23 a.m. September 11, 2001). Although he’d originally wanted the Langley jets sent to the Washington area, he will soon adjust this heading to send them to the Baltimore area. [9/11 Commission, 7/24/2004, pp. 27]
NEADS Orders Jets North - A NEADS officer calls Langley Air Force Base and instructs: “Langley command post, this is Huntress with an active air defense scramble for Quit 2-5 and Quit 2-6.… Scramble immediately.… Scramble on a heading of 010, flight level 290.” This means the jets are to head in a direction just east of north, at an altitude of 29,000 feet. [9/11 Commission, 1/9/2004; 9/11 Commission, 8/26/2004, pp. 96; Spencer, 2008, pp. 142] At Langley Air Force Base, a Klaxon horn will sound, notifying the pilots of the scramble order (see 9:24 a.m. September 11, 2001), and they will be airborne by 9:30 (see (9:25 a.m.-9:30 a.m.) September 11, 2001). [Filson, 2003, pp. 63; 9/11 Commission, 8/26/2004, pp. 16; Spencer, 2008, pp. 141]
Fighters Launched in Response to Flight 77? - In later testimony, military officials will give contradictory explanations for why the Langley F-16s are scrambled. An early NORAD timeline will indicate the fighters are launched in response to NORAD being notified at 9:24 that Flight 77 has been hijacked (see (9:24 a.m.) September 11, 2001). [North American Aerospace Defense Command, 9/18/2001] Colonel Alan Scott, the former vice commander of the Continental US NORAD Region (CONR), will suggest the same, telling the 9/11 Commission: “At 9:24 the FAA reports a possible hijack of [Flight] 77.… And at that moment as well is when the Langley F-16s were scrambled out of Langley.” [9/11 Commission, 5/23/2003; 1st Air Force, 8/8/2006] And a timeline provided by senior Defense Department officials to CNN will state, “NORAD orders jets scrambled from Langley” in order to “head to intercept” Flight 77. [CNN, 9/17/2001]
In Response to Flight 93? - However, Major General Larry Arnold, the CONR commander, will give a different explanation. He will tell the 9/11 Commission, “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]
In Response to Incorrect Report about Flight 11? - In 2004, the 9/11 Commission will dispute both these previous explanations, and conclude that the Langley jets are scrambled in response to an incorrect report that Flight 11 is still airborne and heading toward Washington, DC (see 9:21 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 26-27; 9/11 Commission, 8/26/2004, pp. 15] Tape recordings of the NEADS operations floor will corroborate this account. [Vanity Fair, 8/1/2006] According to the 9/11 Commission, its conclusion is also confirmed by “taped conversations at FAA centers; contemporaneous logs compiled at NEADS, Continental Region headquarters, and NORAD; and other records.” [9/11 Commission, 7/24/2004, pp. 34] Major Nasypany will tell the Commission that the reason the Langley jets are directed toward the Baltimore area is to position them between the reportedly southbound Flight 11 and Washington, as a “barrier cap.” [9/11 Commission, 7/24/2004, pp. 27 and 461] John Farmer, senior counsel to the 9/11 Commission, will later suggest that NORAD deliberately misled Congress and the Commission by hiding the fact that the Langley scramble takes place in response to the erroneous report that Flight 11 is still airborne. He will write that the mistaken report “appears in more logs, and on more tapes, than any other single event that morning.… It was the reason for the Langley scramble; it had triggered the Air Threat Conference Call. Yet it had never been disclosed; it was, instead, talked around.” [Farmer, 2009, pp. 266-267]
Conflicting Times - Early news reports will put the time of the scramble order slightly later than the 9/11 Commission places it, between 9:25 and “about 9:27.” [Washington Post, 9/12/2001; CNN, 9/17/2001; CNN, 9/19/2001] But a NORAD timeline released a week after the attacks will give the same time as the Commission does, of 9:24. [North American Aerospace Defense Command, 9/18/2001; 9/11 Commission, 7/24/2004, pp. 27]

Entity Tags: 9/11 Commission, Kevin Nasypany, Alan Scott, Larry Arnold, North American Aerospace Defense Command, Langley Air Force Base, US Department of Defense, Northeast Air Defense Sector

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

According to the 9/11 Commission, NEADS contacts Washington flight control to ask about Flight 11. A manager there happens to mention, “We’re looking—we also lost American 77.” The commission claims, “This was the first notice to the military that American 77 was missing, and it had come by chance.… No one at FAA Command Center or headquarters ever asked for military assistance with American 77.” [9/11 Commission, 6/17/2004] Yet, 38 minutes earlier, flight controllers determined Flight 77 was off course, out of radio contact, and had no transponder signal (see 8:56 a.m. September 11, 2001). They’d warned American Airlines headquarters within minutes. By some accounts, this is the first time NORAD is told about Flight 77, but other accounts have them warned around 9:25 a.m.

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

Timeline Tags: Complete 911 Timeline, 9/11 Timeline

Smoke rising, minutes after Flight 93 crashes in Pennsylvania.Smoke rising, minutes after Flight 93 crashes in Pennsylvania. [Source: CNN]Exactly when Flight 93 crashes is unclear. According to NORAD, Flight 93 crashes at 10:03 a.m. [North American Aerospace Defense Command, 9/18/2001] The 9/11 Commission gives an exact time of 11 seconds after 10:03 a.m. It will claim this “time is supported by evidence from the staff’s radar analysis, the flight data recorder, NTSB [National Transportation Safety Board] analysis, and infrared satellite data.” It does note that “[t]he precise crash time has been the subject of some dispute.” [9/11 Commission, 6/17/2004] However, a seismic study authorized by the US Army and drafted by scientists Won-Young Kim and Gerald Baum to determine when the plane crashed will conclude that the crash happened at 10:06:05 a.m. [Kim and Baum, 2002 pdf file; San Francisco Chronicle, 12/9/2002] The discrepancy is so puzzling that the Philadelphia Daily News will publish an article on the issue, titled “Three-Minute Discrepancy in Tape.” This notes that leading seismologists agree on the 10:06 a.m. time, give or take a couple of seconds. [Philadelphia Daily News, 9/16/2002] The New York Observer will note that, in addition to the seismology study, “The FAA gives a crash time of 10:07 a.m. In addition, the New York Times, drawing on flight controllers in more than one FAA facility, put the time at 10:10 a.m. Up to a seven-minute discrepancy? In terms of an air disaster, seven minutes is close to an eternity. The way our nation has historically treated any airline tragedy is to pair up recordings from the cockpit and air traffic control and parse the timeline down to the hundredths of a second. However, as [former Inspector General of the Transportation Department] Mary Schiavo points out, ‘We don’t have an NTSB (National Transportation Safety Board) investigation here, and they ordinarily dissect the timeline to the thousandth of a second.’” [New York Observer, 2/15/2004]

Entity Tags: 9/11 Commission, North American Aerospace Defense Command, Federal Aviation Administration, Won-Young Kim, Mary Schiavo, Gerald R. Baum

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/13/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

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

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