← All free guides
Free Guide · Communications

Radio Communications & ATC Phraseology

12 chapters · glossary

Standard phraseology exists so a controller and a pilot who have never met, flying an airplane they can't see, can exchange exact, unambiguous instructions in a few seconds, on a busy frequency, in a language that isn't necessarily either party's first language. Sounding confident on the radio isn't about bravado, it's about knowing the structure well enough that you don't have to think about it in the moment.

In this guide

  1. Why Standard Phraseology Exists
  2. The Structure of a Radio Call
  3. The Phonetic Alphabet and Numbers
  4. Ground Control
  5. Tower
  6. Approach, Departure, and Center
  7. Readbacks: What Must Be Read Back
  8. Requesting Flight Following
  9. Non-Towered Airports: CTAF and Self-Announcing
  10. Lost Communications
  11. Worked Example: A Full Flight
  12. Common Mistakes and Practical Tips
  13. Glossary

1. Why Standard Phraseology Exists

Radio communication has no facial expressions, no body language, and often a weak, static-filled signal. Standard phraseology strips a message down to the smallest set of words that convey exactly one meaning, and always says the important parts (call sign, instruction, altitude, runway) in a predictable order so a listener can catch them even if part of the transmission is stepped on or garbled. It also lets every pilot and controller instantly recognize a non-standard or unclear transmission as something worth clarifying, rather than guessing at.

Key Idea Phraseology isn't about sounding professional for its own sake, it's a shared protocol that makes communication reliable under noise, time pressure, and language differences.

2. The Structure of a Radio Call

Almost every initial call follows the same shape: who you're calling, who you are, where you are, and what you want. "Bay Approach, Cessna 12345, ten miles south of Springfield at 4,500, request flight following to Meadowlake." Once a controller has your call sign established and you're in an ongoing exchange, subsequent calls drop straight to the point, no need to re-state who you're calling every time.

Practical Tip Think the whole sentence through before you key the mic. A confident, complete transmission on the first try is faster for everyone than a hesitant one that needs a "say again."

3. The Phonetic Alphabet and Numbers

The ICAO phonetic alphabet exists to make individual letters unmistakable over a noisy radio, where "B," "D," and "E" can otherwise sound nearly identical.

LetterWordLetterWord
AAlfaNNovember
BBravoOOscar
CCharliePPapa
DDeltaQQuebec
EEchoRRomeo
FFoxtrotSSierra
GGolfTTango
HHotelUUniform
IIndiaVVictor
JJuliettWWhiskey
KKiloXX-ray
LLimaYYankee
MMikeZZulu

Numbers are spoken individually (12,500 is "one two thousand five hundred," or in some contexts "one two five" for a frequency or squawk digit group), except for round thousands and altitudes, which are often spoken as a whole number followed by "thousand." "Niner" is used instead of "nine" specifically because it's harder to confuse with "five" over a weak signal.

4. Ground Control

Ground handles movement on taxiways and non-active runway areas. A typical initial call: "Springfield Ground, Cessna 12345 at the FBO, ready to taxi, information Alpha." Ground will respond with a taxi clearance specifying the route and, critically, any runway crossing instructions, which must be explicitly issued and read back.

5. Tower

Tower controls the runway environment and traffic in the immediate vicinity of the airport. Before entering a runway or the pattern, you need a clearance: to take off, to cross a runway, to enter the pattern or land. A typical clearance: "Cessna 12345, runway 27, cleared for takeoff," or "Cessna 12345, cleared to land runway 27."

Common Trap Never cross a hold-short line, or enter an active runway, without an explicit clearance to do so, even if the runway looks clear. "Taxi to runway 27" alone does not authorize crossing any other runway along the way, each crossing needs its own clearance.

6. Approach, Departure, and Center

Once airborne and outside the tower's immediate airspace, you're typically handed off to departure, then to one or more en-route Center facilities, then eventually to an approach control near your destination. Instructions from these facilities (headings, altitudes, frequency changes) use the same structural pattern as tower and ground calls, just typically covering a larger area and longer duration.

7. Readbacks: What Must Be Read Back

