All Activity

Hello, had the problem today as EGBE_I_TWR that aircraft couldn't contact me at all via voice. Found out that my the receiver location is nowhere near Coventry but instead near Doncaster. Guess thats the problem. Here comes the interesting part. how do I fix it? Thanks

I am pleased to announce that James Bayliss-de Gruchy has been appointed as the events manager. I have been covering this role for a while whilst James got to grips with the department. He will now be supporting me with the events side of operations, whilst support the events assistants.

As we head into the summer of 2025, the Operations Department is short of a few staff members. We would like to recuit one events assistant and a handful of operations assistants. If you have any questions about the roles, including suitability then please don’t hesitate to get in touch. Myself and peter are keen to foster some more home-grown talent in the department - we do not expect anyone to be the complete package when they apply for staff roles - training and guidance will be provided. I would be keen to receive applications from newer and more experienced members alike. Vacancies I am opening applications for the following roles: Operations Assistant Enroute Operations Coordinator Events Assistant The Operations Assistant role is a very fluid, as their primary responsibilities can be within Enroute, Aerodrome or the Sector file. It is suited to both experienced and inexperienced members. Currently in our assistant roles in the department, we have some of our most experienced writers who work on projects rather than coordinating the entire branch. We equally recruit less experienced members to work on Aerodrome or Sector File projects and to develop their skills. The Enroute Operations Coordinator is the department’s subject matter expert on area control. For this reason, a C1 rating (or greater) is required. No-one is an expert on every sector and I do not expect applicants to be (I am certainly not one!). We are lucky to have many contributors, all with their own knowledge bases whose experience you would be required to draw upon in the role. The Events Assistant role, will report to the Events Manager . You will be helping the events manager to organise the UK’s event schedule including Hogmanay Fly-ins, Mancheaster and any new events! You will also be working with the Community department to help them advertise our events, organising our Events Team of volunteers who produce rosters and help to manage events on the day (including flow management). More detail can be found on these roles in the Operations Handbook. If you wish to discuss any of these positions, particularly if unsure how you might best fit into the department, please feel free to contact me or Peter, either via Discord DM or via email archie.middlefell[at]vatsim.uk To Apply Please submit an application by email to jobs[at]vatsim.uk. Please write a short application (max. 300 words) outlining your relevant experience and why you are interested in the role. We are not expecting long applications! Application Deadline EDIT: Applications will be accepted until latest 23:59z on Tuesday 19th August for the Operations Assistant and Events Assistant Role. Applications for the Enroute Operations Coordinator will remain open UFN.

Vatsim UK are pleased to announce the latest in the VFR Event Series, Wingin’ it in Wales. On Friday 8th August between 1730-1930z, we hope to see North Wales lit up with VFR traffic. ATC will be available at Caernarfon (EGCK), Sleap (EGCV) and Hawarden (EGNR). Whether you want to visit the welsh coast line or further inland to discover Snowdonia, this event will sure not disappoint.

Good Afternoon, I'd like to start by announcing the departure of @Thomas Hallam from the team. After years of dedication, hard work and valuable contributions, Tom will be stepping away from his role in the Outreach Team. Tom began in the Marketing team where he helped deliver numerous successful events, with a particular focus on the graphical elements that came with them. Since the disbandment of that team, Tom agreed to continue some of his responsibilities within the newly formed Community Team, where he has been a great help that will be missed. On a more positive note, I am pleased to announce that @Callum Hicks, @Noah Murdochand @Charles Newman will be joining the team in the role of Outreach Assistants. All three bring fresh ideas, and new skills to the team, allowing us to make consistent progress across multiple projects, designed to help us better engage with both current and prospective members, improving the overall experience across the board.

