Rules and Etiquette

Flying on VATSIM is a shared experience built on mutual respect and adherence to a common set of rules. Understanding these rules and following proper etiquette will make your time on the network enjoyable for everyone - including yourself.

Violations of the VATSIM Code of Conduct can result in suspension or permanent ban from the network. All members are expected to read and follow the Code of Conduct in full. Ignorance of the rules is not accepted as an excuse.

Code of Conduct

The VATSIM Code of Conduct is the foundational document that governs all member behavior on the network. It covers everything from registration requirements to communication standards and disciplinary procedures. You can read the full document here: VATSIM Code of Conduct Below is a summary of the most important rules that every pilot should know before connecting.

Key Rules

Rule	Details
Real name required	You must register with your real first and last name using English/Latin characters. Nicknames, callsigns, and pseudonyms are not permitted.
One connection at a time	You may only be connected to VATSIM with one account and one callsign at any given time.
No unattended connections	If you are away from your computer for more than 30 minutes, you must disconnect from the network.
No unauthorized military callsigns	Military callsigns and operations are restricted to approved virtual military organizations.
English proficiency required	All pilots must be able to communicate in English on the network. Local languages may be used between consenting parties, but English is the fallback.
Minimum age of 16	You must be at least 16 years old to register for a VATSIM account. Members aged 13-15 may register with parental consent.
No interfering with others	Intentionally disrupting other members’ flights, blocking runways, or harassing controllers or pilots is strictly prohibited.
Follow ATC instructions	When ATC is online, you must follow their instructions unless doing so would be unsafe or impossible in your simulator.

Etiquette Best Practices

Beyond the formal rules, there are unwritten expectations that experienced VATSIM members follow. These make the network run smoothly and keep the experience enjoyable for everyone.

Be patient with ATC

Controllers on VATSIM are unpaid volunteers who donate their time to provide services. They may be students learning their craft or experienced controllers handling heavy traffic. If a controller takes a moment to respond, be patient. If they make a mistake, be understanding. A polite attitude goes a long way.

Do not frequency hop between controllers

Once you have been assigned to a controller, stay on their frequency until they hand you off to the next controller. Do not switch frequencies on your own to talk to a different controller unless instructed to do so. If you need to leave a frequency, let the controller know.

Do not request specific runways unless operationally needed

Active runways are determined by the controller based on wind direction, traffic flow, and other factors. Requesting a specific runway because you prefer it or because it is closer to your gate is generally frowned upon. Only request a runway change if you have an operational reason, such as a performance limitation.

Be prepared before contacting ATC

Before keying up your microphone, know what you want to say. Have your flight plan filed, your ATIS information noted, and your callsign ready. Controllers handle many pilots at once, and concise, prepared communication keeps things moving efficiently.

Use text if voice is not available

If you do not have a microphone or are in a situation where you cannot use voice, you can communicate with ATC via text. Add “T/” to your flight plan remarks to indicate you are text-only. Controllers will accommodate you, but voice communication is strongly preferred.

Never spawn on active runways or taxiways

Always start your flight at a gate, parking stand, or ramp area. Spawning on a runway or taxiway can cause conflicts with other pilots who are landing or taxiing. If your simulator places you on a runway by default, reposition to a gate before connecting to VATSIM.

Do not transmit on Guard (121.5)

Unlike in real-world aviation, the Guard frequency (121.5 MHz) is not actively used on VATSIM. Do not transmit on it. If you need to reach a controller, use the correct facility frequency listed in your pilot client or on tools like VATSpy.

Common Mistakes to Avoid

Every VATSIM pilot makes mistakes early on. The table below covers the most frequent ones and how to handle them properly.

Mistake	Why It Is a Problem	What to Do Instead
Flying a heavy aircraft (A380, 747) at a tiny airport	These aircraft cannot realistically operate at small airports. It breaks immersion and can block taxiways not designed for them.	Match your aircraft to the airport. Check real-world operations to see what aircraft types actually serve a given airport.
Not filing a flight plan	ATC cannot provide proper service without a flight plan, especially for IFR flights. You may be asked to disconnect or file one before proceeding.	Always file a flight plan before connecting, using SimBrief or the VATSIM prefile system.
Saying “any traffic in the area” on UNICOM	UNICOM (122.800) is for position announcements, not open-ended queries. This phrase has no standard meaning on VATSIM.	Announce your position and intentions clearly. For example: “Toronto Pearson traffic, ACA456, taxiing to runway 05, UNICOM.”
Connecting to VATSIM while on a runway	Other pilots may be on approach or landing. Appearing on an active runway can cause a conflict.	Always connect at a gate or parking position. Reposition your aircraft if needed before connecting.
Not reading back clearances	Controllers need to confirm you received the correct information. Failing to read back critical items can lead to misunderstandings.	Read back all altitude assignments, headings, runway assignments, squawk codes, and frequency changes.
Using an incorrect callsign format	Random or improperly formatted callsigns confuse ATC and other pilots.	Use your airline’s ICAO code plus flight number (e.g., ACA456) or a valid general aviation registration (e.g., C-GABC).

Add “RMK/NEW TO VATSIM” in your flight plan remarks field. Controllers will see this and will be more patient and helpful with you. There is no shame in being new - everyone started somewhere.

If you make a mistake on frequency, simply say “Correction” and try again. Controllers deal with mistakes regularly and will not judge you for it. The important thing is to correct yourself calmly and move on.

Introduction

Getting Connected

Pilot Clients

Communication & ATC

Advanced Operations

Resources

Code of Conduct

Key Rules

Etiquette Best Practices

Common Mistakes to Avoid

​Code of Conduct

​Key Rules

​Etiquette Best Practices

​Common Mistakes to Avoid

Code of Conduct

Key Rules

Etiquette Best Practices

Common Mistakes to Avoid