Hi,I have been having this problem for awhile now, but I have just decided that they may be a solution to the problem. The problem is that on approach, Radar Contact gives the weather and for the winds given its sometimes gives the active runway as the tailwind. This often occurs when the airport I am approaching has only one ILS runway, and this is often which Radar Contact wants me to land at. But I would prefer the VOR approach and landing into a headwind. This isn't a problem cos I can ask the ATC for the other runway, but the AI aircraft still land on the tailwind runway meaning that often I have to go around due to the other aircraft.Is there any solution to this problem?CheersRob

RC gives first priority to AI landing direction to avoid conflict. FS has complex algorithms and based on aircraft class and runway length that will accept various amounts of tailwind for AI.Closing one end of a runway in FS does not work for ai.The only control is to dictate your destination weather or shut down AI so there is no conflict.If you are using ASE in FSX with DWC then there can be problems with destination wind changes as you approach affecting ai patterns. See their support forum here on AVSIM for service packs and notes on this.

Ronzie, as for ASE/DWC and RC4 - since few months new FSUIPC was released I have no problem with RWY in use. Somehow, these two now communicate together, plus do not forget that ASE now has option to have wind locked.I do not know what kind of AI program is in use here, but I have UT2 and always - just to be 101% sure - I reset the AI around 40NM from airport. I have not had any issue since then.

Good to hear : )FYI:For UT2 users, be sure ai is set to spawn ai maximum so it renders ai in stable patterns before RC examines it just before 40 nm out.

Ronzie, as for ASE/DWC and RC4 - since few months new FSUIPC was released I have no problem with RWY in use. Somehow, these two now communicate together, plus do not forget that ASE now has option to have wind locked.I do not know what kind of AI program is in use here, but I have UT2 and always - just to be 101% sure - I reset the AI around 40NM from airport. I have not had any issue since then.

There is a problem, now i cant remember if it FS9 or RC4 specific, yet it still happens to me today. When i start FS9 up to the point where aircraft is ready to go, i MUST fast forward the time by 1 minute or more to have the aircraft use the correct runway.If i dont, then the aircraft will always use the default startup runway no matter what the wind direction is. As soon as i fast forward the time, voila, aircraft start using the correct runway according to wind direction.Pan Pan Pan

There is a problem, now i cant remember if it FS9 or RC4 specific, yet it still happens to me today. When i start FS9 up to the point where aircraft is ready to go, i MUST fast forward the time by 1 minute or more to have the aircraft use the correct runway.If i dont, then the aircraft will always use the default startup runway no matter what the wind direction is. As soon as i fast forward the time, voila, aircraft start using the correct runway according to wind direction.

That forces the traffic to reload, and RC tries to use the same runway as they. Generally that will sort itself out in any case, in time. I always start my 737NG cockpit up "cold and dark" so by the time I'm ready to get RC started all the traffic is behaving correctly. If you need it to happen faster, as an alternative to the method you are using, you can simply toggle the traffic off and on again -- FSUIPC provides an assignable control "toggle traffic density" for that.However, that probably doesn't work with UT2 traffic -- there are UT2 Add-Ons menu items instead for UT2.RegardsPete