1.1. VATSIM Rules

The VATSIM Code of Regulations and Code of Conduct are designed to maximise everyone's enjoyment of the VATSIM network. Consequently, it is important that you remember the following key points:

• You must provide full and accurate details when registering to VATSIM. If any of your details are incorrect, it is important that you update them as soon as possible via the "Member Services" link on the main VATSIM website.
• You can only have one account with VATSIM. If you have accidentally created another due to a misunderstanding during registration, please inform the central Membership Team via the "Member Services" link on the main VATSIM website.
• You can only connect to the network once, unless you are connecting with an ATIS (Airport Terminal Information Service) facility too. In such instances, if someone is already connected as an ATIS facility, you should not - just 1 per airport. Apart from this, duplicate connections are prohibited.
• You must never give anyone access to your account. If you do, you risk permanent suspension.
• Your controller information in your controller client must not exceed 4 lines (as per www.vatsim.net/EC).
• If you find yourself in online conflict, you should call a supervisor by typing .wallop followed by your message
  • e.g .wallop I am having problems with ABC123. (Note: This does not work in FSInn)
• You should never use the GUARD frequency (121.50). If you are flying in uncontrolled airspace, please tune UNICOM 122.80 .
• A pilot must never simulate a HIJACK (by squawking 7500). Any member doing so will be automatically disconnected from the network.
• You must never control traffic whilst connected as an Observer (OBS).
• An Air Traffic Controller has the right to refuse an emergency aircraft. In such situations, a pilot can either:
  • Disconnect from the network
  • Cancel the emergency and resume normal flight
• Active ATC callsigns are (with reference to VATSIM GRP rating in brackets):
  • Ground Controller (S1) _DEL and _GND
  • Tower Controller (S2) _TWR
  • TMA Controller (S3) _APP and _DEP
  • Enroute Controller (C1) _CTR and _FSS (both radar and non-radar control services)

1.2. The Role and Responsibility of an Air Traffic Controller

We start with the most important:

As a controller, your main task is to separate aircraft. Your responsibility is therefore to make sure no collisions occur. You must at all time avoid any risk of collision.

Now that we have said it in three different ways, we hope that you remember what your main task is.
But there are other tasks as well..

• Prevent collisions between aircraft.
• Prevent collisions between aircraft and ground obstacles on ground.
• Expedite and maintain an orderly flow of air traffic.
• Provide advice and information for safe and efficient conduct of flight.
• Make it as real as it gets and at the same time understand that all involved shall have as fun as possible.

As a controller, you have a good overview over the traffic, but you never know how the situation is inside the cockpit where the pilots sit.
Your responsibility is therefore to the traffic situation.
You are not responsible to how the aircraft is flown. Every pilot has a responsibility for his aircraft.

Sometimes, there is a disagreement between you as a controller and the pilot as to what is the right action in the current situation. Remember that it is the pilot who has final word in these situations.
This doesn't mean that he can fly his aircraft the way he pleases, but rather that you cannot give the pilot an instruction which he or his aircraft is physically unable to perform.
To avoid this kind of conflicts, it is always important to give the reason why unusual instructions are given.

It is very rare that disputes occur in our virtual world. We always try to help each other. If you end up in a dispute anyway, try to remember that we are real people in a virtual world.
If you or anybody else makes a mistake, no lives are at stake.This is the most important difference between real life and the virtual world. Try not to get angry, never argue with anybody, but rather point out the problem in a calm and constructive manner.
The above can be summarized in “common sense” and “humility” - two good characteristics.

If a situation gets unpleasant or hatred, or if a pilot deliberately tries to sabotage our environment, you should try to contact a Supervisor (SUP) or Administrator (ADM).
These people have a responsibility to act in these kind of situations and they are also the only ones who can expel pilots and controllers.

Let's move on from this boring but necessary topic and look closer on your task as a controller.
Apart from separation, you should also give service to the aircraft. Simply said, you should guide the pilots from point A to point B.
The pilots are in a never ending need of current information. They need weather and traffic information etc. It is your responsibility to deliver this information as correctly and quickly as possible.

There is one final task which isn't less important than the others. That is to have fun. We want you to enjoy yourself online VATSIM!

