Forums

Valid 26 April 2025 for the duration of the Cross the Pond roster A temporary arrangement is permitted to open ScAC Low during Cross the Pond to alleviate the workload of Scottish upper controllers handling enroute CTP traffic. Any errors in procedures should be reported to the Operations department via the Helpdesk or Discord. Available Position(s) ScAC Low - SCO_L_CTR (Relief: SCO_L__CTR) Frequency: 124.500 MHz RTF callsign: Scottish Control Coordination callsign: Scottish Low Top-down responsibility for: Antrim, ScTMA Talla & Galloway, and all airfields listed in Scottish FIR (EGPX) vMATS Part 2 Chapter 6 Scottish Low is responsible for airspace below FL255 in most of the Scottish AoR as shown in Figure 1 and described below, as well as all top-down provision. Rathlin airspace below FL255 ScAC West airspace below FL255 ScAC North airspace below FL255 The area west of (and including) the P18 (Tay & Borders) CTA complex, south of ADN and north of ERKIT-TENDO, below FL255. Coordination with Adjacent Sectors & Units Standing Agreements Agreements between Antrim, Talla and Galloway and upper/external sectors are unaffected. In general: agreements for outbounds of (climbing) FL250 will be from ScAC Low to the applicable upper sector, and agreements for inbounds of (descending) FL260 will be from the applicable upper sector to ScAC Low. e.g. ScTMA inbounds via ADN - instead of ScAC North to ScAC South, these would be FL260 level ADN from ScAC North to ScAC Low. Splitting Procedure The following sectors and units should be informed when ScAC Low is opened: All ScAC Sectors MPC Northeast MPC West Newcastle ATC All affected Scottish airfield ATC Shannon Low Dublin ACC Figure 1 - ScAC Low Area of Responsibility Notes: ___ Red solid lines indicate areas where the vertical boundaries for ScAC Low differ - - Red dashed lines indicate boundaries between upper sectors, but there is no change of vertical sectorisation for ScAC Low Antrim, Talla and Galloway AoRs are shown in different colours This procedure does not alter the staffing permissions as defined in the UK Division Policy or GCAP.

Valid 26 April 2025 for the duration of the Cross the Pond roster A temporary arrangement is permitted to split ScAC North during the Cross the Pond. Additionally, the Hebrides sector within ScAC North may be combined with the ScAC West (Central) sector. To avoid confusion for pilots and controllers we plan to only open this sector with a Scottish Low also online. However, these sectors can be opened independently. Any errors in procedures should be reported to the Operations department via the Helpdesk or Discord. Available Position(s) ScAC Hebrides - SCO_EH_CTR (Relief: SCO_EH__CTR) Frequency: 133.680 MHz RTF callsign: Scottish Control Coordination callsign: Scottish Hebrides Top-down responsibility for: Stornoway (EGPO) This sector controls only the "Hebrides" portion of the airspace depicted below. ScAC Hebrides-Central - SCO_HC_CTR (Relief: SCO_HC__CTR) Frequency: 128.675 MHz RTF callsign: Scottish Control Coordination callsign: Scottish Hebrides-Central Top-down responsibility for: Hebrides and Central top-down This sector controls the "Hebrides" and "Central" portions of the airspace depicted below. It has priority for the Central airspace from ScAC West or ScAC West-Deancross. Coordination with Adjacent Sectors & Units Standing Agreements Standing agreements to aerodromes still exist (EGPE and EGPF) when ScAC Low is offline. However, there are otherwise no standing agreements for these sectors. Splitting Procedure The following sectors should be informed when this position is opened: Shannon NOTA (Upper and Super) ScAC North ScAC West/Rathlin ScAC Deancross Antrim, ScTMA or ScAC Low Reykjavik East sectors (all levels) Affected airfields, if Low is offline Figure 1 - ScAC Hebrides and Central sectors - whilst ScAC Low is online Figure 2 - ScAC Hebrides and Central sectors - whilst ScAC Low offline This procedure does not alter the staffing permissions as defined in the UK Division Policy or GCAP.

