Coordination between controllers is extremely important to ensuring safe and efficient operations take place at all UK and Ireland aerodromes and airspaces. This document, has been compiled to detail to controllers the standard of coordination that is required for controlling and taking exams within the XU Division.
When coordinating with other controllers the ‘callsign’ that you will use is different to the callsign that pilots use. These are not complicated callsigns, but the use of the correct one is important – these are detailed in the table below.
| Network Identifier | Coordination Identifier | Coordination Identifier Meaning |
|---|---|---|
| DEL | GMP | Ground Movement Planner |
| GND | GMC | Ground Movement Control |
| TWR | AIR | Air Control |
| APP | APC | Approach / Radar Controller |
| APP | INT | Intermediate Approach Controller |
| F_APP | FIN | Final Approach Controller |
| EGTT_X_CTR | LAC | London Area Control |
| EGTL_X_CTR | TC | London Terminal Control |
| EGPX_X_CTR | PC | Scottish Control (Prestwick) |
| EGPX_M_CTR | PC MTMA | (Prestwick) Manchester Terminal Manoeuvring Area |
| EIDW X CTR | Dublin ACC | Dublin Area Control |
| EISN X CTR | Shannon ACC | Shannon Area Control |
| EGVV/QQ CTR | Swanwick Mil | Swanwick Military |
| EGXX_FSS | LAC FISO | London Information |
| EGPX_FSS | PC FISO | Scottish Information |
Note: At aerodromes where, multiple controllers exist that perform the same function in different areas, the controller will append the designator for the area that they control. I.e. “Air North” or “GMC One”. This is also true for area positions. I.e. “LAC North” or “TC South East”.
At aerodromes, the ‘callsign’ is made up of a combination of the above table and the aerodrome that is being controlled. For example, a controller, connected as EGLL_1_GND would be “Heathrow GMC One” and similarly EGCC_S_APP would be “Manchester INT South”. Area positions are as noted.
Circumstances when coordination is required includes but is not limited to:
Aerodrome Control shall co-ordinate with Approach Control:
(1) departing (non-standard) IFR flights; and
(2) arriving aircraft which make their first call on the tower frequency (unless they are transferred to Approach Control).
Approach Control will co-ordinate with Aerodrome Control:
(1) aircraft approaching to land; if necessary requesting landing clearance;
(2) arriving aircraft which are to be cleared to visual holding points; and
3) aircraft routeing through the traffic circuit.
(CAP493: Section 2: Chapter 1: Aerodrome Control - Page 3)
Coordination can take place using a number of channels such as:
It is not suitable to announce your online/offline activity in Discord, this MUST be done in the ATC Chat on IVAN as not all controllers who need the information can see the XU Discord text chat.
One of the mnemonic’s used for handover of aerodrome and approach position’s is PRAWNS.
| P | Pressure | Pressure (QNH, MSL) |
| R | Roles | Which sector/ position are you controlling, who is controlling around you. |
| A | Airport(s) | Runway(s) in use |
| W | Weather | Visibility, weather avoidance, winds |
| N | Non Standard | Priority info. Navaids, danger areas, EAT’s, holding. |
| S | Situation | Explain traffic situation. |
One of the mnemonics used for handover of Terminal and Area control positions is WEST
| W | Weather | Winds, Pressure (QNH/ MSL) |
| E | Equipment | Radio frequency, Radar, Navaids. |
| S | Situation | Sector configuration, Military Area’s, Holding, Flow regulations. |
| T | Traffic | Traffic on frequency, Pending traffic, Potential traffic conflicts, planned solutions. |
Request clearance for (aircraft identity). (Type of Departure/ Aircraft Request)
| AIR | *Starts call |
| INT | “INT” |
| AIR | ”AIR, Request clearance for Ryanair 100T (Radar Vectored Departure, IFR circuits)” |
| INT |
”Clearance, Ryanair 100T, Cleared to Stansted, After Departure, climb Runway heading, altitude 4000 ft, Squawk 4670” |
| AIR | ”Ryanair 100T, Cleared to Stansted, After Departure, climb Runway heading, altitude 4000ft, Squawk 4670” |
| INT | “Correct” |
| AIR | *Ends call |
“Request release (Aircraft Callsign).”
| AIR | *Starts call |
| INT | “INT” |
| AIR | “AIR, Request release, Ryanair 100T” |
| INT | “Ryanair 100T, Released” |
| AIR | “Ryanair 100T, Released” |
| INT | “Correct” |
| AIR | *Ends call |
The approach/area controller may release an aircraft on a condition. For example:
| Phrase | Meaning |
| “(Callsign), Released at Time 30” | The aircraft must not depart until the time stated |
| ”Released subject (Callsign) +3 minutes” | The aircraft must not depart until 3 minutes after the subject aircraft departs. |
At airfields where airway clearances are used, The receiving Approach / Area control sector will specify departure instructions. These instructions should be passed to the pilot before departure.
| AIR | *Starts call |
| INT | INT |
| AIR | ”AIR, Request release, Logan 123” |
| INT | Logan 123, After departure left turn on track NAXIL, Released” |
| AIR | Logan 123, After departure left turn on track NAXIL, Released” |
| INT | ”Correct” |
| AIR | *Ends call |
To be added
| GMC | *Starts call |
| AIR | “AIR” |
| GMC | “GMC, Prenote, Speedbird 100T IFR Circuits” |
| AIR | Speedbird 100T IFR Circuits |
| GMC | ”Correct” |
| GMC | *Ends call |
Inbound release (a/c identity) squawking (four digits) (type) from (point of departure) released at (significant point, time or level), cleared to and estimating (clearance limit) at (time) at (level) expected approach time (time) (or no delay expected) contact at (significant point, time or level).
Example to be added
Radar handover (a/c identity) (position, SSR code and heading/observed track, if own navigation) (level) (additional information). Additional information shall include transfer of control details if not coincident with transfer of communication.
Example to be added
| LAC North | *Starts call |
| PC ALL | “PC ALL“ |
| LAC North | “LAC North, Request co-ordination” |
| PC ALL | “Pass your message” |
| LAC North | “Your traffic TOM123. My traffic SHT123, Squawking 2307” |
| PC ALL | ”SHT123, Identified” |
| LAC North | ”Request TOM123 maintain FL290, SHT123 will maintain FL280” |
| PC ALL | ”TOM123 will maintain FL290, SHT123 will maintain FL280. Coordinated.” |
| LAC North | ”Coordinated” |
| LAC North | *Ends call |
On outside calls, identity should be given in full for example:
London Area Control South, not abbreviated to LAC South.
ICAO do not use the UK CAA term “Radar Handover” instead ICAO use the term “Transfer of Radar Control”.