NORAD Timeline Statement

Similar documents
NATIONAL TRANSPORTATION SAFETY BOARD WASHINGTON, DC. INTERVIEW TRANSCRIPT NYANG TSGT. CHARLES RAMERIEZ JANUARY 15, 1997 (14 pages)

AT-E-17 AIR TRAFFIC CONTROL TRAINING SERIES EQUIPMENT ENHANCED TERMINAL VOICE SYSTEM (ETVS) REQUEST AND ACKNOWLEDGE UNIT (RAU) OPERATIONAL PROCEDURES

Title- RADIO PROTOCOL FOR EMERGENCY INCIDENTS CLASSIFICATION POLICY STATEMENT

2 Flight Plans 1 Fill in the appropriate boxes 2 Find acceptable routes 3 Useful Newbie Comments

Introduction. Traffic Symbology. System Description SECTION 12 ADDITIONAL FEATURES

LETTER OF PROMULGATION

TCAS Functioning and Enhancements

Mission Critical Voice Communications Use Case Development

United States Air Force Europe Bird Strike Hazard Reduction

Advancing SOTA in Applying Network Science to C2

Operational Domain Systems Engineering

ACAS Xu UAS Detect and Avoid Solution

STANDARD OPERATING GUIDELINES FOR MAYDAY OPERATIONS

EVIDENCE Part I.

Policies, Procedures and Guidelines. Section: Operations Page: 1 of 10 Section No: 2.8 Date: November 1, 2014

EFFECTIVE DATE: 01/01/2002 REFERENCES: RELATED DIRECTIVES: RESCINDS:

NOISE ADVISORY COMMITTEE MEETING. October 22, :00 pm 7:30 pm Portland Jetport Main Conference Room

Radar and NTSB Time Normalization. Radar and NTSB Time Normalization for 9/11 Data Sources John S. Farmer December 15, 2009

Mode S Skills 101. OK, so you ve got four basic surveillance skills, you ve got the: ATCRBS Skills Mode S Skills TCAS Skills ADS-B skills

VATSIM CODE OF CONDUCT

Advances in Military Technology Vol. 5, No. 2, December Selection of Mode S Messages Using FPGA. P. Grecman * and M. Andrle

Before the Federal Communications Commission Washington, DC ) ) ) ) COMMENTS OF CTIA THE WIRELESS ASSOCIATION

STRATUS ES/ESG PILOT S GUIDE

MOBILIZE REALTIME INFORMATION SEAMLESSLY ACROSS YOUR OPERATION CONNECT PERSONNEL MORE SAFELY AND EFFICIENTLY WITH OUR MISSION CRITICAL SOLUTIONS

KMA 24 and KMA 24H Bendix/King Audio Control Systems

OVERVIEW. What is Jamming? What is COMPASS CALL? War Stories Operation ENDURING FREEDOM Operation IRAQI FREEDOM 2-Minute Jamming Movie.

A Line in the Pentagon Grass exchange between Ward Schmidt and John Judge October 6-9, 2003

VAE_FSA_13 Page 1 of 5 Jody Sears, Male, Female

KING COUNTY FIRE MODEL PROCEDURE Section 15 Abandon / Withdraw

Changes made for Version 2. 0 (not released)

Flarm Guidance RunwayHD 3.3, Flarm v6.0

KING COUNTY FIRE RESOURCE PLAN Section 9 King County Radio Interoperability

NAVAL AVIATION Carrier Borne AEW&C

400/500 Series GTS 8XX Interface. Pilot s Guide Addendum

10 Secondary Surveillance Radar

Pilot s Operating Handbook Supplement AS-21

Data Link and Technology Integration Benefits to NAS Performance

EVALUATING AN ADAPTIVE SIGNAL CONTROL SYSTEM IN GRESHAM. James M. Peters, P.E., P.T.O.E., Jay McCoy, P.E., Robert Bertini, Ph.D., P.E.

BIGGIN HILL MEMORIAL MUSEUM. Biggin Hill; inspiring generations, Remembering the Few and honouring the Many

Understanding ADS-B traffic

Rulemaking Hearing Rules of the Tennessee Department of Health Bureau of Health Licensure and Regulation Division of Emergency Medical Services

