Jump to content

2021-01-28 - Assuming of Aircraft Tags


Jack Edwards

Recommended Posts

Jack Edwards

Effective 28 January 2021

From the effective date, controllers shall only ‘accept’ the transfer of an aircraft tag from the sending controller when the aircraft has ‘checked in’ on the receiving controller’s frequency. This will apply to all transfers of aircraft tags, both within the UK and with external controllers. The reason for this change is explained at the end of this post.

This change will enable the sending controller to recognise which aircraft have not yet checked in with the next controller, thus helping the sending controller to:

  • recognise which aircraft they did not transfer over voice when they initiated the transfer of the tag.
  • recognise any aircraft which may have read back the frequency incorrectly, or who have not made it to the next controller.
  • regulate the number of active transfers to a single controller - i.e. if the same controller still hasn’t made contact with several aircraft transferred by you, adding another to the queue may not help.
  • recognise when other frequencies are busy - we would encourage members to check in with their peers to offer to help find any adjacent ATC that might reduce their workload in these cases.

The transfer of an aircraft tag from a UK radar-equipped unit to another UK radar-equipped unit shall indicate to the receiving controller that the aircraft has been Identified, their Mode A code Validated, and their Mode C readout Verified. For this reason, tags of departing aircraft should not be assumed by controllers unless it is their responsibility to complete IVV (see notes below).

 

Aircraft from unmanned airspace 

For aircraft coming from unmanned airspace, controllers should continue to assume the tag after sending a  ‘contact me’ request. This signals to other controllers that they are trying to make contact with the aircraft.

 

Applicability 

This change applies to all controllers who assume aircraft tags. 

 

Notes:

  • Controllers should not assume aircraft tags for departures until they have checked in on the frequency.
  • S1 and S2 rated controllers are not trained to complete the IVV process, so should never assume or transfer an aircraft’s tag. 
  • S3+ rated controllers, when manning a DEL, GND or TWR position should not routinely assume aircraft tags as IVV is not normally completed by these stations. However in exceptional circumstances - should they utilise the advanced features of the ATM to complete the IVV process - they may assume and subsequently transfer the aircraft’s tag as a tower controller. 

 


 

Background - Why is this changing? 

VATSIM UK has agreed with some of its neighbours in new LoAs that neither party will accept aircraft tags until they have checked in on the receiving controller’s frequency. This procedure is standard practice across the vast majority of Europe and we are aligning our own procedures to match. We are aware that for UK controllers, changing this ingrained habit will not be easy.

Rather than require controllers to learn in which cases they must not accept the aircraft tag, we have taken this opportunity to produce and apply a simpler, universal policy. Although this is a relatively major change to the way a lot of us work within EuroScope, it should be easier to apply this uniformly, as opposed to only in specific instances.

Edited by Harry Sugden
Corrected date in title
  • Like 8
