ATC best practices

From FlightGear wiki
Revision as of 08:49, 18 February 2014 by Elgaton (talk | contribs) (Added Category:Aviation and Category:Multiplayer to be consistent with the Communications page)
Jump to navigation Jump to search

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.

How do I know if the area is controlled by ATC?

Check the Pilot List in FlightGear or the Multiplayer map. Usually, controllers:

  • have a callsign XXXX_DE, XXXX_GN, XXXX_TW or XXXX_AP (where XXXX is the ICAO code of the airport they are manning);
  • use the OpenRadar, ATC-TOWER, ATC (or similarly named) aircraft.

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:

  1. Know your aircraft well! You should be able to take off, land (instrumentally and also visually), maintain an assigned altitude and heading without difficulty.
  2. 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.
  3. 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.
  4. Mention your callsign every time you contact ATC.
  5. Avoid colliding with other players.
  6. 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.
  7. Do not take off/land/cross runways/change altitude or heading unless you have ATC authorization.
  8. Do not simulate emergencies/squawk 7700 just to land earlier at a busy field.
  9. 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:

  1. 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.
  2. Use TerraSync or TerraMaster to get the latest scenery for the area you are flying from/to.
  3. Contact the controller when you're about 60 NM out from his/her airport (if in flight) or before starting the engines (on ground).
  4. 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).
  5. 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.
  6. Use a multiplayer server that's not overloaded to avoid communication delays - use the Multiplayer server status page ([1], [2] or [3]) to select a server that's near you and with a low number of active clients.
  7. 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.
  8. Disable AI traffic (but leave AI models on).
  9. If you have planned your flight, consider using Lenny's website to file your flightplan.
  10. If you are using a recent version of FlightGear (2.12 or later), use the transponder if the controller requests it.