Skip to content

Phraseology Formatting

Rules for constructing phraseology shall be shown in a blue background for easy identification. Regardless of the format, the text in the phraseology rules must be formatted in a specific way:

Hidden table class directive Hidden table class directive
UPPERCASE WORDSWords in UPPERCASE must be spoken exactly as written.
(lowercase)Words in lowercase and parentheses describe information that should be inserted in place of the text.
[xxxx]Any text in square brackets is optional.
/A slash separates options, of which only one should be used.
(xx/yy)Parentheses are used to group options together, and to show information to be inserted as shown above.
-Hyphens between letters indicate that those letters should be spelled out individually.

There are two formats for defining phraseology rules. The example used contains the same information shown both ways.

The first format is written in one line with extra information written below the rules using a zyzStPh callout and a separate list for adding details:

(aircraft id), (control instructions) [wind] CLEARED (operation) (runway id) [SHORTENED].

Where:

  • control instructions:
    • IFR:
      • Contact when airborne instructions.
      • Heading instructions.
      • Altitude instructions.
        WHEN AIRBORNE CONTACT TORONTO CENTRE ON ONE-THREE-FIVE DECIMAL THREE. ON DEPARTURE TURN LEFT HEADING ONE-EIGHT-ZERO, CLIMB THREE THOUSAND.
    • VFR:
      • Circuit instructions.
      • Departure instructions.
      • Geographic/altitude restrictions.
        RIGHT HAND TURNOUT APPROVED, REMAIN NORTH OF THE LAKE.
  • wind: must be issued when the speed is 15 kts or more, but should always be issued unless the instruction is extremely time-critical.
  • operation: “FOR TAKEOFF” or “FOR THE OPTION”
    “OPTION” allows the pilot to takeoff normally or abort.
  • runway id [SHORTENED]: Append “shortened” when a portion of the runway is closed, unless the pilot is departing from an intersection beyond the closure.

For more complex rules, this table format can be used so that the detailed information is presented alongside the rules.

Use a normal Markdown table with the .syntax Table Column directive, and place a :zyzIcon{icon=zyzStPh} icon at the top of the syntax column. Use the inline lists/inline callouts directives as necessary. Further details can be found in the Internal Syntax document.

Hidden table class directive
Notes
(aircraft id)
(control instructions)IFR:
  • Contact when airborne instructions.
  • Heading instructions.
  • Altitude instructions.
    WHEN AIRBORNE CONTACT TORONTO CENTRE ON ONE-THREE-FIVE DECIMAL THREE. ON DEPARTURE TURN LEFT HEADING ONE-EIGHT-ZERO, CLIMB THREE THOUSAND.
VFR:
  • Circuit instructions.
  • Departure instructions.
  • Geographic/altitude restrictions.
    RIGHT HAND TURNOUT APPROVED, REMAIN NORTH OF THE LAKE.
[wind]Must be issued when the speed is 15 kts or more, but should always be issued unless the instruction is extremely time-critical.
[FROM (intersection)]
CLEARED (operation)“FOR TAKEOFF” or “FOR THE OPTION"
"OPTION” allows the pilot to takeoff normally or abort.
(runway id) [SHORTENED]Append “shortened” when a portion of the runway is closed, unless the pilot is departing from an intersection beyond the closure.

Use the zyzExCon and zyzExPlt callouts.

PRIME AIR FORTY-TWO ELEVEN, FLY LEFT-HAND CIRCUITS. WIND ONE-FIVE-ZERO AT TWENTY, CLEARED FOR THE OPTION RUNWAY TWO-EIGHT.
CLEARED FOR THE OPTION RUNWAY TWO-EIGHT, PRIME AIR FORTY-TWO ELEVEN.

For information that is typed or read from a screen instead of spoken, use a zyzStData callout instead for rules/syntax and a zyzExData callout for examples. For typed equivalents to spoken phraseology, present it next to the spoken equivalent:

REQUEST RELEASE (aircraft id) (runway id).
REQUEST RELEASE RAILCAR ONE RUNWAY ONE-FIVE.
RREQ (aircraft id) (runway id)
RREQ CRR1 15

METAR CYYZ 210700Z 24011G16KT 15SM OVC015 02/M01 A2974 RMK SC8 SLP081=
©2026 Virtual Toronto FIR.
The information contained in this website is to be used for flight simulation purposes only on the VATSIM network. It is not intended nor should it be used for real world navigation or air traffic control services. This site is not affiliated with NAV CANADA, the actual Toronto FIR, or any governing aviation body. All content contained herein is approved only for use on the VATSIM network.