Adelaide TCU

Positions

Name	ID	Callsign	Frequency	Login ID
Adelaide Approach East	AAE	Adelaide Approach	118.200	AD_APP
Adelaide Approach West†	AAW	Adelaide Approach	124.200	AD-W_APP
Adelaide Flow†	AFL			AD_FMP

† Non-standard positions may only be used in accordance with VATPAC Air Traffic Services Policy

Airspace

The Vertical limits of the AD TCU are SFC to F245.

Reclassifications

PF CTR

PF CTR reverts to Class G when PF ADC is offline, and is administered by the relevant AD TCU controller.

EDN CTR

EDN CTR reverts to Class G when EDN ADC is offline, and is administered by the relevant AD TCU controller.

Airspace Division

Note

The following diagram does not include non AD TCU areas of responsibility such as PF CTR or EDN CTR

Scenic Coastal Flights

VFR aircraft may transit the control zone tracking coastal north or southbound, generally at A005. AD TCU is responsible for ensuring these aircraft remain separated from aircraft arriving/departing at YPAD and may delegate this responsibility to AD ADC.

Coordinate the aircraft with ADC, including the use of the appropriate clearance limit in the table below, then issue airways clearance. Before the aircraft reaches the clearance limit, transfer them to ADC who will manage their transit of the extended runway centreline. The clearance limits in the table below will ensure that coastal aircraft remain clear of the runway 05 approach path and runway 23 departure/missed approach path.

Direction of Travel	Clearance Limit
Northbound	BTJ
Southbound	HNLY

Clearance Limits (red) and Approach/Departure Path (green)

Example

CEY: "Adelaide Approach, CEY, Cessna 172, 4nm south of PNL, 1,000ft, received charlie, request coastal northbound"
AD TCU: "CEY, Adelaide Approach, squawk 0542, remain clear of class C airspace"
CEY: "Squawk 0542, remain OCTA, CEY"

TCU -> ADC: "South of PNL, CEY, for coastal northbound, 500ft, clearance limit BTJ"
ADC -> TCU: "CEY"

AD TCU: "CEY, identified, cleared coastal offshore northbound, not above 500ft, clearance limit BTJ"
CEY: "Cleared coastal offshore northbound, not above 500ft, clearance limit BTJ, CEY"

Before CEY reaches BTJ:
AD TCU: "CEY, contact Adelaide Tower, 120.5"
CEY: "120.5, CEY"

Once the aircraft has transited the extended runway centreline and is clear of potential conflict with YPAD, ADC will transfer them back to the TCU.

PF ADC Offline

Due to the low level of CTA at YPPF, it is best practice to give airways clearance to aircraft at the holding point, to ensure departing aircraft can have uninterrupted climb.

Example

ABC: "Adelaide Approach, ABC, PC12, POB 8, IFR, taxiing YPPF for YPAG, Runway 21R"
AD TCU: "ABC, Adelaide Approach, Squawk 3601, no reported IFR traffic, report ready at the holding point for airways clearance"
ABC: "Squawk 3601, wilco, ABC"

ABC: "ABC, ready Runway 21R, request clearance"
AD TCU: "ABC, cleared to YPAG via DOLVU, flight planned route, PARAFIELD1 departure, climb via SID to A040"
ABC: "Cleared to YPAG via DOLVU, flight planned route, PARAFIELD1 departure, climb via SID to A040, ABC"
AD TCU: "ABC, assigned heading right 360, report airborne"
ABC: "Assigned right 360, wilco, ABC"

Flow

The tables below give an estimated time in minutes from the Feeder Fix to the Threshold, which can be used to plan sequencing actions within the TCU.

The times assume there is Nil wind.

Jets

Feeder Fix	05Z	05V/W/X	23A/Z	23V
ALEXI	14	13	-	-
DRINA	-	-	14	13
BLACK	16	15	12^	-
KLAVA	16	15	13	12
ERITH	-	-	13	12
MARGO	14	13	15	13
RIKAB	13	12^	17	15

GULLY - Threshold is 5 minutes
PADSI - Threshold is 3.5 minutes
Add 1 minute for aircraft assigned a reduced speed, Except ^
Subtract 1 minute for MX or CSR
For Non-Jets (except DH8D) tracking via Jet STAR;
- Add 2 minutes (Except ^)
- Add only 1 minute for ^

Note

The adjustments above are cumulative. For example, an Non-Jet aircraft assigned a reduced speed, would have 3 minutes added in total

Non-Jets

This table assumes that aircraft will be assigned:

