By Chris Pawley
Effective 09 November 2017
Liverpool STARs via TIPOD to the North-West are truncated and redesignated
TIPOD2A is truncated at MALUD and is redesignated TIPOD3A
TIPOD1B is truncasted at PENIL and is redesignated TIPOD2B
There are no significant alterations to operational procedures, all agreed levels previously documented remain applicable.
The UK sector file is updated to reflect these changes, other documentation will be forthcoming in a future update.
By Chris Pawley
Effective 04 January 2018
Trail Procedures between 04 January 2018 and 3 January 2019.
The DET2Z SID is introduced at London/Heathrow (EGLL) from the above date. This SID is for departures from runway 09R and follows the same lateral track as the existing DET1J departure; a change to the vertical navigation is applied at DET D29 and DET D34.
All aircraft will be assigned DET2Z by default for the period of the trial. Crews unable to meet the climb restrictions should request a DET1J departure which can be assigned without coordination.
The purpose of the trial is to identify the impact on steeper procedures from a noise, air quality and operational perspective.
The UK Sector File contains this procedure. Other documentation will not be updated due to the trial nature of this procedure.
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)
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.
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
By Chris Pawley
Effective 01 February 2018
From the effective date, the position of TC Bandbox is introduced.
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
LTC_SW, LTC_S, LTC, LON_S, LON
Changes to handoff procedures
Read from Left to Right, hand off to the first online station
LTC_SE, LTC_S, LTC, LON_S, LON_SC, LON, KKAPP
LTC_SW, LTC_S, LTC, LON_S, LON_SC, LON, KKAPP
LTC_NW, LTC_N, LTC, LON_C, LON_SC, LON, LL_N_APP
LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, LL_N_APP
LTC_SE, LTC_S, LTC, LON_S, LON_SC, LON, LL_N_APP
LTC_SW, LTC_S, LTC, LON_S, LON_SC, LON, LL_N_APP
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
ESSEX, LTC_NW, LTC_N, LTC, LON_C, LON_SC, LON
LTC_NE, LTC_N, LTC, LTC_E, LON_E, LON_C, LON_SC, LON, LL_N_APP (LAM only), ESSEX
LTC_NW, LTC_N, LTC, LTC_E, LON_C, LON_SC, LON, ESSEX, GW_APP
GW_APP, ESSEX, LTC_NW, LTC_N, LTC, LTC_E, LON_C, LON_SC, LON
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.