It’s claimed that NORAD didn’t recognise the potential danger from airliners being hijacked and used as “guided missiles”. If you’ve not done so already, it’s worth reviewing what the 9/11 Commission said about this:

Institutionalizing Imagination: The Case of Aircraft as Weapons

Imagination is not a gift usually associated with bureaucracies. For example, before Pearl Harbor the U.S. government had excellent intelligence that a Japanese attack was coming, especially after peace talks stalemated at the end of November 1941. These were days, one historian notes, of "excruciating uncertainty."The most likely targets were judged to be in Southeast Asia.An attack was coming,"but officials were at a loss to know where the blow would fall or what more might be done to prevent it."11 In retrospect, available intercepts pointed to Japanese examination of Hawaii as a possible target. But, another historian observes,"in the face of a clear warning, alert measures bowed to routine."12

It is therefore crucial to find a way of routinizing, even bureaucratizing, the exercise of imagination. Doing so requires more than finding an expert who can imagine that aircraft could be used as weapons. Indeed, since al Qaeda and other groups had already used suicide vehicles,namely truck bombs,the leap to the use of other vehicles such as boats (the Cole attack) or planes is not far-fetched.

Yet these scenarios were slow to work their way into the thinking of aviation security experts. In 1996, as a result of the TWA Flight 800 crash, President Clinton created a commission under Vice President Al Gore to report on shortcomings in aviation security in the United States.The Gore Commission's report, having thoroughly canvassed available expertise in and outside of government, did not mention suicide hijackings or the use of aircraft as weapons. It focused mainly on the danger of placing bombs onto aircraft -- the approach of the Manila air plot.The Gore Commission did call attention, however, to lax screening of passengers and what they carried onto planes.

In late 1998, reports came in of a possible al Qaeda plan to hijack a plane. One, a December 4 Presidential Daily Briefing for President Clinton (reprinted in chapter 4), brought the focus back to more traditional hostage taking; it reported Bin Ladin's involvement in planning a hijack operation to free prisoners such as the "Blind Sheikh," Omar Abdel Rahman. Had the contents of this PDB been brought to the attention of a wider group, including key members of Congress, it might have brought much more attention to the need for permanent changes in domestic airport and airline security procedures.13

Threat reports also mentioned the possibility of using an aircraft filled with explosives.The most prominent of these mentioned a possible plot to fly an explosives-laden aircraft into a U.S. city. This report, circulated in September 1998, originated from a source who had walked into an American consulate in East Asia. In August of the same year, the intelligence community had received information that a group of Libyans hoped to crash a plane into the World Trade Center. In neither case could the information be corroborated. In addition, an Algerian group hijacked an airliner in 1994, most likely intending to blow it up over Paris, but possibly to crash it into the Eiffel Tower.14

In 1994, a private airplane had crashed onto the south lawn of the White House. In early 1995,Abdul Hakim Murad -- Ramzi Yousef 's accomplice in the Manila airlines bombing plot -- told Philippine authorities that he and Yousef had discussed flying a plane into CIA headquarters.15

Clarke had been concerned about the danger posed by aircraft since at least the 1996 Atlanta Olympics.There he had tried to create an air defense plan using assets from the Treasury Department, after the Defense Department declined to contribute resources.The Secret Service continued to work on the problem of airborne threats to the Washington region. In 1998, Clarke chaired an exercise designed to highlight the inadequacy of the solution. This paper exercise involved a scenario in which a group of terrorists commandeered a Learjet on the ground in Atlanta, loaded it with explosives, and flew it toward a target in Washington,D.C. Clarke asked officials from the Pentagon, Federal Aviation Administration (FAA), and Secret Service what they could do about the situation. Officials from the Pentagon said they could scramble aircraft from Langley Air Force Base, but they would need to go to the President for rules of engagement, and there was no mechanism to do so.There was no clear resolution of the problem at the exercise.16

In late 1999, a great deal of discussion took place in the media about the crash off the coast of Massachusetts of EgyptAir Flight 990, a Boeing 767.The most plausible explanation that emerged was that one of the pilots had gone berserk, seized the controls, and flown the aircraft into the sea. After the 1999 -- 2000 millennium alerts, when the nation had relaxed, Clarke held a meeting of his Counterterrorism Security Group devoted largely to the possibility of a possible airplane hijacking by al Qaeda.17

In his testimony,Clarke commented that he thought that warning about the possibility of a suicide hijacking would have been just one more speculative theory among many, hard to spot since the volume of warnings of "al Qaeda threats and other terrorist threats,was in the tens of thousands -- probably hundreds of thousands."18 Yet the possibility was imaginable, and imagined. In early August 1999, the FAA's Civil Aviation Security intelligence office summarized the Bin Ladin hijacking threat. After a solid recitation of all the information available on this topic, the paper identified a few principal scenarios, one of which was a "suicide hijacking operation."The FAA analysts judged such an operation unlikely, because "it does not offer an opportunity for dialogue to achieve the key goal of obtaining Rahman and other key captive extremists. . . . A suicide hijacking is assessed to be an option of last resort."19

