Jump to content

Weekend London (Area) Control Restrictions


Recommended Posts

Jack Edwards

Valid from 10 February 2021 UFN

Every Saturday and Sunday 1200-2200L

Weekend traffic on the network is approximately 80% higher than pre-pandemic levels. Pilot and ATC feedback supports the fact that area controllers are under considerable pressure to provide the consistent high standards of control commonly found in the UK.

Bandbox positions were created to allow area controllers to offer their services to more pilots in off-peak periods. For most of the weekend, using these sectors as originally intended is not possible.

Rather than remove bandbox positions, they are instead temporarily limited. These restrictions will be rescinded if/when weekend traffic levels return to pre-pandemic levels.

-----------------------------------

LON_CTR - May only be opened when 2 or more of the following positions are staffed by other controllers:

  • LON_N_CTR or MAN_CTR;
  • LON_C_CTR;
  • LON_S_CTR.

LON_SC_CTR - May only be opened when either:

  • LTC_N_CTR and LTC_S_CTR are both covered by other controllers (see next section) or;
  • LON_C_CTR or LON_S_CTR is staffed by another controller.

LTC_CTR - LTC can be a very intense sector with many more time-critical interactions than an AC position. The responsibilities of LTC_CTR must be split between a minimum of 2 controllers. For example:

  • LTC_N_CTR and LTC_S_CTR or;
  • LTC_CTR and LTC_SE_CTR or;
  • LON_C_CTR and LTC_S_CTR.

-----------------------------------

Example peak period London FIR split:

  • LON_C_CTR
  • LON_E_CTR
  • LON_S_CTR
  • LTC_S_CTR
  • MAN_CTR
  • LON_CTR

----------------------------------

FAQ

  • Can I always open any of the 'standard' LON_N/S/C/W_CTR sectors? - Yes
  • 2+ people are planning to split a bandbox position according to the restrictions, can I log on before they do? - Yes, common sense applies - a short grace period is assumed (same as opening LTC_SE/SW)
  • Could we open LTC_CTR, LTC_E_CTR and LON_E_CTR during peak periods? - No, as LTC_CTR takes LTC_NE_CTR in this cirumstance and therefore LTC_CTR is not split between 2 controllers
Edited by Jack Edwards
  • Like 14
