Jump to content
Chris Pawley

[Trial] 2017-11-09 LTC_CTR

Recommended Posts

Chris Pawley

Effective 2017-11-09

Trial procedures for a total of 3 AIRAC cycles (84 days). Trial ends 2359z 01 February 2018

 

From the effective date, until the end of the trial, a temporary position will exist:-

Callsign: LTC_CTR

Frequency:  124.920

RTF Callsign: "London Control"

Coordination Callsign: "TC Bandbox"

 

In order to open this position, both of the parent sectors (AC South and AC Central) must be online (in any form; via a bandbox is permitted)

This position is a bandbox of LTC_N_CTR and LTC_S_CTR. Where either of these positions (or their sub-sectors) are online, they will resume responsibilities for their respective pieces of airspace.

 

 

Changes to top-down priorities

 

Who to Call

If there are no aerodrome or approach services at your departure aerodrome, use this list to determine which area sector to call. Contact the first controller listed that is online. If in doubt, don't be afraid to ask. Another good place to check is the controller information, where information is usually displayed as to which areas the controller is covering.

EGSS / EGGW
LTC_NW, LTC_N, LTC, LON_C, LON

EGLL / EGLC / EGKB
LTC_SE, LTC_S, LTC, LON_D, LON_S, LON

EGKK
LTC_SW, LTC_S, LTC, LON_S, LON

 

Changes to handoff procedures

Read from Left to Right, hand off to the first online station

EGKK

BIG/CLN/DVR/ADMAG/ODVIK

LTC_SE, LTC_S, LTC, LON_S, LON_SC, LON, KKAPP

BOGNA/HARDY/KENET/SAM/SFD (26L)

LTC_SW, LTC_S, LTC, LON_S, LON_SC, LON, KKAPP

 

EGLL

WOBUN/BUZAD

LTC_NW, LTC_N, LTC, LON_C, LON_SC, LON, LL_N_APP

BPK

LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, LL_N_APP

DET

LTC_SE, LTC_S, LTC, LON_S, LON_SC, LON, LL_N_APP

MID/SAM/GOGSI/GAGSU/CPT (27)

LTC_SW, LTC_S, LTC, LON_S, LON_SC, LON, LL_N_APP

 

EGLC

BPK/CPT  (09)

LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, THAMES

Others as per the top-down coverage order for Thames

 

EGSS

BPK/UTAVA/NUGBO

ESSEX, LTC_NW, LTC_N, LTC, LON_C, LON_SC, LON

CLN/LYD/DET/LAM

LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, LL_N_APP (LAM only), ESSEX

 

EGGW

OLNEY/CPT

RWY 26

LTC_NW, LTC_N, LTC, LTC_E, LON_C, LON_SC, LON, ESSEX, GW_APP

RWY 08

GW_APP,  ESSEX, LTC_NW, LTC_N, LTC, LTC_E, LON_C, LON_SC, LON

MATCH/DET

LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, ESSEX, GW_APP

 

 

Purpose of Trial

The purpose of the trial is to evaluate the effectiveness of this bandboxed position to fulfill some of the operational requirements of the division. At the end of the trial period, pilot and controller feedback will be gathered and analysed, as well as statistics regarding the manning of this position.

 

If it is deemed beneficial to establish this as a permanent sector - this will be completed in 2018.

 

The data necessary for this trial will be introduced in the sector file release for 2017/12 (on 9th November 2017) - updating your sector file is therefore essential to ensure there is a seemless introduction of these new procedures.

 

Chris.

Edit: 2017-11-07 - handoff order for EGLL/EGLC corrected (due to copy/paste error)

Edited by Chris Pawley
Updated EGSS/EGGW Handoff orders

Share this post


Link to post
Share on other sites
Oliver Gates
2 hours ago, Chris Pawley said:

EGLL

WOBUN/BUZAD

LTC_NW, LTC_N, LTC, LON_C, LON_SC, LON, KKAPP

BPK

LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, KKAPP

DET

LTC_SE, LTC_S, LTC, LON_S, LON_SC, LON, KKAPP

MID/SAM/GOGSI/GAGSU/CPT (27)

LTC_SW, LTC_S, LTC, LON_S, LON_SC, LON, KKAPP

 

EGLC

BPK/CPT  (09)

LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, KKAPP

Others as per the top-down coverage order for Thames

KK_APP for LL and LC?

Share this post


Link to post
Share on other sites
Chris Pawley

Fixed, thanks for flagging.

Share this post


Link to post
Share on other sites
Samuel James

Can I also just remind KK_GND controllers that the above handoff order listed above is for once the aircraft has taken off - if KK_APP and LTC_CTR are online, KK_APP still controls the runway so handoff to APP to issue takeoff clearances. Otherwise if APP isn't online then the handoff order above is correct.

Share this post


Link to post
Share on other sites
Chris Pawley

From AIRAC Cycle 2018/02 the Euroscope Designator for LTC_CTR will change from T to TC

Share this post


Link to post
Share on other sites
Harry Sugden

Out of interest, was this position made permanent?

Share this post


Link to post
Share on other sites
Oliver Parker

It's just been rostered for an event tomorrow evening so I presume it's being used permanently.

And so it should, the position is useful. 

Share this post


Link to post
Share on other sites
Adam Turner

Are the handoffs at Luton meant to be GW_APP (GW INT), SS_APP (SS FIN), ESSEX (SS INT) or should it go straight from GW_APP to ESSEX?  

Share this post


Link to post
Share on other sites
Chris Pawley

Adam,

 

I am not sure why I added SSFIN into the handoff orders, I cannot find the document to support this information. I've corrected this to reflect the order in the current Essex documentation.


Chris.

Edited by Chris Pawley

Share this post


Link to post
Share on other sites
Chris Pawley

This trial is now concluded.

 

The position is perminently added to the sector file and to our procedures.

 

A backdated announcement is located here:

