“Cleared to the circuit”: the Canadian tower phraseology students fumble, and the exact readbacks

We are ten miles out, inbound to a field with a control tower for the first time, and the frequency is busy. We know the shape of a call by now — who we are calling, who we are, where, what we want. What we do not yet know is what comes back, and when we are allowed to act on it. The tower answers with a run of words, and buried in it is "cleared to the circuit." Part of us wants to hear that as "cleared to land" — the runway is right there — and start setting up to touch down. It is not that. The gap between what we were actually cleared to do and what we did next is where a surprising number of student mistakes live.

So here is the arc of a controlled-field arrival, from the join to the wheels, in the order the tower gives it to you — what "cleared to the circuit" authorises, the position reports you volunteer along the way, the instructions that arrive as a change of plan, and the landing clearance that finally lets you down. None of the words are hard. The trap is always the same one: acting on a clearance you were not given.

What "cleared to the circuit" actually authorises

When you call inbound with your position, altitude and intentions, the tower comes back with the runway in use, the wind and the altimeter, and then a join instruction — "cleared to the circuit," or a specific leg like "cleared left downwind" or "cleared left base" — usually with a reporting point attached, such as "report final."^[1] That instruction does three jobs: it tells you the runway, it tells you how to join, and it asks you to call at a named point.

What it does not do is clear you to land. The landing clearance is a separate transmission, with its own words, that comes later — and until you hear it, you are cleared to fly the circuit and nothing more.^[1] At a controlled aerodrome the clearance to land at the runway is something the tower issues on its own; you cannot infer it from having been let into the pattern.^[2] Hold that distinction — it is the whole article.

The circuit you are joining is four legs — crosswind, downwind, base and final — normally flown at a thousand feet above the aerodrome, and in Canada the turns are to the left unless the Canada Flight Supplement specifies a right-hand circuit or the tower authorises one.^[4][2] You are also expected to blend in rather than barge in: entry is made so as not to cut off other aircraft, matching the altitude, speed and size of the circuit the traffic ahead of you is flying.^[4]

The join call, and what comes back

Our aeroplane is a Cessna 172, registration C-GKWL — on the radio, the last four characters with the Canadian "C" dropped: "Golf Kilo Whiskey Lima."^[1] You make this call before you enter the control zone, not as you cross the fence, and having already listened to the ATIS you check its letter in so the tower knows you have the current runway, wind and altimeter.^[4][1]

You: "Springbank Tower, Cessna 172 Golf Kilo Whiskey Lima, ten miles south, three thousand five hundred, with information Delta, inbound for landing."

Tower: "Cessna 172 Golf Kilo Whiskey Lima, Springbank Tower, runway 25, wind 240 at 8, altimeter three zero one two, cleared to the circuit, report left downwind."

You: "Runway 25, cleared to the circuit, report left downwind, Golf Kilo Whiskey Lima."

Notice the readback gives back the runway and the join instruction with the call sign on the end. As a VFR pilot you are not, strictly, required to read back every transmission the tower sends you — the hard rule is that you read a clearance back when the controller asks for it.^[3] But a runway assignment is one of the safety numbers worth returning every time, because a readback is the cheapest place to catch a mix-up between, say, 25 and 07 while there is still a whole circuit in which to fix it.^[1]

"Number two, follow the Cessna on final"

On a busy day the tower fits you into a line and tells you where you are in it — "number two," "number three" — often naming the traffic you are following: "number two, follow the Cessna on final."^[1] That single call is doing two things, and both matter.

The number is your place in the sequence. Number two means one aircraft lands ahead of you, and you do not turn final in front of it.^[1] The "follow the Cessna" half is a traffic instruction, and it wants a specific reply — "traffic in sight" if you have picked the aircraft out of the windscreen, "looking for traffic" if you have not.^[1] Say one of those two; if you had the traffic and then lose it, tell the tower.^[1] The instinct to mumble something vague about the traffic you think you see is exactly the habit that gets a "say again" back from the other side of the mic.

