standard operating procedures (sops) for arabian control … · 2020. 5. 2. ·...

OGCC_SOPs_rev.1.0.docx Created by Matt Torti XG-TC

GULF REGION DIVISION of IVAO (XGCC)

Rev. 1.0 April 2020

Page 1 of 12

Standard Operating Procedures

(SOPs)

for

Arabian Control (OGCC)



Rev. 1.0 April 2020

Page 2 of 12

Index

1. FOREWORD ............................................................................................................................... 3

2. NEIGHBOURING FIRs................................................................................................................ 3

3. ATC UNITS .................................................................................................................................. 4

4. AREA OF RESPONSIBILITY ..............................................................................................................5

5. POLICY ....................................................................................................................................... 5

6. GENERAL REQUIREMENTS ..................................................................................................... 5

7. RECOMMENDATIONS ..................................................................................................... 6

7.1. CONFLICTS OPTIONS .......................................................................................................................6

7.2. USE OF OCA ............................................................................................................................... 6

7.3. USE OF TAGS ....................................................................................................................................6

8. TRANSITION ALTITUDE/LEVEL ................................................................................................ 7

9. FIR/UIR............................................................................................................................. 7

10. ATS Airspace classification ............................................................................................... 8

11. SEMI-CIRCULAR FLIGHT LEVEL RULE ......................................................................................... 10

12. HANDOFF BETWEEN _CTR AND _APP CONTROLLERS ............................................................. 11

13. HANDOFF BETWEEN OGCC_CTR AND Neighbouring CTRs and Lower Centers .................... 11

13.1. TRAFFIC OUTBOUND .......................................................................................................... 11

13.2. TRAFFIC INBOUND .............................................................................................................. 11

13.3. LOWER CENTERS ..............................................................................................................................................................11

14. LOA AND CHARTS ................................................................................................................... 11

14.1. LOA........................................................................................................................................ 11

14.2. CHARTS ................................................................................................................................ 12



Rev. 1.0 April 2020

Page 3 of 12

1. FOREWORD

ATCOs controlling Arabian CACC (Combined ACC) shall be proficient in the local procedures of the

covering countries: Bahrain, Oman, Qatar and U.A.E. All documents and procedures regarding

this complex airspace can be found in this document. Moreover all documentation related to

the single FIR (for example OMAE) can be found on the XG division website.

Before controlling Arabian Control every member will have to obtain an approval, which

consists in a theory and practical test. This test will be done with the XG Training Coordinator

(Matt Torti).

2. NEIGHBOUR FIR

Arabian CACC (Combined ACC) is bordering with Iran (Tehran OIIX) at north-east, Saudia Arabia

(Jeddah OEJD) at south-west and Kuwait (Kuwait OKAC) at north west.



Rev. 1.0 April 2020

Page 4 of 12

3. ATC UNITS

The Arabian Control has 1 single ATC Unit:

Unit providing service

Call sign

IVAC name

Language

FIRs/UIRs

Frequency

Arabian CACC

Sector Arabian Control OGCC_CTR English OBBB+OMAE

+OOMM 132.125



Rev. 1.0 April 2020

Page 5 of 12

4. AREA OF RESPONSIBILITY

Normally the area of responsibility are:

• OGCC_CTR controls all traffic that are in the UIR/FIR of Bahrain, Oman and UAE, from FL3251-2

to FL660; 1 If no ACC online from the listed FIRs above, the OGCC will be responsible from GND-FL660 in that FIR,

plus all traffic that operate in Qatar airspace. 2 If during a session a member decides to connect as Bahrain control (OBBB_CTR), or UAE Control

(OMAE_CTR), the Arabian control is responsible from FL325 to FL660 in those countries where is

ACC connected. Coordination will be a key point should this situation present itself!

In case of absence of APP/TWR/GND controllers the pushback, startup, takeoff, landing, and any

other clearance/instructions required will be given by OGCC controller.

5. POLICY

Before connecting as Arabian Control the user must check which ACC are online.

If there is another ACC online already, the user wanting to open Arabian Control MUST contact

him informing that he will open OGCC and be responsible for traffic above FL325 in his FIR.

Should the ACC controller refuse to do so, please do not connect and send an email to xg-

[email protected] including a screenshot of the chat. Do not take action by yourselves please!

6. GENERAL REQUIREMENTS

You need to be: at least APC and member of any covered country (Bahrain, Oman, Qatar or U.A.E).

The GCA does NOT allow you to open OGCC.

In order to be able to connect on Arabian Control, a theory and practical test needs to be taken with the XG Training Coordinator (XG-TC).

If you meet the requirements you must send an email to [email protected] stating your interest

and request to control OGCC. The Training Department will thereafter evaluate your request

contact you in order to proceed with the testing phase as follows:

1. Theoretical exam via our system. This exam is an easy online quiz with 15 randomly selected

questions. The arguments of questions are about local procedures for all FIRs. The

minimum rate to pass the exam is 72%.

2. After having passed the theoretical test you will proceed to the practical training. You

