VATNZ ATIS Policy
The VATSIM EC policy mandates that ATIS shall have not more than 4-lines.
Note: A "line" is technically a standard 64-character data packet for transmission purposes.
All ATIS used within the VATNZ Division:
- MUST comply with the VATSIM 4-line rule.
- MUST conform to the VATNZ ATIS Policy below.
The purpose of ATIS is to:
- Provide proper voice channel switching (1st line in ASRC)
- Provide operational information, similar to real world ATIS (remaining lines), based on the on-line weather from the network.
Operational information follows immediately after the voice channel switching line and MUST begin with the Aerodrome name and the ATIS Identifier.
Operational information should be presented in the sequence shown, and use standard abbreviations where possible, eg; APCH, ARR, DEP, EXP, PARL, RWY, WND, XW, DW, KTS, VIS, CLD, SKC, FEW, SCT, BKN, OVC, CAVOK, TMP, QNH, WX, Z.
The following items should NOT be included in an ATIS:
- Controller name and/or rating.
- The controller’s frequency.
- Raw METAR data that has not been decoded by the controller.
- Unnecessary or insignificant optional information.
- Information that should realistically be provided by voice interaction with ATC.
If space permits, at the end of the ATIS a controller may optionally include important online information explicitly necessary for a pilot whilst conducting their on-line flight. This additional information may include, but it not limited to:
The location of necessary maps/charts/routes/procedures
Note: Additional information should not be included at the expense of required operational information since that would defeat the basic purpose of ATIS.
Blank lines at the end should be eliminated.
The ATIS Identifier should be incremented for each ATIS change.
Note 1: ATIS Identifier codes should be allocated according to the relevant TMA document, otherwise starting from ALPHA. (See special arrangements within a TMA that ensure nearby adjacent ATIS are never the same as each other)
Note 2: ATIS Identifier ZULU is reserved and should not be used.
New Zealand ATIS do not conform to the ICAO standard, instead having their own codes and unique sequence of information.
The following line should be added to the ATIS Maker URL in Euroscpe:
This will produce an ATIS in the NZ format.
The following variables are available
The apptype can be user modified depending on what the controller wants and what the airport supports.
Valid values are: ILS, RNAV, GPS, VORDME, NDB, and VISUAL.
The ATC parameter can be user modified depending on the controllers online at the time.
Valid values are: GND, TWR, TMA (for approach and departure) and CTR
Up to 2 values can be entered, separated by a ,
If the second value entered is a lower position (I.E TMA,GND) it will be ignored
If both TMA and CTR are used at NZCH and NZHN, only one controller entry will be present in the ATIS due to both TMA and CTR positions at said airports being called Christchurch Control.
The following sequence of information should be used for all VATNZ ATIS:
|APCH:||approach information where an APP service is in operation|
|RWY:||states arrival runways, then departure runways|
|OPR INFO:||states runway operations such as PARL RWY OPS|
|WND:||direction and strength shown as ddd/ss|
|XW MAX:||shown as nn KTS on RWY nn|
|DW MAX:||shown as nn KTS RWY nn|
|VIS:||shown as nnnn or GT 10KM|
|CLD:||shown as coverage amount then altitude|
|TT:||Temperature in degrees C|
|DP:||Dew Point in degrees C|
|QNH:||shown as nnnn HPa|
|2000FT:||direction and strength shown as ddd/ss|
<------------------------------------ 64-CHARACTER WIDTH ------------------------------------->
AUCKLAND INFORMATION HOTEL. EXP ILS OR VIS APCH RWY: 23L
WND: 240/18G35; VIS: 30KM; CLD: FEW 2800, BROKEN 5400; TT: 28 DP: 5
QNH: 1018; 2000FT: 250/28
Note 1: The Identifier HOTEL must appear on the first line of the operational information, and it then becomes unnecessary to use it again at the end.
Note 2: Aliases and placeholders etc may be used to generate parts of the above ATIS.
In VRC the voice switching line is automatically inserted and only the operational information is required to be entered by the controller.
For complete documentation refer to the VRC manual.
Position Specific Guidelines
Different ATC positions have different ATIS requirements. This section provides guidelines for each position. The description column provides examples that may be used to provide the minimum compliance. It should be read in conjunction with the Content section above.
|DEL||None||[Optional] a 1-line statement about Availability - Log off time (UTC)|
Ground ATIS should refer pilots to the associated local Tower ATIS
ATIS AVBL FROM TWR
Note: If Tower is not online, Ground should provide a FULL ATIS if there is a controller providing local control (tower) services at the field for which the ATIS is being created. This can be an overlying center or approach controller. Reference VATSIM Code of Conduct under section C11.1 - C11.7
Tower must at all times provide a FULL ATIS that complies with the content guidelines.
ATIS Changes - should be broadcast on the ATC channel to inform adjacent controllers of the new ATIS Identifier and also new RWYs where these have changed.
NZCH_TWR> NOW BRAVO, RWY20 ALL OPERATIONS
|APP (with TWR)||Redirect|
Approach ATIS should refer a pilot to the associated local Tower ATIS:
|APP (without TWR)||Full ATIS||Approach should provide a FULL ATIS in lieu of the missing local Tower service, in accordance with the content guidelines set for Tower.|
|DEP||None||[Optional] a 1-line statement about Position name|
|CTR||None||[Optional] a 1-line statement about:|
CHRISTCHURCH CONTROL, EXTENDED COVERAGE AVAILABLE,
|FSS||None||[Optional] a 1-line statement about:|
AUCKLAND RADIO, OCEANIC COVERAGE IN THE AUCKLAND OCEANIC FIR,