!! History Commons Alert, Exciting News Context of '(9:03 a.m.) September 11, 2001: Airport Manager Tries Calling Special Ops Personnel at FAA, but Call Goes Unanswered' This is a scalable context timeline. It contains events related to the event (9:03 a.m.) September 11, 2001: Airport Manager Tries Calling Special Ops Personnel at FAA, but Call Goes Unanswered. You can narrow or broaden the context of this timeline by adjusting the zoom level. The lower the scale, the more relevant the items on average will be, while the higher the scale, the less relevant the items, on average, will be.
A number of key senior FAA personnel happen to be away from their usual bases this morning, at the time of the attacks. Bill Peacock, the FAA director of air traffic services, is in New Orleans for a meeting with the National Air Traffic Controllers Association (NATCA). Among his many duties, Peacock is “the ultimate manager of all the air traffic controllers in the country’s system.” He will be transported from New Orleans later in the day in an FAA business jet, one of the few aircraft permitted to fly, and only arrive at FAA headquarters shortly after 5:00 p.m. [Freni, 2003, pp. 12 and 70] Jack Kies, the FAA’s manager of tactical operations, is in Nashua, New Hampshire for a meeting with representatives of the Canadian air traffic control organization. [Freni, 2003, pp. 65-66] Consequently Linda Schuessler, the deputy director of system operations, has to take his place in charge of the FAA Command Center in Herndon, Virginia. [Federal Aviation Administration, 5/18/2006] Tony Ferrante, the manager of the FAA’s air traffic investigation arm, is in Chicago to testify at a hearing. He will become frustrated later in the day about being stuck there, knowing he should he at his post in Washington gathering forensic data on the hijackings and crashes. [Freni, 2003, pp. 7, 19 and 47-48] Rick Hostetler, a member of the FAA’s planning and procedures organization, is at the dentist’s in Waldorf, Maryland when the attacks begin. His job includes acting as the FAA’s primary air traffic liaison for the Secret Service, the US Special Operations Command, and the Pentagon. After seeing the second WTC tower hit live on television, reportedly while sitting in the dentist’s chair, he will quickly set out for his duty station at the FAA Command Center. But due to the heavy traffic, his journey will take hours and the attacks will be over by the time he gets there. [Freni, 2003, pp. 27, 47 and 90] Mike Canavan, the director of the FAA’s Office of Civil Aviation Security, is visiting the airport in San Juan, Puerto Rico. He will only make it back to Washington in the evening, on a special Army flight. [9/11 Commission, 5/23/2003] As part of his job, Canavan is the FAA’s hijack coordinator, responsible for requesting military assistance in the event of a hijacking (see 8:30 a.m. September 11, 2001). [9/11 Commission, 7/24/2004, pp. 17-18] FAA Administrator Jane Garvey is in a breakfast meeting at the Department of Transportation, in Washington, DC. She will quickly relocate to FAA headquarters soon after the first attack (see (8:48 a.m.-9:05 a.m.) September 11, 2001). [Freni, 2003, pp. 62-63] Whether the absence of these senior personnel impairs the FAA’s ability to respond to the attacks is unknown. FAA headquarters in Washington, DC. [Source: FAA]Four minutes after it is informed of the suspected hijacking of Flight 11 (see 8:28 a.m. September 11, 2001), the FAA Command Center in Herndon, Virginia, passes on word of the hijacking to the operations center at FAA headquarters in Washington, DC. The headquarters is apparently already aware of the hijacking, as the duty officer who speaks with the Command Center responds that security personnel at the headquarters have just been discussing it on a conference call with the FAA’s New England regional office. [9/11 Commission, 7/24/2004, pp. 19; 9/11 Commission, 8/26/2004, pp. 11 ] According to the 9/11 Commission, “FAA headquarters is ultimately responsible for the management of the national airspace system,” and the operations center there “receives notifications of incidents, including accidents and hijackings.” FAA headquarters has a hijack coordinator, who is “the director of the FAA Office of Civil Aviation Security or his or her designate.” Procedures require that, if a hijacking is confirmed, the hijack coordinator on duty is “to contact the Pentagon’s National Military Command Center (NMCC) and to ask for a military escort aircraft to follow the flight, report anything unusual, and aid search and rescue in the event of an emergency.” Yet, the Commission will state, although “FAA headquarters began to follow the hijack protocol,” it does “not contact the NMCC to request a fighter escort.” [9/11 Commission, 7/24/2004, pp. 16-19] Mike Canavan, who would normally be the FAA’s hijack coordinator, is away in Puerto Rico this morning, and it is unclear who—if anyone—is standing in for him in this critical role (see 8:30 a.m. September 11, 2001). [9/11 Commission, 5/23/2003; 9/11 Commission, 7/24/2004, pp. 17] The most senior manager on duty at Washington’s Reagan National Airport tries to contact Special Operations personnel at FAA headquarters, but his call is not answered. Bob Lazar, the airport’s acting operations manager, was in his office in the administrative wing of Reagan Airport at the time the first attack in New York took place. Upon hearing news of the crash, he went to the nearby break room to watch the television coverage of it. Lazar has a background in Navy Special Operations, and immediately suspected that terrorism was involved. Therefore, at around the time the second attack is taking place, he tries calling Special Operations people at the FAA headquarters in Washington, DC. However, no one answers his call. The reason for this is unknown. [9/11 Commission, 7/28/2003 ] Two unidentified military aircraft fly in the vicinity of the Pentagon at an altitude of over 20,000 feet, and are in the area during the minutes before the Pentagon is hit. [Federal Aviation Administration, 9/20/2001 ; 9/11 Commission, 7/28/2003 ] Between at least 9:31 a.m. and 9:40 a.m., the two aircraft communicate with the air traffic control tower at Washington’s Reagan National Airport, which is less than a mile from the Pentagon. [Federal Aviation Administration, 9/20/2001 ; St. Petersburg Times, 10/3/2001] Radar data will show that they fly “in trail” (in single file, with one aircraft directly behind the other) at 21,000 feet, and are overhead during the last few minutes that Flight 77 is airborne, before it hits the Pentagon at 9:37 a.m. (see 9:37 a.m. September 11, 2001). [9/11 Commission, 7/28/2003 ] Launched from Delaware Base - The identities of the two aircraft are unclear. They have the call signs “Bobcat 14” and “Bobcat 17.” [Federal Aviation Administration, 9/20/2001 ] A 9/11 Commission memorandum will state that “flight strips and other information indicate that Bobcat 14 and Bobcat 17 originated out of Dover Air Force Base in Delaware.… It is possible, but not confirmed, that they were Air Force corporate passenger jets.” Airport Managers Do Not Recall Planes - Two key officials will later be unable to specifically recall the aircraft when questioned by the 9/11 Commission. Bob Lazar, the acting operations manager at Reagan National Airport, will say he “did not remember any aircraft with the call sign ‘Bobcat’ that hung out over the National airspace” on this day. However, as well as two of the fighter jets that are inbound from Langley Air Force Base (see (9:25 a.m.-9:30 a.m.) September 11, 2001), he will recall two aircraft “coming from the north, but he did not think that they entered National’s airspace.” Donny Simons, the airport manager at Baltimore-Washington International Airport in Linthicum, Maryland, will stress “that he did not remember the Bobcats specifically,” but he speculates that controllers at his airport “were working the two ‘Bobcats’ and needed vectors from National controllers.” [9/11 Commission, 7/28/2003 ]
| Email Updates Receive weekly email updates summarizing what contributors have added to the History Commons database
Donate Developing and maintaining this site is very labor intensive. If you find it useful, please give us a hand and donate what you can. Donate Now
Volunteer If you would like to help us with this effort, please contact us. We need help with programming (Java, JDO, mysql, and xml), design, networking, and publicity. If you want to contribute information to this site, click the register link at the top of the page, and start contributing. Contact Us
|