Jake S - 927562
-
Posts
2250 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Calendar
Posts posted by Jake S - 927562
-
-
As BRM and KA positions are new, vRoute does not yet recognise them as belonging within a particular FIR. You'll notice if you try to book the position using vRoute, you can't as it's not yet in the list of available positions. So when the website component asks vRoute who's booked in the respective FIR's it doesn't supply the information about BRM or KA bookings and subsequently they aren't shown on the page.
vRoute will eventually update to reflect these positions, but not until they have been opened online for a while and are reflected in the VATSIM statistics. So in short - if you want them to display you need to control them online first!
-
Thanks Kirk and Daryl... medical to go before I start celebrating too much
-
Stickied. Looks great John :thumbs:
-
Hi All,
As most EuroScope users should know, EuroScope provides controllers with the capability of generating a Voice ATIS using pre-recorded voice samples. The voice samples are combined together by ES in order to form a complete ATIS. The benefits of using this method to create a voice ATIS are twofold; you don?t have to take the time to record the ATIS using your own voice in one hit, and for pilots the voice quality and constant speech rate make listening and deciphering the ATIS much easier.
We have finally put together a more or less complete voice ATIS package using text-to-speech software for use with EuroScope, and it can now be found on the VATPAC website under ATC Software.
Thanks to Luke Bruce-Smith and Andrew Harle for their help in compiling the wave files.
:banana:
Version4 Uploaded to Website - LBS
Reuploaded to website with two additional sounds by Kirk Christie - DZ
-
I actually remember reading that and thinking the same thing :2banana:
-
Well said guys. A stress ball is a worthy investment :banana:
Remember where you are and where you came from and just try to have a bit of fun in the process.
-
David,
As David and Shannon have highlighted, it's more a case of someone donating their time and knowledge to jump in and write one. It can be quite involved so is certainly no easy task.
If you (or anyone else) are willing to donate some time we're always looking for more hands in the Documentation Team to help with writing more documents and maintaining current ones. PM or email me if you're interested.
-
Now you guys get to write "I survived a breakdown of runway separation to win Panic Stations!"
:party:
-
I should also mention that the SY TMA split is shown in the sectorfiles as a "STAR" so you'll need to venture into your display settings/diagrams to activate the lines.
There are also some additional labels to emphasise the vertical limits of the sectors.
-
Guys,
My apologies for not being able to get this out sooner - hard to do when you're stuck at work for the vast majority of the weekend
If you're rostered on you'll receive a copy in your inbox shortly, otherwise I've attached everything here.
-
Yes Hayden I'll be doing up a briefing after work this afternoon. Stay tuned.
-
Fixed.
-
a) A METAR gives a brief report of current weather conditions for a given location.
The amount of detail within these reports vary from location to location. For example Melbourne's VATSIM METAR (in VRC press F7, type YMML (or any other airport code) and hit enter) reads:
YMML 180300Z 15007KT 9999 VCSH FEW010 SCT035 BKN050 15/13 Q1017 INTER 0300/0430 4000 SHRA BKN010
Which is formatted like this:
>[airport icao] [time observed at] [winds (xxx degrees yy knots)] [visibility (xxxx metres)] [weather and cloud] [temperature/dewpoint] [QNH] [extra remarks]
b) Tower can amend all details of the flight plan by bringing up the flight plan window using F6. You must be connected as a controller to change any of the details. Any changes made would be communicated to the pilot through an amended clearance, or airways clearance.
c) A Squawk Code is a 4 digit identifier that pilots enter into their transponder. The transponder transmits altitude and position information to ground based radar stations, allowing controllers to "see" where an aircraft is on radar.
The squawk code allows one of these radar returns to be identified as a specific aircraft, or a category of flight. For example, all VFR aircraft squawk 1200 unless told otherwise. A controller assigns a unique squawk code when he needs to identify a specific aircraft, this is done in VRC using the F9 key.
d) The POF file contains a whole host of information relating to the ATC Positions that we control online. The POF file is only for ATC clients, and has no impact on pilots. Some of the things it does: Defines an assignable squawk code range for each position, defines the expected primary frequency of each position and the 2 or 3 letter identifier for each position (ie. you'll see that ML-CAN_CTR is labelled as CY in the controller list).
Controllers need to download the latest version of this file from the VATPAC website (under sectorfiles) and point their ATC client to the location of this file on their computer.
e) Pilots should vacate the runway via the first available taxiway and once clear of the runway come to a stop on that taxiway until ground can give further taxi instructions.
f) Correct, Tower should not electronically track any aircraft.
g) Approach does not electronically hand off the aircraft, rather they are just instructed to call tower on tower's frequency once approach has finished with them.
h) The localiser (abbreviation LLZ) is a navigational aid that helps pilots establish on the runway centreline and track to final. In an Instrument Landing System (ILS) this is coupled with a Glideslope which helps pilots fly the correct approach to the runway.
These approaches are typically used when poor weather conditions exist and the pilots can't physically see the airport/runway.
i) VRC is unable to plot airways, but should show you the general direction the flight is taking.
The decodes like this:
Flying DIRECT to ML,
then via airway H66 to JCW,
then via airway H185 to BN,
then DIRECT to the airport.
j) Standard Instrument Departure (SID) and Standard Arrival Route (STAR).
These are a set of predefined departure and arrival procedures that are used at bigger airports to facilitate the movement of aircraft. They usually replace the beginning or ending of a pilots route (respectively) and take them via a set of FIXES and Navaids from/to the runway.
SID's/STAR's can be found in pilot or ATC assist as well as where they are published here: http://airservicesaustralia.com/publications/current/dap/AeroProcChartsTOC.htm
Clearance Delivery assigns SID's (or whichever controller is covering the clearance delivery role ie. Tower usually) as part of the aircrafts airways clearance.
For example a typically airways clearance will go like this:
"QFA123 cleared to Sydney via DOSEL flight planned route, maintain 5000, DOSEL 7 departure, squawk 1234, departures 132.0"
Note how the controller has replaced up to DOSEL in the pilots route with the DOSEL 7 departure.
STAR assignment is done by the Centre controller.
------------------------------------------------------------------
And Arjun's beaten me to the rest, so I'll post this anyway.
-
Updated. Thanks Ben.
-
Can't keep everyone happy all the time James :wall:.
If anyone would like SNO post below/PM me.
-
Thanks to everyone that applied :banana:. We had quite a high number of applicants, so apologies to those who missed out on their preferred position..
>ML-BIK_CTR Arjun Murthy BN-ARL_CTR Alex Gielis ML-SNO_CTR Scott Partington ML-BKE_CTR [color=Red]Vacant[/color] SY-N_APP Alexander Lynskey SY-S_APP Steven Brown SY-D_APP Andrew Harle SY_DEP Hayden Manuka SY-E_TWR David Zhong SY_TWR Sam Schiphorst SY_GND Matthew Ellem
The observant of you will notice that there's a few extra positions in there, I'll be posting details of how things will operate closer to the event so stay tuned.
As always it is an expectation that the controllers will log on with enough time to get set up and be ready before the first lot of aircraft will enter that position. This means that it's a good idea for the CTRs to log on up to a few hours before the landing time of 0930z and APP and TWR controllers should be on by 0830z. If assigned controllers are not present in their positions by this time they may be given to another controller. If you believe you will not be able to make it either at all, or within the recommended time to spare, please contact me ASAP.
Good luck :thumbs:
-
Sounds good Hayden.
Perhaps you should contact Merv over at Austscene (they provide SID's & STAR's for PMDG/Level-D for free). Many hands make light work
-
Cool bananas. The forums look good too.
-
It would be nice Alex (in fact I requested it of the ES developer a while ago), though James has pointed out the technical problem prohibiting us from doing this now.
I've attached a sneak peak of what the ATIS will sound like using the VATPAC voice files.
-
:whistle:
I just need to polish some things off, but yes, we have a full set of recorded voice files for use with the ES Multiple File ATIS. Coming soon.
UniATIS could also be set-up to reference these file names if that is something someone might find useful?
-
Not that I'm aware of Sam. There seem to be quite a few for different airports on the UniATIS site, I haven't looked into what it takes to get one setup and running well.
-
I could imagine the 'Imperial March' as a suitable soundtrack to that bunch being on the horizon
Certainly lots of cannon fodder flying the YBBN-YSSY route, look forward to seeing the official stats.
-
-
For the purposes of clarity - I think David is referring to just being able to see the actual position of the aircraft on the ground at an airport.
EuroScope and TAAATSMod are simulating radar coverage using the actual locations of radar and ADS-B beacons, and as such radar coverage on the ground at most locations is non-existent. But even if there was radar coverage, aircraft are not squawking Mode C so you will not get any correlation between the return of the aircraft (the little '+' symbol for a primary only return) and the aircraft's flight information. This is true to real life.
Now this is also why if you track an aircraft who is on the ground, all you will get is a Flight Plan track (the square symbol).
This is fine so long as you aren't providing any TWR services. If you are extending down to say ML TWR, you'll obviously need to be able to see the actual location of the aircraft to simulate "looking out the window" or using the A-SMGCS equipment available at some airports. There are a couple of ways to go about doing this. One method would be to use the EuroScope ground modes as described by Kirk. Another method (this is what I do) is connect VRC to the EuroScope proxy as Arjun has said, allowing you to see the exact location of all aircraft whilst retaining TAAATSMod/ES radar simulation goodness.
You can find more information on how radar simulation etc. works in the TAAATSMod Moodle Course.
Saturday Afternoon Flight - YBRM/YPKA
in Regular Events
Posted
Thanks to those that turned out, what quite enjoyable on PIL with lots of procedural separation to worry about