What to Say to Ground Control: A Student Pilot's Script

<link rel="stylesheet" href="/marketing-app/blocks.css?v=fd2b772a">

<div class="mb mb-summary" style="--mb-accent:#5c6b7e;--mb-on-accent:#ffffff"><p class="mb-label">In short</p><p>When calling ground control, state who you are (callsign and aircraft type), where you are (your parking spot or ramp), and what you want (taxi, pushback, or progressive instructions), then add that you have the current ATIS. Keep it short, in that order, and ground will usually respond with a taxi clearance you read back.</p></div>

Getting this call right the first time takes most of the pressure off a flight. Once a student pilot knows the order of information ground control expects, the radio stops feeling like a test and starts feeling like a routine checklist item.

In this article

• Why Ground Control Calls Feel Hard
• The Basic Format for Ground Control Calls
• Common Ground Control Scenarios
• Listening Back: Reading Clearances Correctly
• Practicing Until It's Automatic
• Fly the Pattern With More Confidence

Mic fright is normal

Mic fright hits almost every student at some point, usually right before the first transmission of the day. The controller is busy, the frequency is crowded, and there's a nagging fear of saying the wrong thing in front of a stranger. This isn't a sign of being unprepared — it's a predictable reaction to an unfamiliar format. The fix isn't more confidence; it's a fixed structure to lean on so there's less to think up on the spot.

Who, where, what, with information

Every ground call follows the same shape:

1. Who you are — your full callsign, including aircraft type if it helps identify you (e.g., "Cessna 123AB").
2. Where you are — your current position, such as a specific parking spot, ramp, or FBO.
3. What you want — taxi for departure, a pushback, or progressive taxi instructions if the airport layout is unfamiliar.
4. With what information — confirming you have the current ATIS letter.

Put together, it sounds like: "Ground, Cessna 123AB, at the north ramp, ready to taxi, with information Bravo." That's the whole call. Nothing more is needed until ground responds with instructions.

For a full breakdown of this structure, including how it changes slightly depending on airport size, see this guide to the first radio call to ground.

Taxi to runway

The most common ground call is a straightforward taxi request. Ground will typically reply with a runway assignment, a taxi route, and any hold-short instructions. All three parts need to come back in the readback, word for word where phraseology requires it.

Pushback and engine start

At towered airports with a ramp or pushback area, the call to ground (or sometimes a separate ramp frequency) requests pushback and engine start clearance before the taxi request. This is common at larger airports and less so at smaller training fields, so it's worth knowing which applies before keying the mic.

Progressive taxi instructions

Unfamiliar airports can have confusing taxiway layouts. Asking for progressive taxi instructions is a normal, accepted request — it simply means ground will give turn-by-turn directions instead of a single route clearance. There's no downside to asking; it's far better than guessing at an intersection.

Crossing a runway

If the taxi route crosses an active runway, ground control must issue an explicit clearance to cross, and the pilot must read that runway number back. Taxiing across a runway without a clear crossing clearance is one of the more serious errors a student pilot can make, so this readback deserves extra attention.

Readback requirements

Ground control phraseology leaves little room for paraphrasing. Runway numbers, taxiway letters, and hold-short instructions all need to be read back exactly as given, not summarized. If any part of the instruction wasn't caught clearly, phraseology provides a standard way to ask for it again rather than guessing. This guide on roger, wilco, and say again covers exactly when and how to use each phrase so a missed word doesn't turn into a missed instruction.

Why saying it out loud matters

Reading ground control phraseology off a page is one thing; producing it under pressure, at speed, with a real controller's voice in the headset, is another. The gap between the two is where most mic fright comes from.

This is the gap ATCpal was built to close. It's a browser-based app where student pilots talk out loud to an AI air traffic controller and get their readback graded right, not guessed. Instead of a language model's subjective opinion of whether a response was "close enough," ATCpal checks readbacks with deterministic, token-exact matching against a fixed FAA answer key — so the same readback produces the same result every time. With 201 lessons spanning 11 phases of flight and 10 practice modes, from casual open radio practice to a scored checkride run, a student can drill ground calls specifically until the who-where-what-with order becomes automatic. A progress dashboard tracks clean-readback rate and flags dropped elements, so it's clear exactly which part of the phraseology still needs work.

<div class="mb mb-cta" style="--mb-accent:#5c6b7e;--mb-on-accent:#ffffff"><h3 id="ready-to-buy">Ready to buy?</h3><a class="mb-btn mb-btn-main" href="https://atcpal.app">Buy from ATCpal</a></div>