Valid 26 April 2025 for the duration of the Cross the Pond roster A temporary arrangement is permitted to split TC East during the Cross the Pond. This TI must be read in conjunction with the Temporary Instruction 2025-04-26 - [Enroute] LAC Clacton - Splitting Procedures as the TC East airspace is also divided when the upper Clacton split is used. Any errors in procedures should be reported to the Operations department via the Helpdesk or Discord. The diagrams are slightly outdated as they do not reflect the changes at the interface with North Sea (EFMIH and AMFEP). Sectors The TC East group consists of 2 sectors, as shown in Figure 1 at the end of this post. TC REDFA (north side) Covers the northern part of TC East (real world TC REDFA & TC DAGGA sectors) as shown in Figure 1, handling a majority eastbound traffic flow. This sector is responsible for inbounds to EGLC/KB via ODVOD, Essex Group inbounds from IDESI and MEGEL, and LTMA departures to the east and via EFMIH. This sector has top-down responsibility for TC North East in their absence except the airspace belonging to TC Lambourne (FL175-), but no top-down responsibility of airfields. TC SABER (south side) Covers the southern part of TC East (real world TC JACKO & TC SABER sectors) as shown in Figure 2, handling a majority westbound traffic flow. This sector is responsible for inbounds to the London TMA from Brussels, Amsterdam and BARMI. This sector has top-down responsibility for the TC Lambourne AoR (FL175-) in their absence, but no top-down responsibility of airfields. Positions There are two positions available for use. TC REDFA - LTC_ER_CTR (Relief: LTC_ER__CTR) Frequency: 133.525 MHz RTF callsign: London Control Coordination callsign: TC REDFA Top-down responsibility for: TC North East (excluding TC LAM FL175-) TC SABER - LTC_ES_CTR (Relief: LTC_ES__CTR) Frequency: 129.605 MHz RTF callsign: London Control Coordination callsign: TC SABER Top-down responsibility for: TC LAM only (FL175-) Agreed Levels A TC East Split Agreed Levels Diagram is available at the link below. OUTDATED 🗺️TC East (REDFA+SABER) Agreed Levels Diagram Coordination with Adjacent Sectors & Units It is the responsibility of the TC SABER/REDFA controller (or London Coordinator) to inform the following controllers when TC SABER/REDFA are split from TC East/AC Clacton: TC North East AC Clacton TC South East Southend/Thames AC Worthing AC Dover Amsterdam ACC Brussels ACC Figure 1 - TC REDFA - Area of Responsibility Figure 2 - TC SABER - Area of Responsibility This procedure does not alter the staffing permissions as defined in the UK Division Policy or GCAP.

Valid 26 April 2025 for the duration of the Cross the Pond roster A temporary arrangement is permitted to split LAC Clacton during the Cross the Pond. Clacton North and Clacton South are permitted to be opened with or without AC Clacton or Central for the duration of CTP. This TI must be read in conjunction with the Temporary Instruction 2025-04-26 - [Enroute] TC East - Splitting Procedures as the TC East airspace is also divided when the upper Clacton split is used. Any errors in procedures should be reported to the Operations department via the Helpdesk or Discord. The diagrams are slightly outdated as they do not reflect the changes at the interface with North Sea (EFMIH and AMFEP). Available Position(s) Clacton North - LON_EN_CTR (Relief: LON_EN__CTR) Frequency: 133.925 MHz RTF callsign: London Control Coordination callsign: Sector 12 Top-down responsibility for: TC REDFA (north half of TC East) Clacton North (Sector 12) handles almost exclusively Eastbound traffic, leaving the FIR at SOMVA, REDFA and entering North Sea at EFMIH. Some Westbound traffic is handled in the form of Essex inbounds via AMFEP-MEGEL. Clacton South - LON_ES_CTR (Relief: LON_ES__CTR) Frequency: 128.150 MHz RTF callsign: London Control Coordination callsign: Sector 13 Top-down responsibility for: TC SABER (south half of TC East) Clacton South (Sectors 13+14) handles Westbound traffic entering the FIR via the delegated areas and from North Sea at BARMI. Note: Clacton South's responsibilities change depending on who else is online: LON_EN_CTR + LON_ES_CTR online, LON_ES_CTR is responsible for both Sector 13 and Sector 14. LON_C_CTR + LON_ES_CTR online, Clacton South is responsible for both Sector 13 and Sector 14. <- Note: This is the expected configuration for CTP. LON_E_CTR + LON_ES_CTR online, LON_ES_CTR is responsible for Sector 13 only. Agreed Levels A Clacton Split Agreed Levels Diagram is available at the link below. OUTDATED 🗺️LAC Clacton (S12+S13+S14) Agreed Levels Diagram Coordination with Adjacent Sectors & Units The following sectors should be informed when Clacton splits are opened: AC North Sea AC Daventry AC Dover and LUS TC East Amsterdam/MUAC DELTA Brussels/MUAC KOKSY All neighbouring units should be aware of these positions and their functions. Traffic inbound to LTMA via BARMI will be transferred from AC North to Sector 13 / 14, and transits Sector 12 at the agreed level at BARMI (i.e. FL300 for EGLL and FL260 for EGKK). Traffic is not RFD/RFT in Sector 12 without coordination. Traffic inbound to EGLL below FL290 will be transferred to Sector 14 in the delegated area. If Sector 13 and 14 are split, this traffic needs to be descended relatively early to avoid entering Sector 13 enroute to LOGAN. TC East should receive this traffic at FL240, with traffic from Sector 13 at FL250. Figure 1 - Sector 12 Area of Responsibility Figure 2 - Sectors 13+14 Combined Area of Responsibility Figure 3 - Sector 13 Area of Responsibility Figure 4 - Sector 14 Area of Responsibility This procedure does not alter the staffing permissions as defined in the UK Division Policy or GCAP.