Monday Night Net. Standard Operating Procedures LOS ANGELES COUNTY DISASTER COMMUNICATIONS SERVICE

BASH TEAM NEW DEVELOPMENTS

The Nimitz story in the former OMF forum

Portable Radio Fundamentals How to a use a portable, hand-held radio effectively in an emergency

Consultation Paper on Using a Portion of the Band GHz for Tactical Common Data Link (TCDL) Systems

IEEE C802.16d-04/88r2. IEEE Broadband Wireless Access Working Group <

AGENCY: Defense Security Cooperation Agency, Department of Defense. FOR FURTHER INFORMATION CONTACT: Kathy Valadez, (703) or Pamela

Chapter 4. Meaconing, Intrusion, Jamming, and Interference Reporting

Before the FEDERAL COMMUNICATIONS COMMISSION Washington, DC ) ) ) ) ) COMMENTS OF REDLINE COMMUNICATIONS INC.

Department of Defense Instruction (DoDI) requires the intelligence community. Threat Support Improvement. for DoD Acquisition Programs

The Aces High Radio. by Hammer

The Application of Wargaming to Education in Naval Design & Survivability

SATELLITE RADIO/TELEPHONE

Universal ADS-B Receiver. Equipment Supplement

Red Baron Mission Builder

EE Chapter 14 Communication and Navigation Systems

GTS 8XX Series. Pilot s Guide Traffic Advisory System

800 System Procedures

Three-Question Matrix and Reference Checks. RFP Number: R P1 RFP Name: Public Safety Radio APCO Project MHz Communication System

STAUNING Trade-In Internet Sales Process with /Voic Templates to Non-Responsive Prospects 2018 Edition

Wyandotte County Radio Amateur Civil Emergency Service (RACES)

9-11 Commission to Address Emergency Preparedness

RAID OVER MOSCOW INSTRUCTIONS

Airport / Community Roundtable Meeting No. 266 Overview Wednesday, December 2, 2009

Emergency Alert System

MEOSAR Performance Overview. SAR Controllers Training March 2016 Mickey Fitzmaurice NOAA Senior Systems Engineer

AT01 AIRPLANE FLIGHT MANUAL

Wings of war campaign. All players start on the same side, and are in the same scout squadron on the Western front in Late August 1917.

APCO Broadband Working Group and Other Comments

PRODUCTS. Radios. Accessories As shown, and more GPS. Other PUSH-TO-TALK OVER CELLULAR. Heavy Duty, Bluetooth and Smart Digital Headsets.

INTERFERENCE FROM PASSENGER-CARRIED

Proposal # xxxxxxxxxxxx. Intercept Jammer. Date:

Autonomous Tactical Communications

DOWNWIND LEG NOISE MONITORING SUMMARY REPORT

Cooperation Agreements for SAR Service and COSPAS-SARSAT

Portable All-Band Radar and Laser Detector RD950. Owner s Manual

David Siegel Masters Student University of Cincinnati. IAB 17, May 5 7, 2009 Ford & UM

Concordia University Department of Computer Science and Software Engineering. SOEN Software Process Fall Section H

RESPONSE TAPE 2 SIDE A, 10:22-11:10 a.m.

CHAPTER 23 MASS COMMUNICATION SPECIALIST (MC) NAVPERS B CH-55

i 2 OE/AAA Spectrum Engineering Presented to: i 2 OE/AAA Ext. Users Conf Federal Aviation Administration Southern Pines, NC By: Date:

K40 Consult. Don t like to read manuals? Call our experienced K40 Consultants. We ll explain the whole thing

Organizational Culture in Aviation Fire Suppression

A Step by Step guide to making and maintaining a Universal Credit claim online

Lincoln County Fire and Rescue Association Standard Operating Guideline (SOG)

A legacy of regional cooperation, a commitment to a vibrant future. National Capital Region Communications Interoperability Group Procedures

4.9 GHz Public Safety Broadband Spectrum. Overview of Technical Rules And Licensing Instructions. Motorola, Inc. January 20, 2005

Thunderbolt+Apache Leader Designer's Notes

Spectrum & Power Measurements Using the E6474A Wireless Network Optimization Platform Application Note By Richard Komar

