Showing posts with label NORAD. Show all posts
Showing posts with label NORAD. Show all posts

Monday, February 9, 2009

MUZZLING THE DEFENSE

Adam Larson / Caustic Logic
They Let It Happen
[undated]


Note [added 2/8/09] While I am leaving this post up as-is and FWIW, the core point of it - the apparent "muzzling" represented by the 2001 order - seems to have been debunked. See Mike W's 9/11 Myths page. What I'd previously read as an exception to new restrictions was actually THE change to a MORE restrictive previous order. Good thing I had already called it a red herring, rather than hanging any weight on the issue. So for the record - the June 1 change can have had no direct role in impeding the 9/11 defense, and so it's implementation is not direct evidence of any LIHOP thinking. Apologies also for the late update.
---

As indicated by the swift fighter response in the Payne Stewart case, the Chain of Command was not ordinarily needed to get escort fighters off the ground – this could all be done automatically and at intermediate levels. But more tightly controlled actions, like issuing an order for these fighters to shoot down a civilian aircraft, constituted an emergency and had to originate with the President and pass through every link in the chain of command to the responsible fighter pilots.

But these guidelines, in effect since 1986, oddly changed just three months before September 11, extending the need for approval yet further down. A Defense Department directive of June 1 2001 stated: “In the event of a hijacking, the NMCC will be notified by the most expeditious means by the FAA. The NMCC will, with the exception of immediate responses […] forward requests for DoD assistance to the Secretary of Defense for approval.” [1] Aviation Week backed this up: “On Sept. 11, the normal scramble-approval procedure was for an FAA official to contact the National Military Command Center (NMCC) and request Pentagon air support. Someone in the NMCC would call NORAD's command center and ask about availability of aircraft, then seek approval from the Defense Secretary--Donald H. Rumsfeld--to launch fighters.” [2] In other words, the automatic scrambling of fighters was no more – the Secretary of Defense now had to personally sign off before fighters could be sent up, and specifically in response to a hijacking. Michael Ruppert wrote that this change in procedures “demonstrated a willful intent to centralize decision-making away from field commanders prior to the attacks.” [3]

But the 9/11 Commission’s final report states in its blameless way: “As they existed on 9/11, the protocols for the FAA to obtain military assistance from NORAD required multiple levels of notification and approval at the highest levels of government […] The NMCC would then seek approval from the Office of the Secretary of Defense to provide military assistance […] The protocols did not contemplate an intercept […] On the morning of 9/11, the existing protocol was unsuited in every respect for what was about to happen.” [4] They do not mention how recently and intentionally it had become so unsuited.

Of course “immediate response” actions were allowed without Rumsfeld’s immediate permission, and it appears some thought the attacks fit this exception – neither the Otis nor the Langley fighters, the first wave of defense (scrampled 8:52 and 9:30), were scrambled with Rumsfeld’s permission. He claims he never even arrived at the NMCC until 10:30 am. According to the Commission, Major General Larry Arnold, commander of the Continental U.S. NORAD Region said to one of his subordinates “go ahead and scramble [the Otis fighters], and we’ll get authorities later.” So the fighters were sent up, if slowly and with great confusion, and Rumsfeld’s procedure change becomes a red herring, if a telling one.

Sources: [5] Ruppert, Micheal C. Crossing the Rubicon. Gabriola Island, BC, Canada. New Society Publishers. 2004. Page 316
[6] Scott, William B. “Exercise Jump-Starts Response to Attacks.” Aviation week’s Aviation Now. June 3, 2002. Accessed April 27, 2003 at: http://www.aviationnow.com/content/publication/awst/20020603/avi_stor.htm. (need subscription to read it now).
[7] See [5]. Ruppert. Page 337.
[8] National Commission on Terrorist Attacks upon the United States. 9/11 Commission Final Report. Page 17

Wednesday, September 10, 2008

WARGAME IV: VIGILANT WARRIOR

Update, 9/10/08: I wrote this post a long time ago when i was more "Truthy," but in fact there was probably NOT a wargame called Vigilant Warrior on 9/11 - see comments below. For reference purposes at least however I'll leave this post up. Just read "probable" as "faintly possible," and so on...

USA Today reported in April 2004 article also cited a NORAD press release: “Numerous types of civilian and military aircraft were used as mock hijacked aircraft. These exercises tested track detection and identification; scramble and interception; hijack procedures…” [1] These “mock hijacked aircraft,” otherwise called “live-flies,” are used sometimes in air-based war games involving hijacking scenarios. They are actual planes of a variety of makes, in the air (manned or under remote control), pretending to be hijacked for the benefit of effective training.

Ruppert asked some questions, some regarding live-flies, of Major Don Arias, NORAD press spokesman who was on duty and involved in the response the morning of 9/11. Arias at first dismissed Ruppert as part of the “grassy knoll” crowd, but later gave him some good information in a phone interview and follow-up e-mail. He confirmed Vigilant Guardian, and provided clues on the meanings of nicknames.

“Vigilant or Amalgam means it is a HQ NORAD sponsored exercise. Guardian means it is a multi-command CPX, or command post exercise (no live-fly). So on 9/11, NORAD was conducting a NORAD-wide, multi-command, command post exercise with no live-fly. Other exercise terms include: Warrior = JCS/HQ NORAD sponsored FTX, or field training exercise (live-fly).” [2]

Arias thus confirmed that JCS-connected “Warrior” exercises would involve live-flies faking symptoms of a hijacking. Ruppert further speculated that “warrior” and “guardian” exercises would be conducted jointly in an offense/defense simulation, a possibility he was unable to verify. But whatever its relation to the other war games, there is evidence of at least one “warrior” exercise taking place on the morning of 9/11.

Richard Clarke said in his book Against All Enemies that acting JCS Chairman Richard Myers told him in their videoconference on 9/11 “not a pretty picture, Dick… We are in the middle of Vigilant Warrior, a NORAD exercise.” [3] This does not seem to be a confused reference to the already admitted Vigilant Guardian, since that did not involve JCS – but a “Warrior” FTX would have Joint Chiefs involvement – and live-flies. Chalk up another (probable) exercise, this one putting extra “hostile” aircraft in the skies amid the attack.

Sources:
[1] Ruppert, Crossing the Rubicon. p 345
[2] Ruppert, Crossing the Rubion. p 368
[3] clarke, Against All Enemies. p 5

Friday, October 12, 2007

THE CHAIN OF COMMAND ON 9/11 {masterlist}

National Command Authority
The National Defense Chain of Command in a wartime emergency at the time of the September 11 attacks was: 1) President, 2) Defense Secretary, 3) regional combatant commanders. This was established by the Goldwater-Nichols DOD reorganization Act of 1986, which also allowed that on the whim of the President and Defense Secretary, communications with and oversight of these commanders pass through the Chairman of the Joint Chiefs of Staff (CJCS – the nation’s top military officer)

