Every radio call is the same four pieces of information. Learn the format once, learn the handful of calls you’ll actually make, and the radio stops being the scariest part of flight training.
Strip away the jargon and every initial radio call has the same skeleton: who you’re calling, who you are, where you are, and what you want. Master that order and you can build any call you’ll ever need.
The facility, by name. It tells everyone on frequency who should be listening.
Aircraft type or model plus your tail number (drop the leading “N” when you say the type first).
Position — and at a towered field, confirm you have the ATIS by its phonetic letter.
The request, stated plainly. Controllers want the intent, not a story.
Listen for a few seconds so you don’t transmit over someone. Get the ATIS first at a towered field. Say the call in your head (or out loud) once before you push the button. Think, key, pause a beat, then speak — the first half-second is clipped if you talk the instant you key.
Letters are always spoken phonetically — Alfa, Bravo, Charlie … X-ray, Yankee, Zulu — so “N732AB” is “November Seven Three Two Alpha Bravo,” or “Skyhawk Seven Three Two Alpha Bravo” when you lead with the type. Numbers are spoken digit by digit, with three pronunciations worth drilling: “tree” for 3, “fife” for 5, and “niner” for 9. Altitudes read as thousands and hundreds: 2,500 is “two thousand five hundred.”
At a Class D field you’ll typically talk to Ground for taxi and Tower for the runway — bigger fields add Clearance Delivery before Ground and Departure/Approach after Tower. A normal VFR departure and return sounds like this:
“Springfield Ground, Skyhawk Seven Three Two Alpha Bravo, north ramp with information Bravo, ready to taxi, VFR southbound.”
Read back the taxi route — and always the runway and any hold-short instruction, with your call sign.
“Springfield Tower, Skyhawk Seven Three Two Alpha Bravo, holding short Runway Two Two, ready for departure.”
“Cleared for takeoff” gets read back with the runway: “Cleared for takeoff Runway Two Two, Skyhawk Seven Three Two Alpha Bravo.”
“Springfield Tower, Skyhawk Seven Three Two Alpha Bravo, one zero miles south at two thousand five hundred with information Charlie, inbound full stop.”
Call before entering the Class D (the radio call must be established before the boundary), follow the pattern-entry instruction, and read back your landing clearance with the runway.
On the CTAF there’s no controller — you’re broadcasting position and intentions so other pilots can build a picture. Address the airport by name at the start and end of each call, because several airports can share one frequency:
“Millville traffic, Skyhawk Seven Three Two Alpha Bravo, one zero miles west, two thousand five hundred, inbound for landing Runway One Zero, Millville.”
“Millville traffic, Skyhawk Seven Three Two Alpha Bravo, entering left downwind Runway One Zero, Millville.”
“Millville traffic, Skyhawk Seven Three Two Alpha Bravo, left base Runway One Zero, Millville.” — then final, then clear of the runway.
Per the FAA’s AC 90-66, announce roughly 8–10 miles out, before pattern entry, and on downwind, base, final, and exiting the runway. One phrase to drop from your vocabulary: “any traffic in the area, please advise” — the FAA specifically calls it out as unnecessary frequency congestion. Aircraft without radios may legally be in the pattern, so announcements never replace looking outside.
Always read back: hold-short instructions (with your call sign — this one is mandatory), runway assignments, takeoff and landing clearances, and altitude or heading instructions. The readback isn’t ceremony; it’s the error-catching loop that keeps two airplanes off the same runway.
Say it on initial contact — the AIM explicitly encourages it. Controllers will slow down, simplify instructions, and give you extra room. There is zero downside.
Missed a call? Ask for a repeat. Every pilot on frequency has said it thousands of times. Never read back a clearance you didn’t actually hear.
The most underused word in aviation. If an instruction would put you somewhere you can’t safely go — clouds, terrain, an approach faster than you can fly — say “unable” and let ATC work the problem.
Means “I heard you, give me a moment.” Use it when you’re mid-checklist; expect it back when the controller is busy. It requires no response.
Distress and urgency, each spoken three times. With an emergency: squawk 7700, and if you can’t raise anyone, 121.5 is the emergency frequency. Declaring costs nothing — waiting can cost everything.
When you don’t know the phrase, use plain English. “Tower, Skyhawk Two Alpha Bravo, I’m not sure I understood — can you say that more slowly?” is a perfectly good transmission. Controllers are on your side; the AIM itself says clarity trumps phraseology.
FlightKit’s ATC Comms trainer plays the controller — you make the calls out loud, it responds like the real thing and corrects your phraseology. Pair it with live ATC feeds to train your ear between lessons.
Use the four W's: who you're calling, who you are, where you are, and what you want. For example: "Springfield Ground, Skyhawk Seven Three Two Alpha Bravo, at the north ramp with information Bravo, ready to taxi, VFR southbound." Listen first so you don't step on another transmission, and rehearse the call before you key the mic.
Radio calls at non-towered airports are self-announcements on the CTAF, not a conversation with a controller — and while highly recommended, they are not legally required for most aircraft in Class G or E. Announce your position and intentions roughly 8–10 miles out, before entering the pattern, and on downwind, base, final, and when clear of the runway, addressing the airport by name ("Millville traffic ...").
Read back any runway hold-short instruction with your call sign — controllers are required to get that readback. You should also read back runway assignments, takeoff and landing clearances, altimeter settings when issued, and any altitude or heading instructions. When in doubt, read it back: the readback/hearback loop is how errors get caught.
Yes. The AIM specifically encourages student pilots to identify themselves as such on initial contact with any ATC facility. Controllers respond by speaking more slowly, breaking up complex instructions, and watching you more closely. Many CFIs have students keep using it through their first several solo cross-countries.
Nothing. Controllers hear imperfect phraseology all day and will simply ask you to "say again" or confirm what you meant. Plain English is always acceptable when you don't know the standard phrase — clarity beats jargon. The only real radio mistakes are transmitting on top of someone, reading back a clearance you didn't hear, or staying silent when you're confused.
It means the controller has positively identified your aircraft on their radar display and will monitor your position — you no longer need to report crossing positions unless asked. It does not mean ATC is navigating for you or has taken responsibility for your terrain and traffic separation under VFR.
Flight following is radar traffic advisories for VFR aircraft, requested from approach or center ("request VFR flight following"). You get traffic callouts and an extra set of eyes, workload permitting. It's free, it's excellent practice on the radio, and it's one of the best habits a new pilot can build on cross-countries.
Short, practical guides on weather, planning, and staying current. No spam.