ATC best practices
In case you decide to fly into an area controlled by Air Traffic Control, please read these guidelines. Even though the FlightGear multiplayer experience is not by any means a formal environment, you should still follow them to make the experience enjoyable by everyone.
To know if an area is controlled or booked:
- Check for announced ATC sessions on Lenny's website.
- Check the Pilot List in FlightGear or the Multiplayer map. Usually, controllers:
In case multiple controllers are at the same airport, make sure to contact the appropriate one:
- if you are flying to an airport, contact Approach (or Tower if Approach is not available);
- if you are flying from an airport, contact Delivery; if that position is not present, contact Ground (if available) or, failing that, Tower.
Minimum list of best practices
At a minimum, you should do the following:
- Know your aircraft well! You should be able to take off, land (instrumentally and also visually), maintain an assigned altitude and heading without difficulty.
- Know basic ATC phraseology. The ATC phraseology and ATC Tutorial pages should be enough to get started; if you want to learn more, the Phraseology page on the VATEUD site is a great resource.
- Follow the instructions given by ATC timely and read them back. This will let the ATC know that you have received the clearance and that you understood it completely and correctly.
- Mention your callsign every time you contact ATC.
- Avoid colliding with other players.
- Do not start on runways - start FlightGear without connecting to the multiplayer server, taxi to an unoccupied parking position if necessary, then connect. It's not nice for other players to land and have another aircraft appear on the runway just before touchdown.
- Do not take off/land/cross runways/change altitude or heading unless you have ATC authorization.
- Do not simulate emergencies/squawk 7700 just to land earlier at a busy field.
- If other players are abusive, simply ignore them (open the Pilot List and click on the Ignore button next to their callsign).
Additional best practices
This is not essential, but would be really nice on your part:
- Get updated charts for the areas you are going to fly to and read them. If a controller is following real life procedures, it's better to get an idea of what you should expect.
- Use TerraSync or TerraMaster to get the latest scenery for the area you are flying from/to.
- Contact the controller when you're about 60 NM out from his/her airport (if in flight) or before starting the engines (on ground).
- If both you and the controller are able to use FGCom, use it. This will make communication easier for both of you (and adds realism). Some controllers also use TeamSpeak or Mumble as an alternative to FGCom (that is usually announced when the controller contacts you for the first time).
- If you are using text chat, prefix messages directed to the controller with his/her callsign; the controller will do the same for you. It's a lifesaver in busy areas.
- Use a multiplayer server that's not overloaded to avoid communication delays - use the Multiplayer server status page (,  or ) to select a server that's near you and with a low number of active clients.
- Respect speed restrictions. Don't taxi at more than 20/30 kts and be aware that in most parts of the world you are required not to exceed 250 kts below FL100.
- Disable AI traffic (but leave AI models on).
- If you have planned your flight, consider using Lenny's website to file your flightplan.
- If you are using a recent version of FlightGear (3.2 or later), use the transponder if the controller requests it.
- If you're flying into an uncontrolled area, use the multiplayer chat to advise nearby traffic of your intentions.
- Check the wiki to get more information about the scenery existing at your destination
- Offer voice communication if able; use text chat for initial contact and as a backup.
- Make sure you know phraseology very well.
- Plan your sessions on Lenny's website.
- Be patient and polite - not all pilots know real life procedures. On initial contact, ask them if they do; if not, just give them vectors.
- Get charts for the airspace you're controlling and familiarize with the standard procedures.
- Before asking a pilot if he's "inbound" (flying to your airport), check the heading he's flying to and his current altitude and read his flightstrip to see his destination. Contact him only if:
- his flightstrip mentions he's inbound;
- if no destination is indicated, he must be flying towards the space you're controlling and must be definitely not just overflying.
- Use the flightplan exchange feature as a courtesy to other controllers. At a minimum, fill in the pilot's destination and cruise altitude; if the pilot did not file a flightplan, ask him those data.
- Make sure you know how to handoff aircraft to other ATCs.