IEEE C802.16h-05/001. IEEE Broadband Wireless Access Working Group <

Game Turn 11 Soviet Reinforcements: 235 Rifle Div can enter at 3326 or 3426.

Phrases for presentations in English

December 5, Activities Following the I-35W Bridge Collapse

Trajectory Assessment Support for Air Traffic Control

DS-160 CHEAT SHEET. This DS0160 Cheat Sheet will tell you what to write for EVERY SINGLE QUESTION on the DS-160 form.

Ima Student 315 S. Plymouth Court, Apt. 222 Chicago, IL (312)

Frequently Asked Questions

Wings of Glory campaign

REGIONAL MCI COMMUNICATIONS AND EXERCISE (DRILL) PLAN

Transcription:

FEB. 23. 2 0 0 4 1 1:1 5 A M 9-11 C O M M I S S I O N. NO. 1914 P. 2 NORAD Timeline Statement Comments on NEADS Briefing. "America Under Attack: 11 Sep 01" Slide 14: 2. 1305Z FAA reports hijack of UA175 Comment: Notification from FAA to NEADS occurred at I303Z. 4 Slide 18:2. 1316Z FAA reports possible hijack of UA93. ^ Comment: FAA hijack notification for UA93 did not occur until 1406:28Z when conversation begins between Cleveland Center and NEADS that UA93 had a possible bomb on board." Slide 20: 1. 1324Z FAA reports possible hijack of AA77 Comment: FAA hijack notification on AA77 did not occur until 13342 when Washington Cenier Ops Manager told NEADS that AA77 was "lost."3 Slide 20: 2. (xjl2242^langley scrambled on AA77 ComTnentTNEADS Commander scrambled the fighters at Langley because he felt there was a ~" threat tojwashington DC. but not specifically because of AA77 which was not mentioned until 'l334z7r =^-, Slide 20: 3. 1325Z AA77 Ueaded toward Washington DC Comment: Even though AA77 was headed toward Washington DC at this^time, NEADS does not know this is occurring. -7^ Slide 20: 4. 1327Z Boston FAA reports/sth-'aircraft missing (D89?) fifu- H - Comment: There is some contusion as to whether there are three or five unaccounted for aircraft at this time. On the NEADSTDl voice recorder the following statement was made: "there is 3 jin^cc^mtejjpj^airwift, mek^aircraftjmic^ojinte^otjbpjto^." It is possible that this statement could have been combined with the knowledge that AA11 and UA175 had been hijacked, accounting for the entry on the slide as "5Ul aircraft missing.'* Slide 26: 1-. 1347Z Delta 89 landed in Cleveland Comment: At 1345Z, FAA notified NEADS that D89 might not be a hijack and had acknowledged air traffic control instructions to land (not landed) in Cleveland0 First notification of D89 landing at Cleveland was passed from Cleveland Center to NEADS at 1359Z.7 Slide 28: 1-. 1407Z FAA reports bomb on board UA93 Comment: Conversation discussing a possible bomb on board UA93 begins at 1406:28Z.K 1 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01 at 0903:20L, background voice on IDl, p.10. - NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 1006:28L to 1010:53L, from Cleveland Center and IDl, p.28-30. 3 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01 at 0934:02L, Washington Center Ops Manager to IDl, p. 19. 4 "NORAD's Response to request for Information From the Meeting With 9-11 Commission Staff, 24 October, 2003," Statement from Colonel Marr, NEADS Commander, p.2-3. 5 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01 at 0926:57L, byidl,p.l6. * NEADS voice data extracted from voice recorder, DRM 1, Dat 2, Channel 8, from 9-11-01, 0945:22L, from FAA to IDl. 7 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 0958:29L, from Cleveland Center and IDl, p.26. 8 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 1006:28L to 1010-.53L, from Cleveland Center and IDl, p.28-30. NCTOOfiTBS*

