Skip to content

Regional Virtual Airline (rVA) Partner Policy

Effective Date: 01 February 2025
Version: 0.1

1. Policy Introduction

This policy outlines how VATSSA can support and collaborate with Regional Virtual Airlines (rVAs) operating within its jurisdiction. It does not replace or supersede VATSIM’s Virtual Airline Associate Policy or VATSIM’s VA Partner Policy.

The purpose of the policy is to:

  • Enhance visibility and establish event-related partnerships for rVAs.
  • Maintain an up-to-date inventory of rVAs, including their owners and key details.
  • Guide rVAs towards becoming VATSIM-partnered entities.

To apply for VATSSA rVA partnership, complete the application form on the VATSSA website. The Virtual Airline Relationship Manager will follow up after submission.

2. Roles and Responsibilities

2.1 VATSSA

VATSSA will appoint a Virtual Airline Relationship Manager, responsible for:

  • Following up on rVA registrations.
  • Maintaining an active inventory of rVAs.
  • Ensuring rVAs meet policy requirements.
  • Coordinating with tech and social teams for displaying rVA information and logos.
  • Coordinating with the events team regarding event benefits.

2.2 Regional Virtual Airline (rVA)

Owners of rVAs must:

  • Register their rVA with VATSSA to apply for Partner status.
  • Inform the VATSSA Relationship Manager of any changes in ownership or registration.
  • Register and maintain rVA Event Managers, if applicable.

Event Managers, once registered, may coordinate rVA events directly with VATSSA’s Event Team.

3. Requirements

For rVA eligibility, the following are required:

  • A unique name distinct from other VATSSA-affiliated rVAs.
  • Provide valid email addresses, full VATSIM registered names, and CIDs for the primary contact, owner, and Event Managers.
  • Notify VATSSA promptly of any email changes.
  • Provide ICAO callsign codes and radio callsign lists used on the network, and update VATSSA if they change.
  • Encourage pilots to fly on VATSIM professionally and abide by the VATSIM Code of Conduct.
  • If the rVA has a website, supply the URL and keep VATSSA updated of additions or changes.

4. Partner Tiers

VATSSA offers three partnership tiers depending on rVA maturity and alignment with VATSSA airspace:

4.1 Tier III – Regional VA (Growing rVAs)

Additional Requirements:

  1. Registered or created at least 90 days prior to application (e.g., via domain or forum creation date).
  2. Completed at least one online VATSIM flight in the past 15 days (proof may be requested).
  3. Main hubs located within VATSSA airspace, with most flights routing through VATSSA. Provide home country and hub information, and notify VATSSA of any changes.

Benefits:

  • Visibility on the VATSSA website and Discord server.
  • Participation in multi-rVA VATSSA-hosted events.

4.2 Tier II – Regional VA (Established rVAs)

Additional Requirements:

  • Minimum of 5 active pilots (each having completed at least one VATSIM flight in the past 30 days).
  • Hubs and home country within VATSSA airspace (as above).

Benefits:

  • Full visibility on the VATSSA website and Discord.
  • Permission to display the VATSSA logo on rVA platforms.
  • Participation in general VATSSA-hosted rVA events.
  • Participation in an annual VATSSA-hosted event dedicated exclusively to the rVA.

4.3 Tier I – Regional VA (Active VATSIM Partner rVAs)

Additional Requirements:

  • Must be an active VATSIM Virtual Airline Partner (VAP).
  • Hubs and home country within VATSSA airspace (as above).

Benefits:

  • Highest visibility on VATSSA website and Discord.
  • VATSSA logo display permission.
  • Participation in general VATSSA-hosted rVA events.
  • Participation in biannual VATSSA-hosted events dedicated exclusively to the rVA.

5. Policy Governance

5.1 Maintenance

This policy must be reviewed and updated:

  • Following significant changes in VATSIM or VATSSA policies.
  • At least annually.

5.2 Audit

Compliance documentation should be maintained, including:

  • Spot checks and archival records of registrations.
  • Quarterly reviews and any required remediation actions.

5.3 Supporting Material

May include:

  • Detailed procedures, guidelines, checklists, flowcharts, or models to aid implementation.

5.4 Distribution

The policy must be:

  • Available on the VATSSA website for all members.
  • Communicated via Discord.

6. Standard References

  • VATSIM’s Virtual Airline Associate Policy
  • VATSIM’s Virtual Airline Partner Policy
  • VATSIM’s Code of Conduct

7. Policy Administration

  • Policy Owner: Miguel Albano, Division Director (VATSSA)
  • Version History:
Version Date Description Author Approver
1.0 01/02/25 Initial Policy Draft Miguel Albano Miguel Albano