Tightly controlled actions, like issuing an order for fighter jets to shoot down a civilian aircraft, constituted an emergency and had to originate with the President and pass through every link in the chain to the responsible fighter pilots. As the 9/11 Commission explained, “prior to 9/11, it was understood that an order to shoot down a commercial aircraft would have to be issued by the National Command Authority (a phrase used to describe the president and secretary of defense).” [2]

This Chain of Command was not ordinarily needed to get escort fighters off the ground – this could all be done automatically and at intermediate levels, as indicated by the swift fighter response in the Payne Stewart case. These guidelines, in effect since 1986, oddly changed just three months before September 11, with Rumsfeld asserting the sole authority to allow fighters to take off at all. This is covered in more in detail in the post "Muzzling the Defense?"

The 9/11 Commission’s final report later stated in its blameless way: “As they existed on 9/11, the protocols for the FAA to obtain military assistance from NORAD required multiple levels of notification and approval at the highest levels of government […] The protocols did not contemplate an intercept […] On the morning of 9/11, the existing protocol was unsuited in every respect for what was about to happen.” It became even more unsuited in the days and hours and even minutes before the attacks, and on the morning of September 11th, strangely, the National Command Authority’s chain of command seemed to sprout new links, swap out old ones, and seemed to not be anchored down to anything. The following posts deal with the US leadership response and the flailings and failings of a Chain of broken links.

- President Bush: “There’s one Terrible Pilot:” The accidental President Stumbles into 9/11.

- Vice President Cheney, the Roadmap Swap, and the “Effort.” Clarifying the Record. Did Bush hand Cheney the joystick to control the attacks?

- Cheney and the Shoot-Down Order: Who issued the order and when? 9:45, 10:14, 10:18?

- Link #2 AWOL: Psychic Rumsfeld’s Wanderings

- Myers the stand-in: How he responds "when things are happening."

- First Day Jitters: Sliney, Leidig, Myers: Three Defense Links Swapped out at the last minute at Joint Chiefs of Staff (ACTING Chairman richard Myers, as of ?:00 am, 9/11) Benedict Sliney at FAA Operations Center (first day as of ?:00 am, 9/11) and Leidig at the NMCC (see chart below - standing in as of 8:30 am, 9/11, as per a request from the previous day). This is spooky.

In the end, what we got was a startlingly "unprepared" and disjointed command authority that ran something like this:

Monday, June 18, 2007

FAILED AIR DEFENSE {masterlist}

AN AERIAL BALLET OF PERFECTLY SYNCHRONIZED FAILURES (updated 2/5/07)
“Is this part of the exercise? Is this some kind of a screw-up?”
- Larry Arnold, NORAD Commander, upon hearing of the first hijack
“That was news to me. I thought we were still chasing American 11.”
- F-15 pilot “Duff” on hearing a second plane had hit the WTC
“Holy smoke, that’s why we’re here.”
- F-16 pilot “Lou” upon seeing smoke from the Pentagon


This post is to organize and link together all the related sub-posts on the ridiculously inadequate air defense during the 9/11 attack. The air-based wargames, which are referred to often in these posts, are covered seperately in the wargames masterlist. People still argue about whether our fighter defenses could have done anything if they had been better integrated. The answer depends on the presumptions one makes, but basically the answer is yes - there were procedures to defend the nation from roughly the 9/11 threat of suicide hijackings, but they have been magnified, obscured, and muddled by both sides in the post-9/11 debate. And they seem to have not been followed that morning.