Certain instructions must always be read back verbatim, in full, because a misunderstanding here has immediate safety consequences: runway assignments, hold-short instructions, taxi-into-position-and-hold instructions, takeoff and landing clearances, and any altitude, heading, or frequency change instruction. "Simple" acknowledgments like a general traffic advisory can sometimes get a shorter response, but anything involving a runway should always be read back with your full call sign attached.

Why This Matters to a Pilot A readback isn't a formality, it's the controller's only way of confirming you heard the instruction correctly. If a controller doesn't hear the correct readback, they're expected to correct it immediately, but only if you actually say it back.

8. Requesting Flight Following

Flight following is a workload-permitting VFR radar advisory service, not a clearance and not guaranteed. Request it with your position, altitude, and destination: "Approach, Cessna 12345, request flight following, ten southeast of Springfield at 4,500, en route to Meadowlake." If accepted, you'll be assigned a squawk code and receive traffic advisories along your route; if the controller is too busy, they may say so plainly and you continue as before.

9. Non-Towered Airports: CTAF and Self-Announcing

At a non-towered airport, there's no controller to issue instructions, so pilots self-announce intentions on the Common Traffic Advisory Frequency (CTAF) so everyone in the pattern can build a shared picture of traffic. A typical sequence: "Springfield traffic, Cessna 12345, ten miles north, inbound, will report entering downwind, Springfield," followed later by calls entering downwind, base, and final, and finally clearing the runway. These calls are advisory, not clearances, since there's no one to issue a clearance, which makes clear, predictable radio calls even more important.

10. Lost Communications

If your radio fails, the standard guidance (14 CFR 91.185 for IFR flight, and general practice for VFR) is to fly a predictable, expected profile so ATC can anticipate your actions without talking to you: for IFR, fly the route and altitude combination that's highest of the assigned route, the expected route, or the filed route, and land as soon as practicable using best judgment. For VFR in the pattern, a light gun signal system from the tower substitutes for voice instructions (steady green for cleared to land or take off, steady red for stop, flashing red for taxi clear of the runway).

11. Worked Example: A Full Flight

Ground: "Springfield Ground, Cessna 12345, at the FBO with Alpha, request taxi for VFR departure to the north." Tower: "Cessna 12345, Springfield Tower, runway 27, cleared for takeoff." Departure: "Bay Approach, Cessna 12345, request flight following to Meadowlake." Handoff to Meadowlake's own tower near the destination: "Meadowlake Tower, Cessna 12345, ten miles south with information Bravo, inbound for landing." "Cessna 12345, Meadowlake Tower, enter left downwind runway 18, report midfield." Each exchange follows the same who/who/where/what shape from Chapter 2.

12. Common Mistakes and Practical Tips

MistakeCrossing a runway on a taxi clearance that didn't explicitly authorize that specific crossing. Every runway crossing needs its own clearance.
MistakeNot including your call sign in a readback, especially on a busy frequency where the controller needs to know exactly who just accepted an instruction.
MistakeStepping on another transmission by keying the mic without listening first. A brief pause to listen prevents most "blocked" transmissions.
Practical TipListen to live ATC audio from a busy towered airport before you fly there yourself; hearing the real rhythm and phrasing does more than reading a script.
Practical TipIf you don't understand an instruction, say "say again" immediately rather than guessing. A short delay for clarification is always better than acting on a misheard instruction.

Glossary

CTAF
Common Traffic Advisory Frequency, used to self-announce position and intentions at a non-towered airport.
Readback
Repeating an instruction back to the controller to confirm it was received and understood correctly.
Flight following
A workload-permitting VFR radar traffic advisory service, not a clearance.
Hold short
An instruction not to cross a specific line (usually a runway boundary) until explicitly cleared to do so.
Position and hold
An instruction to taxi onto the runway and wait, without a takeoff clearance yet.
Phonetic alphabet
The standardized set of words (Alfa, Bravo, Charlie...) used to spell out letters unambiguously over radio.
Squawk code
A four-digit transponder code assigned by ATC to identify a specific aircraft on radar.
Light gun signals
A backup visual signaling system tower uses to communicate with aircraft that have lost radio contact.

Want more free guides like this one?

Browse all free guides

This guide is intended for educational and training purposes only. It is not a substitute for official FAA publications, an authorized ground school, or qualified flight instruction, and should not be used as a sole source for real-world flight planning, dispatch, or operational decisions.