Systems Check: 0%
Official Standard Operating Procedures (SOPs) for all pilots. Flight standards, scoring, fleet, weather, and network conduct.
Last updated January 21, 2026
All pilots must fly with the same level of realism. These standards ensure ACARS and PIREP integrity.
Strictly 1x (real-time). Time acceleration is prohibited; it corrupts ACARS fuel and timing data.
Forbidden. Use of slew or the "Travel To" feature (e.g. MSFS) will result in automatic flight rejection.
If the sim crashes, the pilot has 15 minutes to restart and reposition the aircraft at the same coordinates/altitude to resume the ACARS log. Beyond that, the flight must be abandoned and resubmitted only if permitted by operations.
Must be done at the gate with engines off. Refueling in the air or with engines running results in automatic PIREP rejection.
When flying on VATSIM or IVAO, pilots represent Virtual Star Alliance. The following is mandatory.
Pilots must use the VA callsign (e.g. NXA101) and never their personal VATSIM/IVAO ID as the primary identification for the flight.
A specific remark is required in the flight plan to promote the VA. Example: OPR/VIRTUAL STAR ALLIANCE - WWW.FLYVASTARALLIANCE.NET
Strictly for intentions (position, intentions). Chatting on 122.8 or equivalent is prohibited to keep frequencies clear.
Pilots must follow all ATC instructions. Receiving a report or sanction from a VATSIM Supervisor or IVAO equivalent can lead to immediate VA suspension.
VATSIM and IVAO require virtual airlines and their pilots to adhere to the following. These are network-mandated requirements in addition to our VA rules.
Pilots must comply with the VATSIM Code of Conduct and/or the IVAO Rules and Regulations at all times when connected. Violations are subject to network action and VA discipline.
By using VATSIM or IVAO, pilots agree to the network's User Agreement and Terms of Service. Virtual Star Alliance expects all members to have read and accepted these before flying under our callsign.
Only use callsigns approved by the network for Virtual Star Alliance (e.g. NXA). Do not fly under our identity with unauthorized or personal-only callsigns when representing the VA.
Impersonating real-world airlines, other users, or ATC is strictly prohibited by both networks and will result in network sanctions and immediate VA suspension or termination.
Pilots must maintain a valid, in-good-standing membership with VATSIM and/or IVAO. Suspended or banned network accounts will result in VA membership review and possible termination.
Pilots should report observed network or VA rule violations to the relevant network (VATSIM/IVAO) as per their procedures, and may also report to Virtual Star Alliance staff for VA-level action.
Flights are scored for landing quality and approach stability. The following defines good vs bad outcomes.
All flights must be stable by 1,000 ft AGL (IMC) or 500 ft AGL (VMC). Criteria: gear down, flaps in landing configuration, and vertical speed not exceeding −1,200 fpm.
Penalties apply for landing without landing lights or failing to retract gear above 1,500 ft AGL.
Pilots must only fly aircraft that their rank and type rating authorize. Operating an aircraft without the appropriate rating results in PIREP rejection and may lead to disciplinary action.
High-fidelity add-ons (e.g. FSLabs, X-Crafts) have certified limits. Our rules reflect those limits.
Pilots must not attempt landings when the crosswind exceeds the aircraft's certified limit (e.g. 33–38 knots for an A320, depending on runway state).
Autoland is permitted only when weather is below CAT I minimums or for designated maintenance test flights. Otherwise, manual landing is required.
Anti-ice and de-icing procedures are required when OAT (Outside Air Temperature) is below 10°C in visible moisture.
To maintain A-to-B realism, your pilot is considered to be at their last landed airport until relocated.
To fly from a different hub or airport, a pilot must "buy" a jumpseat (using virtual currency) or wait a real-time period (e.g. 2 hours) to simulate traveling as a passenger.
Acceptable swaps are clearly defined. Example: if the schedule calls for an A320neo, a pilot may fly the FSLabs A320ceo as an acceptable substitute, but may not substitute a B737 for an A320.