Jump to content

CTP Eastbound 2021 - Scottish


Harry Sugden
 Share

Recommended Posts

It's CTP time! Hope you're all ready for some fun. It's no secret that this time around we have an acute shortage of controllers, so we are very grateful to the visitors who have offered to assist us, particularly on Scottish. Expect the roster to change, sorry about the amount of traffic (we'll try to keep it to a minimum)... any questions, shout to me or @Kieran Hardern!

 

Flow/Route/Level Restrictions

Expect anything on the fly to be communicated to you before your slot. Please ensure that you include non-standard coordination or restrictions in any controller changeover. This will be integral to ensure smooth interaction with each other and our neighbours. Already confirmed are:

  • ⚠️ 10-minute MDI from all UK airfields applied to successive departures bound for the London TMA
  •  Traffic departing for LEBL, EIDW, EGLL, or LOWW will need a release via the UK Flow Coordinator (callsign UK_FMP)
     
  • EGLL inbounds level cap from ScAC Rathlin (SCO_W) and ScAC Deancross (SCO_D) to London AC Lakes is  FL330 ⚠️
     
  • Northbound traffic level cap from ScAC East to BIRD (Reykjavik) is  FL280 ⚠️
  •  Westbound traffic level cap from ScAC West to EGGX via GOMUP is  FL280 ⚠️
     
  • Eastbound eFLAS between Scottish and Shannon. The only westbound levels into EISN shall be FL300 and FL320

    image.png.9f6d9b455e0d1975135a8b437be69c1e.png

Process for traffic to LEBL, EIDW, EGLL, or LOWW

Please speak to the UK Flow Coordinator (callsign UK_FMP) as soon as a plane bound for these airfields pops up. They will then handle the release process and get back to you.

See:

Adjacent Unit Sectorisation

There should be absolutely nothing abnormal in terms of our neighbours' sectorisation.

Agreed Levels Diagrams

Familiarise yourself with the Agreed Levels Diagrams here:

Top-Down

Apologies in advance that due to a distinct shortage of UK Area controllers, some top-down provision by controllers unfamiliar with the airspace is inevitable. We have put a plea out to UK S3 and below controllers to staff up airfields as much as possible. If you have any questions, we'll all be friendly in TeamSpeak / over text!

Other Notes

Scottish is likely to be quite busy. Don't be afraid to degrade top-down service to the bare minimum where necessary (assign a squawk and "report ready for departure" - then give an initial route and level when departure is requested). It is OK to make things up as you go along...

 

ScAC West

You're the first controller for a good number of aircraft coming off the ocean, so you'll likely need to assign squawks. Using the UK pack, this should be automatic when you assume a tag, but usually takes a few moments to generate. From experience, contact mes are often required as whether pilots get handed to (a) the right frequency, or (b) any frequency at all(!) is hit and miss.

Recommended is to use all levels (both directions from FL330 and above). Westbound levels cap at FL320. Individual coordination of aircraft is not required.

Important! ⚠️ Level cap for EGLL inbounds into London North is FL330.

Important! ⚠️ Level cap for westbound transatlantic flights via non-event track GOMUP is FL280. Aircraft should be descended to reach FL280 in good time prior to GOMUP.
 

ScAC Deancross

This position is the middleman. Most of the CTP work will be in on the left, out on the right. There will also be some ScTMA traffic to handle, but hopefully not too much!

Important! ⚠️ Level cap for EGLL inbounds into London North is FL330.
 

ScAC East

ScAC East will be busy. However, there is no convergence or crossing of routes so the majority of the time you will just need to be keeping an eye on speed and handoffs required, with some requests from pilots for changes in levels. 

