Skip to content

Quick Reference

  • IFR Departure Altitude: 6,000(Jet)/4,000(Prop)
  • IFR Departure Heading:
  • VFR Altitude: 2,500 (Heading 252-058)/3,000(Heading 059-251)
  • Pattern Altitude: 1,800
  • Missed Approach: 4,000

General

Positions

Callsign Position Radio Name Position ID Frequency
DTW_DEL Clearance Delivery Metro Delivery CD 125.050
DTW_M_GND Ramp/Metering Metro Ground GC 121.700
DTW_NW_GND Northwest Ground Metro Ground GNW 121.800
DTW_NE_GND Northeast Ground Metro Ground GNE 119.450
DTW_SE_GND Southeast Ground Metro Ground GSE 119.250
DTW_SW_GND Southwest Ground Metro Ground GSW 132.725
DTW_SW_TWR Southwest Local Metro Tower LSW 135.000
DTW_SE_TWR Southeast Local Metro Tower LSE 118.400
DTW_NE_TWR Northeast Local Metro Tower LNE 128.750
DTW_NW_TWR Northwest Local Metro Tower LNW 128.125
  1. Bolded positions must be opened first. Other positions may only be opened during events or with the permission of the ATM/DATM/TA/EC/CIC.
  2. When only one ground and local position is open, callsigns may be simplified to DTW_GND and DTW_TWR, respectively. In the event that ground and local are split:
    • Ground will operate as DTW_W_GND on 121.800 and DTW_E_GND on 119.450
  3. Local will operate:
    • DTW_N_TWR on 128.120 and DTW_S_TWR on 135.000
    • DTW_W_TWR on 128.120 and DTW_E_TWR on 128.750.
    • A combination of the two options is NOT permitted.

Runway/Flow Procedures

  1. RWYs 21/22 are designated as the preferential runways.
  2. DTW CIC has primary responsibility for initiating and coordinating runway changes. The DTW OM/OS/CIC determines the runway in use for DTW. Collaborate with D21 and ZOB TMUs for proposed runway changes. Use the following factors to determine the runway configuration:
    • Winds, to include: current, forecasted, TDWR boundary, adjacent facility, and final approach (pilot reported 500’ and below) winds.
    • Runway Selector Guide (see Appendix 2).
    • Runway availability based upon contaminants (standing water, FOD, etc.), snow removal, braking action, construction, emergencies, and/or special activities.
    • Environmental documents concerning Quiet Hours and South Flow priority.
  3. Inform DTW personnel when a runway change is going to occur. Ensure LC does not release new runway configuration departures until the change has been completed.
  4. Advise D21 CIC of the last aircraft to depart under the old configuration and when DTW has completed the runway change.
  5. Update the ATIS.
  6. Change appropriate equipment configuration.
  7. Opening and/or closing a runway.
    • Coordinate with D21 OM/OS/CIC, and DTW/D21 TMU.
    • Ensure ATIS, ASDE-X, and IDS are updated

Arrival/Departure Procedures

  1. Coordinate the TCP with D21.
  2. Reduced Separation on Final.
    • Separation of 2.5NM is authorized between aircraft established on the final approach course within 10NM of landing RWYs 03R, 21L, 04L, 22R, and 22L IAW JO 7110.65. -Should conditions prohibit the exercise of, or warrant suspension of this procedure, DTW will ensure the phrase “2.5 NA” appears on the DTW and D21 SIA pages of the IDS-4.
  3. Simultaneous Departures and Arrivals on Parallel Runways with Staggered Thresholds. Ensure ATIS contains the statement, “simultaneous arrival and departure operations are in use on RWYs 22R and 22L”. See para. 6-2-9 for additional requirements.
  4. Check the ATIS and IDS for accuracy and currency.
  5. Adhere to all National Traffic Management directives and procedures.

