Hi,

 

Today morning I was flying (Wilco A320 Evolution) form EKCH (Copenhagen) to LOWW (Wien), and when I was round 60 miles from LOWW, I heard an ATIS where runway to land was 16. Two minutes later, when I was switching to Approach - I got vectors to runway 11. No weather update during those two minutes.

 

And here is the question - what was wrong that runway in ATIS was different from indicated by Approach?

 

I use FS9,1 and FSrealWX as a weather program (the program uses Vatsim servers)

Hi,

 

What AI program do you use?

 

RC reads what the AI are doing and then chooses the same runway.If RC does not have AI to see,because they have not yet appeared at your arrival airport it then uses wind.In your case it woulkd seem that when within the AI spawning distance the runway was adjusted.

 

Some AI programs allow you to adjust spawning distance.

 

N

I am sure it was that @ 60 nm out when you checked ATIS there was no AI acticity happening at your destination. If RC sees no AI activity then is selects a runway based on other variables. Then when you got closer RC checked for activity again and then it gave you the runway that was being used by the AI for landing. UT2 will let you set a spawn distance at 50nm out which helps with this problem but I dont think UT2 is available for FS9 ....

norman is right. at 60 miles, i look at the ai. if there are no ai, i look at the wind

 

at 40 miles, i look at the ai, and then i look at the wind

 

either fsuipc needs to have an unlimited range set to 0

 

ai may need adjustment

 

fsrealwx may need tweaked.

 

at least you weren't landing into outgoing traffic :-)

What AI program do you use?

 

I use MyTraffic 2006 ver. 4,1 and AI Smooth 1,2.

 

 

Thank you for the solution, indeed when I was checking ATIS I had no incoming traffic to LOWW on the ND (the range was 80 nm).

 

@jd

Thank you very much for the information, it helped me a lot.