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

# Radio Phraseology

> Complete radio phraseology reference for VATSIM pilots - standard calls, readbacks, and ATC communication for every phase of flight from clearance to shutdown

export const RadioExchange = ({exchanges, title}) => <div className="radio-exchange">
    {title && <div className="radio-exchange-title">{title}</div>}
    <div className="radio-exchange-body">
      {exchanges.map((ex, i) => <div key={i} className={`radio-line radio-line-${ex.from?.toLowerCase()}`}>
          <span className="radio-tag">{ex.from}</span>
          <span className="radio-msg">{ex.msg}</span>
        </div>)}
    </div>
  </div>;

This page is your complete reference for communicating with ATC on VATSIM. Every call, every readback, and every phase of flight is covered here with realistic examples. Use standard ICAO phraseology and you will sound professional from your very first flight.

<Info>
  ATC controllers on VATSIM are volunteers who do this because they enjoy it. If you make a mistake on the radio, simply say **"Correction"** and try again. Controllers will help you through it - everyone was new once. Do not let fear of making a mistake stop you from flying online.
</Info>

## Flight Phase Phraseology

<Tabs>
  <Tab title="IFR Clearance">
    ### Requesting Your IFR Clearance

    Before you push back from the gate, you need your **IFR clearance** from Delivery (or whichever controller is providing that service under top-down coverage). This tells you exactly how you are authorized to fly to your destination.

    #### When to Contact Delivery

    * After you have listened to the ATIS and noted the information letter
    * After you have programmed your FMS and are ready to copy your clearance
    * Before requesting pushback or taxi

    #### The CRAFT Mnemonic

    ATC will issue your clearance following the **CRAFT** format. Have a pen ready (or a notepad app) and write down each element:

    | Letter | Element              | Example                                                              |
    | ------ | -------------------- | -------------------------------------------------------------------- |
    | **C**  | Clearance limit      | "Cleared to Montreal" (your destination)                             |
    | **R**  | Route                | "Via the DEDKI3 departure, AVSEP transition, flight planned route"   |
    | **A**  | Altitude             | "Climb via SID, expect flight level 350 ten minutes after departure" |
    | **F**  | Frequency            | "Contact Ground 121.9 when ready to push"                            |
    | **T**  | Transponder (Squawk) | "Squawk 4521"                                                        |

    #### Full Clearance Exchange

    <RadioExchange
      title="Requesting IFR Clearance"
      exchanges={[
    { from: "PILOT", msg: "Toronto Delivery, Air Canada 456, at gate Charlie 32, Airbus A320, request IFR clearance to Montreal with information Bravo." },
    { from: "ATC", msg: "Air Canada 456, Toronto Delivery, cleared to Montreal via the DEDKI3 departure, AVSEP transition, flight planned route. Climb via SID, expect flight level 350 ten minutes after departure. Squawk 4521." },
    { from: "PILOT", msg: "Cleared to Montreal, DEDKI3 departure, AVSEP transition, flight planned route. Climb via SID, expect flight level 350 ten minutes after departure, squawk 4521. Air Canada 456." },
    { from: "ATC", msg: "Air Canada 456, readback correct. Contact Ground 121.9 when ready to push." },
    { from: "PILOT", msg: "Contact Ground 121.9, Air Canada 456." },
  ]}
    />

    #### What You Must Read Back

    * Clearance limit (destination)
    * Full route including SID and transitions
    * Altitude instructions (initial and expected)
    * Squawk code

    <Tip>
      Write down the clearance before reading it back. It is completely acceptable to say **"Say again"** if you missed part of the clearance. You can also ask **"Say again the route"** to get just one element repeated. Take your time - accuracy matters more than speed.
    </Tip>

    #### If You Get a Reroute

    Sometimes ATC will change your filed route. If the new clearance is significantly different from what you filed, you may need a moment to reprogram your FMS.

    <RadioExchange
      title="Requesting Time to Program a Reroute"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, cleared to Montreal via the OAKVL3 departure, radar vectors BAGEL, direct. Climb via SID, expect flight level 350. Squawk 4521." },
    { from: "PILOT", msg: "Air Canada 456, standby to copy." },
    { from: "PILOT", msg: "Air Canada 456, ready to copy." },
    { from: "ATC", msg: "Air Canada 456, cleared to Montreal via the OAKVL3 departure, radar vectors BAGEL, direct. Climb via SID, expect flight level 350. Squawk 4521." },
    { from: "PILOT", msg: "Cleared to Montreal, OAKVL3 departure, radar vectors BAGEL, direct. Climb via SID, expect flight level 350, squawk 4521. Air Canada 456." },
  ]}
    />

    #### Common Mistakes at This Phase

    * Not listening to ATIS before calling Delivery
    * Forgetting to include the ATIS letter in your initial call
    * Reading back only part of the clearance (you must read back the full clearance)
    * Not writing it down and then fumbling the readback
  </Tab>

  <Tab title="Pushback and Taxi">
    ### Pushback and Taxi

    After receiving your IFR clearance, Delivery will instruct you to contact **Ground** when you are ready to push. Ground controls all movement on taxiways and ramp areas.

    #### Requesting Pushback

    <RadioExchange
      title="Requesting Pushback"
      exchanges={[
    { from: "PILOT", msg: "Toronto Ground, Air Canada 456, gate Charlie 32, request pushback." },
    { from: "ATC", msg: "Air Canada 456, pushback approved, face south." },
    { from: "PILOT", msg: "Pushback approved, facing south, Air Canada 456." },
  ]}
    />

    ATC may specify a direction to face after pushback. This ensures your aircraft is pointed the right way for the taxi route.

    #### Requesting Taxi

    Once pushback is complete and engines are running, call Ground for taxi instructions.

    <RadioExchange
      title="Requesting Taxi"
      exchanges={[
    { from: "PILOT", msg: "Toronto Ground, Air Canada 456, ready to taxi." },
    { from: "ATC", msg: "Air Canada 456, taxi to runway 05 via Alpha, Bravo, hold short runway 06L." },
    { from: "PILOT", msg: "Taxi to runway 05 via Alpha, Bravo, hold short runway 06L, Air Canada 456." },
  ]}
    />

    #### Complex Taxi Routes

    At large airports, taxi instructions may be long. If you are unsure of the route, ask for progressive taxi instructions.

    <RadioExchange
      title="Requesting Progressive Taxi"
      exchanges={[
    { from: "PILOT", msg: "Toronto Ground, Air Canada 456, unfamiliar with the airport, request progressive taxi." },
    { from: "ATC", msg: "Air Canada 456, no problem. Turn left on Alpha, continue to the intersection with Bravo, then turn right on Bravo. I will call you at the next turn." },
    { from: "PILOT", msg: "Left on Alpha, right on Bravo, Air Canada 456." },
  ]}
    />

    #### What You Must Read Back

    * Runway assignment
    * Complete taxi route
    * Any hold short instructions

    <Warning>
      **Always read back hold short instructions.** Failure to hold short of a runway is one of the most serious errors a pilot can make. If ATC says "hold short runway 06L," you must repeat it back word for word and stop your aircraft before reaching that runway.
    </Warning>

    #### Common Mistakes at This Phase

    * Calling for taxi before completing pushback
    * Not reading back the full taxi route
    * Missing or ignoring hold short instructions
    * Taxiing before receiving explicit taxi instructions
    * Crossing a runway without clearance
  </Tab>

  <Tab title="Takeoff and Departure">
    ### Takeoff and Departure

    When you reach the departure runway, Ground will hand you off to **Tower**. Tower controls the runway and issues takeoff clearances.

    #### "Monitor" vs "Contact" - Critical Difference

    Pay close attention to the wording when Ground sends you to Tower:

    | Instruction               | What It Means                      | What You Do                                                        |
    | ------------------------- | ---------------------------------- | ------------------------------------------------------------------ |
    | **"Contact Tower 118.7"** | Tune the frequency AND call them   | Switch to 118.7 and announce yourself                              |
    | **"Monitor Tower 118.7"** | Tune the frequency but do NOT call | Switch to 118.7 and wait silently. Tower will call you when ready. |

    <Warning>
      If told to **monitor**, do not transmit. Tower knows you are there and will call you when it is your turn. Calling in when told to monitor creates unnecessary frequency congestion.
    </Warning>

    #### Ready for Departure

    <RadioExchange
      title="Ready for Departure"
      exchanges={[
    { from: "PILOT", msg: "Toronto Tower, Air Canada 456, runway 05, ready for departure." },
    { from: "ATC", msg: "Air Canada 456, winds 040 at 8, runway 05, cleared for takeoff." },
    { from: "PILOT", msg: "Cleared for takeoff, runway 05, Air Canada 456." },
  ]}
    />

    #### Line Up and Wait

    Sometimes Tower will position you on the runway but not clear you for takeoff yet. This is called **"line up and wait"** (or "position and hold" in older phraseology).

    <RadioExchange
      title="Line Up and Wait"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, runway 05, line up and wait." },
    { from: "PILOT", msg: "Line up and wait, runway 05, Air Canada 456." },
    { from: "ATC", msg: "Air Canada 456, winds 040 at 8, runway 05, cleared for takeoff." },
    { from: "PILOT", msg: "Cleared for takeoff, runway 05, Air Canada 456." },
  ]}
    />

    #### Departure Handoff

    After takeoff, Tower will hand you off to **Departure** (or directly to Center if Departure is not online).

    <RadioExchange
      title="Departure Handoff"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, contact Toronto Departure 126.4." },
    { from: "PILOT", msg: "Departure 126.4, Air Canada 456." },
  ]}
    />

    When you check in on the new frequency, state your callsign, current altitude, and the altitude you are climbing to.

    <RadioExchange
      title="Checking In with Departure"
      exchanges={[
    { from: "PILOT", msg: "Toronto Departure, Air Canada 456, passing 3,000, climbing flight level 350." },
    { from: "ATC", msg: "Air Canada 456, Toronto Departure, radar contact. Climb flight level 350." },
    { from: "PILOT", msg: "Climbing flight level 350, Air Canada 456." },
  ]}
    />

    #### Departure Instructions

    Departure may issue vectors (headings), altitude changes, or speed restrictions as you climb out of the terminal area.

    <RadioExchange
      title="Receiving Vectors After Departure"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, turn right heading 090, climb and maintain flight level 240." },
    { from: "PILOT", msg: "Right heading 090, climb and maintain flight level 240, Air Canada 456." },
  ]}
    />

    #### Common Mistakes at This Phase

    * Calling Tower when told to "monitor"
    * Not reading back the takeoff clearance
    * Forgetting to include current altitude when checking in with Departure
    * Taking off without an explicit "cleared for takeoff" from Tower
  </Tab>

  <Tab title="En Route">
    ### En Route (Cruise)

    Once you leave the terminal area, Departure hands you off to **Center** (en route control). Center manages aircraft at cruise altitude across large sectors of airspace.

    #### Checking In with Center

    Keep your initial call brief. State your callsign and current flight level.

    <RadioExchange
      title="Center Check-in"
      exchanges={[
    { from: "PILOT", msg: "Montreal Center, Air Canada 456, flight level 350." },
    { from: "ATC", msg: "Air Canada 456, Montreal Center, radar contact." },
  ]}
    />

    That is it. Center has your flight plan on their scope. You do not need to repeat your destination or route unless asked.

    #### Requesting a Flight Level Change

    If you want to climb or descend, make a request. ATC may approve it immediately, delay it, or offer an alternative.

    <RadioExchange
      title="Requesting Flight Level Change"
      exchanges={[
    { from: "PILOT", msg: "Montreal Center, Air Canada 456, request flight level 370." },
    { from: "ATC", msg: "Air Canada 456, climb flight level 370." },
    { from: "PILOT", msg: "Climbing flight level 370, Air Canada 456." },
  ]}
    />

    <RadioExchange
      title="Flight Level Change Denied"
      exchanges={[
    { from: "PILOT", msg: "Montreal Center, Air Canada 456, request flight level 390." },
    { from: "ATC", msg: "Air Canada 456, unable flight level 390 due traffic. I can offer flight level 370 or flight level 410." },
    { from: "PILOT", msg: "We will take flight level 410, Air Canada 456." },
    { from: "ATC", msg: "Air Canada 456, climb flight level 410." },
    { from: "PILOT", msg: "Climbing flight level 410, Air Canada 456." },
  ]}
    />

    #### Requesting Direct to a Waypoint

    <RadioExchange
      title="Direct Request"
      exchanges={[
    { from: "PILOT", msg: "Montreal Center, Air Canada 456, request direct CYUL." },
    { from: "ATC", msg: "Air Canada 456, cleared direct CYUL." },
    { from: "PILOT", msg: "Direct CYUL, Air Canada 456." },
  ]}
    />

    #### Requesting a Speed Change

    <RadioExchange
      title="Speed Change Request"
      exchanges={[
    { from: "PILOT", msg: "Montreal Center, Air Canada 456, request Mach 0.84." },
    { from: "ATC", msg: "Air Canada 456, Mach 0.84 approved." },
    { from: "PILOT", msg: "Mach 0.84, Air Canada 456." },
  ]}
    />

    #### Sector Handoffs

    As you fly across the country, you will be handed off between Center sectors. Each handoff follows the same pattern.

    <RadioExchange
      title="Center-to-Center Handoff"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, contact Moncton Center 132.2." },
    { from: "PILOT", msg: "Moncton Center 132.2, Air Canada 456." },
    { from: "PILOT", msg: "Moncton Center, Air Canada 456, flight level 370." },
    { from: "ATC", msg: "Air Canada 456, Moncton Center, radar contact." },
  ]}
    />

    #### Reporting Weather Deviations

    If you need to deviate around weather, let ATC know.

    <RadioExchange
      title="Weather Deviation Request"
      exchanges={[
    { from: "PILOT", msg: "Montreal Center, Air Canada 456, request 20 miles right of course for weather." },
    { from: "ATC", msg: "Air Canada 456, deviation right of course approved. Report back on course." },
    { from: "PILOT", msg: "Deviation right approved, will report back on course, Air Canada 456." },
  ]}
    />

    #### Common Mistakes at This Phase

    * Giving a long check-in with unnecessary details (keep it to callsign and flight level)
    * Forgetting to read back altitude assignments
    * Not reporting back on course after a weather deviation
  </Tab>

  <Tab title="Approach">
    ### Approach and Descent

    As you approach your destination, Center will hand you off to **Approach** (also called Terminal or TRACON). Approach controls the airspace around the airport and sequences arriving aircraft onto the final approach.

    #### Before Contacting Approach

    Make sure you have:

    * Listened to the destination ATIS and noted the information letter
    * Briefed the expected approach (check the ATIS for the active runway and approach type)
    * Set up your FMS for the arrival and approach

    #### Initial Contact with Approach

    Include your current altitude, the ATIS information you have, and what approach you are expecting.

    <RadioExchange
      title="Initial Contact with Approach"
      exchanges={[
    { from: "PILOT", msg: "Montreal Approach, Air Canada 456, descending flight level 240, information Delta, expecting ILS runway 24R." },
    { from: "ATC", msg: "Air Canada 456, Montreal Approach, expect vectors ILS runway 24R. Descend flight level 120." },
    { from: "PILOT", msg: "Descend flight level 120, expecting vectors ILS 24R, Air Canada 456." },
  ]}
    />

    #### Receiving Vectors

    Approach will issue headings and altitudes to sequence you for the approach.

    <RadioExchange
      title="Vectors for the Approach"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, turn left heading 180, descend and maintain 4,000." },
    { from: "PILOT", msg: "Left heading 180, descend and maintain 4,000, Air Canada 456." },
  ]}
    />

    #### Speed Assignments

    Approach may assign speeds to manage spacing between arriving aircraft.

    <RadioExchange
      title="Speed Assignment"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, reduce speed 210 knots." },
    { from: "PILOT", msg: "Speed 210 knots, Air Canada 456." },
  ]}
    />

    #### Approach Clearance

    This is the clearance to fly the published instrument approach procedure.

    <RadioExchange
      title="Cleared for the Approach"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, turn right heading 210, maintain 3,000 until established on the localizer, cleared ILS runway 24R approach." },
    { from: "PILOT", msg: "Right heading 210, maintain 3,000 until established, cleared ILS runway 24R approach, Air Canada 456." },
  ]}
    />

    <RadioExchange
      title="Visual Approach Clearance"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, the airport is at your 1 o'clock, 8 miles. Report the field in sight." },
    { from: "PILOT", msg: "Looking for the field, Air Canada 456." },
    { from: "PILOT", msg: "Air Canada 456, field in sight." },
    { from: "ATC", msg: "Air Canada 456, cleared visual approach runway 24R." },
    { from: "PILOT", msg: "Cleared visual approach runway 24R, Air Canada 456." },
  ]}
    />

    #### Common Mistakes at This Phase

    * Not getting the ATIS before contacting Approach
    * Forgetting to include the ATIS letter in the check-in
    * Not reading back altitude restrictions in the approach clearance
    * Descending below assigned altitude before being cleared for the approach
  </Tab>

  <Tab title="Landing">
    ### Landing

    Approach will hand you off to **Tower** for the final portion of your flight. Tower controls the runway and issues landing clearances.

    #### Checking In with Tower

    <RadioExchange
      title="Checking In with Tower on Final"
      exchanges={[
    { from: "PILOT", msg: "Montreal Tower, Air Canada 456, ILS 24R, 8 miles final." },
    { from: "ATC", msg: "Air Canada 456, Montreal Tower, winds 250 at 12, runway 24R, cleared to land." },
    { from: "PILOT", msg: "Cleared to land, runway 24R, Air Canada 456." },
  ]}
    />

    #### Go-Around

    If ATC instructs you to go around, or if you decide to go around on your own, the call is straightforward.

    <RadioExchange
      title="Go-Around (ATC Instructed)"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, go around. Fly runway heading, climb 3,000." },
    { from: "PILOT", msg: "Going around, runway heading, climbing 3,000, Air Canada 456." },
  ]}
    />

    <RadioExchange
      title="Pilot-Initiated Go-Around"
      exchanges={[
    { from: "PILOT", msg: "Air Canada 456, going around." },
    { from: "ATC", msg: "Air Canada 456, roger. Fly runway heading, climb 3,000, contact Approach 119.1." },
    { from: "PILOT", msg: "Runway heading, climbing 3,000, Approach 119.1, Air Canada 456." },
  ]}
    />

    #### Vacating the Runway

    After landing, exit the runway promptly. Tower will tell you which taxiway to use and hand you off to Ground.

    <RadioExchange
      title="Vacating the Runway"
      exchanges={[
    { from: "ATC", msg: "Air Canada 456, turn right on Bravo, contact Ground 121.9." },
    { from: "PILOT", msg: "Right on Bravo, Ground 121.9, Air Canada 456." },
  ]}
    />

    <Tip>
      Do not stop on the runway to complete checklists. Exit the runway first, then run your after-landing checklist once you are clear on the taxiway.
    </Tip>

    #### Common Mistakes at This Phase

    * Landing without receiving an explicit "cleared to land" from Tower
    * Not reading back the landing clearance
    * Stopping on the runway after landing instead of vacating promptly
    * Forgetting to switch to Ground frequency after exiting the runway
  </Tab>

  <Tab title="Taxi In and Shutdown">
    ### Taxi to Gate and Shutdown

    After vacating the runway and switching to **Ground**, you request taxi to your gate or parking position.

    #### Requesting Taxi to Gate

    <RadioExchange
      title="Taxi to Gate"
      exchanges={[
    { from: "PILOT", msg: "Montreal Ground, Air Canada 456, runway 24R vacated at Bravo, request taxi to gate." },
    { from: "ATC", msg: "Air Canada 456, taxi to terminal via Bravo, Alpha." },
    { from: "PILOT", msg: "Taxi to terminal via Bravo, Alpha, Air Canada 456." },
  ]}
    />

    #### Requesting a Specific Gate

    If you know your assigned gate, you can mention it.

    <RadioExchange
      title="Requesting Specific Gate"
      exchanges={[
    { from: "PILOT", msg: "Montreal Ground, Air Canada 456, runway 24R vacated at Bravo, request taxi to gate Bravo 21." },
    { from: "ATC", msg: "Air Canada 456, taxi to gate Bravo 21 via Bravo, Alpha, Lima." },
    { from: "PILOT", msg: "Taxi to gate Bravo 21 via Bravo, Alpha, Lima, Air Canada 456." },
  ]}
    />

    #### Shutting Down

    Once at the gate, you can simply disconnect from the network. There is no required radio call to shut down on VATSIM. However, if you want to be thorough, a brief goodbye is always appreciated.

    <RadioExchange
      title="Closing Out (Optional)"
      exchanges={[
    { from: "PILOT", msg: "Montreal Ground, Air Canada 456 is at the gate, shutting down. Thanks for the service." },
    { from: "ATC", msg: "Air Canada 456, welcome to Montreal. Good day." },
  ]}
    />

    #### Common Mistakes at This Phase

    * Disconnecting on the runway or taxiway (always taxi to a gate or parking spot first)
    * Not reading back the taxi route
  </Tab>
