General


The purpose of this document is to ensure that quality service is provided at all times in Australia airspace, and also so that a controller will never find himself submerged, and unable to cope.

It is mandatory for all IVAO members controlling a Australia position to follow these guidelines. Users who do not comply may be asked to close their position.

The Guidelines


  1. Active controllers should be able to use all functions of IvAc, and have read the manual thoroughly.

  2. All controllers must maintain their ATIS with the following information:
    - Position name (Full name, not ICAO code. e.g. 'Sydney Approach', not YSSY_APP)
    - Voice channel (if applicable)
    - Weather / runway information / TA/TL (if applicable)
    - No unnecessary remarks in the remarks section

  3. The language used for aviation in the Australia is english and must be used at all times..

  4. All controllers must use standard Australia phraseology at all times.

  5. When available, controllers should read and understand the appropriate airport/sector procedures before logging on. If you should have any doubts please don't hesitate to contact the FIR chief, or AOC if there is no chief.

  6. Controllers are required to have all applicable charts available while on duty (for centre controllers this can be quite a bunch).

  7. Controllers must make proper use of all datatag labels (F5 = cleared waypoint, F7 = cleared speed, and F8 = cleared altitude) when handing-off to adjacent sectors. We highly recommend you use these functions at all times, unless you prefer using the paper flight strips available in the downloads section..

In addition to the above controllers are required to meet the requirements set out in the position SOPs.

Operating Procedures - XO Division


Upper Center - FL300 to FL600
Lower Centers - FL180 to FL600 (A020 if APP not exist or FL300 if Upper Center is open)
Oceanic Sectors must not be open unless an ajoining Sector is open or is opened for a shceduled event.
Upper Centers opened over an exsisting Lower Center must be approved by the Lower Center Controller.
If no Lower Center exsists, an Upper Center can control from A030 to FL600.
Major Airports should be opened before smaller Regional Airports unless for an event. (With the exception of YSTW - Tamworth)
Unless otherwise stated, or agreed upon by ajoining controller, APP is 60Nm from A030 to FL180.
A controller can provide services to an "under" (Lower) posistion if that position is closed.

Squawk Codes


SSR codes fall into two groups; discrete and non-discrete. These groupings are a function of the ground radar/flight data processing system rather than the SSR system itself.

A non-discrete code is any code ending in '00' (e.g. 2000). Non-discrete codes may be used ('squawked') by more than one aircraft at a time and some non-discrete codes are allocated as general codes to certain classes of operation. For example, the standard SSR code for VFR aircraft in Australia is 1200 (formerly 2000). Some non-discrete codes are also allocated for emergency use; for example, 7700 denotes 'Mayday' and 7600 'Radio Failure'.

A discrete code, in contrast, is one which may only be assigned to a single aircraft at a time (codes may be re-used when no longer required by the original user). Any code not ending in '00' is considered non-discrete. As an aside, modern flight data processing systems may actually allow the simultaneous use of the same discrete code in certain circumstances.

In Australia for many years all high-capacity Regular Public Transport aircraft were allocated a 'skin' code. This was a discrete code allocated to the individual aircraft hull. The aircraft's transponder therefore never needed to be changed while the aircraft was operating in Australian airspace. This simple system was too difficult for the new TAAATS equipment, so it was discontinued from 1998.

Code

Assignment
0000-0777
0000 SSR data unreliable
0001-0017 Air Ambulance Emergency Medivac - Helicopter
0020-0027 Air Ambulance Emergency Medivac
0030-0037 Radar Flight Evaluation / Sector Calibration
0040-0057 MET research flight
0060-0077 Aircraft Paradropping
0100-0177 Royal Flights
0200-0277 Royal Flights - Helicopter
0300-0777 Not allocated yet
1000-1777
1000 NATO Fighter Ops.
1001-1077 Not allocated yet
1100 NATO Fighter Ops.
1101-1177 Not allocated yet
1200 Standard VFR in Australia,US. - In Europe Standard VFR is 7000 or 2000 - (Standard FS Squawk)
1201-1777 Not allocated yet
2000-2777
2000 Standard VFR in Europe - In US. standard VFR code is 1200
2001-2777 IFR Flights in Australia - VFR Flights in Europe
3000-3777
3000 NATO Fighter Ops.
3001-3777 Not allocated yet
4000-4777
4000 NATO Fighter Ops.
4001-4777 Not allocated yet
5000-5777
5000 NATO Fighter Ops.
5001-5777 Not allocated yet
6000-6777
6000 NATO Fighter Ops.
6001-6777 Not allocated yet
7000-7777
7000 Standard VFR in Europe - In US. standard VFR code is 1200
7001-7017 Aerobactic flights
7020-7037 Police Flights
7040-7477 VFR flights
7500 Hi-Jacking - Must NOT be used on IVAO
7501-7527 Aircraft engaged in police air support operations
7530-7557 Aircraft engaged in police air support operations - Helicopters
7600 Radio Failure
7700 Emergency
7701-7727 Aircraft engaged in actual SAR Operations
7730-7757 Aircraft engaged in actual SAR Operations - Helicopters
7760-7776 Ground Transponders Tests/Trials

Guidelines for IVAO Guest Controller Approval (GCA)



1. Any active division may require GCA for FRA restricted positions from air traffic
controllers who are not members of their division
2. If they do so, they must issue requirements to be fulfilled by the applicant for a
GCA.
The following guidelines must be observed when establishing the requirements
a. The requirements must at least be provided in English language.
b. The requirements shall specify the knowledge of local procedures, in respect
to regulations of ATC positions and/or general procedures of the division
c. The requirements may contain restrictions regarding local language,if the Divs
allow other than English in their Division (Ref. 4.4.1b R&R)
d. The requirements may take into consideration user’s behavior in the network, as
well as his mind of the spirit of IVAO and the division spirit.
3. A refusal for the GCA must be motivated and explained to the applicant. A copy
must be sent to HQ Training and Membership Departments.
4. Division HQ has to report accepted users to Membership and Training
Departments. MD will make an entry into the user’s profile. (In the future, an
automated entry may be possible.)
5. The requirements must be approved by HQ and then published on the division’s
web site.
6. Users violating these rules can be asked to leave the respective ATC position. If the
user is not leaving, an IVAO Supervisor may disconnect the user from the network.
7. The divisional staff has to observe the adherence of the GCAs (an automatic
rejection (like on FRA Position) is anticipated for the future).
8. The GCA can be withdrawn at any time if the member does not fulfill the mentioned
requirements

Full information about our GCA can be found under Guest Controllers

Visiting controllers

The Oceanic Region adheres to the new CGA structure and request all non Australian Controllers to apply at your earliest convenience.
The Australian division welcomes all IVAO members regardless of their division to come and control in the Australia, but we expect them to comply with all procedures just like any Australia Air Traffic Controller. Also we recommend you contact our staff (if online) to introduce yourselves. We reserve the right to ask you to close your position if you do not respect the Division procedures.
Guest Approval Applications are more than welcome, please fill out the GCA form to send us your GCA application.