This is a chart I made of the timeline of the attack and overall air defense during it - click the image to get a full-size, readable view (can also be saved and printed, 8.5 x 11").

> Status of air terror readiness as of 9/11: Could it be this bad on accident?
- Payne Stewart and Standard procedure: We had standard procedures for intercepting stray planes
- Rumors of a Stand-Down: Unprepared or Stood Down? (neither - this dichotomy is a false one).
- Muzzling the Defense: Rumsfeld's recent changes to fighter scramble procedures - ultimately a red herring?
- Warnings ignored?
- Fighter deployments decided on to defend the known primary zone of terrorism threats: notably inadequate.
- Commercial pilots' right to bear arms in the air rescinded in 2001? Post in the works...


> A Hobbled Defense in Action on 9/11
- Federal Attack Assistance? {masterlist}: The FAA's role in "dropping the ball" on 9/11, in several sub-posts: Sliney, the phantom Flight 11, the mistaken memo, etc...
- Phantom flights/radar inserts
- Radar blind spots
- Otis and Langley: Scrambling against the clock
-
Heading and Speed: slowly away from the attacks
- Information shared with the defending fighter pilots:
RIDICULOUSLY inadequate

> Permission to use deadly force to protect America: Negligently (?) denied
- No Such order recieved by the five defending pilots.
- Bush at Booker: Isolated accidents require no defensive orders, and Bush insisted on pretending it was an isolated accident until the last possible minute - and then still refused to issue the order for at least another hour. By the official story.
- Cheney and the Shoot-Down Order

Monday, May 7, 2007

BUSH, CHENEY, AND SECRET SERVICE COMMUNICATIONS

Adam Larson / Caustic Logic
They Let It Happen
last updated 5/7/07


A year after the attack, CNN retold Vice President Cheney’s version of what happened. Cheney was in his proper office in the West Wing when he heard that a plane had crashed into the WTC. Unlike everyone else whose reactions I’ve looked at - with the notable exception of counter-terrorism “Czar” Richard Clarke - Cheney had an inkling this may not be a simple accident. “He watched TV and hoped that his instincts were wrong.,” CNN reported. He explained “it was a clear day, there were no weather problems, and then we saw the second airplane hit in real time. At that moment, you knew this was a deliberate act. This was a terrorist act.” [1]

Shortly after this, his Secret Service agent “all of a sudden materialized right beside me and said, 'Sir, we have to leave now.' He grabbed me and propelled me out of my office, down the hall, and into the underground shelter in the White House." [2] So while, as many noted, the Secret Service was allowing the President to linger in the open at the schoolhouse, they were “propelling” Cheney to safety in an underground bunker. While both men were on the East Coast, they seemed to be operating in two different time zones.

This underground shelter was the Presidential Emergency Operations Center (PEOC). From the previously unused but well-equipped PEOC, as CNN explains, the Vice-President “directed the U.S. government's response” to the attack. The actions Cheney took “included moving key members of Congress to a secure location and having the Secret Service bring his wife, Lynn, to the bunker.” [3] Somehow, these radical moves failed to halt the attack.

Cheney and Rice share a tense moment in the PEOC on 9/11. Photo chosen for presence of Cheney on the phone.
Cheney’s account actually offers little in the line of useful action, focusing more on talk of raw emotion – agony and impotence and rage – just like the rest of us – after he saw the second plane hit on the TV - just like the rest of us. But Bush talked to Cheney on a regular cell phone instead of a secure phone, which wasn’t working right. Cheney’s information seemed partial and confused. The 9/11 Commission, based on Cheney’s private testimony, decided Cheney suffered major communications problems that hampered a response. [4] CNN described the PEOC’s performance on 9-11 “a day of crisis with some hitches.” For example, “Cheney wanted to track TV reports of the devastation and listen in on communications with the Pentagon.” But, as aide Mary Matalin recalled, “you can have sound on one or the other and he found that technically imperfect.” [5]

But we know he was in the presence of Secret Service agents during the entire crisis, and the evidence indicates their communication abilities were widespread and efficiently used. Cheney seemed to slip on this once, telling Meet the Press, on September 16 “the Secret Service has an arrangement with the FAA. They had open lines after the World Trade Center was ...” [6] He cut himself off there and shifted gears. What this means is that after the first plane hit, and we would presume soon after, the Secret Service knew, and were listening in on, at least, the FAA’s communications by about 8:50. The second plane was already confirmed hijacked by FAA and NORAD and headed to New York by this time.

Richard Clarke also testified in his book Against All Enemies that at about 9:40, Brian Stafford, Director of the Secret Service “slipped me a note. “Radar shows aircraft headed this way.’” Clarke explained “Secret Service had a system that allowed them to see what FAA’s radar was seeing.” [7] The 9/11 Commission also has backed up direct Secret-Service-FAA communications in their final report. [8] The Secret Service knew all these things and were just a “hey, you!” away from Cheney’s ear and Bush’s.

The communication abilities of the Secret Service also, apparently, extended into the military chain of command, their contacts to the very front lines of the battle. Recall that it was the Secret Service who called the Langley fighter pilots around 9:55 and told them to “protect” the White House (though with no mention of precisely how). [9] They also called Andrews Air Force Base, near the Pentagon, shortly after 9:03 to request fighter jets, which didn’t get any off the ground until 10:42. [10]

Bush's famous shot talking to Cheney from Air Force One
So the Secret Service - and thus both Bush and Cheney - were as in the communications loop as they wanted to be. There was two-way access to all information from FAA, regional Air Force bases, and even the actual fighter pilots, and probably also NORAD, NMCC, etc. So why, with access to a bird’s eye view of the situation and universal communications at Cheney’s and the President’s fingertips, wasn’t an adequate defense marshaled? The story that the phones didn’t work well that day, that Cheney couldn’t talk to the Pentagon and get his intelligence briefings from CNN at the same time, etc. does not pan out well. Something else, probably something sinister, had to be behind this curiously long roster of excuses.

[1], [2], [3], [5] “Cheney recalls taking charge from bunker.” CNN. September 12, 2002. Accessed at: http://archives.cnn.com/2002/ALLPOLITICS/09/11/ar911.king.cheney/
[4] 9/11 Commission Final Report. Page 40.
[6] Thompson and the CCR. "The Terror Timeline." Page 375.
[7] Ruppert, "Crossing the Rubicon." Page 427.
[8] 9/11 Commission Final Report. Page 41.
[9] Thompson and the CCR. "The Terror Timeline." Page 436.
[10] Thompson and the CCR. Page 458.

Thursday, March 22, 2007

FAA IV: SLINEY'S AUTHORITY, UNLIMITED YET UNSURE

Ben Sliney’s Odd Initiation
Adam Larson
Caustic Logic / They Let It Happen
March 22 2007


Benedict Sliney, on the set of “Flight 93,” (2006), reliving his high-pressure first day as FAA national operations manager

Besides the NMCC and Joint Chiefs of Staff, the Federal Aviation Administration, through whose system the 9/11 attacks occurred, was in weird hands on that weird day. Benedict Sliney had experience with FAA air traffic control dating back to 1964, but from the early 1980s took an 18-year hiatus to practice law in Manhattan. [1] He made a name for himself defending NY’s transit authority against passenger lawsuits, and once suing the FAA on behalf of fellow air traffic controllers. He gave up law in mid-2001, which he surrendered only, he says, after his 72-year-old secretary unexpectedly retired.

“I could not work without her, […] I wasn't going to continue. I didn't like law anyhow, it paid well, but it's very demanding in terms of time. I maintained my friendship of course with people in the FAA. The person in charge of the command center asked me, when I would complain about the law to come back to the FAA and I did.” [2]

This was apparently in mid-2001 when some combination of FAA connections, leadership skills, whatever, gave him a sudden career change back to the Administration, and straight to the top: National Operations Manager, a short, powerfully titled post described by USA Today as “the chess master of the air traffic system.” The paper explained “when he accepted the job overseeing the nation's airspace a few months earlier, Sliney wanted to be sure he had the power to do the job as he saw fit. "What is the limit of my authority?" he asked the man who had promoted him. "Unlimited," he was told.” [3] He got the job, and over the next several weeks set to re-learning the ropes and the two decades of technological and procedural changes since his old days.

It was hoped he’d learn enough to fulfill his normal, routine, functions. But Sliney’s new job also made him the man who would, theoretically, be responsible for such unprecedented things as ordering nationwide ground-stop of all air traffic, not that it ever had been an issue before. And he would also be the very guy in charge of requesting fighter assistance in the event of a suicide hijacking, on the off-chance that should ever be needed, which also had never ever happened once in the US. So perhaps understandably, these more esoteric duties were seemingly passed over a bit.

Tuesday being the slowest air travel day, little was expected (?) as Sliney clocked in for his first day at the FAA national operations center in Herndon Virginia, smack between Dulles Airport, the capital, and the Pentagon, at some time before 8:00 am on September 11. But it didn’t stay quiet for long; “It was a very short time,” Sliney later remembered, before he received the first clue this day would not be routine. At about 8:25 am, one of his assistant informed him “that they had an admission that a flight attendant was stabbed. Now it's starting to take a road that we hadn't been down before. It swiftly escalated after that.” [4] Somewhat less swiftly, the FAA response to the unfolding attack, largely overseen by Sliney, was measured, graduated:

8:15-20ish – Numerous calls sent to FAA from flight attendants Ong and Sweeney onboard Flight 11, clearly telling of a hijacking in progress.

8:24 - a transmission intended for the passengers on Flight 11 but accidentally sent system-wide by the hijackers, was received: "We have some planes. Just stay quiet and you will be OK." After Sliney learned of this line, USA Today reported, “the words will haunt him all morning. "We have some planes." Some? How many?” [5]

Before 8:46 – Sliney later described “an unidentified aircraft,” that is, with no transponder, “at 16,000 feet approaching New York City from the northwest at a pretty moderate ground speed of 300 knots. No one was working and we did not know who the aircraft was.” [6] Without transponders, we're told, it was hard to tell one of the thousands of blips from the next (which, if true, made the system completely useless)

8:46-8:50 - Sliney receives word from New York of a “small plane” crash into the World Trade Center. They turn on CNN in the control center. “That was no small plane, Sliney thinks.” Within minutes his suspicions were confirmed: it was the missing AA11. [7]

9:03 – The second plane, UA175, hits the second tower, and New York’s air space is ordered shut down, a multi-state area cleared of air traffic in the first such unprecedented move of the morning. Realizing this is an attack, and twenty minutes into it, Sliney scrambles to make up for lost time. It was time for bold – but not hasty - action.

9:15 – American Airlines orders no more AA takeoffs in the northeast. No concrete moves from Sliney in Herndon yet, just listing all troubled, possibly hijacked flights on a dry erase board. “The moves aren't strong enough for some of the air traffic specialists at the center,” says USA Today, “who bombard Sliney with advice. "Just stop everything! Just stop it!" The words ring true to Sliney.” [8] Haunted by knowledge of more planes, Sliney responds. Seconds tick by. (one mississippi, two mississippi, three mississippi... ten more minutes pass)

9:25 - AA77 has now been unaccounted for as well, for thirty minutes. Sliney issues another unprecedented order: full groundstop. No FAA controlled flights are to take off, anywhere in the country. The skies are full enough, but it wasn't yet time to order them cleared altogether.

“Amid the shouts and chatter and conflicting reports,” USA Today reported, Sliney “reminds himself: Don't jump to conclusions. Sort it out.” Indeed, deliberation seems his strong point: “since the second Trade Center tower was hit, Sliney has considered bringing every flight down,” the paper reported. It wasn’t until after the Pentagon was hit with AA77 at 9:38 that “the manager in charge of the nation's air traffic system is certain. He has no time to consult with FAA officials in Washington,” and made his snap decision all on his own to have all air traffic get out of the sky ASAP. "Order everyone to land! Regardless of destination!" Sliney shouted, since shouting helps orders get back in time to when they might have done some good. [1] The 9/11 Commission agreed that Sliney “ordered all FAA facilities to instruct all aircraft to land at the nearest airport” at exactly 9:42, 56 minutes after the first strike of the war against his native New York, an hour and twenty minutes after the first hijacking was known of.

Is that slow or fast? There’s not much precedence to judge by, but a faster response is at least feasible, by Sliney’s own account. US News reported in June 2004 that “he says he would have stopped everyone sooner,” had he not been left out of the pre-9/11 terror warning loop. Ominous predictions that had been issued that summer about al Qaeda’s potential air designs “never reached key people like Benedict Sliney.” [10] Whoever preceded Sliney in the NOM position likely had been aware of the threat, considering for example, the August 2001 CIA memo "Islamic Extremist Learns to Fly," and the high-level meeting Richard Clarke called on July 5, including FAA, and warning “something really spectacular is going to happen here, and it’s going to happen soon.” But the manager who might’ve known the score on what to expect, and probably had a better understanding of what could be done in response, was just not working out. And his replacement, being a first-day rookie not clued into the earlier threat assessments, was in effect a blank spacer inserted, by chance we are to believe, into a key spot in the air defense system.

Sliney was not the top link at FAA, of course. He had superiors like FAA administrator Jane Garvey and her deputy Monte Belger, and running all the way up to Transportation Secretary Norman “fuck pilot discretion” Mineta, in the PEOC beneath the White House with Cheney and Rice. But Sliney was the top hands-on guy with radar screens in front of him, called on to make major decisions that morning beside the ground stop. He told the 9/11 Commission about his first call with NORAD, at some point before 8:46:

“NORAD […] asked me if I were requesting a military intervention. And I indicated to NORAD that I'm advising you of the - of the facts of this particular incident. I'm not requesting anything. I wasn't sure I even had the authority to request such a thing. And when the lady persisted at NORAD, I asked her if I could call her back and I went to the domestic event net, which is available to all facilities and most of the major facilities around it, and I queried NORAD and the FAA headquarters as to whether or not I had such authority to ask for intervention by the military or a scramble on this particular aircraft, and they did agree that I had such authority after a discussion on the virtues of collaboration. However, I indicated further when I agreed that we should collaborate on such decisions, but if time did not permit it, did I have that authority, I persisted in that and they said that I did. I didn't know that prior to that moment in time.” [11]

CNN’s Paula Zahn explained further “Mr. Sliney says these conversations took several minutes and by the time he received an answer, the aircraft was past Manhattan,” meaning, I presume, past gone into the WTC. [12] Sliney had unlimited authority but like Bullwinkle the moose, he didn’t know his own strength, at least not precisely enough to do much of use on 9/11. He learned his powers eventually, of course, but too late. I’m not sure how long after 9/11 he held the NOM job, but by the time of his candid and well-covered May 2004 testimony to the 9/11 Commission, he had switched over to Operations Manager for the New York Terminal Radar Approach Control, another slot that had been vital on 9/11. This shows he’s serious about FAA; he didn’t just come on just for 9/11. That would look suspicious...

Pure coincidence is the official reason such man was put into such a spot at just that time, but the agency of chance is already strained enough to explain the events of that morning without adding this to its burden. If indeed Sliney were placed to help facilitate the attacks, it’s important to consider whether his part was really central or important enough to warrant the risk of dropping the spacer into his spot less than an hour before the attacks began. Delays in ground stop and military escorts seem to have had little overall effect, only helping keep the skies as cluttered as normal, limiting radar tracking. Even swift action would not clear the skies immediately anyway. This is secondary. As for his requests for fighter assistance, with or without Sliney’s involvement, fighters were off the ground just after the first plane hit, which is reasonably swift. Even if scrambled sooner, the total disempowerment of the defending fighter pilots was beyond his mandate and would have happened either way. His well-timed placement then serves as another redundant screw-up that helps cancel out the culpability of the others. The precision of the placement makes it also seem a possible distraction, but one engineered in advance, which is telling.

Curiously, Ben Sliney was able to regain the limelight again and add another title to his resume with another unexpected job offer – an actor, playing the part of himself in the 2006 film Flight 93 (which I have yet to see). He had become a piece of history, an ironic 9/11 artifact, the first-day guy! Man what a first day; Murphy’s law, we can all relate to that! He was initially brought on by director Paul Greengrass as an adviser on re-enacting his part of the morning of 9/11 – what it was like at the center, how to accurately reflect the events. Oddly parallel to his actual switch back to FAA moths before 9/11 as a last-minute replacement, Sliney explained in a 2006 interview: “they hired an actor to play me. And he was having a little difficulty with it. And after two days, they asked me to do it. I got a note under the door. 5 in the morning, I was getting ready to go to the set, could you please bring your suit, tie, shoes. At the bottom it said “this is not a test. This is not a drill.” [13]
---------
Back to "Federal Attack Assistance?" Masterlist

Sources:
[1], [2], [4], [13] United 93: An Interview with National Operations Manager Ben Sliney
By Tonisha Johnson April 2006. http://www.blackfilm.com/20060421/features/bensliney.shtml
[3] Adams, Marilyn, Alan Levin and Blake Morrison. “Part II: No one was sure if hijackers were on board.” USA Today. Posting date unlisted.
http://www.usatoday.com/news/sept11/2002-08-12-hijacker-daytwo_x.htm
[5], [7], [8], [9] Part I: Terror attacks brought drastic decision: Clear the skies
By Alan Levin, Alan, Marilyn Adams and Blake Morrison, USA Today. August 13 2002.
http://www.usatoday.com/news/sept11/2002-08-12-clearskies_x.htm
[6], [11] Benedict Sliney Testimony 9/11 Commission. May 21 2004. Via CNN. http://transcripts.cnn.com/TRANSCRIPTS/0406/17/pzn.00.html
[10] Levine, Samantha. “In the skies, a scary 'failure of imagination.” US News And World Report. June 28 2004. Posted June 20 2004. http://www.usnews.com/usnews/news/articles/040628/28nine11.b.htm
[12] Paula Zahn Now. “Chilling Audio From 9/11 Hijack Played at Hearing.” Aired June 17, 2004. Transcript: http://transcripts.cnn.com/TRANSCRIPTS/0406/17/pzn.00.html

Monday, February 26, 2007

FAA I: THE COVER-UP ON PAGE 34

Adam Larson
Caustic Logic / They Let It Happen
2/27/07


The current official story of what precisely happened on 9/11 has changed repeatedly, from the first chaotic report to the stalled and limited investigations culminating with the 9/11 Commission. Some major changes ere set in stone with the publication of their final Report in mid-2004. One that caught my attention was the assymmetry of White House accounts and evidence over the shoot-down order passed from Bush to Cheney at some vague time after 10:00 am. While all their evidence points to a call at 10:18 officially the Commission maintained the White House story that the call was placed at about 10:10, neither Bush nor Cheney recalls exactly when, and no records exist. [1]

Another changed story I’d noticed also became a central focus of "Nick7261" at Above Top Secret, who posted what he felt was “the strongest evidence of some sort of government cover-up.” He found this compelling seam in the pages of the 9/11 Commission’s final report, where they pointed out that NORAD had given them “incorrect” information regarding their awareness of and reaction to the hijackings of Flight 93 and 77. This is pivotal, since even many skeptics can see why the NY attack planes could have slipped through our defenses by sheer earliness and the whole “it’s never happened before” thing. By 9:03 am it had happened twice, and was looking to happen again, reportedly as many as eleven planes were suspected hijacked, and still no defenses showed late enough in the game to shoot AA77 or UA93 out of the sky. This might seem embarrassing to some.

Regarding the May 2003 testimony of NORAD officials, the Commission found three main issues of contention:
1) at 9:16 am NEADS (North East Air Defense Sector) received notification from the FAA that Flight 93 was hijacked.
2) NORAD received notification at 9:24 am that Flight 77 was hijacked.
3) As the Commission put it: “In their testimony and in other public accounts, NORAD officials also stated that the Langley fighters were scrambled to respond to the notifications about American 77, United 93, or both.”

