This page is to help pilots flying in UK airspace determine when they should contact one of our Area (CTR) sectors. We have tried to keep this as simple as possible, splitting the information into distinct sections depending on your type of flight.
If you are ever unsure, please PM one of our controllers saying that you have read the website but are unsure whether you need to contact them. They will gladly advise!
Do not call EGTT_I_CTR or EGPX_I_CTR as civilian ‘airliner’ traffic – these positions are for Flight Information Services outside of controlled airspace only.
Do not call EGVV_CTR or EGQQ_CTR as a civilian ‘airliner’ – these positions are primarily for Military operations. UK FIS may be available on request/as coordinated with civilian area controllers (normally only above FL100).
The two main radio callsigns for Area controllers in the UK are:
Always contact local ATC (DEL/GND/TWR/APP) where it is online. There are a number of APP positions that cover more than one airfield top-down:
In the absence of local ATC, our area sectors provide a top-down service at airfields contained within the sector(s) they are controlling. You should request clearance, pushback, taxi etc. as you would if there were an aerodrome controller online.
At airfields outside of controlled airspace you may, if you wish, depart at your own discretion. However, if you intend to join controlled airspace, it is generally advisable to request airways clearance from the controller prior to departure.
In the absence of local ATC, contact the first controller listed below that you see online (the priority is from left to right). Sometimes, the callsign may differ slightly, so it is best to cross-check the frequency too.
The location of these airports within our sectors are also marked on the diagrams in the next section.
MAN_SE_CTR (134.425) → MAN_E_CTR (133.800) → MAN_CTR (133.200) → LON_N_CTR (133.700) → LON_NW_CTR (135.575) → LON_CTR (127.825)
Leeds (EGNM), Doncaster (EGCN), Humberside (EGNJ), Newcastle (EGNT), Teesside (EGNV)
MAN_NE_CTR (135.700) → MAN_E_CTR (133.800) → MAN_CTR (133.200) → LON_NE_CTR (128.125) → LON_N_CTR (133.700) → LON_CTR (127.825)
Liverpool (EGGP), Hawarden (EGNR), Isle of Man (EGNS), Blackpool (EGNH)
MAN_W_CTR (128.050) → MAN_CTR (133.200) → LON_NW_CTR (135.575) → LON_N_CTR (133.700) → LON_CTR (127.825)
LON_NE_CTR (128.125) → LON_N_CTR (133.700) → LON_CTR (127.825)
East Midlands (EGNX), Birmingham (EGBB), Coventry (EGBE)
LON_M_CTR (120.025) → LON_C_CTR (127.100) → LON_SC_CTR (132.600) → LON_CTR (127.825)
London/Stansted (EGSS), London/Luton (EGGW), Cambridge (EGSC)
LTC_NW_CTR (121.275) → LTC_N_CTR (119.775) → LTC_CTR (135.800) → LON_M_CTR (120.025) → LON_C_CTR (127.100) → LON_SC_CTR (132.600) → LON_CTR (127.825)
London/Heathrow (EGLL), London/City (EGLC), Southend (EGMC), Biggin Hill (EGKB), Lydd (EGMD)
LTC_SE_CTR (120.525) → LTC_S_CTR (134.125) → LTC_CTR (135.800) → LON_D_CTR (134.900) → LON_S_CTR (129.425) → LON_SC_CTR (132.600) → LON_CTR (127.825)
London/Gatwick (EGKK), Farnborough (EGLF)
LTC_SW_CTR (133.175) → LTC_S_CTR (134.125) → LTC_CTR (135.800) → LON_S_CTR (129.425) → LON_SC_CTR (132.600) → LON_CTR (127.825)
Southampton (EGHI), Bournemouth (EGHH)
LON_S_CTR (129.425) → LON_SC_CTR (132.600) → LON_CTR (127.825)
Bristol (EGGD), Cardiff (EGFF), Exeter (EGTE), Gloucester (EGBJ), Newquay (EGHQ), Channel Islands (EGJJ/JB/JA)
LON_W_CTR (126.075) → LON_CTR (127.825)
Edinburgh (EGPH), Glasgow (EGPF), Prestwick (EGPK)
STC_CTR (126.300) → SCO_D_CTR (135.850) → SCO_WD_CTR (133.875) → SCO_S_CTR (134.775) → SCO_CTR (135.525)
Belfast/Aldergrove (EGAA), Belfast/City (EGAC)
STC_A_CTR (123.775) → SCO_R_CTR (129.100) → SCO_W_CTR (132.725) → SCO_WD_CTR (133.875) → SCO_CTR (135.525)
Aberdeen/Dyce (EGPD), Dundee (EGPN)
SCO_S_CTR (134.775) → SCO_E_CTR (121.325) → SCO_CTR (135.525)
Inverness (EGPE), Stornoway (EGPO), Kirkwall (EGPA), Sumburgh (EGPB), Wick (EGPC)
SCO_N_CTR (129.225) → SCO_E_CTR (121.325) → SCO_CTR (135.525)
Our controllers will always send you a contact me if you are entering their airspace. However, if you’d like to pre-empt their call, please use the diagrams below for an idea of where each sector covers.
You are encouraged to look-up and plan for descent in accordance with your expected STAR. If you need to descend before you enter an online controller’s airspace, then please do.
The main London sectors (North, South, Central & West) are shown below. Sometimes these sectors are bandboxed using the LON_SC_CTR or LON_CTR callsigns.
e.g. If LON_CTR, LON_S_CTR and LON_W_CTR are online, then the...
We regularly split off the airspace in the London TMA area with LTC sectors, which are shown in the diagram below. There are 4 main sectors (NE, NW, SE, SW) which can be ‘bandboxed’ together using the LTC_N_CTR, LTC_S_CTR or LTC_CTR callsigns.
The top of these sectors is generally at FL155, up to a maximum of FL185.
It is especially important to descend in accordance with the STAR when only these sectors are online.
The most frequent callsign you will see for Scottish Control is SCO_CTR which bandboxes all Scottish airspace. Two main splits are shown on the diagram below.
The STC_CTR callsign covers an area below FL255 around the Scottish TMA (near the main airports, EGPH, EGPF and EGPK).
The STC_A_CTR callsign covers an area below FL255 in the Belfast area, with responsibility for EGAA and EGAC traffic.
If Scottish airspace is split any further, it will most likely be during events when lots of ATC is online to direct you between controllers, so do not worry.
If you are departing from an airfield inside controlled airspace, then you must obtain clearance for all stages of your departure from the relevant area controller, as set out in Section 1.
If you are departing from an airfield outside of controlled airspace, then you may ask the area controller directly above that airfield whether they are able to provide an air traffic service.
If you have departed from an airfield without speaking to ATC but wish to enter controlled airspace, you must obtain a clearance from the area controller that covers that airspace before doing so. Feel free to ask a controller whether they cover airspace if you are unsure.
EGTT_I_CTR (124.600) – "London Information"
EGPX_I_CTR (119.875) – "Scottish Information"
Both of these positions are able to provide a Basic Service, which is a type of UK Flight Information Service (UK FIS) (see page 71 of The Skyway Code), to aircraft operating outside of controlled airspace.
They are also able to coordinate airways joining clearances for IFR departures from airfields outside of controlled airspace.
Military airfields are not covered 'top-down' by the civilian Area Control positions outlined in Section 1.
The same principles apply for military operations – contact local ATC if online but otherwise, the two main relevant callsigns are:
EGVV_CTR (135.150) – "Swanwick Mil"
Covers EGTT FIR airspace and airports for military operations, as well as in the EGPX FIR when Swanwick Mil (North sector) is offline.
EGQQ_CTR (134.300) - "Swanwick Mil" (North sector)
Covers EGPX FIR airspace and airports for military operations.
If you are departing from a military airfield and joining the airways system as civilian air traffic does, please ensure you request airways joining clearance from the relevant civilian area sector (in Section 2) before you enter controlled airspace. If you are unsure who to obtain this from, please ask a controller.
For the purpose of controller bookings, the 'Primary Sectors' are defined as:
The 'Secondary Sectors' are defined as:
Members may open either a single Primary or Secondary sector, or a valid combination of
Primary (e.g. LON_SC_CTR) or Secondary (e.g. LTC_CTR, MAN_CTR) sectors.
Further splits require the remaining portion of the Primary or Secondary sector to be staffed too - e.g. opening LTC_NE_CTR requires LTC_NW_CTR (as the remaining portion of LTC_N_CTR) to be online. Splits not defined in the London or Scottish FIR (EGTT) vMATS Part II require specific approval from the Operations Department in the form of a Temporary Instruction or Procedure Change.