By Chris Pawley
For this weekend's SouthWest Overload event, in order to manage the increased workload and interest in controlling the West sector group, a temporary arrangement is made to allow for the split of the London West sector between the dates specified above:
LON_W_CTR (AC West)
West may be split into 2 positions: AC West (126.075) and AC Brecon (133.600). AC West remains the parent sector under the rules determining opening order and controller priority.
(Callsign “London Control”, Login: LON_W_CTR) is responsible for airspace South of a line passing approximately EVRIN-EXMOR-BDN VOR as shown above. Their top-down responsibilities reflect the airspace of this sector (i.e. Channel Islands, Newquay and Exeter) in the absence of other controllers.
(Callsign “London Control”, Login: LON_WN_CTR) is responsible for airspace North of a line passing approximately EVRIN-EXMOR-BDN VOR as shown above. Their top-down responsibilties reflect their airspace (i.e. Bristol, Cardiff, Gloucestershire, Kemble) in the absence of other controllers.
This procedure does not alter the staffing permissions as defined in the UK Division Policy or GRP.
By Chris Pawley
Effective 01 February 2018
From the effective date, the position of TC Bandbox is introduced.
RTF Callsign: "London Control"
Coordination Callsign: "TC Bandbox"
In order to open this position, both of the parent sectors (AC South and AC Central) must be online (in any form; via a bandbox is permitted)
This position is a bandbox of LTC_N_CTR and LTC_S_CTR. Where either of these positions (or their sub-sectors) are online, they will resume responsibilities for their respective pieces of airspace.
Changes to top-down priorities
Who to Call
If there are no aerodrome or approach services at your departure aerodrome, use this list to determine which area sector to call. Contact the first controller listed that is online. If in doubt, don't be afraid to ask. Another good place to check is the controller information, where information is usually displayed as to which areas the controller is covering.
EGSS / EGGW
LTC_NW, LTC_N, LTC, LON_C, LON
EGLL / EGLC / EGKB
LTC_SE, LTC_S, LTC, LON_D, LON_S, LON
LTC_SW, LTC_S, LTC, LON_S, LON
Changes to handoff procedures
Read from Left to Right, hand off to the first online station
LTC_SE, LTC_S, LTC, LON_S, LON_SC, LON, KKAPP
LTC_SW, LTC_S, LTC, LON_S, LON_SC, LON, KKAPP
LTC_NW, LTC_N, LTC, LON_C, LON_SC, LON, LL_N_APP
LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, LL_N_APP
LTC_SE, LTC_S, LTC, LON_S, LON_SC, LON, LL_N_APP
LTC_SW, LTC_S, LTC, LON_S, LON_SC, LON, LL_N_APP
LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, THAMES
Others as per the top-down coverage order for Thames
ESSEX, LTC_NW, LTC_N, LTC, LON_C, LON_SC, LON
LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, LL_N_APP (LAM only), ESSEX
LTC_NW, LTC_N, LTC, LTC_E, LON_C, LON_SC, LON, ESSEX, GW_APP
GW_APP, ESSEX, LTC_NW, LTC_N, LTC, LTC_E, LON_C, LON_SC, LON
LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, ESSEX, GW_APP
The data necessary for this trial was introduced in the sector file release for 2017/12 (on 9th November 2017) - updating your sector file is therefore essential to ensure there is a seemless introduction of these new procedures.
There is quite alot of documentation still to be incorperated into this update, but this will be conducted as time permits.
By Chris Pawley
Updated agreement between Manchester TC East Sector and AC North:
Manchester Group, Midlands Group, Barton, Leeds, Blackpool, Warton, Newcastle, Durham Tees Valley outbounds via AMVEL should be handed to AC North climbing to FL270 FL280
Manchester/Barton/Leeds/Blackpool inbounds via OTBED should be handed to Manchester TC East level FL280 FL290 (level by/abeam OTBED)
The UK Sector File has been updated with these changes, a new version of the agreed levels diagram will be released in a future cycle.