Chairmen Kean and Hamilton and their cohorts decided all these assertions were “incorrect,” and chose to publish another, stranger version. But rather than simply alter the record silently, they drew attention to the changes in the text of their actual report, on page 34. Regarding the first point, NEADS’ notice of 93’s hijacking, they explained “this statement was incorrect. There was no hijack to report at 9:16. United 93 was proceeding normally at that time.” Indeed, by my research, the hijacking seems to have occurred at just about the time the pentagon was stricken at 9:37.

The Commission give no explanation of how NEADS was able to submit a timeline that was clearly false on at least this point; not having been given one, they probably didn’t feel like guessing a reason. The closest they came was in hinting “those accounts had the effect of deflecting questions about the military’s capacity to obtain timely and accurate information from its own sources. In addition, they overstated the FAA’s ability to provide the military with timely and useful information that morning.” (p 34) They didn’t like to look weak, so they overstated their abilities, both internally and with regard to FAA.

But either way, their explanation for the other two less-than correct statements are more interesting and bring us to our first major anomaly. The Commission found that NORAD had been informed by an unnamed FAA employee that Flight 11 did not fly into the WTC and was heading south towards Washington. Nick found on study “out of the entire 567-page 9/11 Commission Report, only one page covers how Flight 77 was able to avoid U.S. Air Defense and hit the Pentagon,” and that’s page 34, where they clarified that the Capital’s air defense was gunning for a ghost while a third real weaponized airliner, and soon a fourth, was targeting DC unseen. This is explosive evidence, indicating to me something, at best, on the far side of negligence.