Link to post
Share on other sites
  • Harry Sugden changed the title to 2021-01-28 - Assuming of Aircraft Tags
  • Jack Edwards pinned this topic
  • Jack Edwards unpinned this topic
  • Similar Content

    • Jack Edwards
      By Jack Edwards
      Valid 17 June 2021
      PC Northeast, PC Southeast and PC West are incorporated as permanent secondary sectors and may therefore be staffed without adjacent control online (previously PC could only be split if the whole sector was covered).
      PC Northeast, PC Southeast (previously event only sectors) are incorporated into the 2021/06 version of the London FIR (EGTT) vMATS (Part 2) and may now be routinely staffed without specific approval (Temporary Instruction) from Operations.
       
      PC Northeast - MAN_NE_CTR (Relief MAN_EN_CTR)
      Frequency: 135.700 MHz
      RTF callsign: Scottish Control
      Coordination callsign: PC Northeast
      Top-down responsibility for: EGNT, EGNV, EGNM, EGNJ and EGCN
      PC Northeast is responsible for the northeastern portion of the PC East sector, handling traffic in the POL area and out towards the North Sea as shown in Figure 1 below. Their top-down responsibilities reflect the airspace of this sector in the absence of other controllers.
       
      PC Southeast - MAN_SE_CTR (Relief MAN_ES_CTR)
      Frequency: 134.425 MHz
      RTF callsign: Scottish Control
      Coordination callsign: PC Southeast
      Top-down responsibility for: EGCC
      PC Southeast is responsible for airspace up to FL195 in an area to the south of Manchester, as shown in Figure 2 below. This sector is primarily responsible for the streaming of inbounds and outbounds to/from Manchester via TNT and HON respectively, as well as Liverpool traffic via NANTI and East Midlands traffic via TNT.
      Note: After PC Bandbox, PC SE is covered top-down by AC North (not Lakes or North Sea). If AC North is not online then Lakes (LON_NW_CTR) covers it top-down. This is to allow PC SE to either be controlled top-down by the sector covering Lakes (i.e. LON_N_CTR or LON_NW_CTR online together with LON_NE_CTR) or the sector covering North Sea (LON_N_CTR and LON_NW_CTR online together).
       
      Coordination with Adjacent Units
      Coordination with adjacent sectors is described in the latest release of the London FIR (EGTT) vMATS Part II and Agreed Level Diagrams. There are no changes to existing agreements, but 3 new agreements are established between PC NE and PC SE.
      Manchester is the only airfield where the handoff order for departures is significantly changed. The handoff orders may be reviewed in the latest release of the Manchester (EGCC) Crib Sheet.
      The following airfields have departure handoff orders that include PC East or AC North (which are now split). The handoff orders are therefore modified as follows: 
      East Midlands (EGNX) -> PC SE before PC E, LNW after LN Birmingham (EGBB) -> PC SE before PC E, LNW after LN  
      Leeds (EGNM) -> PC NE before PC E, LNE before LN Newcastle (EGNT) -> PC NE before PC E, LNE before LN Teeside (EGNV) -> PC NE before PC E, LNE before LN Doncaster (EGCN) -> PC NE before PC E, LNE before LN Humberside (EGNJ) -> PC NE before PC E, LNE before LN  
      Liverpool (EGGP) -> LNW before LN Hawarden (EGNR) -> LNW before LN Ronaldsway (EGNS) -> LNW before LN Blackpool (EGNH) -> LNW before LN Warton (EGNO) -> LNW before LN Local aerodrome documentation will be updated to reflect these changes in due course.
       
      Figure 1 - PC Northeast - Area of Responsibility

      Figure 2 - PC Southeast - Area of Responsibility

    • Chad Byworth
      By Chad Byworth
      Effective 25 July 2021
      Following the release of the updated Birmingham vMATS Part 2 there has been a slight amendment to inbound release procedures (primarily via CHASE with the release point now specified at FL120 [previously FL100]) and new procedures have been introduced with AC West with regards to the Birmingham/Cotswold Flexible Use Airspace.
      There have been no changes to outbound agreements with AC Daventry (via ADMEX/COWLY/CPT/DTY/UNGAP/WCO) or PC South East (via LUVUM).
      This post documents these changes for AC controllers pending an update to the London vMATS Part 2.
       
      Inbound Releases
      Inbounds via CHASE
      Inbounds via CHASE will be transferred from PC South East to Birmingham RAD by means of the following silent transfer agreement:
      Via
      Standing Agreement
      Release Point
      CHASE
      Descending FL90
      Passing FL120
      Note 1: Traffic will be transferred level separated at CHASE with PC South East descending successive inbounds to FL90 when the prior inbound is observed to have vacated FL90. If this cannot be achieved, then PC South East is responsible for coordinating each inbound.
      Note 2: Birmingham RAD shall suspend the silent release procedure when holding at CHASE.
      Note 3: Restrictions for vectoring/descending inbounds via CHASE once passed FL120 are detailed below.
      Inbounds via HON to GROVE
      Inbounds via HON to GROVE will be transferred from AC Daventry to Birmingham RAD by means of the following silent transfer agreement:
      Via
      Standing Agreement
      Release Point
      HON
      FL90 level HON
      HON
      Note 1: Traffic will be transferred 10 NM in trail or greater, constant or increasing. If this cannot be achieved, then AC Daventry is responsible for coordinating each inbound.
      Note 2: Birmingham RAD shall suspend the silent release procedure when holding at GROVE at FL90 or above.
      Inbounds via BIFIN to GROVE
      Inbounds via BIFIN to GROVE will be transferred from AC West to Birmingham RAD by means of the following silent transfer agreement:
      Via
      Standing Agreement
      Release Point
      BIFIN
      FL130 level BIFIN
      GROVE
      Note 1: Traffic will be transferred 10 NM in trail or greater, constant or increasing. If this cannot be achieved, then AC West is responsible for coordinating each inbound.
      Note 2: Transfer of communication shall be after FIGZI but prior to BIFIN.
      Note 3: Birmingham RAD shall suspend the silent release procedure when holding at GROVE.
      Note 4: The silent transfer agreement is replaced with a reduced radar handover outside the hours of operations of Birmingham/Cotswold FUA – see below.
       
      Vectoring and Descent before Release Point
      Inbounds via CHASE
      Birmingham RAD may vector for right turns only and descend inbounds after passing FL120 when they ensure separation from Birmingham/Coventry outbounds – this is achieved when:
      There are no outbounds, or When outbounds are retained by Birmingham RAD until transferred clean to PC South East, or When outbounds under the control of PC South East are observed to climb above FL80 (PC South East is responsible for separation of all outbounds under its control cleared above FL80). Inbounds via CHASE which are turned right will be considered fully released upon entering the Birmingham Area of Responsibility or upon passing abeam CHASE, whichever sooner.
      Inbounds via BIFIN to GROVE
      Traffic is released for descent to FL80 on contact (subject to the base of controlled airspace) and released for turns after BIFIN subject to outbounds – Birmingham RAD is responsible for providing separation against outbound traffic previously transferred to AC West.
      Inbounds via HON to GROVE
      Runway 33 Operations
      Traffic is released for descent below FL90 and vectoring once west of the extended centreline. Additionally, when Birmingham RAD ensures 5 NM separation against all outbound Birmingham/Coventry traffic at or below FL90 then inbound traffic may be issued descent and turns up to 30° left of track upon entering Daventry CTA 9 (that section of the Daventry CTA north of DTY VOR).
      Runway 15 Operations
      Traffic is released for descent below FL90 and vectoring at HON.
      Additionally, when Birmingham RAD implements a departure check and there are no conflicting outbounds then traffic may be issued descent/turns to position for a left-hand downwind upon entering the lateral confines of Birmingham delegated airspace prior to HON.
      In the event there is conflicting traffic then Birmingham RAD must coordinate with AC Daventry.
       
      Birmingham and Cotswold Flexible Use Airspace
      Birmingham CTA 10 and Cotswold CTAs 15-18 are designated Flexible Use Airspace (FUA). These portions of airspace are established between 1700-0900 local Monday-Thursday and 1700 local Friday-0900 local Monday (extended to include public holidays). Outside of these hours the airspace reverts to Class G.
      Controllers should note that Delegated Area C includes Birmingham CTA 10, when established it exists FL65-FL105, outside the hours of operations the overlying Daventry CTA remains active with a base of FL105.
       
      Procedures outside FUA Hours of Operations
      Inbounds via BIFIN
      Outside the hours of operation of Birmingham/Cotswold Flexible Use Airspace inbounds via BIFIN will leave controlled airspace at FIGZI. AC West will continue to route inbounds via the FIGZI 1B STAR and will transfer inbounds descending to FL130 level BIFIN (to maintain consistency with the silent transfer agreement) but transferred by means of a reduced radar handover. AC West shall verbally coordinate the reduced radar handover with Birmingham RAD in the format:
      “BIFIN radar handover, [Callsign], [UK FIS type].”
      Note: If AC West initiates a transfer without conducting the verbal reduced radar handover then Birmingham RAD may assume the traffic is under a Deconfliction Service.
      Unless specified in the reduced radar handover, traffic is fully released on contact subject to outbounds routing to MOSUN  – Birmingham RAD is responsible for providing separation against outbound traffic previously transferred to AC West.
      It is the responsibility of AC West to initiate coordination with Birmingham RAD when unknown traffic in Class G airspace prevents AC West from achieving the standing agreement.
      Birmingham RAD will provide clearance to enter the Birmingham CTR/CTA and integrate the inbound into arrival stream/instruct the inbound to hold at GROVE as required.
      Outbounds to MOSUN
      Outside the hours of operation of Birmingham/Cotswold Flexible Use Airspace the N92 ATS route (LUXTO – OKTAD) is disestablished. Outbounds from Runway 33 will route via the UMLUX 1M SID then route direct MOSUN, outbounds from Runway 15 will fly the MOSUN 15 procedure. These outbounds will leave controlled airspace at the Birmingham CTA boundary and shall be provided a Deconfliction Service (reduced to a Traffic Service if workload or other factors prevent Birmingham RAD from applying a Deconfliction Service).
      Birmingham RAD shall transfer outbounds to AC West, either on own navigation MOSUN or a radar heading, climbing to FL120, by means of a reduced radar handover. RAD shall verbally coordinate the reduced radar handover with AC West in the format:
      “MOSUN radar handover, [Callsign], [UK FIS type].”
      Traffic is to be transferred once it is outside of controlled airspace and, unless specified by Birmingham RAD during the handover, outbounds are released for climb on contact (subject to AC Daventry controlled airspace). Birmingham RAD is responsible for providing separation against inbound traffic routing via BIFIN.
      Birmingham RAD is responsible for coordinating with AC West when unknown traffic in Class G airspace prevents RAD from achieving the standing agreement.
      Note: In the absence of AC West, RAD may provide a Deconfliction Service to 40 NM (ie. to MOSUN) from Birmingham (subject to workload).
       
      Documentation Status
      The updated Birmingham vMATS Part 2 incorporates these procedures.
      The London vMATS Part 2 will be amended at its next revision.
    • Chad Byworth
      By Chad Byworth
      Effective 15 July 2021
      Following a new obstacle survey the Heathrow (EGLL) and London City (EGLC) ATC Surveillance Minimum Altitude Charts (SMAC) have been amended to incorporate a 1900 ft restriction of 3 NM radius about an obstacle (843 ft AMSL) which is located in the north-eastern portion of the London CTR.
      Due to the levels involved this change will not impact on the control of flights following standard inbound/outbound procedures but should be considered when proving a service to low-level IFR traffic conducting non-standard flights within the London CTR.
      Documentation Status
      The Heathrow (EGLL) and London City (EGLC) & TC Thames vMATS Part 2(s) will be amended at their next revisions.
      The sector file has not yet been updated to incorporate this change.
    • Chad Byworth
      By Chad Byworth
      Effective 15 July 2021
      The Aldergrove Radar (INT) (EGAA_APP) frequency has been amended to 133.125 MHz.
      Documentation Status
      The Belfast/Aldergrove (EGAA) & Belfast/City (EGAC) Airfield Controller Brief and Scottish vMATS Part 2 will be amended at their next revisions.
    • Chad Byworth
      By Chad Byworth
      Effective 17 June 2021
      The following STARs have been re-designated following an amendment to the planning level at LELNA.
      STARs Re-designated
      GUR 1Y/Z → GUR 2Y/Z (no change to route).
      Note: There is an associated change to the planning level at LELNA - the agreed level between AC Worthing and Jersey Control will remain FL200 level 10 NM before LELNA until further notice.
      Documentation Status
      The London and Guernsey vMATS Part 2(s) will be amended at their next revisions.
×
×
  • Create New...