> ## 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.

# Melbourne: Runway Modes

> Melbourne: Runway Modes: frequencies, local rules and operational references.

Runway Modes at Melbourne (YMML).

## Preferred Runway Modes

See Runway Mode Formatting for details on how to format each runway mode in the ATIS.

| Mode | Arrivals | Departures |
| - | - | - |
| 27AD/34D | 27 | 34 (via MNG, NONIX, and DOSEL), 27 (all other deps) |
| 16A/27D | 16 | 27 |
| 09A/16D | 09 | 16 |
| 34A/27AD | 34 & 27 | 27 |

* Runway Mode Formatting

## LAHSO

LAHSO is a complex runway mode requiring close attention by aerodrome, TCU, and enroute controllers. Controllers must ensure they are familiar with the specific LAHSO procedures before implementing LAHSO.

LAHSO is best run with a flow controller online.

* LAHSO procedures

## Weather Conditions

LAHSO may only be used where the weather conditions meet the following minimum requirements:

Two simultaneous landings may be conducted by both day and night. A simultaneous takeoff and landing may only be conducted by day.

| Element | Criteria |
| - | - |
| Cloud Ceiling | A045 or higher |
| Visibility | 8km or greater |
| Surface Condition | Dry |
| Windshear | None Reported |

## Runway Mode

The only approved LAHSO mode at YMML is 34A/27AD. Runway 34 is considered the active runway, while runway 27 is considered the passive runway.

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


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