Valid 2025-07-13 – 2025-07-21 General During the Royal International Air Tattoo (RIAT) at RAF Fairford (EGVA), temporary restricted airspace will be in operation. Please note, the times and dates of the restricted airspace on the AIC do not reflect the times and dates we are following on VATSIM. For the duration of the real-world event, Restricted Airspace (Temporary) is established (see diagram in AIC link above). This airspace is considered active on VATSIM when a controller is providing a service as per the instructions below. An air traffic control position will be available for suitably qualified controllers (S3 or above and Military Approach endorsed) to operate on frequency 134.555 MHz (EGVA_APP – “Fairford Radar”) providing approach and departure services for RAF Fairford. Fairford Radar assumes overall control of the RA(T) in the absence of Brize Approach (EGVN_APP). Fairford Radar will also provide top-down services for Fairford in the absence of Fairford Tower (EGVA_TWR). ATC Procedures Fairford Radar is allocated squawk range 6001-6037. 6007 is used as a VFR conspicuity code. Three VRPs are used for Fairford VFR inbounds during the effective period only: Northleach (N) Highworth (SE) Blakehill Farm (SW) VFR departures and arrivals routing via these points require a pre-note to the receiving controller. Three Standard IFR Departure Procedures are to be used to reduce coordination. These consist of a climb straight ahead to 2400 ft before commencing turns: “Fairford North” (all rwys) - H320 climbing FL50 “Fairford West” (27 only) H270 climbing FL50 “Fairford East” (09 only) H090 climbing FL50 The naming conventions are for coordination purposes only. Pilots shall be passed these clearances as if they were non-standard departure instructions. For example: “After departure climb on runway track. On passing 2400 ft, turn left heading 320 degrees. Climb FL50. Squawk 1234. Departure frequency Fairford Radar on 134.555”. All IFR departures are subject to release from Fairford Radar, who will provide a departure frequency in the release. Arrivals Traffic or Deconfliction Service for IFR aircraft Basic or Traffic Service for VFR aircraft IFR codes 6001-6037 (excl. 6007, 6010, 6017) VFR conspicuity squawk 6007 Airways traffic may retain assigned code All traffic to be given clearance into RA(T) over RT by Brize or Fairford Radar controllers - “[Callsign], cleared to enter the RAT…” IFR inbound lowest level FL60 - individually coordinated Inbounds via Q63 route ASHUM/CONKO - NAXAT - BZN descending FL110 as per standing agreement Others route DCT BZN after final fix Holding to take place overhead BZN FL60 and above - coordinate with London AC West, Daventry and Swanwick Mil (not required) Brize Approach remains responsible for BZN hold No aircraft shall be cleared DCT FFD Inbounds shall be transferred directly to Fairford Radar unless holding ILS - Vector to 10 NM intercept RTV - Vector to 5 NM initials VFR - Clear via Northleach (N), Highworth (SE) or Blakehill Farm (SW) VFR may also route DCT if unfamiliar Pre-note Fairford TWR after initial contact Callsign Aircraft type Type of approach Range checks with Fairford TWR ILS - 10 NM range check RTV - 10 NM range check VFR - Not required but transfer by 5 NM (MATZ Boundary) or assigned VRP IFR Departures Clear via Radar Vectors to First Waypoint (preferred) or MAXOB SID Straight ahead until passing 2400 ft, then: “Fairford North” (all rwys) H320 “Fairford West” (27 only) H270 “Fairford East” (09 only) H090 Initial climb FL50 UKCP squawk if GAT (Airways) Fairford Radar local squawk if OAT (non-Airways) Codes from range 6001-6037 (excl. 6007, 6010 and 6017) Release from Fairford Radar during taxi giving C/S and Departure Procedure (eg. “Release: BLACK 01, Fairford North”) Departure frequency given by Fairford Radar with release (eg. “BLACK 01 released on a Fairford North, departure frequency 134.555”) Fairford Radar controller will coordinate with Area Control units: GAT coordinate with AC West or AC Daventry/Central OAT coordinate with Swanwick Mil VFR Departures Clear to leave RA(T) via COBEL (North) or MANOR (South), not above 3000ft VFR squawk 6010 Low level via Northleach (N), Highworth (SE) or Blakehill Farm (SW), not above 2000ft VFR squawk 6017 Free-flow - prenote details to Fairford Radar (eg. “Prenote: TENNIS 1, Spitfire, VFR to Duxford, MANOR departure”) COBEL or MANOR VFR departures contact Fairford Radar 134.555 VFR departures via Highworth, Northleach or Blakehill Farm contact Brize Zone 119.005 VFR freecall enroute once clear of RA(T) or outside Brize LARS coverage (40 NM) Kemble VFR Routes Blue (Northwest) - Dursley DCT Green (Northeast) - Chedworth DCT Red (Southeast) - M4 J16 DCT Yellow (Southwest) - M4 J17 DCT VFR aircraft squawk 3717 Circuit traffic squawk 7010 Departures not above 1500 ft VFR - Kemble AFIS to prenote Brize Zone who will provide clearance Arrivals not above 2500 ft VFR Clear to enter RA(T) via a route with Basic Service, and prenote Kemble AFIS Transfer to Kemble AFIS (118.430) with approx. 5 NM to run Kemble AFIS will transfer to Brize Zone (119.005) once reported leaving the ATZ and clear of known traffic Example; “Brize clears GELUE to leave the RAT via the Green Route, not above altitude 1500 ft VFR, squawk 3717. Next frequency Brize Zone on 119.005.”

