Amberley / Oakey TCU

Positions

Name	Callsign	Frequency	Login ID
Amberley TCU	Amberley Approach	126.200	AMB_APP
Oakey TCU	Oakey Approach	125.400	OK_APP

AMB APP is expected to extend to OK APP when they are offline. No frequency cross coupling is required.

Airspace

AMB TCU

Restricted Areas

By default, AMB APP owns all of the R625 Restricted Areas, as detailed below:

R625A (A015-A085)
R625B (A025-A085)
R625C (A045-A085)
R625D (A085-F210)

Optional, as required

AMB APP can negotiate further airspace releases from surrounding ENR sectors to facilitate planned military operations of the following Restricted Areas:

R650A (A050-A100)
R650B (A050-F600)
R662A (A050-F600)
R662B (A050-F600)
R671A (F125-F245)
R671B (F240-F600)

Note

See VATPAC Notams for active NOTAMs which may affect military operations.

Diagram

AMB ADC

AMB ADC owns the Class C airspace in the AM CTR within 10nm of the YAMB ARP from SFC to A015.

OK TCU

Restricted Areas

By Default OK APP owns all of the R625 Restricted Areas, detailed below:

R654A (SFC-A065)
R6545B (SFC-A065)
R654C (A065-F125)
R654D (A065-F125)

Diagram

OK ADC

OK ADC owns the Class C airspace within 5 DME of the OK VOR from SFC to A025. This airspace is designed to facilitate circuit traffic.

YAMB Aerodrome

Coded Departures (Fast Jets)

Visual Departures are commonly requested by high performance military jets, and often processed in the form of a coded departure (e.g. BYRON7 departure), which can be found in the AD2 Sups Page for Amberley. These coded departures provide a corridor with altitude constraints to join the Military Training Areas east of Brisbane avoiding civilian traffic inbound to Brisbane.

Aircraft will make a visual departure in the circuit direction and fly overhead YAMB to begin tracking for their initial waypoint.

Example

WOLF03 was assiged the BYRON7 departure with their intial clearance.
AMB ADC: "WOLF03, make left turn, reach F190 by COWIE, cleared for takeoff"
WOLF03: "Make left turn, reach F190 by COWIE, cleared for takeoff, WOLF03"

Departure	Initial Constraint	Route
Northern 1	`F190` at BINUP	BINUP MURJO BOBED LESKO MOSSI/ADNUK (Transition)
Central 1	`F190` at BINUP	BINUP MURJO BOBED VIRGE
Byron 7	`F190` at BINUP	COWIE KIWEE ZANET LOTMA SEMAJ

Note

Charts for the Coded Departures may be in YAMB AD2 Supplements 6.2.25.11 available here: RAAF AIP page

Note

AMB ACD will record the name of the coded departure in the Global Ops Field of the FDR and amend the flight plan route with all necessary tracking points.

Charts

Note

Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of RAAF AIP page

Coordination

AM/OK ADC

Airspace

AMB ADC owns the Class C airspace in the AMB CTR within 10nm of the YAMB ARP from SFC to A015.

OK ADC owns the airspace within 5 DME of the OK VOR from SFC to A025.

Departures

'Next' coordination is required from AMB ADC to AMB TCU for all aircraft.

Example

AMB ADC -> AMB TCU: "Next, ASY01, runway 33"
AMB TCU -> AMB ADC: "ASY01, Assigned Heading Right 030, unrestricted"
AMB ADC -> AMB TCU: "Assigned Heading Heading Right 030, ASY01"

INL / BN TCU

Departures

All aircraft from AMB/OK TCU to INL(All) and BN TCU require Heads-up coordination prior to the boundary, however, as soon as practical (when is the aircraft becomes airborne) is prefered.

The Standard Assignable Level from AMB ADC to AMB TCU is:
a) The Lower of F180 or RFL for Aircraft assigned via Procedural or RNAV SID.
b) F190 for Aircraft assigned a Coded Departure.

The Standard Assignable from OK ADC to OK TCU is the lower of F120 or RFL.

Example

AMB TCU -> BN TCU: "via BN, DRGN02"
BN TCU -> AMB TCU: "DRGN02, F180"

Example

BUCK03 is assigned the BYRON 7 coded departure. AMB TCU -> NSA: "via COWIE, BUCK3."
NSA -> AMB TCU: "BUCK03, F190"

Arrivals/Overlfies

All aircraft transiting from GOL/DOS/BUR to AMB TCU and OK TCU must be heads-up coordinated prior to 20nm from the boundary and aircraft from BN TCU to AMB TCU only prior to the boundary. Operations within AMB TCU are fairly ad-hoc, so there are no standard assignable levels. GOL/DOS/BUR and AMB TCU/OK TCU controller must agree on a suitable level during coordination.

Example

GOL -> AMB TCU: "via HUUGO, PUMA11, will be assigned A090"
AMB TCU -> GOL: "PUMA11, A090"