General

• Overview
• Revision Highlights
• Useful links and resources
• Observer's Guide
• EuroScope and GNG package Installation
• EuroScope Profiles
• TopSky Profile
• TWR / TWR CDM Profile
• Software and Tools
• vATIS
• AMAN (MAESTRO)
• TS VCCS (Ground to Ground Coordination)
• AFV (Audio for VATSIM)
• VatIRIS
• GNG Package Changelog

Overview

This page highlights how operational information for ATS in Sweden FIR is distributed to controllers.

Announcing operational Changes

Operational changes are announced in in the #swedish-bulletins channel on our Discord server. example of changes: GNG Package updated, vATIS profile updated, GOP/LOP/LoA Updated.

Changes are summarised in Revision Highlights.

Wiki Pages

The pages listed below can be found under "ATC Sweden"

GEN - General Operational Information

Contains general information for controllers in Sweden, also containing information about the tools used for/when controlling, such as Euroscope, TopSky, AFV, vATIS.

GOP - General Operational Procedures

Information relevant to all ATS positions in Sweden FIR, necessary for understanding the LOP.

LOP - Local Operating Procedures

Information specific to an Airport and/or ATS Position

LoA - Letters of Agreement

Contains agreements between Sweden FIR and its neighbouring FIR/UIRs regarding airspace, coordination, transfers of aircraft etc.

Event Procedures

Contains information intended exclusively for use during events.

Training in Sweden

Contains general information about ATC training in Sweden and training documents.

Swedish Airports & Charts

Contains information and links mainly intended, but not limited to, pilots.

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

EuroScope does not allow for plugins to overwrite when updating the GNG package using the automatic download. After updating, close EuroScope then go to %appdata%\EuroScope-> ESAA > Plugins > Updated Plugin" and copy the .dll files in the folder. Thereafter go back in the "Plugins" folder and paste the .dll files there. Overwrite existing files when prompted.

AIRAC 2505

The new AIRAC provider for GNG is taking longer than expected. The files will still indicate AIRAC 2413.

ESGG

• Standard taxi routes removed. LOP ESGG TWR updated. There is no difference in ATC procedures as GND should give complete taxi instructions anyway.
• Information about propeller traffic has been clarified.

ESSV

New SID/STAR available.

AIRAC 2504

GOP Updated

• Minimum horizontal separation changed - Now 3 NM may also be used also outside TMA below FL195.
• Other minor changes, mainly to terminology used ("APP" replaces "TMC").

(ESOS) ACC Restructure

The position groups for Stockholm AoR (ESOS) have been restructured.

• ESAA replaces (old) ESOS 1 -> No ESOS position will cover ESMM sectors (and vice versa).
  • Except for ESAA position replacing ESOS 1, ESMM positions/sectors remains unchanged.
• ESOS 3 remains the main position, covering all of ESOS AoR.
• Most other ESOS ACC positions have been revamped.

See ACC Appendix A for more information.

The new ESOS main positions are added to VATSpy (and ESMM K), the updated sector priorities will soon be added to VATGlasses, both of which can be shown on VATSIM Radar.

RTC Malmö added

A new RTC (Remote Tower Centre) position is available, RTC Malmö (ESSR_MM_APP), available to S3 controllers.

• RTC Stockholm (the pre-existing RTC position) will will cover airports that fall under top-down coverage of ESOS ACC.
• RTC Malmö will cover airports that fall under top-down coverage of ESMM ACC.

See LOP RTC for more information.

AIRAC 2503

General

• To remove nuisance distractions the messages ES shows have been revised. Some messages like Info, Server and Coordination messages have been removed. Some messages have been down prioritised to remove distractions and unnecessary clicks when removing them. 

TopSky

• With the new LOP for ESGG TWR the way DCL is handled by DEL is changed. TopSky is now set up so if a flight is not assumed when the DCL messages is sent, the preselected frequency will be the frequency for the controller covering the GND position. However, if a flight is assumed when the DCL message is sent, the preselected frequency will be the controller's own frequency.

CDM

• All profiles are now using the CDM-plugin CTOT function instead of the TopSky version.
• For the TWR CDM profile (only for ESSA) the Right click has changed to allow for sending REA (Ready messages) for traffic with system generated CTOTs. The same will happen if you select "Ready TOBT". 
• For the TopSky and TWR profile the CTOT will display system CTOT if any. Same click functionality as describes above.
• To be able to manually add/change/remove a CTOT you have to be "Master" for that airport even though the airport is not necessarily a CDM airport. To become master, you type the following: .cdm master XXXX

Revised LOPs

• ESGG TWR
• ÖKC

AIRAC 2413

General

• Added new tex aliases for unruly pilots
  • .listen - when not listening
  • .plane - when not able to fly the plane
  • .many - when busy
  • .new - for new pilots, includes links to VATSIM CoC and Learning Center
• ESMT MVA updated (TMA sector a changed)

AIRAC 2412

General

• Standard inbound clearance for ESTL is now via SOGJU.

TopSky v2.5 beta 15

• Now possible to highlight AFL by Left Click on AFL.

AIRAC 2411

• Updated login profiles

TopSky v2.5 beta 14

Revised LOPs

• ESKN
  
• ESMS
• ESNU
  
• ESOK
• ESPA
• ESSP
• ESSV
  • Standard inbound clearance is now via VSB, unless "pink value" via TMA entry point is sent ESSV->ACC
• ESTA
• ESTL

AIRAC 2410

• SI sequence tweaked at ESGG
  • TWR should no longer be skipped for arrivals to ESGG.
  • Aircraft shown in grey for DEL unless assuming, then correct sequence to GND.
• Added VCH CTL (cleared to land) flag in Sector List for TopSky-profile.
• Removed all separate non-Swedish TMA, they are now consolidated to one selection INT TMA.
• ESTL SID/STAR/ILS unavailable due to VOR LJU withdrawn. RNP still available (REF AIP SUP 200/24). 

TopSky

• All non-Swedish TMA now consolidated to one: ARTCC HIGH/INT TMA.

GRP

• ESSA
  • Added long term closure of APN BC (REF AIP SUP 192/24), no safety nets activated, the closed gates will not be automatically assigned by GRP.
  • Terminal 3 open again.

AIRAC 2409

TopSky v2.5 beta 13

• All traffic assumed to be mode-S equipped, disregarding equipment filled in FPL.

Virtual Controller Helper (VCH)

• Added Taxi to pending requests menu.

AIRAC 2408

Virtual Controller helper (VCH) added.

VCH list entries are NOT published to other controllers, except "hold short of" which is forwarded when a strip is transferred.

• Pending requests field added to the start-up list.
  • Shows and automatically sequences pending requests in the order they were entered.
  • Automatically clears pending request when the corresponding clearance is entered in STS.
• Hold short of field added to taxi out, taxi in and ADC sector lists.
• Cleared to land flag (Now from VCH, replacing TopSky mark) 
  
  • Shown within 12 NM from ADES. Red until toggled green.

VFR Overhaul.

• VFR-fixes now 5 letter fixes (or less when actual name is shorter).
  • Points with cardinal directions have XXYYY syntax, XX=last two letters of ICAO, YYY=direction.)
• VFR maps revised, adding one map showing full VFR point names (including ÅÄÖ).
  • ALT+V Toggles VFR Points map.
  • ALT+B Toggles VFR Points + Labels map.
• VFR-SIDs added for all controlled airports, named VFR•XXXXX

AIRAC 2406

No major changes

AIRAC 2405

TopSky v2.5 beta 8

ALL SWEDISH APP/APS/ACC CONTROLLERS ARE URGED TO REVIEW THIS INFORMATION IN FULL

This post highlights the most important changes to the Swedish GNG package, now using TopSky v2.5 beta 8.

For an exhaustive list of changes, refer to TopSky plugin for EuroScope - Version History.pdf included in the GNG package.

For a technical manual, refer to TopSky plugin for EuroScope - General - B.pdf included in the GNG package (relevant paragraph referenced below where applicable).

SSR Code Generation

Generating a new SSR Code is now done using the Get SSR button in the SSR Code menu (see 6.10)

• The previous method pressing Ok where no code has been assigned is no longer possible, that button is greyed out.

Waypoint menu

Waypoint menu revised, left click on COPN/COPX or NPT to open (see 6.3).
"Pink Values" (SYSCO/System Coordination) are no longer sent automatically

• To manually send Pink Values where necessary, use Probe in the Waypoint menu (this also activates a FLEG to probe the effect of the possible route change), then use left click to send a SYSCO. Probe mode can also be activated by right clicking any waypoint in the TopSky Waypoint menu.
• Right clicking a waypoint in the old Euroscope Waypoint menu still works for assigning direct-to clearances without sending Pink Values.

Auto DCL/PDC

Datalink departure clearances are now sent automatically if the departure clearance has been prepared in the departure clearance window (7.43) by the time the departure request is sent (see 7.3).

Track Labels

For a complete description of the TopSky track labels, flight lists and its functions, see TopSky | Wiki.

Monitoring Aids (see 11.) are now shown differently

• CLAM (Cleared Level Adherence Monitoring): Yellow L shown in row 0.
• RAM (Route Adherence Monitoring): Circle shown surrounding the RPS (Radar position symbol).
• DUPE (Duplicated squawk): Yellow D shown in row 0.

Other Functions/Data Fields.

• Right click on COPN/COPX to toggle Route draw (FLEG) with MTCD.
• Right click on AFL/XFL toggles AFL/XFL level band highlight (see 5.3.8.9).
• Left click on GS or • (MTCD indicator) invokes SEP tool (see 5.3.3).
• Left click on ↑ or ↓ (vertical trend indication) invokes SEP tool with VSEP (see 5.3.3).
• DIAS and DMACH ("downlinked" IAS/MACH estimated using upper winds) is now available, shown in row 4 beside DHDG/DRC.

Keybord Shortcuts (ALT+)

• A: Toggles Basic ATS-Routes map.

• V: Toggles VFR Points map.

• F: Toggles TWR/APP Frequencies map.

• T: Toggles TMA Altitudes map.

• M: Toggles MVA/AMA map.

• F1: Opens new Notepad window.

  • GeForce Experience/GeForce uses the same keybind to take screenshots. If experiencing problems, disable the overlay or change the keybind as shown here.

• F2: Invoke SEP tool (see 5.3.3).

• F3: Invoke QDM vector (see 5.3.1).

• F4: Toggles quick look (see 5.3.8).

• F5: Toggles all prediction lines on/off.

• F6: Opens runway approach line window (see 7.37).

• F7: Opens FPL selection window (see 7.7).

• F8: Opens SSR code menu for the find track function (see 5.3.10 and 6.10).

• F9: Opens create APL window (see 7.10).

• F10: Toggles filtering of uncoupled labels (see 5.3.8.3).

• F11: Opens small QNH/TL window (see 7.27).

• F12: Opens track control window (see 5.3.5).

Airspace Management window

For exhaustive information about the ASM window see 7.5

Activation data of R/D-Areas (incl temporary from AIP SUP) are loaded automatically when signing in to an ATC position (it can also be done manually by pressing AUP in the ASM window).
This data is loaded from LFVs AUP (Thank you very much Felix!)

To toggle AUP activation data, press AUP in the bottom left corner of the ASM window.

• AUP shown in yellow: Activation data is loading/did not load successfully.
• AUP shown in white: Activation data is loaded and in use.
• AUP greyed out: Activation data is deselected.

Areas marked with FLYG contains aircraft activities (IRL), this indicates that an increased lateral separation must be applied to the area (see GOP).

Area activations are now automatically synced between Euroscope instances.

Moving SEP/QDM Labels

QDM Vector/SEP tool labels can be moved by middle mouse button clicking on the:

• QDM vector label.
• Tip of a SEP tool line.

Multi-QDM Vector

For exhaustive information about QDM vectors see 5.3.1

QDM vectors drawn from a fixed point to several tracks (aircraft) creates a Multi-QDM group, (see 5.3.2)

When hovering over a track label of one of the tracks in a group, a relative distance indication is shown in all other vectors in the same multi-QDM group.

Left click on any QDM vector (connected to a track) in a group to continue drawing within that group.

Other

Other changes.

• TSA Hold (For suspending APW/SAP for activities in TSA) now called Suspend (see 6.1.8), available in the Hold menu, accessible through the Callsign menu (6.1) or Waypoint menu (6.3).

• The old QNH/TL Window has been replaced by two windows:

  • Airfield Data window, showing QNH/TL and more data for several airports (see 7.23).

    • Using this and deactivating all fields in View is the closest thing you can get to the old QNH/TL Window.

  • Small QNH/TL window, showing QNH/TL for only one airport (see 7.27).

• Upper Winds window (7.22) displays upper winds and temperatures at a specified coordinate/position.

  • This window is automatically opened when signing in to an ATC position to show DIAS/DMACH. After loading, this window may be closed.
    

• STCA alert sound activated (Only triggered on assumed aircraft)

• Shortcut window added (see 7.17).

• The ETO field in TMLs (Traffic Management List 1 & 2) displays:

  • ETA over airport when list not filtered on point
  • ETO over point specified in filter (see 8.8).

• Show hidden (by CJI filter etc) labels by middle mouse button click RPS (radar position symbol).

• Enter "present heading" in AHDG by right click, shown as an H without numbers.

• OP-TEXT and OP-TEXT2 is editable also by downstream controller (Green/coordinated labels). This requires both parts to use v2.5b8.

2024-04-02

LOP ESNQ

• There are no major changes from the previous version, except that the new version has some guidance on how to separate traffic at ESNQ where the high MVA means that vectoring for approach is not possible.
• Also, RNP STAR is now considered standard procedure, so traffic unable RNP or requesting conventional STAR should be coordinated.

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.

  • Get your code