Duty Familiarization and Transfer of Position Responsibility

  1. All operational tower personnel are required to complete duty familiarization at the beginning of each shift.
  2. All operational positions require operational continuity through a transfer of position responsibility. Relief briefings shall be conducted verbally. With the approval of the controller being relieved, the relieving controller shall properly configure the position prior to transfer of control. Upon combining positions or position relief, there will be a 2-minute overlap. At the conclusion of the overlap, the relieved controller must state their operating initials verbally.
    • Note: The OS/CIC may waive the 2-minute overlap requirement if they deem the situation warrants. The following (not all-inclusive) may justify waiving the overlap:
      • Traffic
      • Staffing necessity
      • Physiological need.
  3. When position relief is required at a position where training is being conducted, the trainee (OJT) will brief the OJTI. When the briefing is completed, the OJT will unplug and the relieving CPC will plug in and receive a briefing from the OJTI. The OJTI, CIC or OS may waive the OJT briefing at their discretion.

Clearance Delivery

Duties and Responsibilities

  1. Receive and disseminate weather information.
  2. Prepare ATIS.
  3. Process miscellaneous flight data information.
  4. Accept requests for filing IFR flight plans.
  5. Process and distribute flight plan information.
  6. Issue clearance instructions.

Procedures

Prepare ATIS

  1. Prepare the ATIS broadcast in accordance with JO 7110.65.
  2. Use ATIS phonetic alphabet codes:
    • A – Z for ATIS.
  3. Other optional information as local conditions dictate.
  4. Subscribe to the ATIS in the controlling client.

Prepare Data for Distribution

  1. Review flight plans for accuracy.
  2. Amend routes/altitudes as appropriate.
  3. Coordinate route/altitude revisions with appropriate ZOB sector.
  4. Enter flight plans if operationally advantageous or as directed by the CIC.
  5. Enter VFR flight plans into the NAS and obtain a discrete beacon code.

Issue Clearances

  1. Issue departure clearances, amendments, and refile as follows:
    • Issue initial altitude and restrictions in accordance with DTW/D21 LOA.
    • Issue departure frequency as required.
    • If advised “Unable RNAV SID” by a flight crew, assign aircraft the METRO SID.
    • Ensure FPs being used are current. Immediately notify controllers of amended or removed flight plans.
  2. When Ramp Control is online:
    • Issue all aircraft “Call for Push” on 130.750 utilizing vTDLS

West Flow Procedures

  1. ROTG is suspended.
  2. Assign departure frequencies IAW the following table
West Depature East Depature
CCOBB PAVYL
KAYLN LIDDS
MIGGY CLVIN
TRMML BARII
ZETTR SNDRS
HHOWE MAARS/AANTS
HARWL/DUNKS/PISTN

Ramp Control

Duties

  1. This position is only to be controlled:
    • As a pre-approved rostered position during an event.
    • At the discretion of the ATM, DATM, or TA.
  2. Scan all areas of responsibility.
  3. Develop and implement a plan in coordination with the ATCT CIC that will ensure a safe and orderly flow of traffic.
  4. Process and forward flight plan information to the appropriate controller

Areas of Responsibility

  1. Ramp Control is responsible for the following non-movement areas:
    • South Ramp.
    • Gates A76-A78, B2-B20 (even), and C2-C38 (even) shall be sent to the appropriate ground frequency after contacting RC for pushback.
  2. North Ramp including Taxiway E

Procedures

Pushback Procedure

  1. When Ramp Control is active, all aircraft shall call RC for push and taxi.
  2. RC shall verify that the departure runway assigned to the aircraft is in compliance with any current event restrictions.

Strips Procedure

  1. Verify all information in each flight strip when an aircraft calls for push.
  2. Provide flight strips to the appropriate ground controller when the aircraft is transferred to GC.

Metering

  1. Ramp Control shall clear aircraft for pushback in a manner consistent with the order in which the aircraft requests were received.

Arriving Aircraft

  1. Arriving aircraft shall be issued taxi to requested gate if available.

Ground Control

Duties

  • Scan all areas of responsibility including; taxiways, runways, non-movement areas, ILS critical areas (see Appendix 8), and equipment at the position.
  • Develop and implement a plan that will ensure a safe and orderly flow of traffic.
  • Ensure computer entries are completed for instructions or clearances issued or received.
  • Process and forward flight plan information to the appropriate controller.
  • Establish queue lines for de-ice pads. Transfer of control will be at the discretion of the ground controller once all traffic concerns have been addressed.

