Melbourne ATIS - Narev Docs

Melbourne (YMML) uses ATIS identifiers N through Y. Nearby Essendon (YMEN) uses A through M.

Approach expectations

Arrival runway	Cloud base	Approach information
09	Any	Expect a GLS or RNP approach.
16 or 27	Any, subject to the runway 16 low-cloud rule below	Expect a GLS or ILS approach.
16	At or below A005	Expect an ILS approach.
34	Above A030	Aircraft on the Alpha STAR can expect a GLS or RNP approach.
34	At or below A030	Expect a GLS or RNP approach.
34 and 27, with LAHSO	Any	Expect an instrument approach.

For runway 34 above A030, the Alpha-STAR wording allows controllers to assign either the Alpha or Victor STAR and process aircraft for GLS/RNP or a visual approach, depending on traffic flow and pilot preference. A005 and A030 retain the source’s altitude notation.

Runway information

Mode	Information to include
27AD/34D	Runway 27 for arrivals. Runway 34 for departures via MNG, NONIX and DOSEL; runway 27 for all other departures.
16A/27D	Runway 16 for arrivals; runway 27 for departures.
09A/16D	Runway 09 for arrivals; runway 16 for departures.
34A/27AD	Runways 27 and 34 for arrivals; runway 27 for departures.

Operational information

Runway mode	Information to include
09A/16D	Simultaneous independent crossing-runway operations in progress.
34A/27AD with LAHSO	LAHSO in progress.

For independent 09A/16D operations, aircraft depart runway 16 from taxiway Echo, allowing runways 09 and 16 to operate independently.

Pushback requests

When the pushback-on-airways-clearance procedure is in use, the operational-information field must tell all departures to request pushback on 127.2 MHz. Source: VATPAC Melbourne SOP, CC BY 4.0. Snapshot: 29 September 2026; source updated 22 September 2026. ATIS abbreviations expanded for readability.

Last modified on October 30, 2026