FSX - Wind Direction & Rwy alottment

[XCLTM3]

Hi George/Martin,

I just wanted to ask for your assistance in unlocking this mystery.

When arriving into YSSY - particularly if the winds are from the North-East, YSSY Arrivals (FSX ATC) issues instructions for landings on Runway 25. I've observed this quite often of late, and around 50% of the time I'm being instructed to use Runway 25 instead of Runway 07.

I've just completed a live flight using ASN (as I always do), despite winds from the North-East ie 030@22, FSX ATC has yet again instructed me to use Runway 25. (UTC 2.30)

ASN shows the correct wind speed and direction as 030@22, and this corresponds to the SkyVector website which provides live up to date information for YSSY.

I was hoping you could help illuminate why this is happening.

PS: there is no sudden wind shift either. The winds from the North East have been constant (UTC 10.00 to UTC 3.00 and beyond)

Thanks & Regards,

Steve

[capt sl]

my understanding is the if wind is conducive to a 34 arr/dep 25 will also be used in fsx . 07 is attached to 16 side of things . so if 16 is active then 07 will also be. that's the way the crossing runway activation is set up I think

atc in fsx tends to allocate nearest runway to the direction u r coming from . so if u approaching from the northeast or somewhere from that side u r being given 25

[george[flytampa]]

I'm not going to pretend to understand the afcad we use at Sydney. Garry Lewis kindly authored it for me.

It does allow for crossing runway use which a traditional afcad wouldn't. Advantages are that the traffic flows more efficiently, less blockages & shorter takeoff queues.

Can you not request a different runway for landing from ATC?

[XCLTM3]

Thanks for the response George.

I can't request 07 despite the fact that the winds are prevailing from that direction. I'm only being given a choice of 34L or 34R or 25 under the circumstances I provided.

BTW: I really enjoy the fact that YSSY has cross runways. In the examples I have experienced thus far, it's just a minor annoyance that for some reason unbeknownst to me, the wrong runway is being allocated. My best guess is, that the parameters in the afcad that dictate wind direction and use/choice of runway may be out a little.

captsl:

believe it or not, there have been some occasions where north easterlies have blown at YSSY and FSX ATC have appropriately allocated rwy 07. However, there have been an equal amount of times where it was ordering the use of rwy 25 which of course meant I'd be landing in a cross tail wind of sometimes 20+ knots. Not that I accepted that, I would just go ahead and use 34L or 34R in that instance.

Is it that 07 & 16L/R are tied somehow whilst 25 & 34L/R are tied? I don't believe so, as there have been occasions where I've been given 07 by FSX ATC when south easterly winds prevailed.

That's why I eventually posted this as it was becoming a little baffling and I wondered if it could be fine tuned by the afcad author.

As usual George, it's not a huge annoyance. If the author can investigate this....great.

Otherwise, I'm enjoying the hell out of YSSY - it's not just an FSX airport - you created an absolute piece of art.

Thanks & regards,

Steve

[capt sl]

there is a certain angle range of direction which will trigger a certain runway although im not very sure what and how much .

this is just for eg purposes . say from 250 deg around to 060 will cause runway 34 to be used and anything else 16. sometimes its just a few deg and runway ends change. which is chaotic for AI traffic when u see both ends getting used at once LOL

25 is attached to 34 ops and 07 to 16 . so wind direction for 34 like northeasterlies for eg will obviously not be ideal to use 25 but since 34 is operating 25 will as well.

with the south easterlies u mentioned 16 would have been in use therefore 07 which is y u would have assigned 07

[george[flytampa]]

Try this afcad. Seems 07 landings are working now. At least with AI & basic ATC.

[XCLTM3]

Try this afcad. Seems 07 landings are working now. At least with AI & basic ATC.

As usual, many thanks again George!

From your #1 fan down under.....


Captsl:

I don't doubt you're on the right logical path of thinking.

I'm keen to test this new afcad George has provided.

Fingers crossed this will improve things.

Thanks & Regards,

Steve

[atco]

Sorry I missed this post earlier on.

When using crosswind runways in FS, you have to have a master runway and the crosswind runway is tied into it.
Of course at SYD the main 16/34 are the master runways and 07/25 is the crosswind one.
FS should allocate either the 07 or 25 end accordingly, but unfortunately its not very clever and often results in frustrating experiences like this.
For example with a wind of 280/15 that would mandate RW34 being in use with RW25. However a wind of 030/15 would mandate RW34 in use but 07 active as well. FS should be able to cope with this, but sadly it doesn't do too well.
I set 07 to be used for landings but closed for takeoffs with 25 open for takeoffs and closed for landing as based on my research and talking to some local spotters that was the most common use for when 07/25 was active. Unfortunately FS loves to ignore these instructions and just do what it wants. The only way to eliminate that completely would be to have one ADE for RW16&07, one for RW16&25, as well as one for RW34&07 and another for RW34&25 - which the user would have to swap in and out depending on the winds.
I am more than happy to make such a set, but for the majority of people its just too much hassle, which is why I went for a compromise solution with the original.

Unfortunately in ADE design you quickly learn that much of what you would like to do is not possible, and its incredibly frustrating!
Hope this was at least informative if probably not very helpful to solving your issue!

[XCLTM3]

Sorry I missed this post earlier on.

When using crosswind runways in FS, you have to have a master runway and the crosswind runway is tied into it.
Of course at SYD the main 16/34 are the master runways and 07/25 is the crosswind one.
FS should allocate either the 07 or 25 end accordingly, but unfortunately its not very clever and often results in frustrating experiences like this.
For example with a wind of 280/15 that would mandate RW34 being in use with RW25. However a wind of 030/15 would mandate RW34 in use but 07 active as well. FS should be able to cope with this, but sadly it doesn't do too well.
I set 07 to be used for landings but closed for takeoffs with 25 open for takeoffs and closed for landing as based on my research and talking to some local spotters that was the most common use for when 07/25 was active. Unfortunately FS loves to ignore these instructions and just do what it wants. The only way to eliminate that completely would be to have one ADE for RW16&07, one for RW16&25, as well as one for RW34&07 and another for RW34&25 - which the user would have to swap in and out depending on the winds.
I am more than happy to make such a set, but for the majority of people its just too much hassle, which is why I went for a compromise solution with the original.

Unfortunately in ADE design you quickly learn that much of what you would like to do is not possible, and its incredibly frustrating!
Hope this was at least informative if probably not very helpful to solving your issue!

Thanks very much for the explanation atco....I appreciate it.

Regards,

Steve