Hi all! Please take note of the purple supplements/corrections to the original post for changes made on 2 July 2025 after further consultation with members and PT staff.

What's Changing? Each of the Pilot Training waiting lists can be subject to three types of restrictions: Minimum network experience This requires members to have a minimum number of flying and/or ATC hours on the VATSIM network Minimum activity This requires members on the list to maintain a minimum amount of activity on the VATSIM network Maximum list size This will close enrollment to the list if it reaches a predetermined size The implementation of these three control measures will vary with time and the demand for any given course. The following controls remain in place: The P1 PPL(A) course will not be available to visiting members This is due to the demand for the P1 from home members and will be continually assessed Both the P1 PPL(A) and P2 SEIR(A) require Moodle course completion to receive a training place Note: these changes, along with the full policy for training place allocations, will be formally written into a policy document within the next quarter. How will it work? The maximum list size will be handled automatically through logic in the self-enrollment system. Additionally, the Community team will not process waiting list additions manually if the list has reached its capacity. Minimum network experience will be determined manually by the Pilot Training Department team through software tools. I estimate that these checks will be run on a weekly basis. If a member joins the list with insufficient network experience, they will be removed from the list at the next check and notified of the reason for the removal. The member may rejoin the list without any restriction at a later date once they have the minimum network experience. Minimum activity will also be manually tracked by the Pilot Training Department team through software tools. Activity will be assessed over a fixed period, beginning on the first day of the month following the member’s initial join date. The member will be notified at the end of the activity period if they did not meet the minimum activity requirement. A member will be removed from the list if they receive three two or more activity reminders without providing mitigating circumstances. For example, if a member joins a list with a 3-month activity window on 12 May 2025, their activity will be measured from 1 June 2025 at 00:00:00z until 31 August 2025 at 23:59:59z. If the member accumulates 10 hours within this period then they are considered active and their next activity window will begin on 1 September 2025 at 00:00:00z. I'm currently on the list. What happens now? The activity window for all members currently on the list will start on 1 July 2025 at 00:00:00z. Members on the list who do not meet the minimum network experience will be given the opportunity to engage with the network and acquire 10 hours of network experience by 31 July 2025 at 23:59:59z. If the member meets this, they will be expected to acquire the remaining minimum experience before the end of their activity window. An email referencing this post and explaining how it is individually applicable will be sent out over the next few days to all members of the waiting list. Supplement for clarification (2 July 2025): Activity will be measured for the period 1 April 2025 00:00:00z to 30 June 2025 23:59:59z to determine the initial activity for everyone on the waiting list. The "strike system" will come into effect, with the first strikes being issued on 1 October 2025. If a home member has at least 10 hours of flying (or 5 hours if they are an active ATC) in that period, they will receive an email notifying them of these changes. If a home member has less than 10 hours of flying (or 5 hours if they are an active ATC) in that period, they will be informed by email. Between 1 July 2025 00:00:00z and 30 September 2025 23:59:59z, the member must complete at least 10 hours of flying (or 5 hours if they are an active ATC). If the member has not completed the minimum hours, they will be removed from the waiting list. A visiting member must complete 10 hours of flying (or 5 hours if they are an active ATC) before 1 August 2025 00:00:00z to be moved to the master list with their original join date. P1 PPL(A) List Controls The P1 PPL(A) will receive the strictest control measures due to the excessive demand for the course. Minimum network experience Members with no ATC experience are required to have a minimum of 30 hours of flying time logged on the VATSIM network Members with ATC experience are required to have a minimum of 15 hours of flying time logged on the VATSIM network In the future, members who have completed The Flying Programme will be credited with a reduced hour requirement Minimum activity Members who do not control within the specified activity period are required to have a minimum of 10 hours of flying every 3 months Members who do control within the specified activity period are required to have a minimum of 5 hours of flying every 3 months Maximum list size The maximum size of the P1 PPL(A) waiting list is 100 members Note: Members are required to complete the P1 Moodle course before receiving a training place. Any members near the top of the waiting list without Moodle completion will be notified and given 1 month to complete the course. P2 SEIR(A) List Controls The P2 SEIR(A) will receive the following control measures. Minimum network experience Members are required to have a minimum of 60 hours of flying time logged on the VATSIM network Minimum activity Members are required to have a minimum of 10 hours of flying every 3 months Maximum list size The maximum size of the P1 PPL(A) waiting list is 20 members Note: Members are required to complete the P2 Moodle course before receiving a training place. Any members near the top of the waiting list without Moodle completion will be notified and given 1 month to complete the course. Why is this necessary? Firstly, these changes are long overdue. The P1 waiting list has been unmanageably long for a significant amount of time. This has meant that we could not give accurate waiting times for people on the list. Since the P1 started, we used the Moodle course as the only criteria for people to get a training place. However, this has proved to be unhelpful. Students get to the course having forgotten most of the theory and it has not been an effective stopgap in managing the list size. As of 16 June 2025, this is the distribution of people on the list sorted into bins by join month: As is evident by the massive spikes this year, the majority of people on the P1 list joined within the last 2 months. I then looked at the amount of network experience people on the list had with flying and controlling on VATSIM: The list has 189 members on it. The vast majority of people on the list do not have any ATC experience. 84 of the people on the list have less than 50 flying hours on the network, of which 73 have less than 30 hours. Worryingly, 30 people on the list have never logged onto VATSIM as either a pilot or an ATC. While we strive to offer training opportunities to as many students as possible, practical limitations make this unachievable. Data consistently shows a strong correlation between a student’s network activity and their engagement with the P1 course. Furthermore, those with broader foundational experience on the network tend to perform significantly better when operating in controlled or high-traffic airspace. Prolonged waiting times, caused by slow training progression and an imbalance between demand and available mentors, can demotivate even the most promising candidates. We believe this has, in some cases, led to the loss of potential mentors. The P1 course is currently our strongest performer and ranks among the highest-performing programmes in the division. After reviewing relevant statistics with both our Flight Instructors and the Pilot Training Manager, we have concluded that introducing additional restrictions to all training lists is the most effective way forward. These changes will enhance the overall quality of training, increase the conversion rate from student to mentor, and enable us to provide more accurate waiting time estimates to those on the list. The effectiveness of these changes will be monitored over the next two quarters of 2025 and will be reviewed in Q1 2026.

