temporary instruction 2024-04-20 - LAC South Splitting Procedures (LUS)

[VATSIM UK Operations]

Valid 1100-1700z 20th April 2024

A temporary arrangement is permitted to split LAC South during the Cross the Pond. This post allows London Upper Sector (LUS) to be opened with or without AC South online for the duration of CTP.

This position is rostered and not available for bookings.

Controllers operating this split must provide a link to vatglasses.uk/ukireland/ in their Controller ATIS.

Any errors in procedures should be reported to the Operations department via the Helpdesk or Discord.

 

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, as long as it is at its RFL, thus allowing 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 western 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, as long as it is at its RFL, thus allowing 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.