Skip to main content

ORH - Operational Revision Highlights

This page summarises operationally relevant changes to material/procedures for ATS in Sweden FIR.

For an unfiltered technical changelog, see GNG Package Changelog or vATIS

AIRAC 2403

  • Arlanda SID from RWY 19R to BABAP and TOVRI has been revised. Due to the unpredictability of using an altitude (2500 ft) as initiation of left turn the new SID is instead based on waypoints. This will give controlles a more predictable trajectory for east-bound departures. The waypoint where the the left turn begins still has an altitude restriction of 2500 ft to allow for independent approaches to RWY 19L. In the SID description there is a note stating that aircrafts unable to reach 2500 ft before commencing left turn shall "continue on track 178° and inform ATC". We can probably not expect VATSIM-pilots to comply with this, however the separation to missed approaches on RWY19L is worth monitoring even though it should be procedurally separated. Speed restriction can be lifted by APP once the aircraft passes SA554 (the southern tip of the turn). A Minimum Departure Interval (MDI) of 120 seconds is until further valid for east-bound departures to protect sector E.

 

  • To facilitate a more seamless transfer of traffic between ESMM ACC and ESSA/SB APP when ESOS sector 2/6/7 is not covered, some changes has been made to the sector sequence. Relevant ESMM ACC positions now act as a guest in the ESOS 6 sector closes to XILAN and a low priority owner of some ESOS 2/7 sectors in the area of PETEV, NOSLI, TRS and NILUG. This will generate a correct sector sequence allowing ESMM ACC and ESSA/SB APP to transfer traffic between them more easily. Due to limitations in EuroScope there are some restriction on how this works. 
    • For traffic departing via PETEV, NOSLI and TRS: 
      • APP shall climb traffic to correct XFL for relevant TMA exit point.
      • All traffic will have ESMM as next sector regardless if traffic will climb above FL 285 or not. APP need to check RFL and if below FL 285 that traffic shall be sent to UNICOM. 
      • ESMM will have all departures as coordinated regardless of RFL until traffic passes about 10 nm south of TMA-exitpoint.
    • For traffic departing via BABAP and ALOLA: 
      • No change to sector sequence. If RFL above 285, APP can manually transfer traffic to ESMM.
    • For traffic arriving via XILAN, TRS and NILUG: 
      • ESMM shall descend traffic to correct XFL for relevant TMA entry point.
      • Only once traffic descends below ESMM airspace will the sector sequence show correctly.
      • For arrivals via XILAN if ESOS is online: a late transfer to ESOS once the traffic has already entered ESOS airspace will result in the wrong sector sequence. It will show APP as the next sector even though traffic shall be transferred to ESOS.
    • For traffic crossing in the area of PETEV, NOSLI, TRS and NILUG: 
      • Traffic below ESMM airspace might show as coordinated for ESMM ACC even though traffic is below FL 285. This traffic can be ignored.

 

  • The C-flag at row 0 in the label that indicates that inbound clearance shall be issued has been overhauled. Now they are more filtered to reduce the number of spurious C-flags. E.g. ESMM ACC will not have C-flags for traffic that ESOS ACC is responsible for issuing inbound clearance for. Also, now C-flags only shows for controlled airports as no inbound clearance is issued for uncontrolled airports like AFIS.

 

  • CPDLC address for GG/SA/SB APP has been added since approach now can use CPDLC in real life. There is a limitation in TopSky, when you log on with an airport in the position name, that airport will be prefilled in the CPDLC sign in window. To get correct functionality change to a correct CPDLC address. 
    • ESGG_E_APP -> ESGE
    • ESGG_W_APP -> ESGW
    • ESSA_E_APP -> ESSE
    • ESSA_W_APP -> ESSW
    • ESSB_APP -> ESSS

 

  • The CARD (Conflict And Risk Display) is now automatically displayed in the primary ES-instance for any ACC position. As it is mandatory to display CARD in real life and I urge you to use it to. It will help you discover conflicts up to 20 minutes ahead of time.

 

  • The CPDLC login window is now also automatically displayed for positions that can use it. This is to promote the use of data link functionality. If your Hoppie code has expired please request a new one and put it in the TopSkyCPDLChoppieCode.txt in the plugin folder to have it automatically preset.
Back to top