Aerodrome

Radio Setup

Avionics and radio hardware setup is generally pilot preference. Aircraft with a requirement to maintain two-way communications with ATC (e.g. IFR aircraft operating OCTA) will need to manage both the relevant ATC frequency and local CTAF.

A common radio setup is:

COM 1	COM 2
ATC/Area Frequency	CTAF

Single Radio Aircraft

Aircraft equipped with a single radio engaged in IFR operations must continue to comply with the two-way communication requirement (outlined above). When operating OCTA in the vicinity of an aerodrome, these aircraft will need to switch between the relevant ATC frequency and the local CTAF.

Pilots must report when leaving an ATC frequency in this manner, including listing the CTAF they are switching to.

Phraseology

RXA6518: "RXA6518, switching to Parkes CTAF 126.7"
GUN: "RXA6518, identification terminated"

Important

You must not leave an ATC frequency whilst inside controlled airspace. For aircraft equipped with a single radio, pilots must wait until they leave CTA and then notify ATC that they are switching frequencies.

ATC Frequency

Taxi

Immediately prior to, or during, taxi at a Class G aerodrome, IFR aircraft must make a taxi report to the enroute or terminal controller managing the overlying airspace.

Format

"ATC Unit, Callsign, Aircraft Type, [Persons on Board POB], IFR, taxiing Location for Destination, runway Departure Runway"

POB is not required for scheduled air transport flights.

Example

"Melbourne Centre, RXA6588, SAAB 340, IFR, taxiing YORG for YPKS, runway 29"

"Sydney Approach, FWC, Cessna 172, 3 POB, IFR, taxiing YWBN for YYNG, runway 35"

In response, ATC will likely issue a squawk code and traffic statement of any relevant nearby aircraft.

Low Overlying CTA

Some aerodromes, particularly those in the capital city terminal areas or procedural towers where the tower is closed, have low overlying CTA steps which may be difficult to avoid on departure. In these situations, ATC will issue an airways clearance for aircraft planned into CTA prior to departure.

Example

QLK101D: "Brisbane Centre, QLK101D, Dash 8, IFR, taxiing YCFS for YSSY, runway 21"
INL: "QLK101D, squawk 1202, no reported IFR traffic, report lined up for airways clearance"
QLK101D: "Squawk 1202, wilco, QLK101D"

QLK101D: "QLK101D, lined up"
INL: "QLK101D, cleared to YSSY via SORTI, flight planned route, climb to F120"
QLK101D: "Cleared to YSSY via SORTI, flight planned route, climb to F120, QLK101D"

Poor Radio Reception

Where poor radio reception precludes establishing contact with ATC on the ground, report airborne to commence your SARWATCH service.

Format

"ATC Unit, Callsign, airborne Location"

After establishing contact, report your departure.

Example

IBU: "Melbourne Centre, IBU, airborne YMRY"
WOL: "IBU, squawk 3277, no reported IFR traffic"
IBU: "Squawk 3277, departed YMRY 44, tracking 340, climbing to A080, estimating ATGOD at 12, IBU"
WOL: "IBU, no reported IFR traffic for climb to A080, area QNH 1009"
IBU: "Area QNH 1009, IBU"

Arrival

After landing at their destination, or where insufficient radio coverage exists on the ground, at a suitable time during their arrival, IFR aircraft must report their arrival to ATC and cancel their SARWATCH.

Format

"Callsign, Location, cancel SARWATCH"

Example

EWQ: "EWQ, Charleville, cancel SARWATCH"
ISA: "EWQ, Charleville SARWATCH terminated"

SARWATCH termination is not required to be read back by the pilot. Once your SARWATCH has been terminated, your flight has finished in the eyes of ATC. No further services will be provided to you.

CTAF Frequency

When operating within, or approaching, the vicinity of a non-controlled aerodrome, you should tune the appropriate CTAF and make broadcast radio calls as deemed appropriate.

Format

"Location traffic, Callsign, Message, Location"

You are only required to make a radio broadcast on a CTAF where you consider it necessary to avoid a collision with another aircraft. However, common sense would suggest that regular, structured broadcasts are the best way to mitigate potential conflict and aid other pilots in their situational awareness.

Pilots should reply to any received broadcast with their own position and intentions (and any other relevant information) where they deem potential for conflict.

Note

The vicinity of an aerodrome is a broad term with no strict definition. As a general rule, pilots should broadcast on the frequency when within roughly 5 to 8 minutes laterally and when intending to operate in the airspace from the surface to roughly 5,000ft above ground level. In practice, this translates to a 10 nautical mile radius for small, piston aircraft like Cessna 172s and Piper Cherokees, and up to a 30 nautical mile radius for high performance aircraft like turboprops and jets.