So after the report’s release, we have two stories, one covering the other. Nick wondered if the new version were true, who gave the false info on Flight 11, why, and why the anonymity? And if the original NORAD version delivered under oath were true, then why did the Commission replace it with the new FAA version instead without seeking clarification on that perjured testimony? Certainly budgetary restraints, time pressures, and limited subpoena powers would be cited if we asked, but either way, there’s a slew of questions left unanswered, and possibly a cover-up. Nick speculated as one possibility that “the 9/11 Commission fabricated the story that the fighters were chasing a plane that didn't exist to explain how two hijacked planes were flying unimpeded towards their targets.” I had to admit it sounded plausible, and started digging in a little bit.

Next: The Phantom Flight 11
Back to FAA Masterlsit

Sources:
[1] 9/11 Commission Final report, pages 40-41.
[2] Ibid. Page 34.

Wednesday, December 27, 2006

Suited Up for Standard Procedure

To this day, opinions differ as to whether or not scrambling fighter jets was considered standard procedure in air emergencies at the time of the attacks or whether, as Popular Mechanics argued in March 2005, this was something rare and extraordinary. In their cover story “Debunking 9-11 Lies,” they tried to explain NORAD’s delays and failures by pointing out lamely that "in the decade before 9/11, NORAD intercepted only one civilian plane over North America: golfer Payne Stewart's Learjet, in October 1999 […] it took an F-16 1 hour and 22 minutes to reach the stricken jet. […] Prior to 9/11, all other NORAD interceptions were limited to offshore Air Defense Identification Zones (ADIZ). The ADIZ areas seem to be a sort of moat 'round the castle, where incoming international flights are made to identify themselves or risk being taken out. They run along the East and West Coasts and along the Mexican and Canadian borders. "Until 9/11 there was no domestic ADIZ," FAA spokesman Bill Schumann told the magazine. [1]

They would probably have liked to say there were no intercepts at all over continental airspace, but had to cede the one instance after it was pointed out in the factual record by 9-11 revisionists, an errant plane that crossed no borders or ocean shores and yet triggered a fighter escort. On October 26, 1999, famous pro Golfer Payne Stewart was flying in his private Learjet when the cabin lost pressure and killed all on board. The plane continued on autopilot across several states, trailed by fighter jets until it finally crashed in North Dakota. The shoot-down option was publicly addressed at the time: The Washington Post reported “Pentagon officials said they never considered shooting down the Learjet” because, according to a senior defense official, ‘the (FAA) said this thing was headed to a sparsely populated part of the country, so let it go.’” [2] Now, if it had been a hijacked 757 headed for New York after one plane had already crashed into the World Trade Center…

