By Archie Bailey
Can someone explain how to install the new UKCP - when I downloaded the zip file I have loads of different folders including 'lib', 'resource', 'spike', 'test' and many more. I just don't know what to do with them and what needs to be done inside of Euroscope.
Any help would be great.
By Matthew Topping
I saw this on my news feed the other day and thought it was really interesting...
By Rhys Warner-Smith
Where is the love?
London City airport from a pilots' perspective is an interesting and, somewhat different, experience from the standard arrival. One gets to weave the skies around Heathrow and Gatwick and treated with an interesting approach at the end of it.
From a controllers' perspective, there is the above aerial weaving and wrangling for our S3's and the sequencing processes for our S2's and S1's. City is an interesting airfield and, in my humble opinion, not loved enough.
In your humble opinions, why do you think City is relatively unloved? I don't have any data to hand to support my loveless claims but arrivals and departures seem to be few and far between plus the tower seems to be gathering dust too.
I think that London City could be an interesting jewel in the heart of UK airspace. What do you think?
By Andy Ford
If you're reading this, then there's a good chance that you're interested in flying to support an ATC practical exam in VATSIM UK. First of all, thank you for supporting our controllers by providing them with the crucial traffic required to show off their skills and obtain their next rating, it wouldn't be possible without you! The purpose of this post is to offer some guidance to you, the pilot, about what to expect when flying around an exam and some of the do's and don'ts of the process. Exams in the UK can often be a fairly busy affair, with lots of people all wanting to do a variety of different things.
Come prepared. Make sure you have charts handy for the aerodrome that you will be visiting so that you don't forget the ILS frequency or get caught unawares with a taxi route that you weren't expecting. Be patient. Exams in the UK are often busy and frequencies can become congested. Try to avoid transmitting over other pilots and please don't transmit when another pilot needs to read something back to the controller. As a general rule, if it's a clearance (IFR/VFR, Taxi, Takeoff), the pilot needs to readback before the next one transmits. Ask the examiner if you're unsure. The lead examiner for an exam will always use the "X" callsign, for example, EGKK_X_TWR. If you're not sure if you should be doing something, or if you just want to know what type of traffic might be useful for the exam, ask the examiner. Aviate, Navigate, Communicate. This is especially important if you're flying using text only for radio transmissions. Make sure that you fly the plane before responding on the radio - if that means you need a second to turn the heading dial before responding, that's better than starting your turn much later after you've done your readback. Fly standard procedures. An exam should reflect a fairly busy but normal scenario - plenty of normal IFR traffic, with the occasional VFR or non-standard movement to integrate, is usually all that's necessary. We can't assess a student if we only have VFR zone transits! Don't:
Declare an emergency. Emergencies are not an exam requirement under VATSIM GRP and can be very disruptive both to the exam candidate and other pilots. If you experience a significant issue with your aircraft, it would be better to resolve it and complete your flight offline. Please do not ask the examiner if you may conduct an emergency, the answer nine times out of ten will be "no". From time to time, an examiner may ask for an emergency, in order to generate a particular traffic situation - but the examiner will come to you if you're the lucky person. Conduct unnecessary missed approaches. In order to assess exam criteria, we only need a total of one missed approach per exam. Pilots who constantly go around without good reason can be disruptive to the exam and often do not allow the candidate to demonstrate any additional skills. If the missed approach is genuine or you're conducting training circuits that have been approved by the controller, then this does not apply to you. In all other cases, if the examiner would like a missed approach, they will ask. Make long, unnecessary transmissions. The controllers don't need to hear your life story. If they give you an instruction, read it back as it was given. If it's your first transmission on a new frequency, keep it short and only give relevant details - what you had for dinner doesn't count. Expect the candidate to grant your every request. Exams are busy. If you request something like a full racetrack procedural approach, expect the candidate to decline your request or make you wait until the traffic allows it to happen. If time is of the essence, consider accepting vectors to final approach for your approach of choice. Take the biscuit. Aircraft such as Blimps (this really happened!) aren't productive in 99.9% of exams - as they really don't reflect VATSIM traffic. Really. We're not here to ruin someone's night, we're here to facilitate them in demonstrating their skills. Once again, thank you for supporting our ATC exams and we hope you have a pleasant experience.
By Harry Sugden
The Sector File <- Download Link
You can also use the auto-download feature of EuroScope to obtain the latest version.
Found a bug while using the new sector file? That’s anything from an auto-handoff that doesn’t work, to a missing position, to a misbehaving agreement… Use the EuroScope department of the helpdesk!
Alternate ownerships for observing/mentoring
It's possible for mentors to get the correct sector ownerships without needing to select a primary frequency. Just go to Other settings...Sector ownership setup, click 'select all' and select 'Mentoring TWR/APP' from the list. For mentoring on LON_*_CTR (or SCO_CTR) you will need to select the relevant 'Observing LON_*_CTR' option instead to specify which sector(s) you are interested in.
The LON_*_CTR can also be used for observing purposes rather than mentoring, but this requires a quick edit of the UK.ese file to tell Euroscope what your log-in callsign for observing will be. (E.g. HS_OBS.) Open UK.ese in Notepad or another text editor and the line to edit is at the top and clearly indicated. There's also an 'Observing London FIR' option that will give you ownership of every sector in the FIR, regardless of who else is online.
Adjacent airports shown when using the General Setting 'Set active APT by owned sectors'
There is now an option to choose which departure airports to show, by means of a special runway 00 at '000A Show adjacent departure airports' in the Runway Selector dialogue. This mainly affects London and Scottish Control sectors.
Option 1, with a selected runway 00 on the right hand side (under DEP or ARR, or both, doesn't matter): the departure list will show departures from all airports within the sector, or immediately adjacent to it.
Option 2, with no runway 00 selected: the departure list will show departures only from airports for which you have top-down responsibility for TWR services. That is, only when nobody else is covering it. This is the mode of operation found in previous versions of the sector file.
Updating the sector file in the controller pack
If you're using a controller pack later than 2020/02 - you can use the auto-download tool built in to Euroscope. This will automatically download the new sector file and ask if you want to use it in place of the previous version.
If you prefer to do things manually, if your ASR is looking for a file called "UK.sct" - you can simply rename the sectorfile you have downloaded. If you want to have some automation, you can change each ASR to look for UK_yyyy_mm.sct and add your new sector file to the folder located at Euroscope\UK\Data\sector\... - Euroscope will prompt you to use the latest version of the sector file each time you load Euroscope.
Contributing to the Project
We always welcome contributions as the sector file works best when we all work towards keeping it updated. Below you can find the repository of data and the guide to contributing to our sector file in a future cycle.