Jump to content

2021-11-12 - Relief Callsign Policy


Harry Sugden
 Share

Recommended Posts

Effective 12 November 2021

 

Upgrades to the VATSIM infrastructure now permit the use of an additional character in callsigns. The variable use of relief callsigns for positions with a double letter middle identifier has long been a source of confusion.

 

As such, the formal policy for the relief callsigns of all UK (London and Scottish) area positions is the addition of a second underscore between the middle identifier (e.g. SC) and the suffix (CTR).

For example:

  • LON_SC_CTR → LON_SC__CTR     [LSC]
  • MAN_SE_CTR → MAN_SE__CTR    [PCSE]
  • LTC_SW_CTR → LTC_SW__CTR     [TCSW]

 

This policy extends to aerodrome/approach positions that previously required amended middle identifiers or truncated callsign prefixes to implement a relief callsign. The relief callsign for positions without a middle identifier shall also be determined by the addition of a double underscore, and not a number.

For example:

  • THAMES_APP → THAMES__APP (previously THA_APP)
  • EGLL_2_GND → EGLL_2__GND (previously EGLL_5_GND)
  • EGKK_P_TWR → EGKK_P__TWR (previously EGKK_Q_TWR)
  • EGCC_DEL → EGCC__DEL (not EGCC_1_DEL)

 

Controllers are reminded that it is also possible to identify a controller position by its identifier in the controller list. These are the same identifiers used in crib sheets and in vMATSs when defining handoff and top-down orders.

Edited by Harry Sugden
  • Like 4
Link to comment
Share on other sites

 Share

  • Similar Content

    • Harry Sugden
      By Harry Sugden
      Effective 2 December 2021
       
      To increase the availability of the use of 3 NM radar separation, the terms of its use are revised.
      Section 3.3.4 in both the London (EGTT) vMATS Part 2 and Scottish (EGPX) vMATS Part 2 shall be amended as follows (additions in bold):
       
      When the only means of coordination is via text, this is not sufficient for the application of 3 NM radar separation between aircraft on different frequencies.
      Note 1: Both controllers/units must be approved to use 3 NM for these revised conditions to apply.
      Note 2: For APC controllers, local ATC documentation will specify the airspace in which 3 NM radar separation may be applied. In the absence of any local ATC documentation this shall default to within 40 NM of the aerodrome and below FL195.
    • Harry Sugden
      By Harry Sugden
      Effective 2 December 2021
       
      Due to the difficulty in applying time-based rules on VATSIM and the lack of a planner controller under busy conditions, the rules for the Deemed Coordination of En-Route Traffic are amended as follows in the Scottish and London vMATSs.
       
      Additionally, a new section is added:
       
      The next sector shall be notified via:
      Voice communication; Text communication; EuroScope coordination request*; or TopSky, which automatically highlights changes in RFL on the aircraft tag. *Rejection of the coordination request by the receiving controller should be actioned as appropriate either by follow-up verbal/text coordination or by reverting to the previously agreed RFL when an aircraft has not yet changed its level.
      Verbal or written acknowledgement is not required, but controllers should be mindful that the receiving controller may still raise an objection or propose an alternative level.
    • Daniel Chester
      By Daniel Chester
      Does anybody have a quick and easy method for working out an aircrafts track miles from touchdown when starting approach? I am aware its something we should be passing to an aircraft on initial contact when working an approach position, but I often find it difficult to work out accurately - especially when busy!
    • Harry Sugden
      By Harry Sugden
      Effective 4 November 2021
      Due to a Eurocontrol requirement, the UK has now removed all CDR 3s from the AIP. Now that all CDR 2 and 3s have been removed, the 1/2/3 categorisation is no longer required.
      As such, the AIP has amended the definition in ENR 1.1 as follows:
      This replaces the previous definition:
      The Scottish and London vMATSs will be updated at the next revision.
    • Chad Byworth
      By Chad Byworth
      Effective 4 November 2021
      To better protect commercial air traffic movements operating between Land's End and Scilly Isles/St Mary's airports the Lands End Transit Corridor has been withdrawn and replaced with the newly effective Land's End Radio Mandatory Zone (RMZ). The RMZ (depicted in the figure below) is slightly larger than the previous LETC in its eastern portion and is notified from surface to 4000 ft AMSL (defined on the Land's End and Scilly Isles/St Mary's QNHs depending on the controlling authority).
      Figure 1 - Land's End RMZ and local airspace features

      The controlling authority is:
      Land's End Tower (120.250 MHz) EAST of 10 DME LND Scillies Approach (124.875 MHz) WEST of 10 DME LND When only one position is open it shall control the entire RMZ (but shall not provide top-down ATC at the opposite airport).
      For pilot's requiring a surveillance based service either Culdrose Approach (134.050 MHz) or Newquay Radar (133.400 MHz / 127.925 MHz) may provide a service within the RMZ subject to satisfactory coordination with Land's End Tower and/or Scillies Approach (London Control (West) may provide this service in the absence of either Culdrose or Newquay).
      Full ATC procedures will be notified in the pending Land's End ACB and Scilly Isles/St Mary’s ACB which shall be released for public review this weekend.
      Documentation Status
      This procedure change post will be incorporated into the pending ACBs in this documentation cycle. The sector file will incorporate the change into the 2021/12 release.
×
×
  • Create New...