Runway Assignments for Dual Departure Operations

Runway assignments will be issued on initial contact with Ground Control and will be based on traffic conditions, runway closures, and other operational requirements. 1. South Flow - BARII, CLVIN, HHOWE, LIDDS, PAVYL - EXPECT RUNWAY 21R - CCOBB, KAYLN, MIGGY, SNDRS, TRMML, ZETTR - EXPECT RUNWAY 22L 2. North Flow - BARII, CLVIN, HHOWE, LIDDS, PAVYL - EXPECT RUNWAY 3L - CCOBB, KAYLN, MIGGY, SNDRS, TRMML, ZETTR - EXPECT RUNWAY 4R 3. West Flow - BARII, CLVIN, LIDDS, PAVYL, SNDRS - EXPECT RUNWAY 27L - CCOBB, HHOWE, KAYLN, MIGGY, TRMML, ZETTR- EXPECT RUNWAY 27R 4. BARII, CLVIN, and SNDRS departures may be assigned either complex in South/North flow as operationally advantageous.

Procedures

Intra-Facility Coordination

  1. Operational requests:
    • Prior to coordination, scan for traffic to ensure a request can be approved.
    • Coordinate with the appropriate LC when an aircraft/vehicle is requesting to cross an active runway by stating the request and position; example, “CROSS RUNWAY (number) AT (position)”. Report completion of the runway crossing to the appropriate LC in a timely manner. When taxiing an aircraft to a runway other than the posted flow, coordinate with appropriate ground controllers to ensure “first come, first served”, EDCT, and ESP release times can be met; if unable, advise TMU. Comply with sequence dictated by other ground positions, TMU, or CIC.
    • Authorization for aircraft/vehicles to proceed on or along an active runway for purposes other than crossing, may be provided on GC frequency after coordination with LC is complete IAW JO 7110.65 Para 3-1-3d.
    • Coordinate all intersection departures with LC.
  2. Controllers are authorized to transgress, using non-verbal coordination, adjacent controllers’ delegated taxiways and ramps depicted in Appendix 3, provided the following conditions are met:
    • Traffic can be visually monitored and separation with other aircraft can be ensured.
    • Traffic will proceed in the normal traffic flow.
    • The CIC may re-delegate control responsibility of coordinated taxi areas to the associated controller

Taxiway Routes and Restrictions

Taxiway restrictions: (see Appendix 1)

  1. Do not allow two ADG V aircraft to pass each other on TWY Y and TWY K, between TWY U and TWY K-6.
  2. ADG V aircraft parking at RON spot A may taxi in and out at TWY H-2. They may not taxi on TWY H to TWY F, they must be towed.
  3. No ADG V aircraft may turn:
    • North on TWY K while westbound on TWY B.
    • East on TWY B while southbound on TWY K.
  4. No ADG IV or above may turn:
    • South on TWY Y while westbound on TWY B.
    • East on TWY B while northbound on TWY Y.
  5. ADG V aircraft and above are restricted from using TWY P between TWY J and TWY P-3.
  6. ADG V aircraft and above are restricted from using TWY H between TWY B and TWY F.
  7. No aircraft with a wingspan more than 135 ft may turn east on TWY V while northbound on TWY G.
  8. When B757 or larger push back at D6, no aircraft may taxi on TWY K between TWY K-6 and TWY K-7.
  9. TWY K is for northbound traffic only. TWY Y is for southbound traffic only.
  10. During weather conditions less than 300’ ceiling and/or 1SM visibility, aircraft with tail heights of 35' or above must not be allowed to pushback or taxi on TWY K north of TWY Y-10 while an aircraft is departing RWY 04R.
  11. When departing RWY 21R, aircraft with tail heights above 61’ are not authorized to use TWY J between TWY J-7 and TWY P.
  12. Via Letter of Authorization, multiple runway crossings may be issued with a single clearance along the routes shown below: (see Appendix 5)
    • RWY 27R and RWY 22L at TWY V and TWY Y
    • RWY 27R and RWY 22L at TWY V and TWY K
    • RWY 27R and RWY 21L at TWY W and TWY W-6
    • RWY 27R and RWY 21R at TWY P and TWY V
  13. Do not allow aircraft to taxi between an aircraft pushed back, and the gate from which that aircraft was pushed.
  14. Jet engine run-ups can only be conducted in the GRE.
  15. Movement of aircraft or vehicles on non-movement areas is the responsibility of the pilot, the aircraft operator, or the airport management. (see Appendix 4).