Useful links and resources

Charts/Flight Planning

• eAIP Sweden

• Daily use plan for R- and D-Areas

• wx.awos.se (Real ATIS / MET REPORT for some Swedish airports: ESSA, ESGG, ESMS, ESSB, ESKN, ESOW, ESGP and more)

• Skyvector (Map for route VFR/IFR Route planning)

• Openflightmaps (Open source VFR Maps for some parts of Europe)

• LFV eCharts

  • (with MIL PCA sectors)

• OpenAIP Map (Showing Gliding Sectors)

• LFK Flight Planner (Flight planner for VFR Flights, in Swedish)
  

• Eurocontrol - AIRAC Dates

• Eurocontrol - Cartography (Regional charts and others)

• Eurocontrol - Odd/Even? Flight level orientation map
  

Navigation data (Paid services)

• Navigraph (Paid subscription service, Navdata, VFR/IFR Charts (Jeppesen))
  

Flight tracking and live ATC feeds

• Flightradar24

• ADS-B Exchange

• FlightAware

• LiveATC

Regulations (Callsigns and Phraseology)

• TSFS 2019:126K: Swedish Transport Agency regulations and general guidelines on air traffic control services (ATS) (Swedish only)

• TSFS 2019:36 Swedish Transport Agency regulations and general guidelines on radiotelephony and phraseology (Swedish and English)

• Regulations for Military Aviation (Swedish only)

• Military callsigns and new civil callsigns

Other Resources

• Procedures for PANS/ATM (a.k.a. the ATC bible) - DOC 4444

• Aircraft Type Designators - DOC 8643

• ICAO Annexes

• ICAO Manuals

• EASA Easy Access Rules for Air Traffic Management/Air Navigation Services

• SKYbrary (Safety related content by Eurocontrol)
  

• Svenskt Flyghistoriskt Forum - Civilflygregistret (If you have a specific aircraft type and want to use a realistic/historic registration, Swedish only)
  

VATSIM

• Event Overview (Simple, showing the next days only)

• Event Calendar (All events, scrollable Date)
  

• Pilot Learning Center

• Documents and Policies (CoC, CoR, GDPR, GCAP)

• VATSIM Radar (Map showing online ATC and traffic)

• AFV-Map (Shows voice range of online ATC Positions and traffic)

• VATGlasses (Shows ATC Sectorization (Sweden included) and traffic)

• VAT-Spy (Downloadable software, shows online ATC and traffic)

• Worldwide Airport charts (Chartfox)

Flight Planning

• VATSIM Flightplan Prefile

• Simbrief (Flight planning solution for IFR Flights)

• GRD - Global Route Database

• EDI-GLA (Real World Flightplan Database)

VATSIM Scandinavia

• Forums

• Event Calendar (VATSIM Scandinavia events only)

• Discord Server (Verify Discord account through VATSIM Community Hub)
  

• Training System (Control Center)

• Moodle

• Examiners List (Within CC)

• Visiting Endorsements List (Within CC)

• Available Airport Stands List (Available for ESSA, ESSB, ESGG, ESMS, ESPA among others)

VATEUD

• List of Approved ATC Frequencies

• Policies

Observer's Guide

This guide assumes that you have installed EuroScope and the Swedish GNG package according to THIS GUIDE.

Audio Client Installation

In order to hear pilots and controllers on the network you need to download and install an audio client.

There are two commonly used audio clients approved for use on the VATSIM Network as a controller, both listed on the AFV (Audio for VATSIM) Wiki page.

Connecting and setting things up

You are now ready to connect to VATSIM as an observer.
Press "Connect" in the top-left corner of EuroScope. Fill in the following:

If you get a message saying that the callsign is in use, you can add more letters, such as MMU_OBS.

The rest of the fields are not relevant at the moment.

Press Connect and close the Voice Communication Setup window that appears.

We need to set up visibility centres to see aircraft on the radar.
In the chat window at the bottom left, write .vis1 and click on a spot on the "map" or add a waypoint/airport etc, .vis essa esms risem for example will add vis points at Arlanda, Sturup and at the waypoint RISEM, just south of Kallax.
You will see a circle appear, which is where you can see aircraft.

You can have up to 4 visibility centres at once. The others are .vis2 .vis3 .vis4 if you want to add/change them separately.
To see what visibility centres you have set, type .showvvis

To make flight plans appear in the flight plan lists, click on the runway symbol on the top bar.

This will open the window as shown below.
On the red side, you select the airports you want flight plans from/to be displayed. -> As a controller you should NOT have to change these manually!
On the green side, you select the active departure and arrival runways. This makes sure that the correct SIDs/STARs are displayed.

Audio Client Configuration

If you want to receive voice communications, we must use one of the audio clients mentioned at the top of this page. They are used to receive voice communications on the frequency.

Below is an example of how to set up TrackAudio.

1. Open the TrackAudio client and go into Settings.
2. Fill out your VATSIM ID and password.
3. Configure the correct audio devices.
   Both headset and speaker device must be configured, but same device can be selected.
   A push-to-talk key must also be configured. A good suggestion is the right control key.
4. Settings saves automatically, press Close

Your audio client is now configured and ready to connect to VATSIM.

You must first have a active VATSIM connection via EuroScope to be able to connect in TrackAudio

Press "Connect" in the client.
To add a frequency to listen to, we must add a station first.
Under Add a station write the callsign of the station you want to listen to - For example, ESSA_W_TWR, ESOS_1_CTR, or ESGG_DEL
Press Add.
Enable RX for all the frequencies you want to listen to - RX indicates green when its active - orange when someone is transmitting.

You can use vatglasses to see what controllers are online in Sweden and which sectors they cover.

EuroScope and GNG package Installation

This guide will describe how you install and set up EuroScope using the Swedish GNG package, also commonly called sector file package.

EuroScope is the most common controller client used in Europe on the VATSIM network, it is the only supported client used in Sweden. EuroScope is used to observe VATSIM traffic from the ATC's perspective and when becoming an ATC controller, to control traffic yourself.

EuroScope is only supported by Windows.
There have been members who has been able to adopt it to MacOS, however not without issues.
No support is provided to MacOS users as Euroscope is officially only supported by Windows.

There are several steps to the installation, it is important that each step of the instructions are followed to the last detail. There are no shortcuts.

If you have any issues, primarily contact your mentor, or ask for help in the #swedish-helpme Discord channel.

EuroScope Installation

EuroScope version 3.2.3.2 is the only version of EuroScope supported for use with the Swedish GNG package. 

Newer versions of EuroScope have breaking bugs/issued and changes introduced which are not covered in the documentation available on the Swedish Wiki pages. 

There will be no support offered for users who employ other EuroScope versions than 3.2.3.2

Step 1: Install the Visual C++ package from the link below, this is needed to run the Swedish GNG package.

• Microsoft Visual C++ Redistributable - https://aka.ms/vs/17/release/vc_redist.x86.exe

Step 2: Install the EuroScope installer from the link below, this is the only supported EuroScope version for use with the Swedish GNG package.

• EuroScope installer - https://euroscope.hu/install/EuroScopeSetup.3.2.3.2.msi

There is no need to change any options during the install process of EuroScope, leave the installation folder as the default filled adress.

GNG Package Installation

Once you have finished installing EuroScope it is time to download the Swedish GNG package, which contains the data needed for EuroScope to display the Airspace and Procedures specific for Sweden.

Step 1: Start Euroscope, if asked to open a profile file, click Cancel.

Continue to step 2 even if you were not asked to select a profile.

Step 2: Make sure the following options are deselected under OTHER SET as shown in the picture below.

Step 3: Open the ES Sector File Downloader by pressing Download Sector Files ... located under OPEN SCT

Step 4: Select and download the "EuroScope main sector file provider", then the "AeroNav GNG Sector File Provider", following steps 1-4 as shown below.

Step 5: Select and download the "AeroNav GNG SCA VATSIM Scandinavia" provider, following steps 1-2 below.

Then: Select the "A"  it should show a green checkmark (step 3), this is for ES to automatically look for updated versions of the GNG Package.

Do not download Vatsim-Scandinavia - Sweden - This one is no longer in use.

Step 6: Select the "AeroNav GNG SCA VATSIM Scandinavia" provider, then select and download "ESAA Full_Package" located in in the lower portion of the window, following steps 1-3 as shown below.

Then: Verify that a green checkmark appears in the "D" column, this indicates that the download has completed successfully (step 4 below).

A successful download can also be confirmed by checking the message handler at the bottom left of the ES main window as shown in the two bottom rows as shown below.

Step 7: Select and download "ESAA Update_Only", following steps 1-2 as shown below.

Then: Activate automatic downloading of "ESAA Update_Only" by selecting the "A" column, it should show a green checkmark (step 3). This will keep your GNG package up to date by automatically downloading new versions as they become available (except for plugin updates, which need some files to be manually replaced, see Q&A below).

Step 8: Close EuroScope, and press Cancel All when it prompts you to save.

Then: Open EuroScope again and select "ESAA TWR.prf" when prompted to select a profile.
If the installation of the GNG package was completed successfully the window should look something like this:

Always run EuroScope from a shortcut, there is a shortcut created in the start menu during the installation process. Check the Q&A on the bottom of this page you are having issues.

If your window does not look like the picture above, something went wrong during the installation process. Try doing a clean install of the GNG Package as shown in the Q&A on the bottom of this page:

Keeping the GNG Package updated

If you followed the guide above, ES will automatically notify you and download new files when they become available.

It is mandatory to always use the latest available GNG package. You cannot choose to postpone updating to a later time point, since it is necessary that all controllers use the latest and the same files.

EuroScope does not allow for plugins to overwrite when updating the GNG package using the automatic download. After updating, close EuroScope then go to %appdata%\EuroScope-> ESAA > Plugins > Updated Plugin" and copy the .dll files in the folder. Thereafter go back in the "Plugins" folder and paste the .dll files there. Overwrite existing files when prompted.

If you are notified that there is a new version of a plugin available: Do NOT update it by manually installing a new version of the plugin, wait for a new GNG package to become available.

New versions of the GNG package are announced in the #swedish-bulletins Discord channel.

EuroScope notifies you when new files are available.

Click Yes in all the following prompts when notified:

• "An updated version is downloaded to replace XXXX.sct sector file. Do you want to load and change it?"
• "Do you want to use C:\..XXX.sct sector file automatically in all ASR?"
• "Shall I delete the old C:\..XXX.sct sector file?"

Observer's Guide

If you want to get going, observing online traffic and controllers, check THIS GUIDE

Q&A

Checking your EuroScope version

If you are unsure which ES version you are running, this can be checked under OPEN SCT -> About EuroScope,

