Jump to content

active 2020-06-18 Delegated Airspace between PC East and Sco East


Recommended Posts

Chris Pawley

Effective 18 June 2020

The delegated airspace between Sco East and PC East is expanded between FL255 and FL285 in the vicinity North and West of ERKUT to facilitate traffic on N110 and L602. The new sector diagrams are shown below:

 

PC East

O6hBptee7uMhKjuVofYQOB2-vcBsHffg9wm6qFRMMRsyXs4uwppBact31HR0r3xZNU-gadX-vsi0je0YVRjFqJ76YummZDQfnYkQhHrAKICHtJoVlgQ3evksnhDfU52bzwuj82_Z

Sco East

v1-9zHV_b2BlnksVvQRUe-Z5Iq_bJnvmTSPaFMZWKhGjn52un5blkuQgt8pLpeq93QfcNCOBApX9AWc-lToubDEZi49oxi_86cuP5WuVhfMX8Vt5yUIB9P4QV_wgBk0l6KdzU6JE

These changes are in the 2020/07 sector file and will be reflected in upcoming document releases. Thanks to @Harry Sugden for preparing these figures.

Link to post
Share on other sites
  • Similar Content

    • Chris Pawley
      By Chris Pawley
      For the Amsterdam <-> Liverpool/Manchester  event and in order to manage the increased workload in the PC West sector, the airspace may be split into two sectors.
      Positions
      MAN_WI_CTR (Relief MAN_W2_CTR)
      Frequency: 133.050 MHz
      RTF callsign: Scottish Control
      Coordination callsign: PC Isle of Man
      Top-down responsibility for: EGNS, EGNH, EGNO, EGNL
      PC Isle of Man is responsible for airspace up to FL285 in an area on the western part of the PC West sector as shown below. Their top-down responsibilities reflect the airspace of this sector (i.e. Blackpool and Isle of Man) in the absence of other controllers. This sector is primarily responsible for the interface with Dublin, positioning MTMA outbounds and Dublin TMA inbounds appropriately as well as handling Dublin outbounds and MTMA inbounds from the West.
       

       
      An agreed levels diagram for PC IOM here:  PC IoM.pdf
       
      MAN_W_CTR (Relief MAN_W__CTR)
      Frequency: 128.050 MHz
      RTF callsign: Scottish Control
      Coordination callsign: PC West
      Top-down responsibility for: EGGP, EGNR and PC Isle of Man
      PC West is responsible for its usual airspace, minus that of PC Isle of Man’s. The sector diagram below represents this airspace but is only valid for use when PC Wallasey is online. Their top-down responsibilities reflect the airspace of this sector in the absence of other controllers. This sector is responsible for PC West’s remaining functions, which for this event, will be focused on the presentation of traffic to Manchester and Liverpool approach.

      Coordination between PC West and PC Isle of Man
      Traffic Positioning
      PC West should position westbound traffic from EGCC, EGGP and EGNR on a heading north of WAL prior to transfer to PC Isle of Man. This traffic is RFT on transfer of communication to PC West.
      PC Isle of Man should position eastbound traffic inbound on a heading south of WAL prior to transfer of to PC West. This traffic is RFT on transfer of communication to PC West.
      If traffic is not operating in accordance with this guidance or is on a heading against traffic that is unknown to the receiving sector, then coordination must be effected.
      Aircraft inbound to the MTMA with an RFL below the Standing Agreement Level
      Traffic inbound to MTMA airfields cruising below the standing agreement level is RFD on transfer of communications from PC Isle of Man to PC West. Coordination must be effected if the aircraft is not RFD.
      Aircraft inbound to EGGP/EGNR from the northeast
      Controllers should be aware that there is no standing agreement for EGGP or EGNR arriving traffic via the TIPOD 1C, 1D or 1E arrivals between PC East and PC West. A level must be individually coordinated between the controllers responsible for these sectors, as it would need to be without this event split.
       
      Standing Agreements
      PC Isle of Man to PC West
      To
       
      Via
       
      Level
       
      EGCC
      L15, Q38
      L10, (U)L28
      FL170 lvl IBRAR. See Note.
      FL170 lvl PENIL. See Note.
      EGNM and EGCN
      L15, Q38
      FL170 lvl NOMSU. See Note.
      EGCC, EGNM and EGCN
       
       
      FL170 lvl MALUD. See Note.
      EGGP and EGNR
      L15, Q38
      L10, (U)L28
      FL130 lvl PENIL. See Note.
      EGGP and EGNR
      (U)L975, Q37
      FL130 lvl MALUD. See Note.
                      Note: Traffic should be positioned according to the conditions detailed above.
       
      PC West to PC Isle of Man
      From
       
      Via
       
      Level
       
      EGCC
      (U)L70, L10, M144, M145, M146
      Climbing FL160. See Note.
      EGGP and EGNR
      (U)L70, L10, M144, M145, M146
      Climbing FL120. See Note.
                      Note: Traffic should be positioned according to the conditions detailed above.
       
       
       
      PC East to PC West
      To
       
      Via
       
      Level
       
      Conditions
       
      EGGP and EGNR
      NANTI
      FL100 lvl NANTI
      RFD to MSL. See Note.
                      Note: When Manchester is landing 05L/R, PC East will vector traffic clear of the 05L/R RMA.
       
      PC West to PC East
      From
       
      To
       
      Via
       
      Level
       
      Conditions
       
       
       
      EGNM and EGCN
      (U)N864, (U)L975
      FL150 lvl 5NM before BARTN
      RFT and RFD to FL110
      EGGP and EGNR
       
       
      NANTI, POL, BARTN
      FL90
      See Notes.
      Note 1: When Manchester is landing 05L/R, PC Wallasey will vector traffic clear of the 05L/R RMA.
       
      Note 2: Traffic via the Daventry Corridor with an RFL200+ may be positioned by PC Wallasey towards VIDOK or the Honiley Radar Gate without coordination.
       
      AC West to PC West
      To
       
      Via
       
      Level
       
      EGCC, EGNH, EGNO, EGNM and EGCN
      N864
      FL200 lvl OKTEM to be FL190 or below by MONTY
      EGGP and EGNR
      N864
      FL200 lvl 10NM before OKTEM to be FL190 or below by MONTY
       
       
      PC West to AC West
      From
       
      Via
       
      Level
       
      MTMA
      N864
      Climbing FL190
       
       
      Coordination with Adjacent Units
      Airfields
      It is the responsibility of the PC Isle of Man controller (or PC Coordinator) to inform the following controllers when PC Isle of Man is split from PC West:
      Scottish Control Dublin Control Shannon Control PC East AC North PC East
      PC West/Wallasey controllers are reminded that there is no standing agreement for traffic via the TIPOD 1C, 1D or 1E STARs into EGGP or EGNR between PC East and PC Wallasey.
       


    • Chris Pawley
      By Chris Pawley
      For the Amsterdam <-> Liverpool/Manchester  event and in order to manage the increased workload in the PC East sector, the airspace may be split into two sectors.
      Positions
      MAN_S_CTR (Relief MAN_S__CTR)
      Frequency: 134.420 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. 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.
       

      MAN_E_CTR (Relief MAN_E__CTR)
      Frequency: 133.800 MHz
      RTF callsign: Scottish Control
      Coordination callsign: PC East
      Top-down responsibility for: EGNT, EGNM, EGNV,, EGNJ, EGCN and PC SouthEast
      PC West is responsible for its usual airspace, minus that of PC Southeast’s. The sector diagram below represents this airspace but is only valid for use when PC SouthEast is online. Their top-down responsibilities reflect the airspace of this sector in the absence of other controllers. This sector is responsible for PC West’s remaining functions, which for this event, will be focused on the presentation of traffic to Manchester approach via ROSUN.

      Coordination between PC West and PC Isle of Man
       
       
      Standing Agreements
      Intra PC East agreements
      PC SouthEast to PC East
      To
      Via
      Level
      EGNJ
      (U)N57, T420, (U)N601
      Descending FL180
      EGNM
      T420, (U)N601
      FL120 lvl 10 NM before DENBY or 25 NM before POL (See note 1)
      EGNJ and EGNO
       
      T420, (U)N601
      FL120 lvl 10 NM before DENBY or 25 NM before POL (See note 2)
      EGCN
      (U)N57, T420, (U)N601
      FL120 lvl EVSON (See note 2)
                          Note 1: Traffic should be positioned on a heading East of BULBI. Note 2: Traffic should be positioned on or East of EVSON-ADELU track
       
      PC SouthEast to PC East
      None
      Agreements Out of PC SouthEast
      PC West to PC SouthEast
      To
      Via
      Level
      Midlands Group
      MCT
      FL200 lvl MCT. See Note 1
      Midlands Group
      AMPIT
      FL200 level abeam NOKIN, 25 NM before CREWE See Note 2
                      Note 1: Traffic should be positioned over MCT unless coordinated with PC SouthEast, traffic must be FL190 or lower 10 NM south of MCT. Note 2: Traffic inbound to BB/NX above FL195 should file via AMPIT, agreement at CREWE remains only for incorrect flightplanning.
      From
      Via
      Level
      Conditions
      EGGP and EGNR
      NANTI
      Climbing FL90
      See notes
                      Note 1: When Manchester is landing 05L/R, PC West will vector traffic clear of the Manchester 05L/R RMA. Note 2: Traffic RFL200+ may be positioned by PC West towards VIDOK  or Honiley RADAR Gate without coordination
      AC Daventry to PC SouthEast
      To
      Via
      Level
      MTMA Group
       
      FL200 lvl ELVOS (See notes 1-3)
      FL200 lvl 10 NM before EMBOR (See notes 1-3)
      FL200 lvl 25 NM before TNT (See notes 1-3)
      EGNM, EGNH, EGNO
      T420/(U)N57
      FL200 lvl 10 NM before TNT
      EGNM, EGNH, EGNO
      (U)N601
      FL200 lvl EMBOR
      EGNJ, EGCN
      T420/(U)N57
      FL200 lvl 25 NM before EMBOR
                      Note 1: Traffic on a heading is not RFT. Note 2: PC SouthEast is to ensure that this traffic is descended to avoid PC West airspace, Note 3: AC Daventry is to coordinate with PC SouthEast and PC West in case traffic is unable to comply with the standing agreement. PC SouthEast is to subsequently ensure this traffic does not enter PC West.
      Agreements out of PC SouthEast
      PC SouthEast to PC West
      From
      Via
      Level
      Midlands Group
      WHI
      FL190 lvl 10 NM before abeam WHI
      Midlands Group
      POL
      FL200 level  25 NM before POL See Note 1
              Note : Traffic positioned East of PEDIG-POL
      To
      Via
      Level
      Conditions
      EGGP and EGNR
      NANTI
      FL100 lvl NANTI
      RFD to MSL See Note
            Note: When Runway 05L/R is in use at Manchester, PC West will vector clear of the Manchester 05L/R RMA
       
       
      PC SouthEast to AC Daventry
      From
       
      Via
       
      Level
       
      MTMA Group
       
      FL190 lvl 10 NM before HON
       
       
      Coordination with Adjacent Units
      Airfields
      It is the responsibility of the PC SouthEast controller (or PC Coordinator) to inform the following controllers when PC SouthEast is split from PC East:
      Manchester ATC Birmingham APC East Midlands ATC PC West AC Daventry  
       
      A PDF of these procedures is available here: PC_East_-_SE.pdf
       
      Thanks to @Harry Sugden for preparing these procedures.
       
    • Chris Pawley
      By Chris Pawley
      For this today's Amsterdam <=> Liverpool/Manchester event, in order to manage the increased workload in  the North sector group, a temporary arrangement is made to allow for the split of the London North sector.
      LON_N_CTR (AC North)
      West may be split into 2 positions: AC North (133.700) and AC North Sea (128.125). AC North remains the parent sector under the rules determining opening order and controller priority.

      LON_N_CTR / 133.700 MHz
      RTF callsign: London Control
      Coordination callsign: AC Lakes
      Top-down responsibility for: EGCC, EGGP, EGNM, EGNS, EGNT, EGNJ
      AC Lakes is responsible for airspace West of a line passing approximately GOLES-NAPEX as shown above. Their top-down responsibilities reflect the airspace of this sector (i.e. Manchester, Liverpool, etc.) in the absence of other controllers.
       
      LON_NE_CTR / 128.125 MHz
      RTF callsign: London Control
      Coordination callsign: AC North Sea
      Top-down responsibility for: EGSH
      AC North Sea is responsible for airspace East of a line passing approximately GOLES-NAPEX as shown above. Their top-down responsibilties reflect their airspace (i.e. Norwich) in the absence of other controllers.
       
      This procedure does not alter the staffing permissions as defined in the UK Division Policy or GRP.
      Chris.
    • Chris Pawley
      By Chris Pawley
      With the publishing of the newest version of the London (EGTT) vMATS, there is a deviation between the documented procedures for inbounds to Birmingham (EGBB). To resolve this conflict we summarise here the current procedures for Birmingham (EGBB) inbounds.
       
      Traffic via GROVE1A/1C is transferred by AC Daventry to Birmingham descending to FL90, 10 NM in trail and coordinated where this is not possible.
      Traffic via CHASE is transferred by PC East to Birmingham descending to FL90 and should be level seperated at CHASE and coordinated where this is not possible.
       
      When holding begins at either GROVE above FL90 or CHASE, coordination should take place between the relevant enroute sector and the approach sector to ensure the suspension of these procedures and coordination of appropriate levels can begin.
      Runway 33
      Inbounds via GROVE1A/1C
      Traffic may be turned left by up to 30 degrees and descended below FL90 so long as:
      Traffic is in Daventry CTA 9 (North of DTY) and is 5NM laterally seperated from any Birmingham/Coventry outbounds until they are above FL90 Inbounds via CHASE
      Traffic may be turned and descended below FL90 when they are below 1000ft above the release level or below and seperation is ensured against outbounds. This can be achieved when (for example):-
      Birmingham Approach works the outbounds to ensure seperation There are no outbounds PC East is working the outbounds, is in contact with them and has issued a climb above FL80 Runway 15
      Inbounds via GROVE1A/1C
      Traffic may be turned and descended below FL90 when passing HON. This can also occur within the delegated airspace when there are no departures.
      Inbounds via CHASE
      Traffic arriving from the West of CHASE (CHASE3A/1C/2D) may be turned and descended when they pass the release point (1000ft above the release level) so long as they do not pass East of the extended centerline.
      For all other arrivals, traffic may be turned and descended below FL90 when they pass the release point (1000ft above the release level) and seperation is ensured against outbounds. This can be achieved when (for example):-
      Birmingham Approach works the outbounds to ensure seperation There are no outbounds PC East is working the outbounds, is in contact with them and has issued a climb above FL80
    • Chris Pawley
      By Chris Pawley
      Effective 16 July 2020
       
      In the absence of Cardiff Radar, the agreements between AC West and Bristol Approach are amended. This allows Bristol (with theoretically more ability to focus on the local situation) the ability to manage conflicts and alleviate workload from AC West.
       
      Arrivals
      Traffic from the East in unaffected, the existing agreement is retained.
      Other traffic should be on it's STAR routing ultimately going to the BRI, clean of traffic unknown to Bristol and transferred as soon as practical. On transfer it is RFD and RFT.
      Traffic on a BRI1A and BRI1B is transferred to Bristol APC descending to FL110 Traffic on a BRI2D arrival is transferred to Bristol APC descending to FL100 AC West will ensure separation from inbounds at their release level but Bristol must ensure separation against Bristol departures after descending or turning inbound traffic.
       
      The next release of the EGTT vMATS Part 2 will contain these procedures, the Bristol vMATS contains these procedures already.
×
×
  • Create New...