Braking Action

  1. Braking action reports of NIL closes the affected runway and/or taxiway to all aircraft.
  2. Notify the CIC upon initial receipt of any reported braking action less than GOOD, and any reported POOR or NIL braking action, and when reports indicate that conditions have changed

Departure Restrictions

  1. Ensure that aircraft with an EDCT are, to the extent possible, able to depart on time. Departures may be released no earlier than 5 minutes prior to the EDCT or 5 minutes after the assigned EDCT. If the aircraft is unable to meet these parameters, advise TMU/CIC for a revised EDCT.
  2. Request an ESP release time, as appropriate. Departures may be airborne from 2 minutes before, to 1 minute after the ESP time.

West Flow Procedures

  1. GC must advise LNE when using TWY A.
  2. GC must advise LSE when using TWY Q.
  3. GNE will
    • Own the movement areas depicted in Appendix 3 (West Flow).
    • Sequence departures to RWY 27R at TWY S-7.
    • Control pushbacks from gates A76 – A78.
    • Hand off aircraft to GSE on TWY W holding short of TWY J.
    • Hand off aircraft to GSW on TWY Y holding short of TWY Y-4
  4. GSW will:
    • Own the movement areas depicted in Appendix 3 (West Flow).
    • Hand off aircraft to GNW on TWY A holding short of TWY V.
    • Hand off aircraft to GNE on TWY K holding short of TWY U.
  5. GNW will:
    • Own the movement areas depicted in Appendix 3 (West Flow).
    • Deliver departures to RWY 27R at TWY V-1, and deliver FPs to GNE for sequencing
  6. GSE will:
    • Own the movement areas depicted in Appendix 3 (West Flow).
    • Sequence departures to RWY 27L.
    • Hand off aircraft to GNE on TWY P holding short of TWY P-3 and/or on TWY M holding short of TWY M-3.
    • Hand off aircraft to GSW on TWY T holding short of TWY Q.

Ramp Control Online Procedures

  1. All arrivals shall be handed off to RC before entering the north or south ramp

Position Specific Procedures

Ground Control Northwest (GNW)

  1. GNW delegated areas are depicted in Appendix 3.
  2. Control pushbacks from the following terminals and gates:
    • North Terminal – D2, D4, D6 (B757 or larger), D30, D32 and any aircraft that will infringe on the movement area.
    • DAL Ramp – A76, A77, A78.
  3. Traffic for GSW will be handed off on:
    • South Flow – TWY Y holding short of TWY U.
    • North Flow – TWY Y holding short of TWY Y-4.
  4. During North Flow, comply with metering and staging requests from GSW.
  5. Traffic for GNE will be handed off on:
    • TWY U holding short of TWY U-8.
    • RWY 09L holding short of TWY F.
    • TWY V holding short of TWY F.
  6. Sequence departures to RWY 22L, RWY 22R, and RWY 27R at TWY V-1
  7. Monitor and operate communications equipment on frequencies: VHF - 121.8

Ground Control Northeast (GNE)

  1. GNE delegated areas are depicted in Appendix 3.
  2. Sequence departures to RWY 03L at TWY M-1, RWY 21R, RWY 21L, and RWY 27R at TWY S-7.
  3. Traffic for GNW will be handed off on TWY H holding short of TWY B.
  4. Taxi aircraft into the DAL ramp via TWY U-7.
  5. During de-ice season, GNE is delegated Taxilane F, Taxilane E-2 and pushback gates D1, D3, and D5.
  6. Monitor and operate communications equipment on frequencies: VHF - 119.45

