Introduction
New Virtual Airline Checklist
Work In Progress!
Documentation is work in progress. If you notice discrepancies between documentation here and reality on vAMSYS, please let us know in Discord so we can fix it.
We are thrilled to have you on board.
Setting up a Virtual Airline on vAMSYS can seem daunting, but we’re here to make the process as easy as possible. Follow the instructions provided, and don’t rush or skip steps (unless you’re already running a VA with us 😄—thank you for creating another VA!). Complete all the items listed to avoid running into problems.
Join our Discord
Before proceeding, your first task is to join our Discord.
We require all VA Owners to be part of our Discord. It’s where we make important announcements, engage in discussions, and where you can ask questions. Discord is our primary means of communication between Team vAMSYS and Virtual Airlines.
Our Discord is open to VA Owners and Staff Members only.
Basic Requirements for Discord Access
To get access to all channels, please ensure you request a nickname change if you haven’t joined with the correct naming scheme. Post a message in #nickname-changes with your username formatted as follows:
Primary VA Owner:
FirstName - VA Identifier - Owner
Example: John - HTB101 - OwnerVA Staff Member:
FirstName - VA Identifier - Staff
Example: John - HTA100 - Staff
Do Not request a nickname change to your Pilot ID. For instance, "Lukas - HTA0002" is incorrect. Many VA Owners and Staff make this mistake—save yourself some embarrassment and avoid being that person.
You can find your VA Identifier in the Orwell Dashboard. 
Team vAMSYS administers ranks to VA Owners. VA Owners are responsible for role management for their Staff.
Now, put this into practice and join the community here.
Checklist
Once you’ve joined our Discord, let's start with the steps you need to take—in the order they are listed (trust us!).
If you haven’t yet, please familiarize yourself with key terms.
Promise yourself that you will not rush. We are not trying to be patronizing, but our experience with many VAs launching using vAMSYS has shown that most issues arise from VA Owners rushing through the process or delegating tasks to their Staff without proper training or instructions. Rest easy—you won’t be adding any routes on Day 1 or making any flights. Take your time to do things right, not fast.