The instructions that arrive as a change of plan

Four calls come up in the circuit that students hesitate on — not because the words are hard, but because each lands as a change to the plan you had, and each has a right response.

Extend downwind. "Extend downwind to follow traffic on final" means keep flying the downwind heading past the point where you would normally turn base, so you roll onto final behind the traffic instead of in front of it.^[1] You keep going until you can turn base with that traffic ahead of you — or, if the tower said it would call your base turn, until it does.^[1] The fumble is turning base on schedule anyway, out of habit, straight into the aircraft you were told to follow.

Orbit. When the pattern is saturated the tower may hold you with an orbit — "orbit left," or "orbit north of the highway" — a 360-degree turn flown to bleed off time.^[1] An orbit is a hold, not a single turn: you keep circling until the tower releases you.^[1] The same tool can reach you earlier, before you are even in the circuit, as "remain outside the control zone" when the airspace is busy.^[1]

Cleared touch-and-go. If you are flying circuits you request the exercise on downwind — "request touch-and-go" — and the tower answers "cleared touch-and-go runway 25," which you read back like any other runway clearance.^[1] The option, a stop-and-go, a low approach: same shape every time — you ask, the tower clears it or replies "unable," and you read the clearance back.^[1]

Go around. If something is wrong — traffic still on the runway, spacing gone — the tower sends you around: "pull up and go around."^[1] The reply is short: "going around," with your call sign, and then you fly the airplane.^[1] It runs the other way too. A landing clearance authorises the landing, but the decision to land or to overshoot is always the pilot's, and if you elect to go around on your own judgement you tell the tower as soon as you safely can.^[1]

The landing clearance, and its mandatory-ish readback

Somewhere on base or final the transmission you have been waiting for arrives:

Tower: "Golf Kilo Whiskey Lima, cleared to land runway 25."

You: "Cleared to land runway 25, Golf Kilo Whiskey Lima."

That is the one that authorises the landing — separate from, and later than, "cleared to the circuit."^[1][2] The readback sits in an honest grey area. Strictly, the legal readback rule for a VFR pilot is that you read a clearance back when ATC asks.^[3] But a runway clearance is exactly the kind of safety-of-flight item the phraseology expects back, and reading "cleared to land runway 25" aloud is how a wrong-runway slip surfaces while there is still time to catch it.^[1] Call it mandatory-ish: not the hard "shall" that a hold-short instruction carries, but a habit you never want to be caught without.^[1]

The one true exception to "read it back when asked" is that hold-short instruction. If one is ever attached to your clearance — sending you to stop short of an intersecting runway — the words "hold short," the runway, and your call sign come back every single time, no matter what else is happening.^[1][3]

The three that bite students

Almost every circuit mistake is one of three, and all three are avoidable.

Hearing "cleared to land" inside "cleared to the circuit." The most common one, and the reason for this whole piece. The two clearances are different transmissions with different words, and the join clearance never doubles as the landing clearance.^[1][2] If final is coming up and the landing clearance has not, that is a question to ask, not a gap to fill in yourself.

Turning final ahead of your sequence. "Number two" means an aircraft lands before you do. If you have not visually got that traffic, you say "looking for traffic" and you hold your place — you do not slot yourself onto final in front of an airplane you cannot see.^[1]

Reading back the wrong runway — confidently. A readback is only worth making if it is the clearance you were actually given. If the numbers went by too fast, do not read back a hopeful reconstruction; say "say again" and copy it clean.^[1] A confident readback of the wrong runway is worse than none, because it tells the controller you understood when you did not.^[1]

None of these calls is hard to say. The work is wearing the grooves deep enough that "cleared to the circuit" and "cleared to land" never blur into each other under the load of flying the airplane, watching your sequence, and setting up an approach all at once. Get the difference dull, get it automatic, and the first time you fly a real circuit into a real tower, the only new thing about it is that the seat beside you is empty.