How to Request a Stop and Go: ATC Phraseology Guide
Learn how to request a stop and go from tower, the exact phraseology to use, and what to expect in the clearance and readback. · 4 min read

<link rel="stylesheet" href="/marketing-app/blocks.css?v=cd1fc801">
<div class="mb mb-summary" style="--mb-accent:#5c6b7e;--mb-on-accent:#ffffff"><p class="mb-label">In short</p><p>To request a stop and go, call the tower with "[Callsign], request stop and go" while on downwind or base, before your turn to final. The controller issues a landing clearance that includes "stop and go," you read it back, then land, come to a full stop on the runway, and take off again without taxiing clear.</p></div>
Student pilots working on takeoffs and landings often ask how to request a stop and go once they've gotten comfortable with the touch and go. A stop and go adds one more skill to the pattern: bringing the aircraft to a complete stop on the runway before advancing the throttle again. It's a common request during dual instruction and checkride prep, and getting the phraseology right helps the tower sequence you correctly with other traffic in the pattern.
In this article
What Is a Stop and Go?
A stop and go is exactly what it sounds like: the aircraft lands, rolls out, comes to a full stop on the runway, and then departs again from that same position without taxiing back to the hold-short line or clearing the runway. It's used to practice full-stop landings and the transition back into a takeoff roll, without the time cost of taxiing back for another circuit.
How It Differs from a Touch and Go
A touch and go never stops rolling — the aircraft touches down, then immediately reconfigures and accelerates back into the air. A stop and go requires a genuine full stop, which means the controller needs to know your intentions in advance so they can plan separation for the aircraft behind you. If your training syllabus calls for touch and goes instead, the request and readback differ slightly; see the guide on how to request touch and go or the option for that phraseology.
How to Request a Stop and Go
The Phraseology to Use
The request itself is short. On initial contact or when reporting your position in the pattern, say something like:
"Tower, Cessna 345AB, downwind, request stop and go."
If you're on an extended pattern or approaching from a straight-in, state your position and intentions the same way. Keep it simple — the controller only needs to know what runway operation you're planning.
When to Make the Request
Make the request early enough that the controller has time to work it into the sequence, typically on downwind or base, not on short final. Waiting too long forces the controller to issue last-second instructions, which increases the chance of a rushed or missed readback — a common source of mic fright for students still building pattern confidence.
What to Expect From the Controller
Clearance Wording
Once approved, the tower will issue something like: "Cessna 345AB, runway 27, cleared for the option, stop and go approved," or simply "cleared to land, stop and go approved," depending on local phraseology and whether other options are also authorized.
Readback Requirements
Read back the runway number and the clearance type exactly as issued. Omitting the stop and go portion of the readback is one of the more frequent errors examiners and instructors flag, because it leaves the controller unsure whether you understood the full clearance.
Common Mistakes to Avoid
- Requesting the stop and go too late in the pattern
- Reading back only part of the clearance
- Taxiing clear of the runway instead of stopping and departing from position
- Forgetting to reconfigure the aircraft (flaps, trim) before the takeoff roll resumes
Practicing Stop and Go Calls Until They're Automatic
Phraseology for pattern work sounds simple on paper, but under pressure — with a real controller, real traffic, and a real stopwatch — it's easy to drop a word or hesitate. That's where repetition against a fixed standard matters more than general familiarity.
ATCpal lets student pilots practice this exact exchange out loud with an AI controller, then grades the readback word-for-word against FAA phraseology rather than relying on a language model's opinion of how close the call sounded. Because the grading is deterministic and token-exact against a fixed answer key, a stop and go readback is either correct or it isn't — nothing is guessed. With 201 lessons across 11 phases of flight and 10 practice modes, from open radio work to a scored checkride run, pattern calls like this one can be drilled until the clean-readback rate climbs and the hesitation disappears.
Related Pattern Work for Student Pilots
Stop and go requests rarely happen in isolation. The same radio session often involves a practice approach request, a progressive taxi request after landing, picking up flight following on departure, or a frequency change request once clear of the pattern. Building fluency across all of these keeps a training flight moving without unnecessary back-and-forth with the controller.
Put the Phraseology to the Test
<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>
Phraseology sourced from the FAA Aeronautical Information Manual (Change 3, effective 9 July 2026) and the Pilot/Controller Glossary. Check the AIM · Last reviewed 13 August 2026.