Jump to content

Callum S - 1179882

ATS Staff
  • Posts

    1498
  • Joined

  • Last visited

  • Days Won

    101

Posts posted by Callum S - 1179882

  1. Hi All,

     

    Welcome back to another VATPAC tip - designed to educate, remind and open a discussion on particular trends that are observed within the Division. 

     

    This week, we're taking a look at coverage area's and how to determine whether you're in controller coverage. VATPAC's airspace is a little different to other Divisions so it's important to pay attention, even if you've flown with us before. ;) 

     

    A brief explanation of Australia's Airspace

    Australia is made up of 2 FIR's (Flight Information Region). They're roughly split diagonally down the entirety of Australia. The northern part is known as Brisbane Centre and the Southern, Melbourne Centre (Split with a green line below). A controller who is rated as C1 (Controller) can logon to a position which laterally covers the entire domestic (everything except oceanic) portion of the Brisbane or Melbourne FIR. These controllers will only cover above FL245 unless a local TMA controller (APP/DEP) is online. If you see a controller logged on as "YBBB_FSS" or "YMMM_FSS", they'll be covering one of the Upper Sectors. If you're flying, approaching FL245 you should contact the CTR for clearance to enter controlled airspace. As long as you're above FL245 and laterally within these upper sectors when they're online, you should be in contact with them. 

     

    Australia also has 2 major Oceanic sectors. These are known as Melbourne Indian (Controller Callsign ML-IND_FSS) and Brisbane Tasman (Controller Callsign BN-TSN_FSS). When talking to these stations, you may need to use Oceanic Reporting when radar coverage isn't available. There is some basic information here https://vatpac.org/pilots/pilot-tools/oceanic-reporting-tool/. These positions both share the same radio callsign of "Brisbane Radio", regardless of whether they're logged on to the ML or BN position. The oceanic sectors can be further split, indicated by the smaller text and frequencies on the positions chart below. These are usually split during major events and when traffic requires additional controllers to manage the workload. When travelling through our Oceanic Sectors, if you're laterally within their airspace (you can see this on VATSPY) and you're in Class A airspace, you should be in contact with them. 

     

    The most common positions that you'll see filled are Standard Centre positions. These are all of the sectors that have Bold, Larger text on the map below (eg. ORE, ESP, TRT, ARA, ASP etc.). If the controller is logged onto a position in the Brisbane FIR, they'll put "BN-" before the sector (eg. BN-TRT) followed by the position type (BN-TRT_CTR). This is also applied to the Melbourne sectors (eg. ML-SNO_CTR). These positions have been designed to best suit the general, every day traffic we get in VATPAC while adapting the real world setup in the most appropriate way we can. We also have additional sectors which can be used to split the primary sectors. For example, looking at ASP below, we can see that there is also WAR, ASP and FOR (in non bold text) which fall in the area of ASP. If a controller, in accordance with the VATPAC Controller Positions & Ratings Policy, opened up a split, they would own only the area of the split. When they open the primary sector, they have all subsectors/splits in that area. This generally only occurs during events as every day traffic rarely requires the use of subsectors. 

    All centre positions in Australia are simply called "Melbourne Centre" or "Brisbane Centre" on the radio, dependent on whether they're located in the Melbourne or Brisbane FIR. 

    EnrouteSectors_FULL.jpg

    Above is an image showing all of the sectors and sub sectors within Australia. 

    Below is an image displaying YMMM_FSS logged on. This position covers the entire domestic Melbourne FIR above FL245 only. As ML-ESP_CTR (Displayed on VATSPY as YESP) is online, they will own that sector/portion of airspace, not YMMM_FSS. 

    VATSpy_2019-09-22_13-56-49.png

     

     

    Extended Coverage - How do I know where a controller is controlling?

    image.thumb.png.1ea8745034a0f60cc205eed9f1607dc9.png

    This is an image from VATSPY. It is a who-is client that displays online VATSIM traffic including ATC and pilots. VATPAC has updated VATSPY data files available here https://vatpac.org/operations/vatspy-and-servinfo/

    A centre controller can choose to extend to adjacent domestic sectors (adjacent to their primary sector) based on their workload. While they don't have to, it's important to know when a controller is and if they are. what area they cover. As a controller, you need to put this in your controller information. For pilots, you can find this information in a controller's "controller information". There are two ways you can locate this. 

    A) Using a who is client (VATSPY or vattastic)

    B) Using your pilot/controller client. 

     

    image.png.2220246878670a0637e448f778999eeb.png

    image.png.3b5d19d35d735bb5fd0b47bcab5cb6a9.png

    In Euroscope, Go to your controller list > Right click on the controller you want to get info from > Click GET ATIS. It will come in the form of a PM in your chat window at the bottom as displayed. I can see Brisbane Centre (BN-TRT) is extending to ARA and ISA. 

     

    As an example, I am logged onto BN-DOS_CTR. You can see the area I cover per the sectors map above (Covers KPL CVN, DOS, BUR, SDY, GRN sub-sectors). My controller information also advises that I am providing extended coverage to the TBP, MDE and ISA sector which you can also see above. There currently isn't a who-is client which can accurately display where I am extending which is why it's important for both pilots and controllers to understand our sectors in Australia. Additionally, in my controller information, there is a list of airports for Top Down coverage. Top Down coverage means I provide all services from Clearance Delivery at that airport where the local controller isn't logged online. 

     

    As an example, the image below shows how much airspace the CTR controllers logged on are covering with extended coverage. With just 3 centre controllers extending, we cover the majority of Australia as seen by the outlines. I am controlling YDOS (Brisbane Downs Sector) which is lit up Blue. The darker yellow lines indicate the airspace I am actually controlling. It's significantly more than just the sector I'm logged onto. extend.thumb.png.7479d8ebf0a86efab422bc7ff8647ee5.png

     

    What about our Pacific Island and PNG Sectors? They operate very similarly except there is generally no extended coverage. You will find top down coverage available if the controller is providing this service. They'll put this in their remarks the same way they would extended coverage. 

    VATSpy_2019-09-22_12-36-41.png

     

     

    Not Sure? Just Ask! :) 

    Our controllers would rather you ask if you're extending or providing top down coverage than someone not knowing and departing from a controlled airfield. As controllers, we're here to help :D  Please also remember it's not the job of a controller to tell you when to contact us.

     

    Don't forget to discuss this below! We all have things to learn and I hope we can all contribute in some way to learning more about aviation :D 

    • Like 5
    • Thanks 1
    • Confused 1
    • Sad 1
  2. The frequency you input as an observer theoretically doesn't have any affect on who you're listening to. As long as you have the voice channel and voice server set to the same as the controller you're tuning, the frequency and name could be anything else. 

     

    I've never heard of VRC randomly changing frequencies. Strange... 

  3. Thanks to everyone that came guys! We had 8 VATPAC members attend and it was fantastic to meet new people and put names to faces. 

     

    I intend on holding further VATPAC Meetups in November around the time of the Expo. Further information to follow on those :)

     

     

    • Like 2
  4. Hi All,

     

    Sorry for the late notice but a few of us were planning to have dinner on Tuesday night and we thought we could turn it into a proper social event. I’d like to extend the invitation to all VATPAC members who can make it to come out to socialise about all things aviation over some dinner and drinks. 

    I was thinking of somewhere in Victoria Park however this will be dependant on the amount of people who can come.

     

    If you’re interested, please post below, message me on facebook or send me an email. We’d love to get as many of our Perth people together as possible!

     

    Thanks,

    Callum

     

     

    • Like 5
  5. The VATPAC Discord will be returning shortly and we are now looking for potential candidates to assist in the moderation of the service as a Discord Moderator. We'll be moderating Discord differently to how we moderate Teamspeak to ensure consistency and fairness. One major change to the moderation process is the enlistment of Designated Discord Moderators. VATPAC General Staff and Senior Staff are not entitled to this automatically and will be required to apply through the same process as community members. VATPAC Directors will hold the role of Discord Moderator.

    You do not need to be a member of VATPAC Staff to apply to be a Discord Moderator. 

     

    We're looking for candidates who are actively involved in the community, are committed to the online safety of everyone (including minors) and are willing to assist others with navigating the Discord server. 

     

    Reports To

    The VATPAC Discord Administrator

    • The VATPAC Discord Administrator is an Executive Board Member appointed by the VATPAC Board who is responsible for the overall Administration of the server. The purpose of a Discord Moderator is to assist in the day to day administration of the server and where required, refer cases to the Discord Administrator. 

     

    Duties

    • Regularly monitor the voice and text channels of the VATPAC Discord
    • Where required, moderate the voice and text channels of the VATPAC Discord in accordance with the VATPAC Discord Policy and Moderator Guidelines
    • Escalate issues where required to the VATPAC Discord Administrator
    • Assist in conflict resolution between Discord Users
    • Assist other Discord users with using the server
    • Act in accordance with the Expectations of Staff Policy

     

    Essential Criteria

    • Be a VATPAC Discord User (When Discord Launches)
    • Be in good standing with VATPAC
    • Be 16 years or older
    • Be an active member of VATSIM & VATPAC for at least one (1) year
    • Be familiar with the VATSIM CoC and Divisional Policies

     

    How to apply

     

    Members who are interested in being considered for this role should send a brief application addressing their suitability and experience to [email protected] by 2359 AEST on Sunday 8th September 2019. 

    • Like 7
  6. G'day Everyone,

     

    Due to a recent spike in incorrect observer callsigns being used, just a quick reminder to anyone observing, both new and old that you should be logging onto the Network with the correct observer callsign. The callsign format we use is your Initials _OBS. 

    Eg. Mine is CS_OBS 

     

    If CS_OBS was taken, you could add an additional initial (eg. CJS_OBS). 

     

    If you have any questions or queries, just ask :)

     

    • Like 5
  7. Hi All,

     

    I wanted to keep you in the loop about changes to the VATSIM Australia FSD server (The server your VATSIM client connects to). The server has been redeployed and is now known as SYD-1. If your client was previously connecting to the Australia Server, you'll need to select the SYD-1 server so that you can connect to the Network. 

     

    This change is one of many being made to VATSIM's infrastructure to ensure users get the best experience they can when using the VATSIM Network. You can find details on these changes on the VATSIM website https://www.vatsim.net/news/upgrades-vatsim-infrastructure

     

    If you have any issues, please reach out. 

    • Thanks 1
  8. The VATPAC I.T team has a long road ahead with various updates to current systems and new implementations planned. Due to the amount of work planned, we're seeking interest from potential candidates within the community to join the team as an I.T Developer. 


    Becoming a member of the VATPAC I.T team allows you to expand your skill set with the opportunity to work on a diverse range of projects in varying areas of the community.


    Reports to
    As an I.T Developer you'll report directly to the VATPAC Director, I.T.

     

    Duties Include

    • Assist in the development of web, desktop and back-end based applications that will ultimately enhance the VATPAC I.T infrastructure
    • Liaise with the Director, I.T and/or Deputy Director, I.T to set and meet deadlines and targets for assigned project
    • Ensure all projects are compliant with GDPR, VATPAC Data Handling Policy and VATPAC Privacy Policy requirements
    • Work closely in a team to deliver new projects to the VATPAC community
    • Maintain VATPAC's I.T systems as required by the Director, I.T
    • Assist other departments with I.T related queries and projects
    • Assist in maintaining the VATPAC I.T Helpdesk

     

    Essential Criteria Include

    • Be a member of good standing
    • Be able to work well in a team in a voluntary organisation
    • Have good problem-solving skills and are able to 'think outside the box'

     

    A candidate applying for this position will preferably

    • Be a general member of VATPAC for six months at the time of application. 
    • Be able to provide an example/portfolio of previous work.
    • Have good knowledge in one or more of the following
      • Web (HTML, CSS, JS)
      • Backend (PHP, Ruby On Rails, NodeJS, Python)
      • Angular CLI
      • Window Applications (C++, C#, etc.)
      • Support/Administration


    How to Apply

    Members who'd like to submit their interest for the role can do so by outlining any experience and suitability with links to any previous work.

    Expressions of interest should be sent via email to [email protected]

     

    APPLICATIONS ARE IN STRICTEST CONFIDENCE. Applications Close 23:59z, November 17th, 2019.

  9. As announced last night via Oz Flight Sim Expo, VATSIM will be attending the 2019 Expo at HARS. 

     

    This year, VATPAC will be attending on behalf of VATSIM to represent the VATSIM Network to visitors of the Expo and we're looking for volunteers! If you'd like to be a part of the Expo Team, please get in touch with me by emailing [email protected]

     

    The only requirements are that you'll need to be available on Saturday and Sunday (23rd and 24th) of November for the Expo and preferably on Friday 22nd for the bump in. You'll also need to be located in the Sydney/Wollongong area or be able to make your way there (at your own expense) for those days. We'll also be looking for assistance from the community with regards to supplying equipment for our displays. If this is something you would be able to assist with, please get in touch as well. 

     

    For those who don't wish to be a part of the team but want to attend the expo, I'll post further details regarding the Expo soon. I'm currently investigating accommodation in the Wollongong/Shell Harbour area and will provide a list of recommended accommodation soon for those who are interested in travelling for the event! 

     

    Expect further updates soon! :)

     

    Thanks,

    Callum

    • Like 6
  10. It's with great pleasure that I announce Harrison Scott has been appointed by the VATPAC Board as Director, Operations. 

     

    Harrison has been a member of staff at VATPAC for some time now holding roles in the ATC Training, Operations and I.T departments. During his time on the Board as the I.T Director, Harrison gained an important insight into the day to day operations of VATPAC which, alongside his recent work in Operations, has adequately prepared him to take on a role in the Operations Department. He'll be working closely with Peter Story while a transition occurs. 

     

    I'd like to take this opportunity to thank Peter Story for stepping in as Acting Director. Peter not only kept his own work progressing but also took on the workload of the Operations Director and saw through several projects over the last couple of months including Local Instructions updates, AIRAC1907 + 1909 and work on the Euroscope controller client updater. Peter will stay on-board the team as Deputy Director, AIS, supporting the team as we continue to update and bring new content to the community. 

     

    Congratulations and welcome to the team Harrison. 

    • Like 5
    • Thanks 1
  11. G'day All,

     

    I've noticed a trend occurring more and more recently which I feel needs to be addressed.

     

    When flying on the Network, I almost always replicate real world flights, including the gates at both my arrival and departure airports as do many other members. I've observed recently when arriving with ATC, I'll vacate the runway then be given taxi instructions before even calling vacated. The issue is without knowing the bay, a controller could issue incorrect taxi instructions for the location the aircraft is taxiing too. In the real world, an aircraft will report their current position and requested/allocated bay to the ground controller (eg. "Melbourne Ground, QFA401 vacated on Echo for Bay C7).

     

    While not everyone is going to have a preferred gate, the important note here is to give people that opportunity to pass this information along prior to issuing taxi instructions so we can give the correct taxi instructions. If the aircraft calls vacated but doesn't request a bay, giving them taxi instructions to the general vicinity of their operator is perfectly fine. 

     

    Cheers,
    Callum

    • Like 9
    • Thanks 1
×
×
  • Create New...