Jump to content
Sign in to follow this  
Chris Pawley

atc-discussion Cross the Pond Westbound Information

Recommended Posts

Chris Pawley

Hello All,

This post contains some useful information for CTP Westbound 2019



Traffic Flow:


Traffic flows outbound from EGKK and EGLL via GIBSO and ADKIK and via LAM (EGKK only)

Some high level transiting traffic from Central to West near CPT


Traffic from EGKK entering at GIBSO/ADKIK and leaving via either EVRIN or SLANY. SLANY traffic needs to cross over traffic at cruise level in the L9 airway


Traffic from EHAM and EDDH entering in the RAVLO area and leaving into Shannon near BAGSO. Crossing traffic underneath ex EGKK for Scottish and some (6 an hour) merging with mainland Europe traffic to exit at BAGSO.


Traffic ex EHAM/EDDH entering in the IBNOS delegated airspace and leaving at CPT. Underneath, LAM departures from EGKK routing via the DTY corridor, expect this area to also be busy with non-event Heathrow departures to West Coast destinations.

Shannon Sectors can be found here:-



Edited by Chris Pawley

Share this post

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now
Sign in to follow this  

  • Similar Content

    • Chris Pawley
      By Chris Pawley
      The Letter of Agreement between London and Amsterdam (Dutch vACC) is revised to take into account changes in AD3 at the end of 2018. It's available here.
    • Harry Sugden
      By Harry Sugden
      Hi all,
      I've been working to trawl through the agreements in the sector file to introduce more of the arrows to indicate that an agreement is climbing/descending (rather than level by the point shown), so you should start to see more of these with an update to 2019/05 when it's out.
      If you have no idea what I'm talking about, the first few were introduced in December, and are as shown in this procedure change post. (And also here:)

      [If you're not seeing them, you might need to expand the width of your Sector exit point name column to 6 rather than 5.]
      As they are rolled out, I'd quite like to know whether people find the fix name useful at all. They're perhaps advantageous in that they give you a rough idea of where the transfer takes place, but I'm of the personal opinion that they might look better as simply an arrow in order to differentiate completely from those agreements that are actually level by.
      What do you think?
    • George Barlow
      By George Barlow
      Hello all,
      Since the enrollment of the dedicated VCCS server, there have been various issues regarding connection, general calling and also the sound that alerts you of an incoming call. I thought I would take the time to address these issues and supply a possible fix.
      Connection issues to the server & General calling
      Many have faced this issue and the reason behind many of you getting a 1797 issue is due to the revision of Euroscope you are on. The most current beta released is r19, which can be downloaded here: http://www.euroscope.hu/installbeta/EuroScopeBeta32a19.zip All of the contents in this .zip file should be moved to your main Euroscope directory (Default: C:\Program Files (x86)\EuroScope), please note that this will require you to overwrite existing files in the directory - a backup of your Euroscope folder should be made before transferring the files.
      Incoming call alert sound
      This issue occurs due to the current 'landline_request.wav' is too long. A simple resolution to this would be either to crop the sound file down yourself or download a new and improved one, courtesy of George Peppard: https://drive.google.com/file/d/11Tq58cAVQRX8AuHa1aCpnwi4t7qeqrvv/view?usp=sharing This file should overwrite the current 'landline_request.wav' file in your main Euroscope directory (Default: C:\Program Files (x86)\EuroScope\Sounds\), restart Euroscope after this change and this issue should've been resolved - be sure to make a backup of this file before overwriting!
      Multiple Euroscope instances open & VCCS won't work
      This issue occurs when two or more VCCS instances are opened/used in one single connection to the network (usually by proxy). This can be resolved by making sure you only open the 'VCCS dialogue' on one instance or making sure you stick to calling other positions on one of the Euroscope instances only - switching between two instances on a proxy connection will confuse VCCS and the server, potentially causing further issues.
      Majority of the issues faced with VCCS are down to either the server address entered wrong or not having the most up-to-date beta of Euroscope.
      If any other issues arise that I have not addressed, do give me a shout through private message on the forums, Slack or Teamspeak.
      Hope this helps use VCCS to its full potential, giving a better amount of realism on the VATSIM network.
      Kind Regards,
  • Create New...