Membership Policy
Policy Information
Control Details
| Type | Policy |
| Revision | 03/2025 |
| Effective Date | 12 SEP 2025 |
| Prepared by | Ian Bijl - ACCARB6 |
| Approved by | Chriss Klosowski - ACCARB1 |
| Next review date | 12 SEP 2026 |
| Cancelled documents | N/A |
Record of Revisions
| Revision Number | Notes | Effective Date |
|---|---|---|
| 01/2020 | Initial Issue | 27 JUL 2020 |
| 02/2020 | Document formatting and ordering have been revised, The definition of "good standing" has been added, The general visiting controller policy has been amended, granting staff the right to remove a visiting member, The requirement for applying as a visiting controller has been updated to S3 or higher only, The process for regaining status after removal from the ATC roster has been amended. Sign-offs will be revoked after the first instance of approval revocation. |
26 AUG 2020 |
| 03/2020 | The term "resident" has been updated to "home", The format has been revised. |
30 SEP 2020 |
| 01/2021 | Initial issue for 2021, Section 1.1.5: Added visiting controller airport activity restrictions, Section 1.1.6: Added visiting controller check-out requirement, Section 1.2.3: Added transferring controller check-out requirement. |
05 JAN 2021 |
| 02/2021 | Major changes to Section 1.2: Transferring controllers, with a new process aligned with VATMENA policy. | 01 APR 2021 |
| 10/2021 | Changes to Section 1.1.1: General visiting controller policy, Changes to Section 2.1: Controller inactivity. |
01 OCT 2021 |
| 01/2025 | Full policy rewrite to ensure full compliance with VATSIM’s Global Controller Administration Policy (GCAP), Transfer & Visiting Controller Policy, and VATMENA Divisional Policies, Removed Emirates vACC branding and updated to align with the new Arabian vACC branding, including the addition of two additional FIRs. |
10 APR 2025 |
| 02/2025 | Added references to Tier 1 standarised training as defined in the Arabian vACC Training Policy | 18 AUG 2025 |
| 03/2025 | Additions to policy, such as: Clauses for easier referring, Controller conduct policy Dispute and reporting, Event policy, Rewrite of Controller Activity Requirement Standard calender quarters |
12 SEP 2025 |
Organization
The Arabian Virtual Area Control Center (hereinafter referred to as Arabian vACC or ARBvACC) is a recognized subdivision within the Middle East & North Africa Division (VATMENA), operating under the Europe, Middle East, and Africa Region (VATEMEA) of the VATSIM Network.
The Arabian vACC is responsible for the provision, management, and facilitation of Air Traffic Control (ATC) services on the VATSIM network across the airspaces of Oman, Qatar, and the United Arab Emirates. These services are delivered in accordance with the vACC's guiding values of #ClearVision and #ClearMission, aiming to uphold a high standard of realism and operational excellence.
As part of its core responsibilities, the Arabian vACC oversees the training and certification of controllers operating within the Muscat FIR (OOMM), Doha FIR (OTDF), and U.A.E FIR (OMAE).
All members of VATSIM are expected to comply with the VATSIM Code of Conduct and Code of Regulations, which serve as the foundational rules governing behavior and operations across the network.
1. Controller Membership
1.1 Transferring Controllers
A transferring controller is defined as a VATSIM member seeking a permanent reassignment from their current vACC to the Arabian vACC. The following conditions apply:
- The controller may hold any ATC rating.
- A minimum of 50 hours of controlling must be logged at the current vACC before applying.
- The controller must have completed any rating upgrade or previous transfer at least 90 days prior to the new transfer request.
- The controller must agree to and comply with the Arabian vACC ATC Training Policy upon acceptance.
- All transfers must conform to the VATSIM Transfer and Visiting Controller Policy (TVCP) and the VATMENA Membership Policy.
To initiate a transfer request, please refer to the official guide:
This guide outlines the required steps and documentation for a successful transfer application.
1.2 Visting Controllers
A visiting controller is a VATSIM member who retains their primary home vACC but wishes to control within the Arabian vACC on an occasional basis. Visiting controllers must meet the following criteria:
- Applicants must possess an S2 ATC rating for VATMENA residents or an S3 ATC rating for non-VATMENA residents, in compliance with the VATSIM Global Controller Administration Policy (GCAP) and VATSIM Transfer Visiting Controller Policy (TVCP).
- Must comply with the Arabian vACC Training Policy and operational procedures.
- Acceptance is subject to staff discretion and space availability.
To apply as a visitor, please consult the official visiting controller guide:
👉 Applying as a Visiting Controller
This guide provides step-by-step instructions for submitting your application and preparing for operations within the Arabian vACC.
1.3 VATMENA Transfer and Visiting Policy Alignment
The Arabian vACC abides by Sections 7, 8, and 9 of the VATMENA Membership Policy regarding all inbound transfer and visiting controller requests. Please note:
- Transfer controllers are not considered full division members until all onboarding and training requirements have been met.
- Visiting controllers will not be added to the Arabian vACC ATC roster until all initial approvals and training prerequisites are fulfilled.
2. Controller Activity Requirements
2.1 Maintaining currency
To maintain a high level of operational readiness and service, all controllers assigned to the Arabian vACC are required to meet the following minimum quarterly activity threshold:
| Category | Hours Requirement | Notes |
|---|---|---|
| Unrestricted | Minimum of 3 hours per quarter in highest approved position | Hours do not count towards Tier 1 hour requirement |
| Tier 1 | Minimum of 3 hours per quarter in highest approved position | Hours count towards unrestricted total |
-
Hours controlled on a Tier 2 facility only count towards restricted hours, and as such do not count for the Tier 1 requirement.
-
Sessions below 30 minutes are also not counted towards your monthly requirement, as per the operations policy.
Calendar quarter are those as defined in the Arabian vACC Membership Policy, clause 7.
This activity requirement supports the Arabian vACC's core values of #ClearVision and #ClearMission, ensuring service consistency and procedural compliance with GCAP policy 9.4(c)(i) and divisional policy VATMENA_POL_TRP_R01-2025.
2.2 Non-Compliance and Roster Removals
Controllers who fail to meet the quarterly activity requirement will be:
- Removed from the Arabian vACC roster;
- Have all endorsements and position approvals revoked.
Roster cleanups are conducted on the final day of March, June, September, and December. A general notice will be issued on the Arabian vACC Discord server 2 to 4 weeks in advance.
2.3 Leave of Absence (LoA)
Controllers may request a Leave of Absence (LoA) if unable to meet activity requirements. The following conditions apply:
| Step / Topic | Details |
|---|---|
| Submission | Submit a support ticket via the Arabian vACC Discord, titled "Leave of Absence Request" |
| Reason | Provide a valid reason for the request. Approval is subject to staff discretion. |
| Duration | LoA duration: up to 90 days, with one renewal allowed unless extended by written approval from the Membership Director or designee. |
| Activity Requirement | Controllers on LoA are exempt from the activity requirement and will be marked as “Not Approved” on the roster. |
| Revocation | If a controller is found actively controlling on the network during their LoA, the leave will be immediately revoked. |
Controllers may cancel or modify their LoA by notifying the Membership Department. Upon completion, the controller will return to their previously approved status. A recurrency session may be required if the LoA was extended.
3. Reinstatement to Roster
3.1 Resident Controllers
Resident controllers removed from the roster due to inactivity may request reinstatement to the controller roster. This is done by submitting a support ticket via Discord. Once accepted for reinstatement, they shall follow the process as defined in the Arabian vACC Training Policy "Reinstatement to Roster" section.
3.2 Visiting Controllers
Visiting controllers removed from the roster for inactivity or other reasons (such as disciplinary or failure to meet competency requirements) may reapply after a minimum of 30 days. This is done by submitting a support ticket via Discord. Once accepted for reinstatement, they shall follow the process as defined in the Arabian vACC Training Policy "Reinstatement to Roster" section.
3.3 Exemptions:
- New visiting controllers actively engaged in training are exempt from the quarterly activity requirement.
- Visiting controllers approved within the current quarter are also exempt.
4. Controller Conduct
Controllers in the Arabian vACC must uphold professionalism and adhere to the following standards:
-
Adherence to VATSIM Regulations Controllers must comply with the VATSIM Code of Conduct and Code of Regulations.
-
Good Standing Requirement Controllers must remain in good standing with the Arabian vACC, VATMENA, VATEMEA, and the VATSIM network.
-
Violation Consequences Controllers found violating the VATSIM Code of Conduct, regardless of role (controller, pilot, or observer), will be immediately removed from the Arabian vACC roster. No prior notice will be given for such removal.
-
Compliance with Policies and Procedures Controllers must comply with all applicable Arabian vACC standards, policies, and procedures, including:
| The Arabian vACC Training System |
| SOPs (Standard Operating Procedures) |
| vMATS (Virtual Manual of Air Traffic Services) |
| Operational Changes |
| Letters of Agreement (LoAs) |
4.1 Zero Tolerance for Misconduct
Hate speech, violence, derogatory remarks, or personal attacks directed at pilots or fellow controllers will result in immediate and permanent removal from the Arabian vACC, with further reporting to the VATSIM network.
4.2 Conduct within the network
Additionally, any resident of the Arabian vACC personally represents our morals and values. As such, it is in no way accepted for our residents to speak ill towards any controller or vACC, even outside of our own scope.
If these issues are reported by any member of the Vatsim network, you will initially receive a formal warning. Any subsequent behaviour will result in immediate termination from the roster and an escelation to the division.
Failure to comply with the conduct guidelines may lead to disciplinary action, including removal of controlling privileges.
5. Disputes and Reporting
5.1 Reporting Issues
Controllers can report non-compliance via this form.
5.2 Conflict Resolution Process
If the feedback form does not sufficiently address the issue, controllers should first contact the vACC Membership Director by submitting a membership ticket. The ticket should follow the format below:
| Item | Description |
|---|---|
| Conflict With | [Name and CID of the individual involved] |
| Describe Conflict | [Brief summary of the issue] |
| Evidence | [Relevant screenshots, logs, or supporting documentation] |
If the issue remains unresolved after this step, it should be referred to the vACC Director or Deputy Director for informal mediation. Should the matter still not be resolved, it may be escalated to the Division Director or the Division Conflict Resolution Manager (DCRM) for further action.
6. Events
Membership works directly with Marketing to ensure compliance with all relevant policies and to identify opportunities for improving event controller quality and attendance:
6.1 Cancellations and No-Shows
All cancellations and no-shows for events are recorded. Controllers should only sign up for an event if they can commit to attending. In unavoidable circumstances, controllers must notify the Marketing Department as soon as possible using both of the methods below: * Notify the person responsible for rostering
| Post in the signup forum on Discord |
| Submit a Support Ticket to the Marketing Department |
- Update the original availability post
| Use strikethrough text to indicate the change and avoid confusion. |
7. Calender Quarters
| Quarter | Months Covered |
|---|---|
| Q1 | January – March |
| Q2 | April – June |
| Q3 | July – September |
| Q4 | October – December |
8. Non-compliance with this Policy
Ignorance of policies is not an acceptable defense. It is each member’s responsibility to stay informed of the latest procedures. Repeated violations will result in the revocation of approvals.