Ground Control Southeast (GSE)

  1. GSE delegated areas are depicted in Appendix 3.
  2. Sequence traffic to RWY 03L at TWY P-1, and RWY 03R at RWY 27L.
  3. Traffic for GSW will be handed off on TWY T holding short of TWY Q.
  4. During North Flow, comply with metering and staging requests from GSW.
  5. When instructed to take control of RWY 04L arrivals, assume control responsibility of TWY T between TWY Q and TWY K, and TWY A and TWY Q. Hand off to GSW on TWY T holding short of TWY K.
  6. Taxi aircraft into the DAL ramp via TWY J-8 and TWY J-9.
  7. Monitor and operate communications equipment on frequencies: VHF - 119.25

Ground Control Southwest (GSW)

  1. GSW delegated areas are depicted in Appendix 3.
  2. Control pushbacks from even numbered gates at Concourses B and C.
  3. During North Flow, GSW may stipulate to the surrounding ground controllers (GNW, GSE) how traffic will be delivered to their movement areas. This includes metering and staging requests.
  4. Sequence traffic to RWY 04R and RWY 04L.
  5. Deliver aircraft to the DAL ramp at the intersection of TWY Q and TWY J, or TWY J short of TWY J-9. Resolve all conflicts at the intersection of TWY Q and TWY J.
  6. Traffic for GNW will be handed off on:
    • South Flow – TWY K holding short of TWY U.
    • North Flow – TWY K holding short of TWY U.
  7. Monitor and operate communications equipment on frequencies: VHF - 132.72

Local Control

Duties

  1. Separate:
    • Aircraft within the lateral limits of DTW delegated airspace. (see appendix 6)
    • Aircraft IAW DTW/D21 LOA.
    • Operations conducted on active runways.
  2. When vectoring IFR aircraft, refer to MVAs depicted in Appendix 10.
  3. When Mode C is determined to be invalid, notify the CIC of the callsign, assigned/reported altitude and Mode C indicated altitude

Combining LC Positions

  1. The combining controller shall not relinquish the position while a runway is being crossed, or occupied by a vehicle.
  2. The combining controller shall place all pertinent FPSs in the active bay of the relieving controller.

Airspace Delegation

  1. South Flow (see Appendix 6):
    • Area A – Delegated to LSW.
      • NOTE: LSW delegates to LNW the final approach course for RWY 22L.
    • Area B – Delegated to LSE.
      • NOTE: LSE delegates to LNE the final approach course for RWY 21R.
    • Area C – Delegated to LNE.
    • Area D – Delegated to LNW.
  2. North Flow (see Appendix 6):
    • Area A – Delegated to LNW.
    • Area B – Delegated to LNE.
    • Area C – Delegated to LSE.
      • NOTE: LSE delegates to LNE the final approach course for RWY 03L.
    • Area D – Delegated to LSW.
      • NOTE: LSW delegates to LNW the final approach course for RWY 04R.
  3. West Flow (see Appendix 6):
    • Area A – Delegated to LNE
    • Area B – Delegated to LNE.
    • Area C – Delegated to LSE.

General Procedures

Utilizing a Runway Not Designated as Active

  1. Coordinate with all GCs and all other LCs prior to landing/departing on a runway not designated as active.
  2. Advise all affected positions when an operation on a runway not designated as active is complete.

Braking Action Reports

  1. Solicit and forward to the OS/CIC, braking action reports when the possibility of diminished or improved braking action exists.
  2. Upon receipt of a "POOR" or “NIL“ braking action report:
    • Immediately notify the OS/CIC.
    • Any runway receiving a NIL braking action is closed to all aircraft

IFR/Not in Sight Operations

Departure headings must parallel or diverge from the arrival runway until separation with the arrival is assured when: 1. The field is IFR, or an arrival aircraft is inside of two miles and not in sight, and 2. 2 increasing to 3 is not being applied, and 3. Departure is not on an RNAV SID.

