At 8:30 that morning, the exercise proper had not yet got under way. The colonel was munching apple fritters. His mission control commander, Major Kevin Nasypany, was away from the ops floor—in his words, “on the shitter.” The general to whom they answered, Larry Arnold, was at NORAD’s regional command center in Florida.
On the ops floor at NEADS, Master Sergeant Maureen Dooley, Technical Sergeant Shelley Watson, and Senior Airman Stacia Rountree were chatting about furniture at the mall—wondering whether an ottoman and a love seat were on sale. To be sure, the orders for the day’s training exercise provided for the team to be capable of responding to a “Real World Unknown,” but no one expected much to happen.
Then the unknown arrived, in the form of a call from FAA controller Joe Cooper, at Boston Center, to Sergeant Jeremy Powell. It was 8:38.
COOPER: 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.
SGT. JEREMY POWELL: Is this real-world or exercise?
COOPER: No, this is not an exercise, not a test.
The sergeant, and the women who moments earlier had been discussing home furnishings, needed some persuading. Fazed by the advent of real-life excitement, Shelley Watson even exclaimed, “Cool!” A moment later, after an “Oh, shit,” she was all business. “We need call-sign, type aircraft. Have you got souls on board, and all that information? … a destination?” Boston Center could say only that the airplane seized was American 11—as would become clear, the first of the four hijacks. No one could have imagined the destination its hijackers had in mind.
By 8:41, Colonel Marr had ordered the two alert jets at Otis Air National Guard Base, on Cape Cod, to battle stations. At 8:46, having conferred with General Arnold, he ordered them into the air—to no avail. Absent any detailed data, they were assigned merely to fly to military-controlled airspace off the Long Island coast. In the same minute, 153 miles away, American 11 smashed into the North Tower of the World Trade Center.
The NEADS technicians, who had glanced up at a TV monitor, saw the tower in flames. “Oh, God,” one technician said quietly. “Oh, my God …” A colleague at her side cried, “God save New York.”
FAA controllers had meanwhile lost contact with the second hijacked plane, United 175. “It’s escalating big, big time,” New York Center manager Peter Mulligan told colleagues in Washington. “We need to get the military involved.” The military was involved, in the shape of the two NEADS fighters, but impotent.
The Air Force knew nothing of the second hijack until 9:03, the very minute that Flight 175 hit the South Tower. News of that strike reached the Otis pilots Lieutenant Colonel Timothy Duffy and Major Dan Nash while they were still holding off the coast of Long Island.
Five minutes after the second strike, NEADS mission commander Nasypany ordered his fighters to head for Manhattan. Now, though, there was no suspect airliner in New York airspace to intercept. When the pilots began to fly a Combat Air Patrol over Manhattan, as soon they did, there was no enemy to combat. As catastrophe overwhelmed the city, they could only watch from high above. “I thought,” Nash remembered, “it was the start of World War III.”
The Air Force officers and the FAA controllers rapidly began to fear—correctly—that they had seen only the start of something, that there were more strikes to come. Where might they come from? It was perhaps no coincidence, they figured, that both the planes so far hijacked had started their journeys from Logan Airport. “We don’t know how many guys are out of Boston,” mused mission commander Nasypany. “Could be just these two—could be more.” An FAA manager voiced the same thought. “Listen,” he said, “both of these aircraft departed Boston. Both were 76s, both heading to LA.”
“We need to do more than fuck with this,” Nasypany told Colonel Marr, urging him to scramble the other alert fighters available to them—at the Langley base, three hundred miles south of New York. Marr agreed at first only to put Langley on standby. Then, at 9:21, came a call with information that changed the colonel’s mind—and later led to lasting controversy.
The caller was Colin Scoggins, an FAA controller at Boston Center who—in part because of his own previous military service—had special responsibility for liaison with the Air Force. On the phone to NEADS, he shared stunning news:
SCOGGINS: Military, Boston. I just had a report that American 11 is still in the air, and it’s on its way towards—heading towards Washington.
NEADS: OK. American 11 is still in the air?
SCOGGINS: Yes … It was evidently another aircraft that hit the tower … This is a report in from Washington Center. You might want to get someone on another phone talking to Washington Center.
One of the technicians did check with Washington, more than once—only to be told that they knew nothing about American 11 still being airborne. “First I heard of that,” said one supervisor. The source could not be Washington Center, another said. He added, correctly, that “American 11 is the airplane, we’re under the premise, that has already crashed into the World Trade Center.” Scoggins, however, insisted that he had heard “from Washington” that American 11 was still in the air, going “southwest.”
After Flight 11’s transponder was switched off, FAA controllers at New York Center had entered a new “track” for the flight into the system in order to alert other controllers to the airliner’s projected southerly direction. The track remained in the system for a while even after the real Flight 11 had crashed into the Trade Center. 9/11 Commission staff conjectured that it was that track, and emerging information about the loss of Flight 77, that sparked the rumor that Flight 11 was still airborne.
Scoggins never has been able to recall his source of the erroneous information—only that he picked it up while “listening on a Telcon with some people at Washington HQ, and other facilities as well, but I don’t know who they were.”
The information was a red herring. In the chaos of the moment, however, no one knew for certain that it was Flight 11—as opposed to some other aircraft—that had hit the North Tower. If it had not, and if hijackers were taking the captured plane southwest—as Scoggins suggested—their target had to be Washington, D.C. The realization galvanized NEADS.
“Shit!” exclaimed Nasypany. Then, “OK. American Airlines is still airborne, 11, the first guy. He’s heading toward Washington. OK. I think we need to scramble Langley right now … Head them towards the Washington area.”
So it was that at 9:30, chasing a plane that did not exist, three more Air National Guard fighters raced into the air—three, not just the two on alert duty, because NEADS had asked for every plane available. If a hijacked airliner was headed for Washington, Nasypany figured, he would send the fighters to the north of the capital, and block its way. NEADS duly ordered a course that would take them there, but the order was not followed. The tower at the base sent the fighters in another direction—east, out over the Atlantic. Where they were of no use at all.
Chaos prevailed. Four minutes into the fighters’ flight, at 9:34, NEADS finally learned something American Airlines had known for more than half an hour and FAA controllers had known for even longer. “Let me tell you this,” said Cary Johnson, the Washington Center operations manager. “We’ve been looking. We also lost American 77 … Indianapolis Center was working this guy … They lost contact with him … And they don’t have any idea where he is.”
Two minutes later, at 9:36, Scoggins came up on the phone again. “Latest report,” he said. “Aircraft VFR [Visual Flight Rules, meaning the plane was not under the direction of Air Traffic Control], six miles southeast of the White House … We’re not sure who it is.” NEADS technician Stacia Rountree dialed Washington, only to be told, “It’s probably just a rumor.” This time, though, Scoggins’s information was accurate. The plane maneuvering near the nation’s capital was no phantom Flight 11. It was the very real,
hijacked, American 77—lining up to strike.
In the NEADS bunker, mission commander Nasypany had no way of knowing that. What he knew, thought he knew, was that his Langley fighters were by now close to Washington, well positioned for an intercept. “Get your fighters there as soon as possible,” he ordered.
Two minutes later, at 9:38, the major asked where the fighters were and learned that they were out over the ocean, 150 miles from where they were needed. Nasypany hoped against hope there was still time to respond. He urged them to fly supersonic—“I don’t care how many windows you break.” And, in frustration, “Why’d they go there? Goddammit! … OK, push ’em back!”
Too late, far too late. Even before Nasypany asked the whereabouts of his fighters, American 77 had scythed into the Pentagon.
Then, and even before the devastating news reached NEADS, Colin Scoggins was back on the phone again from Boston Center—this time with information as misleading as had been his report that Flight 11 was still airborne. “Delta 1989,” he said, “presently due south of Cleveland … Heading westbound.” Delta 1989 was a Boeing 767, like the first two planes seized, and like them it had left from Boston. “And is this one a hijack, sir?” asked Airman Rountree. “We believe it is,” Scoggins replied.
They believed wrong. Boston Center speculated that Delta 1989 was a hijack because it fit the pattern. It had departed Boston at about the same time as the first two hijacked planes. Like them it was a 767, heavily laden with fuel for a flight across the continent. Unlike them, however, it was experiencing no problems at all—until the false alarm.
NEADS promptly began tracking the Delta plane—easy enough to do because as a legitimate flight it was transmitting routine locator signals. It was the only airplane the military was able to tail electronically that day for any useful period of time. On seeing that Delta 1989 was over Ohio, NEADS sent a warning to the FAA’s Cleveland Center. For the airliner’s pilots, already jolted out of their routine by what little they had learned of the attacks, hours of puzzlement and worry began.
First came a text message, instructing Captain Paul Werner to “land immediately” in Cleveland. When the captain sent a simple acknowledgment, back came a second message reading, “Confirm landing in Cleveland. Use correct phraseology.” A perplexed Werner tried again—more wordily, but still too casually for Cleveland. Phrases like “confirmed hijack” and “supposedly has a bomb on board” began flying across the ether. Information from Delta 1989, a controller would report, was “really unreliable and shaky.”
By 9:45, only six minutes after his initial warning, Scoggins was saying the plane “might not be a hijack … we’re just not sure.” By then, though, the Air Force was busy trying to get fighters to the scene, Cleveland airport was in a state approaching panic, and 1989’s pilots feared they might have a bomb on board.
“I understand,” Cleveland control radioed Captain Werner meaningfully, “you’re a trip today,” The word “trip” was an established code for hijack, and Werner assured control he was not—only to be asked twice more. Once on the ground, at 10:18, he was ordered to taxi to the “bomb area,” far from the passenger terminal. Passengers and crew would not be allowed to disembark for another two hours, and then under the wary eyes of gun-toting FBI agents and a SWAT team in full body armor.
It had all been, a Cleveland controller would recall, like a “scene out of a bad movie.” Even before the innocent Delta 1989 landed, however, the latest phase of the aviation nightmare had become real-life horror—for Cleveland, for the Air Force team in its bunker, and, for the fourth time that day, for the nation. At 10:07, a phone call between the FAA’s Cleveland Center and NEADS produced a revelation.
FAA: I believe I was the one talking about that Delta
1989 … Well, disregard that. Did you? …
NEADS: What we found out was that he was not a confirmed hijack.
FAA: I don’t want to even worry about that right now. We got a United 93 out here. Are you aware of that?
NEADS was completely unaware. During the wild-goose chase after Delta 1989, NEADS had been told nothing of the very real hijacking, also over Ohio, of United 93. An FAA controller had heard screams from Flight 93’s cockpit, followed by a hijacker’s announcement about a “bomb on board,” some seven minutes before Scoggins alerted NEADS to the imagined problem aboard Flight 1989.
The controller had reported the new hijack promptly, and word had been passed to FAA headquarters. Cleveland control then came up again, purposefully asking whether the military had been alerted. A quarter of an hour later, nevertheless, the following pathetic exchange took place:
FAA COMMAND CENTER: Uh, do we want to think, uh, about scrambling aircraft?
FAA HEADQUARTERS: Uh, God, I don’t know.
FAA COMMAND CENTER: Uh, that’s a decision somebody is going to have to make, probably in the next ten minutes.
FAA HEADQUARTERS: Uh, you know, everybody just left the room.
Five minutes after that, at 9:53 and as United 93’s passengers prepared to attack their captors, an FAA staffer reported that—almost twenty minutes after word of the hijack had reached the agency’s headquarters—senior FAA executive Monte Belger and a colleague were discussing whether to ask for fighters to be scrambled. Belger would tell the 9/11 Commission that he “does not believe the conversation occurred.”
At 10:03, ten minutes after the reported discussion, a full half an hour after FAA headquarters learned of the hijack, United 93’s passengers and crew all died when the airliner plunged into the ground in Pennsylvania. NEADS knew nothing at all of the airliner’s plight until several minutes later—and were then given only vague, out-of-date information.
“In a day when we were already frustrated,” the FAA’s Colin Scoggins recalled, “we were always a day late and a dollar short. We just could never catch up.”
THAT, THE LOGS and documents clearly show, is the true story of the effort to defend America on 9/11. Why, then, did senior military and political men say otherwise? Why, within days, did General Myers and Paul Wolfowitz suggest that fighters had been in pursuit of Flight 93 and would have been able to bring it down? Why did senior officers, and in particular General Arnold—who had been in charge at the NORAD command center in Florida on the day—make similar claims to the 9/11 Commission?
“We believe,” Arnold wrote as late as 2008, “we could have shot down the last of the hijacked aircraft, United 93, had it continued toward Washington, D.C.” It was a statement founded on sand, one that airbrushed out of history the inconvenient facts of the general’s previous claims. Four months after the attacks, he asserted that NORAD had already been “watching United Flight 93 wander around Ohio” at the time the Trade Center’s South Tower was hit. That strike had occurred at 9:03, twenty-five minutes before Flight 93 had even been attacked.
Two years later, as noted earlier, Arnold would claim that NORAD’s focus had been on Flight 93 by 9:24—when the hijack “was being pointed out to us very aggressively, I might say, by the FAA.” This assertion also suggested a magical feat by the military, that the Air Force had been concentrating on United 93 before the plane was seized. The documented reality—damning to the FAA—is that no one at the agency reported the hijack to NORAD in any way, let alone “aggressively,” until after it crashed.
General Arnold would eventually concede that his testimony had been inaccurate. What he, General Myers, and Deputy Defense Secretary Wolfowitz had said about Flight 93 had been nonsensical—though just how nonsensical would emerge only after the disentangling by Commission staff of a maze of logs and tapes—a prodigious task.
Why the officers initially told inaccurate stories is rather clear. In the fuzzy immediate aftermath of 9/11, before the facts and the timings could be analyzed, they conflated the flap over Delta 1989, the hijack that never was, with the very real hijack of Flight 93. That does not explain, however, why they continued to perpetuate the fiction long afterward, when there had been ample time to check
the facts.
Former Commission analyst Miles Kara has likened NORAD’s account to an attempt to solve a Sudoku puzzle—fated to fail if a single early mistake is made. He put the inaccurate story down to shoddy staff work and repeated misreadings of the logs.
Commission general counsel Daniel Marcus, though, pointed to disquieting discrepancies, including the “suspicious” omission of key times from an FAA document, the alteration of a NORAD press release, and a disputed claim about the reason for a supposed tape malfunction. Referring the matter to the inspectors general of both the Department of Defense and the Department of Transportation, he raised the possibility that the FAA and Air Force accounts were “knowingly false.”
NORAD’s commander-in-chief, General Ralph Eberhart, for his part, had assured the Commission he and his fellow officers “didn’t get together and decide that we were going to cover for anybody or take a bullet for anybody.”
Senator Mark Dayton, speaking at a hearing on the Commission’s work, would have none of it. “NORAD’s public chronology,” he declared, “covered up … They lied to the American people, they lied to Congress, and they lied to your 9/11 Commission, to create a false impression of competence, communication, coordination, and protection of the American people … For almost three years now NORAD officials and FAA officials have been able to hide their critical failures, that left this country defenseless during two of the worst hours in our history.”
The senator called on President Bush to fire “whoever at FAA or NORAD, or anywhere else who betrayed the public trust by not telling us the truth. And then he should clear up a few discrepancies of his own.”
“At some level of the government, at some point in time …,” Commission counsel John Farmer has written, “there was a decision not to tell the truth about what happened.” The troubling questions about the way the government really functioned on 9/11, Farmer made clear, also involved the White House.
The Eleventh Day Page 14