. 2004 11:16AM 9-11 COMMISSION NO, 1914 Slide 30: 1415Z UA93 reported crash Comment: Conversation between Washington Center and NEADS begins at 1414:09Z.' Comments on CONR brief: "Operation NOBLE EAGLE, Air War Over America" Slide 17; 2. 0905LFAA reports hijack of UA175 Comment: Notification from FAA to NEADS occurred at 0903L. Slide 19: 2. 0916L FAA reports possible hijack of UA93 Comment: FAA hijack notification for UA93 did not occur until 1006:28L when conversation begins between Cleveland Center and NEADS that UA93 had a possible bomb on board. Slide 20: 1. 0924L FAA reports possible hijack of AA77 Comment: FAA hijack notification on AA77 did not occur until 0934L when Washington Center Ops Manager told NEADS that AA77 was "lost."11 Slide 20: 2. 0924L Langley scrambled on AA77 Comment: NEADS Commander scrambled the fighters at Langley because he felt there was a threat to Washington DC, but not specifically because of AA 77 which was not mentioned until 0934T7 7V Slide 20: 3. 0925L AA77 headed toward Washington DC Comment: Even though AA77 was headed toward Washington DC at this time,neads does not know this is occurring. Slide 20: 4. 0927L Boston FAA reports 5th aircraft missing (D89?) Comment: There is some confusion at this point as to whether there are three or five unaccounted for aircraft at this time. On the NEADS IDl voice recorder the following statement was made: "there is 3 unaccounted for aircraft, more aircraft unaccounted for Boston." It is possible that this statement could have been combined with the knowledge that AAl 1 and UA175 had been hijacked, accounting for the entry on the slide as "5m aircraft missing.'" Slide 22: 4-. 0943L AA77 impacts Pentagon Comment: Impact later confirmed to occur at 0937L. Slide 23: 0947L Delta 89 landed in Cleveland Comment: At 1345Z, FAA notified NEADS that D89 might not be a hijack and had acknowledged air traffic control instructions to land,(not landed) in Cleveland.1" First notification of D89 landing at Cleveland was passed from Cleveland Center to NEADS at 0959L,15 10 9 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat2, Channel4 from 9-11-01, 1014:09L to 1015:23L, from Washington Center and IDl, p.30-31, 10 NEADS voice data extracted from transcript of voice recorder, DRM l,dat2, Channel 4 from 9-11-01 at0903:20l, background voice on IDl, p. 10, 1' NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11 -01 at 0934:02L, Washington Center Ops Manager to IDl, p. 19. 12 ''NORAD's Response to request for Information From the Meeting With 9-11 Commission Staff, 24 October, 2003," Statement from Colonel Marr, NEADS Commander, p.2-3. 13 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01 at 1326:571, byidl,p.l6. NEADS voice data extracted from voice recorder, DRM 1, Dat 2, Channel 8, from 9-11-01, 0945;22L, from FAA to ID2. NCT0067534

23, 2004 11M6AM 9-11 COMMISSION NO, 1914 P, 4 Slide 24: 1-. 1007L FAA reports bomb on board UA93 Comment: Conversation discussing a possible bomb on board UA93 begins at 1006:281.'* Slide 25: 1015Z XJA93 reported crashed Comment: Conversation between Washington Center and NEADS begins at 1014:09L.17 15 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 0958:29L, from Cleveland Center and ID1, p.26. 16 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 1006:28L to 1010:53L, from Cleveland Center and ID1, p.28-30. 17 NEADS voice data extracted from transcript of voice recorder, DRM l,dat2, Channel 4 from 9-11-01,1014;09Lto 1015:23L, from Washington Center and ID1, p.30-31. NCT0067535

