Skip to main content
Manoeuvring Area at Sydney (YSSY).

Manoeuvring Area Responsibility

The vatSys ground map includes new taxiways which some simulators may not include. Some pilots will be unable to accept taxi via: Taxiway D south of G Taxiway J east of Runway 16R Taxiway K east of C

Heliport Responsibility

When runway 07 or 25 is in use for either arrivals or departures, the responsibility for management of the helicopter area and associated arriving and departing helicopters falls to ADC West. During all other runway modes, ADC East (if online) takes responsibility for the heliport.

Transferring Between SMC and ADC West

When both ADC and SMC are online, SMC shall issue aircraft departing on runway 16L/34R with a taxi limit in accordance with the table below. When runway 34R is in use, ADC shall issue further taxi to the holding point, considering any conflict with arriving aircraft taxiing via U1 and L. Aircraft landing on runway 16L/34R are expected to vacate the runway and taxi via the standard taxi routes to join taxiway Lima. If pilots are unfamiliar with local procedures, they should be instructed by ADC to taxi accordingly. Where possible, outbound aircraft should give way to inbound aircraft to avoid creating congestion at the runway exits.
  • standard taxi routes

Transferring Between SMCs

When both SMC positions are online and an aircraft is to be passed from one to the other (e.g. an aircraft taxis from the domestic terminal for runway 34L), they should be instructed to hold short of runway 16R/34L at the appropriate point and to contact the next SMC frequency. The aircraft’s strip shall be placed in the receiving controller’s bay prior to frequency transfer. The receiving controller is responsible for coordinating the runway crossing with ADC.
  • the appropriate point

Standard Taxi Routes

Standard taxi routes establish an implied set of taxi instructions which pilots are expected to comply with in the absence of other instructions. All runway crossings require an explicit crossing instruction. Controllers do not need to explicitly say each taxiway provided it is covered by a standard taxi route in the tables below. Not all pilots are aware of the existence of standard taxi routes. When in doubt, provide full taxi instructions detailing the full desired route. Standard taxi routes are published in Pilot Procedures and on the STANDARD DOMESTIC TAXI ROUTES charts. Controllers may choose to provide instructions which contradict a published standard taxi route to expedite traffic flow.
  • Pilot Procedures

General Flow

Except when the traffic situation warrants, taxi clearances shall conform to the following: For aircraft taxiing northbound on B, consider instructing them to hold short of taxiway B8 when 34L or 16R are in use for arrivals, in order to separate from aircraft using the B7 & B9 rapid exits.

Runway 16L/34R

The standard taxi routes for arrivals on Runway 16L/34R are: Aircraft landing on Runway 16L/34R are expected to vacate the runway and taxi via the standard taxi routes to join taxiway Lima, before contacting Ground.

Domestic Aprons

Additional standard taxi routes exist into and out of the domestic aprons. ERSA FAC YSSY noise abatement procedures require jet aircraft to depart runway 34L from full length only. This should be simulated where practical but intersection departures should be offered to jet aircraft on request where available.

Arrivals

Departures

Crossing Runway 16R/34L

Generally, aircraft cross runway 16R/34L at the following locations.

Taxiway Restrictions

Category F aircraft cannot use Taxiway H, or the sections of Taxiways B and C north of Taxiway G and south of Taxiway K. Certain Category E aircraft, such as B77W and A35K, are also unable to use the full extent of Taxiways B and C. ERSA FAC YSSY contains alternate taxi routing options to enable such aircraft to reach Runway 16L/34R. Source: VATPAC Sydney SOP, CC BY 4.0. Adapted for the simulator from the snapshot retrieved 2026-09-29; source updated 2026-09-01. Licence.
Last modified on October 30, 2026