Jump to content

Ryan M - 1255571

ATS Staff
  • Posts

    90
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by Ryan M - 1255571

  1.  

    Quote

    I am new to all this and had Rob Hooley looking after me (Sydney Approach)... He was very helpful and explained anything I didn't understand. Really made me feel comfortable after being very nervous... Great work!

    Nice work @Rob Hooley, a mentor to the young'ns. +5.

    • Like 5
  2.  

    1. INTRODUCTION

    The VATPAC Operations Department has updated the sector files, Euroscope Client Installer and Controller Client Updater. The version released today is AIRAC 2011, effective on the 10th of September  2020. The sector files provided support the Virtual Radar Client, Euroscope Client, and VatSYS client. Please see below for details.

    2. DETAILS


    1. INTRODUCTION

    The VATPAC Operations Department has updated the sector files, Euroscope Client Installer and Controller Client Updater. The version released today is AIRAC 2011, effective on the 7th of October 2020. The sector files provided support the Virtual Radar Client, Euroscope Client, and VatSYS client. Please see below for details.

    2. DETAILS

    • WLM APP airspace boundary update
    • New YSNW and YPEA airport layouts
    • YMML, YBAS, YPAD airport layout updates
    • Updated coastline for VRC and Euroscope Enroute files to improve client responsiveness for large sector files
    • World Flight Preparation

    Vatsys Only:

    • Australia and Pacific dataset updated for ease of handoff to active adjacent external sectors
    • ALL_SECTORS and FIR_BDRY maps updated
    • Terminal labels available in sector file database included in TAXI_ALL map

     

    3. DOWNLOAD LINKS

    4. AUTHORITY

    Director, Operations – [email protected]


    5. CANCELLATION

    This NOTAM will self cancel on 05th November 2020, unless otherwise noted.

  3. 1.       INTRODUCTION

    The VATPAC operations department is publishing this NOTAM to designate procedures and airspace around the upcoming Panic Stations: Alice Springs event. This involves the creation of two new sectors as well as an addition to the current airspace around the airport.

    2.       EFFECTIVE DATE & TIME
    19th of September 2020, 0900z

    3.       AFFECTED POSITIONS

    -          Melbourne Centre - Alice Springs – 131.800 (ASP)

    -          Melbourne Centre - Alice Springs (East)* - 128.850 (ASE)

    -          Melbourne Centre - Alice Springs (West)* - 121.850 (ASW)

    -          Alice Springs Tower – 118.300 (TWR) -          Alice Springs Ground* – 119.900 (SMC)

    *indicates an event specific position.

    4.       PROCEDURE DETAILS

    4.1   ML-ASP

    This sector will assume responsibility of the Class C and G in the predefined AS sector. All approach clearances (excluding aircraft already in the YBAS CTR, Class D) will be given by this sector.

    4.2   ML-ASW

    This sector will be responsible for the western Class A airspace of the ASP sector, as defined in the green shaded are of figure 1 below.

    4.3  ML-ASE.

    This sector will be responsible for the eastern Class A airspace of the ASP sector, as defined in the red shaded area of figure 1 below.

    4.4   AS_TWR.

    This sector will assume responsibility of the Alice Springs CTR, Class D airspace. The use of radar for this sector is strictly for situation awareness only and may not be used to provide a separation standard. This sector will coordinate any non-auto-release departures into CTA with an appropriate “NEXT” call, and in doing so, obtain and requirements or delays for the departing aircraft. Auto-release SIDS will be co-ordinated at the time of the event between AS_TWR, AS_GND and ML-ASP_CTR. Please refer to the MATS for other coordination requirements.

    4.5   AS_GND.

    This sector will assume responsibility of the YBAS manoeuvring areas as shown in figure 2. This sector will also issue airways clearances to any departures from YBAS but must coordinate with ASP via a “TAXI” if the aircraft is not departing via an auto-release SID into CTA. Auto-release SIDS will be co-ordinated at the time of the event between AS_TWR, AS_GND and ML-ASP_CTR. Please refer to the MATS for other coordination requirements.

    5.       CONTACTS

    Ryan McDonald, Acting Director Operations - [email protected] 

    Joshua Micallef, Director Events – [email protected]

    6.       CANCELATION

    This NOTAM will self-expire on 19th September at 1300z unless otherwise stated by the Director (Operations) or Director (Events)

    7.       APPENDIX

    1. Fig 1 – ASP E-W split.

    image.png.31f6ab4f7a6ca10ebc54eb3b13e74108.png

    1. Fig 2 – ASP manoeuvring areas.

     image.png.99511f99ea51d2619e92c49c3c6529f0.png

     

  4. 1. INTRODUCTION

    The VATPAC Operations Department has updated the sector files, Euroscope Client Installer and Controller Client Updater. The version released today is AIRAC 2010, effective on the 10th of September 2020. The sector files provided support the Virtual Radar Client, Euroscope Client, and VatSYS client. Please see below for details.

    2. DETAILS

    • AYPY, NFFN airport layouts and SIDS & STARS updated - Thanks to @Clem Wu
    • RNAV Updates (YBUD, YCNY, YBHM)
    • YBTL PEWEE6 SID
    • YPPD SSR Radar added for Worldflight.

    3. DOWNLOAD LINKS

    • VRC: Sector Files & POF (please note there are no changes to the VRC POF file, only an updated link for the VATPAC CDN migration)
    • Euroscope: Client Updater & Sector Files
    • VatSYS: Please use the inbuilt updater when prompted.

    4. AUTHORITY

    Director, Operations – [email protected]


    5. CANCELLATION

    This NOTAM will self cancel on 05th November 2020, unless otherwise noted.

  5. 1. INTRODUCTION

    The VATPAC Operations Department has updated the sector files, Euroscope Client Installer and Controller Client Updater. The version released today is AIRAC 2009, effective on the 13th of August 2020. The sector files provided support both the Virtual Radar Client and the Euroscope Client. This will bring changes to SID and STAR procedures, and a mirage of updates to ground maps, sector boundaries and frequencies. Please see below for details.

    2. DETAILS

    • SID STAR, IFR fix updates as per DAP and SUPs.
    • YBSU runway, SID, STAR, airport layout update (updated scenery for pilots provided by Sean Harrison).
    • YBCG Taxiway E extension, YSCB Taxiway B extension, YBRM Apron update.
    • New airport layouts: YAMB, YMES, YBOK
    • SDY Enroute sector boundary change with VATSPY update
    • YSSY TCU airspace boundary update for rwy 25 MARLN STAR and RWY 07 Dir airspace
    • Position Updates: Brisbane Finals 119.25 added, YPTN ATIS updated to 124.0, TN_APP to 120.95.
    • YBBN TCU airspace boundaries updated to the latest diagrams.
    • BN-TSN position now includes ANAU and AGGG airspace in Euroscope.
    • New ADSB sites in PNG: Mt Nauwein, Mt Mission, Mt Konokalang, Mt Dimodimo, Lorengau, Mt Robinson, and Burns Peak.

    3. DOWNLOAD LINKS*

    4. AUTHORITY

    Director, Operations – [email protected]


    5. CANCELLATION

    This NOTAM will self cancel on 05th November 2020.

    *Vatsys Beta users will be able to access this package through the in-built updater.

    • Thanks 1
  6. I just wanted to send a huge thank you to Cameron Wilbraham. He was controlling ML-WOL_CTR today and was absolutely incredible. It was my first flight on the network and despite a ton of flying off network this week in preparation I was still nervous. He was so friendly throughout, gave lots of options, was flexible all while managing traffic in and out of YSSY and YMML. I really appreciate his help, understanding and patience. His professionalism was also noted while speaking with other pilots on frequency. Such a great start to VATSIM and I am so grateful to have had him control this morning.

    Incredibly appreciated. Thanks Cameron for an awesome intro to VATSIM and VATPAC.
     

    Awesome job AGAIN Cameron!!

    • Like 2
  7. 50 minutes ago, Tristan Garratt said:

    If someone logs in with a relief calllsign, then instead of disconnecting and such, the outgoing controller can hand off aircraft, and the incoming can just simply TX/RX the frequency. It makes for easier transfer of control.

    At what point would you change back to the normal callsign? Would this not be the exact same as the aformentioned, only later?

    I do see the benefit in it and am trying to play devils advocate a little. However, I do hope to see you both doing the proper handover briefings online in the future ;)

  8. 8 hours ago, William Teale said:

    Would definitely be more convenient to be able to log in and receive the briefing from the outgoing controller who is still connected, then have them hand over the airspace and freqs. Logging on as an observer doesnt really allow that in full. In particular its not very feasible with the current system to handover a position while traffic is busy. I suspect this hasnt been an issue up to now because its not typical for positions to be terribly busy in VATPAC airspace.

    Hi Bill, can you go into more detail about how logging in as an observer doesn't allow that? What things are you looking for in a handover, and what benefit does logging in with a relief callsign have over an observer callsign?

    The way I see it, the observer would log into to be able to view their airspace, setup the sector information required, copy over ATIS, and do the brief. If you are fully setup, chaning over to the CTR callsign should be a matter of announcing "controller change in progress", the controller disconnecting, and you reconnecting as a controller. I fail to see hopw this takes any more than 15 seconds. Or am I missing something.......?

  9. 50 minutes ago, Angus McKenzie said:

     

    We can’t logon like the UK can with a relief call sign, we only log onto the position once the other has logged off. However, if this could be changed, it would help a lot with handover. Also, our tags don’t stay up to date with TAATS/vatSys, they reset every time a controller connects/disconnects 

    Angus, you can always log on as an observer if time permits

     :)

  10. Hi all, some recent feedback from the community has suggested that people may want to learn more about ATC position handover briefing between units. This post will attempt to outline a little bit more information on how to coordinate a handover, and hopefully give some more insight into this.

    What is the goal of an ATC position handover briefing?

    The goal of a position handover briefing is to ensure minimal disruption to pilots, and the highest possible situational awareness for the incoming controller. A position handover should be done with both controllers looking at the scope, in an environment free of distractions (for example, Discord co-ordination rooms, or the VSCS function of your controller client).

    What does an ATC position handover briefing look like?

    An ATC briefing should use the checklist “RAWFNTO”.

    ·         Runways – what runways are in use?

    ·         Airspace – what is the current airspace config in use? Are there any runways released to SMC.?

    ·         Weather – any diversions due weather? Any cells worth mentioning? TEMPOS, SIGMETS, ect.

    ·         Facilities – is everything working?

    ·         Navaids – anything unserviceable?

    ·         Traffic – provide any relevant traffic information – is anyone on a vector? What is your sequence? Who is taxing?

    ·         Outstanding actions – What are the outstanding actions for the aircraft? Is there any coord required? Do you need to give an aircraft an onwards clearance? Does an aircraft require landing clearance?

    An example for the following situation could be:

    coord.png.44c628a9f7484a32d36d7dfc8f878930.png

    Quote

    “G’day Harrison, Runway 19L, runway 19R available upon request, weather is good but expecting a change to easterlies on the hour, everything is working, ILS for 19R unserviceable and has false indications reported so we have been assigning runway 19L. Traffic, RBA1352 at BENBO is cleared the ILS runway left. UAE401 descends via the STAR to 5000. ZOD tracks direct the control tower for an overfly and then city orbits, currently with a clearance limit of the control tower, not above 1500. Coordination for ZOD with the tower controller for the overfly and onwards clearance and to cancel auto-release is still outstanding. Any questions?”

    This is by no mean a complete guide on what your handover briefings should consist of, and you should always be ready to adapt to the situation being presented in front of you. Any questions, feel free to ask below and a staff/training member will try to answer as best as possible :D

    • Like 4
    • Thanks 2
  11. From the MATS

    2.12.7.7 Issue to aircraft required to hold short of a runway intersecting the taxi

    route, a taxi instruction limit of the associated holding point.

     

    2.12.7.8 Do not include instructions past an intermediate hold short instruction in

    taxi instructions.

    Since we would be required to hold VOZ690 short of 24, being an active runway with no coord taking place; the correct option would be C. Note that in Australian airspace a clearance limit is given on taxi instructions and to save confusion, information should never exceed the limit given.

     

  12. Hi Avi and those else who are reading,

     

    There were a few issues with applications this time around with a large amount of them not getting through the system. We believe this is to do with a VATSIM SSO bug through mobile devices. If you would like to control, but do not see your name on the roster here; please send an email through to [email protected] and we can sort it out. If not, jump onto the teamspeak on the day and we will see if we can slot you anywhere.

     

    Sorry for the inconvenience!

     

    Ryan

×
×
  • Create New...