New VATSIM Global Controller/ATIS Policy

Seattle ARTCC Approved NOTAMs to be used while Controlling/Flying

Moderator: ZSE Executive Staff

Post Reply
User avatar
Brayden Manzella
Posts: 108
Joined: Thu Aug 22, 2013 7:53 pm
Location: Buffalo, NY

New VATSIM Global Controller/ATIS Policy

Post by Brayden Manzella » Wed Feb 11, 2015 6:03 pm

A new VATSIM Policy has been placed in effect as of February 1, 2015. This new policy is for Controller Information and ATIS information. Please make sure we are following this policy as the Supervisors will be enforcing it, and correcting people if they are not following this policy. Thank you for your help.

http://www.vatsim.net/documents/global- ... ion-policy

Global Controller/ATIS Information Policy

Effective 1 February 2015. This policy is maintained by the Executive Committee.
Controller information is a component of published text ATIS broadcasts. Approved controller software programs format the broadcast of the Controller and ATIS Information slightly differently, but regardless of the software used, the following limitations shall apply:

For Controller Information:

The first line of any Controller Information may contain voice channel or network information that is either automatically inserted by the ATC software or manually entered by the controller
Beyond the one line of voice channel or network information, a controller shall add not more than four lines of airport operational information and each line shall be not more than 76 characters in length.
Controllers should be as succinct as possible and construct the Controller Information in fewer than the maximum number of characters per line allowed by this policy.
Information that is not permitted to be included in the Controller Information includes: Controller’s name and or rating or raw METAR data that has not been decoded.

For ATIS Information:

ATIS information must contain only Aerodrome Name or Identifier, ATIS Information letter, Observation Time, Weather, Active Runway, Expected Approach Type, Frequency to contact first and appropriate aviation-safety related operational information.
Operational information should include only information that is applicable in the VATSIM environment. Real-world operational information that cannot be effectively implemented on VATSIM (e.g., lighting and/or equipment outages) should not be included in any ATIS information.
Controllers should attempt to limit the ATIS Information to as few lines as possible.
Brayden Manzella
Air Traffic Director
VATUSA - Western Region
VATSIM Network Supervisor
Image

Post Reply