The appropriate Non-Jet STAR (ATPIP, ELROX, GULFS, PAMMY, RUSSL, SURGN), or if none is available:
No STAR

Thence track via a 5nm final for the assigned runway.

For Non-Jets tracking via the full Jet STARs, see table above

Feeder Fix	05	12	23	30
ALEXI	12	14	12	11
DRINA	14	17	14	13
BLACK	16	15	13	13
RUSSL	17	15	14	13
KLAVA	15	13	13	16
ERITH	-	-	-	-
MARGO	13	12	13	15
RIKAB	13	13	15	16
ELROX	11	11	14	13

5nm final - Threshold is 2 minutes
Subtract 1 minute for MX
Subtract 1 minute for DH8D

Note

The adjustments above are cumulative. For example, a DH8D with a MX, would have 2 minutes subtracted in total

Coordination

Enroute

Departures

Voiceless for all aircraft:

Tracking via a Procedural SID terminus; and
Assigned the lower of F240 or the RFL

Note

Aircraft are not required to be tracking via the SID procedure, simply tracking via any of the terminus waypoints (Regardless of departure airport or assigned SID) is sufficient to meet the criteria for voiceless coordination

All other aircraft going to TBD CTA must be Heads-up Coordinated by AD TCU prior to the boundary.

Example

AD TCU -> TBD: "PFY1234, request DCT LOLLS"
TBD -> AD TCU: "PFY1234, concur DCT LOLLS"

Arrivals

Voiceless for all aircraft:

With ADES YPAD; and
Assigned a STAR; and
Assigned A090

All other aircraft coming from TBD CTA will be Heads-up Coordinated to AD TCU.

AD ADC

Auto Release

'Next' coordination is not required from AD ADC for aircraft that are:
a) Departing from a runway nominated on the ATIS; and
b) Assigned the standard assignable level; and
c) Assigned a Procedural SID

Example

AD ADC -> AD TCU: "Next, ABC, runway 05"
AD TCU -> AD ADC: "ABC, Track Extended Centreline, unrestricted"
AD ADC -> AD TCU: "Track Extended Centreline, ABC"

The Standard Assignable level from AD ADC to AD TCU is:
For Jets: A050
For Non-Jets: The lower of A040 or the RFL

AD TCU Internal

All aircraft transiting between internal AD TCU boundaries must be heads-up coordinated.

Example

AAW -> AAE: "via AD, FD123"
AAE -> AAW: "FD123, A090"

Boundary coordination is not required between AAW and AAE for aircraft arriving or departing tracking via the 05/23 extended centreline.

PF ADC

Airspace

PF ADC is responsible for the Class D airspace in the PF CTR SFC to A015.

Refer to Reclassifications for operations when PF ADC is offline.

Departures

When the aircraft is ready for departure, PF ADC will coordinate with AD TCU for permission to release the aircraft into CTA.

Example

PF ADC -> AAW: "Next, XMM, 03L"
AAW -> PF ADC: "XMM, Heading 020, unrestricted"
PF ADC -> AAW: "Heading 020, XMM"

The Standard Assignable level from PF ADC to AD TCU is the lower of A030 or the RFL, any other level must be prior coordinated.

Arrivals/Overfliers

AD TCU will heads-up coordinate arrivals/overfliers from Class C to PF ADC prior to 5 mins from the boundary.
IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to PF ADC, unless PF ADC nominates a restriction.
VFR aircraft require a level readback.

Example

AAW -> PF ADC: "via PAL, YTS"
PF ADC -> AAW: "YTS, A010"

EDN ADC

Departures

Aircraft departing YPED in to AD TCU Class C will be coordinated from EDN ADC at Taxi.

Example

EDN ADC -> AD TCU: "Taxi, BLKT11 for YMES, via GULLY"
AD TCU -> EDN ADC: "BLKT11"

When the aircraft is ready for takeoff, EDN ADC will give a "Next" call, where AD TCU will provide the cleared level.

Example

EDN ADC -> AD TCU: "Next, BLKT11, runway 18"
AD TCU -> EDN ADC: "BLKT11, A050"
EDN ADC -> AD TCU: "A050, BLKT11"

Arrivals

AD TCU Must coordinate the sequence information to EDN ADC prior to transfer of jurisdiction.

Example

AD TCU -> EDN ADC: "New sequence of 2. MRNR21, via AD, Number 1. MRNR22, via AD, Number 2"
EDN ADC -> AD TCU: "MRNR21, Number 1. MRNR22, Number 2"