Classroom · Radio & ATC
Aviation Radio, ATC & Phraseology: What to Say and When
The radio scares more student pilots than crosswinds do — not because it is hard, but because it feels like a foreign language spoken at machine-gun speed. It is not. Every transmission is built from the same small kit of parts: a four-part call, a phonetic alphabet, a handful of standard words that mean exactly one thing each, and a fixed set of procedures for towered fields, non-towered fields, transponder codes, light signals, and lost communications. Learn the kit once and any frequency becomes predictable. This lesson teaches all of it, in order, with an original diagram for every idea and a full flight’s worth of real calls at the end.
Why the radio feels hard — and the fix
New pilots hear a controller rattle off a taxi clearance and panic because it sounds like undifferentiated noise. Experienced pilots hear the same transmission as a short list of expected fields in a fixed order — call sign, then instruction, then a runway, then a hold-short point — and they simply write it down. The difference is not talent or a “good radio ear.” It is knowing the structure in advance, so you are matching what you hear against a template instead of decoding it cold.
That is the whole secret of aviation communication: it is standardized on purpose. The FAA lays out recommended phraseology in the Aeronautical Information Manual (AIM) precisely so that a pilot in Alaska and a controller in Atlanta build and parse the same sentences the same way. Standard phraseology is brief, unambiguous, and predictable — and predictability is what lets you talk and fly the airplane at the same time. Your job as a student is to internalize the templates until building a call takes no more thought than reading a checklist.
This lesson is part of the FlightPerformanceCalc Classroom. Work through it once for understanding, then drill the pieces — phonetics, standard words, transponder codes, light signals — with the radio & ATC flashcard deck until they surface instantly.
Key idea Radio work is not improvised. It is a small set of templates assembled in a fixed order. Learn the templates and every transmission — yours and the controller’s — becomes a checklist you run, not a puzzle you solve.
The four-part call: who, who, where, what
Almost every initial call you make to a facility — ground, tower, approach, center, or a UNICOM operator — is built from the same four parts, in the same order:
- Who you’re calling — the facility’s name and function (“Palo Alto Tower”).
- Who you are — your full call sign, usually aircraft type plus the tail number (“Skyhawk 12345”).
- Where you are — your position, and altitude if airborne (“ten miles south”).
- What you want — your request or intention (“landing with information Bravo”).
Chain them and you get a complete, unambiguous call that tells the controller everything needed to slot you into the picture:
Once you are in two-way contact and the controller is working you, you can shorten things — you don’t re-state your position on every call — but the initial call and any request should carry all four parts. When in doubt, over-communicate: a slightly long but complete call is far better than a terse one the controller has to chase.
Listen before you key Before that first call, listen to the frequency for a few seconds and build the whole sentence in your head. Key the mic only when you have all four parts ready and no one else is talking. Stepping on another transmission — “blocking” — erases both, so a two-second pause to listen is never wasted.
The phonetic alphabet
Radio is noisy, and many letters sound alike — B, C, D, E, G, P, T, V, Z are nearly indistinguishable through static. The ICAO phonetic alphabet replaces each letter with a purpose-built word that survives a bad signal. You spell your tail number, an intersection, a runway exit, or an ATIS code letter with it, and you hear controllers use it constantly. This is the single highest-value thing to memorize cold.
Speaking numbers
Numbers on the radio are spoken digit by digit, not as ordinary quantities. A heading of 270 is “two seven zero,” not “two hundred seventy.” A tail number ending 45 is “four five.” A frequency of 121.9 is “one two one point niner.” (Altitudes are the common exception: the thousands and hundreds are grouped, so 5,500 is “five thousand five hundred.”) Speaking each digit removes ambiguity that whole-number phrasing invites over a scratchy channel.
Three digits get a deliberately distorted pronunciation so they can’t be confused with other words or with each other:
“Niner” keeps nine from being heard as the German nein or as five; “tree” and “fife” sharpen sounds that mush together in noise. So heading 350 at 5,500 is “heading tree fife zero, five thousand fife hundred,” and squawk 1200 is “squawk one two zero zero.”
Standard words — and what they really mean
A short list of words carry precise, agreed-upon meanings on the radio. Using them correctly is not pedantry — it prevents the exact misunderstandings that phraseology exists to kill. The most abused of all is Roger: it means “I have received all of your last transmission,” and nothing more. It is not “yes,” and it is not agreement to do anything. If a controller says “report the airport in sight” and you answer “Roger,” you’ve only said you heard them — you have not agreed to report. The word for “I will comply” is Wilco.
| Word | Means | Watch out |
|---|---|---|
| Roger | I received all of your last transmission. | Not “yes,” and not agreement to act. |
| Wilco | I will comply with the instruction. | Implies you received it and will do it. |
| Affirmative | Yes. | Say the full word, not “affirm-yeah.” |
| Negative | No. | Clear opposite of Affirmative. |
| Say again | Repeat your last transmission. | Use this — not the word “repeat.” |
| Standby | Wait; I’ll get back to you. | Not a clearance or approval to proceed. |
| Unable | I cannot comply (with that request/clearance). | Say it plainly when you can’t or shouldn’t do it. |
| Say intentions | Tell me what you plan to do. | A controller’s cue for you to state a plan. |
Roger vs Wilco Roger = “heard you.” Wilco = “heard you and will do it.” And Standby is never permission — if you asked to enter a runway and got “standby,” you hold. The deadliest runway collision in history grew from a crew treating “standby”-adjacent language as clearance. When unsure whether you’re cleared, ask — don’t assume.
A few more habits round out clean radio work: if you need something repeated, say “say again,” not “repeat” (which has a specific meaning in other contexts). If you can’t do what you’re asked — too fast a descent, a turn into weather — say “unable” without apology; you are the final authority for the safe operation of your aircraft. And keep transmissions concise: think it, then say it once, cleanly.
ATIS, ASOS & AWOS: getting the picture before you call
Before you make that first call at a busy field, you’re expected to already have the current airport information — so the controller doesn’t have to read you the weather and active runway individually. That information comes from the ATIS: the Automatic Terminal Information Service, a continuous recorded loop broadcasting the current weather (essentially a spoken METAR), the runways in use, approaches in use, and any notes (closed taxiways, birds, construction). It updates about once an hour — more often if conditions change — and each new recording is tagged with a phonetic letter, advancing Alpha, Bravo, Charlie, and so on.
You listen to the ATIS, note the letter, and then state on first contact that you have it: “…with information Bravo.” That tells the controller you already know the weather and active runway, which shortens the exchange and confirms you’re working from current data. If your letter is stale, they’ll pass you the update.
Smaller airports without an ATIS often have an automated weather station instead — ASOS (Automated Surface Observing System) or AWOS (Automated Weather Observing System) — broadcasting current weather over a dedicated frequency or by phone. Same idea, no phonetic letter, no runway assignment; it’s just the observation, spoken aloud, so you can plan your pattern entry and expected runway from the wind.
Same data, spoken ATIS, ASOS, and AWOS are the same observation you’d read in a METAR — just broadcast over the radio. If the wind, visibility, sky, or altimeter in an ATIS puzzles you, decode the equivalent text with the METAR/ATIS decoder until the spoken version is second nature.
Transponder codes & “squawk / ident”
Your transponder replies to radar with a four-digit code (each digit 0–7 — it’s octal) so controllers can tag your target. “Squawk 4271” means set code 4271. Most VFR flying in the U.S. uses the general code 1200 when you’re not being assigned a discrete code. Four codes, though, are reserved for emergencies and must never be dialed by accident — even briefly passing through them while spinning the knobs can trigger alarms:
The other command you’ll hear is “ident.” When a controller says “N12345, ident,” you press the IDENT button once; your target blooms briefly on their radar so they can positively identify which blip is you among many. You never key ident on your own — only when asked.
Never dial through them When changing codes, be deliberate: momentarily rolling 7500, 7600, or 7700 under the knob can set off cockpit-security or emergency responses on the ground. Set the new code cleanly, digit by digit, and confirm before it’s active.
Towered vs non-towered airports
Airports come in two radio flavors, and knowing which you’re at determines who you talk to and what a transmission means.
At a towered airport, a controller issues instructions and clearances you must comply with: ground control moves you on the taxiways, tower controls the runways and the immediate airspace, and you get explicit clearances to taxi, take off, and land. It is a two-way, authoritative conversation.
At a non-towered airport — the majority of U.S. fields — there is no controller. Instead, pilots self-announce their positions and intentions on a shared CTAF (Common Traffic Advisory Frequency) so everyone builds a mental picture of the traffic and separates themselves. Nobody clears you to do anything; you announce, you listen, and you fit in safely. The CTAF might be a UNICOM frequency (a non-ATC advisory station, often 122.7–123.0), the universal MULTICOM 122.9 where no UNICOM exists, or even the tower’s own frequency when the tower is closed (a “part-time” tower).
Towered
Ground & Tower issue clearances you must obey. You’re told when to taxi, take off, land.
Non-towered
No controller. You self-announce on CTAF and separate yourself from other traffic.
CTAF sources
UNICOM 122.7–123.0, MULTICOM 122.9, or the tower freq when closed.
Announce pattern
Field name first and last: “Half Moon Bay traffic… Half Moon Bay.”
A self-announce call names the airport first and last — because several nearby fields may share 122.9, bracketing the call with the field name tells listeners it’s about their airport. A typical inbound call: “Half Moon Bay traffic, Skyhawk 12345, ten miles east, inbound landing, will report left downwind Runway 30, Half Moon Bay.”
Not a clearance “Line up and wait” means taxi onto the runway and hold in position — it is NOT a takeoff clearance. You wait for a separate “cleared for takeoff.” Rolling on “line up and wait” is a classic, dangerous error. (This phrase replaced the older “taxi into position and hold.”)
The read-back rule & runway incursions
A runway incursion — an aircraft, vehicle, or person mistakenly on a runway — is one of aviation’s most serious ground risks. The single most effective defense a pilot has is the verbatim read-back of any instruction to hold short of a runway or to cross a runway. When you read the instruction back word-for-word with your call sign, the controller hears whether you understood correctly and can catch an error before you move.
Read back the runway number and the hold-short/crossing instruction, and include your call sign — every time, without shortcut. “Hold short Runway 31, N12345.” “Cross Runway 25, N12345.” A bare “Roger” or a click of the mic is not a read-back and gives the controller nothing to verify. If you ever taxi toward a runway and are not certain you were told to cross or line up, stop and ask — “confirm cleared to cross Runway 31?”
Self-check Ground says “N345, Runway 31, taxi via Alpha, hold short Runway 22.” What’s the minimum correct read-back?
Show answer
“Runway 31, taxi via Alpha, hold short Runway 22, N345.” The hold-short instruction (Runway 22) and your call sign are mandatory in the read-back; reading back the assigned runway and taxi route as well confirms the whole clearance. A plain “Roger” is not acceptable.
Light-gun signals
If your radio fails at a towered airport, the tower can still direct you with a focused light gun, shining colored beams at your aircraft. Every pilot must know these cold, because they are your only two-way link when the radio is dead. The meaning of each signal differs depending on whether you are in flight or on the ground, so learn them as a matrix.
| Signal | In flight | On the ground |
|---|---|---|
| Steady green | Cleared to land. | Cleared for takeoff. |
| Flashing green | Return for landing (a steady green will follow). | Cleared to taxi. |
| Steady red | Give way to other aircraft and continue circling. | Stop. |
| Flashing red | Airport unsafe — do not land. | Taxi clear of the runway in use. |
| Flashing white | (not used in flight) | Return to starting point on the airport. |
| Alternating red/green | Exercise extreme caution. | Exercise extreme caution. |
Memory hooks Green = go (land or take off), red = stop/no (don’t land, stop), flashing = “not yet / conditional” (return, taxi clear), and alternating red-and-green is the same warning in both worlds: extreme caution. Flashing white only exists on the ground — “go back where you started.”
Lost communications
Radios fail. When yours does, there is a defined procedure so you and everyone else stays predictable. For a VFR flight, the sequence is straightforward:
- Squawk 7600 so radar-equipped controllers see you’ve lost comms.
- Try the basics: check volume, frequency, the correct comm radio, and your headset/mic connections — many “radio failures” are a knocked-loose plug or a wrong frequency.
- Watch the tower for light-gun signals as you approach a towered field, and comply with them.
- Acknowledge that you’ve received a light signal by rocking your wings in the day, or flashing your landing light at night.
Enter the pattern normally, keep a sharp lookout, and let the tower sequence you with the light gun. At a non-towered field you simply fly a normal, cautious pattern and use your position to separate from others as always.
A note for IFR Under IFR in actual lost-comms, 14 CFR 91.185 governs. Fly your route by the mnemonic AVE‑F — Assigned, then Vectored (proceed to the fix you were being vectored to), then Expected, then Filed — and fly the altitude that is the highest of the MEA, Expected, or Assigned altitude for each segment. That’s an instrument-rating topic; as a VFR pilot, remember 7600 and the light gun.
Guard: the emergency frequency 121.5
121.5 MHz is the international VHF emergency (“Guard”) frequency, monitored by ATC facilities, Flight Service, and many aircraft. It is where you go when you have an emergency and no better frequency, when you’re lost and need help, or when you must reach someone quickly. It’s also the frequency emergency locator transmitters (ELTs) chirp on after a hard landing or crash.
Guard is not a chat channel — keep it clear for genuine need. But know it’s always there: if you’re ever truly stuck — disoriented, an emergency unfolding, unable to raise the facility you expected — a call on 121.5 (“Mayday” for distress, “Pan-Pan” for urgency) reaches help.
One flight, every call
Let’s put the whole lesson together the way a real flight strings it: a towered departure (Palo Alto), a hand-off to departure/approach control, and a landing at a non-towered field (Half Moon Bay). Notice how each call is just the four-part template, trimmed once you’re already talking to a facility.
Here is the same flight as a script you could read aloud. Facilities’ replies are omitted for brevity; your read-backs of any hold-short or runway-crossing instruction would be verbatim, with your call sign.
Common mistakes & misconceptions
These are the errors nearly every student makes at least once. Knowing them in advance is how you skip them.
Myth “Roger means yes.” No — Roger only means “I received your transmission.” To agree to comply, say Wilco. To answer a yes/no question, say Affirmative or Negative.
Myth “‘Line up and wait’ means I can go.” It does not. You taxi onto the runway and hold until you hear “cleared for takeoff.”
Myth “‘Standby’ is permission.” Standby means wait. It is never a clearance to enter a runway, taxi, or take off.
Myth “A quick ‘Roger’ is a fine read-back for hold-short.” No. Hold-short and runway-crossing instructions require a verbatim read-back with your call sign — it’s the top defense against runway incursions.
Myth “At a non-towered field, someone clears me.” There is no controller. You self-announce on CTAF and separate yourself — nobody clears you to take off or land.
Myth “I’ll figure out my call while keying the mic.” That produces the dreaded “uhhh…” that blocks the frequency. Build the whole four-part call first, then key and say it once.
Myth “Numbers are said normally.” They are spoken digit by digit — and 3=tree, 5=fife, 9=niner. “Two seven zero,” not “two hundred seventy.”
Frequently asked questions
What is the four-part radio call?
Nearly every initial transmission follows the same four parts in order: who you’re calling (the facility), who you are (your call sign), where you are (position, and altitude if airborne), and what you want (your request or intention). For example: “Palo Alto Tower, Skyhawk 12345, ten miles south, landing with information Bravo.”
Does “Roger” mean “yes”?
No. Roger means “I have received all of your last transmission” — nothing more. To say you will comply with an instruction, use Wilco. To answer a yes/no question, use Affirmative or Negative.
Why are 3, 5, and 9 pronounced “tree,” “fife,” and “niner”?
Numbers are spoken digit by digit, and these three get distorted pronunciations so they survive noise and accents: “tree” (3), “fife” (5), and “niner” (9). “Niner” in particular keeps nine from being confused with the German “nein” or with “five.”
What do the transponder codes 7500, 7600, and 7700 mean?
7500 = hijack / unlawful interference, 7600 = lost communications (radio failure), and 7700 = a general emergency. The general VFR code in the U.S. is 1200. A common memory aid: “7500 taken alive, 7600 radio nix, 7700 going to heaven.” Avoid dialing through these codes accidentally.
What is the difference between “squawk” and “ident”?
“Squawk” means set a transponder code — “squawk 4271” tells you to dial in 4271. “Ident” means press the IDENT button once so your target momentarily highlights on the controller’s radar, letting them positively identify you. You press ident only when asked.
What is ATIS, and how is it different from ASOS/AWOS?
ATIS (Automatic Terminal Information Service) is a recorded loop at busier towered fields giving current weather, active runways, and notes; it updates about hourly and is labeled with a phonetic letter (“information Alpha”), which you state on first contact. ASOS and AWOS are automated weather broadcasts at fields without ATIS — the observation only, with no runway assignment or phonetic letter.
What does “line up and wait” mean?
It means taxi onto the runway and hold in position — it is not a takeoff clearance. You wait for a separate “cleared for takeoff” before rolling. The phrase replaced the older “taxi into position and hold.”
What must I read back verbatim?
Any instruction to hold short of a runway or to cross a runway must be read back word-for-word, including your call sign — for example, “Hold short Runway 31, N12345.” This verbatim read-back is the single most effective defense against runway incursions. A plain “Roger” is not acceptable.
What are the light-gun signals if my radio fails?
Meaning depends on whether you’re airborne or on the ground. Steady green = cleared to land (air) / cleared for takeoff (ground). Flashing green = return for landing (air) / cleared to taxi (ground). Steady red = give way and continue circling (air) / stop (ground). Flashing red = airport unsafe, do not land (air) / taxi clear of the runway (ground). Flashing white = return to your starting point (ground only). Alternating red-and-green = exercise extreme caution (both).
What do I do if I lose radio communication as a VFR pilot?
Squawk 7600, troubleshoot the radio (volume, frequency, correct radio, headset connections), and watch the tower for light-gun signals as you approach. Acknowledge a light signal by rocking your wings in daytime or flashing your landing light at night, then comply. (IFR lost comms is governed by 14 CFR 91.185 — fly the route AVE-F and the highest of the MEA, Expected, or Assigned altitude.)
What is a CTAF, and which frequency is it?
CTAF (Common Traffic Advisory Frequency) is the frequency pilots use to self-announce at a non-towered airport. It may be a UNICOM frequency (often 122.7–123.0), the MULTICOM frequency 122.9 where no UNICOM exists, or the tower’s frequency when the tower is closed. There is no controller; you announce your position and intentions and separate yourself from other traffic.
What is 121.5 used for?
121.5 MHz is the international VHF emergency frequency, called “Guard.” It’s for distress (“Mayday”) and urgency (“Pan-Pan”) calls, for reaching help when lost or unable to contact your expected facility, and it’s the frequency emergency locator transmitters broadcast on. Keep it clear of routine chatter.
Keep going: memorize the alphabet and standard words with the radio & ATC flashcards, decode a live ATIS with the METAR decoder, and browse more lessons in the Classroom. Always fly current phraseology and procedures per the AIM, the Pilot/Controller Glossary, and 14 CFR — this lesson is a study aid, not operational authority.