3.0 Event Guest Approvals Policy

Category: Divisional Events Policy | Middle East / North Africa Division Policy

Event Guest Approvals Policy v1.1

October 29th, 2017


Created and edited to v1.0 by Saad Belouafi [29.08.2017].

Edited to v1.1 by Chriss Klosowski [17.012.2019]



Section 1 – VATME Policy Range

This document is the basis for all future & present C1 Controllers. This document aims to provide requirements and operations for events that need ATC support within the Middle East.

This policy follows higher VATSIM rules published here:

For any conflicting rules, the one that is higher than is policy is effective, if not mentioned differently directly by the policy.


1.1     Ratification

This policy is in effect as of the 29th of October 2017.


1.2      Purpose

In an effort to increase activity, the VATME Division Director (VATME1) has created this policy to allow exceptions to certain controllers ("visiting ATC") to control in an area within the VATME division without having formal approvals for the area. This policy takes effect only during events affecting the VATME division and during no other times.

For the purposes of this policy, the term "visiting ATC" differs from the general definition of a "visiting ATC" used in other parts of VATSIM. A "visiting ATC" is any member in the VATME division, resident or visitor, controlling an area that they do not formally have approvals for (i.e. does not have approvals for that vACC on their VATME HQ profile page).


1.3     Description

Visiting ATC meeting the eligibility requirements above are given exceptions in the VATME division to provide ATC services during events for areas that the majority of event traffic will fly through, provided...

  • Approval only during event time (must log off within 30mins after the event ends)
  • Local ATC have priority over any visiting ATC
  • If Local ATC comes online or is available, the visiting ATC must log off


Section 3 - Event Notification

Any events in VATME should involve ALL vACCs that the event will affect (the origin, destination, and any vACCs the traffic will fly through) from the start of planning. The vACC event staff in VATME should make sure to contact any other vACCs in VATME that aircraft will be flying through at least 48 HOURS IN ADVANCE at the latest! The affected vACCs will need to email and let their members know about the event so that local ATC will have a chance to come online.


3.1     Examples

Example 1

An event is occurring between the United Arab Emirates (UAE) vACC and with Hellenic vACC. Majority of the traffic will be flying through Egypt, Saudi Arabia, Bahrain, and UAE vACCs. If any of the 4 vACCs (Egypt, Saudi Arabia, Bahrain, or UAE) does not have enough controllers to provide full-service ATC on any positions, then a visiting ATC may control the position without requiring any approvals or permissions from any other persons.

Example 2

An event is occurring between Indian vACC to Jordan vACC. The majority of the traffic is expected to fly through Oman, Iran, UAE, Bahrain, Saudi Arabia, Kuwait, and Jordan vACCs in VATME. If any of the vACCS in VATME are short on controllers for any of their overflying CTRs then any visiting ATC in VATME may go online on the CTR positions in Oman, Iran, UAE, Bahrain, Saudi Arabia, and Kuwait vACCs OR any position that is needed in Jordan vACC.

Example 3

An event is occurring between Egypt and Bahrain. The majority of the traffic will be flying through Egypt, Saudi Arabia, and Bahrain vACC. A visiting ATC has taken CTR for Saudi Arabia vACC and is currently controlling the position. However, in the middle of the event, an ATC that is approved on the HQ for CTR in Saudi Arabia vACC is available. The visiting ATC must coordinate and release control of the CTR position to the approved CTR ATC. The visiting ATC must then find a different position in the event to take.


3.2     Considerations

A few considerations must be taken for this policy to be effective, organized, and civil...

  • Be kind and courteous to fellow members at all times. Any issues should be referred to this policy or the VATME Division Director.
  • ALWAYS review the proper resources (charts, sector files, and SOPs) for the area that you wish/will be controlling prior to logging online at the position. The vACC websites can be found at https://vatsim.me
  • ALWAYS coordinate before logging on or off a position with any other position that may be affected. NEVER log on directly onto a position. Log on as an observer on the network and first observe the traffic in the area and coordinate with any other ATC in the area over Teamspeak or private chat.
  • VATSIM GRP 4.4.1: "Graduated controller ratings are essential within the VATSIM online environment since on-line ATC shall provide a 'top-down' service and whenever traffic load permits cover for any missing control positions beneath them; this applies to all control positions from CTR down". Hence if you are controlling CTR and have heavy traffic load, however, an aircraft come online at the ground level, priority should be given to traffic at the CTR level.



End of Document