Link to post
Share on other sites
  • Similar Content

    • Harry Sugden
      By Harry Sugden
      Effective 7 March 2021
       
      The Eurocontrol Islands (EURI_FSS) position has now been removed and as such, will no longer be opened. This affects the ownership order of airspace (FL245+) above the UK (London & Scottish FIRs), Ireland (Shannon) and Iceland (Reykjavík).
      All references to the position in the following documentation are therefore no longer applicable, and will be removed in future revisions:
      London FIR (EGTT) vMATS Part 2 London Agreed Levels Diagrams Scottish FIR (EGPX) vMATS Part 2 Scottish Agreed Levels Diagrams VATSIM Scandinavia (Reykjavík ACC) & VATSIM UK (Scottish ACC) LoA VATSIM Scandinavia (Polaris ACC - Stavanger) & VATSIM UK (Scottish ACC) LoA VATSIM Scandinavia (Copenhagen ACC) & VATSIM UK (Scottish ACC) LoA VATéir (Shannon & Dublin ACCs) & VATSIM UK (Scottish ACC) LoA VATéir (Shannon & Dublin ACCs) & VATSIM UK (London ACC) LoA ✔️ French vACC (Paris, Reims & Brest ACCs) & VATSIM UK (London ACC) LoA Belux vACC (Brussels ACC and Maastricht UAC – KOKSY) & VATSIM UK (London ACC) LoA Dutch vACC (Amsterdam ACC & Maastricht UAC – DELTA) & VATSIM UK (London ACC) LoA (Documents with a ✔️ have been updated since this post)
       
      All other Eurocontrol positions remain unaffected.
       
      Please see the announcement on the VATSIM.net Forum for more information.
    • Harry Sugden
      By Harry Sugden
      Valid 14 April 2021
      For the Manchester Midweek Madness event, in order to manage the increased workload in the North sector group, a temporary arrangement is made to allow for the splitting of the London North sector.
       
      AC North - LON_N_CTR (Relief: LON_N__CTR)
      Frequency: 133.700 MHz
      RTF callsign: London Control
      Coordination callsign: AC North
      Top-down responsibility for: AC Lakes & North Sea; PC West & East
      AC North is the parent position of the AC North group, as published in the London FIR (EGTT) vMATS Part 2.
       
      AC Lakes - LON_NW_CTR (Relief: LON_N1_CTR)
      Frequency: 135.575 MHz
      RTF callsign: London Control
      Coordination callsign: Lakes
      Top-down responsibility for: None
      AC Lakes is responsible for airspace West of a line passing approximately GOLES-NAPEX as shown in Figure 1. Unlike the AC North (133.7) position above, this position does not take ownership of the PC sectors beneath when they are not online.
       
      North Sea - LON_NE_CTR (Relief: LON_N2_CTR)
      Frequency: 128.125 MHz
      RTF callsign: London Control
      Coordination callsign: North Sea
      Top-down responsibility for: EGSH
      AC North Sea is responsible for airspace East of a line passing approximately GOLES-NAPEX as shown in Figure 2. Their top-down responsibilities reflect their airspace (i.e. Norwich) in the absence of other controllers.
       
      Agreed Levels
      For AC North Sea controllers (LON_NE_CTR), an Agreed Levels Diagram is available:
      North Sea 2021 03.pdf
       
      There are no agreed levels between AC Lakes and AC North Sea.
       
      Figure 1 - London AC North - Lakes Sector - Area of Responsibility

      Figure 2 - London AC North - North Sea Sector - Area of Responsibility

      This procedure does not alter the staffing permissions as defined in the UK Division Policy or GRP.
    • VATSIM UK
      By VATSIM UK
      London (EGTT) Agreed Levels Diagrams for all permanent positions in PDF format.
      Controllers should familiarise themselves with agreement conditions and coordination procedures, as detailed in the London (EGTT) vMATS Part 2.
      Note: Whilst every effort is made to reflect the contents of the London (EGTT) vMATS and Letters of Agreement, where there are any discrepancies, these documents shall take precedence over the diagrams contained within this download.
    • VATSIM UK
      By VATSIM UK
      London (EGTT) Sector Diagrams for all permanent positions in PDF format.
      Contains:
      South LAG - AC Worthing, AC Dover, TC South West, TC South East Central LAG - AC Daventry, AC Clacton, TC East, TC North West, TC North East North LAG - AC North, PC West, PC East West LAG - AC West
    • Harry Sugden
      By Harry Sugden
      Effective 22 April 2021
      Alongside introducing the capability for more advanced splitting options in AC South, some associated changes are being made to the day-to-day sectorisation. This affects mainly airspace over central London in what’s known as ‘TC Capital’. There are also some minor changes to airspace elsewhere in the sector. A number of agreements are also affected.
      Note: This Procedure Change does not introduce any new positions. The airspace of some of our existing sectors is changing, along with some agreements.
       
      Sectors
      Summary of Main Changes
      The airspace up to FL215 over central London and to the east of the current high level Worthing-Dover boundary is being transferred from Worthing to Dover. Two portions of airspace on and around the MAY-VATON track are transferred from TC South East to AC Dover. A section of airspace southwest of GWC from FL125-FL175 is transferred from TC South West to AC Worthing. Slight changes have also been made to the AC West and AC Daventry sectors in areas to the north of KENET and KIDLI.
      Want to know why? This post talks about the TC Capital airspace and why we’ve decided to change the ownership here in a little more detail.
       
      Revised Diagrams
      These changes are represented on the updated Sector Diagrams available for review HERE.
      Additionally, the areas that have changed are shaded in red on the following figures:
      Figure 1 - New TC South East Sector

      Figure 2 - New TC South West Sector

      Figure 3 - New AC Dover Sector

      Figure 4 - New AC Worthing Sector

       
      Agreements
      A number of agreements are affected by the changes to sectorisation, and there have been two further changes to agreements for EGLF outbounds via OTSID-BIG and Essex/Thames outbounds via LYD.
      The draft Agreed Levels Diagrams for 2021/04 are available HERE. Please note that further changes will likely be made before the release date, so it is important to download the final published version.
      The changes are available in table format here:
      Changes to Agreements.pdf
      The most notable changes affect:
      EGKK LAM departures - which are now transferred from TC South East to AC Dover (previously Worthing); and  Essex inbounds via VATON - which are now transferred from AC Dover (previously Worthing) to TC North East. -----
      Tip! If you prefer to visualise things, I recommend opening an existing Agreed Levels Diagram and the new one (linked above) side by side and flicking between them to look at what has changed. For example:

       
      Documentation Status
      The changes will be reflected in the 2021/04 releases of the UK Sector File, London (EGTT) vMATS, Agreed Levels Diagrams, and Sector Diagrams.
×
×
  • Create New...