F 23, 2004 11M6AM 9-11 COMMISSION NO. 1914 P. 5 Sources for Times for AA11: NORAD 9-11 Timeline 0759 - AAl 1 takeoff time extrapolated from RADES radar data' 0820 - AAl 1 turns off transponder from RADES radar data 0827 - AA11 Turns south from RADES radar data 0840 - FAA reports possible bijack from NORAD/PA News Release on 18 Sep 01:, from "FAA Responds'0 (Note: Former FAA administrator, Jane Garvey, testified that the notification took place at 8:34. According to NEADS Commander, Colonel Robert Marr, "This is the time [0840] captured in the primary operations log maintained by he Mission Crew Commander Tech (MCC/T). SSgt Powell answered the call from Mr. Joe Cooper of Boston Center at 0837:24"* and put a supervisor, Maj Deskins, on the line to get the information needed TO take action. By the time this information was gathered the time was between 0839 and 0840, leading to the logged time of 0840L."5) from NEADS logs 0846 - Otis scramble order from NEADS logs6 0846 - AAl 1 impacts WTC 1 from RADES radar data 0852 - Otis airborne from NEADS logs1 ' RADES radar data reduction provided by 84* Radar Evaluation Squadron (RADES), Hill AFB, UT, 25 Sep 01. 2 "NORAD Response Times, September. 11, 2001," at w\v\v,norad.mil'index.cfm?fuscachon-home,news rel_q9jft_()i 3 "FAA Responds, September, 11, 2001," at w\».w2.faa._iun- sentl lnortrait.s/chronoloiiv.cfrn 4 NEADS voice data extracted from transcript of voice recorder DRM 2, Dat 2, Channel 14 from 9-11-01 at 0837:24L, p.l. 5 "NORAD's Response to Request for Information From the Meeting With 9-11 Commission Staff, 24 October, 2003," Statement from Colonel Marr, NEADS Commander, p.2. 6 NEADS voice data extracted from transcript of voice recorder DRM 1, Dat 2, Channel 2 from 9-11-01 at 0846:22L, background voice on MCC-OP, p.52. 7 NEADS voice data extracted from transcript of voice recorder DRM 1, Dat 2, Channel 15 from 9-11-01 at 0857:55L from AST, p.32. NCT0067536

. 2004 11:16AM 9-11 COMMISSION NO. 1914 P. 6 Sources for Times for UA175: 0814 - UA175 takeoff from Boston extrapolated from RADES radar data and from "FAA Responds" 0843 - FAA reports possible hijack from NORAD/PA News Release on 18 Sep 01 and from "FAA Responds" (Note: According to NEADS Commander, Colonel Marr, "The time that the FAA notified NEADS of the hijacking of UAL175 is listed as 0843L. None of the NEADS logs, transcripts, or audio recordings support this time. My recollection of the events was that the first indication we had of a second hijacking was the media transmission of the second tower being hit. The first transcript indication that the FAA had contacted NEADS was background voices at 0903L providing the call sign ofual175....0843l was labeled as the reporting time, but this time was attributed to an early effort by Operations people to build a timeline using a faulty computer time indication (numerous entries that used this method were later proven to be inaccurate by the transcript that used the Naval Observatory Time Hack on the tape). It is my speculation that this early, incorrect time was used to build the early NORAD timeline."8) 0846 - UA J75 changes transponder code from 1470 to 3020, then to 3321 from RADES radar data 0846 - Otis scramble order from NEADS logs 0852 - UA 175 alters course toward WTC frorh RADES radar data 0852 - Otis airborne from NEADS logs 0902 - UA175 impacts WTC2 from RADES radar data and frofn l'faa Responds" 0903 - FAA reports hijack of UA175 from NEADS logs'* 0905-0907: Discussion about UAI75 between NEADS ID and FAA (Boston Military) from NEADS logs10 0909 - Langley to Battle Stations from NEADS logs" 0909-0915: Discussion about UA175 between NEADS ID and FAA (Boston and New York Military) continues from NEADS logs': 0915 - FAA confirms thai UA 175 has crashed into WTC from NEADS logs1-' 8 "NORAD's Response to request for Information From the Meeting With 9-11 Commission Staff, 24 October, 2003," Statement from Colonel Marr, NEADS Commander, p.2, 9 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01 at 0903:20L, background voice on ID I. p. 10. 10 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01,0905:23L to 0907:15L, between Boston Military and ID1, p.10-11. " NEADS voice data extracted from transcript of voice recorder, DRM 1, Dai 2, Channel 2 from 9-11-01, 0908:58L, by MCC, p.57, lz NEADS voice data extracted from transcript of voice recorder, DRM 1. Dat 2, Channel 4 from 9-11-01, 0910:04L to 0915:02L, between Boston and New York Military and ID1, p.11-12. 13 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01 at 0915:28L, New York Military to ID 1, p. 13. NCT0067537

23. 2004 11:16AM 9-11 COMMISSION NO. 1914 P. 7 Sources for Times for AA77: 0820 - AA77 takeoff from IAD extrapolated from RADES radar data 0851 - Transponder and radar returns lost from RADES radar data 0905-0907: Discussion about UA175 between NEADS ID and FAA (Boston Military) from NEADS logs'4 0909 - Langley to Battle Stations from NEADS logs15 0909-0915: Discussion about UA175 between NEADS ID and FAA (Boston and New York Military) continues from NEADS logs'" 0915 - FAA confirms that UA175 has crashed into WTC from NEADS log17 0917-0918: Discussion between NEADS MCC and FAA (Boston Military) about fighter availability from NEADS logs'* 0922-0930: Discussion begins / continues about AA11 still being airborne between NEADS ID and FAA (New York and Washington Center) from NEADS logs" 0924 - FAA reports possible hi-jack from NO RAD/PA News Release on 18 Sep 01, from "FAA Responds" (Note: According to the NEADS Commander, "The time that the FAA notified NEADS of the hijacking is listed at 0924L. However, this was not a clear indication that AA77 was hijacked. The first specific information regarding AA77 did not come until 0934L, just three minutes prior to impact at 0937L. At 0924L it was reported to the Operations floor from Boston Center the AA11 had not impacted the WTC, but was still airborne en route to Washington, DC (which later proved to be inaccurate). Simultaneously, there were indications of UAL93 as a possible hijack in Ohio (Col Man is now unable to confirm this specifically about UA93 happening at this time) and a reported "third" hijacking. Numerous other uncorroborated reports were coming in that increased the likelihood that an attack would be possible against Washington, so the 0924L report time is more accurately a general indication of a possible targeting of Washington rather than a specific notification of AA77 hijacking which actually was reported to NEADS at 0934L.20) 0924 - Fargo alert fighters at Langley AFB scramble order from NEADS logs:i 0930 - Fargo alen fighters at Langley AFB Airborne from RADES radar data 0934 - FAA reports AA77 "lost" from NEADS logs" 0935-0940: Discussion between NEAD ID and FAA (Indy Center) about location of AA77 from NEADS logsj? 0936 - NEADS MCC directs that fighters airborne from Langley go straight to Washington based on aircraft reported 6 miles west of White House from NEADS logs2"1 0937 - AA77 crashes into Pentagon from RADES radar data 14 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 0905:23L to 0907:15L, between Boston Military and ID I, p, 10-11. 15 NEADS voice data extracted from transcript of voice recorder, DRM 1. Dat 2, Channel 2 from 9-11-01, 0908:58L, by MCC, p.57. 16 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dai 2, Channel 4 from 9-11-01, 0910:04L to 0915:02L, between Boston and New York Military and ID 1, p. 11-12. 17 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dai 2, Channel 4 from 9-11-01 at 0915:28L, New York Military to ID1, p.13. 16 NEADS voice data extracted from iranscript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 0917:01L to 0918:37L, between Boston Military and MCC, p. 13-14. 19 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 0922:38L to 0930:08L, between New York and Washington Center and IDl, p. 14-17. 20 "NORAD's Response to request for Information From the Meeting With 9-11 Commission Staff, 24 October, 2003," Statement from Colonel Marr, NEADS Commander, p.2-3. 21 NEADS voice data extracted from transcript of voice recorder. DRM 1. Dat 2, Channel 15 from 9-11-01, 0924:33L byast,p.35. 22 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01 at 0934:02L, Washington Center Ops Manager to IDl, p. 19. 23 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 0935:40L to 0940:23L, between Indy Center and IDl, p.i9-21. 24 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 2 from 9-11-01, 0936:37L, from MCC, p.67. NCT0067538

23. 2004 1M7AM 9-11 COMMISSION NO. 1914 Sources for Times for UAg3: 0842 - UA93 takeoff from Newark extrapolated from RADES radar data 0909 - Langley to Battle Stations from NEADS logs"5 0916-0922: NEADS Commander stated, "The time that the FAA notified HEADS of the hijacking of UAL93 is described as being unknown, part of open line conversations with the FAA that were established while discussing AA77. Some briefings describe the time that the UAL93 hijacking was announced as being 0916L. Any of these times are educated guesses based upon the wide range of information, most of it inaccurate, which was coming into NEADS at the time. The Mission Crew Commander log describes hijacking information at 0916L, but further research indicates that this information is most likely related to the previous hijackings that impacted the World Trade Center. It is most likely that the first report of UAL93 came into the Battle cab via a conference call (DEN line which was not recorded) that established with the FAA that morning. As a result, it is most likely that the UAL93 hijacking was originally discussed over the FAA conference line as a possibility some time between 0916L and 0922L (allowing for an estimated two minutes processing time from the direction to scramble Langley fighters 10 the time the scramble order was actually transmitted at 0924L.)"26 0922-0930: Discussion begins about AA11 still being airborne between NEADS ID and FAA (New York and Washington Center) continues from NEADS logs" 0924 - Fargo alert fighters at Langley AFB scramble order from NEADS log28 0930 - Fargo alert fighters from Langley AFB airborne from RADES radar data 0935-0940: Discussion between NEAD ID and FAA (Indy Center) about location of AA77 from NEADS logs29 0936 - NEADS MCC directs that fighters airborne from Langley go straight to Washington based on aircraft reported 6 miles west of White House from NEADS logs1" 0936 - UA93 alters course to the southeast from RADES radar data 0940 - UA93 turns transponder off from RADES radar data 0941-0958: Discussion between NEADS ID and FAA (Indy and Cleveland Center) about Delta 89 being hijacked near Cleveland from NEADS logs31 0945 - FAA notifies NEADS that D89 has acknowledged air traffic control instruction to land in Cleveland and may not be hijacked from NEADS logs" 0946 - Radar contact lost from RADES radar data 0959 - FAA (Cleveland Center) confirms that Delta 89 is not hijacked from NEADS logs'11 1002 - Radar contact regained from RADES radar data 1003 - UA93 crashes in PA from RADES radar data 1006 1010: First discussion about UA93 having a bomb on board from NEADS logs3" 1014 - FAA notifies NEADS that UA93 has crashed from NEADS logs" 25 NEADS voice data extracted from transcript of voice recorder, DRJVl 1, Dat 2, Channel 2 from 9-11-01, 0908:58L, bv MCC, p.57. NORAD's Response 10 request for Information From the Meeting With 9-11 Commission Staff, 24 October, 2003," Statement from Colonel Mau, NEADS Commander, p.3. 27 NEADS voice data extracted from transcript of voice recorder, DRM l,dat2, Channel 4 from 9-11-01, 0922:38L to 0930:08L, between New York and Washington Center and ID 1, p. 14-17. 28 NEADS voice data extracted from transcript of voice recorder, DRM 2, Dat 2, Channel 15 from 9-11-01, 0924:33L bvast,p.35. NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 0935:40L to 0940:23L, between Indy Center and ID1, p.l'9-21. 30 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 69 from 9^11-01, 0936:37L, from MCC, p.67. 31 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 094l:08L to 0958:01L, between Indy and Cleveland Center and ID1, p.21-25. 32 NEADS voice data extracted from voice recorder, DRM 1, Dat 2, Channel 8, from 9-11-01, 0945:22L. from FAA to ID2. 33 NEADS voice data extracted from transcript of voice recorder. DRM 1, Dat 2, Channel 4 from 9-11-01, 0958:29L, from Cleveland Center and ID1, p.26. 3" NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 1006:28L to 1010:53L, from Cleveland Center and ID1, p.28-30. 35 NEADS voice data extracted from transcript of voice recorder, DRM 1, Dat 2, Channel 4 from 9-11-01, 1014:09L to 1015:231, from Washington Center and ID1, p.30-31. NCT0067539

i. 23. 2004 11:15AM COMMISSION NO. 1914 Thomas H-Kcan Lee H. Hamflcon VICE CHAIR FAX COVER SHEET Richard Ben-Veniste Mar debnd Fred P. Relding Jamie S. Gorelidc Sladc Goitoo John Lehman Fax#: From: Date: Number of pages (including cover sheet): Timothy J. Roemci James IL Thompson philipd. Zclitow EXECUTIVE DIHECTOR TEL(202)331-