Good airmanship would dictate monitoring the CTAF even when outside this volume of airspace where it is known that high-performance aircraft are operating in the vicinity.

On VATSIM, some aerodromes may be partially controlled and may, or may not, require CTAF calls to be made.

Video Demonstration

Finding the Correct Frequency

The CTAF for each aerodrome can be found by referencing its appropriate ERSA entry or reviewing its aerodrome chart. These resources are available on the Airservices website for free or through providers like Navigraph, Chartfox and the VATPAC Tools page.

Additionally, the VATSIM AIP includes all published VATPAC aerodromes, with information including the correct frequency to use. This is particularly important for locations like Sydney, Melbourne, and the other Class C airports which operate 24 hours a day in the real world. VATPAC has defined an appropriate CTAF for these locations which should be used by pilots when there is no ATC coverage online.

Tip

Pilots can type .ctaf into any VATSIM pilot client to display the appropriate frequency to use at an aerodrome.

Default Frequency

Where a particular aerodrome or landing site is not included in the VATSIM AIP and/or does not have an ERSA FAC entry, pilots shall use the default frequency.

The default frequency is 126.7.

If no discreet frequency is published for a particular aerodrome or the landing area you are operating from is not listed, you should use this frequency.

Partial ATC

ADC Online

If an ADC is online but no TCU controller is controlling the airspace above the aerodrome, the aerodrome is designated a controlled aerodrome and pilots will receive normal aerodrome services from ADC. After departure, in lieu of the 'contact departures' call, ADC will inform pilots that their 'frequency change is approved'.

Pilots should switch to the most suitable frequency, generally Advisory (122.8).

Tip

In some circumstances, it may also be beneficial to monitor/broadcast on a nearby CTAF (e.g. YMEN if departing towards YMML with both aerodromes uncontrolled).

Inbound aircraft should utilise Advisory when entering the vicinity and organise separation with other traffic on that frequency, then switch to the Tower frequency approaching the circuit area or when established on final.

SMC Online

If an SMC is online but no ADC is available, the aerodrome is designated an uncontrolled aerodrome. Pilots will receive normal clearance delivery and taxi instructions but will be required to utilise the aerodrome's CTAF for any runway entry, takeoff, and departure broadcasts.

Approaching the holding point, pilots of domestic aircraft shall switch autonomously from the SMC frequency to the CTAF and commence normal CTAF calls. Pilots of international aircraft can expect an explicit frequency transfer.

Inbound aircraft should utilise the CTAF when entering the vicinity and organise separation with other traffic on that frequency.

Recommended Calls

Departures

Pilots departing an aerodrome are encouraged to make a CTAF broadcast when they are:

• Taxiing for departure

Example

"Dubbo traffic, Cessna 182 CSA, taxiing to runway 05, Dubbo"

• Entering the runway

Example

"Dubbo traffic, Cessna 182 CSA, entering and backtracking runway 05, Dubbo"

• Commencing the takeoff roll

Example

"Dubbo traffic, Cessna 182 CSA, rolling runway 05 for a downwind departure to the southwest, climbing to A065, Dubbo"

• Departing the circuit

Example

"Dubbo traffic, Cessna 182 CSA, departed downwind runway 05, passing A023, climbing to A065, tracking 214 to Griffith, Dubbo"

Arrivals

Pilots arriving to aerodrome are encouraged to make a CTAF broadcast when they are:

• About to enter the vicinity of the aerodrome

Example

"Cowra traffic, Cub ELN, 11 miles south southeast, A045, inbound, estimating the circuit area at 36, Cowra"

• Joining the circuit

Example

"Cowra traffic, Cub ELN, joining downwind runway 15, Cowra"

• Clear of the runway

Example

"Cowra traffic, Cub ELN, clear of all runways, Cowra"

Overflyers

Pilots overflying an aerodrome are encouraged to make a CTAF broadcast when they are:

• About to enter the vicinity of the aerodrome

Example

"Wagga traffic, Helicopter SUA, 8 miles west, A035, overflying to the east, estimating overhead at 40, Wagga"

• Overhead

Example

"Wagga traffic, Helicopter SUA, overhead, A035, tracking to the east, Wagga"

Circuits

Pilots conducting circuits at an aerodrome are encouraged to make CTAF broadcasts as appropriate to mitigate conflict with other aircraft. At a minimum, broadcasting on the base leg with your intentions is generally acceptable.

Example

"Winton traffic, Cherokee KLR, base, runway 14, touch and go, Winton"