{"id":222,"date":"2009-09-07T07:45:10","date_gmt":"2009-09-07T11:45:10","guid":{"rendered":"https:\/\/www.oredigger61.org\/?p=222"},"modified":"2011-12-05T09:17:23","modified_gmt":"2011-12-05T14:17:23","slug":"9-11-air-defense-response-first-things-first-the-scott-trilogy-part-2","status":"publish","type":"post","link":"https:\/\/www.oredigger61.org\/?p=222","title":{"rendered":"9-11: Air Defense Response; first things first, the Scott Trilogy (part 2)"},"content":{"rendered":"

This is the second in a series of three articles concerning the Scott trilogy.\u00a0 To set the stage, I recommend a reading of the short introductory article and the article concerning the first of William Scott’s three articles published in 2002.\u00a0 In this article we will consider Scott’s second article, “Command Cells Speed Airspace Reactions<\/strong><\/span><\/a>,” published June 10, 2002.<\/p>\n

FAA\/Military Interface<\/strong><\/p>\n

Government functions because agencies establish relationships with each other to facilitate work and the flow of information.\u00a0 Since the military is a constant presence in air space controlled by the FAA it is natural that such relationships would have developed over time between the military services and the FAA. In this article we will identify and discuss three such relationships in existence on 9-11.\u00a0 The three are the Air Traffic Services Cell (ATSC), the Central Altitude Reservation Function (CARF) and the exchange of liaison officers.<\/p>\n

Some have speculated that because of these relationships the FAA had direct, immediate, and responsive communication with the military concerning the events of the day, in other words what FAA knew in real time the military, especially NORAD, also knew in real time.That was not the case as we shall see.\u00a0None of the three relationships was structured to help with the battle that morning.<\/p>\n

Two, the CARF and the liaison function, were ultimately helpful in establishing a secure communications link between the NMCC and FAA, but not until the fate of all four hijacked aircraft had been determined.\u00a0 All three, especially the ATSC, were extremely helpful the rest of day as the nation transitioned to military control of the sky; they were not helpful in fighting the battle itself.<\/p>\n

Scott’s first article, setting the stage<\/strong><\/p>\n

Scott’s first article is a departure point for our discussion.\u00a0 In that article Scott stated, “the…hijack notification was being passed by phone to a Norad [sic] command center…and the joint FAA\/Defense Dept. Air Traffic Services Cell (ATSC) colocated with the …Command Center in Herndon…”\u00a0 Scott provided no antecedent to tell us who made those two passes.<\/p>\n

Moreover, Scott’s own reference is to a page in a December 2001 AW&ST<\/em> article which simple shows the floor layout at Herndon.\u00a0 There is a desk specifically designated for the DoD\/CARF, but not the ATSC.\u00a0 It was not a desk normally occupied except when needed, according to Herndon managers who briefed the Commission Staff.\u00a0 Two desks in the immediate vicinity were for the Air Traffic Association and the National Business Aircraft Association.\u00a0 Scott’s source article stated that the latter two organizations were represented on the operations floor and “in a fluke, so was what Herndon called the ‘military cell’.”<\/p>\n

Scott set up his second article with this passage in his first article: “The Air Traffic Services Cell [was]created\u00a0 by the FAA and the Defense Dept. for use when needed to coordinate high priority aircraft movements during warfare or emergencies.\u00a0 The Pentagon staffs it\u00a0 only three days per month for refresher training, but Sept. 11 happened to be one of those days.”<\/p>\n

He segued smoothly into a discussion of a small office “established after the 1990-91 Persian Gulf War to facilitate movements of military aircraft in U.S., Pacific and European airspace.\u00a0 Reservists assigned to ATSC have strong backgrounds in fighter, tanker, AWACS and strategic airlift operations.\u00a0 Many were also pilots.”\u00a0 This was not a crisis management operation, it was simply a routinized process set in place to manage significant military use of domestic and foreign airspace.<\/p>\n

Scott goes astray<\/strong><\/p>\n

As we discussed in the first article, Scott had little help to validate what he was being told.\u00a0 He clearly gained the impression that the ATSC was something more than it turned out to be.\u00a0 He assessed it this way.\u00a0 “That experienced cadre…paid dividends on Sept. 11, when the cell quickly became a key communications node during the military’s response to terrorist attacks.”\u00a0 Scott then goes on to give a reasonable account of how valuable the ATSC was, except that value came in the aftermath, well after the battle was over.\u00a0 The ATSC played no role in the response to the four hijacked aircraft that morning.\u00a0 Before we can establish what actually happened we first need to consider the other two interface functions, the CARF and the liaison officers, and we start with the CARF.<\/p>\n

Central Altitude Reservation Function<\/strong><\/a><\/p>\n

The CARF operated a secure facility co-located with the ATSC.\u00a0 Its function is further described in the Robert Williams MFR<\/a>.<\/strong> Among other activities, “the primary space they reserve is for military movement overseas, and for mass military movements.\u00a0 They also handle ‘more unusual’ circumstance [sic] like the dropping of rocket boosters for a space shuttle launch..”<\/p>\n

As a secure facility it had phone lines capable of linking to the NMCC.\u00a0 The Commission Staff determined that sometime in the 10:15 time frame a CARF member, Rayford Brooks, was monitoring the Air Threat Conference Call.\u00a0 Brooks and Williams, both civilian, were two people on duty in the CARF that morning.\u00a0 Although the CARF mission was to provide military interface its work force was civilian, no military personnel were assigned.\u00a0 ATSC was the military cell which, according to the Williams MFR, “co-join[ed] the CARF office for the practicality of proximity for secure information.”<\/p>\n

In order to find out how the CARF ended up as the FAA node on the Air Threat Conference Call we first need to discuss the last of the three interface functions, liaison officers. Scott did not discuss the liaison function in his article.<\/p>\n

Liaison between FAA and NORAD<\/strong><\/p>\n

A long-established liaison relationship existed between FAA and NORAD.\u00a0 At FAA Headquarters that relationship was formalized as “Detachment Two,” the military liaison office at FAA headquarters, commanded that day by Colonel Sheryl Atkins.\u00a0 Each service had its own liaison officer who reported to his\/her service directly but worked administratively under Atkins.<\/p>\n

FAA regional offices also had military liaison officers assigned.\u00a0 In the Northeast those officers were accredited to both the New England Region and the Eastern Region and split their time between the two.\u00a0 None of the liaison officers at any level had crisis management responsibilities.<\/p>\n

In Atkins case she was en route work when AA 11 struck the North tower and was at FAA Headquarters by the time the second plane struck. She went to the 10th floor shortly after AA 77 struck the Pentagon, but reported to the Air Traffic Situation Room not the Washington Operations Center.\u00a0 Atkins and the other liaison officers were effective in the management of airspace in the aftermath but were not engaged in the crisis, itself.<\/p>\n

The liaison relationship was a two-way arrangement.\u00a0 FAA liaison officers were accredited to key NORAD echelons, including NEADS.\u00a0 At NEADS, Steve Culbertson was at the Headquarters when the World Trade Center was twice struck. (Note: Leslie Filson’s notes<\/a> at one point have Culbertson at the Headquarters after the second plane struck and, later, headed for the SOCC before the second plane struck.)\u00a0 My recall is that when he learned that FAA was having difficulty communicating with the military he went to the Sector Operations Center to help.\u00a0 That would be closer to 9:30 and that initiative is documented in the primary sources of the day.\u00a0 The NEADS tapes show that a few minutes after 9:30 Steve Culbertson was looking for a STU-III (secure telephone) and Major Nasypany is heard asking the SOCC Director if Culbertson can use his STU-III.\u00a0 According to the Staff’s interview with Culbertson he estimated that the line was established around 10:15.<\/p>\n

Culbertson and Bill Ayers, the DoD Airspace Manager for NEADS, are among the unsung group of people who struggled that day to bring order out of chaos.\u00a0 Their effort, according to Filson’s notes, became the Domestic Events Network (DEN).<\/p>\n

Back to William Scott<\/strong><\/p>\n

Scott, in his second article discusses only the ATSC.and that’s OK, given the time at which he was writing.\u00a0 He focused on the visible and the tangible and that was the ATSC embedded with the Herndon Center.\u00a0 Our treatment here of the CARF and the Liaison Function between FAA and NORAD completes the record.\u00a0 He teed up the ATSC in his first article and made it the centerpiece for his second article.\u00a0 In his opening sentence to the second article he gets the story right, “a small group of Air Force reservists and FAA air traffic experts [including CARF] started working on the inevitable next phase–how to restore the National Airspace System.”<\/p>\n

And that was their proper role.\u00a0 There should be no expectation that the three linear process in existence discussed in this article could have or should have been engaged earlier than they ultimately were.\u00a0 I will add these three processes\/functions to the growing list of identifiable linear procedures in effect on 9-11.<\/p>\n","protected":false},"excerpt":{"rendered":"

o <\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[20],"tags":[],"class_list":["post-222","post","type-post","status-publish","format-standard","hentry","category-scott-trilogy"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.oredigger61.org\/index.php?rest_route=\/wp\/v2\/posts\/222","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oredigger61.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oredigger61.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oredigger61.org\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oredigger61.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=222"}],"version-history":[{"count":35,"href":"https:\/\/www.oredigger61.org\/index.php?rest_route=\/wp\/v2\/posts\/222\/revisions"}],"predecessor-version":[{"id":5278,"href":"https:\/\/www.oredigger61.org\/index.php?rest_route=\/wp\/v2\/posts\/222\/revisions\/5278"}],"wp:attachment":[{"href":"https:\/\/www.oredigger61.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=222"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oredigger61.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=222"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oredigger61.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}