WASHINGTON DULLES ATCT STANDARD OPERATING PROCEDURES February 18, 2017
RECORD OF CHANGES BULLETIN NUMBER SUBJECT AUTHORIZED BY DATE ENTERED DATE REMOVED 7110.110 Initial RR 08/04/14 02/26/16 7110.111 Added MCRAY and new PDCs RR 02/26/16 12/12/16 7110.120 General update RR 12/23/16 1/18/17 7110.121 -Added ATIS frequency -Added gate diagram appendix -Fixed typo -Minor formatting changes 7110.122 -Added altitude restrictions to close airports -Minor formatting changes 7110.123 -Corrected typo in runway configs -Added scratchpad entries RR 1/18/17 2/14/17 RR 2/14/17 2/18/17 RR 2/18/17 -- FOR FLIGHT SIMULATION USE ONLY 2
VIRTUAL AIR TRAFFIC SIMULATION NETWORK VATUSA DIVISION WASHINGTON ARTCC SUBJ: IAD 7110.65V This order provides direction and guidance for the day-to-day operations of the Washington-Dulles Control Tower and prescribes air traffic control procedures and phraseology. Controllers are required to be familiar with the provisions of these procedures. This document is only to be used in a simulated environment. This document shall not be referenced or utilized in live operations in the National Airspace System (NAS). The Washington ARTCC, VATUSA, and VATSIM do not take any responsibility for uses of this order outside of the simulation environment. /Rick Rump/ Air Traffic Manager Washington ARTCC FOR FLIGHT SIMULATION USE ONLY 3
Contents CHAPTER 1. POSITIONS... 6 1-1. POSITIONS.... 6 1-2. OPENING SECONDARY POSITIONS... 6 CHAPTER 2. RUNWAY CONFIGURATIONS.... 7 2-1. GENERAL... 7 2-2. CHANGE IN RUNWAY CONFIGURATION... 7 2-3. NORTH OPS... 7 2-4. NORTH WITH 30... 7 2-5. SOUTH OPS... 7 2-6. SOUTH WITH 30... 8 2-7. SOUTH WITH 12... 8 CHAPTER 3. CLEARANCE DELIVERY.... 9 3-1. DUTIES.... 9 3-2. IFR DEPARTURE INSTRUCTIONS.... 9 3-3. VFR DEPARTURE INSTRUCTIONS... 9 3-4. DEPARTURE GATES... 10 3-5. DEPARTURE FREQUENCY ASSIGNMENT.... 10 3-6. DEPARTURE ALTITUDE RESTRICTIONS... 10 CHAPTER 4. GROUND CONTROL... 11 4-1. GROUND CONTROL 1.... 11 4-2. GROUND CONTROL 2.... 11 4-3. GROUND CONTROL 3.... 11 4-4. RUNWAY ASSIGNMENTS.... 12 4-5. TAXI ROUTES.... 12 4-5-2. ARRIVALS.... 12 CHAPTER 5. LOCAL CONTROL... 13 5-1. DUTIES.... 13 5-1-1. LOCAL CONTROL 1 (LC1).... 13 5-1-2. LOCAL CONTROL 2 (LC2).... 13 5-1-3. LOCAL CONTROL 3 (LC3).... 13 5-2. CHANGES IN RUNWAY OPERATIONS CHECKLIST.... 14 FOR FLIGHT SIMULATION USE ONLY 4
5-3. RNAV DEPARTURES.... 14 5-4. DEPARTURE HEADINGS.... 15 5-5. MISSED APPROACHES/GO AROUNDS... 15 CHAPTER 6. MID-FIELD RAMP CONTROL... 16 6-1. DUTIES.... 16 6-2. RAMP JURISDICTION.... 16 6-3. PROCEDURES.... 16 APPENDIX 1. LOCAL CONTROL AIRSPACE... 17 APPENDIX 2. AIRFIELD LAYOUT... 19 APPENDIX 3: PARKING GATES... 22 FOR FLIGHT SIMULATION USE ONLY 5
1-1. POSITIONS. CHAPTER 1. POSITIONS Identifier Position Frequency VOX Channel IAD_DEL Clearance Delivery 135.700 IAD_1D IAD_R_GND Ramp/Ground Metering 129.550 IAD_1R IAD_E_GND Ground Control East (GCE) 121.900 IAD_1G IAD_W_GND Ground Control West (GCW) 121.625 IAD_2G IAD_N_GND Ground Control North (GCN) 123.775 IAD_3G IAD_E_TWR Local Control East (LCE) 120.100 IAD_1T IAD_W_TWR Local Control West (LCW) 120.250 IAD_3T IAD_N_TWR Local Control North (LCN) 134.425 IAD_2T KIAD_ATIS ATIS 134.850 IAD_ATIS Unless stated otherwise, Ground Control East (GCE) and Local Control East (LCE) are the primary positions. 1-2. OPENING SECONDARY POSITIONS. Secondary positions (those not denoted as primary) may only be open once LCE, GCW and CD are all open; unless otherwise authorized by the ATM, DATM or CIC. FOR FLIGHT SIMULATION USE ONLY 6
2-1. GENERAL CHAPTER 2. RUNWAY CONFIGURATIONS. a. The clam wind operation is south with 30, otherwise refer to the configs below and select one most suitable for wind and traffic conditions. b. Controllers must be cognizant of 30 departures/12 arrivals when landing north. c. Runway 1R/19L should only be used for arrivals. d. Runway 12 should only be used for arrivals. e. Runway 30 should be used for departures only unless a sustained wind of greater than 25 kts aligns with runway 30 more than any other runway. 2-2. CHANGE IN RUNWAY CONFIGURATION. The CIC must determine the need for making any runway change. A routine runway change occurs when traffic and/or weather conditions are such that the change can be made with little or no degradation in service. In this instance, departures are allowed to depart from the runway originally assigned. Use the following procedures to complete a routine runway change: a. Provide PCT with the last departure s identification, its estimated time of departure, and the departure runway. b. Once the last aircraft departures, ensure that no other aircraft departs IAD without a release from PCT. c. Ensure that departures off of the new runway have received the appropriate DP and departure control frequency, as needed. d. PCT shall inform the CIC when the sector reconfiguration has been completed. e. Ensure the ATIS has been updated and reflects the proper status. 2-3. NORTH OPS a. Arrival runways are 1L, 1C and 1R. departure runways are 1C and 1R b. North and East departures should get runway 1R, South and West departures should get runway 1C c. This config should only be used when the wind is out of the north and greater than 15kts. If the wind is less than 15kts, departing runway 30 is preferred. 2-4. NORTH WITH 30 a. Arrival runways are 1L, 1R and 1C. Departing runway 30. b. All departures get runway 30 regardless of departure procedure or gate, unless coordinated otherwise c. Preferred if wind is out of the North and less than 15kts d. Runway 30 departures may not be cleared for takeoff if a runway 1C arrival is within 2.27nm of the threshold e. A runway 30 departure may not be cleared for takeoff if a runway 1L arrival is within 3.56nm of the threshold 2-5. SOUTH OPS a. Arrival runways 19L, 19C and 19R. Depart runways 19C and 19R b. South and West departures should get runway 19C, North and East departures should get runway 19R. c. This config should only be used when the wind is out of the south and greater than 15 kts. If the wind is less than 15kts, departing runway 30 is preferred. FOR FLIGHT SIMULATION USE ONLY 7
2-6. SOUTH WITH 30 a. Arrival runways are 19L, 19R and 19C. Departing runway 30. b. All departures get runway 30 regardless of departure procedure or gate, unless coordinated otherwise c. Preferred wind calm configuration. Preferred if wind is out of the North and less than 15kts d. A runway 30 departure may not be cleared for takeoff if a runway 19R arrival is within 1.3nm of the threshold 2-7. SOUTH WITH 12 a. Should only be used if there is a sustained wind greater than 20 kts that most closely aligns with runway 12 b. Arrival runways are 12, departing runways are 19C and 19R c. South and West departures should get runway 19C, North and East departures runway 19R. 2-8. LANDING RUNWAY 30 a. Due to Potomac TRACON airspace, all landing on runway 30 should be accomplished via circling procedures b. Based on weather or traffic conditions, utilize an instrument approach to runway 1R circle to runway 30. Local control will provide circling instructions. The ILS runway 1R circle to runway 30 is the preferred approach. FOR FLIGHT SIMULATION USE ONLY 8
3-1. DUTIES. Clearance Delivery (CD) must: CHAPTER 3. CLEARANCE DELIVERY. a. Formulate and issue IFR and Class B airspace clearances to aircraft departing IAD. b. Review proposed flight plan information received and verify for accuracy and amend routings and altitudes as necessary, in accordance with LOAs. 3-2. IFR DEPARTURE INSTRUCTIONS. a. Departure procedures: 1. RNAV aircraft on the correct RNAV SID 2. Non-RNAV aircraft on the Capital SID (CAPTL) 3. Climb via SID should be used for all SIDs. 4. In the event the pilot files NO SID issue the following: A clearance to Fly runway heading, radar vectors to their first fix, maintain 3,000, altitude to expect ten (10) minutes after departure. b. Do not amend flight plans unless the pilot is able to accept the changes. c. Annotate in the scratchpad per the Potomac TRACON (PCT) SOP appendix. d. Because the JCOBY SID transits the Washington Flight Restriction Zone (FRZ), United States carriers are able to fly it. General Aviation (N) numbers, Foreign Air Carriers not routed via the JCOBY Departure SWANN or AGARD transitions, Air Taxis (EJA, LXJ, FIV, etc.), and other aircraft routed over SWANN, PALEO, and COLIN must be rerouted around the FRZ and must get a different route. If you have any questions about finding a new route, as TMU or the CIC. a Put simpler, any N-callsigns and Air Taxis (EJA, LXJ, FIV, etc.) are not able to fly the JCOBY Departure SWANN/AGARD/PALEO transitions, and any of those, in addition to foreign air carriers, are not able to fly the JCOBY departure, COLIN Transition. Those aircraft all need to be rerouted to different departure gates. e. It is very important that all aircraft routed to the northeast with a destination north of New York or with an overseas destination be routed via SWANN..BROSS.J42.RBV before proceeding along their flight plan or amended route. 3-3. VFR DEPARTURE INSTRUCTIONS. a. Issue a clearance to depart the Washington Class Bravo airspace. b. Assign runway heading. c. Issue an altitude. a. Jets: AOB 3,000. b. Props: AOB 2,500. c. Helicopters: AOB 1,300. d. Issue the appropriate departure control frequency for direction of flight. e. Assign local VFR beacon code. FOR FLIGHT SIMULATION USE ONLY 9
3-4. DEPARTURE GATES Unless otherwise coordinated with departure, all aircraft shall use one of the following departure gates. DIRECTION GATE North JERES, BUFFR, EMI/WOOLY, MCRAY West East South RNLDI, BUNZZ, LDN/OTTTO, AML.J149, RAMAY SWANN, PALEO, JCOBY HAFNR, GVE, CLTCH, CSN, JDUBB, FLUKY, MOL, SCRAM, BRV, HANEY 3-5. DEPARTURE FREQUENCY ASSIGNMENT. South or West TILLY (126.650) North or East ASPER (125.050) 3-6. DEPARTURE ALTITUDE RESTRICTIONS a. Aircraft departing IAD to the following airports must meet certain route and altitude requirements; a. DCA, IAD Capital# (CAPTL#) departure, radar vectors direct, maintain 4000 b. RIC Preferred route, 10000 (Prop), 14000 (Jet) c. PHL Preferred route, 7000 (Prop), 11000 (Jet) d. JFK Preferred route, 17000 e. EWR, TEB or LGA Preferred route, FL210 f. ORF 15,000 (route via HAFNR) FOR FLIGHT SIMULATION USE ONLY 10
4-1. GROUND CONTROL 1. CHAPTER 4. GROUND CONTROL Ground Control 1 is responsible for all aircraft/vehicles on the east-side taxiways and runway 19L/1R run-up blocks. 4-2. GROUND CONTROL 2. a. GC2 is responsible for aircraft/vehicles on the following areas of jurisdiction: 1. Departing Runway 30: TWY Y8, all taxiways north of Y8. All of TWY Z and Z7. TWY Y11 and TWY Q east of TWY Z. 19C/30 Run-Up Blocks. 2. Not Departing RWY 30: Taxiway Y11 and all Taxiways north of Taxiway Y11 Rwy 19C and 30 Run- Up Blocks. NOTE. GC2 and GC3 s areas of jurisdiction change depending on whether IAD is departing RWY 30 or not, regardless of the landing direction (see Figure 12-1.) Areas of jurisdiction may change due to construction, b. ILS CRITICAL AREA. LC2 has primary responsibility for crossing RWY 1C/19C. 4-3. GROUND CONTROL 3. GC3 is responsible for aircraft/vehicles on the following areas of jurisdiction: 1. Departing RWY 30: The West Complex (all U and W Taxiways, TWY S and T), TWY Y south of Y8. TWY Y9/TWY Y11 and all Q TWYs west of TWY Z. 2. Not Departing RWY 30: The West Complex Taxiways (all U and W Taxiways, TWY S and T), and all Q Taxiways. TWY Y and TWY Z south of TWY Y11. 3. West Complex: When LC3 is delegated the West Complex (refer to Appendix 9, Section 1), GC3 retains control of the Q Taxiways and GC3 will normally be combined with GC2. NOTE. GC2 and GC3 s areas of jurisdiction change depending on whether IAD is departing RWY 30 or not, regardless of the landing direction (see Figure 12-1.) Areas of jurisdiction may change due to construction, volume or runway closure (pushing all departures east to depart RWY 30.) FOR FLIGHT SIMULATION USE ONLY 11
4-4. RUNWAY ASSIGNMENTS. Assign the departure runway for aircraft based on their initial fix based on CHAPTER 2. RUNWAY CONFIGS. 4-5. TAXI ROUTES. a. Taxiway directions. In general, it is recommended that the following taxiways be used in the following directions. This is only recommended, and may be used otherwise if operationally beneficial; 1. Kilo North 2. Juliet South 3. Yankee North 4. Zulu South b. Ensure that ground traffic will not obstruct runway exits that may be used by landing traffic. 4-5-2. ARRIVALS. a. Ensure appropriate runway exits are available to aircraft and there are no ATC restrictions to continued movement beyond the applicable holding position marking. Advise LC if appropriate runway exits are not available. b. The preferred taxi routes from RWY 1L/19R: 1. South Operation: a. During moderate to heavy RWY 19C arrival traffic: Taxiway U, T and Q. b. During light RWY 19C arrival conditions, traffic may be taxied via Taxiway W2, W3 or W4 with prior approval from LC2 and the FLM/CIC. 2. North Operation: Taxiway W2, W3 and W4. NOTE: The practice of the pilot being on LC2s frequency for the crossing of RWY 1C/19C is a best practice, resulting from the IAD Collaborative Workgroup. Unless coordinated otherwise, GC3 should have aircraft contact or monitor LC2 to cross runway 01C/19C. FOR FLIGHT SIMULATION USE ONLY 12
5-1. DUTIES. Local Control (LC) is responsible for: a. Separation between arrivals and departures. b. Successive departures. c. Departures and missed approaches/go-arounds. d. Tower local traffic and overflights. e. Maintaining the ATIS (preferably via vatis). CHAPTER 5. LOCAL CONTROL Local Control shall assign departure headings in accordance with this SOP or as otherwise coordinated or directed by PCT. All aircraft should be assigned a heading, even if on an RNAV departure. Local Control may circle arrivals between active runways provided coordination is accomplished and visual separation is established. Aircraft on missed approaches shall be climbed via runway heading to 2,000 and handed off to departure or if on an instrument approach told to execute the missed approach (Unless otherwise coordinated with PCT). Ensure departures are on their assigned heading and handed off to PCT within one mile of the runway. 5-1-1. LOCAL CONTROL 1 (LC1). Local Control 1 shall have jurisdiction for the LC1 airspace depicted below and for runway 1R/19L. Local Control 1 is responsible for helicopters operating in the east side of the airport. Handoff or point out helicopters inbound to/outbound from Landmark from northeast through southeast clockwise or traffic overflying the airport east to west at or below 2,000 feet to LC2/LC3, as appropriate. 5-1-2. LOCAL CONTROL 2 (LC2). Local Control 2 has no vertical airspace jurisdiction but is responsible for runways 19C/1C. LC2 must be aware of the ILS critical area. When visibility is less than two (2) miles or the ceiling is less than 800 feet and an aircraft conducting an ILS approach is inside of the ILS outer marker (OM) or the fix used in lieu thereof LC2 must protect all ILS critical safety areas and make sure runway crossings at W2, W3, or W4 are not performed when landing 19C in Cat II or III conditions. See APPENDIX 2 for ILS Critical areas. 5-1-3. LOCAL CONTROL 3 (LC3). Local Control 3 has jurisdiction as depicted below and for runways 12/30 and 1L/19R. Local Control 3 has control of helicopters land/departing Landmark to/from the west 5-1-3-1. 1C/30 OPERATIONS. Local Control 3 must be cognizant of arrivals for 1C with departures off of 30: a. An aircraft departing Runway 30 shall begin takeoff roll before the arrival to Runway 1C passes a point 2.27 NM south of the Runway 1C threshold. Local shall continue to monitor to ensure the departure crosses the extended FOR FLIGHT SIMULATION USE ONLY 13
centerline of Runway 1C prior to the arrival crossing over Runway 30. If the aircraft has not begun takeoff roll, and the arrival is inside the cut-off (2.27NM), the takeoff clearance shall be cancelled and/or go-around instructions shall be issued. b. LC3 shall not clear a Runway 30 departure for take-off when an aircraft is inside the Runway 1C cut-off point depicted on the final. c. The 2.27 NM cut-off point south of the Runway 1C threshold is depicted as a hash mark on the north video map. 5-1-3-1. 1L/30 OPERATIONS. Local Control 3 must also be cognizant of arrivals for 1L with departures off of 30: a. An aircraft departing Runway 30 shall begin takeoff roll before the arrival to Runway 1L passes a point 3.56 NM south of the Runway 1L threshold. Local shall continue to monitor to ensure the departure crosses the extended centerline of Runway 1L prior to the arrival crossing over Runway 30. If the aircraft has not begun takeoff roll, and the arrival is inside the cut-off (3.56 NM), the takeoff clearance shall be cancelled and/or go around instructions shall be Issued. b. LC3 shall not clear a Runway 30 departure for take-off when an aircraft is inside the Runway 1L cut-off point depicted on the final. c. The 3.56 NM cut-off point south of the Runway 1L threshold is depicted as a hash mark on the north video map. 5-2. CHANGES IN RUNWAY OPERATIONS CHECKLIST. a. Coordinate the first and last arrival/departure for each runway with SHD IADFW. b. Upon notification by SHD IADFW, ensure departures are stopped for sector reconfiguration. c. Ensure departures are held until SHD IADFW releases them. d. Inform Ground Control and Ramp Control of the new departure configuration and where to stage aircraft for departure. e. Ensure coordination is accomplished with all tower personnel. f. SHD IADFW shall inform LCE the sector reconfiguration is complete and when departures are released. g. Ensure the ATIS has been updated and reflects the proper status. 5-3. RNAV DEPARTURES. RNAV departures will be given to turbojet aircraft only. Even if an aircraft is on an RNAV departure, they should be assigned a heading consistent with the tables below. FOR FLIGHT SIMULATION USE ONLY 14
5-4. DEPARTURE HEADINGS. Config Runways or Directions Departure Corridor North South/West 245-310 North/East 010 North with 30 30 245-340 South 19L 190 19C 250-320 South with 30 30 220-320 South with 12 19L/C 190-210 5-5. MISSED APPROACHES/GO AROUNDS a. Assign all missed approach or go around aircraft to fly runway heading and to climb and maintain 2000. b. In the event of a missed approach or go around, automatic departure releases are suspended and local control MUST obtain a release from the departure controller prior to clearing another aircraft for takeoff. FOR FLIGHT SIMULATION USE ONLY 15
6-1. DUTIES. CHAPTER 6. MID-FIELD RAMP CONTROL The midfield ramp area is a non-movement area and in the real world it is operated by the Metropolitan Washington Airport Association (MWAA), not the FAA. We have created a Ramp Control position to establish order on the midfield ramp area during events or periods of heavy traffic. During normal operations on VATSIM, no controller is responsible for aircraft movement in this area. That means pilots may push back and startup at will. When RAMP is closed, GC does not assume the RAMP position and duties. When RAMP is open, it does not assume the Clearance Delivery position and duties, those remain with GCW. Ramp Control may only be opened when authorized by the ATM, DATM, TA, or CIC. 6-2. RAMP JURISDICTION. RAMP has jurisdiction for the midfield ramp area (outlined in blue below) which includes taxiways A, B, C, D, E, and F between J and Z. 6-3. PROCEDURES. a. RAMP shall approve all push backs in the midfield ramp area and inform aircraft which way to push their tail. Runway 1R/19L shall push tail west and Runways 1L/19R, 1C/19C and 30 shall push tail east. Example: UAL123 push approved, tail west, advise ready to taxi. b. Use the table in the Runway Assignments section to determine which runway to use based on the departure gate and runway configuration. Ground Control may change runway assignments as needed. c. When aircraft are ready to taxi, instruct aircraft to: a. Runway 1R/19L: Taxi east off the ramp, hold short of J, and contact ground. b. Runway 1/19R, 1C/19C, 30: Taxi west off the ramp, hold short of Z, and contact ground. FOR FLIGHT SIMULATION USE ONLY 16
APPENDIX 1. LOCAL CONTROL AIRSPACE Local Control Airspace. Local Control airspace North Ops. FOR FLIGHT SIMULATION USE ONLY 17
Local Control Airspace 12/19C/19L/19R Operations. Local control Airspace North Ops. FOR FLIGHT SIMULATION USE ONLY 18
APPENDIX 2. AIRFIELD LAYOUT Distance Remaining Information FOR FLIGHT SIMULATION USE ONLY 19
ILS Critical Areas (North Ops) FOR FLIGHT SIMULATION USE ONLY 20
ILS Critical Areas (South Ops). FOR FLIGHT SIMULATION USE ONLY 21
APPENDIX 3: PARKING GATES FOR FLIGHT SIMULATION USE ONLY 22
APPENDIX 4. SCRATCHPAD ENTRIES MCRAY: MCR JERES J211: JS1 JERES J220 or JERES J227: JS2 JCOBY# SWANN: SOK JCOBY# AGARD: DCR JCOBY# COLIN: DXE WOOLY#: BFR BUFFR: BFR OTTTO: OTO SCRAM#: SCR JDUBB#: JDB CLTCH#: CLH FOR FLIGHT SIMULATION USE ONLY 23