VATEUD policy changes to §6 and §7

[Martin Georg 811874]

Dear VATSIM members,

 

 

as VATSIM has revised it´s policy regarding the use of voice lately, a revision of VATEUD´s policy was needed to be in accordance with the latest changes. Also, the opportunity was taken to change the policy in regards to the "middle initial" in ATC position callsigns also. Briefly spoken, the "_V_" letter has been dropped, and the "middle inital" is now free for use by the vACC´s. VATEUD recommends to use the letter to indicate a sub-sector inside the FIR sector, or to designate a trainer/mentor duo on position. All vACC´s are encouraged to create and publish a local policy about how to make use of the middle letter.

 

 

Below is the old and new policy text. Changes are marked red (old text) and green (new text).

 

 

1. §6 Use of text and voice for ATC

 

Old text:

Voice restrictions, based on Controller ID level, do not yet apply within VATEUD.

 

Each controller who provides voice services must include the middle letter _V_ in his/her callsign, and the Voice Server IP address in his/her ATIS. Some local exemptions exist for areas like Spain and the Netherlands, where other middle letters are used for their daily procedures.

 

Voice IP must be the first line of the Controller's ATIS, enabling SquawkBox (or other approved Pilot client) to identify the voice IP as quick as possible, if network lag is present.

 

Text ATC remains the official mode of communication, and every pilot and controller must be able to exercise this if needed. Pilots must be tuned to their controller's text ATC frequency (COM1 in FlightSimulator), even if they intend to use voice. Voice ATC is supplementary, to aid speed, ease, and realism of communications, but many times for various reasons, like Voice connectivity problems, text-only communications has to be used.

New text:

Voice restrictions, based on Controller ID level, do not apply within VATEUD.

 

Each controller who provides voice services must [Mod - Happy Thoughts]ure that his voice server IP is distributed to clients via his radar client software. In case the radar client software requires the voice IP to be entered manually, the voice IP must be the first line of the Controller's ATIS, enabling pilot clients to identify the voice IP as quick as possible.

 

Text ATC remains active as the secondary mode of communication, and every pilot and controller must be able to exercise this if needed. Pilots must be tuned to their controller's text ATC frequency (COM1 in FlightSimulator), even if they intend to use voice. Voice ATC is primary, to aid speed, ease, and realism of communications, but some times for various reasons, like voice connectivity problems, text-only communications has to be used.

 

 

2. §7 Login callsigns

 

Old text:

Members connecting to the VATSIM network with ASRC (approved ATC client) can only logon with the following callsigns within VATEUD:

 

4 letter ICAO code (for Airport, FIR or ACC), followed by a

 

_V_ if you are using voice (or _T_ for Training/Test procedures in progress), and finally

 

the 3 letter ATC code, depending on services provided.

 

Only the following ATC callsign suffixes are authorized for ATC: DEL, GND, TWR, APP, DEP, CTR and FSS.

New text:

Members connecting to the VATSIM network should use the following callsign name scheme for ATC positions in VATEUD airspace:

 

* 4 letter ICAO code (for Airport, FIR or ACC),

 

optionally followed by

_x_ , where "x" stands for a single letter to indicate a sub-sector inside the standard sector border (or _T_ for Training/Test procedures in progress)

 

* the 3 letter ATC callsign suffix, depending on the station providing service.

 

Only the following ATC callsign suffixes are authorized for ATC: DEL, GND, TWR, APP, DEP, CTR and FSS.

 

All changes are effective immediately. The VATEUD webpage will be updated today.