-
Posts
1812 -
Joined
-
Last visited
-
Days Won
88
Content Type
Profiles
Forums
Calendar
Posts posted by Zach B - 1217663
-
-
I think the code is somewhere on the VATPAC server still...
Something along the lines of ATA (ATC Training and Administration).
-
I was even building something about a year and a half ago along these lines. Still have the code on my computer!
- 1
-
The procedural towers regularly use the VOR for separation...at least they do where I fly.
Things are starting to transition to GNSS now.
This...
QuoteQ-Link Six, Cleared to Sydney on the 155 Tamworth VOR radial to OLTIN planned route, climb to 8000, squawk 0154
Became this...
QuoteQ-Link Six, Cleared to Sydney on the 155 GNSS track, reference the Tamworth VOR to OLTIN planned route, climb to 8000, squawk 0154
and it will eventually become this...
QuoteQ-Link 6, Cleared to Sydney via OLTIN planned route, climb 8000, squawk 0154
- 3
-
-
Great initiative David!
- 1
-
The new system has the capability for voice CTAF.
We are currently exploring what policies need to be adjusted/introduced to support this technology.
- 2
-
What do you mean VHF simulation? The new voice system has VHF simulation?
-
DAP plates will (no doubt) change for the AIRAC active 08NOV18.
- 2
-
Yep, I just overwrite the sector files and good to go, that way I don't lose any of my existing settings/preferences.
-
Good comments by all.
One person has (in my opinion) the correct answer and they know who they are.
Does anybody else want to contribute their ideas OR +1 somebody else's?
- 1
-
Good discussion...
Further details, the VFR aircraft is a C172 doing 110 knots.
How does this change your response (if at all)?
-
You are controlling Melbourne Tower on a busy Milk Run Monday when a new pilot requests clearance for VFR circuits. Current ATIS information indicates VMC conditions, runway 34 for arrivals & departures and wind 030 at 10 knots.
What is the most efficient, safe and friendly way to handle this traffic?
And discuss.....
-
Hoping to be able to get on and help this weekend.
Send me a message on the new discord to see if I'm around to take-over.
- 1
-
We are usually pretty good at these.
I think we won all three last time we attempted it!
- 1
-
ATC booking system.
Booking details posted on the main page, so that if you plan to control, pilots know where to fly. Won't always work (if someone decides in-the-moment they want to control) but might improve traffic at events (like regionals), given pilots can see that there will be ATC.
- 1
-
GA Madness
in Events
Might come and test the local knowledge of the controllers...
-
Looks good mate, pretty awesome!
- 2
-
This should probably be updated with links to the Google Drive or un-stickied.
-
Finally..! A newsletter!!
Make use of the exposure to ~600 members and make sure it's a good one. Hopefully, Dan can put some stuff together from ATC training to throw in; if I have time i'll throw some ideas around).
Deadline for submissions?
-
Can I ask, was he told to cease or did he ask to cease?
Sorry to hear you go Eoin..
-
Thanks Quiqs!
-
Should have been locked about 10 post earlier then Tracy..!!
-
Respectfully, the supervisor book needs some editing (I still have a copy of it from when I was a supervisor), not Gregs...
He is right, the supervisor processed the .wallop as per the book, following the procedure and they asked a legitimate (albeit, uneducated) question about the extended coverage.
There is nothing in the supervisor book with regards to the specific of extended coverage in Australia. As Pete and many other people already said (well above the fluff that the thread as turned into), it's a simple email to VATSIM to ensure some communication is sent out directly to all the SUPs.
The only people who should be commenting on whether the SUP followed the correct policy, are SUPs themselves; i.e Kurt, Tracy (Greg and Me as ex SUPs).
Stay friendly..!
-
Pretty cool mate.
Is there any way to override the automation? I was controlling Tamworth the other day and there was a variation with the METAR format, meaning none of the variables were showing correctly (cannot remember what the formatting issue was though).
YBCG ILS
in Airspace
Posted
Sydney needed to build the runways so that the centrelines were > 4300FT apart, to be able to do independent instrument approaches without PRM.
The new BNE runways are ~6500FT apart so won't need PRM approaches.
They could close the STARs (for example, when it's quiet on VATSIM, I often tell aircraft to track NASHO -> SOSIJ) but since it's busy at SYD I'm sure they'd end up canceling the STAR on downwind and extending the downwind leg as required to maintain the sequence - might as well leave it as is.