NOTE: This may have an effect on coordinated releases

Class B VFRs.

VFR arrivals or overflights at or below 2,500 will be worked by LC. Obtain a beacon code and issue clearance into Class B airspace and point-out aircraft as necessary to D21

Class B Violations.

  1. If an aircraft contacts DTW and is within the confines of Class B airspace, you must:
    • RADAR identify the intruder.
    • Verify altitude/accuracy of the intruder mode C.
    • Advise the pilot that they are within Class B airspace without a clearance.
    • Advise the intruder of their exact location.
    • Advise the CIC.
  2. For an unidentified target that DTW tracks through Class B airspace:
    • Start a track on the intruder using the word “VIOLATR” in scratchpad.
    • Solicit pilot reports to identify the intruder.
    • Hand-off the intruder inter/intra-facility. Advise the receiving controller that the aircraft being tracked is a Class B violator and that the aircraft should be tracked to its destination. Request that the receiving controller/facility attempt to identify the intruder.

Transitioning Between South and West Flow

  1. Configuration transitions involving RWY 27L arrivals and RWY 21R and/or RWY 22L departures must adhere to the following requirements:
    • To transition from a South Flow to West Flow configuration, the last departure from RWY 21R or RWY 22L must have crossed the RWY 27L projected center line prior to the RWY 27L arrival crossing the RWY 27L ILS FAF.
    • To transition from a West Flow to South Flow configuration, the last arrival for RWY 27L must have landed and be clear of RWY 27L prior to a RWY 21R or RWY 22L departure being cleared for takeoff and commencing takeoff roll.
  2. Configuration transitions involving RWY 27R arrivals and RWY 21R and/or RWY 22L departures must adhere to the following requirements:
    • To transition from a South Flow to West Flow configuration, the last departure from RWY 21R or RWY 22L must have crossed the RWY 27R centerline prior to the RWY 27R arrival crossing the RWY 27R ILS FAF.
    • To transition from a West Flow to South Flow configuration, the last arrival for RWY 27R must have landed and be clear of RWY 27R prior to a RWY 21R and/or RWY 22L departure being cleared for takeoff and commencing takeoff roll

Waiver 14-T-13

DTW has been granted a waiver to conduct Simultaneous Departures and Arrivals on Parallel Runways with Staggered Thresholds. Special provisions, conditions, and limitations are as follows: 1. Applies only to RWY 22L departures and RWY 22R arrivals. 2. ASDE-X must be operational. 3. Departure and missed approach course diverge by at least 30 degrees. 4. A proper radar presentation is available to adequately monitor arriving and departing aircraft. 5. Individual aircraft identification is maintained. 6. ATIS contains a statement that simultaneous arrival and departure operations are in use and on which runways.

Arrival Procedures

  1. LC must perform the following procedures prior to assuming control of approach sequenced arrival aircraft:
    • Ensure arrival aircraft are “quick looked” to the tower radar and that full data blocks are displayed.
    • Scan scratch pad information to correlate the type approach and runway assignment for each arrival.
  2. LC must coordinate with the appropriate arrival controller/final monitor any change in arrival runway assignment via the STARS scratch pad.
  3. LC must display the tower delegated airspace map and the approach courses in use.
  4. When required, protect ILS Critical Areas as depicted in Appendix 8.

Reduced Separation on Final

  1. Separation of 2.5NM is authorized between aircraft established on the final approach course within 10NM of landing RWYs 03R, 04L, 21L, 22L, and 22R IAW JO 7110.65.
  2. Advise OS/CIC when conditions prohibit reduced separation on final

Monitor Approaches

  1. LC must:
    • Coordinate with the CIC to determine the TCP.
    • Coordinate a VSP with the associated final monitor, as appropriate.
  2. Simultaneous Independent Approaches may be conducted to:
    • South Flow – RWY 21L, RWY 22L, and RWY 22R.
    • North Flow – RWY 3R, RWY 4L, and RWY 4R.
    • West Flow – RWY 27L and RWY 27R.
  3. Simultaneous Independent Close Parallel Approaches/PRM approaches, and Y-localizer must be used for the following runway pairs:
    • RWY 22L and RWY 22R.
    • RWY 4L and RWY 4R

