Joel R - 891193
-
Posts
313 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Calendar
Posts posted by Joel R - 891193
-
-
I think that Euroscope is definitely better and easier. The VATPAC AIS team provide you with an installer to get all the "fumbling" out of the way. You can simply install, open select the TMA you want and start controlling.
-
Good afternoon everyone,
I wish it was under happier circumstances that I was posting today. It is with a great loss I need to reluctantly announce the resignation of Peter Story as Deputy Director Aeronautical Information. Peter has been in this role now for over two years and has pushed VATPAC from one strength to another. He has kept us all updated on airspace and has implemented huge improvements to the way we handle AIRAC updates, ATC Assist, VATSPY and ServInfo. Peter's departure is going to leave a huge hole in the AIS Team with big shoes for the replacement to fill. On behalf of the VATPAC Staff and members I would like to thank Peter for his hard work and counsel during his time in the role. We also owe him a great debt for the work he has recently done in over seeing the biggest change in VATPAC airspace for nearly 10 years.
Over the next month, Eoin Motherway will step up as Acting Deputy Director Aeronautical Information. I would also like to announce that Sean Harrison is taking a more senior role as the Assistant Deputy Director Aeronautical Information - Pacific. Sean is going to be critical in furthering the work of sector files and information for the Pacific Islands. This area has been long over looked and from this hopefully some events on the islands would be in the winds.
Over the next few days I will advertise the vacancy of the permanent DDAIS. Peter has agreed to be around for the handover of this role when the permanent replacement is found.
Once again, thank you Peter and I hope to see you flying soon with your spare time.
-
Hi Zach,
VATNZ has asked VATPAC to staff these positions as they are not able to. The Roster will take precedence in VATOCE as per the controller agreement and the request from VATNZ.
-
NOTAM 02NOV16 - RESERVED POSITIONS FOR WORLDFLIGHT 2016
1. INTRODUCTION
This NOTAM is detailed in accordance with Part 4 Division 1 Paragraph 25 (1)-(3) of the Controller Positions and Ratings Policy 2015. This is for the purpose of WorldFlight 2016 and will be for the times as listed below.
2. DEPARTURE LEG
The following positions will be reserved between 0800-1100 AEST 06 November 2016:
(a) Sydney Delivery
(b) Sydney SMC & SMC East
© Sydney Tower & Tower East
(d) Sydney Approach & Departure
(e) Melbourne Centre BIK
(f) Brisbane Centre ARM
(g) Brisbane Radio
3. ARRIVAL LEG
The following positions will be reserved between 0300-2000 AEST 12 November 2016:
(a) Brisbane Centre TRT
(b) Brisbane Centre ASP
© Alice Springs Tower
(d) Melbourne Centre BKE
(e) Melbourne Centre MUN
(f) Melbourne Centre YWE
(g) Melbourne Approach & Departure
(h) Melbourne Tower
(i) Melbourne SMC
(j) Melbourne Delivery
(k) Melbourne Centre WON
(l) Melbourne Centre TAS
(m) Hobart Tower
(n) Hobart SMC
(o) Melbourne Centre SNO
(p) Melbourne Centre HUM
(q) Canberra Approach
® Canberra Tower
(s) Canberra SMC
(t) Melbourne Centre BIK
(u) Melbourne Centre WOL
(v) Sydney Approach & Departure
(w) Sydney Director
(x) Sydney Tower & Tower East
(y) Sydney SMC & SMC East
(z) Sydney Delivery
4. SPECIAL POSITIONS
In addition to these positions, the non-standard special purpose positions are approved:
(a) Alice Springs Director - 126.10 - 40nm radius on YBAS SFC-FL120
(b) Hobart Director - 126.10 - 40nm radius on YMHB SFC-FL120
5. CONTACT
For operational matters, contact [email protected]
6. DISTRIBUTION
This NOTAM is issued by VATSIM Australia Pacific (VATPAC) and shall be distributed via:
(a) VATPAC Forums
© WorldFlight Forums
7. CANCELLATION
This NOTAM self-cancels at 12 November 2016 2359 AEST.
-
-
Guys, please refrain from using this just for the minute. I'd like to discuss this with AIS first.
Cheers
-
NOTAM 26OCT16 - CHANGES TO VATPAC AIRSPACE
1. INTRODUCTION
The existing enroute sectors of Australia were developed many years ago and they were loosely based on some real world sectors. Some sectors had names or frequencies that were not associated to any real world links. Through the use of our sector file program and references to real world documentation, we have developed a precisely accurate depiction of Australian Airspace.
While it is not possible to exactly replicate real world, we have made a concerted effort to hold the realism to account. This change to airspace will be introduced in the next AIRAC release in early November.
2. EFFECTIVE
This change will be effective as of 9 November 2016 1400 UTC. AIRAC1612 will be available to download including an updated Euroscope VATPAC Package Installer from 8 November 2016 0800 UTC on the VATPAC website http://www.vatpac.org.
2. STANDARD SECTORS
Standard sectors are those which controllers with a C1 rating may open on a regular occasion. No permission is required to open these. The image below shows these sectors and the associated new callsign and frequencies where appropriate. Extended coverage is possible provided that:
(a) You only extend your coverage to sectors that share a common boundry
(b) You must be able to cover the whole sector using up to four visibility points with a diameter no larger than 400nm, as this is a radio range limitation set by VATSIM
© You must advise pilots via your controller information which standard sectors you are covering i.e. Extending coverage YDOS, YWOL
The following are the standard sectors in Australia:
BN-ARA_CTR 133.700 Brisbane Centre Arafura *
BN-DOS_CTR 135.600 Brisbane Centre Downs *
BN-ISA_CTR 125.200 Brisbane Centre Isa *
BN-MDE_CTR 133.000 Brisbane Centre Mudgee *
BN-TBP_CTR 120.550 Brisbane Centre Tabletop *
BN-TRT_CTR 133.200 Brisbane Centre Territory *
ML-ASP_CTR 131.800 Melbourne Centre Alice Springs *
ML-BKE_CTR 128.200 Melbourne Centre Bourke *
ML-ESP_CTR 123.950 Melbourne Centre Esperance *
ML-ORE_CTR 127.000 Melbourne Centre Ore *
ML-SNO_CTR 124.000 Melbourne Centre Snowy *
ML-TAS_CTR 123.800 Melbourne Centre Tasmania *
ML-TBD_CTR 125.300 Melbourne Centre Tailem Bend *
ML-WOL_CTR 125.000 Melbourne Centre Wollongong *
3. NON-STANDARD SECTORS
Non-standard sectors are used for events or period of high traffic volume where the workload of one standard sector controller would be inefficient or detracting from the experience of live ATC. In these circumstances a C3 controller or Deputy Director or above may approve the opening of a non-standard sector. A map showing all the non-standard sectors is attached.
The following non-standard sectors will be available when approved:
BN-ARM_CTR 130.900 Brisbane Centre Armidale
BN-BAR_CTR 123.800 Brisbane Centre Barra
BN-BUR_CTR 123.000 Brisbane Centre Burnett
BN-CVN_CTR 133.800 Brisbane Centre Carnarvon
BN-GRN_CTR 120.300 Brisbane Centre Grafton
BN-KEN_CTR 120.150 Brisbane Centre Kennedy
BN-KIY_CTR 133.400 Brisbane Centre Kimberley
BN-KPL_CTR 125.900 Brisbane Centre Keppel
BN-MLD_CTR 132.350 Brisbane Centre Maitland
BN-OCN_CTR 128.600 Brisbane Centre Ocean
BN-SDY_CTR 134.400 Brisbane Centre Straddy
BN-STR_CTR 134.400 Brisbane Centre Sturt
BN-SWY_CTR 133.200 Brisbane Centre Swampy
BN-WEG_CTR 132.450 Brisbane Centre Warrego
ML-AUG_CTR 127.050 Melbourne Centre Augusta
ML-BIK_CTR 129.800 Melbourne Centre Bindook
ML-BIL_CTR 132.000 Melbourne Centre Billabong
ML-CRS_CTR 135.800 Melbourne Centre Cross
ML-ELW_CTR 123.750 Melbourne Centre Eildon Weir
ML-FOR_CTR 132.700 Melbourne Centre Forrest
ML-GEL_CTR 121.200 Melbourne Centre Geraldton
ML-GTH_CTR 122.750 Melbourne Centre Griffith
ML-GVE_CTR 133.800 Melbourne Centre Grove
ML-HUM_CTR 132.200 Melbourne Centre Hume
ML-HYD_CTR 118.200 Melbourne Centre Hyden
ML-JAR_CTR 133.700 Melbourne Centre Jarrah
ML-KAT_CTR 133.500 Melbourne Centre Katoomba
ML-LEA_CTR 122.400 Melbourne Centre Leeman
ML-MOR_CTR 133.700 Melbourne Centre Morris
ML-MUN_CTR 132.600 Melbourne Centre Mungo
ML-OXL_CTR 128.500 Melbourne Centre Oxley
ML-PIY_CTR 133.900 Melbourne Centre Pingelly
ML-TFR_CTR 125.400 Melbourne Centre Telfer
ML-WAR_CTR 124.900 Melbourne Centre Warburton
ML-WON_CTR 135.300 Melbourne Centre Wonthaggi
ML-WRA_CTR 132.800 Melbourne Centre Woomera
ML-YWE_CTR 134.320 Melbourne Centre Yarrowee
To view a full version of the sector images with all the non-standard sectors, click here: http://www.vatpac.org/operations/files/161026_All_Sectors.jpg
4. CONTACT
For operational matters, contact Joel Richters, VATPAC Director Operations, at [email protected]
5. DISTRIBUTION
This NOTAM is issued by VATSIM Australia Pacific (VATPAC) and shall be distributed via:
(a) VATPAC Forums
(b) VATSIM Forums
6. CANCELLATION
This NOTAM remains current until otherwise cancelled or superseded.
-
When I try doing this, if I switch to a frequency with a controller on I get an error "Specified voice channel does not exist." This error appears only on vPilot
Hi Jacob,
When you are using AVC, all voice channels are manually connected to. AVC will prohibit vPilot from automatically tuning to a frequencies voice room. If you are not using CTAF, just don't open AVC and vPilot will operate as normal.
-
Is the VATPAC CTAF procedure/guide document still in the library? Could probably just add Joel's feature to that doc save duplication.
We still have the document... just not on the web as it didn't comply with the VATSIM Policies
-
Is it worth including in the above, that your radio freq should also be tuned correctly in case of text only pilots.
So that you can still receive text messages as required by VATSIM, but also the correct CTAF freq.
E.G.
Text COM1 122.800 Voice rw1.vatpac.org/unicom-au
Text COM2 118.300 Voice rw1.vatpac.org/YAMB
That keeps everyone happy and compliant, in my humble opinion.
A very good idea in the perfect world. AVC will only allow one voice channel at a time. Until there is a decision by the BoG and an update to vPilot, thats not possible.
-
Good evening all,
VATSIM Board of Governors are currently in the process of considering the proposal of Voice UNICOM/CTAF. However, Australia has been using voice CTAF for a number of years. This all fell by the way side when we got P3D and vPilot. Custom voice rooms are not currently possible through these clients, however there is a work-around.
The reason I post this is the VATPAC VFR daily focus events heavily use the old voice CTAF through FSInn, which has caused many members to downgrade their flight sim experience just to be able to communicate with everyone else.
Step 1
Download this zip file (http://www.vatpac.org/operations/files/AVC.zip 1.1mb). Inside is a program called Advanced Voice Client or AVC. Install this program to where ever you like.
Step 2
Feel free to start up all your software that you use to fly EXCEPT vPilot.
Step 3
Start AVC however do not connect. By starting this app, you want to have it use the port to stop vPilot from using it, this gets allocated on a first come basis. If you have never use AVC you will need to use your VATSIM CID and Password, and select a server (the Australian server is not in the list, just select one of the others). Make sure you setup your mic and the other audio details. When you do connect, you must use the same callsign as you will in vPilot.
Step 4
Start vPilot and connect to the network. You should receive and error saying it couldn't connect to the port. Just disregard, this is not important and is what we want.
Step 5
Connect to a voice room using AVC. The voice rooms that Australia uses are fairly simple to understand.
When you are flying into a major airport, one that is manned H24 in the real world; you will need to connect to rw1.vatpac.org/unicom-au.
To connect to an airport CTAF, the general rule is to use rw1.vatpac.org/XXXX - where XXXX is the four letter ICAO code e.g. YHOT. There are likely to be exceptions to this rule, especially when there might be multiple airports in the same vicinity.
Happy VFR Flying
-
I think the wording would be "ABC, cleared for the visual approach runway 26, report vacating runway"
-
So I have spoken to Essendon Tower to seek clarification. We are all beating around the same bush. After tower hours, 118.45 is transferred to who ever is least busy in the ML Control Room. This is 9/10 the planner, which is no doubt what we would consider FLOW.
John advised that the APP Controller would ask them to contact 118.45 before landing as to allow the pilot situational awareness of what is happening in Essendon.
The reality is that someone needs to take ownership of this job. Regardless of who it is, if I was ML APP and there was enough traffic to warrant DEL, GND, TWR, APP & DEP to be online, I would not want to be contacted by aircraft in Essendon to ask for airways clearance, or to advise me they are taxiing or vacated the runway. I would want someone who is less busy like DEL to be taking these advisory calls; leaving me to control the aircraft manoeuvring in to ML. If ML APP is the only person online, this is a no brainer.
I don't think we need to water down procedures just because we are simulating flying, the same procedures apply and this would only need to be educated to those who want to fly here. There are an avg of 15 movements at YMEN each month online, and most of these are done when no controllers are online.
-
The point is that ML APP doesn't own the runway, just the airspace. So ML APP doesn't know nor care if there is an aircraft on the runway. Its the pilots job to make sure the runway is clear.
-
Cut me some slack mate! I've been away for 8 years! (Well that and my undeniable antiquity and the afflictions to which ancient flesh is heir! ;D)
Fixed above!
Sorry Richard, I was just trying to clarify.
I have attached an extract straight out of ERSA which I have amended to cater for VATSIM use.
-
Not quite Richard. You can perform the tower closed procedures.
In VATPAC the only services below an APP/DEP that are stepped down is for H24 services. If the airfield has an tower closed component, it is only considered open when that position is being filled.
Same as Canberra... hint hint 😉
-
So my expectation is that the top down rules for VATSIM apply. The reason you would contact DEL is because DEL is the service providing the departure clearances. APP is not giving landing clearance so this is at the pilots discretion. Thence APP doesn't care whether the runway is clear.
-
Looks good Zach. I like the mobile responsive theme
-
All good advice. I would simply add that if all positions where manned except EN TWR then the clearances are from ML DEL, and the advice of clearing the runway after landing is with ML DEL.
-
Go to this link for more information: https://www.facebook.com/events/1707769709547661/?ti=icl
-
Sean, can you send me that file so we can upload it on the website.
Are you interested in doing any others out that way?
-
Brodie, can you please contact me at [email protected]
-
Maybe it should be in the helpful links box
-
2.5h flight time is probably the limit of a milkrun. Longer events should be on holidays
Thanks for the Friday VFR
in General
Posted
Well the Friday Night VFR event went well and had some interesting twists as far as scenery. Great choice guys and thank for waiting for me to get there.