are required to provide at least 3 dates stating your availability, and it has to be done in

the next 30 days. Should you fail to reply within 7 days your request will be cancelled. If

you don’t show up for the training/checkout and you don’t have a valid reason, we will

cancel your request and block you for 3 months to request training for this level. The

applicants need to have at least 1 online session before the checkout. To validate the

checkout we require at 15-20 traffic and the maximum duration of the session is 2 hours.

3. If you are successful during the practical training(s), the next phase is the Checkout.

mailto:[email protected]:[email protected]:[email protected]



Rev. 1.0 April 2020

Page 6 of 12

Notes:

The maximum duration of the checkout is 2 hours, and the minimum require traffic

amount is 15. The applicant will need to open OGCC_CTR 132.125.

Auto failures are: the loss of separation (min is 5 nm), Vectoring below MRVA and lack knowledge of

LoAs, local procedures.

After 2 failed checkouts (not due to lack of traffic) we block the applicant for 6 months before

he/she can request the next checkout.

Exceptions can be given in special cases by TC/TAC in all stages.

7. RECOMMENDATIONS

7.1. CONFLICTS OPTIONS

It is recommended to select with Conflict Options to these values: 6-7 nm/800ft.

7.2. USE OF OCA

It is recommended using OCA to note on radar screen important information about coordination

such as frequencies, turbulence reports, speed, etc.

7.3. USE OF TAGS

In aircraft labels assigned flight level should always be updated.

For waypoint tags we recommend the following use:

• When cleared to standard arrival routes the controller will insert the last two letters of the

ICAO destination code for aircraft with destination OMxx (e.g. DB, SJ).

• The controller, in according to arrival program, will insert which runway will be use for

landing (e.g. DB-L for Dubai 30L or 12L; DB-R for Dubai 30R or 12R; SJ-30 for Sharjah 30; SJ-

12 for Sharjah 12).

• Only for “direct” to waypoints outside of own sector or out of standard arrival routes the

first three letter of the assigned FIX or navaid will be inserted, or the first three letter of the

fix and the last of the destination for arrival traffic (e.g. DXB-DB).

• For departing traffic DEL/GND/TWR will insert the initial climb (e.g. 040 for OMDB) and SID

in the following format: XXX YY (e.g. SID DARAX 5F, will be inserted DAR5F).

• We suggest not using tags such as FPL RTE, FP ect. which do not provide any useful

information to other units and keep ATCs busy in adding them or removing them.



Rev. 1.0 April 2020

Page 7 of 12

8. TRANSITION ALTITUDE/LEVEL

The transition altitude is always 13000 ft.

The transition level is always 150.

9. FIR/UIR

When no other ACC Online

Units Vertical limits and class

of airspace

Type of traffic permitted

Emirates + Bahrain + Oman FIR SFC/4500 FT Class : G IFR/VFR

Emirates + Bahrain + Oman UIR FL145 / UNL Class : A Only IFR

United Arab Emirates Division of IVAO Rev. 1.0

January 24, 2016

Pag.8 of 12

Standard Operation Procedures for Arabian Control (OGCC)

10. ATS Airspace classification

Airspace classes used in UAE, Bahrain, Oman and Qatar

Class Type of

Flight

Separation

provided Service Provided

VMC visibility and distance from cloud

minima Speed limitation

Radio comm.

required

ATC

clearance

A IFR only All aircraft Air traffic control service Not applicable Not applicable Continuous

two - way Yes

B

IFR All aircraft Air traffic control service Not applicable Not applicable Continuous

two - way Yes

VFR

All aircraft

Air traffic control service

8 KM at and above 3050 M (10000 FT) AMSL

5 KM below 3050 M (10000 FT) AMSL

Clear of cloud

Not applicable

Continuous

two - way

Yes

C

IFR IFR from IFR

IFR from VFR Air traffic control service Not applicable Not applicable

Continuous

two - way Yes

VFR

VFR from IFR

1) Air traffic control service for

separation from IFR

2) VFR / VFR traffic

information (and traffic

avoidance on request)



1500 M horizontal: 300 M vertical distance

from cloud

250 KT IAS below 3050

M (10000 FT) AMSL

Continuous

two - way

Yes

D

IFR

IFR from IFR

Air traffic control service

including traffic information

about VFR flights (and traffic

avoidance advice on request)

Not applicable


M (10000 FT) AMSL

Continuous

two - way

Yes

VFR

NIL

IFR / VFR and VFR / VFR traffic

information (and traffic

avoidance advice on request)


5KM below 3050 M (10000 FT) AMSL


from cloud


M (10000 FT) AMSL

Continuous

two - way

Yes

OGCC_SOPs_rev.1.0.docx


January 24, 2016

Pag.9 of 12


Class Type of

Flight

Separation

provided Service Provided

VMC visibility and distance from cloud

minima Speed limitation

Radio comm.

required

ATC

clearance

E

IFR

IFR from IFR

Air traffic control service and

traffic information about VFR

