5. Arrivals
5.1 Approach and runway assignment
5.1.1 Initial contact
On initial contact with aircraft, aircraft shall be assigned the arrival runway and expected approach type for the appropriate aerodrome.
If aircraft have not reported receipt of the ATIS information, they must also be passed the current QNH.
Traffic shall also be requested to pass aircraft type if they have not already done so.
5.1.2 Instrument approach
In most cases, the ILS approach is the preferred approach type, however for D-APO operations, aircraft may be issued the visual approach in accordance with the conditions laid down in 5.1.3.
RNAV approaches are also available, however, should not be used unless specifically requested by the pilot, or due to any other reason such as ILS unserviceability.
5.1.3 Visual approach
Visual approaches may be initiated by APP or requested by the pilot. Pilot acceptance of a visual approach means that they will be able to visually maintain safe terrain clearance and accepts responsibility for establishing a safe landing interval behind the preceding aircraft.
A visual approach may be initiated by APP under the following conditions:
- The pilot concurs;
- The pilot reports the preceding aircraft in sight and accepts responsibility to maintain own separation;
- Wherever necessary, a caution of possible wake turbulence has been issued
If minimum wake turbulence separation cannot be maintained, controllers may offer pilots a visual approach, so they may maintain visual/wake turbulence separation from preceding traffic.
Visual approaches shall only be permitted if traffic is arriving straight in from IMPED/VUTEB. They shall not be permitted from the downwind.
5.1.4 Change of runway or approach type
A change of approach type or runway shall not be initiated by the controller within 30 NM of touchdown. Pilot initiated change of approach type/runway is permitted at any time.
5.2 Speed control
5.2.1 General
As far as practicable, aircraft shall be given speeds in compliance with 3.2.2, to maintain separation. Where necessary for separation, speeds within the recommended speed range shall be used, provided the maximum or minimum speeds for the respective segment is not exceeded. To reduce controller workload, aircraft may also be instructed to maintain published speeds on the STAR.
5.2.2 Published and recommended speeds
The speed limits and recommended speeds within different segments of the Dubai CTA is as follows:
Speed range | Recommended/Published speeds | Arrival segment |
---|---|---|
210 - 250 knots | 230 - 250 knots | CTA entry |
190 - 230 knots | 210 knots; maximum for aircraft initiating turn from upwind to downwind leg | Approaching downwind |
180 - 210 knots | 190 knots; this must be enforced before handoff to Dubai Director (FIN) | From downwind to base leg |
170 - 210 knots | 170 - 190 knots | Closing heading to final approach |
160 - 190 knots | 170 - 190 knots | At 10 NM from touchdown |
160 knots | 160 knots | Until 4 NM from |
5.2.3 Deviation from published and recommended speeds
Deviation from the recommended speeds from the downwind onwards is not recommended as the turn radius and turn rate becomes affected and may result in a localiser overshoot. In addition, it affords the controller more time to manage aircraft on the downwind.
For aircraft making a straight-in approach from the initial STAR fix, speed control need not be applied until the aircraft has established on the final approach course, or unless otherwise necessary for separation.
However, it is recommended that traffic is instructed maintain a maximum speed of 190 knots at 10 NM from the landing threshold to ensure approach stabilisation criteria can be met.
High speed may be permitted in the CTA provided the aircraft is not expected to make turns exceeding 30 degrees of course change at any given arrival segment and the traffic level and controller workload permits.
5.3 Final approach sequencing
5.3.1 Final descent
Descent for final approach shall be to the appropriate platform altitude for the respective runway as provided in 5.4.3.
Clearances to descend below the platform altitude are not recommended, however, this may be permitted provided that they are not below the minimum radar manoeuvring altitude for the sector and horizontal separation is assured with other traffic.
Due consideration shall be given to aircraft on opposite downwind legs. Descent clearances to the same level for aircraft on opposite downwind are not recommended to avoid a loss of separation in case of a localiser overshoot.
5.3.2 Sequencing requirements
At all times, it shall be the endeavour of the sequencing sector to maximise runway utilisation by achieving the minimum safe separation between traffic on final approach. Large gaps in the sequence are to be avoided, as this reduces hourly arrival rate.
Notwithstanding the above, minimum traffic separation in the base-to-final segment shall be ensured at all times. Due consideration shall be given to enhanced wake turbulence category, aircraft performance and landing runway when sequencing base-to-final.
Speed control shall be applied in the same manner as provided in 5.2.2.
If separation cannot be maintained, aircraft may be instructed to maintain visual wake turbulence separation if meteorological conditions permit. If this is not possible, aircraft shall be sent around and re-sequenced.
5.3.3 Use of standard headings
Standard 90-degree base-legs and 30-degree intercepts shall be used when vectoring aircraft from the downwind.
5.3.4 Longitudinal separation requirements
5.3.4.1 Single runway operations
At OMSJ and OMDW and when operating in single runway configuration at OMDB, minimum longitudinal separation of 7 NM shall be applied between arriving aircraft unless otherwise coordinated with the appropriate AIR controller.
5.3.4.2 Low-visibility operations
When operating under LVO conditions, minimum longitudinal separation of 7 NM shall always be applied between arriving aircraft.
5.4.4 Platform altitudes
5.4.4.1 Dubai (OMDB)
Traffic establishing on final approach course at Dubai shall be cleared to a level as follows.
The platform altitudes provided below shall be mandatory during all operations.
Arrival runway | Final descent |
---|---|
OMDB 30L | 2000 ft |
OMDB 30R | 3000 ft |
OMDB 12L | 2000 ft |
5.4.4.2 Sharjah (OMSJ)
Traffic establishing on final approach course at Sharjah shall be cleared to a level as follows.
Arrival runway | Final descent |
---|---|
OMSJ 30 | 2000 ft |
OMSJ 12 | 2000 ft |
5.4.4.3 Al Maktoum (OMDW)
Traffic establishing on final approach course at Al Maktoum shall be cleared to a level as follows.
Arrival runway | Final descent |
---|---|
OMDW 30 | 2000 ft |
OMDW 12 | 2000 ft |