
TowerTalk
Worked from the ground up — start with the alphabet, build to a full flight, and finish with the emergencies.
Not sure where you stand? Free Radio Readiness Check →New · hands-free
Listen to the revision audiobook
Revise in the car or away from a screen — with lock-screen controls.
Met Office codes
Searchable A–Z to decode any METAR or TAF — BKN, CAVOK, FZRA and the rest.
Numbers are normally spoken digit by digit — e.g. 120.375 is “WUN TOO ZE-RO DAY-SEE-MAL TREE SEV-en FIFE”. Round figures may be grouped, e.g. 3000 ft as “TREE TOUSAND”.
Loading…
You don't talk in Morse, but you'll hear it: navigation aids (VOR, NDB, ILS) constantly transmit their identifier in Morse. Before using one, listen and confirm the ident matches the one on your chart — that proves you've tuned the right station and it's serviceable.
Your opening message to a station, after their name and your callsign. A memory aid for what to include — not a phrase to recite mechanically, and not every item fits every call.
Norwich Approach, G-ABCD, Cessna 152, from Beccles to Norwich, overhead Bungay, 2000FT, request Basic Service
The fuller report you give when a unit answers your initial call with “pass your message”. It repeats your callsign and adds route, altitude with the pressure setting, and your intentions.
G-ABCD, Cessna 152, Leicester to East Midlands, overhead Syston, 1900FT, QNH 1000, VFR routing via Shepshed Lane
A procedural position report, given en route or when ATC asks for one. Often shortened — pass what the controller actually needs.
G-ABCD, BUNGAY, 25, 2000FT, DISS, 35
Tower (ATC)
Controls the airfield — issues clearances and instructions (taxi, line-up, take-off, landing). Use “request taxi”.
Approach / Radar
A radar service (Basic, Traffic or Deconfliction). Free-call “inbound” for joining instructions.
“Radio” (Air/Ground, AGCS)
Information only — no instructions or clearances; you stay responsible for your decisions. Use “request taxi information”.
“Information” (FIS, e.g. London Information)
A Flight Information / Basic Service for en-route VFR traffic.
“Ground” (Ground Movement Control)
Controls aircraft and vehicles taxiing on the manoeuvring area — issues taxi instructions and clearances. Found at busier ATC aerodromes; suffix “Ground”.
“Delivery” (Clearance Delivery)
Passes your departure / route clearance before you taxi, to keep the Ground and Tower frequencies clear. Busier aerodromes only; suffix “Delivery”.
ATC — Tower / Approach / Radar
A control service: issues clearances and instructions you must comply with and read back (and provides the agreed service, e.g. separation in controlled airspace).
AFIS — “Information”
Aerodrome Flight Information Service: information and aerodrome instructions, but NOT clearances or separation — decisions and responsibility stay with the pilot.
AGCS — “Radio”
Air/Ground Communication Service: information only (runway in use, known traffic, weather). It cannot issue instructions or clearances — you act at your own discretion.
Outside controlled airspace you ask for one of four UK Flight Information Services (CAP 774). Whichever you get, you stay responsible for collision avoidance unless told otherwise.
Basic Service
General information for any phase of flight (e.g. weather, changes of serviceability). Traffic information only if the controller happens to have it. You remain entirely responsible for your own collision avoidance, terrain clearance and navigation.
Traffic Service
A surveillance (radar) service: the controller passes traffic information on relevant conflicting traffic. You decide on and take your own avoiding action — no avoiding advice is given.
Deconfliction Service
A surveillance service giving traffic information AND deconfliction advice (headings and/or levels) to keep you clear of other traffic — usually IFR/IMC. You may accept it or not, but if you don't comply you take responsibility for your own separation.
Procedural Service
A non-surveillance service: instructions are based on reported positions (no radar). Deconfliction advice is given against other procedural traffic; traffic information where possible.
Acknowledge a traffic call promptly with your sighting status. Under a Traffic Service you still take your own avoiding action.
“… cleared to the zone boundary, route via Whiskey, Special VFR not above altitude 1500 feet” → readback: “Cleared to the zone boundary, route via Whiskey, Special VFR not above altitude 1500 feet, G-ABCD”
A MATZ is a Military Aerodrome Traffic Zone. Crossing one isn't compulsory for civil flights, but you should request penetration so the military controller knows you're there and can pass traffic information.
Wattisham Zone, G-ABCD, Cessna 152, 5 miles east of Wattisham, heading 270, altitude 2000 feet QNH 1013, VFR routing to Cambridge, request MATZ penetration.
RMZ — Radio Mandatory Zone
You must ESTABLISH two-way radio contact with the notified unit BEFORE you enter. Two-way is achieved only once you've passed your callsign, aircraft type, position, level, flight rules and intentions AND received an acknowledgement. If you can't make contact, stay outside. Marked “RMZ” on the chart.
TMZ — Transponder Mandatory Zone
You must have a serviceable transponder operating with the correct mode (Mode S, or Mode C with altitude reporting selected). If you can't comply (no transponder or a failure), get permission from the controlling unit first, otherwise remain outside. Marked “TMZ” on the chart.
Select altitude reporting (Mode C) unless told otherwise; the ATC instruction for it is “squawk Altitude” (CAP 413 Table 2). A frequency-monitoring code (“listening squawk”) is a discrete code you set while just listening out on a unit's frequency, so they know you're monitoring without calling. Always read SSR instructions back, e.g. “squawk 6171” → “6171, G-ABCD”.
Flying close to certain controlled airspace without wanting a service? Set that airfield's published frequency monitoring code (with Mode C if you have it) and listen out on the promulgated frequency. The code tells ATC you're on frequency — so if you look like you're about to infringe, they can call you and sort it before it happens.
A selection, not the full list. Each code applies only in a specific area, and codes change — check the current charts and the aerodrome's own published information before you fly.
A VDF (VHF Direction Finder) station fixes your bearing from your transmission. Ask: “<station>, <callsign>, request QDM, <callsign>” — repeat your callsign at the end of a VDF call. For a QTE, prefix with “true bearing, true bearing”. Each bearing comes with an accuracy class (A is best, down to D).
These must be read back word-perfect. Other information (e.g. readability) is acknowledged, not read back.
CAP 413 Edition 24, §2.69. A conditional clearance is read back with the condition FIRST and in the same sequence it was given — “behind the landing Cessna, line up runway two four, behind”. Read back complete and in order: an incomplete read-back is harder to spot than a wrong one.
The controller transmits — type back exactly what you’d say, then get marked on what must be read back.
“G-ABCD, taxi to holding point Alpha, runway 27, QNH 1013.”
These three are constantly confused. “Roger” only means received — use “Wilco” when you’ll act on an instruction, and answer a “report” request when you actually reach the point.
Roger
“I have received your last transmission.”
Acknowledges information only. It does NOT mean you will comply, it is never used where a readback is required, and it is never the answer to a question — use “Affirm” or “Negative” for that.
Wilco
“Will comply” — I understand your message and will comply with it.
Use to acknowledge an instruction you will act on, e.g. after “report final” → “Wilco, G-ABCD.”
Report …
An instruction to tell the controller when you reach a point or condition, e.g. “report final”, “report field in sight”, “report downwind”.
Acknowledge it now — “Wilco, G-ABCD” (or read back the report point) — then actually make the report when you get there.
The standard words have precise meanings — using the right one (and not a casual substitute) is what keeps RT brief and unambiguous.
Affirm
Yes.
Negative
No / not correct / permission not granted / not able.
Standby
Wait and I will call you. It is not an approval or a clearance.
Roger
I have received your last transmission. It does NOT mean “yes” and does NOT mean you will comply.
Wilco
“Will comply” — I understand your message and will comply with it.
Say again
Repeat all, or the following part, of your last transmission.
I say again
I am repeating my own transmission for clarity or emphasis.
Correction
An error has been made; the correct version is…
Disregard
Ignore.
Acknowledge
Let me know you have received and understood this message.
Read back
Repeat all, or the specified part, of this message back to me exactly as received.
Unable
I cannot comply with your request or instruction (usually followed by the reason).
Approved
Permission for the proposed action is granted.
Over
My transmission is ended and I expect a reply (often omitted on VHF where it's obvious).
Out
My transmission is ended and no reply is expected (rarely needed on VHF).
TowerTalk's Virtual ATC pulls the latest METARs for you. You can also read them at aviationweather.gov, or get a UK aviation weather briefing from the Met Office.
EGSH 121350Z 25012KT 9999 FEW035 14/09 Q1013
Weather is added when present: RA rain, SHRA showers, TS thunderstorm, BR mist, FG fog; “-” light, “+” heavy; NSC = no significant cloud, NOSIG = no significant change expected.
Pull the current weather at a UK airfield and see it broken down.
An ATIS (Automatic Terminal Information Service) is a continuous recorded broadcast of an aerodrome's essential information, on its own frequency, so it doesn't tie up the controller.
Listen before your first call. On contact, tell the unit you have the current letter — e.g. “… information Bravo”. If there's no ATIS, ask the station for the current aerodrome information.
UK airspace is divided into two Flight Information Regions (FIRs): the London FIR (south) and the Scottish FIR (north).
Within each, a Flight Information Service — London Information or Scottish Information — gives a Basic Service to en-route VFR traffic: flight information, weather, and traffic information where available. Free-call them and “request Basic Service”.
“… for spacing, orbit right”
“Orbit right, wilco, <callsign>” — a 360° turn to create spacing.
“… runway 27, land after the [traffic]”
“Runway 27, land after the [traffic], <callsign>” — you may land while the preceding aircraft is still on the runway, provided it will be clear, it's daylight, and you can see it. Read it back.
“… go around, I say again go around”
“Going around, <callsign>” — abandon the approach, climb away and rejoin.
Overhead join
The standard join where the procedure isn't otherwise notified: overfly at 2000 ft above aerodrome elevation, descend on the dead side, then cross the upwind end to position downwind.
Downwind join
Join directly onto the downwind leg at circuit height when advised/cleared, e.g. “join downwind runway 27”.
Base join
Join onto the base leg and turn final from there — when the traffic and controller allow it.
Crosswind join
Join on the crosswind leg (after the upwind end) to slot into the downwind leg.
Straight-in approach
Approach straight to the runway without flying the circuit, traffic permitting — report your range on final, e.g. “8 miles, straight-in approach runway 27”.
The join you use depends on the aerodrome, the traffic and the controller. At an ATC unit you're given joining instructions to read back; at an AGCS (“Radio”) field you choose, report your join and intentions, and make your own decisions.
Sleap Traffic, G-ABCD, overhead 2000 feet, descending dead side to join downwind runway 36, Sleap Traffic
Exact circuit calls vary by airfield and service. At a controlled (Tower) field, read back clearances; at an Air/Ground (“Radio”) field you give your position and intentions and make your own decisions.
Get the weather first
Listen to the ATIS if the field broadcasts one, or ask the station for airfield information. Note the information letter, the runway in use and the QNH.
Set up
Set your altimeter to that QNH and note the active runway.
Initial call & taxi
Tune the aerodrome frequency. Make your first call with your FULL callsign and request a radio check + taxi (ATC: “request taxi”; AGCS: “request taxi information”).
Read back
Read back the taxi instructions, runway and QNH.
Departure
At the holding point, when cleared, read back the line-up / take-off clearance (and any conditional clearance, ending with “behind”).
Leaving the zone
Request a frequency change to your next service.
New frequency
Make your initial call; when told “pass your message”, give your details using CARPAI.
En route
Give position reports using CPTANE when asked or at reporting points.
Arrival
Nearing your destination, free-call the approach/radar unit “inbound”, pass your details, and get joining instructions.
Join & land
Change to Tower, report as instructed, join the circuit and land — reading back the landing clearance.
If it goes wrong
Use PAN-PAN (urgency) or MAYDAY (distress), each spoken three times, then the message content.
The international aeronautical emergency frequency is 121.5 MHz (civil); military aircraft also guard 243.0 MHz (UHF). Address a MAYDAY or PAN to the unit you're already working, or to 121.5 MHz if you need to.
PAN-PAN, PAN-PAN, PAN-PAN
Urgency. A serious situation but no immediate danger — e.g. a rough-running engine, getting lost, a sick passenger.
MAYDAY, MAYDAY, MAYDAY
Distress. Grave and imminent danger needing immediate help — e.g. engine failure, fire.
Fuel shortage: two calls, only one an emergency
Source: CAP 413 Ed 24 §8.29–8.32; NCO.OP.185.
Message content (after the prefix):
When it's resolved, cancel it: “<callsign>, cancel PAN-PAN / MAYDAY …” so ATC can release any priority handling.
The emergency frequency 121.500 is guarded continuously by the Distress & Diversion cell — military controllers at NATS Swanwick, callsign “London Centre” — with coverage over most of the UK above about 3,000 ft.
Sources: CAP 413 Ed 24, CAA Safety Sense Leaflet 22 (Radiotelephony).
An engine failure leading to a forced landing is a distress situation — declare a MAYDAY. But fly the aircraft first: best glide speed and choose a field, THEN make the call. Don't get drawn into a long conversation.
Priority order: Aviate → Navigate → Communicate. The radio call comes AFTER flying the aircraft and picking your field. Don't expect a reply — pass what you can.
If you can't use the radio (e.g. a radio failure), the tower can direct you with light signals. The meaning differs depending on whether you're in the air or on the ground.
| Signal | In flight | On the ground |
|---|---|---|
| Steady green | Cleared to land | Cleared for take-off |
| Steady red | Give way to other aircraft and continue circling | Stop |
| Green flashes | Return for landing (a steady green will follow) | Cleared to taxi |
| Red flashes | Aerodrome unsafe — do not land | Taxi clear of the landing area in use |
| White flashes | Land at this aerodrome and proceed to the apron (after a steady green) | Return to your starting point on the aerodrome |
A red pyrotechnic / red flare means “do not land for the time being”. Acknowledge a signal by day by rocking your wings, and by night by flashing your landing/navigation lights. These are standard signals — verify against the current UK Rules of the Air / SERA.
If the radio fails, keep flying the aircraft and squawk 7600 (or 7700 if it's part of a wider emergency). What you do next depends on which part has failed.
Receiver failed (you can still transmit)
Transmit reports twice at the scheduled times or positions, prefixed “transmitting blind due to receiver failure” (CAP 413 §2.88), stating your intentions.
Transmitter failed (you can still receive)
Listen out and comply with instructions; acknowledge by an agreed means — press IDENT, or by day rock your wings and by night flash your lights.
Complete failure
Squawk 7600, follow your last clearance or the expected procedure, and look out for light signals from the tower.
MAYDAY RELAY: if you hear a distress call the controlling station hasn't acknowledged, or you need to pass one on behalf of an aircraft that can't, transmit “MAYDAY RELAY” (×3) and relay the distress message you heard.
Unsure of your position? Don't leave it too late — ask for help early: request a position fix or a QDM, or call for a Basic/Traffic Service. If you become genuinely lost or short of options it becomes an urgency (PAN-PAN), or a distress (MAYDAY) if you're in real difficulty.
SRG1171 1.1 · 1.2 · 1.3 · 1.4 · 1.6 · 1.8
Draft — not yet verified against CAP 413
Treat the wording below as indicative only until it's confirmed against the current manual. Always defer to CAP 413 and your instructor.
Transmitting technique (CAP 413 guidance — verify wording)
DRAFT: press the PTT fully before speaking and hold it until after the last word, or the start/end of the call is clipped; speak at an even rate; think out the whole call before transmitting; listen out before transmitting so you don't cut across another station.
OFCOM licence Schedule (verify current requirements)
DRAFT: the licence Schedule lists the equipment covered; owner to verify current OFCOM requirements on validity and carriage before this is taught as fact.
Active
124.600
Standby
118.825
Receiving 124.600. Ready to transmit.
Fault-finding drill
The set is misconfigured at random. Work out which control is wrong and put it right — that's the diagnosis the practical test asks for.
SRG1171 3.2 · 3.4 · 3.6 · 3.9
Draft — not yet verified against CAP 413
Treat the wording below as indicative only until it's confirmed against the current manual. Always defer to CAP 413 and your instructor.
Request start (verify phraseology vs CAP 413)
DRAFT: at aerodromes where engine start needs approval: “<station>, <callsign>, <location>, request start” — with information letter where ATIS is in use. Owner to verify the exact form.
Ready for departure (verify phraseology vs CAP 413)
DRAFT: at the holding point, when ready: “<callsign>, ready for departure”. Do NOT say “ready for take-off” — the words take-off are reserved for the clearance itself. Owner to verify.
SRG1171 3.3
SRG1171 4.4
Draft — not yet verified against CAP 413
Treat the wording below as indicative only until it's confirmed against the current manual. Always defer to CAP 413 and your instructor.
Example calls (verify vs CAP 413)
DRAFT: “<callsign>, extend downwind, number 2 to a Cessna on final” → “Extending downwind, number 2, traffic in sight, <callsign>”. Owner to verify the exact readback expectations.
SRG1171 5.10
Draft — not yet verified against CAP 413
Treat the wording below as indicative only until it's confirmed against the current manual. Always defer to CAP 413 and your instructor.
Example calls (verify vs CAP 413 / AIP)
DRAFT: DACS: “<station>, <callsign>, request Danger Area Crossing Service for EG D123”. DAAIS: “<station>, <callsign>, request Danger Area Activity Information for EG D123”. Owner to verify exact phraseology and current service names.
SRG1171 5.5
SRG1171 6.9
Draft — not yet verified against CAP 413
Treat the wording below as indicative only until it's confirmed against the current manual. Always defer to CAP 413 and your instructor.
Exact calls (verify vs current CAP 413 — deliberately not asserted)
DRAFT: the exact wording for a Practice PAN and for requesting a Training Fix must be taken from the current CAP 413 — the existing D&D revision section already defers on this, and this topic should too until the owner confirms the current calls.