But was this the only fighter intercept ever ordered over the continental U.S.? If intercepts simply weren't done over the mainland, why was an exception made in this one case and this one case alone? Or did they mean this was the only intercept over America that made the news? According to an article in the Calgary Herald-Tribune from a month after the attack, fighter interception for stray aircraft actually was a weekly occurrence even before 9-11: “Today […] fighter jets are scrambled to babysit suspect aircraft or "unknowns" three or four times a day. Before Sept. 11, that happened twice a week. Last year, there were 425 unknowns -- pilots who didn't file or diverted from flight plans or used the wrong frequency. Jets were scrambled 129 times.” [3] Was every one of these 129 intercepts in the year 2000 over the ocean in ADIZ areas, with none over the continental U.S.? And in the nine years before that too, with the exception of one famous golfer?

Common sense and some evidence indicate otherwise. One of the fighter pilots that was scrambled on 9-11 said in a BBC documentary on his first notification of trouble “they said the Tower [was] calling and something about a hijacking. It was flight American 11, a 767, out of Boston going to California. At the time we ran in and got suited up… It's just peacetime. We're not thinking anything real bad is going to happen out there.” The narrator of the documentary adds “neither pilot at this time has any reason to believe that this is other than a routine exercise.” [4]

This was at some point before American 11 ended – we were still in pre-9-11 peace time, if the last minutes of it, and he knew to get suited up (that is, ready for takeoff) in response to the hijacking of a trans-continental flight. This sounds like a routine, standard procedure scramble and intended intercept over continental airspace to me. Perhaps the Payne Stewart case is not so anomalous after all.


Sources:
[1] Chertoff, Benjamin et al. “Debunking 9/11 Myths.” Popular Mechanics. March 2005.
[2] Walsh, Edward and William Claiborne. “Golfer Payne Stewart Dies in Jet Crash.” Washington Post. October 26, 1999. Page A1.
[3] Slobodian, Linda.
“NORAD on Heightened Alert.” The Calgary Herald. October 13, 2001.
[4] BBC Video. Clear the Skies. First Aired September 2002.

Friday, December 22, 2006

WARGAME 2: NORTHERN VIGILANCE

OPERATION NORTHERN DISTRACTION

First revealed by the Toronto Star as early as December 9 2001, Northern Vigilance was set up in the arctic with Canadian assistance. As the exercise opened, NORAD explained on September 9 that it was a follow up to Operation Northern Denial, and like it was meant “to monitor a Russian air force exercise” happening just on the other side of the North Pole. [8] The Russians in fact cancelled this exercise as soon as they heard word of the attack in New York.[9]

The Northern Vigilance exercise thus drew fighters away from the East Coast that day, leaving them stationed near the Arctic Circle. One news story claimed “investigators at the September 11 Commission confirm they are investigating whether NORAD’s attention was drawn in one direction – toward the north pole – while the hijackings came in from an entirely different direction.” [10] I'm not sure how many fighter were there or how many of these may have been active in the defense otherwise, but there is a crucialirony here. The predecessor exercise Northern Denial indicates a desire to "deny" the Russians this attack route across the North Pole, but this curiously outdated drill, by drawing fighters and attention north, may have helped open another attack route for a different enemy on the East Coast at just the right time.

Northern Vigilance also reportedly involved radar “inserts,” blips that would look like attacking planes or other airborne objects on the attack but in reality would represent nothing. How many inserts were used, on whose screens, and inserted into which air traffic regions are all questions that remain unanswered. As it became clear an attack was underway, at 9:00 am, NORAD (officially) cancelled the exercise and erased the inserts. [11] But until that time at least, they couldn’t help but add to the confusion in the air.

Monday, December 11, 2006

OTIS AND LANGLEY

SCRAMBLING AGAINST THE CLOCK

According to the official pre-2004 timeline supplied by NORAD, Boston flight control had waited twenty minutes after it decided Flight 11 was hijacked to alert them, at 8:40 am. This has been widely contested, with FAA insisting it had alerted NORAD much earlier. But anyway, at 8:46 NORAD issued the scramble order to Otis Air National Guard base in Cape Cod, Massachusetts – the same minute flight 11 slammed into the North Tower. The first two F-15 pilots, Lt. Col. Timothy Duffy (code-named “Duff”) and Major Daniel Nash (“Nasty”), were off the ground to intercept American 11 six minutes later, at 8:52.

This yielded a 39-minute loss-of-contact to takeoff time for Otis. This delay, coming after months of foreign and domestic warnings of possible hijackings, is 50%, longer than reaction in the totally unexpected Payne Stewart case two years earlier. These fighters were sent to intercept American 11 six minutes after it was obliterated in its impact with the WTC. [1] They finally arrived and established a combat air patrol over Manhattan at 9:25, 33 minutes after takeoff. [2]

At about this time, more jets were scrambled from Langley AFB in Virginia, the other ready pair in the northeast. NEADS called Langley at about 9:15 and asked national guardsman “Honey” urgently “how many planes can you send?” “We have two ready,” Honey replied. “That’s not what I asked,” came the curt reply. “How many can you get airborne?” “With me, three.’” Honey said.” [3] It’s not clear why there was an insistence on sending a third jet when standard procedure was to send a pair – I looked for clues in the 9/11 Commission’s final report, but it does not seem to mention the number of fighters sent from Langley. Since only two fighters were ready, prepping this third plane would set their schedule back. “Honey,” his partner “Lou,” and the unnamed third pilot took off at 9:30, just minutes before flight 77 reappeared on radar screens closing in on Washington. The CCR lists the pilots as pilots were Major Brad Derrig, Captain Craig Borgstrom, and Major Dean Eckmann, all from the North Dakota Air National Guard’s 119th Fighter Wing, then stationed at Langley, but I cannot find who was Honey, who was Lou, and ho as the third. The commission concluded they were not being sent to intercept American 77 closing in on Washington, but rather to New York to back up the Otis pilots. [4]

This was the entire first wave of national defense – five fighters, scrambled late from two bases far from the scene of the crime. More fighters would join them by about 10 am, but during the actual attack, the first wave was all there was. The following sections detail their mission, doomed to failure from the beginning.

(also linked on the air defense masterlist)

- Heading and Speed

- Information shared with the defending fighter pilots: RIDICULOUSLY inadequate

- No shoot-down order received.

Sources:
[1] North American Aerospace Defense Command News Release. “NORAD’s Response Times” September 18, 2001. Accessed May 7, 2003 at: http://www.unansweredquestions.org/timeline/2001/norad091801.html
[2] National Commission on Terrorist Attacks Upon the United States. The 9/11 Commission Report. Authorized First Edition. New York. W.W. Norton. 2004. Page 24.
[3] "9;30 am: Langley Fighters Take Off." http://www.cooperativeresearch.org/context.jsp?item=a930langleylaunch#a930langleylaunch
[4] Longman, Jere. Among the Heroes: United Flight 93 and the Passengers and Crew who Fought Back. New York. Harper Collins. 2002. Page 65.

Tuesday, November 28, 2006

STAND-DOWN: DE JURE OR DE FACTO?