NOTE: When conducting successive ILS Y approaches to RWY 04L/22R, Category A, B, & G aircraft will normally be assigned a different runway unless coordination has been accomplished with the tower

Clearing the Runway

  1. LC is responsible for advising GC when an aircraft will be issued subsequent taxi instructions following the initial turn off, if not in compliance with para. 6-2-1.b.
  2. Instruct the aircraft where to exit the runway and issue the appropriate GC frequency if not IAW para. 6-2-1.b

Depatures Procedures

  1. Prior to departure, but not more than 5 minutes prior to expected departure, coordinate with the receiving departure position:
    • Departures that advise they will be unable to meet a crossing restriction.
    • Departures that will exceed 250kts.
    • Non-RNAV departures when ROTG is in effect.
  2. TWY Y-2 is the normal departure point for RWY 04R.
  3. Intersection departure distances are rounded down to the nearest 50ft. See Appendix 7.
  4. Advise CIC of any stops or restrictions received from D21.
  5. LC must ensure FPs are complete and accurate

ROTG

  1. Issue appropriate initial fix for the assigned runway and SID.
  2. The issuance of ROTG is runway dependent.
  3. When aircraft depart on RNAV SIDs that turn in the same direction off different runway complexes, apply 3nm radar separation, or required separation IAW DTW/D21 LOA (para. 10). In the event ROTG aircraft are in an unsafe situation, it may be necessary to take one or more of the aircraft off the RNAV SID with a vector and/or an altitude.
    • NOTE: When issuing a vector, DTW must assign, “CLIMB AND MAINTAIN (altitude)”, and coordinate with the appropriate DTW and/or D21 sectors
  4. When ROTG is suspended, refer to DTW/D21 LOA
  5. All departures via CLVIN#, BARII#, and SNDRS# procedures during south flow operations must adhere to the following departure separation requirements:
    • (INSERT CHART HERE!!!!!!!!!!!!!)
    • Note: MIT specified as “Boundary” references the local airspace boundary with D21 departure.
  6. Ensure that aircraft are on their assigned route prior to frequency change.
  7. When an airborne aircraft will be taken off the RNAV OTG procedure, do not release a subsequent departure that will enter the receiving controller’s airspace until that aircraft exits the lateral limits of DTW airspace

LUAW

In addition to the requirements in JO 7110.65, the following procedures must be followed while conducting LUAW: 1. During same runway operations, while LUAW is being applied, landing clearance must be withheld if the conditions are less than reported ceiling 800 or visibility less than 2SM. Landing clearance may be issued once the departing aircraft starts takeoff roll. - EXAMPLE: “DAL123, runway 22L, continue, traffic holding in position.” 2. C must not be combined with any other non-local position 3. Do not authorize an aircraft to LUAW at any time when the intersection is not visible from the tower. - EXCEPTION: Via waiver, DTW is authorized to LUAW at RWY 04R at TWY Y-2 when the intersection is not visible from the tower provided: - GC must ensure the accuracy of the departure sequence prior to switching the aircraft to LC - GC and LC must correlate the aircraft’s position using the ASDE IAW JO 7110.65. - LC must state the aircraft call sign and intersection on initial contact when issuing a LUAW clearance IAW prescribed phraseology (JO 7110.65, para. 3-9-4). - LC must receive pilot read back for accuracy when issuing a LUAW clearance at an intersection, and restate the aircraft call sign and intersection when issuing a departure clearance IAW prescribed phraseology (JO 7110.65, para. 3-9-4). - RWY 04R must be restricted to departures only when the waiver is in use. - Ensure only one aircraft at a time is permitted to LUAW on RWY 04R.

Release Definitions

  1. Rolling Call: The notification that the released aircraft has begun departure roll.
  2. Release: Authorization to enter airspace or depart on a SID delegated to another local controller.
  3. Releasing Controller: The controller delegating airspace required by the other controller.
  4. Released Controller: The controller receiving a release.