Edited by Chris Pawley

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

  • Similar Content

    • 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.
    • Chris Pawley
      By Chris Pawley
      Effective 6 December 2018
       
      Airspace Deployment 4 is a redesign of the Dutch interface with AC Clacton. The previous design provided a single routing into the London airspace, regardless of destination. The new design expands the number of airways for inbounds to three, with specific purposes for each. This is part of the Swanwick Airspace Improvement Programme (SAIP).
       
      An overview for the new flow is given below:

      The Northerly airway (at NOGRO) accepts all Essex inbounds as well as overflights from the NE
      The middle airway (at ABNED) accepts all EHAM outbounds (except those going to Essex), all EGLL inbounds
      The Southerly airway (at GALSO) accepts all EGKK/EGLC inbounds as well as overflights from the SE
       
      New RNAV 1 STARs are introduced for Heathrow, Gatwick, Thames, Essex and Southend
      Note these STARs are named following the ICAO standards, after the first waypoint rather than the last waypoint as is typical in the UK.
      New SIDs are introduced for Gatwick outbounds
      Airspace in the vicinity of CLN is redesigned also, with new routings for some aircraft which avoids the CLN VOR.
      Agreements at GORLO are revised for these changes
      The REFSO delegated area becomes the IBNOS delegates areas and has expanded slightly (shown below together with the SASKI area):
       

      There are new agreed levels diagrams to support these changes, we are (re) negotiating the text for a new LoA with the Dutch vACC.

      Thanks to @Sebastian Rekdal for preparing the graphics for these changes
    • Chris Pawley
      By Chris Pawley
      Effective 6 December 2018
       
      Airspace Deployment 3 is a redesign of (Real world) London AC Sector 21 (AC Worthing on VATSIM), with new routings for traffc outbound from Solent airfields, and new procedures for traffic inbound and outbound from the Channel Islands via the North-East interface with London. This is part of the Swanwick Airspace Improvement Programme (SAIP). The majority of these changes are made to reduce complexity in this sector.
      An overview for the new flow is given below:
       
      (Note the majority of the lines at ORTAC are old RNAV5 specification routes, so alternatives are available for most flights)

       
      A number of new RNAV 1 Airways are introduced between SAM/GWC and the FIR boundary with France.
      New RNAV 1 STARs are introduced for Solent Inbounds
      Note these STARs are named following the ICAO standards, after the first waypoint rather than the last waypoint as is typical in the UK.
      New SIDs are introduced for Guernsey and Jersey
      Agreements at ORTAC are extended to LELNA for Southbound traffic and ORIST for Northbound traffic
      There are new agreed levels diagrams to support these changes.

      Thanks to @Sebastian Rekdal for preparing the graphics for these changes
    • Chris Pawley
      By Chris Pawley
      Effective 01 February 2018
      From the effective date,  the position of TC Bandbox is introduced.
      Callsign: LTC_CTR
      Frequency:  124.920
      RTF Callsign: "London Control"
      Coordination Callsign: "TC Bandbox"
       
      In order to open this position, both of the parent sectors (AC South and AC Central) must be online (in any form; via a bandbox is permitted)
      This position is a bandbox of LTC_N_CTR and LTC_S_CTR. Where either of these positions (or their sub-sectors) are online, they will resume responsibilities for their respective pieces of airspace.
       
       
      Changes to top-down priorities
       
      Who to Call
      If there are no aerodrome or approach services at your departure aerodrome, use this list to determine which area sector to call. Contact the first controller listed that is online. If in doubt, don't be afraid to ask. Another good place to check is the controller information, where information is usually displayed as to which areas the controller is covering.
      EGSS / EGGW
      LTC_NW, LTC_N, LTC, LON_C, LON
      EGLL / EGLC / EGKB
      LTC_SE, LTC_S, LTC, LON_D, LON_S, LON
      EGKK
      LTC_SW, LTC_S, LTC, LON_S, LON
       
      Changes to handoff procedures
      Read from Left to Right, hand off to the first online station
      EGKK
      BIG/CLN/DVR/ADMAG/ODVIK
      LTC_SE, LTC_S, LTC, LON_S, LON_SC, LON, KKAPP
      BOGNA/HARDY/KENET/SAM/SFD (26L)
      LTC_SW, LTC_S, LTC, LON_S, LON_SC, LON, KKAPP
       
      EGLL
      WOBUN/BUZAD
      LTC_NW, LTC_N, LTC, LON_C, LON_SC, LON, LL_N_APP
      BPK
      LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, LL_N_APP
      DET
      LTC_SE, LTC_S, LTC, LON_S, LON_SC, LON, LL_N_APP
      MID/SAM/GOGSI/GAGSU/CPT (27)
      LTC_SW, LTC_S, LTC, LON_S, LON_SC, LON, LL_N_APP
       
      EGLC
      BPK/CPT  (09)
      LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, THAMES
      Others as per the top-down coverage order for Thames
       
      EGSS
      BPK/UTAVA/NUGBO
      ESSEX, LTC_NW, LTC_N, LTC, LON_C, LON_SC, LON
      CLN/LYD/DET/LAM
      LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, LL_N_APP (LAM only), ESSEX
       
      EGGW
      OLNEY/CPT
      RWY 26
      LTC_NW, LTC_N, LTC, LTC_E, LON_C, LON_SC, LON, ESSEX, GW_APP
      RWY 08
      GW_APP,  ESSEX, LTC_NW, LTC_N, LTC, LTC_E, LON_C, LON_SC, LON
      MATCH/DET
      LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, ESSEX, GW_APP
       
       
      The data necessary for this trial was introduced in the sector file release for 2017/12 (on 9th November 2017) - updating your sector file is therefore essential to ensure there is a seemless introduction of these new procedures.
       
      There is quite alot of documentation still to be incorperated into this update, but this will be conducted as time permits.
       
      Chris.
×