Jump to content
Sign in to follow this  
Chris Pawley

active 2019-01-03 Agreements in TC North East

Recommended Posts

Chris Pawley

Effective 03 January 2019

Due to the implimentation of the TC VATON airspace on VATSIM - our current sectors and agreements do not allow the full flexibility of the airspace to be exploited by TC North East. We therefore have changes some agreements between sectors.

image.png.916d149a9ad0202d82f8780439e34759.png

 

Currently, two agreements exist in the South-West corner of this sector which can cause problems for the controller of TC North East.

  • AC Worthing->TC North East : Essex inbounds are routing VATON->BPK descending FL140 level BPK
  • TC South East -> AC Worthing : Gatwick outbounds are on a heading West of LAM, towards HEMEL climbing FL130 to FL190 (unknown to TC North East) - FL130 must be achieved by the TC South East/TC North East boundary.

We considered changing the boundary between AC Worthing and TC North East here, but found it would limit the controller further (especially when climbing Heathrow outbounds via Brookman's Park)

New Agreements

  • Essex inbounds will be handed from AC Worthing to TC North East descending FL160 (no level by point, but approx VATON)

This agreement will be shown with a down arrow to indicating descending, no level by

image.png.1c13284cf7d3f4970e58f97b6eba52dd.png

  • TC South East-> AC Worthing : Agreement does not change, traffic needs to climb such that it crosses the TC South East/TC North East boundary at or FL130 (as currently)
  • AC Worthing will ensure this traffic climbs FL155 or higher before a line parrallel to the North edge of the London CTA and hand to AC Daventry climbing FL190.

See below a schematic for the relative positions and level by points:

 

image.png.6419b77597401217911820125c0b7ea6.png

We have implimented the new agreement in the UK Sector File and will provide new agreed level diagrams as soon as is practicable.

 

Thanks to @Harry Sugden for preparing the graphics for these changes.

Edited by Chris Pawley

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Similar Content

    • Chris Pawley
      By Chris Pawley
      Effective 25/05/2017
       
      Updated agreement between Manchester TC East Sector and AC North:
       
      Manchester Group, Midlands Group, Barton, Leeds, Blackpool, Warton, Newcastle, Durham Tees Valley  outbounds via AMVEL should be handed to AC North climbing to FL270 FL280
      Manchester/Barton/Leeds/Blackpool inbounds via OTBED should be handed to Manchester TC East level FL280 FL290 (level by/abeam OTBED)
       
      The UK Sector File has been updated with these changes, a new version of the agreed levels diagram will be released in a future cycle.
    • Chris Pawley
      By Chris Pawley
      Effective 03 January 2019
       
      Redhill Information will be broadcast on 125.305MHz instead of 125.300 MHz. Due to 8.33KHz restrictions, we are unable to replicate this change, so we will retain the old frequency.
       
      A note will be added to relevant documentation to ensure no future confusion arises relating to these changes.
    • Chris Pawley
      By Chris Pawley
      Effective 08 November 2018
       
      The following frequencies are amended or converted to 8.33 kHz spacing:
      Jersey Zone 125.200 becomes 125.205 due to 8.33 kHz spacing restrictions, we are unable to replicate this. Therefore the existing frequency is retained as it is the closest usable frequency.
      Jersey Zone (SKERY) 120.450 becomes 120.455 due to 8.33 kHz spacing restrictions, we are unable to replicate this. Therefore the existing frequency is retained as it is the closest usable frequency. 120.450 retained in AIRAC 2019/01
      Jersey APP 120.300 becomes 120.305 due to 8.33 kHz spacing restrictions, we are unable to replicate this. Therefore the existing frequency is retained as it is the closest usable frequency.
      Jersey RAD 118.550 becomes 118.555 due to 8.33 kHz spacing restrictions, we are unable to replicate this. Therefore the existing frequency is retained as it is the closest usable frequency.
      Jersey TWR 119.450 becomes 119.455 due to 8.33 kHz spacing restrictions, we are unable to replicate this. Therefore the existing frequency is retained as it is the closest usable frequency.
      Jersey ATIS 134.675 becomes 134.680 due to 8.33 kHz spacing restrictions, we are unable to replicate this. Therefore the existing frequency is retained as it is the closest usable frequency.
      Jersey and Channel Islands Documentation is slated for update in a coming AIRAC cycle to reflect these changes.
    • Chris Pawley
      By Chris Pawley
      Effective 06 December 18
       
      From the effective date a frequency monitoring code is established at Edinburgh. Those pilots tuned to 121.200 may squawk 0440 when outside the Edinburgh CTA/CTR and not in reciept of an flight information service or when no other code is provided my air traffic control when recieving a service. Controllers are informed that this code may not be used to validate or verify aircraft as it may be used by mutliple aircraft.
       
      Edinburgh documentation will be updated in a future update to detail these changes.
    • Chris Pawley
      By Chris Pawley
      Effective 06 December 18
       
      From the effective date a frequency monitoring code is established at London/City. Those pilots tuned to 132.700 may squawk 0012 when outside the London CTR and the London/City CTA/CTR and not in reciept of an flight information service or when no other code is provided my air traffic control when recieving a service. Controllers are informed that this code may not be used to validate or verify aircraft as it may be used by mutliple aircraft.
       
      London/City documentation will be updated in a future update to detail these changes.
×