Analysts could have shed some light on what kind of "opportunity for dialogue" al Qaeda desired.20 The CIA did not write any analytical assessments of possible hijacking scenarios.

One prescient pre-9/11 analysis of an aircraft plot was written by a Justice Department trial attorney. The attorney had taken an interest, apparently on his own initiative, in the legal issues that would be involved in shooting down a U.S. aircraft in such a situation.21

The North American Aerospace Defense Command imagined the possible use of aircraft as weapons, too, and developed exercises to counter such a threat -- from planes coming to the United States from overseas, perhaps carrying a weapon of mass destruction. None of this speculation was based on actual intelligence of such a threat. One idea, intended to test command and control plans and NORAD's readiness, postulated a hijacked airliner coming from overseas and crashing into the Pentagon.The idea was put aside in the early planning of the exercise as too much of a distraction from the main focus (war in Korea), and as too unrealistic. As we pointed out in chapter 1, the military planners assumed that since such aircraft would be coming from overseas; they would have time to identify the target and scramble interceptors.22

We can therefore establish that at least some government agencies were concerned about the hijacking danger and had speculated about various scenarios. The challenge was to flesh out and test those scenarios, then figure out a way to turn a scenario into constructive action.

Since the Pearl Harbor attack of 1941, the intelligence community has devoted generations of effort to understanding the problem of forestalling a surprise attack. Rigorous analytic methods were developed, focused in particular on the Soviet Union, and several leading practitioners within the intelligence community discussed them with us.These methods have been articulated in many ways, but almost all seem to have at least four elements in common: (1) think about how surprise attacks might be launched; (2) identify telltale indicators connected to the most dangerous possibilities; (3) where feasible, collect intelligence on these indicators; and (4) adopt defenses to deflect the most dangerous possibilities or at least trigger an earlier warning.

After the end of the Gulf War,concerns about lack of warning led to a major study conducted for DCI Robert Gates in 1992 that proposed several recommendations, among them strengthening the national intelligence officer for warning.We were told that these measures languished under Gates's successors. Responsibility for warning related to a terrorist attack passed from the national intelligence officer for warning to the CTC. An Intelligence Community Counterterrorism Board had the responsibility to issue threat advisories.23

With the important exception of analysis of al Qaeda efforts in chemical, biological, radiological, and nuclear weapons,we did not find evidence that the methods to avoid surprise attack that had been so laboriously developed over the years were regularly applied.

Considering what was not done suggests possible ways to institutionalize imagination.To return to the four elements of analysis just mentioned:


The CTC did not analyze how an aircraft, hijacked or explosivesladen, might be used as a weapon. It did not perform this kind of analysis from the enemy's perspective ("red team" analysis), even though suicide terrorism had become a principal tactic of Middle Eastern terrorists. If it had done so,we believe such an analysis would soon have spotlighted a critical constraint for the terrorists -- finding a suicide operative able to fly large jet aircraft.They had never done so before 9/11.

The CTC did not develop a set of telltale indicators for this method of attack. For example, one such indicator might be the discovery of possible terrorists pursuing flight training to fly large jet aircraft, or seeking to buy advanced flight simulators.

The CTC did not propose, and the intelligence community collection management process did not set, requirements to monitor such telltale indicators.Therefore the warning system was not looking for information such as the July 2001 FBI report of potential terrorist interest in various kinds of aircraft training in Arizona, or the August 2001 arrest of Zacarias Moussaoui because of his suspicious behavior in a Minnesota flight school. In late August, the Moussaoui arrest was briefed to the DCI and other top CIA officials under the heading "Islamic Extremist Learns to Fly."24 Because the system was not tuned to comprehend the potential significance of this information, the news had no effect on warning.

Neither the intelligence community nor aviation security experts analyzed systemic defenses within an aircraft or against terroristcontrolled aircraft, suicidal or otherwise. The many threat reports mentioning aircraft were passed to the FAA.While that agency continued to react to specific, credible threats, it did not try to perform the broader warning functions we describe here. No one in the government was taking on that role for domestic vulnerabilities.

Richard Clarke told us that he was concerned about the danger posed by aircraft in the context of protecting the Atlanta Olympics of 1996,the White House complex,and the 2001 G-8 summit in Genoa. But he attributed his awareness more to Tom Clancy novels than to warnings from the intelligence community. He did not, or could not, press the government to work on the systemic issues of how to strengthen the layered security defenses to protect aircraft against hijackings or put the adequacy of air defenses against suicide hijackers on the national policy agenda.

The methods for detecting and then warning of surprise attack that the U.S. government had so painstakingly developed in the decades after Pearl Harbor did not fail; instead, they were not really tried.They were not employed to analyze the enemy that, as the twentieth century closed,was most likely to launch a surprise attack directly against the United States.

9/11 Commission Report
Pages 344-348
or
http://pocket-pc-ebook-reader.com/en/911/11.01.Imagination.htm