Standard Operation Procedures for Arabian Control (OGCC) Pag.1 of 12 Standard Operating Procedures (SOPs) for Arabian Control (OGCC)
Standard Operation Procedures for Arabian Control (OGCC) Pag.2 of 12 Index 1. FOREWORD... 3 2. NEIGHBOUR FIR... 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_W/E_CTR AND NEIGHBOUR _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
Standard Operation Procedures for Arabian Control (OGCC) Pag.3 of 12 1. FOREWORD ATCOs controlling Arabian CACC (Combined ACC) shall be proficient in the local procedures of the covering countries: Bahrain, Kuwait, Qatar and U.A.E. All documents and pages published on the IVAO AE division Arabian Control website what you need to know for the controlling. To be able to control and log on as Arabian Control you need to pass the theoretical and practical checks. 2. NEIGHBOUR FIR Arabian CACC (Combined ACC) is bordering with Iran (Tehran OIIX) at north-east, Oman (Muscat OOMM) at south-east, Saudia Arabia (Jeddah OEJD) at south-west and Iraq (Baghdad ORBB) at north west.
Standard Operation Procedures for Arabian Control (OGCC) Pag.4 of 12 3. ATC UNITS The Arabian Control has 2 ATC Units: Unit providing service Call sign IVAC name Language FIRs/UIRs Frequency Arabian CACC West Sector Arabian CACC East Sector Arabian Control OGCC_W_CTR English OBBB+OKAC 126.700 Arabian Control OGCC_E_CTR English OBBB+OMAE 132.125
Standard Operation Procedures for Arabian Control (OGCC) Pag.5 of 12 4. AREA OF RESPONSIBILITY rmally the area of responsibility are: OGCC_E_CTR controls all traffic that are in the UIR/FIR of Bahrain and UAE, from FL325 1-2 to FL660; OGCC_W_CTR controls all traffic that are in the UIR/FIR of Bahrain and Kuwait, from FL325 1-2 to FL660. 1 If no ACC online from the listed FIRs above it s responsible from GND-FL660 in that FIR, plus all traffic that operate in Qatar airspace. 2 If during a session someone connect as Bahrain control (OBBB_CTR), or UAE centre (OMAE_CTR), the Arabian control is responsible from FL325 to FL660 in those countries where is ACC connected. 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 to connect as Arabian control the user must check which ACC are online and in function of this situation the controller can choose which Arabian control sector can be opened. It s not possible to have both Arabian control sectors online. So, as first the user must check if there is other controller connected as Arabian control. If during a session, someone connect as Kuwait Center (OKAC_CTR) isn t possible to still online as OGCC_W_CTR. In this case the controller can choose to connect, or OGCC_E_CTR, or as Bahrain center (OBBB_CTR). 6. GENERAL REQUIREMENTS You need to be: at least APC, member of any covered country (Bahrain, Kuwait, Qatar, U.A.E) or you have GCA for ACC the above listed countries for at least 1 month. You need to make a course with checkout at the final. If you meet the requirements you must request a training using our tool: http://www.ivaoae.com/tools/atctraining/, after that you ll contact by a member of training department in order to do these following phases: 1. Theoretical exam via our system. This exam is an easy online quiz with 8 randomly selected questions. The arguments of questions are about local procedures. The minimum rate to pass the exam is 62%. 2. After your passed theoretical exam your assigned trainer contact you for the Practical Training. You need to give 3 dates when you re available to do it in the next 30 days. After 7 day without reply the training department cancels the training. If you don t come up on the training/checkout and you don t have a valid reason we cancel your request and block you for a month to request training for this level. The applicants need to have at least 1 online session before the checkout. To validate the checkout we need 15-20 traffic at all and maximum 2 hours can be the duration. The Practical trainings are suggested to do them on weekends to have enough traffic (Friday-Saturday-Sunday) 3. After the passed Practical Training(s) comes the Checkout. The checkout shall be on weekend to catch the enough traffic (Friday-Saturday-Sunday) in special cases TC/TAC or AE- HQ can give exceptions on request. The maximum duration is 2 hours and the required
Standard Operation Procedures for Arabian Control (OGCC) Pag.6 of 12 traffic amount is 15. The applicant needs to control east or west sector of Arabian control, so, or OGCC_E_CTR, or OGCC_W_CTR. If the applicant choose OGCC_W_CTR, Kuwait and Bahrain ACCs must be offline, otherwise, if he choose OGCC_E_CTR, Bahrain, and UAE ACCs must be offline. tes: 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 a month to request another checkout. Exceptions can be given in special cases by TC/TAC or AE-HQ 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 3F, will be inserted DAR 3F). 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.
Standard Operation Procedures for Arabian Control (OGCC) Pag.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 Emirates + Bahrain + Kuwait FIR SFC/4500 FT Class : G IFR/VFR Emirates + Bahrain + Kuwait UIR FL145 / UNL Class : A Only IFR Type of traffic permitted
Standard Operation Procedures for Arabian Control (OGCC) Pag.8 of 12 10. ATS Airspace classification Airspace classes used in UAE, Bahrain, Qatar Class Type of Flight Separation provided Service Provided VMC visibility and distance from cloud minima Speed limitation A IFR only All aircraft Air traffic control service t applicable t applicable B C D IFR All aircraft Air traffic control service t applicable t applicable VFR All aircraft Air traffic control service IFR VFR IFR VFR IFR from IFR IFR from VFR VFR from IFR IFR from IFR NIL 8 KM at and above 3050 5 KM below 3050 Clear of cloud t applicable Air traffic control service t applicable t applicable 1) Air traffic control service for separation from IFR 2) VFR / VFR traffic information (and traffic avoidance on request) Air traffic control service including traffic information about VFR flights (and traffic avoidance advice on request) IFR / VFR and VFR / VFR traffic information (and traffic avoidance advice on request) 8 KM at and above 3050 5 KM below 3050 1500 M horizontal: 300 M vertical distance from cloud t applicable 8 KM at and above 3050 5KM below 3050 1500 M horizontal: 300 M vertical distance from cloud Radio comm. required ATC clearance
Standard Operation Procedures for Arabian Control (OGCC) 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 F G IFR VFR IFR IFR from IFR NIL IFR from IFR as far as practical Air traffic control service and traffic information about VFR flights as far as practical Traffic information as far as practical Air traffic advisory service, Flight information service VFR NIL Flight information service t applicable 8 KM at and above 3050 5 KM below 3050 1500 M horizontal: 300 M vertical distance from cloud. t applicable IFR NIL Flight information service t applicable VFR NIL Flight information service 8 KM at and above 3050 5 KM below 3050 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 8 KM at and above 3050 5 KM below 3050 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 (10 000 FT) AMSL
NOT AVAILABLE FOR VFR TRAFFIC NOT AVAILABLE FOR VFR TRAFFIC United Arab Emirates Division of IVAO Rev. 1.0 Standard Operation Procedures for Arabian Control (OGCC) Pag.10 of 12 11. SEMI-CIRCULAR FLIGHT LEVEL RULE The AE + KW + BH + 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 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
Standard Operation Procedures for Arabian Control (OGCC) Pag.11 of 12 12. HANDOFF BETWEEN _CTR AND _APP CONTROLLERS The _APP units will normally handle tfc up to his TMA limit/boundary. OGCC_W/E_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_W/E_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 completed 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.8. Voice OR automatic release message are both acceptable. 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. In any time controllers can coordinate about altitudes and fixes. 14. LOA AND CHARTS 14.1. LOA The Letters of agreements are available to download in http://ae.ivao.aero/
Standard Operation Procedures for Arabian Control (OGCC) Pag.12 of 12 14.2. CHARTS The charts needed to control, and are available in AE-IVAO website (http://ae.ivao.aero/), or on the AIPs of the covered countries.