1.3. Controller Functions

One of the most common mistakes made in the VATSIM environment is the misconception of a particular facility's function.
A controller can work in many different roles, where maybe Tower is the most well known. Every role has its own responsibilities and working tasks as described below.
Note that in the online environment we have reduced the number of tasks. In real life there are many more.

A basic summary of what each position does follows below. The usual practice is that a position takes over all of the “lower” when they are unmanned.

Example:
TWR handles all the duties of the position DEL, GND and TWR if none of the “lower” is on-line.
If DEL gets online, then DEL will of course handle DEL and TWR will handle GND and TWR.
Finally (to make things really clear) if GND gets online, then GND handles DEL and GND and TWR only TWR.

Note that some positions require a minimum rating. There may also be stricter local rules that apply for certain controller functions. Please refer to your local vACC for more information.

1.3.1 Clearance Delivery (DEL)

Clearance Delivery gives ATC clearances to the pilot after checking the Flight Plan.
If the Flight Plan contains error it is DEL’s responsibility to correct them before releasing the aircraft.
This function is not often in use online during normal operation, but you might see it on very busy airports and during fly-inns.

1.3.2 Ground (GND)

Ground Control is responsible for exercising general surveillance on the airport movement area - apron.
Ground gives taxi clearances and restrictions. Note however that Ground isn't responsible for the runways, they are tower’s responsibility. When the aircraft is approaching the active runway, Ground hands over to Tower, who “owns” the runways.

If an aircraft needs to cross a runway, (active or inactive) on its way to it’s destination a specific clearance to do so must be obtained. Ground then needs to coordinate with tower to get approval or hand over the aircraft to TWR for that clearance (the first being the preferable).
There are a few airports that have runways that are used as taxi-ways. They are controlled by GND, if this is clearly stated and coordinated between TWR and GND.

1.3.3 Tower (TWR)

Tower is responsible for all take-offs and landings and gives instructions to effect proper sequencing and separation of aircraft for departure.
Tower decides which runways are being used for take-offs and landings depending on wind direction etc. You are also responsible for aircraft on the ground when they are on the runway or are about to cross a runway.

Landing aircraft are handed over to Ground as soon as they leave the runway (or sooner at tower’s discretion)
Departing aircraft are handed over to the next controller when they leave your airspace, which normally means 3000-4500ft. The hand-off can also be done earlier if coordinated between TWR and next controller.

1.3.4 Departure Control (DEP)

Departure Control is responsible for ensuring separation between departures once they are handed over from TWR. This controller may also suggest headings or vectors as appropriate to maintain this separation.
APP take care of DEP, when this position isn’t manned.

1.3.5 Approach Control (APP)

As the name implies, Approach is responsible that aircraft when they approach the airport.

For arriving aircraft, the hand over point is normally when the aircraft enters the STAR (Standard Instrument Arrival) entry point. Approach is responsible that separation is made in a safe way. In case the STAR doesn't end at the initial approach fix (final), Approach is responsible for vectoring aircraft on to the final with proper altitude and speed. Approach may also vector aircraft away from a STAR or SID (Standard Instrument Departure if this is necessary for safety reasons, or to get a good traffic flow.

Normally Approach also handles departure’s responsibilities, taking care of departing aircraft which are handed over to Centre Control.

Arriving aircraft are usually handed over to Tower when they have established ILS (Instrument Landing System) or when on final for visual approach.

1.3.6 Area Control Center (ACC)

Area Control Center (sometimes called Control CTR) provides ATC to aircraft on the en-route phase of flight.
This includes giving information that the pilot needs such as weather and traffic information.
It usually includes taking care of departing traffic, climbing to their cruising altitude and issuing inbound-clearance to traffic that is approaching the final destination of the flight.

ACC is also responsible for all airports where Tower and Approach are not manned.

ACC is a demanding position and requires a great deal of experience.

1.3.7 Flight Information Centre (FIS)

Flight Information Centre (sometimes called FSS) is an air traffic facility that provides a myriad of services to the pilot, such as pilot briefings, relaying of clearances and broadcasting of weather information.
At selected locations, FIS also provides en-route Flight Advisory Services. Last Updated on Tuesday, 11 November 2008 19:04