VATSIM UK and the Portuguese vACC are partnering to bring you an event to kick off summer! Join us on an unique one way city shuttle between Bristol (EGGD), heart of the West Country, known for Banksy, cider and greenery as far as the eye can see and Porto (LPPR), Portugal's riverside gem known for the famous Port Wine, the UNESCO-listed old town and the scenic approach into runway 35 over the city. We hope to see you on the 12 of July, with departures from EGGD from 1400-1600z and arrivals into LPPR from 1600-1800z.

Waiting Lists Are Now Self-Enrollable! We’re excited to announce that all ATC and Pilot rating-based waiting lists are now self-enrollable. These are available through https://www.vatsim.uk/mship/waiting-lists If you meet the required rating and hour criteria, you’ll be able to add yourself directly, meaning no more waiting to be manually added by a staff member. This change brings several benefits: Reduces the workload on our Community Department. Ensures a faster and fairer process for members. Helps the division move towards greater automation, allowing staff to focus more on development and support. Note: Some ATC endorsement lists such as Heathrow TWR/APP are unavailable for self-enrolment. These lists require prerequisite endorsements that must be checked manually for the time being. Please continue to submit tickets for these as normal. A huge thank you to our Technology Team for making this possible! Their continued work behind the scenes is helping us create a more streamlined and modern experience to members. Going forward, any questions about ATC waiting lists (e.g. "Am I eligible?", "Why isn’t it moving?", "Where am I on the list?") should be directed to the ATC Training Department, not Community.

