> ## Documentation Index
> Fetch the complete documentation index at: https://www.narev.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Sydney: Coordination

> Sydney: Coordination: frequencies, local rules and operational references.

Coordination at Sydney (YSSY).

## Auto Release

YSSY utilises auto release for all Procedural SIDs, and the SY (RADAR) SID provided aircraft are assigned the standard assignable level and a Standard Assignable Heading.

Next coordination is not required for aircraft that are:

Departing from a runway nominated on the ATIS; and

Assigned the Standard assignable level; and

Assigned a Procedural SID, or the Radar SID/ANKUB SID with a Standard Assignable Heading; or

A helicopter cleared via an outbound helicopter route.

All other aircraft require a 'Next' call to SY TCU.

'Next' coordination is additionally required for:

After a go around, the next departure from that runway

All aircraft during the Curfew Runway Mode

The standard assignable level from SY ADC to SY TCU is:

| Aircraft | Level |
| - | - |
| Jets | A050 |
| Non-Jets | The lower of A030 and RFL |

* [Standard Assignable Heading](https://www.narev.ai/docs/irl-gym/airports/sydney/procedures/coordination.md#standard-assignable-departure-headings)
* Next
* After a go around

## Departures Controller

When a TCU controller is online, aircraft shall be issued with a departure frequency during their airways clearance in accordance with the table below. If no TCU controllers are online, the appropriate enroute frequency or advisory frequency shall be issued.

### RWY 07

| Runway | Via | Departure Frequency |
| - | - | - |
| 07 | ANKUB SID, or FISHA SID, KADOM/OLSEM/STUIE Transitions, or Tracking N, NW, or NE | 123.0 (SDN) |
| 07 | FISHA SID, WOL Transition, or Tracking S, W, or SE | 129.7 (SDS) |

### RWY 16s

| Runway | Via | Departure Frequency |
| - | - | - |
| 16L | KEVIN SID (exc. radar trans to S or W), or Tracking SE, E, NE, or N | 123.0 (SDN) |
| 16L | ABBEY SID, or ANKUB SID, or Tracking S or W | 129.7 (SDS) |
| 16R | All | 129.7 (SDS) |

### RWY 25

| Runway | Via | Departure Frequency |
| - | - | - |
| 25 | AVMOV SID, or Tracking N, or NE | 123.0 (SDN) |
| 25 | ANKUB SID, or KADOM SID, or STUIE SID, or Tracking S, W, or SW | 129.7 (SDS) |

### RWY 34s

| Runway | Via | Departure Frequency |
| - | - | - |
| 34L | AVMOV SID, or Tracking N, or NE | 123.0 (SDN) |
| 34L | ANKUB SID, or KADOM SID, or STUIE SID, or TONTO SID Tracking S, W, or SW | 129.7 (SDS) |
| 34R | MARUB SID (exc. WOL trans), or OLSEM SID, or Tracking N, or NE | 123.0 (SDN) |
| 34R | MARUB SID, WOL Transition, or Tracking S, W, or SW | 129.7 (SDS) |

## Standard Assignable Departure Headings

Aircraft that have been cleared the SY (RADAR) SID or ANKUB SID must receive an assigned heading with their line up or takeoff clearance. 'Next' coordination is not required to the SY TCU controller when the departing aircraft has been assigned the standard assignable level and assigned one of the headings listed below:

Where multiple standard assignable headings are available, assign the heading most suitable for the aircraft's direction of flight.

If strong winds are present at altitude, ADC/DEP should discuss slight changes to these headings (+/- 5 degrees) to compensate for large crosswind components.

| Runway | Jet | Non-Jet |
| - | - | - |
| RWY 07 | H070 | H020, H110 |
| RWY 16L | H125 | H090 (RWY 25 not in use) H125 (RWY 25 in use) |
| RWY 16R | H170 | H210 |
| RWY 25 | H300, H240 | H020, H210, H240 |
| RWY 34L | H290 | H230 |
| RWY 34R | H030, H070 | H350 |

* [ANKUB SID](https://www.narev.ai/docs/irl-gym/airports/sydney/procedures/sid-selection.md#ankub-non-jet-sid)

## Between ADC and SMC

## Inactive Runway Releases

SY ADC has responsibility of all runways, requiring SY SMC to coordinate with SY ADC to allow aircraft to cross runways whilst taxiing. SY SMC may request, or SY ADC may elect, to release certain runways to the SY SMC controller, so they may let aircraft cross the runway without coordination (for example, releasing runway 07/25 to SY SMC whilst PROPS are in progress.) This release may also be cancelled at the controller's discretion.

## ACD to SY TCU

The controller assuming responsibility of SY ACD shall give heads-up coordination to the relevant SY TCU controller prior to the issue of the following clearances:

VFR departures, other than helicopters assigned a helicopter route coded clearance

Aircraft using a runway not on the ATIS

* heads-up

Source: [VATPAC Sydney SOP](https://sops.vatpac.org/aerodromes/classc/sydney/), CC BY 4.0. Adapted for the simulator from the snapshot retrieved 2026-09-29; source updated 2026-09-01. [Licence](https://creativecommons.org/licenses/by/4.0/).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.