</Tabs>

## Readback Requirements

Certain items **must always** be read back to ATC. If you fail to read back a required item, ATC will ask you to confirm. Here is the complete list:

| Item                    | Example Readback                                   |
| ----------------------- | -------------------------------------------------- |
| Runway assignments      | "Runway 05"                                        |
| Altimeter settings      | "Altimeter 29.92"                                  |
| Altitude / flight level | "Flight level 350" or "Descend and maintain 4,000" |
| Heading assignments     | "Heading 210"                                      |
| Speed assignments       | "Speed 250 knots"                                  |
| Frequency changes       | "Contact Departure 126.4"                          |
| Squawk codes            | "Squawk 4521"                                      |
| Hold short instructions | "Hold short runway 06L"                            |
| Route clearances        | Full clearance readback                            |
| Approach clearances     | "Cleared ILS runway 24R approach"                  |

<Note>
  When in doubt, read it back. ATC will never be annoyed by a pilot confirming an instruction. It is far better to read back too much than too little.
</Note>

## Essential Words and Phrases

These standard aviation terms have specific meanings. Use them correctly and your communication will be clear and professional.

| Word / Phrase         | Meaning                                                                                   |
| --------------------- | ----------------------------------------------------------------------------------------- |
| **Roger**             | "I have received and understood your message." Does NOT mean "yes."                       |
| **Wilco**             | "I will comply with your instruction." Only use when no readback is required.             |
| **Affirm**            | "Yes." Use this instead of "yes" on the radio.                                            |
| **Negative**          | "No." Use this instead of "no" on the radio.                                              |
| **Say again**         | "Please repeat your last message."                                                        |
| **Correction**        | "I made an error. The correct information is..."                                          |
| **Unable**            | "I cannot comply with that instruction." Always state the reason if possible.             |
| **Standby**           | "Wait, I will get back to you."                                                           |
| **Go ahead**          | "Proceed with your message." Used when ATC is ready to hear your request.                 |
| **Read back correct** | ATC confirming that your readback was accurate.                                           |
| **How do you read**   | "How is my signal quality?" Answered on a scale of 1 (unreadable) to 5 (perfectly clear). |
| **Mayday**            | Emergency distress call. Only use in genuine emergencies (with ATC permission on VATSIM). |
| **Pan-Pan**           | Urgency call, less severe than Mayday.                                                    |