Thanks for your hard work Cole! Don't be a stranger a ✈️

Good job Cholay! Good luck cooking your own steaks ❤️

Hi everyone, After joining the VATSIM UK Pilot Department in September 2023, I’ve made the decision to step down from the Initial Flight Instructor role. It’s been a genuinely rewarding experience to contribute to The Flying Programme, especially during a period of significant growth and change across the division. Life, however, has a habit of catching up with us all, and I’ve found it increasingly difficult to give the role the time and attention it deserves. I’m proud of what I’ve been able to contribute and grateful for the opportunity to work alongside such dedicated and passionate individuals and wish everyone the best of luck for the future. A huge thank you to everyone who’s supported me along the way - it's been a pleasure to be part of the team. Cole

It’s been in the events teams diary for months, so I'm delighted finally to announce the latest rendition of VATSIM UK's longest running event! An event that was first held in 2006, Mid Summer Madness is an annual event based out of Birmingham Airport (EGBB. On Saturday 2nd and Sunday 3rd August, Birmingham will host the 19th edition of its annual Mid Summer Madness (MSM) Event. Birmingham Airport will be fully staffed from 0900-1700Z on 2nd August and 0900-1500z on 3rd August. There are no flight bookings, so just turn up and fly to and/or from EGBB in whatever you like, when ever you like and as many times as you like! Please help us celebrate the 19th anniversary of this fantastic event by flying in and out of Birmingham - the skies are guaranteed to be busy around Birmingham! To help manage the sanity of our controllers, some airports may be subject to flow restrictions. We appreciate your patience in the event these flow measures affect your flight. Most of your controllers and a few of your fellow pilots will be sat in the same room coordinating in person in real time. We really hope you can help us make this the best Mid Summer Madness event yet! Prizes This year we've again teamed up with some amazing flight simulation software companies. Thanks to the generosity of these fantastic companies, we're able to offer the following prizes to pilots who fly in or out of Birmingham during the event weekend: Velocity Flight Training – 30 minute fixed-base Boeing 737 simulator ride British Avgeek – merchandise from online store Mystery Prize – from a well known addon creator Inbuilds – £45 store gift card for use on an item of your choice Pyreegue Dev Co – free copy of their upcoming Birmingham Scenery FS2Crew – 1 copy for a product of your choice These prizes will be available to win for pilots for the below: One for the pilot who flies the furthest distance whilst online to be with us, either departing or arriving Birmingham EGBB during event hours. Remaining prizes at random for pilots who fly a full flight online into or out of Birmingham EGBB during event hours. Winners will be contacted via the VATSIM UK Discord by a member of the MSM event team after the event to claim their prize. Please make sure you are registered there and check regularly after the event in case you win. We have also partnered this year with some of the UK’s favourite virtual airlines. Thanks to those who have offered to join us for the event: vEZY, BAVirtual, vEXS, UKV, vRYR, BVX (Osprey), vTUI, UNI – check with your favourite VA for more information! Thanks again to our sponsors who have made this possible. We hope to see you there! Controllers please note, Birmingham positions for this event will be staffed by those in attendance at the venue. Support with enroute and adjacent control would be greatly appreciated.

Effective 12 June 2025 Some of Prestwick's SIDs/RNAV transitions have been re-designated after waypoint OKNOB was replaced with AKODA, and UTITI replaced with MIJAG. TRN2S -> TRN3S SUMIN2S -> SUMIN3S OKNOB1L -> AKODA1L Documentation Status The Prestwick (EGPK) documentation at docs.vatsim.uk has been updated.

Effective 12 June 2025 Some of Guernsey's SIDs have been re-designated after waypoint PIKEY was renamed to VAXMA. LUSIT1E -> LUSIT2E GULDA1W/1E -> GULDA2W/2E Documentation Status The Guernsey (EGJB) controller documentation will be amended at the next release.

From 2025/06, the Sector File has a new home! The Sector File is included in the controller pack, but if you need to download it separately: https://docs.vatsim.uk/General/Software Downloads/Controller Pack %26 Sector File/

Get ready for one of Europe's biggest aviation gatherings! VATSIM UK will be hosting a Royal International Air Tattoo (RIAT) Fly In. Held at RAF Fairford (EGVA) on the 13th of July from 1830-2100z, we invite people to come and celebrate the magic of military and civil aviation. RAF Fairford will be fully staffed, ready to handle a variety of inbounds. We invite VSOAs to attend, as well as civilian aircraft (which make up a small section of RIAT). Please note this event will not be simulating the aerial display part of the airshow. It's purely a fly in. A briefing will be published before the event. Controllers wishing to control this event should book via the CTS

Effective 12 June 2025 FAO: LAC Lakes; MPC West; Antrim; ScAC Rathlin Summary The sectorisation between Lakes & Rathlin, and PC West & Antrim is being revised. The changes will transfer airspace: From Rathlin → Lakes - for traffic via new COP WETFI (see this procedure change post) in EGPX FRA that will remain with AC Lakes before transfer to Shannon From Rathlin → Lakes - to give Lakes more room for vectoring in an area south of REMSI From PC West → Antrim - to enable earlier descent of Belfast inbounds. Revised Sector Diagrams LAC Lakes MPC West Antrim ScAC Rathlin Documentation Status The London (EGTT) and Scottish (EGPX) vMATS Part 2 and Agreed Levels Diagrams will be amended to coincide with this change. Revised versions will be available at docs.vatsim.uk/Enroute from the effective date.

Effective 12 June 2025 Introduction A new COP WETFI has been established north of BAGSO for Shannon overflights via northern Oceanic Entry Points (excluding MTMA outbounds). Traffic via WETFI will show intention code L6. The COP is situated in the part of the EGPX FRA volume newly transferred from ScAC Rathlin to LAC Lakes (see this procedure change post). We have also taken the opportunity to review our LoA with VATeir, permitting: cross-border FRA directs by Lakes into Shannon airspace RFC and RFT of all westbound traffic transferred from Lakes to Shannon after passing abeam RAMOX unlimited RFC and RFT of MTMA outbounds from PC West to Shannon after passing abeam RAMOX. vMATS Procedure Deleted text – red and strikethrough. New text in blue. LAC 6 | North LAG | AC Lakes LAC 6.4.4 Coordination with Shannon LAC 6.4.4.3 Transfer of Control and Communication (excerpt) Unless otherwise specified in the table below, transfer of communication shall occur at or before the relevant COP at the FIR/AoR boundary. UK ATS Route Coordination Point Transfer of Control Transfer of Communications From London ACC to Shannon ACC From Shannon ACC to London ACC FRA WETFI WETFI Abeam RAMOX N/A LAC 6.4.4.7 RFC/RFT of Westbound Traffic to Shannon ACC (new section) All westbound traffic transferred to Shannon via BAGSO and WETFI is RFC to any level and RFT after passing (abeam) RAMOX. This traffic must not enter Scottish Rathlin sector without co-ordination. LAC 6.4.4.8 Permitted Cross-Border FRA Directs (new section) Shannon overflights may be cleared by London direct to their Oceanic Entry Point (OEP), except that traffic with an OEP north of RESNO may only be cleared to REVNU (if not filed via REVNU, the traffic shall be left on its flight planned route). Where traffic is given a direct route, the transferring controller is responsible for ensuring that, at the point of transfer, converging aircraft have at least 10 NM planned lateral separation for a minimum of 20 NM beyond the common boundary. MPC 3 | PC West MPC 3.2.2 External Standing Agreements MPC 3.2.2.8 Shannon LIFFY (FL245+) (excerpt) From PC West to Shannon LIFFY From Agreement Conditions MTMA Group, EGNH, EGNO FL280 lvl RAMOX (See Note) Note: This traffic is RFC with Lakes to any level and RFT after passing (abeam) RAMOX, subject to known traffic. This includes traffic transferred on a heading. Note: Traffic is released for climb to FL330 after passing RAMOX, subject to known traffic. Traffic transferred on a heading is not RFT until passing RAMOX. Documentation Status The London (EGTT) and Scottish (EGPX) vMATS Part 2 and Agreed Levels Diagrams will be amended to coincide with this change. Revised versions will be available at docs.vatsim.uk/Enroute from the effective date.

Effective 12 June 2025 Introduction Berry Head CTAs 6 & 7 have been expanded both laterally and vertically, and the associated ATS route structure revised used by Cork (EICK) inbounds and outbounds. Traffic from/to Cork will be permitted to route via both LEDGO and now SAMON. We have also taken the opportunity to review our LoA with VATeir, introducing a LEDGO RFC Area and additional cross-border FRA directs for traffic in both directions. Berry Head CTAs 6 & 7 Airspace and Route Structure Existing CTA 6: Image from eAIP ENR 6-7 (15 May 25) New CTA 6: Image from eAIP ENR 6-7 (12 Jun 25) New route structure: Image from eAIP ENR 6-68 (12 Jun 25) vMATS Procedure Deleted text – red and strikethrough. New text in blue. LAC 8 | West LAG | AC West LAC 8.3.4 AC West External Standing Agreements LAC 8.3.4.6 Shannon Low Level (FL245-) From AC West to Shannon Low Level (excerpt) To Via Agreement Conditions EICK LEDGO/SAMON Max FL240 lvl LEDGO/SAMON (See Note) Note: Traffic must cross BOGMI OVZOG/EVCOR/CANZI at FL250 or above and is RFD and RFT after passing BOGMI these points. The transfer of communications shall take place prior to BOGMI OVZOG/EVCOR/CANZI. From AC West to Shannon Low Level From Via Agreement Conditions EICK SAMON/LEDGO Max FL230 Notes (1 & 2) Note 1: Traffic may be presented in the climb to the coordinated level at the AoR boundary. Note 2: This traffic is RFC to FL290 within the confines of the LEDGO RFC Area. It is not released for turn until passing SAMON/LEDGO. Shannon ACC shall ensure separation between this traffic and other aircraft within the Shannon FIR. [...] LAC 8.4.1 Coordination with Shannon ACC LAC 8.4.1.8 LEDGO RFC Area (new section) Traffic outbound from EICK via SAMON and LEDGO transferred from Shannon Low Level to London ACC is RFC to FL290 within the LEDGO RFC Area (see Figure LAC-34), without co-ordination with Shannon Upper. Aircraft must not be turned without co-ordination until passing SAMON / LEDGO. Figure LAC-34 - LEDGO RFC Area LAC 8.4.1.89 RFC/RFT of Westbound traffic to Shannon ACC (section renumbered) All westbound traffic transferred to Shannon is RFC and RFT (up to a maximum of 45°) on contact within the offering sector only. All traffic inbound to Irish airfields (EI** & EGA*) is RFD on contact within the offering sector only. If Shannon changes the level or heading of an aircraft, they are then responsible for providing separation against any potentially conflicting traffic on routes in the vicinity of DUB or CRK. If London is transferred a potentially conflicting eastbound aircraft from Shannon, the level of said traffic shall not be changed until co-ordination is effected with Shannon. LAC 8.4.1.910 Permitted Cross-Border FRA Directs FRA Directs from 15W to London AC Sector 9 Where traffic is given a direct route, the transferring controller is responsible for ensuring that, at the point of transfer, converging aircraft have at least 10 NM planned lateral separation for a minimum of 20 NM beyond the common boundary. Traffic making landfall at 15W may be cleared to certain directs by Shannon without co-ordination with London ACC, provided that the sector sequence remains unaltered. London TMA Arrivals – PEWBI, FONZU, SIDDI Overflights – FACTU, EMJEE, NUCHU, GAJIT, OXLOW, AMPOP, TALIG, DOLUR, NAKID, LIZAD Shannon overflights may be cleared by London direct to their Oceanic Entry Point (OEP), except that traffic with an OEP north of RESNO may only be cleared to REVNU (if not filed via REVNU, the traffic shall be left on its flight planned route). Documentation Status The London (EGTT) vMATS Part 2 and Agreed Levels Diagrams will be amended to coincide with this change. Revised versions will be available at docs.vatsim.uk/Enroute from the effective date.

Effective 12 June 2025 FAO: All Enroute Introduction The Westcott (WCO) NDB is being decommissioned. It is being replaced by new waypoint WEZKO, affecting Heathrow STARs. Following a review of the naming of 5LNCs (5-letter name codes), the CAA (see AIC Y 066/2025) have amended a number of waypoint names deemed inappropriate, affecting Severn Group STARs. Changes to Prestwick and Guernsey procedures will be notified separately. WCO NDB replaced by WEZKO WCO is replaced by a new waypoint, WEZKO, in the same geographical position. The affected London Heathrow (EGLL) and Northolt (EGWU) STAR designators are incremented: Designator Arrival Via Route FITBO 2H Y125 FITBO – SOPIT – WEZKO WCO – BNN HON 2H L15, L10, L612 HON – TOBID – SOPIT – WEZKO WCO – BNN NUGRA 2H (U)Y53, Q36, Q38 NUGRA – TOBID – SOPIT – WEZKO WCO – BNN Oxford (EGTK) departures that previously routed via WCO will now route via WEZKO. Enroute 5LNC Changes Scottish - RATPU on P18 (Aberdeen traffic) is replaced by EPCAN. LAC Worthing - RUBMI on N866 (north of LORKU) is replaced by LAWJO. LAC West - COXPE on Severn Group STARs is replaced by FARJO. The affected Cardiff (EGFF) & St Athan (EGSY) and Bristol (EGGD) STAR designators are incremented: Designator Arrival Via Route TOJAQ 2B P16, FRA TOJAQ – FARJO COXPE – IZLAW – EXMOR – BRI TOJAQ 2C P16, FRA TOJAQ – FARJO COXPE – IZLAW – EXMOR – CDF Documentation Status The London (EGTT) and Scottish (EGPX) vMATS Part 2s will be amended to coincide with this change. Revised versions will be available at docs.vatsim.uk/Enroute from the effective date.

Effective 12 June 2025 FAO: Inverness (EGPE); Scottish Procedural Approach Position Removed Inverness (EGPE) Approach Control Services will always be provided using Radar. Therefore, the procedural Inverness Approach position (EGPE_A_APP) is being removed and shall no longer be opened by controllers. Radar Services are provided by Inverness Radar (EGPE_APP) on 122.605 SMAA Revisions Two Surveillance Minimum Altitude Area (SMAA) sectors on the ATC Surveillance Minimum Altitude Chart have been revised: The north east sector is raised from 2200' to 2300'. The southern sector is raised from 3700' to 3900'. The revised ATC SMAC can be viewed here (note that this link will only work until July). Documentation Status The Inverness (EGPE) documentation on the docs.vatsim.uk site will be updated to coincide with these changes.

Effective 12 June 2025 Summary The Heathrow Tower backup frequency is being converted to an 8.33 channel. We allocate this frequency for use as Heathrow Planner, therefore: Heathrow Planner (EGLL_P_GND) 124.475 becomes 124.480 Required Actions by Controllers Controllers are required to update their Sector File, Controller Pack and ATIS profiles to ensure correct recognition in EuroScope and radio coverage in AFV. Audio For VATSIM will be updated by the Operations Department on AIRAC day to reflect the new frequencies. Documentation Status The London Heathrow (EGLL) vMATS Part 2 and any other affected documentation will be updated at its next release.

Effective 12 June 2025 Summary The remaining 25 kHz Glasgow (EGPF) frequencies will be converted to 8.33 channels. Glasgow Radar (EGPF_APP) 119.100 becomes 119.105 Glasgow ATIS (EGPF_ATIS) 129.575 becomes 129.580 Required Actions by Controllers Controllers are required to update their Sector File, Controller Pack and ATIS profiles to ensure correct recognition in EuroScope and radio coverage in AFV. Audio For VATSIM will be updated by the Operations Department on AIRAC day to reflect the new frequencies. Documentation Status The Glasgow (EGPF) and Scottish (EGPX) vMATS Part 2s and any other affected documentation will be updated at their next update.