September 13, 2001: The nation is still staggering, in deep shock over the most devastating act of terrorism in American history. With the body count still not finalized but sitting near 6,000 (well-down from initial estimates of 20,000), General Richard B. Myers, Vice-Chairman of the Joint Chiefs of Staff (JCS), sits under oath in front of the Senate Armed Services Committee. This is his confirmation hearing, scheduled weeks before, to be promoted to the post of JCS Chairman, the highest U.S. military post. It was surely a bittersweet event for him. He had already started his tenure as acting JCS Chairman two days earlier - on the morning of September 11th. He had been standing in for his superior Henry Shelton, who had just that morning left on a trip to Europe on prearranged but unspecified business. [1] In the hearing, this curious coincidence was ignored, but Chairman Carl Levin (D-MI) asked the candidate about the failed military response during the attack, with which Myers was closely involved.

Levin: “Was the defense department asked to take action against any specific aircraft? […] And did you take action against – for instance, there has been statements that the aircraft that crashed in Pennsylvania was shot down. Those stories continue to exist.”
Myers: “Mr. Chairman, the armed forces did not shoot down any aircraft. When it became clear what the threat was, we did scramble fighter aircraft, AWACS, radar aircraft and tanker aircraft to begin to establish orbits in case other aircraft showed up in the FAA system that were hijacked. But we never actually had to use force.”
Levin: “Was that order that you just described given before or after the Pentagon was struck? Do you know?”
Myers: “That order, to the best of my knowledge, was after the Pentagon was struck.”
[2]

With his first-hand knowledge of what happened only two days earlier, he maintained that his military did not scramble any fighters in response until after the Pentagon was hit by the third hijacked plane of the morning at 9:37. This was thirty-five minutes – at least - after a second hijacked airliner plowed into the World Trade Center at 9:03, clarifying to everyone we were at war – and quickly losing. How could the mightiest Air Force on Earth be so slow responding to such an urgent emergency?

This was not merely Myers’ confused recollection; the next day, Major Mike Snyder, a spokesman for the North American Aerospace Defense Command (NORAD), backed him up on this point. According to the Boston Globe: “[Snyder] said the fighters were not scrambled for more than an hour after the first hijacking was reported, by which time the three buildings were struck […] Never before had a hijacked airliner been steered into a skyscraper, Snyder noted, in trying to explain the lack of immediate response.” [3]

So on September 14, that was the official story, confirmed by both Myers and Snyder, by both the JCS and NORAD, and generally taken as fact. Even long after this official story had changed, then-Mayor of New York Rudy Giuliani would confirm this original assessment. He told the 9/11 Commission in May 2004 that he was told he just minutes before the first World Trade Tower collapsed at 9:58 that fighters had just been scrambled to protect New York “twelve minutes ago.” [4] By this account, the jets were airborne at about 9:46, exactly an hour after the first attack in New York.

It became clear with a CBS News broadcast that very night that this was actually not the case, that two fighter pilots had been sent at 8:52 from Massachusetts, and soon we had confirmation of another pair sent from Langley AFB in Virginia at 9:30. So why the early confusion?

I don't know the reason for this incongruity, but I do know the effects. On September 11, NORAD knew as of 8:40 (by their own account) that American 11 was (possibly) hijacked and headed to New York. Three minutes later, they learned a second airliner, United 175, was also (possibly) hijacked. As of 8:46, when flight 11 hit the Word Trade Center, they knew what kind of (possible) hijackings these were – just as UA175 changed course and headed for New York itself. Fighter interception should have been a no-brainer at this point, and authorization to shoot to kill should have been sought swiftly to defend future targets. Yet fifty-one minutes later, the new JCS Chairman tells us under oath, NORAD hadn’t got a single fighter off the ground? Honestly, that doesn’t even make sense. It looks like a stand-down.

Rumors began to spread of just this possibility, and persisted well past the reports on 9/14 and after that fighters were scrambled. In September 2003 Michael Meacher, former British Environment Minister, wrote an article for the Manchester Guardian called “This War on Terrorism is Bogus.” He pointed out that no fighters were scrambled from the nation’s premier Andrews Air Force Base, only ten miles from the Pentagon, during the course of the attack. Meacher wondered “was this inaction simply the result of key people disregarding, or being ignorant of, the evidence? Or could US air security operations have been deliberately stood down on September 11? If so, why, and on whose authority?” [5]

It’s a good question; Andrews is the nation’s premiere Air Force base, home of Air Force One, and touchdown point for world leaders visiting the U.S. It is in many ways the central staging ground for the most elaborate airspace defense in the world – yet no fighters were sent from there until well after the attack was over with. Mark R. Elsis of StandDown.net. put it “there is only one explanation. Our Air Force was ordered to stand down on 9/11.” [6]

I had always found a direct stand-down order a possibility, but too simple of one – did Meacher and Elsis mean an indirect, de facto stand-down or a direct, de jure one? A formal stand-down order is an order, official, total, and enforced as such. Are we really to believe that of the hundreds of pilots ready to take off and help in such a crisis, all told by their superiors to stay on the ground, none would be angry and courageous enough to speak up? Even I, in my profound cynicism, find this hard to swallow. A de jure stand-down seems unlikely to me, and a simplistic argument that looks for an easily identifiable smoking gun of complicity.

Mike Ruppert took this line as well in mid-2004: “There never was a stand down order issued. That would have been way too incriminating and risky a piece of evidence. And it also might have been ignored by eager fighter pilots who had trained their whole lives to respond to a hostile aircraft killing Americans. There are several statements that the "new" NORAD procedures transferring scramble authority to Rumsfeld on June 1, 2001 were ignored by several NORAD commanders on 9/11 including General Larry Arnold. That's exactly what I would have expected.” [7]

However, a close look at the facts reveals an air defense system not just broken but peculiarly broken on that “fateful” morning, with the same net result as a de facto stand-down order. That is, stand down or no, the defense was as ineffective as if there had been, and it hardly seems any less purposeful than Meacher or Elsis suggests.


Sources:
[1] Balz, Dan and Bob Woodward. “America's Chaotic Road to War: Bush's Global Strategy Began to Take Shape in First Frantic Hours After Attack.” Washington Post. January 27, 2002. Page A01. Accessed November 6, 2004 at: http://www.washingtonpost.com/ac2/wp-dyn/A42754-2002Jan26
[2] General Richard B. Myers, Senate Confirmation Hearing. Senate Armed Services Committee. September 13, 2001. Accessed August 5, 2005 at: http://www.attackonamerica.net/genrichardbmyerssenateconfirmationhearing9132001.htm
[3] Johnson, Glen. "Facing Terror Attack's Aftermath: Otis Fighter Jets Scrambled Too Late to Halt The Attacks" The Boston Globe. September 15, 2001 Third Edition Page A1. Accessed at: http://emperors-clothes.com/9-11backups/bg915.htm
[4] Thompson, Paul and the Center for Cooperative Research. The Terror Timeline: Year by Year, Day by Day, Minute by Minute. New York. Regan books. 2004. Page 439
[5] Ruppert, Michael C. Crossing the Rubicon: The Decline of the American Empire at the End of the Age of Oil. Gabriola Island, BC, Canada. New Society Publishers 2004 P. 309
[6] Chertoff, Benjamin et al. “Debunking 9/11 Myths.” Popular Mechanics, March 2005. http://www.popularmechanics.com/technology/military_law/1227842.html?page=3
[7]Ruppert, Michael C. http://www.fromthewilderness.com/free/ww3/060704_tripod_fema.html