Valid 26 April 2025 for the duration of the Cross the Pond roster A temporary arrangement is permitted to split LAC South during the Cross the Pond. London Upper Sector (LUS) is also permitted to be opened with or without AC South online for the duration of CTP. Any errors in procedures should be reported to the Operations department via the Helpdesk or Discord. Available Position(s) London Upper Sector - LON_SU_CTR (Relief: LON_SU__CTR) Frequency: 132.840 MHz RTF callsign: London Control Coordination callsign: London Upper Top-down responsibility for: None LUS is an upper airspace split of the London South LAG, with airspace taken from both the Worthing and Dover sectors. Its area of responsibility is as shown in Figure 1. If LUS logs on, then AC South's area of responsibility is the normal AC Worthing and Dover combined AoR, minus that which is shown in Figure 1. 🗺️Agreed Levels Diagram Agreed Levels There are very few agreed levels in and out of LUS. They are listed below for AC South's (Worthing & Dover) reference: From LUS to Dover To Agreement Conditions Brussels TMA, EBLG, EHBK, EHAM, EHBD and LFPG FL310 lvl BIG Via UL9/L607 FL310 lvl ROKKE Via M140 From LUS to Worthing To Agreement Conditions LFOB, LFOP FL310 lvl SFD Via UM605 LFP* FL330 lvl SFD Via UM605 Paris TMA FL310 lvl 60 NM before ETRAT Via L151/UN859 From Worthing to LUS From Agreement Conditions Brize Group, Midlands Group, Severn Group, EGSS and EGSC ⬆️ FL300 Via E and V intention codes From Daventry to LUS From Agreement Conditions MTMA Group ⬆️ FL310 Via all routes Coordination with Adjacent Sectors & Units Maastricht UAC - KOKSY (Belux vACC) The LUS controller must ensure that traffic cruising in their airspace via KONAN is level at its RFL by the western edge of the DVR RFC Area (EGTT vMATS LAC 3.4.3.9), else the traffic must be coordinated with MUAC. This traffic is considered 'known' to MUAC if it's at its RFL, thus enabling the RFC of LTMA departures via KONAN from Dover into LUS's airspace prior to the FIR boundary. Brest ACC The LUS controller must ensure that traffic cruising in their airspace via SITET/XAMAB is level at its RFL by the northern edge of the La Manche Release Area (EGTT vMATS LAC 2.4.1.8), else the traffic must be coordinated with the relevant Brest sector. This traffic is considered 'known' to Brest if it's at its RFL, thus enabling the RFC of LTMA departures via SITET/XAMAB from Worthing into LUS's airspace prior to the FIR boundary. Daventry Daventry must be informed when LUS is opened. EGCC/GP departures climbing FL310 will be transferred to LUS - Daventry must ensure they reach FL310 by the LUS boundary. MTMA inbounds that are transferred from LUS to Daventry are only RFD to FL310 (i.e. remaining inside LUS's airspace). Clacton and AC West Sectors There are no agreements with sectors within Clacton or AC West airspace. However, these controllers should be informed when LUS is opened. Figure 1 - London Upper Sector (LUS) Area of Responsibility This procedure does not alter the staffing permissions as defined in the UK Division Policy or GCAP.