4. Ground Movement Control ("Dubai Ground")
4.1 General provisions
The Ground Movement Controller (GMC) is responsible for managing aircraft movements on all aerodrome movement areas except for runways and their associated taxiways. Departing aircraft are given pushback instructions and instructions to taxi to the runway holding point. Arriving aircraft are assigned a stand and instructed to taxi as appropriate.
4.2 Pushback procedures
4.2.1 General procedure
When aircraft have been handed off to GMC, they shall be fully ready for pushback, and are 5 minutes from their TOBT. Assuming no obstructions, they shall be instructed to push back immediately. If an aircraft is cleared for push and start but does not begin pushing within 2-5 minutes, the pushback clearance is canceled, and a new TOBT is assigned.
Aircraft requesting push that are not squawking their assigned transponder code shall be instructed to hold position and squawk the correct code. They must not be allowed to move until doing so.
Pushback direction is based primarily on aircraft location and runway configuration.
All non-A380 traffic on aprons B shall be instructed to push back onto U. All code F (A380/B747-8) traffic on apron B shall be instructed to push back onto taxiway J and face the appropriate direction.
On apron F and A, all traffic shall be instructed to push back onto Z. Pushbacks onto taxiway K shall not be permitted under any circumstances.
A pushback clearance must be a variant of those provided in 3.2.2 and include an instruction to “FACE WEST” or “FACE EAST” as appropriate.
Example
Pilot: "Dubai Ground, UAE4CK, on stand A4 request pushback."
Controller: "UAE4CK, Dubai Ground, pushback approved, face east on Z."
Pilot: "Pushback approved, facing east on Z, UAE4CK."
Conditional pushback instructions may also be issued if an aircraft is taxiing behind another waiting for pushback.
Example
Pilot: "Dubai Ground, FDB647, on stand E8 request pushback."
Controller: "FDB647, Dubai Ground, behind the company 737 passing left to right, pushback approved, face east on P."
Pilot: "After the company 737 passes from left to right, pushback approved, facing east on P, FDB647."
4.2.2 Pushback types
4.2.2.1 Standard pushback
This type will normally have the aircraft stop abeam the adjacent stand. The phraseology for this type of pushback is identical to the pushback phraseology as provided in 3.2.1.
4.2.2.2 Short pushback
A short pushback instruction shall require the aircraft to complete the pushback abeam the current stand such that the adjacent stand will not be blocked.
Example
Pilot: "Dubai Ground, UAE51, on stand F6 request pushback."
Controller: "UAE51, Dubai Ground, short pushback approved, face west on Z to finish abeam stand F6."
Pilot: "Short pushback approved, facing west on Z to finish abeam stand F6, UAE51."
4.2.2.3 Long pushback
A long pushback instruction shall require aircraft to complete the pushback operation two stands away from where the pushback was commenced. This manoeuvre may be used when aircraft are vacating a stand to be used by another aircraft that is taxiing in.
Example
Pilot: "Dubai Ground, UAE6LT, on stand A6 request pushback."
Controller: "UAE6LT, Dubai Ground, long pushback approved, face east on Z to finish abeam stand A4."
Pilot: "Long pushback approved, facing east on Z to finish abeam stand A4, UAE6LT."
4.2.3 Simultaneous pushback operations
Simultaneous pushbacks may be permitted from adjacent stands provided aircraft are instructed to manoeuvre in accordance with 3.2.2 such that on completion of both aircraft’s pushback operation, they will be separated on the taxiway by two aircraft stands.
4.2.4 Dual runway 30R pushback procedures
When departing 30R, all aircraft parked on apron B and F shall be instructed to push back to “FACE WEST”.
Aircraft on A, C, D and E aprons shall be in instructed to push back to “FACE EAST” as provided in 3.2.1.
Traffic pushing back from stand C62, C63 and C64 shall be instructed to "FACE NORTH" on J1.
Traffic pushing back from stand A1 and A2 shall be instructed to "FACE NORTH" on J2.
Traffic pushing back from stand A10 and D10 shall be instructed to "FACE NORTH" on J3.
Other traffic shall be pushed back in the appropriate direction for taxi as provided in 3.3. Care must be taken to ensure that the pushback will not block key taxiway intersections.
Important
For traffic parked on stand A1, A2 and D1, before issuing pushback instruction, GMC 1 must coordinate the pushback with AIR South to avoid blocking the high speed turn onto taxiway J2.
For traffic parked on stand C62, C63 and C64, before issuing pushback instruction, GMC 2 must coordinate the pushback with GMC 1 to avoid blocking J1 for Code F traffic.
4.2.5 Dual runway 12R pushback procedures
When departing 12R, aircraft south of 12L shall push in the appropriate direction to give the shortest taxi possible to the standard departure point on 12R.
Aircraft on aprons E and Q shall be instructed to push in the appropriate direction that will allow the shortest taxi time to holding point N2.
4.2.6 Single runway pushback procedures
During single runway operations, aircraft shall be pushed back in the most convenient direction to join the appropriate taxi route as provided in 4.3 for the respective runway mode.
4.3 Taxi procedures
4.3.1 General procedures
Departing aircraft from aprons F, B and D are usually taxied out using the taxiways closest to the concourses (U, W, Y, Z). The only exception to this is code F (A380/B747-8) traffic departing from apron B which must taxi using J and must not be allowed to taxi on U, W or Y.
Important
Where aircraft are taxied to runway holding points, transfer of control to AIR shall be made early enough such that the aircraft is not required to stop its taxi. For traffic taxiing between GMC areas of responsibility, aircraft should be handed off early enough to ensure a non-stop taxi, provided no conflicts are anticipated.
Example
Pilot: "Dubai Ground, UAE7TR, request taxi."
Controller: "UAE7TR, Dubai Ground, taxi via Z, L4, M, holding point M13A, runway 30R."
Pilot: "Taxi via Z, L4, M, holding point M13A, runway 30R, UAE7TR."
Several “cross-over” taxiways exist to allow aircraft to transfer between the inner and outer taxiways. These shall be used whenever necessary to allow efficient flow of traffic around the airport.
To deconflict traffic, and to reduce the length of taxi clearances, intermediate holding points shall be used wherever possible.
Intermediate holding points shall always be used when transferring aircraft between controllers to avoid conflicts and the area of responsibility boundaries.
Example
Pilot: "Dubai Ground, UAE9LT, request taxi."
Controller: "UAE9LT, Dubai Ground, taxi via Z, L4, hold L4A."
Pilot: "Taxi via Z, L4, hold L4A, UAE9LT."
Arriving aircraft shall not immediately be handed off by AIR. They must instead be given an initial taxi instruction onto M, N, J2 or K to keep traffic flowing. Therefore, GMC shall assign an arrival stand to aircraft when they are on final approach.
Once the aircraft is handed off to GMC, they may be taxied to their stand. Arrivals shall generally be taxied via the outside taxiways that are farthest away from the stands.
Aircraft are not required to cross-over to the inside taxiways before initiating the turn onto stand for aprons A, B, D, and F.
4.3.2 Taxiway restrictions
Code F aircraft shall not be permitted to taxi on U, Y, W. These taxiways are limited to code E and below.
Code F aircraft shall not be permitted to use the curved portions of J, J1 and J2 if code E aircraft are simultaneously taxiing on the curved portions of U, Y or W and vice versa.
In this case, traffic shall be instructed to hold short of the curved portion until the adjacent curved taxiway is clear.
Taxiway Q shall be limited to code C and below.
Important
These taxiway restrictions must be adhered to to ensure adequate wingtip clearance during taxi.
4.3.3 Dual runway 30R
4.3.3.1 Departure taxi procedures
When departing from 30R in the dual runway configuration, all aircraft pushing back on apron B and F shall be instructed to taxi via L4 and M.
Aircraft on aprons A and D shall be instructed to taxi to holding point K14. During periods of lower aerodrome departure or arrival activity, K11 or K12 may be used for runway crossings only after coordination with AIR.
Before reaching these holding points, aircraft shall be transferred to AIR North.
Eastbound traffic flow on K shall not be permitted between K1 and K8, as this blocks the rapid exit taxiways from 30L.
Departures from apron C shall be instructed to taxi via L1 and M.
In all applicable cases, when traffic turns to enter taxiway M, transfer to AIR shall be initiated.
Departures from apron E shall be instructed to cross over to and taxi via N.
4.3.3.2 Arrival taxi procedures
Aircraft shall vacate 30L onto K9, K8 or K6, depending on the stand assignment described in 3.4.5. After initial taxi is issued by AIR, aircraft are handed off to GMC as provided below.
Apron A
For aircraft parking on apron A vacating at K8, taxi routings shall be via K eastbound.
Apron B (except stand B27)
Traffic shall vacate via K8 or K9 then be instructed by AIR South to taxi to J2A. Traffic shall then be transferred to GMC 1.
Traffic shall be instructed by GMC1 to taxi right on J to the appropriate stand.
Stand B27 and F27
Traffic parking on F27 and B27 shall be instructed by AIR South to taxi via J right onto Z then left onto W to hold at WA. Traffic shall then be transferred to GMC 1 for further taxi.
Apron C
Traffic shall vacate at K9, K8 or K6, AIR South shall instruct traffic to taxi via K and hold short at KL and initiate transfer to GMC 1.
GMC 1 shall issue taxi via K westbound to hold at KF and transfer control to GMC 2. GMC 2 shall taxi the aircraft to the appropriate stand.
Apron D
Traffic shall vacate via K8 or K9 then be instructed by AIR South to taxi to J2A. Traffic shall then be transferred to GMC 1.
GMC 1 shall instruct traffic to taxi left on J for the appropriate stand.
Apron E
Traffic shall vacate at K9, K8 or K6, AIR South shall instruct traffic to taxi via K and hold short at KL and initiate transfer to GMC 1.
GMC 1 shall instruct traffic to taxi via K, L3 then to holding point M2. Before reaching M2, aircraft shall be transferred to AIR North for runway crossing.
After runway crossing, traffic shall be transferred to GMC 2 to taxi to the appropriate stand.
Apron F (except stand F26L)
4.3.4 Single runway 30R
4.3.4.1 Departure taxi procedures
When departing 30R in the single runway configuration, all aircraft pushing back on apron A, B, D and F shall be instructed to taxi via K4, K7, or K11 and cross 30L as appropriate.
Except for aircraft taxiing from apron C, the section of taxiway M west of K4 shall not be used for departure taxi as this blocks the arrival flow from 30R.
The taxi routes from apron E shall be the same as with the dual runway 30 configuration.
4.3.5 Single runway 30L
4.3.5.1 Departure taxi procedures
When departing 30L in the single runway configuration, all aircraft pushing back on aprons A, B, D and F shall taxi via Z until past 30L RETs after which they shall cross onto K and taxi to holding point K17.
Eastbound flow shall not be permitted on K between K1 and K8.
Aircraft on apron E shall cross 30R at N9 and taxi to holding point M20.
4.3.6 Dual runway 12R (Arrival Bias)
4.3.6.1 Departure taxi procedures
When departing from 12R, aircraft parked on aprons A, B, D, F and C shall be taxied via the shortest appropriate route to the standard departure holding points K3, K4 and K5 avoiding conflicts with other departing or arriving traffic.
Aircraft parked on apron E and Q shall be taxied via the standard route to holding point N2. Before reaching N2, aircraft are transferred to AIR North for runway crossing. Aircraft then shall taxi via L3, then K to holding point K3, K4 or K5 as appropriate.
Use of full-length holding points (K1, K2) shall require coordination with AIR and shall not be assigned unless requested for performance reasons. These aircraft shall be advised of possible delays due to runway dependency.
Departing traffic shall not be issued taxi to holding points M
4.3.8 Single runway 12R
4.3.8.1 Departure taxi procedures
Departure taxi routes for 12R single runway operation shall be the same as in dual runway operations, except that aircraft may be assigned full length holding points without restriction.
4.3.9 Single runway 12L
4.3.9.1 Departure taxi procedures
When operating from 12L during single runway operation, aircraft pushing back on the southern aprons shall taxi westbound to join L3/L4 and then to M1.
Aircraft departing the northern aprons shall taxi to N1.
4.3.10 Handoff procedures
When departing traffic has been instructed to taxi to their departure holding points as per the standard taxi routings and when the handoff towards AIR is initiated as per AoR, GMC will ask departing aircraft to monitor the AIR frequency.
Example
Controller: "UAE530, monitor tower 118.750."
When departing traffic has been instructed to taxi to runway holding points for crossing as per the standard taxi routings and when the handoff towards AIR is initiated as per AoR, GMC will ask departing aircraft to contact the AIR frequency.
Example
Controller: "UAE8KC, contact tower 119.550."
Important
The key distinction between monitor and contact is as follows: monitor instructs the pilot to switch to the assigned frequency and await a call from the next controller, while contact requires the pilot to switch frequencies and make an initial call. During periods of high traffic, the use of monitor is preferred over contact to reduce radio frequency congestion.
4.4.4 Single runway 30L arrival taxi procedures
Routings are similar to 30L dual runway taxi, however caution should be exercised for traffic vacating onto J2, as this will cross the departure traffic taxiing eastbound on Z. Appropriate coordination shall be used to mitigate the risk of blocking the high speed exit.
Aircraft are also permitted to vacate right onto M and cross 30R at M10A or M5A.
4.4.5 Single runway 30R arrival taxi procedures
Aircraft parking on the southern aprons shall vacate to the left and taxi via L3, L4 or M4 to cross 30L.
Aircraft parking on the northern aprons shall vacate right and take the first appropriate turn onto P.
4.4.6 Dual runway 12L arrival taxi procedures (Arrival Bias)
Aircraft parking on the southern aprons shall vacate 12L onto M9 or M12A and be instructed by AIR to taxi via M to holding points M13B or M14B as appropriate.
Once aircraft have crossed 12R, aircraft will be transferred from AIR to GMC.
Taxi routes to most aprons on the south side will be via K. For aprons B and D, aircraft shall taxi via J2 and then left or right onto J as appropriate.
Aircraft parking on the northern aprons shall vacate 12L onto N6 or N8 and then taxi via N or P as appropriate.
In addition to the standard taxi routings outlined above, a ”bias” mode can be utilised for biasing arrival traffic flow in the Dual runway 12L arrival configuration.
In the arrival bias, arriving traffic may vacate 12L to taxi westbound on M and then southbound on L3 and L4 to enter the C apron. Departing traffic will not interfere with the arrivals as they are prohibited from using any of the runway holding points along taxiway M.
4.4.7 Single runway 12L arrival taxi procedure
Arrival taxi routes during 12L single runway operation shall be the same as 12 dual runway operations.
4.4.8 Single runway 12R arrival taxi procedure
Aircraft parking on the southern aprons shall vacate right and taxi in via K.
Aircraft parking on the northern aprons shall vacate left and taxi via M to cross 12L at M10A.
4.4.9 Stand allocation procedure
Aircraft shall be assigned stands automatically using Ground Radar Plugin Stand Assigner. If this is not possible, aircraft shall manually be assigned a stand in accordance with the following procedure:
| Area | Stand Allocation | Operator |
|---|---|---|
| Concourse A | Stands A1 to A10, D1 to D10 | ACA, QFA, UAE, UAL |
| Concourse B | Stands B14 to B27, F16 to F27 | ACA, QFA, UAE, UAL |
| Concourse C | Stands B1 to B12, F2 to F13 | FDB (Stands: F2, B1 to B10), UAE |
| Concourse D | Stands C48 to C64 | International Operators |
| Apron C (Remote) | Stands C18 to C47 | FDB (Stands: C18 to C23, C27 to C40), International Operators, KAM (Stands: C36 to C40), UAE (Stands: C24 to C40) |
| Apron E (Remote) | Stands E1 to E27 | AXB, FDB, Cargo, low-cost |
| Apron G (Remote) | Stands G1 to G22 | UAE (Overflow) |
| Apron H | Stands H1 to H4 | AUH, DUB |
| Apron Q (Remote) | Stands Q1 to Q11 | FDB |
| Apron S (Remote) | Stands S1 to S15 | UAE (Overflow) |
4.4.10 Stand restrictions
All stands on Apron A and Apron D are up to code F (A380/B747-8) capable, as well as F18 to F22, F27, F12 and F13. All remaining stands are up to heavy (code E) capable except C18 to C23 and B1 to B7 which are up to medium (code C) capable.
4.5 Low visibility operations (LVO)
4.5.1 LVO taxi routes
When LVO is in force, aircraft shall not cross the landing runway as far as practicable.
Aircraft shall only be issued taxi instructions in accordance with the designated LVO taxi routes.
Only designated CAT II/III holding points shall be used during LVO (4.7.2).
4.6 Designated areas of responsibility
4.6.1 GMC positions
Dubai has two GMC positions, GMC 1 and GMC 2.
GMC 1 controls aircraft movements on the following areas and their associated taxiways: - Apron A - Apron B - Apron D - Apron F - Apron G - Apron H
GMC 2 controls aircraft movements on the following areas and their associated taxiways: - Apron C - Apron E - Apron S - Apron Q
(See Section 2)
4.6.2 Handoff procedures
Where transfer of control is to be made between controllers, aircraft shall not be cleared to a point beyond the current controller’s designated zone of responsibility unless there has been prior coordination with the next controller. Intermediate holding points may be used to satisfy this requirement.
4.6.3 Splitting procedure
When there is only one GMC online, they shall cover all surface movement areas from the GMC 1 position.
Unless otherwise authorised by the Arabian vACC staff, GMP (Dubai Delivery) must be online before two GMC (Dubai Ground) positions are be opened.
When GMP is not online, GMC shall assume the responsibility of the lower controller.