ATC and Online Flying

VATSIM Radio Phraseology for Beginners

Beginner's guide to VATSIM radio phraseology: what to read back, key phrases, example calls for every phase of flight, FAA vs ICAO differences and UNICOM.

On this page
  1. The three rules that cover most calls
  2. Alphabet and numbers
  3. What to read back (and what not to)
  4. Key words and phrases
  5. A flight, call by call
  6. FAA vs ICAO differences
  7. Flying with no ATC: UNICOM
  8. When you don’t understand
  9. Practising before your first flight

The three rules that cover most calls

Radio phraseology exists to make messages clear, unambiguous and short, because everyone on a frequency shares the same airtime. For a first call to any station, remember:

  1. Who you are calling, and who you are. “London Ground, Speedbird 123.”
  2. Where you are. “Stand 24.” / “Ten miles south, two thousand five hundred feet.”
  3. What you want. “Request pushback.” / “Request VFR transit.”

After the first contact, keep calls short and lead with your callsign or the station you are calling. Controllers on VATSIM are used to beginners, and if your flight plan remarks say you are new, many will slow down and help.

Alphabet and numbers

Learn the phonetic alphabet (Alpha, Bravo, Charlie…) until it is automatic. You will use it for callsigns, taxiways, ATIS letters and waypoints.

Numbers are usually spoken digit by digit: heading 270 is “heading two seven zero”, and squawk 4521 is “squawk four five two one”. ICAO pronunciation uses “tree” for 3, “fife” for 5 and “niner” for 9 to make them clearer over the radio. Round thousands of feet are usually said as “two thousand five hundred feet”, and flight levels as “flight level three five zero”.

Frequencies are spoken digit by digit with “decimal” in ICAO regions (“one two one decimal eight”) and often “point” in the US.

What to read back (and what not to)

Controllers send several types of message, and each needs a different response:

ATC sends Example Your response
Clearance “Cleared to Manchester…” Read it back in full
Instruction “Turn left heading 300, descend 4000 feet” Read it back
Approval “High speed approved” Read it back
Request for information “Advise when ready for departure” Answer or confirm
Information “Wind 250 degrees 6 knots” Not read back; acknowledge if needed

As a rule, always read back runway instructions (taxi, hold short, line up, takeoff and landing clearances), altitudes, headings, speeds, squawk codes, frequencies and altimeter settings. Finish your readback with your callsign.

Key words and phrases

Phrase Meaning
Roger I have received your message. (Not “yes”.)
Wilco I understand and will comply.
Affirm Yes.
Negative No.
Unable I cannot comply. Say this promptly if an instruction is unsafe or impossible for you.
Say again Repeat your message. Say “say again” plus the part you missed, e.g. “say again altitude”.
Standby Wait; I will call you back. It is not an approval.
Request I would like…
Go ahead Send your message.

Avoid “please repeat”, “okay” or casual chat on frequency. If something needs a longer explanation, a private text message to the controller is often better.

A flight, call by call

The examples below are illustrative and use an airline callsign, Speedbird 123. Real calls depend on the airport, region and controller.

ATIS. Listen to the ATIS first and note the letter, runway and altimeter setting.

Clearance.

  • You: “Delivery, Speedbird 123, stand 24, information Bravo, request IFR clearance to Manchester.”
  • ATC: “Speedbird 123, cleared to Manchester via the ABCDE 1A departure, runway 27, climb altitude 6000 feet, squawk 4521.”
  • You: “Cleared to Manchester, ABCDE 1A departure, runway 27, climb altitude 6000 feet, squawk 4521, Speedbird 123.”

Pushback and start.

  • You: “Ground, Speedbird 123, stand 24, request pushback.”
  • ATC: “Speedbird 123, push and start approved, face east.”
  • You: “Push and start approved, face east, Speedbird 123.”

Taxi.

  • You: “Speedbird 123, request taxi.”
  • ATC: “Speedbird 123, taxi to holding point runway 27 via Alpha, Bravo.”
  • You: “Taxi to holding point runway 27 via Alpha, Bravo, Speedbird 123.”

Takeoff.

  • You: “Tower, Speedbird 123, holding point runway 27, ready for departure.”
  • ATC: “Speedbird 123, runway 27, cleared for takeoff, wind 260 degrees 8 knots.”
  • You: “Runway 27, cleared for takeoff, Speedbird 123.”

Departure. When handed off, read back the new frequency, change to it, and check in with your altitude:

  • You: “Departure, Speedbird 123, passing 2500 feet climbing 6000 feet, ABCDE 1A.”

En route. Read back level changes, headings and direct routings, and check in with each new controller with your current level.

Arrival and approach. Read back descent clearances, altimeter settings, headings, speeds and approach clearances, for example: “Cleared ILS approach runway 23, Speedbird 123.”

Landing. “Runway 23, cleared to land, Speedbird 123.”

Taxi in. After vacating the runway, contact ground: “Ground, Speedbird 123, runway 23 vacated, request taxi to stand.”

FAA vs ICAO differences

VATSIM controllers use the phraseology of the country they are controlling, so you will hear differences:

United States (FAA) Most ICAO regions
Climb or descend “Climb and maintain 5000” “Climb altitude 5000 feet” or “Climb flight level 70”
Altimeter “Altimeter two niner niner two” (inches of mercury) “QNH 1013” (hectopascals)
Transition altitude 18,000 feet across the country Varies by airport or country
Taxi “Runway 27, taxi via Alpha, Bravo” “Taxi to holding point runway 27 via Alpha, Bravo”
Frequency decimal “point” “decimal”

Follow what the controller says and read back in the same style. Division websites often publish local pilot guides that are worth reading before flying somewhere new.

Flying with no ATC: UNICOM

If no controller covers your area, VATSIM pilots use the UNICOM frequency, 122.800, to coordinate with each other. Announce your intentions at key points such as taxi, takeoff, joining the circuit and landing, commonly by text message, for example: “Bristol traffic, Speedbird 123, taxiing to runway 27.” Keep it brief and check local guidance, since some regions have their own conventions.

When you don’t understand

  • Say “say again” and the part you missed.
  • If you cannot comply, say “unable” immediately rather than accepting and improvising.
  • If you are lost or overwhelmed, tell the controller plainly: “Speedbird 123, new to VATSIM, request progressive taxi” or “request vectors”. Honesty is far better than guessing.
  • Use text if voice is not working, or if you need to explain something complex.

Practising before your first flight

  • Listen to real-world ATC on LiveATC.net, or listen in on a VATSIM frequency as an observer.
  • Say calls out loud when flying offline, or practise with an AI ATC tool; see AI ATC add-ons for MSFS.
  • Write your expected clearance on a notepad before calling, so you only need to fill in the gaps.
  • Pick a quiet airport with a controller online for your first flight.

When you are ready, file your plan using how to file a VATSIM flight plan and connect with how to connect MSFS to VATSIM with vPilot. If you want structured coaching, VATSIM’s optional training is covered in VATSIM pilot ratings explained.

The complete guide to atc and online flying

ATC in Microsoft Flight Simulator: Default AI vs Real Controllers
Read the guide

Keep exploring

Guides from other topics

All topics →