Forums

How did you fix this? I have the same problem at the moment (solved)

Effective 26 May 2025 - 7 June 2025 During the Isle of Man TT, a famous motorcycle race, the Isle of Man attracts a record number of visitors. As a result the airport experiences high levels of traffic and a GMC position becomes necessary. From the 26th of May to 7th June 2025 controllers with an S1 rating may open the following position: EGNS GND (relief EGNS__GND) - 121.305 MHz [Ronaldsway GMC] Ronaldsway GMC is responsible for all aprons and taxiways (except taxiway J which is the responsibility of AIR), issuing IFR clearances and managing the flow of traffic. GMC controllers should familiarize themselves with the GEN section of the ACB, as well as the Apron/Taxiway Restrictions and IFR departure procedures in the ADC section. When Runway 21/03 is not in use, AIR may give GMC approval to cross aircraft across Runway 21/03 without individual coordination. Should Runway 21/03 become active, AIR must immediately inform GMC and suspend the agreement. Setting up Euroscope As the position is not in the sector file, controllers will have to manually add the position to the voice communications list. This can be done by clicking the headphone icon in the top of euroscope and filling in the name and frequency as shown in the screenshot below, then clicking ‘new’. Controllers must also untick 'set active APT by owned sectors' in euroscope general settings, as there is no sector defined in the sector file.

Effective 26 May 2025 - UFN Introduction A Restricted Area (Temporary) has been established overhead the site of the SS Richard Montgomery wreck. The RA(T) is that volume of airspace within 1 NM of the wreck extending from SFC to 13,100 ft and has been established to safeguard aircraft in the event of an inadvertent detonation of munitions within the wreck. On VATSIM, controllers may optionally decide to simulate the following procedures. The RA(T) is located in the Thames Estuary adjacent to fix GAPGI and interacts with the TC Thames and Southend APC RMAs as well as TC South sector. The RA(T) is depicted in red in the figure below alongside the TC Thames RMA: TC Thames The RA(T) infringes upon the RNAV-1 transitions for London City and Biggin Hill. As such, aircraft will require tactical intervention to route clear of the RA(T): Inbounds via JACKO (subject to London City departures and the status of the Shoeburyness Danger Areas) may be routed through the northern portion of the RMA typically direct ATPEV/OSVEV. Inbounds via GODLU (and JACKO inbounds where a northern routing is unavailable) shall be radar vectored to position through the delegated MC CTA-8 and 3500:5500 section of the Thames RMA - this enables descent from 6000 ft to 4000 ft within the RMA confines. These inbounds can then be instructed to resume own navigation via ATPEV/OSVEV. London City outbound traffic routing via SOQQA-SODVU-EKNIV may remain on own navigation in accordance with the current Standing Agreement with TC South. Southbound Southend departures via DET will be positioned by Southend APC on an appropriate radar heading through the EKNIV gate that remains clear of the RA(T). Southend APC Southbound departures via DET may depart on own navigation but must be radar monitored by APC. All radar headings through the EKNIV gate must track clear of the RA(T). TC South The RA(T) is located in the south-eastern portion of the SODVU box and London City departures must not be issued any direct routings that would cause them to enter the RA(T). For example, SODVU DCT DVR would penetrate the RA(T).

Hola! Long time. Your last feedback submission was indeed the 28th July 2024. You'll either need to either blow hotter or colder to solicit more. We discuss automagic feedback periodically, but the problem is that sometimes, there's utter waffle submitted, or things submitted in the wrong name and so on, and we currently have no mechanism to unshare feedback. To that end, the process remains manual for now. A

Hello there, Apologies if this has been mentioned before, but could the feedback be automatically shared with the recipient? My last bit of feedback was in 2024, and I am nowhere near as active as I used to be, but I find that hard to believe that nobody has said anything tepid about my controlling since then. I understand it to be a manual process to share the feedback with the recipient, and I understand why to some degree, but surely a simple profanity filter or reporting function would weed out the probably minute levels of inappropriate and/or 'hurtful' feedback? I shall return to my cave.