6. YBBN to YSSY

Sector Responsibilities

Gold Coast (GOL)

GOL is responsible for managing departures via SANEG.

Additionally, GOL may reclear more aircraft from the standard route to the amended RIKNI MARLN tracking, in order to keep a 50/50 balance between BOREE and MARLN arrivals in to YSSY.

Straddy (SDY)

SDY is responsible for reclearing aircraft via RIKNI MARLN.

All aircraft that SDY receives from BDS/BDN on a heading east of SANEG shall be recleared via this amended tracking.

Tip

Issue a Southbound heading prior to reclearing aircraft via RIKNI. This will help to avoid unpredictability in how long various pilots take to input the amended clearance in to their Flight Computer, and as such, when they start turning.

Inverell (INL)

INL will be responsible for starting to form the sequence in to YSSY, by applying speed control in the cruise.

INL will be responsible for the INL subsector only.

Howe (HWE)

HWE will not be staffed for the event, and they are taken to have No Restrictions or Requirements on Event traffic.

Ocean (OCN)

OCN will be responsible for issuing STAR clearances in to YSSY for aircraft tracking via MARLN only, and finalising the sequence using speed control and vectors in to YSSY.

STARs

Fix	Runway	STAR
MARLN	16L	MARLN5
MARLN	34R	MARLN5

Sequencing

All aircraft must be instructed to cross MARLN at 250 knots, then published STAR speeds.

Note

This instruction is not required for aircraft that have a clear gap in front of them in the sequence (>30nm).

Minimum distance between arrivals at handoff to SAN/SAS is 10nm (with no significant closing speed). It is important to try not to exceed 15nm, due to the large number of arrivals.

Tip

Track shortening direct to MARLN may help to close any gaps ahead of aircraft.

MAESTRO

If a Flow controller is online, the MAESTRO plugin should be used to determine the landing sequence. Enroute positions must ensure they comply with any sequencing instructions set out by Flow and communicated through the plugin.

Note

The MAESTRO plugin has been included in the Australia dataset by default for the event.

Armidale (ARL)

ARL will be responsible for issuing STAR clearances in to YSSY for aircraft tracking via BOREE only, and finalising the sequence using speed control and vectors in to YSSY.

ARL will be responsible for the ARL and MNN subsectors only.

Tip

Early Handoffs to CNK (~30-50nm from boundary) are a great way to balance workload.

STARs

Fix	Runway	STAR
BOREE	16R	BOREE4P
BOREE	34L	BOREE4A

Sequencing

All aircraft must be instructed to cross BOREE or MARLN at 250 knots, then published STAR speeds.

Note

This instruction is not required for aircraft that have a clear gap in front of them in the sequence (>30nm).

Minimum distance between arrivals at handoff to SAN/SAS is 10nm (with no significant closing speed). It is important to try not to exceed 15nm, due to the large number of arrivals.

MAESTRO

If a Flow controller is online, the MAESTRO plugin should be used to determine the landing sequence. Enroute positions must ensure they comply with any sequencing instructions set out by Flow and communicated through the plugin.

Note

The MAESTRO plugin has been included in the Australia dataset by default for the event.

Cessnock (CNK)

CNK will be responsible for finessing the sequence in to YSSY if required.

Offline Sectors

In the event that one or more of these sectors is not online during the event, the Event Coordinator will dictate which sector(s) are responsible for the offline sectors.

Official WorldFlight Teams

Most official team aircraft will depart from YBCG and track via WLM to facilitate their scenic arrival into YSSY. These aircraft should not be issued a STAR clearance. Assign these aircraft A090 and pass them to SAN/SAS.

Important

The YBCG to WLM track approximates a northbound airway. Be vigilant for any aircraft departing YSSY to the north who may conflict with the southbound aircraft.

WorldFlight Teams will be highlighted by default and should receive priority at all stages of flight.

Coordination

BDN/BDS to GOL

Voiceless for all aircraft:

Assigned the lower of F180 or the RFL; and
Tracking via SANEG.

All other aircraft going to GOL CTA will be Heads-up Coordinated.

BDN to SDY

Voiceless for all aircraft:

Assigned the lower of F180 or the RFL; and
Assigned H090.

All other aircraft going to SDY CTA will be Heads-up Coordinated.

SDY to HWE/OCN

HWE will have No Restrictions or Requirements on Event traffic. Aircraft transiting HWE airspace can be handed off directly from SDY to OCN.

SDY to INL

INL will have No Restrictions or Requirements on traffic tracking DCT RIKNI, and they can be handed off directly from SDY to OCN.

ARL to CNK

Changes to Route and CFL are permitted within 50nm of the boundary, without coordination, for sequencing purposes.
Aircraft must be tracking via BOREE.

CNK/OCN to SAS/SAN

Standard as per ARL Local Instructions.

BOREE Arrivals will be handed off to SAN.
MARLN Arrivals will be handed off to SAS.

Between ARL/CNK and SFL

SFL will construct the sequence via the Arrivals List Window.

Appropriate annotations for the Arrivals List Window can be found here.

SFL must voice coordinate any changes to instructions after ARL/CNK/OCN has put a < on it.

SFL will voice coordinate to ARL any aircraft that must be rerouted via RIKNI MARLN for 16L/34R.

Phraseology

SFL -> ARL: "ANZ361 via MARLN for 34R please"
ARL -> SFL: "ANZ361 via MARLN for 34R, will be"

ARL/CNK/OCN must voice coordinate any requests for Track Shortening or CSR to SFL.

Tip

If in your judgement, the request won't be available due to the sequence, there is no need to voice coordinate the requests. Just deny them.