So according to the shi... posters on this site, War games didn't even exist on 9/11
Hilarious
http://en.wikipedia.org/wiki/War_games_in_progress_on_September_11,_2001
Alright let's take a look at the list:
Operation Northern Vigilance
As the name suggests, this was not a war game or exercise, but an operation. Since the early days of the cold war, it was standard protocol if either side conducted a large scale exercise, for the other side to shadow the exercise with an operation. This was done to avoid being caught by a surprise attack concealed as an exercise.
Northern Vigilance was in response to a large scale Russian long-range bomber exercise being conducted in northern Siberia. In order to monitor the exercise units stationed in Canada, Alaska, and Iceland were raised to operational status. This operation did not affect the seven Contiguous USA Alert Stations.
Global Guardian/Vigilant Guardian
Once a year the US military components responsible for repelling a full scale nuclear attack conduct a major Command Post Exercise called "Guardian". Components include US Strategic Command (Global), NORAD (Vigilant), and US Space Command (Apollo).
Vigilant Guardian was the only aspect of this exercise which involved air defense assets. It's what's called a "Vigilant Overview" exercise. According to NORAD Order 11-33 "Code Words, Nicknames, and Exercise terms", "Vigilant" denotes a NORAD-wide CPX or Command Post Exercise. This means an exercise that involves operations centre staff at computer and radar terminals, but not operational units such as fighter squadrons. Every NORAD command centre has two independent computer systems so that one can be maintaining operational status while the other is used to run system checks and for exercises. This insures that training does not interfere with NORAD's day-to-day operations, and avoids any confusion between exercises and real-world events.
"Overview" is the nickname for a specific exercise type, from a list of NORAD exercise nicknames:
ANGEL - Sector-coordinated Unit Level FIX (ROCC/SOCC Controlled Intercepts)
ARIZONA - Cheyenne Mountain Air Force Base Internal System Training Mission (STM)
BRAVE - Region-sponsored System FIX
CHIEF - JCS-approved, CINCNORAD-sponsored FIX
DOLLY - HQ NORAD Battle Staff Exercise
GAIN - Region/sector-sponsored Internal ROCC/SOCC CPX
GOLD - Sector-coordinated Unit Level FIX (autonomous intercept procedures)
INDIAN - Region-sponsored System CPX
KEYNOTE - Region-coordinated, Sector-sponsored FIX
LEADER - Recall of Airborne Forces (FIX)
LIBEL - Region-coordinated, Sector-sponsored System CPX
MUTE - NORAD IG Evaluation
OVERVIEW - JCS-approved, CINCNORAD-sponsored CPX
PIPE - Region-sponsored Nuclear, Biological, Chemical (NBC) Warning and Reporting System (WRS) Training Exercise
RICE - SOCC-sponsored Internal CPX (Battle Staff/BSSC/Crew training)
SPADE - Region/sector No-Notice AST
UNION - Cheyenne Mountain Air Force Base SPACC Training
VANTAGE - Sector-coordinated/scheduled Interoperability FIX with US Navy Units
VIRGO - Special Exercise or Test (FIX)
WARRIOR - JCS-approved, CINCNORAD-sponsored FIX
YELL - FE14A Exercise
As we can see "Overview" is a Joint Chiefs of Staff-approved, Commander in Chief NORAD-sponsored Command Post Exercise.
Now, Vigilant Guardian started on Monday 10th September, and was to continue through the week. However each day the exercise began at 0900hrs. When the first call came in to NEADS about the hijacking, staff were mingling about or in a pre-exercise briefing in the Battle Cab. Major Nasypany - the Mission Crew Commander, for example, was getting coffee. The ID Technicians were talking about furniture.
Of course that exercise never started, because 23 minutes before it was scheduled to start the call came from Boston ARTCC about a hijacking in progress. The exercise was quickly called off and stations were manned to respond to the hijacking.
What's most important to note is normally the Air Defense Sector, Regional HQ, and NORAD HQ is manned by a skeleton crew. In the event of a major crisis it can take several hours to bring in all of the necessary staff (don't forget most of the staff who manned NORAD command centres were only part time military personnel - they had regular jobs as well).
But because Vigilant Guardian was about to start, NEADS was fully staffed, CONUS Region was fully staffed, and Cheyenne Mountain was fully staffed. This allowed NORAD to respond much more rapidly to the situation that they would have been able to normally.
VIGILANT WARRIOR
We have only Richard Clarke's recollection of an off hand comment made by Richard Myers to reference this particular "exercise". But Myers, when directly asked about it, claimed NORAD was only involved in the CPX I've discussed above. Clarke postulates that Vigilant Warrior was a life-fly (field exercise) element of Vigilant Guardian.
There's some problems with this theory. As we already know, "Vigilant" is reserved for NORAD-wide Command Post Exercises. But from the list I posted we can see that "Warrior" is a Joint Chiefs of Staff-approved, Command-in-Chief NORAD-sponsored Field Exercise. So "Vigilant" and "Warrior" can't go together. In fact the correct first word is "Amalgam" which denotes a NORAD-wide Field Exercise. Amalgam Warrior is NORAD's major field exercise, and involves many operational units.
Amalgam Warrior is held twice a year - in the Spring for the West Coast and in the Fall for the East Coast. Amalgam Warrior was held in June 2001, with the second typically scheduled in October.
NRO Drill
The NRO is entirely independent of NORAD, providing maintainence and operation of the USA's surveillance satellites. On 9/11 their head office was conducting a local evacuation exercise. This had no bearing on NRO operational sites, and as NRO does not interact directly with NORAD, had no bearing on NORAD response times on 9/11. Once the attacks started the exercise was called off and most staff were sent home (a testiment to how little their task had to do with air defense).
Okay. Got any more?
-Gumboot