Yeah i know … in 99% of the cases I normally taxi to the CORRECT runway to hold short. And then sign in with Tower and the tower is thinking i am at the correct RNW ( actually the wrong one )
Why a simple option for the user to select dept runway is missing only Asobo can explain … i explain it like “ Asobo being stupid “
For winds in breeze category of 1-2 kts I certainly do not have really a problem with ATC going with a downwind runway.
Especially when there is 12000ft of runway.
It is much more troublesome if all you have is 2600ft and ATC would like you to land with a 20kt tailwind 
But I must say I do see an improvement at least in most cases since SU7 in the most recent flights. But I also think there may be more than one issue at work here. Because now it seems that some airports are better than others.
GCLA and GCTS have been correct both in terms of ATIS as well as runway in use for TO and LDG.
GCXO was a 50-50 so far.
Um, you want people to select their own departing runway and think Asobo are stupid not doing it? Having people be able to use conflicting runways doesn’t sound that sensible to me.
As far as some saying it is “better” than it was. None of the runways I’ve been assigned are correct since using the beta. I fly mainly bush areas like YABA and it is always assigning the wrong end of the runway and winds are often 15kts so it isn’t a calm winds issue. It is rather annoying such a basic and important thing hasn’t been fixed in all this time.
Yes thatbis what i think.
If you are assigned the wrong runway with wrong winds at least you can select the correct one to correct it.
it is impossible for Asobo to implement all the rules and exceptions on thousands of airports worldwide. For example i know a certain runway is used between 8am and 8pm …. Then i can sellect it. Some runways will be favourable due to sound limitations even if the wind is slightly better at another runway … ETC ETC
And what do you care if a person in his own home …. Own flightsimulator … own computer selects a “conflicting” runway using MSFS ATC ?? Its up to that person right ?
If you are SERIOUS at least you can select the CORRECT runway when Asobo lets you select it. If people want the wrong runway … who cares ?
I don’t think I’ve been given a tail wind take off with SU7 yet. I have had lots of them previously though.
Yeah, me too. With SU7 it worked better (maybe the bugfix update will make it worse again).
Just yesterday in-game ATC was way off still, Example:
Two Runways at Airport 5/23 9000’ and 14/32 4000’
ATIS stated Wind 310/10 Runway 23 in use, landing and departing runway 14
Real World arrivals and departures were using Runway 23 at the time as observed.
Ground directed me to use Runway 14, the short runway and basically opposite wind direction
ALL THAT IS NEEDED IS THE ABILITY TO TELL ATC YOU WOULD PREFER AN ALTERNATE RUNWAY, 23 IN MY CASE. FSX had this option…seems simple
I support the preceding post. Just been flying VFR without real weather up and down the Leeward Island chain in “no wind” conditions. The ATC allocated landing runway is often/usually the wrong one. The Navigraph charts show the “standard approach” runway to usually be into the prevailing trade winds which are mostly between NE and E in this part of the world.
Abandonment of ATC on approach could be avoided if there was an option to “select an alternative runway” on the ATC menu for a controlled airfield as there is for an uncontrolled airfield. Not the only situation with ATC where the SIM does not allow a pilot sufficient discretion to fly properly.
This has really been going on for far too long. Having issues with Live weather it was reported as being good to go again yesterday. In checking I was pleased to see it was working.
However, attempting ot take off from Shoreham Airport UK the runway offered by MSFS was with a 7 knot wind 22 degrees off my tail.
Somewhere in the coding for ATC and Planning someone has not realised that METAR information states the angle of the wind as coming from that angle i.e. 27011 means 11knots blowing from West to East.
In looking at the G1000 PFD the wind showed correctly, on my tail at 7 knots. So why was I on the correct runway but at the wrong end i.e. 180 Degrees the wrong way round.
I cannot imagine that this is a difficult fix. Has anyone seen anything from Asobo about this?
The weird thing is its not consistently wrong. In fact I rarely see it. If it were a simple schoolboy error programming wise, you might expect it to be either wrong or right all of the time. Like using the wrong variable, or a double negative/invert, something like that.
The next time I do see this, I will try to remember to do the following, after confirming wrong runway has been assigned:
That might tell us if its wind being mis-interpreted or live weather being mis-interpreted.
I still have a feeling the airport itself has something to do with this problem.
For some time now GCLA has been 99% correct for both departure and arrival in keeping with the prevailing winds.
GCXO not too far east from there is batting about 60%. So far nothing makes any sense, when it does or doesn’t work.
GCTS is mostly correct, but has the occasional wrong assignment.
Flying VFR, I set a gate or other parking as arrival, so I often see ATC assign a landing runway with a tailwind at KSFO, KOAK, and KSTS.
Before SU5, flying VFR, I could always force ATC to assign the landing runway that would have a headwind by turning off live weather and setting wind direction to be a direct headwind for that chosen runway.
Ever since SU5, ATC ignores manually set wind direction when assigning landing runway. I can no longer set a gate or other parking as arrival and specify the landing runway by setting wind direction.
I just was assigned a runway that put the wind at a 40 knot crosswind with slight tailwind when there was an approach and runway directly into the wind…
I hope a fix comes along some day.
The answer to the wrong runway issue as “allocated” by ATC is covered in another post in the labyrinth that is this forum. Surely all that has to be done is to provide the ATC menu with an item for the pilot to “Select an alternative runway” on takeoff and landing at ALL airports.There is also a need for an “Unable” response so a pilot can decline an unrealistic ATC “instruction”. MSOBO must realise that ATC is there to " assist,organise and regulate" safe operations. It is the pilot in command’s responsibility to fly his aircraft…and no-one else.
The buck stops in the PIC seat…NOT in the Control Tower.
Well, it’s “an” answer, not “the” answer. It would be much better if ATC didn’t assign the wrong runway in the first place so you don’t need the option to request something else. But it would be a workaround all the same.
Since SU7, I had correct runway assignments and weather for most of the times. What did get worse is the “flexibility of ATC”. If you launch a flight and the World Map gives a specific wind at destination. And the wind changes at dest (even right after takeoff for a 2h flight) and the landing runway should have changed by far when approaching, ATC still gives you the initially published runway on World Map. (yes: no approach is set on world map > ‘automatic’).
“The” answer is to provide pilots with ATC that works…No computer programme can be 100% right first time all the time. Just as in the real world flexibility is required in the system so pilots can sort things out for themselves if necessary.
Just tried out Real Weather with a flight from MYNN to KTMB in windy low cloud conditions in the Baron. ATC nominated a westerly takeoff runway 28 with a surface wind of 20kts plus easterly. I took off into wind on runway 10
A little “lively” but manageable,
Approaching KTMB ATIS said…wind 094/21…visibility 3 in heavy rain…
ILS 9R…visual 9L in use…Landing and departing runway 27L, 27R. ???
ATC cleared landing on 27…downwind in a 21 knot wind.
I ignored ATC landing clearance and in the absence of options to “unable” or
“select another landing runway” I used ILS 9R , a bit bumpy but the obvious safe option in those conditions.
The wind indicator in the Baron MFD (G1000 Nxi) was right,
Lessons learned…At present .ATIS sometimes confusing and contradictory…cannot be trusted, scrolling text unrealistic (needs on off toggle) ATC inflexible and unreliable…use your pilot skills and common sense…take ATC “instructions” with a large “pinch of salt” and be prepared to ignore them when necessary.
ATC and Real Weather (what happened to the rain) is improving piecemeal but much more to do yet.
X-Plane is worse. You will be sent into a mountain side…
ATC not only assigns an incorrect runway based on winds, but at KSNA (Class C), ATC assigns the incorrect runway based on aircraft type, The shorter runway (20L/2R) is generally for small GA aircraft with single engines. The longer runway (20R/2L) are typically for multi-engine and commercial airliners.
So many times when I’m in the C172, ATC wants me to take off on the airliner runway, which rarely ever happens IRL at this airport.