Before considering any flight on the VATSIM network, you must be able to:
handle your aircraft properly (heading, altitude, speed — indicated airspeed or Mach number)
know how to fly an ILS, RNP (or even VOR) or visual approach
know how to set your radio panel to tune a frequency
Those are the really basics.
VATSIM Learning Center is a good first place to build your theoretical foundations.
Don't forget those 10 golden rules:
| Number | Golden Rule |
|---|---|
| 1 | Aviate, Navigate, Communicate |
| 2 | Ask a question if unsure ! |
| 3 | Maintain a positive and supportive attitude |
| 4 | Remain vigilant of other nearby traffic |
| 5 | Use good radio etiquette |
| 6 | Be familiar with how to fly your aircraft and intervene when necessary |
| 7 | Think ahead of the aircraft. What is next? |
| 8 | Follow instructions and clearances from ATC |
| 9 | Review procedures and use applicable charts while flying |
| 10 | Have fun! |
Phraseology can seem intimidating at first. Before flying on the network, take the time to familiarize yourself with a phraseology manual so you know what to say in common situations: clearance request, taxi, takeoff, approach, landing, and so on. You are expected to know the basics of radio communication and phraseology.
See the SIA phraseology manual: https://www.sia.aviation-civile.gouv.fr/reglementation
We also strongly recommend this very comprehensive video by AviationPro :
Feel free to browse their Youtube channel, as it contains a great deal of content.
Yes, it is essential: both for you as a pilot and to make the controller’s job easier. It will allow you to depart from and arrive at your airport in the most efficient way possible. We therefore recommend that you understand and know how to follow standard departure procedures (SID) and standard arrival procedures (STAR), as well as the initial altitude or flight level assigned to you.
Setting your transponder to Mode C will allow all the necessary information to appear on the controller’s radar: altitude, speed, and your aircraft callsign. Indeed, if your transponder is in standby mode (or OFF, if you prefer), this information will not appear on the radar, making it very difficult for the controller to issue instructions to you.
With the exception of a few airports, whose exceptions do not make the rule, you may assume that your transponder should be set to:
Whether by text or by voice:
Pay in mind, French is a comfort for native people. Not an obligation. English is still the default language on the network, no matter what.
Your client (e.g: xPilot, vPilot, Swift) shoud be properly setup, specifically on below points:
your mic configuration (emitting / receiving / general volumes / PTT (push to talk key))
your VATSIM identity (VATSIM CID + password + your identity*)
About your identity, as per A4b Code of Conduct article, you must choose one of these 5 options, exclusively :
Choose a plausible callsign (take inspiration from real flights or a flight tracker; e.g. for IFR flights: AFRxxx or AFRxxxx, and for VFR flights: Fxxxx).
Whether ATC is online or not, never spawn on a runway, whether it is active or inactive. Spawn at a gate or a parking stand instead.
On VATSIM, filling a flithplan if you are flying IFR is mandatory.
For a VFR flight, filing a flight plan remains optional, but it is still greatly appreciated by VATSIM controllers because it helps them anticipate your intentions and place your route within the airspace under their responsibility based on the expected traffic situation.
No. For IFR flights, choose a cruising level that complies with the French airspace semi-circular rule and the associated parity rules.
In the remarks section of your flight plan, you may include useful information for the controller (beginner / first flight / please speak English slowly / AIRAC cycle / simulator, etc.).
Always respond to a controller’s “Contact me”, either by voice or by text (even if you think they are mistaken).
When tuning to a new frequency, wait a few seconds before transmitting so as not to interrupt an ongoing exchange between the controller and another pilot.
Use of the UNICOM frequency (122.800) is reserved for aeronautical information exchanges so that you can report your intentions and be aware of those of others (takeoff, landing, runway in use, etc.).
You should not use UNICOM to chat about unrelated matters, whether by voice or text. If needed, send a private message to the other person using the following command:
.msg [station] [your message]
Then press "Enter" to send the message.
Example:
.msg AFR48C Hello ! Confirm you will plan runway 22 for departure?
Controllers are grouped by rating, depending on the scope of their responsibility:
Moving from one rating to another is made possible by passing a practical examination on the network (CPT: Controller Practical Test). To train with greater autonomy, the student controller, just like in PPL (Private Pilot Licence) training, goes through a solo release phase during which they may control their training platform independently for a defined period of time.
Each controller on VATSIM normally provides a top-down service: a higher position covers the duties of lower positions when those lower positions are not open.
Example: if an approach controller is online, they also provide tower and ground services.
In exceptional circumstances, a controller may reduce the scope of their service or no longer provide certain lower-level services, especially depending on traffic load.
Example: a center controller may decide not to handle traffic patterns at an aerodrome that still falls within their area of responsibility.
You can always check the network status, see which controllers are online, confirm your own presence on the network, and verify that your flight plan has been filed correctly using tools such as VATSPY, SIMAWARE, VATSCOPE, or others.
We recommend using VATSIM Radar, which is actively maintained and supported by VATSIM : https://vatsim-radar.com/
If you are unsure, do not hesitate to contact the relevant controller to ask whether you are within their area of responsibility or whether they are able to provide any service.
Make sure not to block the frequency with your push-to-talk (PTT) stuck transmitting (this can notably happen when you switch screens or “tab out” of your application).
In the event of a connection loss (without a simulator crash), you may reasonably reconnect within the next 2 minutes, generally without issue.
In the event of a simulator crash, if you have an autosave, you may of course reconnect, but common sense requires that you first check carefully whether there is too much nearby traffic.
Indeed, restarting a simulator and reloading a saved situation often takes 2–3 minutes, and at best you will reappear at the point where you crashed. Traffic following you will most likely already have reached your position, and reconnecting may therefore create a conflict and disrupt the sequence previously established by the controller.
If you are a beginner, start by flying from smaller or less busy airports.
Do not depart from London Gatwick if you are not familiar with the specifics of English procedures and phraseology, if you are flying in text and English is not your language, or if you do not know how to program and fly holding patterns. he same applies to LFPG (and Paris TMA in general due to its complexity)
You may connect at a parking stand and remain stationary simply to listen to the frequency, so you can become familiar with the communications and what is expected from you.
During an active control session, the controller may be able to give you some guidance, but assume they will not necessarily have the time to give you their full attention to help with connection client settings, finding an appropriate flight plan, FMC setup, and similar matters.
On VATSIM, Paris Charles de Gaulle Approach (LFPG_APP) also provides approach service for Le Bourget (LFPB), Orly (LFPO), and sometimes even Beauvais (LFOB).
Example: If you are departing from LFPO and LFPG_APP is online, you are expected to request your clearance from LFPG_APP.
No VFR allowed at Paris Charles de Gaulle (LFPG) and Orly (LFPO).
If you want to fly VFR in the Paris area, use satellite airfields such as Lognes (LFPL) or Paris-Saclay-Versailles (LFPN) instead.
Make sure you are familiar with the airspace. Paris area is not easy for VFR flights.
If you need to leave the cockpit for a few minutes while in flight, ask the controller first.
That way, their call will not go unanswered while you are away on a toilet break
Set up your simulator so that, at all times, you remain above the low-FPS warning threshold, which is around 20 FPS (especially when approaching major airports, where scenery and traffic density are higher).
When your FPS drops and your simulator starts lagging, your aircraft will also appear to move more slowly on the controller’s radar screen. This makes it more difficult to fit you properly into an arrival or departure sequence.
Otherwise, you will be disconnected automatically. You may reconnect, but keep in mind that this will erase part of the information the controller had previously assigned to your label.