Will R - 1097663
-
Posts
376 -
Joined
-
Last visited
-
Days Won
12
Content Type
Profiles
Forums
Calendar
Posts posted by Will R - 1097663
-
-
Just a little heads up, a lot of routes into and out of the SY basin to the North and North West are changing.....also, SIDs and STARs into WLM!!
The ENTRA SID out of Sydney is gone, replaced by the new OLSEM SID.
Old R559 Restricted area is gone, replaced by R560 and R570 plus LOTS of route changes between Coffs and SY.
-
1
-
-
Hi all, someone might be interested....but Airservices is looking for SSOs in Sydney....basically simulate aircraft for ATC training...good money for those with an aviation background.
Ad appeared on Seek today
Cheers
Will
-
Remember people, do NOT use the ASISO SID unless doing SODPROPS....I can see some of you using the ASISO for departures to SANEG off 01R....you dont need to...there is a dedicated SANEG SID off runway 01R.
ASISO provides an immediate right turn to a transition to SANEG, WACKO etc to turn inside the arrivals for runway 19R....it is SODPROPS only.
Also another mention, taxiways A5 and A5S were decommissioned over a year ago....in the past only XP11 scenery had this but now that Orbx has amended their scenery hopefully can be shown...
The taxi flow for NPR still has fixed one way traffic, no matter what.......from existing terminal to the new runway, use taxiway Y. From the new runway to the terminal, always use taxiway Z.
-
2
-
-
Lots of corrections, changes to signage, added new fire station, etc.
https://forums.x-plane.org/index.php?/files/file/48557-brisbane-international-ybbn-2020/
-
1
-
-
new Brisbane runway is now open....it was an interesting event....atc feed here, with the voices of Mick B and Paigey in Brisbane Tower.
-
3
-
-
New runway due to open in just under two weeks.....today was the last chance to get a visit....for those curious..
-
3
-
1
-
-
8 hours ago, Nicholas Gilbert said:
They're already official and already in use real world, they just didn't make it in time for DAP 163. They did a similar thing with Hobart.
Just to be clear they are not in use yet. Only in airline training and internal training until the new runway is commissioned. There were lots of delays in the design of the procedures for many reasons, mostly outside control of ASA
-
1
-
-
1 hour ago, Pheonix Taylor said:
With the latest Airac, Runway 18/36 has just been decommissioned. Runway 18 south of taxiway A has now become taxiway F. Runway 13/31 has become commissioned however appears to still be under construction and their are not approaches available for the new runway. How would be the best way to provide ATC services to pilots on Vatsim?
it has not been decommissioned.....it should have happened but has been put back to June...there are NOTAMs and advisories about it.
Existing runway will indeed become taxiway Foxtrot south of the new extended centreline of 13/31, the remainder of 18/36 will be pulled up.
New taxiway Alpha will run parallel to the runway but only to the halfway point...exits are A1 and A2...there will be lots of changes to the Airline Apron, new gate numbers etc....but until June....nothing changes.
-
2
-
2
-
-
1 hour ago, Craig Deitch said:
The removal of A5 and A5S was an interesting decision for those who are curious. There were two reasons:
1) Removal of the first rapid exit reduced runway occupancy times! A number of aircraft would try to make the first exit, miss it and taxi slowly off on the second exit. That would cause an bit of angst for the ADC if the gap to the next arriving aircraft was tight and they had lined a departure up in the middle. If the vacating aircraft took too long it could cause a go around.
2) It also reduces taxi times and taxiway congestion for aircraft going to 01L, especially out of the International terminal. They have to taxi on A but they can’t cross the exit of the Rapid Exit Taxiways if an aircraft is about to land on 01R. So they might have to hold short of the first RET, cross it and hold short of the second RET, then proceed to 01L. In simulation it could add 5 minutes to the taxi time.
BAC was reluctant to close A5/A5S because they were concerned some pilots might use it anyway. And they were right, it did get used after closure by a few pilots even though it had big crosses on it and no lights... Hence the extra work to hide it completely!
Yup, and it even lead to a nasty incident and a very experienced controller getting tea and bikkies.
the arrivals have a bit of meaning as well. All the A stars are strictly for ILS....and the X, M, W or Z arrivals lead directly to the X,M,W or Z approaches.
Gold Coast arrival is no more, so all aircraft from Sydney or the East Coast plan via GOMOL which is co located with the airport....the blokes in that sector were given 7 choices of name and apparently GOMOL was the winner....you get that...
-
1
-
-
Greetings guys, just a couple of things to help out with the new Brisbane procedures....to help out...
First and foremost...taxiway ALPHA which is nearest to "legacy" runway 01R/19L will always run in the same direction as the duty runway....ie if runway 01R is on duty, then taxiway ALPHA will run northbound and taxiway BRAVO will always be opposite.
As you can see from the attached, taxiways A5 and A5S are decommissioned, and have been for a few months now....they have had their top layer of asphalt removed and painted Green with white crosses everywhere. In the latest charts, they don't even show...so now we only operate two high speed exits off the legacy runway, that is A4S and A6.
Taxiways YANKEE and ZULU link the "legacy" taxiways to the new parallel runway....YANKEE will ALWAYS run westbound and ZULU will always run Eastbound....ie...if you are going to the new parallel runway, you wil always go along Yankee.....if you have landed on either 01L/19R you will ALWAYS take ZULU back to the apron...the traffic pattern on these two runways is fixed...there are many reasons for this and a lot of work done, but in a nutshell that is how it works.
X-Plane has good scenery which already has the complete layout of the airport, with all taxi signs, taxiways, etc so any X-Plane user will probably be making good use of the event on Friday (I certainly wil be...can't wait).
Sunshine Coast airport is next up on the list of releases in qld....it has been pushed back to next month....but I doubt you will see any updated scenery for it for quite a while..
Cheers
-
3
-
-
12 hours ago, David Zhong said:
Thanks Will. I see now that on the eastern runway SIDs there is indeed an immediate turn away from the other runway. Would I be correct in understanding that "Finals" is purely monitoring (i.e. transfer after turn for intercept) and does not do final vectoring (e.g. from downwind like "Director").
Hi @David Zhong
Yes, the primary role of monitor is to guard the NTZ...once an aircraft is established on its approach path it is deemed to be separated from the parallel runway path...thats it, and to ensure this, Monitor will keep an eye on it.
As stated before, Monitor will transfer the aircraft to Tower (ADC) when established, no longer turning, fully stable..... or no closer than 5nm.....however, Monitor will continue to follow the path of this aircraft, even though it has been transferred and it is now talking on ADC frequency, all the way to 1nm (at the moment....although it may be 2nm....we will see)....what that means is that if the aircraft is on the ADC frequency and starts deviating into the NTZ, the monitor will use the "override" function and basically shut BOTH the Tower ADC frequencies and direct a "Break Out"....
When the guys from Tower run simulated transgressions of the NTZ, it was very hard to pick that the aircraft had started a turn into it, and a lot of cooperative work was done between approach and Tower to come up with the procedures to satisfy the NTZ integrity.
The Break Out procedure is an immediate turn of 45 degrees away from the NTZ...if two aircraft are on approach and aircraft A starts turning into the NTZ, Monitor can direct an immediate Breakout of aircraft B...in other words, the non-guilty aircraft gets bumped off first....and then the guilty aircraft second...again this follows ICAO procedures.....to ensure separation is achieved as quickly as possible, the aircraft that is on path and in control will assist in regaining separation....and the floundering aircraft goes next.
The go around procedure reads fly to the far end of the runway and turn 30-35 degrees on climb.....the Break Out procedure dictates a harder turn, this ensures continuity of separation with any departures, go arounds as well as adjacent Archerfield and Amberley aerodromes....and also why we now have a "wedge" to allow Helicopter operations without having to coord and stop any flows at all....a lot of work has gone into this.....at least the guys who worked on this will assist the new SY procedures as well as the new ML parallel
-
1
-
1
-
-
On 3/28/2020 at 9:56 PM, David Zhong said:
@Will Reynolds I notice in the independent parallel approach user instructions page, it talks about finals controllers monitoring the approach paths for deviations towards an NTZ. I was originally under the impression that the increasing spacing of the runways (c.f. Sydney) meant that this was not necessary and I haven't seen that this is something that is discussed in documentation for similar airports overseas. While I have since found ICAO documentation prescribing this, is this done anywhere else overseas (i.e. where runways are spaced far enough apart to forego PRM)?
I notice also the SIDs don't provide for diverging departure tracks... is this not required for independent parallel departures or are independent departures not planned to be used?
Sorry took so long to reply.
as Jake correctly pointed out, a Monitor is a requirement for implementation of Independent Parallel approaches. Actually the requirement is for TWO monitors but Brisbane has submitted a safety case to have only one person. We are about 50% of the way with controllers trained on the position, and their interaction with Tower and how the "Monitor Override" will work.
In a nutshell, aircraft are handed to monitor (Called "Finals"...in other words, "contact FINALS on xxx.xx") and Monitor will have them on frequency until the aircraft is established....handoff to tower will occur WHEN the aircraft is established on final but NO closer than 5nm from the runway. Monitor will continue to radar monitor the approach until 1nm (this distance is still being discussed).
Also, dont forget Sydney cannot make independent parallel approaches unless they are visual and certain conditions are met.....in Brisbane, because each runway is almost exactly 1km either side of the tower, the aircraft are deemed to be separated once "ESTABLISHED ON PATH" and a Monitor is present....the person who worked on creating the new paths worked closely with other NAV providers such as NAV Canada who has pioneered "ESTABLISHED ON RNP" as well as France/CDG were they have some very interesting airspace but it is managed extremely well.
The approaches have changed (as you would have seen)....and the rule to remember is "LEFT IS HIGH"....Brisbane paths are separated vertically with all approaches to the LEFT runway being at 4000ft and RIGHT runway at 3000ft....ie approaches to 19L or 01L will start at 4000ft....and the approach paths have also changed to cater for TCAS TA/RA advisory as well as weather, instrument tolerances and many other factors...a lot of the simulator data for this was done by Boeing and Airbus, even tested with their upcoming version of TCAS, and locally tested at VOZ and QF sims.
RE the SIDs...yes and no....the aim is to be able to operate most departures from either runway.....there are some 9 modes of operation which are active at any time...but in a nutshell....if you are flying to the NORTH from Brisbane, you will depart off the runway NORTH (ie, 01L/19R).....everything else goes off the legacy runway. Tower will call DEPENDENT departures when they have a HEAVY that needs to depart off 19L for example and turn north....once wake turbulence has been addressed, INDEPENDENT departures resume.
Hope that helps?
Cheers
Will
-
2
-
3
-
-
8 hours ago, Peter Story said:
Thanks Will, I saw that the 2006 AIRAC files were published a few days ago. Fortunately most of the importing of this data is automated, but from past experience, I'll wait a little longer before I start as there are usually many amendments to fix errors in the DAH and ERSA prior to the release date.
But there will be a heap of work required to bring the YBBN local instructions up to date....
send me a note if you need help...I am back with ASA and have been involved in the training project for the NPR.
Cheers
-
2
-
-
On 2/29/2020 at 11:37 AM, Peter Story said:
Yes, unfortunately it seems to be a trend where many AIRAC updates appear in the AIP Sups with AIP DAP, ERSA and DAH updates not occurring until the next AIRAC. All of these documents are available from https://www.airservicesaustralia.com/aip/aip.asp?
To complicate matters, many of the AIP SUPs get reissued with a different number if there are minor changes or a change in the implementation date. The numbers below will not exist on the AIP site after a period of time as they are updated or cancelled when they are incorporated into the AIP documents.
Here is a summary of the AIP Sups included in the Controller client and ATC Assist AIRAC2003 update
IFR Waypoint updates
- Sup 155/19 - HB VOR procedures
- Sup 156/19 - AV RNAV-U RWY36
- Sup 11/20 - IFR waypoint updates
- Sup 03/20 - YGLS RNAV updates
- Sup 26/20 - YCEE RNAV updates
NDB's Decommissioned
- YAMB - Sup 152/19 navaids update, IFR wpt update, airways updates, ERSA Flight Planning Requirement(FPR) updates
- YPED - Sup 159/19 navaids update, IFR wpt update, airways updates, FPR updates ATIS: 126.25
SID/STAR Updates
- Sup 141/19 YMML ARBEY 6A
- Sup 153/19 YSSY BOREE 2 and MARLN 5
- Sup 166/19 YPPH AVNEX 3 and OTLED 3
I haven't included SUP 135/19 in the list above as the Tasmanian air route updates where included in AIRAC 1912 and remain in 2003
For pilots who use the Navigraph FMS updates, they usually contain the AIP SUP updates that are valid for each AIRAC, so will align with our Controller client updates.
Just a heads up for you Peter, new ERC, TAC etc for May 2020 AIRAC are now available in the ASA page, they give you a snapshot at the massive changes coming up for YBBN, new procedures, new waypoints, deletion of old waypoints.....and lots of errors.....disregard the ERC HIGH 1 chart, the Holding patterns are a mess and most are wrong...there will be amendments soon....but the DAPs should be ok....
-
As a Founder of VATPAC and a WorldFlight official I have to say that I am amazed at the reaction to the YBAS incident and that you are devoting so much energy to what is, in the overall scheme of things, insignificant. You will take umbrage in my calling it 'insignificant' but you have lost site of what this event is all about.
WorldFlight is the only major event in VATSIM that runs 24/7 for one week each year. It brings hundreds of pilots and ATC together for a week of enjoyable and challenging flying and ATC. It is not real world and therefore real world procedures will have to be put aside to accommodate unrealistic amounts of traffic on any one sector. It is also about raising money for worthy charities around the world. The Australian teams have raised $30,000. for the RFDS this year and that means we have cracked the $300,000 mark.
I am also quite amazed at you Greg for making such an immature statement "Special procedures that just get made up in a drunken state in the back of a Truck company warehouse". That is inappropriate and I would have expected better from you. You would be well advised to consider the VATSIM CoC before going down that road again.
WorldFlight 2018 route has already been sketched out and you can look forward to bigger and better next year so why don't you all move on and enjoy the hobby created by dedicated folk that would hate to see the bickering that is going on in our region at present.
Terry Scanlan
Well said Scanno, surely there are better things to worry about....the joy of Vatpac is not what it used to be....and hope egos and attitutes can be set aside for the sake of a region made of volunteers and hobbyists who have a passion for aviation, not self gratification.
-
Airline is definitely still going, although it seems a lot less, as people fly as QFA or VOZ without necessarily being members of those virtual airlines, so Compass is a lot more apparent in its numbers.
The airline has been using VAFS to give some more meaning to flights but a small amount of pilots dont want to use it and do their own thing...so I guess they are like those who fly as QFA or VOZ on their own. At least a great thing about Compass is that it caters for every taste, has been around a lot longer than most, and still going.
-
Will, thanks for pointing this out.
I had been previously aware of this change and my assessment is that there is not a lot we can do. The status quo remains that: pilots should file, and controllers should clear aircraft, on routes that the aircraft are capable of navigating. Where a pilot has requested a route via navigation aids which are no longer recognised, alternate routes may be offered, but in many areas of the country, it will become impossible to operate within the rated range of radio navigation aids. In those instances, controllers should continue to clear aircraft on radio nav routes and the pilot will need to dead reckon when outside the range of the nav aids.
I am sure this is an issue that the future Director Operations will consider and implement any measures he sees necessary.
Cheers Dave, just wanted to make sure you guys knew about it.
They are working of documentation for the next two weeks and the date may change but at this stage looks to be quite a big Cha he all over the place.
Cheers
W.
-
Not sure if this is known, this project will take effect on the 26th of may.
A lot of VORs and NDBs will be shut down and replaced with Waypoints. This is the official website:
http://www.airservicesaustralia.com/projects/nrp/
Some of the Navaids to note that will be shut down include Wonthaggi, Epping, Rockdale, Essendon, Eidon Weir, Strathbogie, Bindook, Yass, Archerfield, Jacobs Well, Laravale, etc...
Laravale will present a major change for Qld....the old Laravale aid will be replaced with a waypoint called HUUGO. So all departures to the south will have a SID called HUUGO1 initially.
The waypoint was given its name in honour of young Hugo S., son of a senior approach controller who tragically lost his life to a brain tumour a couple of years ago.
Not sure how this will change things in Vatsim as the navaids obviously dont change but I thought you guys should be aware of this.
-
Oh boy...with G20 approaching, wonder what will happen...
Around 11:30 local, reports came of a car having smashed through the perimeter fence and was doing burnouts on the taxiways and eventually the active runway.
Federal Police took control of the airport and all ops ceased (apparently quite a spectacle, all aircraft had to stop on their tracks, and there were cars with flashing sirens running all over the place).
One car was stopped and occupant arrested. A second car was suspected and a thorough search conducted. No second car was found.
Spare a thought for the Singapore Airlines flight....it had been holding to get to Brisbane, and decided to divert to Cooly.
It refuelled, departed Cooly and went back to Brisbane, only for the Airport to be closed. It remained in a holding pattern for just over an hour and had to go back to Cooly. This time Cooly Airport was in chaos. Aircraft parked on taxiways, terminals at bursting point. By now the curfew was in place.
Singa could not obtain a dispensation on the curfew but departed back to Brisbane knowing it would attract a $25k fine. it arrived in Brisbane at 2AM and departed back to Singa at 5AM. It was supposed to have departed at 11:30PM!!
-
Was confirmed the M$ sold the license to their defunct MS Flight, not FSX. Interesting to see what happens to that sim now.
-
Interesting news...looks like one way or another, the FS business created by Microsoft will stir out of its slumber...in what direction, hopefully will become clearer in the next few weeks.
http://forum.avsim.net/page/index.html/_/pri-news/microsoft-sells-license-to-fs-franchise-r2295
-
Tried it last night and so far I really like what I see. It accepts export of flight plan from PFPX, very easy to set up.
It comes ready to go for My Traffic, IVAO, WOAI and a few other AI traffic sets. Creating a new one is very easy and a lot more functional than it was in FSINN.
-
Presumed lost enroute from KL to China. Reached F350 and disappeared. No contact for the last 4 hours.
Sent from my Mobile thing
-
Another interesting thing....don't use P3D2.1 with anything above SPARSE Autogen (which is roughly equivalent to NORMAL Autogen in FSX)....you will get OOM...the Autogen engine needs a fix, but until then, this workaround does the trick.
Airac changes Nov 2023 - Big changes
in Airspace
Posted
And with the changes, there is a lot of confusion regarding the correct flight plan for flights ex SY to the north....also in the real world....the correct route for SY to BN is:
OLSEM - Y193 - BANDA - H252 - GOMOL
The flights going via overhead MATLA (on H140) are for destinations north-west and those aircraft that cannot meet the height requirements in the SY DAPS.
Hope that helps