## Common Mistakes

<AccordionGroup>
  <Accordion title="Saying &#x22;Roger Wilco&#x22;">
    "Roger" means "I received your message." "Wilco" means "I will comply." Using both together is redundant - pick one. In most cases, a proper readback is better than either.
  </Accordion>

  <Accordion title="Saying &#x22;Roger&#x22; when a readback is required">
    If ATC gives you an altitude, heading, frequency, squawk code, or hold short instruction, you must read back the specific information. Saying "Roger" alone is not sufficient. For example, if ATC says "descend flight level 240," your response should be "descend flight level 240, Air Canada 456" - not just "Roger."
  </Accordion>

  <Accordion title="Starting transmissions with long pauses or filler words">
    Do not start your transmission with "Uhhhh" or a long pause. Think about what you want to say before pressing PTT. Press the button, pause for half a second, then speak clearly and concisely.
  </Accordion>

  <Accordion title="Not saying your callsign at the end of transmissions">
    Every pilot transmission should end with your callsign. This confirms to ATC who is speaking, especially when multiple aircraft are on frequency. "Climbing flight level 350, Air Canada 456" is correct. "Climbing flight level 350" by itself leaves ATC guessing.
  </Accordion>

  <Accordion title="Using &#x22;Over&#x22; or &#x22;Over and out&#x22;">
    These phrases are not standard in aviation radio communication. Do not use them. Simply end your transmission with your callsign.
  </Accordion>

  <Accordion title="Reading back the wrong ATIS letter">
    Always double-check which ATIS information you have before contacting ATC. If you say "information Bravo" but the current ATIS is Charlie, ATC will ask you to get the updated information, which delays everyone.
  </Accordion>

  <Accordion title="Speaking too fast">
    Speak at a normal, measured pace. Controllers are often handling multiple aircraft and need to understand you clearly. If English is not your first language, speaking slowly is even more important - and perfectly normal. Clarity always beats speed.
  </Accordion>

  <Accordion title="Not knowing what to say and freezing up">
    If you blank on the correct phraseology, just say what you need in plain English. "Air Canada 456 needs to descend" is perfectly fine. ATC will work with you. The worst thing you can do is sit in silence and not communicate at all.
  </Accordion>
</AccordionGroup>

## Quick Reference: Call Structure

Every radio call follows the same basic structure:

1. **Who you are calling**: "Toronto Ground"
2. **Who you are**: "Air Canada 456"
3. **Where you are** (if relevant): "Gate Charlie 32" or "Flight level 350"
4. **What you want**: "Request pushback" or "Request IFR clearance to Montreal"
5. **Additional info**: "With information Bravo"

After the initial call, subsequent transmissions are shorter - just the readback or request followed by your callsign.

## Next Steps

<CardGroup cols={2}>
  <Card title="ATC Interaction" icon="tower-control" href="/vatsim/communication/atc-interaction">
    Learn how ATC positions work, top-down coverage, and handoff procedures
  </Card>

  <Card title="Voice Basics" icon="tower-broadcast" href="/vatsim/communication/voice-basics">
    Set up your audio, understand frequencies, and learn about UNICOM
  </Card>
</CardGroup>