PI-26-002 - New Worthing only London Position¶
| Instruction ID | PI-26-002 |
|---|---|
| Effective Date | 22/01/2026 (AIRAC 2601) |
| Status | |
| Applicable To | LAG South, LAG Central, LAG West; EGLL, EGKK, EGLF, EGHI, EGHH, EGJJ |
| Incorporated into Docs | Partial |
Introduction¶
In response to enroute controller feedback, a new London position is to be established covering the Worthing half of the South LAG. This will enable both Dover and Worthing to be opened independently.
Warning
All UK controllers must update their Sector File to ensure the position is recognised correctly.
As with all positions published in the vMATS, controllers may open the Worthing only position free of restrictions (a Heathrow Tier 1 endorsement is not required). However, it is the view of the Operations Department that where APC coverage is available at EGLL and/or EGKK, the most effective and even split of the South LAG with two controllers is achieved with TC South/AC South.
New Position¶
Callsign: LON_H_CTR
Coordination Name: “AC Worthing”
Frequency: 134.440
Controller ID: LH
Ownership: Worthing sector (see image); top-down of Solent Radar and airfields (EGHI, EGHH); top-down of TC SW sector and associated airfields (KK, LF, KA)

Ownership Priority¶
This change affects top-down ownership and departure handoff priorities for aerodrome controllers.
The coverage priority order becomes (left to right):
Worthing sector (top-down for EGHI and EGHH)
| LON_H_CTR 134.440 |
LON_S_CTR 129.430 |
LON_SC_CTR 132.605 |
LON_CTR 127.430 |
TC South West sector (top-down for EGKK, EGKA and EGLF)
| LTC_SW_CTR 133.180 |
LTC_S_CTR 134.125 |
LTC_CTR 135.805 |
LON_H_CTR 134.440 |
LON_S_CTR 129.430 |
As per Worthing |
Documentation Status¶
All controller tools (Sector File, Controller Pack, Plugin, VACS) will be updated to coincide with this change.
The London (EGTT) vMATS Part 2 and Agreed Levels Diagrams will be amended to coincide with this change.
Local aerodrome documentation will be updated at the first opportunity.
Errors in this instruction should be reported to [email protected]