From the south upwards, the event traffic exit points are: 

  • ERKIT traffic to EHAM - transfer to London North Sea (mostly online as LON_N_CTR tonight)
  • ROKAN traffic to EHAM - transfer to Amsterdam descending (usually EHAM_W_CTR) FL240 lvl ROKAN
  • AVRAL traffic to EHAM - transfer to Copenhagen at or before AVRAL (maximum 30 NM from AVRAL)
  • ELSAN traffic to LOWW - transfer to Copenhagen at or before ELSAN (maximum 30 NM from ELSAN)
  • BEREP traffic to EDDB - transfer to Stavanger at or before BEREP

If planes appear at EGPD or EGPE and you're too busy, it might be worth asking Deancross (SCO_D) if they are happy to handle this traffic top-down.

Important! ⚠️ Northbound traffic into BIRD is capped at FL280 during the busiest event hours.

Edited by Harry Sugden
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

  • Similar Content

    • Harry Sugden
      By Harry Sugden
      Effective 2 December 2021
       
      To increase the availability of the use of 3 NM radar separation, the terms of its use are revised.
      Section 3.3.4 in both the London (EGTT) vMATS Part 2 and Scottish (EGPX) vMATS Part 2 shall be amended as follows (additions in bold):
       
      When the only means of coordination is via text, this is not sufficient for the application of 3 NM radar separation between aircraft on different frequencies.
      Note 1: Both controllers/units must be approved to use 3 NM for these revised conditions to apply.
      Note 2: For APC controllers, local ATC documentation will specify the airspace in which 3 NM radar separation may be applied. In the absence of any local ATC documentation this shall default to within 40 NM of the aerodrome and below FL195.
    • Harry Sugden
      By Harry Sugden
      Effective 2 December 2021
       
      Due to the difficulty in applying time-based rules on VATSIM and the lack of a planner controller under busy conditions, the rules for the Deemed Coordination of En-Route Traffic are amended as follows in the Scottish and London vMATSs.
       
      Additionally, a new section is added:
       
      The next sector shall be notified via:
      Voice communication; Text communication; EuroScope coordination request*; or TopSky, which automatically highlights changes in RFL on the aircraft tag. *Rejection of the coordination request by the receiving controller should be actioned as appropriate either by follow-up verbal/text coordination or by reverting to the previously agreed RFL when an aircraft has not yet changed its level.
      Verbal or written acknowledgement is not required, but controllers should be mindful that the receiving controller may still raise an objection or propose an alternative level.
    • Harry Sugden
      By Harry Sugden
      Effective 2 December 2021
       
      The purpose of this change is to standardise, across the UK, the responsibility and process for the implementation of a new shared MSL within terminal control areas.
      When the pressure changes across an MSL boundary:
      The first APC/enroute controller to notice the change shall notify all affected units who also refer to the MSL; The first controller shall coordinate the agreement of an effective time that is at least 5 minutes from the time the pressure change was noticed. Aircraft operating at the old MSL are deemed separated from aircraft operating at the Transition Altitude until the new MSL is agreed to be in effect.
       
      Further Guidance
      We do not feel it necessary to define the coordination procedure any further, and trust that controllers will coordinate in the best way appropriate to the traffic situation. For example, it may be sensible for an APC controller to delegate the coordination of MSL to an enroute controller.
      Where an APC unit has traffic in the hold, it is recommended to coordinate with this APC unit early to take into account this traffic.
    • Harry Sugden
      By Harry Sugden
      It's CTP time! Hope you're all ready for some fun. It's no secret that this time around we have an acute shortage of controllers. We are very lucky to have enlisted the help of some visitors, without whom we would be in a dire situation. With this in mind, stay calm, expect the roster to change, and please don't complain too much about the traffic 😄 We'll try to keep it to a minimum...
      Any questions, shout!
       
      Flow/Route/Level Restrictions
      Expect anything on the fly to be communicated to you before your slot. Please ensure that you include non-standard coordination or restrictions in any controller changeover. This will be integral to ensure smooth interaction with each other and our neighbours. Already confirmed are:
      ⚠️ 10-minute MDI from all UK airfields applied to successive departures bound for the London TMA ⛔ Traffic departing for LEBL, EIDW, EGLL, or LOWW will need a release via the UK Flow Coordinator (callsign UK_FMP)
        Level cap for eastbound traffic into EGLL: ScAC Rathlin (SCO_W) & ScAC Deancross (SCO_D) --> LAC Lakes - FL330 EISN LIFFY --> LAC Lakes - FL330 EISN BANBA --> LAC West - FL330
        Eastbound eFLAS between LAC and ScAC to/from EISN. The only westbound levels into EISN shall be FL300 and FL320

      Process for traffic to LEBL, EIDW, EGLL, or LOWW
      Please speak to the UK Flow Coordinator (callsign UK_FMP) as soon as a plane bound for these airfields pops up. They will then handle the release process and get back to you.
      See:
      Adjacent Unit Sectorisation
      There should be absolutely nothing abnormal in terms of our neighbours' sectorisation. French sectorisation will be as documented in the vMATS and on Agreed Levels Diagrams; Shannon will be using their permanently published sectors. If anything abnormal arises, you will be informed.
      Holding
      Controllers should continue to adopt the phraseology we have used in previous events: "hold at Bovingdon as published, right hand turns".
      For a depiction of holding for Heathrow inbounds, see this post:
       
      West
      We will be operating up to a 3-way split during peak times, consisting of an Exmoor (south side), Pembroke (north side) and Sector 23 (final streaming into BEDEK for EGLL inbounds). See this post for details:
      Pembroke will have a relatively small amount of merging of EGLL traffic to do at NUMPO, as routes via EVRIN and BAKUR join a single stream down towards BEDEK. It is likely that the small amount of non-event transatlantic traffic headroom that the US have been given is will be via Pembroke sector, but this is a very limited amount per hour.
      Sector 23 will be responsible for any enroute holding at OKESI up to FL260. Close coordination with AC South (Worthing) and TC SW may be required to manage the multiple streams of traffic into OCK should it become full.
       
      North
      North is likely to be one of the busiest of the London groups tomorrow. We plan to split it 2 ways - AC North (covering North Sea, PC Northeast and PC Southeast) and Lakes (covering Lakes and PC West).
      EGLL traffic from Scottish and Shannon will be level capped at FL330, which should help to reduce the complexity of Lakes.
      Westbound traffic from North to Shannon is capped at FL320 (that is, westbound levels FL320 and below are the only ones available across the border).
      It is our intention to - at all costs - avoid holding at MCT. This will not be possible without severe limiting of domestic/EIDW flights to EGLL, which we endeavour to do.
       
      Central
      Not much to say here. At most, Central will be split 3 ways - Daventry, Clacton and TC North.
      If TC North cannot manage the BNN stack effectively, they may be downgraded to TC NW. Significant holding at LAM is a big warning sign - if it looks like there will be more than a few in the hold at LAM, inform Kieran, myself, or UK_FMP immediately. We really don't want to affect the flow coming out of BNN/OCK by having a big demand in the other stacks.
      In the corridor, if holding begins at HON, the same applies - speak to Kieran, myself, or UK_FMP and we will seek to put in the maximum flow constraints to prevent it moving further back to MCT.
       
      South
      AC South will have fun. TC South will have even more fun. It's unlikely that we'll be able to change TC South to TC SW only without a distinct Dover controller coming along just because of the traffic split here.
      The most important thing for TC SW is to keep that stack at OCK as tightly packed as possible and to communicate in advance and very clearly with Sector 23 and AC South. We always fall down with our communication when enroute holding begins, and this time we don't have the benefit of a dedicated Area coordinator because they have to be controlling.
      The French aren't doing anything non-standard, but please brush up on their possible sector configs and especially who to transfer planes to / coordinate with on the southern SITET/XAMAB/XIDIL boundary.
    • Harry Sugden
      By Harry Sugden
      The coordination box is a guide, and is not exhaustive. 
      LL CTP TC-ENR HOLD CTP21E.pdf

×
×
  • Create New...