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 standardised 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 calendar quarters |
12 SEP 2025 |
1. 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 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), 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 behaviour and operations across the network.
2. Controller Membership
2.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.
2.2 Visiting 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 GCAP and TVCP.
- Must comply with the Arabian vACC Training Policy and operational procedures.
- Acceptance is subject to staff discretion and space availability.
Guide link:
👉 Applying as a Visiting Controller
2.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.
- Transfer controllers are not full division members until onboarding steps are completed.
- Visiting controllers are not added to the ATC roster until all approvals and prerequisites are fulfilled.
3. Controller Activity Requirements
3.1 Maintaining Currency
To maintain operational readiness, all controllers assigned to the Arabian vACC must meet the following minimum quarterly activity requirement:
| 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 |
Additional rules:
- Hours on Tier 2 facilities only apply to restricted hours (not Tier 1).
- Sessions under 30 minutes do not count.
Calendar quarters are defined in Membership Policy clause 7.
This supports #ClearVision and #ClearMission and complies with GCAP 9.4(c)(i) and VATMENA Policy.
3.2 Non-Compliance and Roster Removals
Controllers failing to meet quarterly activity will:
- Be removed from the Arabian vACC roster
- Have all endorsements and approvals revoked
Roster clean-ups occur the last day of March, June, September, December with advance notice on Discord.
3.3 Leave of Absence (LoA)
Controllers may request an LoA if unable to meet requirements.
| Step / Topic | Details |
|---|---|
| Submission | Submit Discord support ticket titled "Leave of Absence Request" |
| Reason | Valid reason required; approval discretionary |
| Duration | Up to 90 days; one renewal allowed unless extended |
| Activity Requirement | Exempt during LoA; marked as “Not Approved” |
| Revocation | LoA revoked if controlling on the network during approved leave |
Controllers may cancel or modify LoA by notifying Membership. A recurrency session may be required after extended leave.
4. Reinstatement to Roster
4.1 Resident Controllers
Removed residents may request reinstatement via Discord support ticket and must follow Training Policy reinstatement procedures.
4.2 Visiting Controllers
Removed visiting controllers may reapply after 30 days via Discord ticket, following Training Policy reinstatement procedures.
4.3 Exemptions
- New visiting controllers in training are exempt
- Visiting controllers approved within the current quarter are exempt
5. Controller Conduct
Controllers must uphold professionalism and comply with:
- VATSIM Code of Conduct
- VATSIM Code of Regulations
- vACC Training System
- SOPs
- vMATS
- Operational Changes
- LoAs
Violations may lead to immediate removal without notice.
5.1 Zero Tolerance for Misconduct
Any hate speech, violence, derogatory remarks, or personal attacks result in immediate permanent removal and reporting to VATSIM.
5.2 Conduct Within the Network
Residents represent the vACC everywhere. Speaking ill of any vACC or controller is prohibited.
- First offence → formal warning
- Second offence → immediate removal + escalation
6. Disputes and Reporting
6.1 Reporting Issues
Submit issues via:
https://vats.im/arb/feedback
6.2 Conflict Resolution Process
If unresolved via form, submit a membership ticket using this format:
| Item | Description |
|---|---|
| Conflict With | [Name + CID] |
| Describe Conflict | [Summary] |
| Evidence | [Screenshots/logs] |
Escalation order:
Membership Director → vACC Director / Deputy Director → DCRM / Division Director
7. Events
Membership works with Marketing on controller quality and attendance.
7.1 Cancellations and No-Shows
All cancellations/no-shows are recorded. Controllers must notify Marketing using:
- Post in signup forum
- Submit Support Ticket to Marketing
Also update your original availability post with strikethrough.
8. Calendar Quarters
| Quarter | Months |
|---|---|
| Q1 | Jan–Mar |
| Q2 | Apr–Jun |
| Q3 | Jul–Sep |
| Q4 | Oct–Dec |
9. Non-Compliance with this Policy
Ignorance is not an acceptable defence.
Repeated violations will result in revocation of approvals.