Sunday, November 26, 2006

Wargame One: Vigilant Guardian

OPERATION VIGILANT GUARDIAN: The ironically dubbed “Vigilant Guardian” was the first to be widely acknowledged, notably in the BBC’s excellent 2002 documentary Clear the Skies. The exercise, as the official one-paragraph web page explains, was a regular, yearly exercise designed to simulate a “crisis to North American Air Defense outposts nationwide.” [1] As a result of Vigilant Guardian, according to NEADS Commander Colonel Robert Marr, “The fighters were cocked and loaded, and even had extra gas on board.” [2] Exact details remain classified, but it was a multi-day exercise, already going on for at least a day as the attacks began.

Three different accounts of first notification of a hijacking indicate that there were to be simulated hijackings in at least Vigilant Guardian: Major General Larry Arnold said “the first thing that went through my mind was, is this part of the exercise? Is this some kind of a screw-up?” [3] Sergeant Jeremy Powell at NEADS, where Vigilant Guardian was being carried out, was contacted by Boston Flight Control at 8:38 am. The Boston controller told him there was a hijacked plane headed to New York. Powell responded “is this real-world or exercise?” He received the answer “no this is not an exercise, not a test.” [4]

The most relevant account is that of Lt. Colonel Dawne Deskins. As NEADS regional overseer of Vigilant Guardian, she should have understood better than anyone what to expect from the drill. Newhouse News Service reported her response to the crisis: "At 8:40, Deskins noticed senior technician Jeremy Powell waving his hand. Boston Center was on the line, he said. It had a hijacked airplane. “It must be part of the exercise,” Deskins thought. At first, everybody did. [After clarifying with FAA] Deskins ran up a short flight of stairs to the Battle Cab and reported the hijacked plane real world, not a simulation.” [5]

Name Meaning: “Vigilant or Amalgam means it is a HQ NORAD sponsored exercise. Guardian means it is a multi-command CPX, or command post exercise (no live-fly). So on 9/11, NORAD was conducting a NORAD-wide, multi-command, command post exercise with no live-fly." - Major Don Arias, NORAD press spokesman who was on duty and involved in the response the morning of 9/11, to Mike Ruppert. As reprinted in Crossing the Rubicon, page 368.

Sources:
[1] http://www.globalsecurity.org/military/ops/vigilant-guardian.htm
(the original page had this quote, but by 2006 the page makes no mention of a crisis but explains it is now "conducted in conjunction with USCINCSTRAT-sponsored GLOBAL GUARDIAN and USCINCSPACE-sponsored APOLLO GUARDIAN exercises. The exercise involves all HQ NORAD levels of command and is designed to exercise most aspects of the NORAD mission.")
[2] Scott, William B. “Exercise Jump-Starts Response to Attacks.” Aviation week’s Aviation Now. June 3, 2002. Accessed April 27, 2003 at: http://www.aviationnow.com/content/publication/awst/20020603/avi_stor.htm
[3] ABC News. “Terror Hits the Towers: How Government Officials Reacted
to Sept. 11 Attacks.” September 14, 2002. Accessed at: http://abcnews.go.com/onair/DailyNews/sept11_moments_1.html
[4] 9/11 Commission Final Report. Page 20
[5] Hart, Seely. “Amid Crisis Simulation, 'We Were Suddenly No-Kidding Under Attack.'” Newhouse News Service. January 25, 2002. Accessed May 7, 2003 at: http://www.unansweredquestions.org/timeline/2002/newhousenews012502.html

A Yawning Gap

On the evening of September 14 the first story of the Air Force response to the three-day old attack was aired on CBS News.- The two F-15 pilots were scrambled from Otis AFB on Cape Cod, Massachusetts at 8:52, just after the first plane's impact but well before the second. Despite what officials had thus far said, it seemed fighters did get airborne during the attack. This made us feel a little better.

After this news was reported, the official stance changed. On the 18th, NORAD published their final initial timeline, including the Otis scramble time as 8:52, and an additional scramble of fighters from Langley Air Force Base at 9:30, ceding two scrambles before the Pentagon was hit. This timeline changed yet again in 2004 as the 9/11 Commission released its findings. Most of the facts that follow are from this newer version of events (the scrambles just mentioned are agreed on in both versions).

At the time of the attacks, only fourteen fighters were routinely kept on ready and alert status across the US mainland. These were deployed and scrambled in pairs, so these fighters represented only seven actual deployments. Nearly all reported pre-9/11 threats of terrorist attacks, some involving hijackings, focused on New York or Washington D.C. Yet on that morning, only two of these seven deployments were in the Northeast sector, thick with air traffic (about 50% of the national total) and with threats against it (nearly all threats targeted New York or Washington). The BBC quoted Colonel Robert Marr, Commander of the North East Air Defense Sector (NEADS), as saying “I had determined, of course, that with only four aircraft we cannot defend the whole north eastern United States.” Worse, these deployments were on the northern and southern fringes of the area of vulnerability, in each case about 150 miles away from the nearest targeted site. One newspaper wondered why NORAD had left “what seems to be a yawning gap in the midsection of its air defenses on the East Coast – a gap with New York City at the center.”

Fighter Deployments

> DEPLOYMENT KEY:
(Graphic by the Author, based on post-9/11 research - exact basing at the time of the attack is not clear, but clearly seems inadequate for what unfolded that day, revealing, at best, poor planning of the air defenses in a time of heightened alert)
1) Hancock Field Air National Guard Base (ANGB), Syracuse, NY. 174th Fighter Wing. Very close to Rome, NY HQ of NEADS.
2) Barnes ANGB, MA. 104th Fighter Wing
3) Bradley ANG base, CT. 103rd Fighter Wing.
4) Otis AFB, Falmouth, MA. Postings and status unclear. Scrambled two F-16s at 8:52.
5) Willow Grove, PA. 11th Fighter Wing.
6) Atlantic City ANGB, NJ. 177th Fighter Wing. Atlantic City had two F-16s In the air on 9/11 for a bombing exercise near the city. Boston flight controllers tried to contact the base at 8:34, but the phone just rang. They weren’t on “ready” status as they had been in previous years. This fighter pair was finally sent to Washington after 10:00.
7) Andrews AFB - it's actually closer than it looks here, only 10 miles from the Pentagon - home of the 113th wing DC Air National Guard and the Air National Guard Readiness Center. They did not get fighter off the ground on 9/11 until 10:42, and these were sent up without missiles. The pair sent had been in the air on a training mission in South Carolina as the attack began.
8) Langley AFB, VA. 10th Intelligence Squadron, Air Force Doctrine Center, Air Combat Command, 1st Fighter Wing. Scrambled two F-15s and an unidentified third plane at 9:30.