New Controller Advice¶
Introduction¶
So, you've passed your S1 exam. First, congratulations! You have taken the first big step into our congested virtual airspace.
Unfortunately, due to network limitations with the OBS rating, the training department are unable to give you any training 'on the network' before you pass your exam. Therefore, we will highlight some differences you need to be aware of before controlling.
The Radio and RDF¶
You will have installed either AFV (Audio for Vatsim), or an alternative such as TrackAudio, however you haven't used it while controlling yet. If you are connected and primed to your frequency in EuroScope, after you press the connect button on AFV everything is done for you. A frequency will automatically be selected, and you will be ready to transmit with your selected PTT key.
You should be aware of 'cross-copuling'. This is connecting 2 frequencies together. It is slightly different for TrackAudio and Audio For Vatsim, if you are using TrackAudio, then you can left-click to 'cross-couple across', which is the same as cross-coupling in Audio For Vatsim. As an S1, this is only really useful when there is a GMP/GMC split, and GMP is logging off. As GMC, you can 'XC' both the ground and delivery frequencies, in order to save pilots switching frequencies. Whilst the use at an S1 level is minimal, it is something you should be aware of. You can also do this when GMP will be opening in less than 10 minutes time, and is connected to the network, unprimed.
Text pilots and the 'command line'¶
This is also something that is briefly mentioned as part of your training, but is something you will use every time you control.
Command Line¶
The bottom bar is called the command line. This functions as a text input bar, anything you type with your keyboard will appear there. You can change who you send messages to by selecting options in the bottom left or to other controllers through the controller list in the top right.
You can find a list of useful commands in the 
EuroScope documentation, but some important ones are listed below.
| Command | Explaination |
|---|---|
.break |
Toggles on 'break' status. This shows that you are looking to close up in the next 10-15 minutes. This is not a form of coordination, so remember to do both. |
.nobreak |
Toggles off 'break' status. |
.center [any object] |
Centres your EuroScope view over any object: VOR, NDB, fix, airport, controller callsign, or aircraft callsign. |
.vis [any object] |
Centres your EuroScope visibility over any object: VOR, NDB, fix, airport, controller callsign, or aircraft callsign. If you do not specifiy an object, it is set to the centre of your EuroScope view. |
.find [any aircraft] |
Draws a white line from the centre of your EuroScope view to the specified aircraft. The line shows for 5 seconds. |
.getfp [any aircraft] |
Sends a request to the sever to retrive the flight plan of the specified aircraft. Use it if you think the FP has not updated correctly |
.inf [any aircraft/controller] |
This sends an information request to the specified aircraft or controller. The answer will come back as a private message. |
.msg [any aircraft/controller] |
This send a private message to the specified pilot or controller. |
.contactme [any aircraft] |
Sends a message to the pilot asking them to contact you. |
| Home then clicking an aircraft (ASEL) | Same as .contactme. |
.wallop [message] |
This sends a message to all supervisors. You should only do this when requesting a supervisor. You can also see |
Text Pilots¶
Text pilots is not a topic that can be fully covered with a mentor before your exam and first network session. You can find out more detail about them at Text Aliases, including a list included with the Controller Pack. You can also find aliases that come with EuroScope at %AppData%\Roaming\EuroScope\alias.txt. If you want, you can also add your own to the file.
Here are a few useful ones:
| Alias | Message |
|---|---|
.rsn |
Report your stand number |
.rat |
Report your aircraft type |
.qnh |
QNH $altim($1) |
.ho |
Contact $radioname($1) ($atccallsign($1)) $freq($1) |
.sid |
Cleared to $arr, $sid departure, squawk $squawk, QNH $altim($dep) |
.rc |
Readback correct |
.rcq |
Reacback correct, QNH $altim($1) |
.ready |
Readback correct, report ready |
.readyq |
Readback correct, QNH $altim($dep), report ready |
.taxi |
Taxi holding point $1 via $2 |
.stand |
Taxi stand $1, via $2 |
.p |
Push and Start approved |
.p(n,e,s,w) |
Push and Start approved, face (North, South, East, West) |
Changes to Policies and/or Procedures¶
Changes to policies and procedures are announced in the Discord #operations-updates channel. You can also find them in the UKCP Notifications list.
It is important that all controllers keep up to date with changes.
Relief Callsigns¶
As you cannot connect under the same callsign as an active connection, we have another callsign to ensure a smooth transition between one controller and another. Relief callsigns include a second underscore between the middle identifier and the suffix, for example EGLL_N_APP has the relief callsign EGKK_N__APP.
You can also identify a controller position by the identifier in the controller list. These are the same identifiers used when defining handoff and top-down orders.
Top-down¶
As outlined in your training, Vatsim follows a 'top down' policy. It is important that you know as a controller what area sector you need to coordinate with. The top down order can be found in the relevant airfield documentation.
You can find out more on the Area Sectors page.
MAN_xx_CTR positions all have the radiotelephony callsign 'Scottish Control', not 'Manchester Control'.
STC_A_CTR covers the Belfast TMA, whereas STC_CTR or other STC_x_CTR callsigns cover the Scottish TMA, or parts thereof. They are not the same thing, and do not cover each other top-down.
Tower Handoffs¶
When busy, TWR may ask that all departures be instructed to 'monitor', rather than 'contact'. This means that the aircraft will switch to the TWR frequency, but will not make an initial call, rather waiting for TWR to call them. You can use the .mon alias for text pilots.
You should always instruct aircraft to "contact" unless TWR tells you otherwise.
vFPC¶
vFPC is a compact flight plan checker that runs inside of EuroScope, and can offer corrections as far as the FIR boundary. You can find out more detail on the vFPC Controller Guidance page.
Warning
vFPC is not a replacement for proper knowledge of basic aerodrome departures and flight plan routes. All controllers must have a working knowledge of SID restrictions, flight level capping, and the semicircular rule. vFPC is an assistive resource and not a substitute for proper knowledge.
Differences between Vatsim and Sweatbox pilots¶
- Always stay calm. Try not to go into tunnel vision when faced with issues or new pilots, it just makes you more likely to make mistakes.
- By the same token, do not 'panic vector'. The term is more applicable at higher ratings, but you may still find yourself issuing not so good instructions when things get hectic. Take a second, breath, think about who needs what, then issue the next instruction. If pilots are shouting other each other, focus on the most important aircraft, and focus on them for a moment.
- Do not be afraid to tell the pilot with an unusual flight plan to stand by while you deal with an influx of moving traffic. It is better to leave them sat there for 5 minutes than to send them off with a bad flight plan, or issue conflicting instructions to several aircraft while you are trying to fix it.
- Sometimes it may be a good idea when making a transmission on voice to send the same thing via text at the same time or immediately afterwards. Situations where this may be beneficial include:
A new pilot is not sure of a clearance, instruction, or rereoute (though you can do all reroutes via text).
You are giving an unusual clearance (e.g. a non-standard IFR clearance with a lot of steps) where a written copy can't hurt.
You are issuing a standard procedure, but a quirk in the rules make it sound horrendous or leads to foreign pilots not understanding it. - This mainly applies during events, but also when traffic is busy. Do not bow to pilot pressure! If you are working planner (
EGxx_P_GND), your entire job is to delay outbound traffic so that other controllers do not get overwhelmed. Plenty of pilots will not appreciate this. Some will ask to skip the queue, some will bemoan that you told them the delay was 15 minutes 30 minutes ago (sometimes things just slow down). Please, for the sake of all those working all overlying positions (including GND and TWR), ignore the complaints. Some of the largest event meltdowns have occurred because planners let the pilots boss them around. Always remember that they are not the boss, you are! If a pilot skips the queue, then do not be afraid to.wallopthem.