Jump to content
Sign in to follow this  
Chris Pawley

active 2018-12-06 London/Gatwick (EGKK) STARs updated

Recommended Posts

Chris Pawley

Effective 06 December 18

 

TIMBA3F STAR is redesignated KONAN1G in line with ICAO standard format.

TIMBA1K STAR is redesignated TEBRA1G in line with ICAO standard format.

There is no change to routing.

TIMBA1J STAR with withdrawn

 

 

The Sector File version 2018/13 contains these changes; other documentation will be updated in a coming cycle.

Share this post


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

  • Similar Content

    • Chris Pawley
      By Chris Pawley
      Effective 31 January 2019
       
      The following frequencies are updated at Belfast/City
       
      Belfast/City Tower 122.820 becomes 122.830 - however due to the inability to simulate 8.33 kHz frequencies - we will retain the existing frequency
      Belfast/City Information 136.620 becomes 124.580 - however due to inability to simulate 8.33kHz frequencies - we will use 124.570
       
      The UK Sector File is updated per 2019/02. Other resources will be updated in a future AIRAC cycle.
    • Chris Pawley
      By Chris Pawley
      Effective 31 January 2019
       
      The following frequencies are updated at Belfast/Aldergrove
       
      Belfast/Aldergrove Ground 121.750 becomes 121.755  - however due to the inability to simulate 8.33 kHz frequencies - we will retain the existing frequency
      Belfast/Aldergrove Radar 120.900 becomes 120.905 - however due to the inability to simulate 8.33 kHz frequencies - we will retain the existing frequency
      Belfast/Aldergrove Information 128.200 becomes 126.130 - however due to inability to simulate 8.33kHz frequencies - we will use 126.120
       
      The UK Sector File is updated per 2019/02. Other resources will be updated in a future AIRAC cycle.
    • Harry Sugden
      By Harry Sugden
      Hi all, particularly those who control Gatwick,
      I have been on London a few times in the last weeks where controllers have asked pilots if they are able to accept the new NOVMA departure which replaced both the conventional and RNAV KENET SIDs from runway 26L. Can I please ask that if they are unable (due to an out of date AIRAC), that you do not then route aircraft via SAM SIDs instead, as having filed a KENET, this take them in a completely different direction? If they only have the old KENET for 26L, KENET is fine.
      08R is of course a different story, since KENET conventional SIDs still exist, but not the RNAV (#KENET1Z). So if someone has the IMVUR1Z departure, this has preference over both the old KENET and SAM SIDs. If they do not have the IMVUR departure, please clear on either KENET or SAM.
      There have also been some changes to CLN->FRANE too.
      May I also suggest that if the SID is no longer published on charts, it might be pertinent to remind the pilot of the initial climb restriction for the old SID? (It will be the same as the new one)
      In sum:
      Filed Routing
      Active Runway
      New Routing
      New SID
      New SID not available (i.e. not updated AIRAC)? Leave route as filed, then clear on…
      CLN
      26L
      CLN DCT LEDBO M604... becomes ->
                   FRANE M604...
      CLN L620 REDFA... becomes ->
                   FRANE M604 GASBA M197 REDFA...
      CLN P44 SOMVA... becomes ->
                   FRANE M604 PAAVO Q295 SOMVA...
      FRANE1X
      CLN9M
      08R
      FRANE1Z
      CLN5P
      KENET
      26L
      NOVMA L620 NIBDA N14 KENET
      NOVMA1X
      #KENET2M*
      08R
      IMVUR N63 VOUGA N14 KENET
      IMVUR1Z
      KENET3P
      SAM
      26L
      NOVMA L620 SAM
      NOVMA1X
      #SAM2M **
      08R
      IMVUR N63 SAM
      IMVUR1Z
      SAM3P
      * old SIDs will be prefixed with a # in EuroScope
      ** currently SAM 2M in the sector file, expect #SAM 2M by 2019/03 release
      Thanks
    • 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 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.

       
      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

      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:
       

      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.
×
×
  • Create New...