flights as far as practical

Not applicable


M (10 000 FT) AMSL

Continuous

two - way

Yes

VFR

NIL

Traffic information as far as

practical




from cloud.


M (10000 FT) AMSL

No

No

F

IFR

IFR from IFR

as far as

practical

Air traffic advisory service,

Flight information service

Not applicable


M (10000 FT) AMSL

Continuous

two - way

No

VFR

NIL




1500 M horizontal; 300 M vertical distance

from cloud

At and below 900 M AMSL or 300 M above

terrain whichever is higher - 5 KM**, clear of

cloud and in sight of ground or water


M (10000 FT) AMSL

No

No

G

IFR NIL Flight information service Not applicable 250 KT IAS below 3050

M (10000 FT) AMSL

Continuous

two - way No

VFR

NIL




1500 M horizontal; 300 M vertical distance

from cloud

At and below 900 M AMSL or 300 M above

terrain whichever is higher - 5 KM**, clear of

cloud and in sight of ground or water


M (10000 FT) AMSL

No

No




April 2020

Pag.10 of 12


11. SEMI-CIRCULAR FLIGHT LEVEL RULE

The AE + BH + OM + QA semi-circular flight level rule is conform to ICAO Doc 8168 - OPS, Volume 1,

Part III, Section 1, Chapter 4, so the controller could check if the pilot send a flight plan conform with

following table:

RVSM

(East-West)

180°-359°

(West)

000°-179°

(East)

IFR VFR IFR VFR

1500 ft

2500 ft 3500 ft

4000 ft 4500 ft 5000 ft 5500 ft

6000 ft 6500 ft 7000 ft 7500 ft

8000 ft 8500 ft 9000 ft 9500 ft

10000 ft 10500 ft 11000 ft 11500 ft

12000 ft 12500 ft 13000 ft

NO

T A

VA

ILA

BL

E F

OR

VF

R T

RA

FF

IC

NO

T A

VA

ILA

BL

E F

OR

VF

R T

RA

FF

IC FL 150

FL 160 FL 170

FL 180 FL 190

FL 200 FL 210

FL 220 FL 230

FL 240 FL 250

FL 260 FL 270

FL 280 FL 290

RVSM RVSM

FL 300 FL 310

FL 320 FL 330

FL 340 FL 350

FL 360 FL 370

FL 380 FL 390

FL 400 FL 410

CVSM CVSM

FL 430 FL 450

FL 470 FL 490



April 2020

Pag.11 of 12


12. HANDOFF BETWEEN _CTR AND _APP CONTROLLERS

The _APP units will normally handle traffic up to his TMA limit/boundary . OGCC_CTR will normally

handle traffic from Upper Levels down to the TMA ceiling. Earlier handover is possible on

coordination if traffic and situation allows, in order to guarantee a CONTINUOUS CLIMB/DESCENT to

the traffic. CAUTION with MSA.

Good use of data tag is paramount for a smooth and safe coordination between units.

Standard traffic separation in the all airspace is 5nm horizontally or 1000 feet vertically, with the

exception of DXB and AUH where traffic on final can be separated by 3nm (comply with local SOPs

published).

13. HANDOFF BETWEEN OGCC_CTR AND NEIGHBOUR _CTRS and Lower

Centers

13.1. TRAFFIC OUTBOUND:

Ideally traffic leaving the OGCC CACC should be handed over to the adjacent sector at least 10nm or

3 minute from the boundary. Good coordination (if necessary) has to be done before then. Earlier

handover is possible if traffic and situation allows.

Where no adjacent ATC sector is active, traffic should be instructed that Radar Service is terminated,

sq 2000 and monitor UNICOM 122.800.

It is good practices to give traffic information as far as practicable.

13.2. TRAFFIC INBOUND:

Ideally traffic entering the OGCC CACC Airspace should be assumed and in contact before crossing

the boundary.

If the traffic has an SSR code assigned by adjacent sector, there is no need to change it. Otherwise

standard SSR code published should be assigned via the system

When congestion over the destination airport is foreseen, use of Holding Pattern (see Local

Procedures) is recommended. Ideally the traffic should stay at or above FL150 in the holding, until

the expected approach time is reached. Only when the traffic is cleared to leave the Hold, It shall be

transferred to the _APP unit. Good coordination is paramount. See Standard Holding Speed.

13.3. LOWER CENTERS

The Lower ACCs must give climb max FL320 when OGCC CACC is online, then transfer the plane if the

separation is maintaining and no turns more than 45 degrees approved by OGCC.

The OGCC Controller must give descend to FL330 then transfer to the Lower Center Controller with

the same rules as before.

Controllers can at any time coordinate other altitudes and fixes.



April 2020

Pag.12 of 12


14. LOA AND CHARTS

14.1. LOA

The Letters of agreements are available to download (Link not ready)

14.2. CHARTS

The charts needed to control, and are available on the AIPs of the covered countries.

standard operating procedures (sops) for arabian control … · 2020. 5. 2. ·...

Documents