The ES version is also shown in the properties of EuroScope.exe (usually located in (C:\Program Files (x86)\EuroScope).

How to do a clean install of the GNG Package.

Step 1: Remove the following files/folders in located in %appdata%\EuroScope.

• The ESAA folder.
• All files starting with ESAA  

Do NOT remove any other files as some of them are required for Euroscope to work.

Step 2: Restart the installation process from Step 1 of the GNG Package Installation.

Running EuroScope (always from a Shortcut!)

There is a shortcut to ES (EuroScope) created in the start menu during the installation process.

Always run ES (EuroScope) from a shortcut, do NOT run by individually opening EuroScope.exe (normally located in (C:\Program Files (x86)\EuroScope).

If you are experiencing issues (or creating a new shortcut for ES), make sure the "Start in:" adress is pointing to the ES folder located in %appdata%, this is needed for ES to load the GNG package correctly.

EuroScope Profiles

TopSky Profile

General

ASR fast keys

(F1+)

• 1: ESAA ACC
• 2: ESAA TWR APP
• 3: ESOS APP
• 4: ESGG APP
• 5: ESSA GND TWR-W
• 6: ESGG GND
• 7: ESMS GND
• 8: ESPA GND
• 9: ESSB GND

Keyboard Shortcuts

(ALT+)

• A: Toggles Basic ATS-Routes map.
• V: Toggles VFR Points map.
• B: Toggles VFR Points + Labels map
• F: Toggles TWR/APP Frequencies map.
• T: Toggles TMA Altitudes map.
• M: Toggles MVA/AMA map.
• F1: Opens new Notepad window.
• F2: Invoke SEP tool.
• F3: Invoke QDM vector.
• F4: Toggles quick look.
• F5: Toggles all prediction lines on/off.
• F6: Opens runway approach line window.
• F7: Opens FPL selection window.
• F8: Opens SSR code menu for the find track function.
• F9: Opens create APL window.
• F10: Toggles filtering of uncoupled labels.
• F11: Opens small QNH/TL window.
• F12: Opens track control window.

The default setup is using the F-keys to access different functions. GeForce Experience/GeForce uses may experience problems with clashing key bindings. Either change the key binding for GeForce or add the following settings to your "TopSkySettingsLocal.txt" file. This will use the normal 1,2,3...8,9,0,+,´-keys instead.

Shortcut_Notepad=0x31
Shortcut_SEP=0x32
Shortcut_QDM=0x33
Shortcut_Quick_Look=0x34
Shortcut_Vector=0x35
Shortcut_Rwy_Line=0x36
Shortcut_FPL_Search=0x37
Shortcut_Find_Track=0x38
Shortcut_Create_APL=0x39
Shortcut_Uncoupled_Label_Combo=0x12
Shortcut_Uncoupled_Label=0x30
Shortcut_QNHTL=0xBB
Shortcut_Track_Control=0xDB
Shortcut_FPL=0x00

Track Labels

Data fields in "Normal Text", can be selected globally on/off via the Track Control Window, or for some of them, for individual tracks via the selected or Extended track label.
Data fields in Bold Text, is always shown.
Data fields in (Parentheses), are blank (instead of displaying the field name) when there is no data.

In case of the CFL/PEL field, only the PEL display can be selected off. For the COPN/COPX field, only the COPX display can be selected off.

The Selected Label is shown when the cursor is hovering over a label, otherwise the Unselected Label is shown.

Uncorrelated label

Track label not correlated with a flight plan.

Unselected track

(EMRG ALRT)
(FLTID)/TSSR
AFL (a) GS
(DSFL) (DHDG) (DIAS) (DMACH) (DRC)

Selected track

(EMRG ALRT)
(FLTID) TSSR
AFL (a) GS
(DSFL) (DHDG) (DIAS) (DMACH) (DRC)

Reduced label

Track label correlated with a flight plan. The Reduced label is shown for uncontrolled, unconcerned and notified tracks.

Unselected track

(V ALRT W S EMRG)
CALLSIGN (SI) (NRAC) ATYP WTC TSSR
AFL (a) FCOPX GS NPT ADES
(DSFL) (DHDG) (DIAS) (DMACH) (DRC)

Selected track

(COM * V ALRT W Y A + C TEL I S EMRG COORD CPDLC_E CPDLC_W TEXT2)
CALLSIGN SI (NRAC) ATYP WTC TSSR
AFL (a) FCOPX GS NPT ADES
CFL
(OP_TEXT) [max 2 lines of text]
(DSFL) (DHDG) (DIAS) (DMACH) (DRC)

Standard label

Track label correlated with a flight plan. The Standard label is shown for Coordinated, Assumed, Redundant and Informed tracks.

Unselected track

(COM * V ALRT W Y R P M • • A + C TEL I F S EMRG COORD NSSR CPDLC_E CPDLC_W TEXT2 TTLTTG)
(MTDC) CALLSIGN (SI) (NRAC) ATYP WTC TSSR
AFL (a) COPN/COPX GS NPT RFL ADES
CFL/PEL XFL AHDG ASP ARC
(DSFL) (DHDG) (DIAS) (DMACH) (DRC)

Selected track

(COM * V ALRT W Y R P M • • A + C TEL I F S EMRG COORD NSSR CPDLC_E CPDLC_W TEXT2 TTLTTG)
(MTDC) CALLSIGN (SI) (NRAC) ATYP WTC TSSR
AFL (a) COPN/COPX GS NPT RFL ADES
CFL/PEL XFL AHDG ASP ARC
(OP_TEXT) [max 2 lines of text]
(DSFL) (DHDG) (DIAS) (DMACH) (DRC)

Extended label

Extended track label correlated with a flight plan. The Extended label can be toggled by right click on Callsign for any track label except Uncorrelated tracks.

(COM * V ALRT W Y R P M • • A + C TEL I F S EMRG COORD NSSR CPDLC_E CPDLC_W TEXT2 TTLTTG    SQ FF STAFF)
(MTDC) CALLSIGN (SI) (NRAC) ATYP WTC     TSSR ASSR PSSR FLTID FLTADD CODE
AFL (a) COPN/COPX GS NPT RFL ADES     ADEP EOBT/ATD
CFL/PEL XFL AHDG ASP ARC           EET
SECTOR STATE LFUNC                ALT1 ALT2
(DSFL) (DHDG) (DIAS) (DMACH) (DRC)
COMP_CS
FIELD15 [max 9 lines of text]
(FIELD18) [max 6 lines of text]
(FMF)
(MALRT)
OP_TEXT
OP_TEXT2

Mouse functions in track labels

Flight Lists

List fields in bold text e.g. "C/S", are shown by default.
List fields in normal text e.g. "EVT", is not shown by default but can be selected in the list top bar by pressing "F".
List fields in parentheses e.g. "(ETN)", indicate the default sorting for that list.

Sector List

The Sector List contains all Departed controlled flights (all IFR, VFR only if assumed) in the Coordinated (from -15 min to ETO) and Assumed state.

Selected and configured from TopSky Tools menu.

Departure List

The Departure List contains all Non-departed flight (IFR and VFR) from active airports.

Selected from EuroScope Quick SET.

Load List

The Load List contains all Departed controlled flight (all IFR, VFR only if assumed) in the Notified state (from -60 to -16 min from ETO) and all Non-departed controlled flights in the Notified state (from -15 min to ETO).

Selected from TopSky Tools menu.

Uncontrolled List 1 & 2

The Uncontrolled List contains all Uncontrolled flights (VFR not in assumed state) within or close to Sweden.

Selected and configured from TopSky Tools menu.

Traffic Management List 1 & 2

The Traffic Management List (TML) contains all Departed flights in the Notified, Coordinated, Assumed and Redundant state with a specific destination and/or routing via specified points. The ETO over the point (or ETA if no point specified) must be within the next 45 minutes. The destination must be specified to include uncontrolled flights in the list.

Selected and configured from TopSky Tools menu.

Sector Inbound List

The Sector Inbound List (SIL) contains all Departed controlled flight (all IFR, VFR only if assumed) in the Notified (no time limit) and Coordinated state. Intended to be used on additional EuroScope instance to show inbound traffic, only shows 4 rows by default.

Selected from EuroScope Quick SET.

ETWR List

The ETWR List (Departure SIL) contains all Controlled flight (all IFR, VFR only if assumed) in the Notified and Coordinated state departing from a specific airport.

Selected and configured from TopSky Tools menu.

Flight Plan List

The Flight Plan List contains all Flight plans on the network. By default the list is filtered to show only flight plans in the Notified, Coordinated and Assumed state. To show all flight plans, click "N" in the top bar.

Selected from EuroScope Quick SET.

Resectorisation List

The Resectorisation List contains all flights Assumed and On-Contact with a specific FLUNC (controller ID). Can be used at controller shift change to show all flights under the control of the other controller.

TWR / TWR CDM Profile

The Setup

ASR fast keys

(F1+)

• 1: ESAA TWR APP
• 2:
  • TWR profile: ESGG GND
  • TWR CDM profile: ESSA GND TWR-W
• 3: ESSB GND
• 4: ESMS GND
• 5: ESPA GND
• 6: ESKN GND

General

The Swedish TWR profile makes use of advanced ground states and flight lists, this requires Euroscope v.3.2.1.27 or later.

Since TopSky is designed to be used in an Area/Approach setting the functionality of that setup is not suited for the tower environment. The tower setup is intended to be used only by DEL, GND or TWR positions (with or without an associated TMA). APP and CTR positions shall use the TopSky setup.

There are two versions of the tower setup, one for use at airports with A-CDM (Airport Collaborative Decision Making) and one for airports without. The tower setup uses EuroScope lists in a way similar to a FPB (Flight Progress Board A.k.a. Strips) where the progress of a flight can be managed.

Flight Progress Board

Layout

The FPB (Flight Progress Board) consists of default EuroScope lists arranged in a way that lets you monitor and manage the progress of a flight. Two TopSky lists, Sector and Uncontrolled, are also part of the setup and they will be used to handle airborne traffic. All lists in the FPB have columns and functions specific to that phase of flight.

A departing flight will appear in the Start-up list and will successively move to the Taxi Out list, Take-Off list and then to the Sector list. In the Start-up list you can manage any action necessary from receiving the flight plan to start-up and push-back. Once the aircraft calls for taxi the flight can be toggled to the Taxi Out list. When the aircraft receives the take-off clearance it will be toggled to the Take-Off list and once airborne it will show in the Sector list.

An arriving aircraft will initially appear in the Sector list and with less than 40 track miles to destination will also show in the ADC Sector list. The ADC Sector list will show the arrival sequence. Once the aircraft has landed it can be toggled to the Taxi In list.

Additionally, the setup contains the Uncontrolled list, showing all VFR flights, the Controller list and the METAR list. These lists are not forming part of the FPB.

The A-CDM version of the FPB have a few additional columns in the Start-Up list related to the A-CDM / Departure sequencing. By default, the A-CDM version have more rows in the Start-Up and Taxi Out/In lists to allow for more traffic. The two versions of the FPB are otherwise identical.

Depending on what position you are working, you are encourage to remove lists that are unnecessary for your task. This will free up screen space and let you focus on the responsibilities specific to your working position. Below is a table suggesting which lists to have open for which position.

*Not needed if GND is open

It is recommended to have the TWR setup in the same Euroscope instance as the primary situation display (radar display). This way the integration between the FPB, TopSky lists and situation display will be maintained and functions like the Flight Leg will work.

Flight Progress

General Use

A complete description of all functions and click actions in the list are described in section Flight Lists.

All lists in the FPB, TopSky lists excluded, have a common left side from where you can manage the progress of the flight:

Ground Status (STS)

• Left Click: Set ground status
• Right Click: Assume/Transfer

Call Sign (C/S)

• Left Click: Open handoff menu
• Right Click: Call Sign Highlight

Sector Indicator (SI)

• Left Click: Open next controller menu
• Right Click: Assume/Transfer

Setting the ground status moves the flight across the FPB. The SI can be pre-set to the correct sector sequence. Right clicking on the STS or SI assumes or transfers the flight. In the handoff menu you can assume an uncontrolled flight, make a manual transfer or release a flight.

Start-Up List

Shows traffic from receiving the flight plan until ground state S/U (Start-Up) or S/P (Start-Up & Push-Back).

Start-Up list is sorted by ground state.

Column RTE/AHD (Route/Assigned Heading) will only work correctly if logged on as DEL, GND or TWR. By default, RTE/AHD will show SID if available otherwise the first waypoint in the route or the assigned heading if set. Left click opens the SID menu where you can assign a different SID and right click opens the AHDG menu. To set a DCT left click on COPX to open the waypoint menu.

Column PR (Pending Request) is used to set reminders of pilot request that cannot handled directly. Left click and select the request in the menu. The letter indicates the type of request and the number in what order it was made. C = Clearance, S = Start Up, P = Push Back and T = Taxi. Once the request has been handled the PR-indicator will reset with either the CLR OK or updating the STS.

Work flow:

1. Check flight plan by left click on ADES to open FPL window, FLEG can be toggled by right click on COPX.
2. If necessary, update RTE/AHD, left click to change SID and right click to set a heading.
3. Left click CLR, this opens the DEP Clearance menu. CFL and ASSR will be set automatically. Click Cancel.
4. Enter any special conditions (SLOW etc.) in the RMK column.
5. When aircraft calls, left click C/S and then assume and also left click STS and then FRQ (On Frequency).
6. Open DEP Clearance menu and give the departure clearance, click OK after the readback. PDC is available as well.
7. If necessary, update SI with correct sector sequence by left click on SI and selecting the next sector.
8. To transfer the flight to the next controller, right click on either STS or SI.
9. When approving start-up or push-back, set correct ground state.
10. With the taxi clearance, set ground state TXO. This will move the flight to the Taxi Out list.

Taxi Out List

Shows traffic with ground state TXO (Taxi Out) or xLU (Line Up).

Taxi Out list is sorted by DSQ (Departure Sequence). To assign a departure sequence, left click on the blank space in the DSQ column, this will assign the next available sequence number. To edit or remove a sequence number left click on a number in the DSQ column, this will open the DSQ menu. To advance an aircraft in the sequence, right click on the number.

Work flow:

1. When the flight appears in the list, update the SI with correct sector sequence if necessary and assign a departure sequence number.
2. Hold Short instructions can be entered in the HS column.
3. To transfer the flight to the next controller, right click on either STS or SI.
4. When aircraft is instructed to Line Up, set ground state xLU.
5. When the aircraft is cleared for Take-Off, set ground state xTO. This will move the flight to the Take-Off list.

Take-Off List

Shows traffic with ground state xTO until the aircraft is airborne. Once the aircraft is airborne the flight will be moved to the Sector list.

ADC Sector List (Arrival Sequence)

Shows arriving traffic within 40 track miles with ground state ARR (Arrival).

This list is sorted by ETA.

Work flow

1. Assume traffic by right click on either STS or SI.
2. If necessary, update SI with correct sector sequence by left click on SI and selecting the next sector.
3. Once cleared to land toggle the CTL (Cleared to Land) indication with a left click. The CTL flag will show up at 12 NM from the airport in red to indicate that landing clearance has not been given. Once toggled the CTL flag will turn green and after landing the flag will disappear.
4. To transfer the flight to the next controller, right click on either STS or SI.
5. With the taxi clearance, set ground state TAXI IN. This will move the flight to the Taxi In list.

Taxi In List

Shows arriving traffic with ground state TAXI IN.

This list is sorted by call sign.

Work flow:

1. Hold Short instructions can be entered in the HS column.
2. If necessary, update SI with correct sector sequence.
3. Once the aircraft is on stand, left click call sign and select release.
4. After traffic is released, left click STS and select PARKED, this removes the traffic from the list.

Sector List

This is a TopSky list with the same functionality as in the TopSky setup and is needed since we are using TopSky as the primary situation display. The Sector list is not part of the FPB but rather a complement to the situation display. For airborne traffic the majority of inputs are done in the label and not through the list.

The list shows airborne traffic that is assumed by you or that will enter your sector in the coordinated state. If needed, traffic in the notified state can be displayed through selection in the TopSky menu TOOLS. Sector list is sorted by ETN for inbound traffic and by call sign when assumed.

The main difference is the call sign menu accessed by left clicking on the call sign. From this menu some additional functionality can be found e.g. setting the Missed Approach manual alert. Additionally, this list is using the TopSky flight plan window.

Uncontrolled List

This is a TopSky list with the same functionality as in the TopSky setup. Uncontrolled list is not part of the FPB.

This list shows only uncontrolled VFR, either in Free or On Contact state. Controlled VFR in the Assumed state is shown in the Sector list. The Uncontrolled list is not exclusive to a specific position and will show all uncontrolled VFR in Sweden.

Known issues

There are some limitations and known issues with the setup. Flights on the FPB cannot easily be moved from the normal departure and arrival flow and this can create some difficulties.

Traffic with the same departure and arrival airport will disappear from the Taxi In list when Euroscope terminating the flight plan.

An arrival with a flight plan to the airport wants to depart again without filing a new flight plan:

1. Set ground status TAXI IN so the flight appear in the Taxi In list.
2. Then change status to TAXI OUT. The flight will now disappear from Taxi In list and will not show in the Taxi Out list since the flight plan contains the wrong departure airport.
3. In the ground radar display, open the call sign menu and select FPL (Flight Plan). Alternatively open the Euroscope Flight Plan list from the “Quick SET” dropdown menu from where the flight plan dialog can be opened.
4. Edit the flight plan and set “Origin” to the current airport. Now the flight should appear in the Taxi Out list.

As a general rule, if a flight is not showing properly in the Start-Up or Taxi Out list. Open the Flight Plan list and set Flight Plan status to “Terminate”. This will usually reset any issues and the flight will appear in the correct list after a few seconds.

When signed in as Delivery there is usually an issue with the Start-Up list. Delivery can technically not have an separate sector in Euroscope when other positions are online and this will make all flights in the list appear in unconcerned state (greyed out). In this state the RTE/AHD column will not show the correct value until you assume the flight.

This can be fixed with the use of sector ownership:

1. Open “Other SET” menu and select “Sector ownership setup”.
2. Click on “Select All” and wait until the list gets a grey background.
3. In the dropdown list at the bottom, select “DEL” and click “OK”. Euroscope can freeze for a few seconds.

Now, the Start-Up list will show correct colours and values. The drawback is that the sector sequence will skip any ground position and those has to be selected manually.

Ground Track Labels

This chapter describes the track labels as shown on ASRs using the Ground Radar plugin. For a description of TopSky track labels (such as shown on ESAA_TWR_APP.asr), see TopSky.

The track symbols and labels are colored according to the flight’s status (arrival, departure or overflight/unknown).

• Arrivals are yellow
• Departures are light blue
• Overflight/unknown are light grey.

Data fields in normal text e.g. "SID", can be selected globally on/off via SETTINGS->Labels.
Data fields in bold text e.g. "CALLSIGN", is always shown
Data fields in parentheses e.g. "(ALRT)", are blank when there is no data.

Right-clicking on the any track symbol toggles the heading lines.

ESGG Departures

Track label for outbound flights.

Unselected track

(ALRT ASSR_E COMM)
CALLSIGN (RMK)
ATYP/WTC DEP

Selected track

(ALRT ASSR_E COMM)
CALLSIGN RMK
ATYP/WTC DEP

ESGG Arrivals

Track label for inbound flights.

Unselected track

(ALRT COMM)
CALLSIGN (STAND)
ATYP/WTC RMK

Selected track

(ALRT COMM)
CALLSIGN STAND
ATYP/WTC RMK

ESGG Overflight

Track label for flights that are neither outbound nor inbound.

Unselected track

(ALRT COMM)
CALLSIGN
ATYP/WTC RMK

Selected track

(ALRT COMM)
CALLSIGN
ATYP/WTC RMK

ESSA Departures

Track label for outbound flights.

Unselected track

(ALRT ASSR_E COMM)
CALLSIGN
ATYP WTC DEP
REG (RMK)

Selected track

(ALRT ASSR_E COMM)
CALLSIGN
ATYP WTC DEP
REG RMK

ESSA Arrivals

Track label for inbound flights.

Unselected track

(ALRT COMM)
CALLSIGN STAND
ATYP WTC DEP
REG (RMK)

Selected track

(ALRT COMM)
CALLSIGN STAND
ATYP WTC DEP
REG RMK

ESSA Overflight

Track label for flights that are neither outbound nor inbound.

Unselected track

(ALRT COMM)
CALLSIGN
ATYP WTC
REG (RMK)

Selected track

(ALRT COMM)
CALLSIGN
ATYP WTC
REG RMK

Mouse functions in track labels

Other

For a description of track labels shown at other airports than ESGG and ESSA, refer to Ground Radar plugin for EuroScope - General.pdf (4. Track presentation) included in the GNG package.

Flight Lists

List fields in bold text e.g. "C/S", are shown by default.
List fields in normal text e.g. "EVT", is not shown by default but can be selected in the list top bar by pressing "F".
List fields in parentheses e.g. "(ETN)", indicate the default sorting for that list.

Start-Up List

Shows traffic from receiving the flight plan until ground state S/U (Start-Up) or S/P (Start-Up & Push-Back).

The fields listed below are shown when using the CDM profile, for more information see CDM Procedures ESSA.

Taxi Out List

Shows traffic with ground state TXO (Taxi Out) or xLU (Line Up).

Take-Off List

Shows traffic with ground state T/O until the aircraft is airborne. Once the aircraft is airborne the flight will be moved to the Sector list.

ADC Sector List (Arrival Sequence)

Shows arriving traffic within 40 track miles with ground state ARR (Arrival).

Taxi In List

Shows arriving traffic with ground state TAXI IN.

Sector List and Uncontrolled List 1 & 2

For a description of the Sector List and Uncontrolled List 1 & 2, see TopSky.

Software and Tools

vATIS

Since ES v3.2.2 it is possible to have up to 4 simultaneous ATIS-connections, however in Sweden we use vATIS. vATIS offers the same number of ATIS connections, but also easier addition of RWYCC (Runway condition codes) and NOTAMs as free text.

To use vATIS you need to download the software itself, and import a profile, both of which are linked below.

vATIS

vATIS Sweden Profile

The profile is updated automatically when a new version is found.

Documentation and more information available on the vATIS website.

https://wx.awos.se/ and VatIRIS shows real life AWOS/ATIS for many airports in Sweden.

ATIS formatting

We use vATIS to simulate as closely as possible both voice ATIS and D-ATIS (datalink ATIS in text format). Therefore it is important to use the correct text format to ensure that both the ATIS text looks reasonable, using plain language or common abbrevations (contractions in vATIS terminology), and that audio output is sensible.

Always check that the ATIS output is reasonable, especially when using free text in the ARPT COND or NOTAMS fields. vATIS may not recognise certain abbreviations. If this is the case use plain language instead. ATIS output can be checked by selecting "Get ATIS" for the relevant ATIS in the ES controller list. Audio output can be checked by using the sandbox feature in vATIS or by adding the relevant ATIS and listening to its frequency in AFV.

LVP:

When LVP is in force it can be added to the ARPT COND window with LVP as free text, or activated by clicking on the APT COND text above the text field, and selecting LVP in the list.

Adding free text:

• SCCs (surface condition codes) can be added as free text to the ARPT COND window. In the real life AWOS, the text is manually entered as free text, which means there are some variations to the formatting and abbrevations used. For the text to work correctly in vATIS, you may need to edit certain phrases or formatting. Examples:
  • Generic format, as used by most ATIS where a single runway is in use: SURFACE CONDITION CODE 3 3 3. DOWNGRADED. ISSUED AT 1944 RWY 100 PCT 3 MM WET SNOW. TWY AND APRON POOR
  • The format used by ESSA AWOS (see below): RWY 01L SCC 5 5 5. ISSUED AT 1800. RWY 100 PCT WET. CHEMICALLY TREATED. Note that the contraction SCC is recognised by vATIS only at ESSA. For other ATIS, use plain text.
  • SNOWTAM format: ESNN 02291436 16 5/5/5 100/100/100 NR/NR/NR WET/WET/WET.
    • The "raw" SNOWTAM text in the example above would have to be formatted as free text to be properly interpreted by vATIS, like this: SURFACE CONDITION CODE 5 5 5 RWY 100 PCT WET
• NOTAMs can be added as free text to the NOTAMS window:
  • e.g. TWY Y3 CLSD or GLIDE PATH RWY 17 OUT OF SERVICE
• vATIS interprets certain phrases and abbrevations differently depending on context.
  • Y3 will be read out as "why three" whereas TWY Y3 will be read out as "taxiway Yankee three".
  • Runway designators will only be interpreted correctly if preceded by RWY, i.e. write RWY 01L instead of just 01L.
  • When a contamination depth is included, make sure there is a space before MM (i.e. make sure it says "1 MM", not "1MM").

For the most common reported contamination depth of 3 mm, the phrase 3MM (without space before MM) has been added for convenience. For other depths, make sure to add a space before MM as described above.

• Use punctuation as needed where a pause is desired in the spoken output.

When adding or pasting free text to the ARPT COND or NOTAMS fields, take care to remove colon symbols ( : ) or double spaces ( ) where included, as the remaining text after will be ignored if the symbol/double space is not removed.

Note: Text added in the ARPT COND and NOTAMS fields is saved by clicking the save icon that appears in the text field when adding text. The text will remain in place for that preset until it is edited or deleted (including after closing and re-opening vATIS). Pre-defined airport conditions (such as LVP) will also remain in place until deselected. When setting up an ATIS, make sure that no old/irrelevant ATIS text is present.

ESSA ATIS set up and formatting:

• AWOS for ESSA which shows real life runways in use as well as runway surface conditions is available at https://wx.awos.se/?siteId=ESSA.
• In vATIS, there are one or more presets for each runway combination. Some runway combinations have separate presets for IMC and VMC conditions (the phrase "additional spacing on final due to runways in use" is added to the IMC preset). Take care to select the relevant preset!
• Runway surface conditions can be added by pasting the info from AWOS. For the text to be displayed and read out correctly by vATIS, it needs to be in the correct format:
  • The "raw" text from AWOS might look like: 01R: SCC 5 5 5. ISSUED AT 18:57. RWY 100PCT DRY SNOW 2MM. TWY P APN P.
  • This needs to be edited to the correct format for vATIS. Include RWY before the runway designator, remove any colons and make sure there are spaces and punctuation where needed. Some abbreviatons may need to be changed into plain language. The above example when edited to suit vATIS should look like this: RWY 01R SCC 5 5 5. ISSUED AT 1857. RWY 100 PCT DRY SNOW 2 MM. TAXIWAYS POOR. APRONS POOR.
  • For DEP ATIS, include surface conditions for the departure runway only, as well as taxiway and apron conditions.
  • For ARR ATIS, include surface conditions for the arrival runway only, as well as taxiway and apron conditions.
  • AWOS lists the runway conditions based on the lowest runway designator, e.g. the conditions for RWY 01L/19R, 01R/19L and 08/26 will always be listed for RWY 01L, 01R and 08. In the ATIS, this needs to be adjusted to reflect the runway direction in use so you may need to manually change it to RWY 19R, 19L and 26.

In real life, the ATIS designator letter for DEP ATIS and ARR ATIS are usually different. This might be inconvenient on VATSIM as there is no practical way to display both ATIS letters in ES. Therefore it may be preferable to use the same letter for both DEP and ARR ATIS.

AMAN (MAESTRO)

1. Background information

The issue and its solution:

Aircraft enter the TMA at several FFs (feeder fixes, the waypoint where the STAR begins). For landing, all aircraft must be sequenced. Here, the problem is building the optimal sequence of aircraft as there are several constraints involved (e.g. wake turbulence, runway specific rates depending on high speed exits, departure gaps). AMAN can calculate this sequence and display it to the controllers, which in turn can act on it when deciding who is allowed inbound without (further) delays, or if holding, who may leave the hold and when.

An arrival manager (or AMAN) works as follows:

• An aircraft approaches a horizon of 150-200 nautical miles, AMAN captures it, calculates its ETA and inserts it in the sequence along with the others already there.
• In the ATCC, the TMA supervisor receives and validates the sequence provided by the AMAN and makes the necessary changes as needed.
• The advisories (Time to lose/Time to gain) that AMAN provides for each aircraft are transmitted to the en-route controllers, which they communicate with the aircraft and apply the appropriate delays or time savings.

2. Introduction

Note: The MAESTRO plugin is WIP and may contain bugs, if you think you have found one, let the developer know via the VATSCA Forums.

2.1 Implementation (and limitations) on VATSIM:

The MAESTRO plugin emulates the AMAN tool with the same name, developed by Egis-Avia (now Thales), in use at EFHK, EKCH, ESSA among others. Its functionality is limited compared to the real systems, however it can be useful in helping virtual controllers monitor and manage inbound flows and delays to one or more airports.

The calculations are based on the predictions provided by EuroScope and its programmed data, so to get useable results, it is important to keep the aircrafts’ data updated. The most common problems are:

• Wrong landing runway:
  • the aircraft won’t be included in the correct runway’s sequence at all.
• Old direct-to clearance stuck:
  • the aircraft’s position in the sequence will be based on the predicted ETA which will be off by hours in the worst case as it assumes the aircraft turns back to that point.
• Calculated sequence not being followed:
  • the whole sequence behind the affected aircraft is delayed until the sequence is manually corrected or the situation resolves itself as aircraft arrive and are removed from the sequence.

Note:The plugin can only be used for one airport group at a time. (If you select ESSA, also traffic to ESSB will be shown)

2.2 Interpreting and acting on generated data:

Example:

• SAS904 is inbound ESSA via ELTOK (ETA at ELTOK 17:35).
• AMAN with help of EuroScope estimates, via the programmed STAR, it will take him 11 minutes flying from ELTOK to touchdown (on the selected runway).
  Without delays, SAS904 would land at 17:46
• Because of a peak in arrivals to Arlanda, the first available landing slot is at 18:00
• AMAN calculates the difference between SAS904s present ETA at ELTOK (17:35) and his STA (scheduled time or arrival) [18:00 - 11 minutes = 17:49].
• The difference between his ETA and STA over ELTOK is calculated [17:49 - 17:35 = 14 minutes].
• SAS904 has 14 minutes to lose (to fit into the sequencing calculated by AMAN), this is called his current delay, or TTL (time to lose).

• Depending on the TTL, delaying vectors, speed restrictions, or holdings may be given, to comply with the STA overhead the FF.
• 14 Minutes is aproximately 3 or 4 patterns in a holding, depending on the outbound time.
  
  
• The time to lose (or to gain, when shortcuts are beneficial for the sequencing) is presented to the controller, and continously updated, freeing him from all manual calculations.
  (This allows the controller to inform the pilot in holdings when to expect further clearance, which is the same as his STA (17:49))

Note: For actual operational procedures with AMAN in use: see 3.6

2.3 Timeline and Glossary

• STA: Scheduled time of arrival - flow planned arrival time by AMAN.
• ETA: Estimated time of arrival - estimated using the FLEG route within Euroscope.
• FF: Feeder fix - the waypoint where the STAR begins.
• Current delay: How much delay is needed to reach RWY at STA - Current ETA RWY-STA RWY.
• Total delay: Initial ETA RWY-STA RWY - (i.e. for holding traffic, the total delay will increase)

3. Plugin usage and procedures

Some information is excluded or simplified for ease of understanding and use, for more detailed information on the inner workings of the plugin, see the included manual in the .zip package.

3.1 Plugin installation

MAESTRO

The Swedish GNG package contains the latest beta version of the MAESTRO plugin by Juha Holopainen.

TopSky

The Swedish GNG package contains a version of TopSky that automatically receives MAESTRO data for ESSA/ESSB and EKCH when updated data is available.

3.2 Operation modes

3.2.1 Standalone mode

The plugin calculates its own data (can be useful for testing the plugin for the first time, not sharing any sequence data)
This mode can also be selected to disconnect from other previously selected modes.

3.2.2 MASTER mode

The plugin calculates its own data, and shares it as follows:

• Web - Data is uploaded to a server
• Local - Data is saved to the local computer to be used by other EuroScope instances
• Web+Local - Both of the above

3.2.3 SLAVE mode

The plugin receives its data from an outside location depending on the settings:

Note: TopSky automatically receives MAESTRO data from the server to show in aircraft labels and traffic management lists without the need to connect in MAESTRO.

You only need to connect via MAESTRO if you want to view the data on the MAESTRO timeline.

• Web - Data is downloaded from a server
• Local - Data is read locally
• Web+Local - Data is downloaded from the server, and then saved to the local computer to be used by other EuroScope instances

Note: All three AMAN operation modes work regardless if you are connected as an active controller or OBS.

The relevant operation modes for live operation on VATSIM are:
• MASTER (Web+Local)
• SLAVE (Web+Local)
The persistent use of (Web+Local) should allow the planned sequence to be kept if MASTER is changed (see 3.8).

When using several instances of EuroScope, the secondary instances are to be connected as:
SLAVE (Local)

3.3 General Operation

The COTS and AMAN windows can be moved by dragging them from the title bar. Other windows are non-moveable.

• Left-clicking on the button above AMAN in the COTS Window opens the AMAN Window.
• Windows are closed by left-clicking the box in the top right corner.
• Windows are resized by dragging the box in the bottom right corner.

3.3.1 The AMAN Window:

1. The current airport (left-click to open the Setup Window)
2. The runway rates (left-click to open the Change Rates Window)
3. The measured actual rates during the past 30 minutes and deviation from set values
4. The sequence in numbers: aircraft past the FF (TMA), and the total number of aircraft (TOT)
5. The current operation mode, empty for standalone mode. (MASTER/SLAVE, the SI of the controller, local/web/web+local)
6. The UTC time when the data was last refreshed
7. Opens a menu to scroll between the FFs when in ACC and FLOW view mode, including an option to toggle visibility of the panels marked in red (1-6)
8. Changing between the three view modes: (See 3.3.2)
9. The “Desequenced” button displays the number of De-sequenced flights, (left-click to open the De-sequenced List).
10. Current UTC time (left-click to open the Labels Window, changing what is displayed in the flight label)
11. Scrollbar (Can be moved by dragging the bar itself, or by clicking on the background area next to the bar. Left-clicking changes the setting by one unit, right-clicking by 10 units, double-click to resume to default view)
12. The flight label, from left to right (left-clict to open callsign menu)
           • Current delay (Color depending on how long the delay is)
           • Aircraft callsign (Color depending on flight state)
           • STA RWY or FF depending on view mode
             (When in holding: the time in which the FF shall be passed, inbound TMA.)
13. The timeline, upwards on the scale indicates the future. defaulting to show current time at bottom. As time progresses, the scale automatically moves from top to bottom (To scroll, see 10.).

3.3.2 The view modes:

Recommended view mode:
• ACC: ACC mode
• APP: Runway mode

Note: The ACC view is new since v1.1b3, it shows FF STA on the timeline instead of RWY STA.

3.3.3 The Flight Information Window:

The Flight Information Window can be opened from the callsign menu (see 3.3.1 -> 12), it displays flight related data. as follows:

3.3.4 The De-sequenced List:

The “De-sequenced” can be opened from the main AMAN window (see 3.3.1 -> 9), it contains flights temporarily removed from the sequence. They are presented in the same order as they were entered into the list. Left-clicking one or more callsigns highlights them. The “Resume” and “Remove” buttons can then be used to either re-enter the highlighted aircraft back into the sequence or remove them from it permanently.

3.3.5 The TopSky track label:

Note: TopSky automatically receives MAESTRO data from the server to show in aircraft labels.

When AMAN is active for an airport, for arrivals having a predicted sequencing, the current delay is displayed in line 0 of the track label in minutes, with one of the following prefixes:

• L (Lose) for time to lose (Delay)
• G (Gain) for time to gain (FF ETA is later than the FF STA)

3.3.6 The Traffic Management Lists

Note: TopSky automatically receives MAESTRO data from the server to show in the TMLs.

See TopSky Profile - Traffic Management List 1 & 2 to see the data fields showing AMAN/MAESTRO data.

3.4 Flight states (and their colors)

Flight labels are color-coded according to their states which are based on the time from the airport and the feeder fix, except for the delay items whose coloring depends on the amount of delay,

• UNSTABLE (More than 12 minutes from the FF - The sequence is recalculated on every position update)
• STABLE (Within 12 minutes from the FF - No plugin-initiated changes to the sequence)
• SUPERSTABLE (Within 8 minutes from the FF - No plugin-initiated changes to the sequence, except for missed approaches re-inserted into the sequence)
• FROZEN (Within 5 minutes from landing - No plugin-initiated changes to the sequence, except for the detected actual order on final)
• LANDED (Flights considered as landed)

Note: An aircraft disconnecting will always initiate a resequencing by the plugin.

Note: A flight still in UNSTABLE state can not be manually manipulated until it is turns STABLE.

3.5 Interacting with flight labels and the timeline

Terminology:

• Slot - During a slot no arriving aircraft will be calculated to land.
  • A slot can either bound to a specific flight (by clicking on a flight label), or specified as a time period (by clicking on the time line when in runway view mode, see 3.3.8)
  • Slots can be useful for manually planning departure gaps, short runway closures, or runway changes.

If managing a runway change using AMAN, it is recommended to set the planned arrival runway manually for each aircraft (to prevent problems when changing the runway set as active for arrivals in EuroScope)

3.5.1 Callsign menu

Left-clicking on a flight label opens the callsign menu with the following options:

• Recompute Recomputes the flight’s data
• Change Runway - Opens the EuroScope menu to set the arrival runway
• Insert Slot - Opens the slot submenu (a value of 0 minutes removes the slot)
• Remove - Removes the flight from the sequence
• (The rest of the options are not implemented)

Note: Recomputing or moving a flight may become necessary when it is no longer in the unstable state (so its position in the sequence is fixed) and can no longer meet its calculated time profile, starting to delay all the flights behind it in the sequence.

Note: Disconnected flights will stay in the sequence for 10 minutes unless manually removed
(If a flight that is still online is removed from the sequence, it will be automatically added again).

3.5.2 Timeline menu

Left-clicking a timeline opens a menu with the following options:

• Insert/Modify Slot Opens the Slot Modification Window (only available in the Runways view)
• Insert Flight Allows to type in a callsign already in the sequence to move into that position

3.5.3 Manually adjusting the sequence

Changing the generated sequence can be done in the AMAN window in following different ways:

• By dragging a flight label to the wanted position in the sequence
• Left-click on a time in the timeline, select "add flight" (can be done to already existing flights)
• Left-double click a flight label (the label becomes boxed), then select another another flight label, the two will swap its positions in the sequence

When manually adjusting the sequence, a confirmation window will always be opened, asking to confirm or cancel the operation.

A flight still in unstable state cannot be moved.

Note:
Moving/adding a flight in only changes position in the sequence. The exact time in the timeline where the flight is placed is calculated by the EuroScope FLEG

3.6 Roles, responsibilities and procedures

In real life. Stockholm (ESOS) receives (and transmits) AMAN data for ESSA. Malmö (ESMM) ATCC additionally receives AMAN data for EKCH also. The MAESTRO tool is managed by APP-C for the arrivals into Arlanda.

The following positions may be responsible managing the arrival sequencing to Arlanda using AMAN as MASTER, beginning with the highest and progressing to the lowest priority:

1. ESSA_C_APP (No active frequency)
2. ESOS_PLN_CTR (Separately approved frequency. 123.975)
3. ESSA_E_APP (When no separate planner is online. 126.650)
4. ESOS_1_CTR (When ARR-E is not separately manned)

Note: Any controller not responsible for managing AMAN may receive data as SLAVE.

ESMM may receive data about the planned sequencing into Arlanda, they do however not act on it, unless requested to by adjacent ESOS sectors (probably as it is too early with a relatively unstable sequence, unless severe delays are indicated/expected).

Mainly the ESOS-sectors adjacent to Stockholm TMA monitor and judge/act on the AMAN data.

The position acting as MASTER shall keep manual changes to the sequence to a minimum

Suggested procedures when AMAN is in use (ONLY after prior coordination):

When only parts of the sequence is indicating a delay, ESOS ACC does not have to act on that information.
If all inbounds show several minutes to lose, consider holding or delaying inbound traffic as appropriate (Use common sense, TTL and TMA/TOT numbers may help in judging this)

At times of higher workloads in the TMA, it is preferable that ACC hands over traffic excactly according to FF STA (no more "current delay" remaining).

3.7 Getting started

So now you've read through the entire wiki page and the pdf documentation? Great! What's next?

Open the Setup window (see 3.3.1), enter the airport identifier in the ICAO window, select the desired operation mode.
After selecting operation mode, it should look like below:

To receive the web password for acting as MASTER, send an Email to max.kuhla@vatsim-scandinavia.org
or contact me via Discord (199890517914288128 or maxlk96)

MASTER:

SLAVE:

Click "Ok", and get to work, sequencing, or observing the sequencing!

Note: You do not need to have the AMAN window open to keep receiving updates to the sequence.
(when working ACC, all the information you need is in the TopSky track label, if all is working as it should for the MASTER)

3.8 Tips and Tricks

Runway rates:
The runway rate preset in the system is defined by enviromental factors (high speed exits, runway used for departure simultaneously).
The actual available rate might be limited by human factors, such as:
• Controller capacity and experience (how consistent spacing can be produced)
• Pilot reliability (how quickly do they react, and how compliant are they in following instructions )

If the outputted numbers make no sense:
Try checking the aircraft in front of (below) the delays. Is there a time gap in front of him?
Also check all relevant FLEGs to see if they are correct, as they are used for the sequencing calculations.

If the final keeps getting longer: Maybe the arrival rate has to be lowered (See 3.3.2).
Alternatively, you can manually put in a slot behind one of the arrivals, in an attempt to give DIR a chance to catch up, and shorten the final.

When planning a runway change: Use time based slots to facilitate a smooth runway change, preventing that arrivals are planned to land on both runways at the same time (unless that is allowable).

When relieving the MASTER:
1. The relieving controller connects as SLAVE, (to fetch the planned sequence).
2. The relieved MASTER disconnects by selecting Standalone or SLAVE.
3. The relieving controller connects as MASTER.

TS VCCS (Ground to Ground Coordination)

1. Introduction

Euroscope has an integrated voice coordination tool, called VCCS (voice communication control system), it can be used for ground to ground communication between controllers as an alternative/supplement to Discord.

To enhance the coordination between controllers, VCCS can be used to solve the problem of controllers muting the Discord channel, with VCCS they are still reachable despite being muted on Discord.

Discord is to be used as the main tool for voice communication, VCCS can be used in parallell to enhance the experience. It does hover require both parts to have it correctly configured.

2. Setup Instructions

1. Open the TS VCCS mini control box using the Quick SET-menu. The VCCS mini box can be moved around, drag with the left mouse button.

2. Right-click the VCCS mini box to open up the VCCS main window, then click EDIT to bring up the settings window.

3. Verify the marked fields are filled in as follows:

   • Server name: any valid TS VCCS server, either ts.intor.fi or ukvccs.vamsys.io.
   • Server port: 9988
   • Nickname: Suggest you use your CID, THIS NAME MUST BE UNIQUE
   • G2G (ground to ground) PTT: SELECT A UNIQE PTT, NOT the same as your AFV or Discord PTT.
   • Devices: Select the desired input and output devices

4. Click okay to save the settings

Note: Do not forget to save the settings when closing Euroscope after the initial setup has been made.

For further information, see the Euroscope doccumentation

3. Usage Instructions

• To test the functionality press TEST in the VCCS window, then use PTT, you should hear yourself.

• To call someone:

  • left-click on a green position in the VCCS window, or
  • right-click on a position in the controller list, Call on VCCS

  then use PTT like in Teamspead/Discord when you want to talk.

• To answer an incoming call:

  • left click where it flashes (and shows which position is calling)
    • in the VCCS mini-control, or
    • in the large window

• To hang up, click where you clicked to answer, or END in the large VCCS window.

Position frame colours

• Green: Position online, using VCCS (not necessarily correctly configured).
• Yellow: Position online, old Euroscope version without VCCS.
• Blue: Position not recognised due to incorrect SI, call via right click->Call on VCCS in thecontroller list.
• Red: You guessed it. Position offline.

If coordinating via VCCS is not successful/suitable, revert to using Discord or Euroscope PM.

4. Known Issues

• Calling the same position several times using VCCS may crash your Euroscope, if this is the case, use Discord.

AFV (Audio for VATSIM)

Since 2018 VATSIM is using a new voice codec, reducing latency and increasing voice quality.

Euroscope has not yet been updated to natively integrate and support the audio client, therefore requiring one of the following standalone audio clients to be able to communicate via radio:

• Audio for VATSIM standalone client
• TrackAudio client (scroll down to assets and download the latest .exe file)

Crosscoupling

When manning positions covering large areas with the use of several tranviecers (i.e. ESOS_1_CTR) controllers are urged to cross-couple (XC) their frequency, even if using a single frequency, this helps pilots hear each other even when outside of their local radar range.

Relieving positions

When relieving positions, make sure to manually add and select the correct position callsign in the audio client, as this is the only way to ensure the correct trancievers are being loaded. (See picture below)

VatIRIS

Overview

VatIRIS is an interpretation of its real-world counterpart:
IRIS - Integrated Real-time Information System,
adapted and extended for use by VATSIM controllers in Sweden.

IRIS is designed to provide real-time information to various aviation facilities. It integrates and displays critical information such as air traffic data, weather conditions, and navigational aids into one flexible, role-based presentation.

Purpose of VatIRIS

VatIRIS can be used to:

• Provide situational awareness for air traffic controllers by combining previously separate data into one interface.
• Improve safety and operational efficiency for airports by allowing seamless communication between controllers and other operational systems.

User Interface

The different modules in VatIRIS are contained in a GUI similar to Windows or MacOS with resizable windows for each module.

Window snapping is enabled by default but can be disabled under SYSTEM -> SETTINGS if desired.

Modules

Below are some examples of the different types of information that the different modules can show:

1. Dynamic Information

   • Real time weather data (METAR, TAF, Weather sensor values, Weather map).
   • ECFMP Flow measures.
   • Airspace Occupancy data.
   • PLS data.

2. Static Information

   • AIP (Aeronautical Information Publications).
   • Pushback procedure maps.
   • Manuals and regulations (LOP, GOP etc. from Wiki)
   • Tactical directs (DCT)

Data timestamps

Most modules show a timestamp in the top right corner of each window.

The timestamp is not shown at all if not relevant (e.g. for data from Wiki and AIP).

Sometimes the timestamp only shows (in red) when the data is outdated (METREPORT and METSENSOR).

Logging in using VATSIM Connect is required to access most features, saved presets etc are also stored connected to your account, this manual assumes you are logged in to IRIS.

Saving/"Installing" VatIRIS an app

Using IRIS as a standalone "app" (PWA - progressive web application) instead of within a browser is recommended. Below you can find guides on how to for the most common web browsers.

• Chrome
• Edge
• Firefox

The Menu Row

All modules/windows can be opened using the menu row,

A short description of the first level of buttons are shown below, modules that can be opened using a button are described in their entirety under Module Descriptions.

System Menu

To the left in the menu bar you'll find the following buttons, affecting the general behaviour of IRIS system-wide.

• Reload arrows Reload Button - Reloads the data in all open windows.
• SYSTEM
  • SETTINGS - Open personal options view.
  • PRESET - Create/manage window presets, default presets are also available here.
  • RESET - Reset settings.
  • ABOUT - Opens the about view, this is also where the privacy policy can be found.
  • LOGIN/LOGOUT - VATSIM Connect: log in/out.
• Search icon To use the global search function, see below.

Main Toolbar

The buttons to the right of SYSTEM are connected to their specific modules, each button opens their own window or a submenu, see Module Descriptions for a full description of each module.

Global Search

The global search function can be used to quickly find the module you are looking for.

The global search can be accessed by pressing the search icon in the menu row, alternatively with the button combination Shift+Space or Shift+Enter

Module Descriptions

MET - Meteorological information

AIRPORT

Showing a combined view of SUN, METREPORT, TAF and METSENSOR.

METREPORT

Showing decoded weather data parsed from one of the selected data sources depending on view mode.

View modes:

Only available sources for the respective airport is shown. The data source is automatically switched to the preferred source when one becomes available (A>W>M).

Updated data (blue flash):

When new data is available for the selected data source:

1. The window for that airport flashes in blue.
2. All text turns blue after the window has flashed.

Left click anywhere in the window to reset the "blue flash" to indicate that you have seen the update.

This is enabled by default but can be disabled under SYSTEM -> SETTINGS if desired.

Runway mismatch indicator in ATIS view mode - Compares the RWY in use between VATSIM ATIS and WX.AWOS data and highlights the runway in use as follows:

•  RWY 21  - No mismatch (ATIS runway matches WX.AWOS)
•  RWY 21  - Mismatched runway (ATIS runway differs from WX.AWOS)

At Stockholm Arlanda (ESSA), both arrival and departure runways are monitored. A warning is shown if one or both mismatches.

Greyed out information in WX.AWOS view mode - the ATIS letter and RWY designator are greyed out from AWOS view mode when a VATSIM ATIS is available:

•  YAN  and  RWY 21  - VATSIM ATIS available, no mismatch (ATIS runway matches WX.AWOS)
•  YAN  and  RWY 21  - VATSIM ATIS available, mismatched runway (ATIS runway differs from WX.AWOS)
•  YAN  and  RWY 21  - VATSIM ATIS not available.

METSENSOR

Showing weather data in real time (updated every minute, or more frequently).

Updated data (blue flash):

When new data is available the data field that was updated flashes in blue.

This is disabled by default but can be enabled under SYSTEM -> SETTINGS if desired.

WINDROSE

Showing a wind rose, indicating wind direction, speed, cross/head/tail-wind component etc.

AWOS data is used for airports where it is available, METAR data will be used where no AWOS data is available, there is no way to manually select which data source to use.

Everything in the middle of the circle shall be read out to the pilot, what is shown is automatically filtered.

Legend

The module will default to display the runway with the highest headwind component.

1. Runway selector, choses which wind anemometer (wind sensor) to use if several are available, this also affects the wind components shown in 5.
2. Mean wind direction and speed (2-minute average, MEAN02 in metsensor).
   • Values shown in the circle shall be read to the pilots!
     • ≤60 degrees direction span (250-320 degrees in the example above) are shown.
     • ≤180 degrees shown as VRB.
     • ≤10 knot difference between mean wind speed and MIN/MAX speeds are shown.
3. The compass rose
   • The red line indicated the mean wind, coming from 280 degrees in the example above (2-minute average, MEAN02 in metsensor).
   • The yellow arc indicates the variable wind (10-minute average), variable between 250 and 320 degrees in the example above.
   • The dark grey thick line indicates the selected runway and its direction, 08/26 in this case
4. MIN/MAX (GUST if METAR data) wind shows the minimum and maximum winds.
   • The MIN/MAX/GUST wind is shown in bold if it shall be read to the pilots (≤10 knots difference between 2-minute and 10-minute min/max wind speed).
5. The head/tail-, and crosswind component indicators, this is affected by the runway selected in the top right corner. The example shows 2 knots headwind component and 1 knot crosswind component from the right for runway 26.

METAR/TAF

Shows raw METAR/TAFs.

Buttons:

• METAR - Toggles visibility of METARs
• TAF - Toggles visibility of TAFs
• AERODROMES - Selects which aerodromes are shown

Aerodromes not listed can be manually added using the text field.

SMHI

Shows SMHI "weather radar" from https://portaler-lfvradar.smhi.se/sverige

The map displays precipitation intensity, along with lightning strikes detected by lightning sensors.

New images are available every 5 minutes.

SWC NORDEN

Nordic significant weather chart.

Legend available here.

VFR

VFR analysis chart - This chart provides a quick and clear overview of weather conditions relevant to Visual Flight Rules (VFR).

SUN

Shows sunset/sunrise and day/night times.

• "Separation VFR" is shown during nighttime when VFR needs to be separated.

NOTAM - Notice To Airmen

Shows information about facility/service/procedure availability and hazards, such as taxiway/runway closures etc.

The NOTAMs can be filtered by aerofrome.

ECHARTS - LFV eCharts

Shows (a custom version of) LFV eCharts, where you can view airspace/waypoint information etc.

FLIGHT - Flight List

ARR DEP

Shows a list of flights to/from the selected aerodromes.

ATFM - Air Traffic Flow Management

ECFMP

Shows flow measures from ECFMP - European Collaboration & Flow Management Project.

DOCUMENTS - Wiki/AIP and other operational information.

CHECKLISTS

Shows checklist for controllers, (to be used as reference, not necessarily "read and do") the following are available:

• Open position - For when opening position.
  • When not taking over any airspace from already open positions.
• Close position - For when closing position.
  • When no relieving controller is taking over position.
• Handover/takeover - For when other controller/position is relieving (taking over) your airspace/position.
• Runway change - For planning and coordinating a runway change.

QUICKREF

Shows Quick References/Appendices as available from Quick References/Appen... | Wiki

The runway configuration in use is automatically selected but can also be manually chosen.

GOP/LOP/LoA

Shows Wiki pages as available from ATC Sweden | Wiki

AIP

Shows AIP pages as available from IAIP – AD 2 Aerodromes

OTHER

Shows other operational information.

• ESSA PUSH - Pushback procedure charts
• ESGG PUSH - Reference to which pushback direction is available from which stand, and information regarding which stands are blocked when pushing back for the respective stand (shown as tooltip when hovering stand number)

Note that pilots may not follow the IRL pushback procedures, depending on usage of tools such as GSX, also depending on updated profiles etc etc...

CODES (ICAO)

Shows a searchable list of

• Aircraft types, showing ICAO type code, wake turbulence category, wingspan, MTOW etc.
• Callsigns, showing ICAO flight plan designator, operator and country.
• Aerodromes, showing ICAO code, name and country.

REGIONAL AD

Shows the "Regional Aerodromes Overview" created by Thomas Ljung, from VATSIM Scandinavia Forum

TEXT ALIAS

Shows a searchable quick reference to the text alias included in the Swedish GNG package.

• Auto - Toggle visibility of "Auto" aliases.
• FSS - Toggles visibility of "FSS" aliases.

NOTEPAD

Shows a notepad to write notes, such as non-standard agreements with adjacent positions etc.

TRAFFIC

Shows sector occupancy for the selected sector combination.

The X-axis shows time, the Y-axis shows number of aircraft in the selected airspace volume.

•           - Indicates airborne aircraft.
•           - Indicates aircraft on ground and pre-filed flight plans.

ATS

Shows ATC bookings for the coming two days.

SECTORS

Shows Otto Tuhkunen's dynamic ACC sectorisation map.

DCT

Shows tactical directs (quick reference to LoA, shown at TopSky-map).

PLS (only shown when PLS integration selected.)

There is a SIMPLE logic mode available, this is completely independent of the actual PLS system and will only show a timer of your time online (using the CID which you are logged in with in IRIS).

Postface

Changelog

There is no specific changelog available, however all changes can be viewed on Github - Commits.

Significant changes are normally also announced in the VatIRIS forum thread. 

Contributing

Contributions of any kind are most welcome.

• If you find a bug or have a feature request/suggestion, please check that it doesn't already exist, if not, add an issue on Github.
• Github Pull requests are welcome.

Credits

To get in contact with the developers of VatIRIS (contact via Github might be preferred):

• Martin Insulander - 814118
  • Discord @mumrikki
• Max Kuhla - 1157125
  • Discord @maxlk96
• Among others.

GNG Package Changelog

This page contains an unfiltered technical changelog to the Swedish GNG package.

The Swedish GNG package is installed as described in THIS GUIDE, or manually from here.

For a filtered summary of changes optimised for controllers, see Revision Highlights.

EuroScope does not allow for plugins to overwrite when updating the GNG package using the automatic download. After updating, close EuroScope then go to %appdata%\EuroScope-> ESAA > Plugins > Updated Plugin" and copy the .dll files in the folder. Thereafter go back in the "Plugins" folder and paste the .dll files there. Overwrite existing files when prompted.

AIRAC 2505 (2413/1)

The new AIRAC provider for GNG is taking longer than expected. The files will still indicate AIRAC 2413.

AIRAC changes

• Area D184 changed
• ESDF RWY 12/30 withdrawn
• ESSV SID/STAR updated

Non AIRAC changes

• General
  • ESDF hold short line B RWY 01 added.
• TopSky
  • Areas AIP SUP 134/25
  • ESMV
    • MVA map added
    • MSAW exclude added
    • Airspace to be updated in 2506
  • SSR codes updated, A1000 not yet implemented
  • Freq maps updated
  • DCT maps updated
• GRP
  • WIP added/updated
    • ESSA (APN AB and APN D)
    • ESSB (APN 6-7)
    • ESGG (N APN)
    • ESNZ (TWY G)
    • ESPA (APN 12B)
  • ESSA Stands updated with type E295
    
• CDM updated to 2.2.6

AIRAC 2504 (2413/1)

AIRAC changes

• The new AIRAC provider för GNG is not yet in place so the ES-files will still indicate AIRAC 2413.
  
• Area R01-R09 renamed R1-R9.
• New R-area, R126 Rågården and R128 Harpsund.
• TRA updated
• EKCH ERNOV STAR runway 22L/R updated.
• AIP SUP added to 70/25.

Non AIRAC changes

• General
  • ESSR_MM_APP added
  • ESAA_CTR added
  • Login profiles updated with ESSR_MM_APP and ESAA_CTR
  • ESOS sector ownership changed
  • Radars updated to extend the Mode-S range
• TopSky
  • Areas AIP SUP 99/25
  • TEXT INFO Levels fixed/updated
  • Auto freq maps updated (AA replaces S1 and OS ACC revamp)
  • ESAA and EVRE added to CPDLC
  • RTM added to show ACC FREQ map
• GRP
  • ESSA: WIPs and pushback STD 8 changed.
  • ESKN: WIP timeframe extended
• CDM
  • Added Event CTOT URL (same server as AMAN data)
• VCH updated to 0.8.6

AIRAC 2503 (2413/1)

AIRAC changes

• The new AIRAC provider för GNG is not yet in place so the ES-files will still indicate AIRAC 2413.
• New waypoints, IBNIC, MIDIC and WAKZU.
• Area R01-R09 renamed R1-R9.
• New R-area, R126 Rågården and R128 Harpsund.
• TRA updated
• EKCH ERNOV STAR runway 22L/R updated.
• AIP SUP added to 70/25.

Non AIRAC changes

• General
  • ÖKC completely revised, split in two TC (primary)/T3. COP updated accordingly.
  • Wrong frequency for ESMM 9 fixed.
  • Missing LENSO STAR at ESNU fixed.
  • EKLOV/SUXEM now selectable as STAR for ESDF without having to select a DFXXX waypoint first.
  • COPX RUMAR/ELPOL to EPGD fixed to retain XFL after DCT.
  • DEP-list in TWR profile removed. Unintentionally added last update.
  • ESTL_TWR and ESGG_W_APP login profile fixed.
    
  • METAR in title removed.
  • Euroscope messages updated to reduce nuisance distractions.
    • Info (Message) -> do not show (VATSIM Data Downloaded, ES Loading files, etc)
    • Warning (Message) -> show chat handler (VATSIM Data not parsed, etc)
    • Error (Message) -> show unread chat handler (Errors in ESE-filer, etc)
    • Server (Server) -> do not show (Welcome message from server)
    • Coordination request (Coordination) -> do not show (Shown both in lists and by sound in TopSky)
  • ES screen will now remain in full view when exiting full screen to more easily show the windows menu bar.
  • Added TECH sector above GOT TMA to resolve issue with tracks staying in coordinated state after transfer to ACC.
  • ESCM ground layout updated, APN 1+2 and TWY J+K added.
• TopSky
  • Latest documentation added.
  • DCL at ESGG updated. The correct frequency for next controller will be included in DCL when logged in as DEL and traffic is not assumed.
  • EKDK L showing wrong frequency fixed.
  • ENOS frequencies shown now in 8,33 kHz.
  • Removed C-flag for ESMM W for traffic to SA/SB.
  • Mil area PCA S12/S13 revised.
  • MSAW exclusion removed where ESGR TIA used to be.
• GRP
  
  • APF split in PAX/Cargo by Callsign to allow correct stand assignment. APF0XX is cargo.
  • USE:C changed to USE:AC for stands at ESSA and some at ESGG to allow aircraft classified as airliners to be assigned cargo stands if correct callsign.
  • ESGG: A318 removed from stands with docking to gate
  • ESSA: Pushback map revised (4, 8, 20, 31 and odd F-stands changed, APN BC hidden)
  • ESCM: APN 1+2 added
  • Revised regions to support new GRP beta (not yet added)
• CDM updated to v2.2.5.3
  
  • In TWR-profile the CTOT kolumn is updated to use the CDM version.
• MAESTRO
  • Latest documentation added.

AIRAC 2413

AIRAC changes

NIL

Non AIRAC changes

• General
  • Corrected typos in login profiles
  • Added new text aliases for unruly pilots
  • Reverted FSS COPX/XFLs
  • Revised sector priority for SU TIZ/TIA (SU now has lower priority than OS APP/ACC)
• TopSky updated to v2.5
  • Revised CPDLC "UNICOM" free text
  • Areas updated to SUP 251/24
  • ESMT MVA changed (TMA A 2600 ft)
• GRP
  
  • Added ESKN RWY 16/34 closure
  • Added ESOW grass RWY closure
  • Cleanup of old/unused ESSA WIP
• CDM updated to v2.2.5.8.10b
  
• MAESTRO updated to v1.1

AIRAC 2412

AIRAC changes

NIL

Non AIRAC changes

• Added FSS COPX/XFLs

AIRAC 2411

AIRAC changes

NIL

Non AIRAC changes

• General
  • Fixed XFL changing close to border for flights to OS APP.
  • Revised logon profiles
    • Removed info about initial altitude where redundant
    • Added missing positions
    • Replaced "Covering xx CTR and TMA" with Vatglasses link where appropriate
    • Added CPDLC logon code for OS/GG APP
• TopSky updated to v2.5 beta 14
  • Added VALDI DCT S3->ENOR
  • Areas updated to SUP 220/24
• GRP
  • ESKN ASR corrected (showed all aircraft with white labels before fix)

AIRAC 2410

AIRAC changes

NIL

Non AIRAC changes

• General
  
  • Added TECH sectors for ARR ESGG so TWR is not skipped in the SI sequency.
  • Updated GND/DEL sectors at GG to align with ESSA and so ARR will not get DEL in SI sequency.
  • DEL will only have gray A/C in list unless assuming. Then correct SI sequence to GND.
  • ESTL TWY designator J corrected
  • ESAA_PLN_CTR SI updated to PLN
  • Added VCH CTL flag in Sector List for TopSky-profile
  • Added possibility to open callsign menu in SEL in TopSky-profile.
  • Removed all separate non-Swedish TMA, they are now consolidated to one selection INT TMA.
  • EKRN CTR removed
  • Mountainous Area in ESOS K renamed ESOS K MOUNTAINIOUS AREA, previously ESOS K.
  • ASR ACC and TWR APP updated with above changes.
  • ESTL SID/STAR/ILS unavailable due to VOR LJU withdrawn. RNP still available.
• TopSky
  • Areas updated to SUP 204/24
  • Map KETAP/OGBER RWY designator changed
• GRP
  • Updated WIP ESSA (incl SUP 192/24), ESCM
  • ESSA stand assignment, APF, JON moved to T3
  • ESSA Updated stand assignment for SAS
  • T3S stand definition updated 
    

AIRAC 2409

AIRAC changes

NIL

Non AIRAC changes

• TopSky updated to v2.5 beta 13
  • Added Equip_Assume_All_SSRs_Mode_S=1
• GRP
  • ESSA
    • wingspan map updated
    • WIP maps updated
    • stand definitions updated (T2 AT7*, T5 E290/295)
• VCH
  • Added Taxi to pending requests menu.
• MAESTRO updated to v1.1 beta 8

AIRAC 2408

AIRAC changes

• Area R124 added, D180 changed.

• ESHI removed (permanently closed)
• AIP SUP 167/24 included

Non AIRAC changes

• General
  • VCH-plugin added. Pending request is now in Start Up list and DEP list. "Hold short of" added to Taxi In/Out list and a new Clear To Land flag has been added. 

  • VFR-SIDs added for all controlled airports

  • VFR fixes revised. VFR-fixes now 5 letter fixes. (points with cardinal directions have XXYYY syntax, XX=last two letters of ICAO, YYY=direction.)

  • ESMQ apron layout revised. Apron by THR 05 added

  • UMKK positions readded with SI

  • Added EKDK_OE/WE_CTR

  • Added EYVL_M_CTR and EYPA Information

  • Removed BALT_CTR no longer used.

  • ESNN APN M layout updated

  • Additional ESSV STAR DCT VSB added.
• TopSky
  • Updated to version 2.5b11
  • CPDLC messages auto archived after 60 sec
  • VFR-waypoints + Label, added with hotkey ALT+B (Both) 
    

  • Added highlight of A345/346, B779 and C5/5M for ESOS CTR

  • Auto freq map ESGG TMA also shown for IBA, IB, GT

  • Auto freq map UMKK revised.

  • MM LOA map. BINKA revised (showing using coordinates as not in dataset)

  • DENOL ADES EDDV corrected to EDLV

  • OGBER/KETAP included in auto map for ML,8,9

  • OS LOA map. 01 also shown for A and AW

  • VSB labels reordered

  • Territorial waters border map added (Under MISC)
    

• GRP
  • LB, LD and LR added to Schengen countries
  • ESKN and ESGP added
  • ESSA TWR ASR: RNP APP maps added
  • ESSA stand F29L, S80, S81 definitions updated.
  • ESGG (Airline stand priorities) assignment revised
  • ESGP and ESMQ RWY end coordinates added
• MAESTRO

  • Updated to version 1.1b7

  • Removed from TWR-profiles

AIRAC 2406

AIRAC changes

• New SID/STAR at ESSD.
• AIP SUP updated to 117/2024
• R05A/B added

Non AIRAC changes

• General
  • Encoding corrected for Areas and Maps files (8859-1)
  • Soaring sectors in Malmö TMA updated 
• TopSky
  • MM K/L auto frequency not shown for MM K/L
  • Auto frequency shown for OS APP reduced to sector name, now excluding "OS", OS 2 labels moved.
  • Transfer Confirmation removed from DEL/GND as XFL is not showing correctly.
  • ENOR_SC_CTR frequency added
  • Some EKDK frequency moved
  • EKRN frequency updated to 8,33
• GRP
  • ESSA and ESGG WIP Timespans updated
  • ESSA Wingspan map layering corrected (to draw above active RWY area and dep/arr arrows)

AIRAC 2405

AIRAC changes

• AIP SUP updated to 101/2024 (Temporary restricted area ESR861 Kramfors)
• R121 Changed
• R123 Added
• D187 Withdrawn
• D191 Re-added
  

Non AIRAC changes

• General
  • COP ERNOV XFL behavior fixed. (XFl now keep close to and after COP)
  • Fixed wrong XFL behavior efter DCT outside TMA for ESSA/B APP
  • ESCF and ESDF heli RWY added (selectable in lists)
  • Login profiles added for ESOS DEP-W and DEP-E
  • Vatglasses link added to ACC login profiles
  • PCA (Military exercise area) Waypoints added to show FLEG to area when PCA filled in FPL. ESxxx (e.g. ESM21)
  • Updated ES to aline with LOP. ESPE/NZ only covering up to FL95 again. COPX updated to FL90.
  • VATCAN not drawing on screen to remove annoying UI. (activate under plug-ins when needed)
• Lists
  • Taxi Out List CTOT item in TWR.prf corrected, now showing TopSky item instead of CDM item.
  • Left click on RTE/AHD fixed to select SID in TWR.prf.
• TopSky
  • PCA M85 corrected, M91, 92 added
  • AMS (Airspace Management) List now sorted (D, R, TRA, PCA, FS(FlygSport))
  • NOTAM activation removed (except for foreign R/D-areas)
  • AUP (Airspace Use Plan) activation now available, including temporary areas from AIP SUP (tack Felix)
  • Manual usertext "FLYG" removed, as it is shown depending on activity loaded from AUP.
  • R/D-Areas in SB CTR revised to match other areas.
  • ROENNE SW level in Freetext corrected
  • ESGG E/W split only shown when relevant (both GE+GW open)
  • Swedish ACC (also APP for ESOS+ESGG TMA) frequencies can be shown for TWR/APP positions.
  • UMKK 2.5NM line added. To aid ATCO not to get too close to UMKK FIR.
  • ESOS TMA D01R sector added. Shown when deparing RWY 01R.
  • EYVL freq updated
  • New CPDLC free text added. 
  • RNP STAR now primary for traffic to ESNQ
  • ESCM VRP encoding corrected
• GRP
  • GRP implemented: ESCF, CM, GT, IB, KS, MQ, MX, NN, NS, NX, OW, SL
  • ESSA WIP updated and reordered (fr Arlandas extranät)
  • ESGG/ESSA ground view and labels reworked, (added LVP auto map with CAT II HP and ILS sensitive area at ESGG)
  • ESMT Stand 7 removed
  • ESSD B 14 holding position moved
  • ESSB RWY THR moved for RIM
  • ESMX Aeroclub moved
  • ESGG APN wingspan restrictions added to map
  • ESSA TWY wingspan restriction map added
  • ESMX Stand labels updated (Aeroclub moved)
• Maestro
  • Updated to v1.1b7 (.dll and ICAO_Aircraft.json)
  • Added final lengths to settings file (SA 01R 14 nm, all other default 10 nm)

Full reinstall required. No file changelog avbl.

AIRAC 2403/2

AIRAC changes

NIL

Non AIRAC changes

• General
  
  • RTC added back in sector ownership to ESSA and ESGG. (APP has priority over RTC on ESSA and ESGG. RTC will cover TWR only if OS/GG APP offline)
  • Text alias: link for .wt corrected
• TopSky
  • Settings: "Airspace_C_No_Flag" in line 2 removed.
  • Areas: Removed space in line 2290, corrected D357 to R357

AIRAC 2403/1

AIRAC changes

• ESSA RWY 19R BABAP/TOVRI SID revised (turn now waypoint based instead of altitude)
• New significant points added: ABJAZ, AGWIM, ARIWA and OTMAB
• New ESD191 Tveta

Non AIRAC changes

• Sector sequence for ESMM to ESSA/SB APP when ESOS is offline now works for Arrivals via TRS/NILUG/XILAN and Departures via PETEV/NOSLI/TRS. Correct SI will only show for ESMM when traffic has descended below MM airspace.
• General
  
  • Removed RTC in sector ownership from ESSA and ESGG.
  • Temp R/D-areas added from AIP SUP 8-57/2024
  • Visibility points updated for ESAA_PLN_CTR
  • Added logon profiles
    • ESAA_PLN_CTR (replaces ESOS_PLN_CTR)
    • ESMM_XK_CTR
    • ESMS_XL_APP
  • New test alias added: "You are not allowed to vacate via taxiway C or D after landing RWY 03 unless approved by ATC, please see https://vatsca.org/esggtaxi"  .wtgg
• Lists
  • Ground state changed to xLU and xTO to be sorted correctly
  • Ground status list column renamed from G/S to STS to make it stand out from C/S
  • Start Up List column VATCAN CTOT added
  • CDM Plugin
    • Added latest CDM-plugin version
    • Updated Startup list with TSAT Delay via left click on TSAT
    • Updated Taxi out list to show CTOT instead of TTOT.
    • A small bug in the new CDM version makes the TSAC show a strange value. This can be disregarded.
• TopSky
  • Removed Auto show VRP for ESSA APP
  • EKCH APP freq now shows for XK/XL
  • TopSky views updated
  • Updated C-flag
  • CARD window open automatically for CTR and ESMS_APP
  • Added AMA-map (combined with MVA)
  • Freq-Map corrected: ESOE TWR
  • Map 25 NM centerlines SA RWY 01/19 added
  • ASR Fast keys (F1+1,2,3 etc.) updated in TopSky.prf
    
  • Glider sectors added (FSxxyyy) xx=ICAO yyy=sector name. Shown on radar display with green borders
  • CPDLC window open automatically for CTR and ESSA_/ESGG_/ESMS_APP
• CPDLC
  • Added CPDLC address for SA/SB/GG APP and ESMM XK/XL
  • All neighbouring FIR updated
• AMAN
  • Added EKCH MAESTRO setup
  • Changed default position for COTS and AMAN-window
• GRPMaps
  • ESSA Pushbacks added
  • ESSA WIP A0299/24 (+TWY Z, U) added
  • ESMS CAT II HP (shown when LVP selected in GRP)
  • Wingspan/ATYP alerts added for ESMS, ESSB, ESPA, ESNU, ESSV, ESSA
  • ESNU GND freetext stand labels adjusted
• GRPStands
  • ESSA Stand S2L, S3L removed. Assignment updated
    
  • ESMS Stand 14 removed. RYR Assignment updated
  • ESNU, ESSV, ESNZ, ESNQ, ESTA, ESDF Added

AIRAC 2401

AIRAC changes

• New significant points added: ARJUD and SEJPA
• ESD186 Trängsletdammen completely withdrawn.
• ESMQ NDB KM withdrawn.
• ESSA RNP Z 01R renamed RNP W.

Non AIRAC changes

• TS VCCS: EKDK positions revised.

AIRAC 2312

AIRAC changes

• ESJS Skellefteå Lasarett Added

Non AIRAC changes

• ESAA_TMC.asr is now split into two ASR. One specific for Stockholm APP and one for Göteborg APP. Please remove the old ESAA_TMC.asr. For ESMS_APP use ESAA_ACC.asr. For any other APP or TWR use ESAA_TWR_APP.asr
• Change to definition of some lines. White dotted lines apart from indicating Control zones also indicate ACC sectors below FL95 that is bordering uncontrolled airspace. A solid white line indicates a border with controlled airspace on both sides. This only applies to ACC sectors and not Approach sectos.
• The graphical representation at the border of ESMM and ENOR (delegated airspace Örje, Bohus and Koster) has been updated to make the AoR more clear.
• EKCH CTR updated.
• XFL for DEP ESNQ now FL90
• Flight Information Service border below Köpenhamn TMA added to MAPS ARTCC LOW
• Added ESOS/ESMM/ESGG ACC/APP Frequency to MAPS
• Köpenhamn APP frequency in MAPS updated to 8.33
• ESNZ RNP AR 12 joining point updated.
• ESOE MVA Sector corrected
• Obstacles 850ft+ height within 10 NM from controlled airspace added.
• Revised auto activation of DCTs to E and S from OS ACC, including zoom filter
• 3 NM SEP AREA removed
• All COPX between sectors with vertical split 365 removed as they create wrong PEL/XFL. Pointless COP 2/3, 6/7 and 8/9 is still in the system.
• Ground layouts for ESNJ and EMSV added. ESOW updated (APN 3 closed, Airways flight school removed)
• ESOE VRP KUMLA changed to KUMLAN
• MIL STD Departures added for ESCM, ESDF, ESPA, selectable in SID
• Stand assignment for F28 at ESSB should now work better.
• Added .833 to text alias with information on how to manually tune frequencies. (use .833)

AIRAC 2311

AIRAC changes

• New D-area D190 Kattegatt
• TopSkyAreas: Added from AIP SUP R833,834,835,839,840, R317,318,319,803,804,970

Non AIRAC changes

• Multiple 8,33 kHz frequency updated
• New PEL/XFL to EPWW for EKCH/ESMS DEP/ARR
• New Release Lines to EDWW/EDUU
• Updated DCT points to EDWW/EDUU/ENOR
• ESSB departures revised, new "SID/HDG" see LPM.
• ESSA config 5 changed. All DEP to ARS, PETEV, NOSLI and TRS is cleared via KOGAV SID.
• Maestro plugin (1.1b6) updated
• GRPluginMaps: File reworked, showing only data for active airport. Wingspan/Heavy restrictions added at ESSA/GG
• Added VATCAN (hidden) and AMAN data fields to TML 1 and 2
• TopSkyMaps: RNP APP displaying filled fix and name at last fix to join RNP APP

AIRAC 2310

AIRAC changes

• NIL

Non AIRAC changes

• CTR Coordinates corrected/updated for, ESNU, ESCM, ESGT, ESDF
• TopSkyMaps missing TMA Altitude for ESNZ added
• TopSkyMaps MVA added
• Maestro plugin, settings and manuals updated (1.1b5)
• GRPMaps ESSB Y3 WIP Removed
• Precision (PAR) Positions added
• CDM plugin updated to latest version

AIRAC 2309

AIRAC changes

• NIL

Non AIRAC changes

• Basic ATS-routes updated.
• 3 nm separation line removed as 3 nm radar separation applies below FL 195 in the whole FIR now.
• PCA sectors (Military exercise areas) updated.
• GRplugin Maps, new WIP areas added at ESGG and ESSA.
• VCCS panel updated.
• 8.33 kHz frequencies added for EDUU.

AIRAC 2308

AIRAC changes

• R-area R122 Muskö added.
• Some R-areas with radiuses has been updated.
• AMA (MSAW) updated.
• New initial climb altitude for ESGG SID to MISVI and SOJWI. New altitude is 4000 ft. Only valid for those two SIDs, the other turboprop SIDs has 5000 ft.
• New IAP for ESCF.

Non AIRAC changes

• Maestro plugin updated. New settings file. Stable state is now at 12 min to not catch aircraft in climb.
• Data link clearance (DCL) format updated to align with real world.
• The data for Holding Point, Taxiway, Stand and Apron moved from GRplugin Maps file to sector file.
• ESSA and ESGG ASR, removed graphical draw directly from ASR. All graphical elements now drawn from GRplugin with sector file as reference.
• GRplugin Functions menu -> Maps, resorted. All aerodrome specific items now found under respective aerodrome while WIP moved to a seperate item. 2nd window now controlled from the same menu item.
• New Alias shortcut for aircraft making wrong turns with link to taxiway map added, ".wt".

AIRAC 2307 V3

AIRAC changes

• ESPA TEMPO VOR approach RWY 14 (Is selectable via STAR as VORDME·T) ESPA banarbete tillfälliga procedurer

Non AIRAC changes

• ESSB WIP area updated
• ESPA WIP area added
• Stand assignment now works correctly for aircraft not approved IRL, eg. F28.

AIRAC 2307

AIRAC changes

• ESOE TMA extended and IAP updated.
• Restricted area R210 new.

Non AIRAC changes

• CPDLC setting changed, now only transfer is default.
• ESE FLEG runway 01R ESSA updated to remove old waypoint.
• New behaviour when resizing windows.
• TWR frequencies can now be selected to be displayed via the Maps menu.
• CDM mode changed to “event mode”. TSAT will not be assigned automatically from EOBT, once a TOBT is entered then a TSAT will be calculated. This will prevent nuisance TSAT.
• Release line ESJAH new. More info will come with the new LOP.
• RNAV SID now default at ESOK.
• ESPA stand stands updated.
• ESGG Ground network updated with new stands.
• ESSB WIP Y3 added.
• ESSA strand assignment updated to allow less common aircraft types to be assigned to the terminal.
• SSR updated.
• CPH_I/E_ APP added. Same as EKDK B/D. New frequencies are not shown automatically yet. Use SI frequency.
• Almost all remaining ground layouts are now completed

AIRAC 2305

AIRAC changes

• New significant points: HUMBE, NAFFI, ODHAF. (In the area of Luleå and Pajala)
• Multiple new, removed and updated R/D-areas.
• New RNP SIDs for ESOK.

Non AIRAC changes

• XFL XILAN for ESSB arrivals changed to FL100.
• ESSA_DEP renamed ESSA_W_DEP with new SI DW. Multiple COP updated to reflect this.
• For EDDB arrivals, KETAP and OGBER added as optional DCT selectable from MAPS -> LOA ESMM submenu.
• General Setting, "Use ISECT.TXT for scratch pad" activated to allow for DCT to point not in SCT-file.
• VCCSSettings updated.
• TopSkySSRcodes updated.
• Symbols setting file updated. (Thanks to Max), Ground layout completely reworked for:
  • ESCM
  • ESDF
  • ESGT
  • ESKN
  • ESKS
  • ESMQ
  • ESMS
  • ESMT
  • ESMX
  • ESNO
  • ESNQ
  • ESNU
  • ESNZ
  • ESOE
  • ESOW
  • ESPA
  • ESSB
  • ESSU
  • ESSV
  • ESTA

AIRAC 2304

AIRAC changes

• Restricted area R117 Nynäshamn new and some small changes to other R/D-areas.
• Instrument procedures updated at ESMT.
• Northern part of ATS-route T31 renamed T81.

Non AIRAC changes

• CDM plug-in updated.
• New tick box added in the CDM list to keep track of what TSAT is communicated to pilot. Some other updated functionality.
• Manuals for the Swedish setup and CDM plugin has been updated.
• All stands now available at ESGG, ground layout updated accordingly.
• ESSB ground layout completely revised.
• Ground Network added at ESSB.
• 2nd Window in the GR-plugin now works for ESSA and ESGG. Thx Max.
• BAW and FIN(short haul) together with some other airline moved from terminal 5 to terminal 2 at ESSA.
• New colour (white) for R/D-areas that where ATC can not give permission to enter. E.g. national parks, prisons, nuclear power plants e.t.c.
• SID NEGIL2G from ESGG now have XFL 90 from GW to GE.
• Missing XFL from ESMM 8 to ESMM L for traffic to airports in northern Germany hopefully fixed.
• Missing line in INT borders fixed.
• Missing RNP-procedure at ESKM added.

AIRAC 2302

AIRAC changes

• NIL

Non AIRAC changes

• ESOS 3 now covers all of ESOS AoR when ESOS 1 is offline. With both online the normal division of sectors apply. If someone is online as ESOS 3, consider opening ESMM 2 instead of ESOS 1, this will result in the same division as ESOS 1 together with ESMM 2. This is a test to see if the workload can be managed better when alone as ACC.
• EFIN C now wovers more sectors when no other EFIN is online.
• Frequencies displayed updated for EDWW/EDUU, EPWW, EFIN and EKCH APP.
• SSR-code assignment updated with better handling of APL, VFR FP, local codes and specific callsigns for ambulance helicopters.
• Stand assignment at ESSB updated.
• Added Holding Points and taxiway closed markings to ESSB ground layout.
• SIM-ONLY ASR for ESSB added.
• Added missing line in area Örje.
• Updated XFL handling inbound ESSB.

AIRAC 2301

AIRC changes

• NIL

Non AIRAC changes

• A-CDM plugin updated.
• New manual: "Swedish tower setup and CDM plugin".
• Updated manual: "Swedish Setup for EuroScope"
• TWR / TWR A-CDM lists reworked.
• Added an Alternate Ownership for DEL-positions to have traffic show correctly in the lists. Only to be used by DEL. Drawback is that the sector sequence for the next GND position will not work, alas it did not work perfectly before either.
• Simulator ground network added at ESGG. All taxiways are now predefined for easier management of simulated ground traffic.
• SIM-ASR fixed, now actually working.
• Colours for ESGG Ground Radar view corrected to match real system.
• Added 90 m markers for TWY C, D and E in ESGG Ground Radar view. Holding points for the same TWY changed to red.
• ESSA Stand F33L renamed F33. Stand F33R removed.
• Correct SID now assigned at ESMS. (K-SID)
• Issue with XFL to EPGD via PENOR fixed.
• Issue with COPX/XFL when close to ESJAH fixed.
• APL squawk code range hopefully fixed, should be 5701 to 5777.
• Restricted areas at national parks are now shown in white.
• Colour for restricted areas adjusted.
• Restricted areas along the national border is realigned

For older changes to the sector file, see this forum thread