Using Alternative Ownership

Alternative Sector Ownership is a powerful and useful tool enabling observers and mentors to see the same area 'lit up' - or 'owned' - as that of the controller they are observing or teaching.

As an observer, you will need to make a quick change to the .ese file each time you get a new version of the sector file.

---

Note: It is only possible to observe area sectors - not TWR/APP positions - with full alternative ownership. (This does not apply to mentoring.)

Note: All of these alternative ownerships only work as long as your primary frequency is 199.998 - i.e. do not select a primary frequency in the voice setup dialog unless you are mentoring and have taken over the frequency.

Set Up

Open up the UK.ese file, and look for the following line, which is clearly labelled near the top:

EXAMPLE_OBS::199.998:O:O:EXAMPLE:OBS:-:-:

Depending on your typical observing callsign, replace 'EXAMPLE' with that:

HS_OBS::199.998:O:O:HS:OBS:-:-:

If you use an INS callsign to observe, you need to change both instances OBS to INS:

HS_INS::199.998:O:O:HS:INS:-:-:

You will need to make this change each time you update your sector file, as it won't be carried over between versions (for obvious reasons).

Using Alternative Ownership

Open up the profile as normal that you would like to observe or mentor using, and connect up to the network.

• Observing? You must use the callsign you specified in the .ese file, as above
• Mentoring TWR/APP? You need to use a callsign in the format EGXX_M_TWR / EGXX_M_APP
• Mentoring CTR? You need to use a callsign in the same format of LON_CM_CTR / LTC_SM_CTR / SCO_M_CTR / STC_M_CTR

Then, go to OTHER SET, and open Sector ownership setup ...

Now click Select All

⚠️ IMPORTANT! We have a lot of sectors in the UK and a complicated file, so EuroScope will look like it's not responding after you press Select All. Do not touch anything and wait this out. ✋ EuroScope will return!

Once EuroScope has started responding again, select the drop-down where it currently says Default:

Instructions from then on are dependent on what role you would like, so pick the appropriate section below:

• Observer
• TWR/APP Mentor
• Area Mentor

...as an Observer

Select the 'Observing [SECTOR DESCRIPTION]' that corresponds to the sector/controller you would like to observe, then click OK to close the window!

Some things to point out:

• This only works for the 'Observing [SECTOR DESCRIPTION]' options, and not the 'Mentoring FIN' or 'Mentoring TWR/APP'. To observe TWR/APP positions, we suggest you simply open the Active airport/runway selector dialog and choose the airports for which you want to see the traffic populate lists for.
• All of the options will work as intended, regardless of whether that controller is online or not. Even if LON_C_CTR is not online on the network, selecting 'Observing LON_E_CTR' will 'own' the area of LON_E_CTR (and LTC_E, LTC_NE). You do not require the position that you select to be online, in order to observe the traffic/airspace it would own.
• The options are dynamic. So if you have selected 'Observing LON_E_CTR' and LTC_NE_CTR is connected as a real controller, then you will only 'own' the airspace of LON_E_CTR and LTC_E_CTR.

...as a TWR/APP Mentor

Select either 'Mentoring FIN' or 'Mentoring TWR/APP', then click OK to close the window!

...as an Area Mentor

Select the 'Observing [SECTOR DESCRIPTION]' that corresponds to the position you are mentoring, then click OK to close the window!

If mentoring SCO_CTR, whilst STC_CTR is also online either as a controller or as another mentoring session, you should select 'Observing Scottish FIR (excl. STC_CTR)'.