Coordination for Departure Releases

  1. When CIC or TMU coordinates a release:
    • Release aircraft as determined by CIC or TMU.
    • It is the releasing controller’s responsibility to initiate coordination.
  2. When LC coordinates a release, include the following:
    • SID and/or heading; advise if aircraft is VFR.
    • Type aircraft if wake turbulence is applicable.
  3. Types of releases.
    • Without traffic. A releasing controller approves a request; phraseology: “(type aircraft if applicable) (SID/heading) RELEASED.”
    • With traffic. When a releasing controller approves a request with traffic exchange, the following conditions must be met:
      • Conflicting airborne/rolling traffic information must be issued, i.e. “KAYLN AIRBORNE, SNDRS ROLLING, CCOBB RELEASED.”
      • Traffic is observed and acknowledged by the released controller.
      • Separation responsibility is transferred to the released controller.

Departure Headings

South Flow

Arrival Runway Depature Runway Depature Fixes Heading Frequency Sector
21L/22R 21R MAARS 150 134.3 East Sat
21L/22R 22L ANNTS, HARWL, DUNKS, PISTN 260 118.95 West Sat

North Flow

Arrival Runway Depature Runway Depature Fixes Heading Frequency Sector
3R/4L 3L MAARS 120 134.3 East Sat
3R/4L 4R ANNTS, HARWL, DUNKS 310 118.95 West Sat
3R/4L 4R PISTN 330 118.95 West Sat

West Flow

Arrival Runway Depature Runway Depature Fixes Heading Frequency Sector
27L/27R 27L ANNTS, MAARS 180 134.3 East Sat
27L/27R 22L HARWL, DUNKS, PISTN 360 118.95 West Sat

Position Specific Procedures

Local Control Northwest (LNW)

  1. LNW is delegated RWY 04R/22L.
  2. Monitor and operate communications equipment on frequencies: VHF – 128.12
  3. LNW is responsible for crossing aircraft holding at taxiways V, Z5, and Z7. After crossing, aircraft shall be instructed to contact Ground Control on the appropriate frequency

Local Control Northeast (LNE)

  1. LNE is delegated RWY 03L/21R and RWY 09L/27R.
  2. LNE must monitor LSE arrivals and advise LSE when wake turbulence advisories are required.
  3. Monitor and operate communications equipment on frequencies: VHF – 128.75

Local Control Southeast (LSE)

  1. LSE is delegated RWY 03R/21L and RWY 09R/27L.
  2. Monitor and operate communications equipment on frequencies: VHF – 118.4

Local Control Southwest (LSW)

  1. LSW is delegated RWY 04L/22R.
  2. LSW shall stage arrival aircraft from Runway 22R parking at the north terminal at taxiways V, Z5 and Z7 holding short of Runway 22L/4R (depending on gate assignment). Aircraft shall be instructed to monitor tower on 128.12 unless otherwise coordinated.
  3. Monitor and operate communications equipment on frequencies: VHF – 135.0

Appendices

Appendix 1: Aircraft Groups, Tail Height, and Wingspan

Appendix 2: Runway Selector Guide

When RWYs 27L/R are being used for arrival traffic, DTW ATCT will depart RWY 22R to the maximum extent possible with strong emphasis toward safety and efficiency. When conditions are such that departing RWY 22R is no longer feasible, RWYs 27L/R will be used for departure traffic.

Utilize the following guide as an aid in determining runway/flow direction: - NOTE: The guide below is based on steady state winds. When gusts are reported, additional consideration must be given based on the velocity, frequency and duration of the gusts.

Appendix 3: Ground Control Areas of Responsibility

Appendix 4: Airport Movement Areas

Appendix 5: Multiple Runway Crossings

Appendix 6: Local Control Delegated Airspace

Appendix 7: Intersection Departure Distances

Appendix 8: ILS Critical Areas

Appendix 9: Adjacent Airspace

Appendix 10: MVAC and Class B Surface Area