So many times I get the ATIS on approach and they call for a particular runway. Then 5 minutes later and handed over to the approach controller he tells me vectors for a different runway. I aint falling for that anymore. There I go setting up my FMS in a furry only to have it re-initialized and then the controller tells me I am getting my original runway! Whats the deal with that? It happens exactly half the time and it is usually reciprocal runways. I need to land in the direction of the AI so I cant just go with what the ATIS said, tried that and had a head on.ThanksNot one flight happens w/o at least one problem with all my bizzilion addons so I am not blaming Radar Contact necessarily. Maybe it is ASE.

I noticed that while RC4 will interact with AI.. it doesn't tell me or the AI to hold short they just run into me anyway :( (so yes I hope this is fixed in RC5)

Hi Marc,When I run ASE with FS I always record the weather at my destination.As i usually fly 2hr sectors when I am 70 miles from touchdown I refresh my AI traffic for the destination in ASE .At 50 miles out the ATIS in RC chimes in and I then check this information against my notes made at departure time.I usually find that my original departure information is still good as ASE ATIS usually gives the Winds Alfoft info at this point instead of Ground level info.

without a log, i can't tell you what/why this happened.but with third party weather programs, if they are changing the weather at the destination airport, the ai are then changing, and rc is picking up the changes in the ai patternsjd

First for those using Ultimate Traffic 2 be sure you set the AI spawning distance to maximum so RC sees them in time for the initial runway assignment.Second for ASE be sure you have the most updated service packs and FSUIPC4. It has to do with using DWC with ASE which in FSX does or did force global weather mode. Workarounds are discussed on the hifi (Active sky) support forum here on AVSIM.

I am using my traffic X. I wish I knew what was what. In other words This usually happens when the winds are reported calm even though the metar from ADDS shows something very different. So when I am out of ATIS range I will set up the approach for what should be the wind favored runway. Then often the ATIS will report calm and tell me the opposite runway in use. The handed of to the final controller they will give me the runway I had expected even though the winds are reported calm but they really are not, or are, I do not know. I use cloud smooth transitions in ASE and not DWC. I have not updated to the latest FSUIPC so maybe that will help. All other programs are up to date.Thanks

This usually happens when the winds are reported calm

Calm winds, or those below a certain speed, are the worst for trying to select a runway which avoids clashes with AI. With such low or absent winds FS allows the AI traffic to use every which way, all at the same time, if they all either have ILS or none do. I've seen AI aircraft landing on both ends of the same runway at the same time! Crazy!I did ask for there to be an option in ASE for a minimum enforced surface wind speed to be imposed at destination airfields. I don't recall whether it went in, but i think it did, but you probably have to provide ASE with the route details, or at least the destination.Pete

Hi Marc,I forgot to mention that I am using DWC which is the one which works best with RC4.My version is build 651.Calm winds are a problem and if what Pete says happens the new version of AS may show some improvments in that area.

Thanks for the replies guys. When en route I check the METAR with Aviation Digital Data Service while still out of range and even when they are really blowing and the TAF's call for blowin as well, several times the wind is reported calm. This may be a separate issue but I hardly think that it is a coincidence but it may be. Yes the calm winds are hectic especially at airports like LSZH (Zurich). I could always force a runway with RC but what fun would that be. It is always exiting and realistic to get a last minute runway change for either takeoff or approach but no when the ATIS reports one thing and you have prepared for another with the actual METAR and TAF and then ATC decides to go with the METAR wind or if that disappears, use a different runway entirely. There is barely enough time to reprogram an FSM single pilot while going 300 knots over the ground, let alone doing it at a later time or a 3rd time. Makes for some interesting approaches and makes me wonder why I spend all this money on scenery when all I do is look at the FMS.I could allways request any runway and sometimes do but with the attendant encounters with AI not working right. I just upgraded to FSUIPC 4.7 so hopefully thing go better.Thanks allot!

There is an option in AES regarding locking destination winds you can investigate. I don't use it, have FS9, with AS65, and have not experienced these random ai assignment problems.The procedure for runway scoring for AI (runway assignment priority) by aircraft type is very complex. As an example it allows tailwinds up to a certain amount based on aircraft type. Then runway length, navaid type priority, visibility/winds, etc. (not in order). It was also observed that at EHAM in FSX showed more variability because it was below sea level. I'm still waiting for the definitive paper to be published. The discussion is in the ADE design forum on FSdeveloper.com.BTW, according to notes posted FS9 had a lock on AI patterns on a certain distance for all AI to follow and was stated in the FSX beta that was removed.Check on the hifi sim forum here if AES introduced the minimum wind in a service pack that Pete Dowson mentioned. That might help some factors.Finally, I use the PMDG 737NG (FS9) aircraft and I don't place the approach into the FMC until assigned by RC along with the runway but I do have an estimated landing runway in it. An approach and landing runway can easily be changed if needed by working on the legs page after reassigning the STAR and runway and working in the LEGS page to 'pop' the waypoint stack and close discontinuities. Of course the aircraft needs to be in MCP mode while these LEGS changed are being made.If vectors are being used then of course a runway change becomes easier.

That's a good procedure actually. It does become difficult when it is a nearside approach and there is only 3 minutes from the hand off to the vector to final. One good way to do it is to setup for the nearside and then if you get the far side you have more time. Versus the other way around.