I have this annoying problem with the Kastrup (EKCH) scenery. Normally runway 4L is used for landing and 4R for take-off. The problem is that it's always like this, even with a strong tailwind, my AI still use 4L for landing and 4R for take-off. I tried editing the afcad file to see what would happen. All I get now is all planes take-off and land on 22R...this is with 220/26. Does anyone have a way to make this more realistic, or perhaps have a afcad file which works for them?Mikkel

Are you talking FS2002 or FS9?Stamatis

fs9/Mikkel

Mikkel, My solution to this problem is to use the runway you need or want. Let me explain what I do. Here in Albuquerque NM, (ABQ) most departures are on runways 8, 21 or 26. Since the terminal is closest to runway 8 and 21, those are the primary runways used depending on which direction the wind is blowing. Shorter taxi times means less schedule delays and since Southwest Airlines have a "Mini" hub here, that can mean better departure performance stats not to mention less traffic congestion. Landing, they use runway 26, 3, and 8 since again that would keep the taxi times down to a minimum after clearing the runway. So that I too do not have to taxi forever before departure or after landing, I sometimes do "Not" call ground after getting my ATIS (weather) at the gate. Instead, I taxi to the appropriate runway for the aircraft I am flying and when it is safe to takeoff, I do so. Then after departure I will contact departure and pick up my IFR clearance in the air and proceed on as normal. On landing, we have a few extra choices in that we can request a different approach and then a different runway other than what ATC is willing to give. Most of the time that works but there are times when you cannot get to the runway you need so I just and on that runway anyway. Most of the time the tower will just tell you to contact ground as if you landed on the assigned runway. As for the programming of the AI traffic in FS2004, it seems like they will start with the "Lowest" numbered runway in a no wind condition. Here in ABQ that would be runway 3, which in the real world is

I agree that they have come a long way, and I guess we'll have to wait for some SDK from microsoft before we can make any real changes.The funny thing is that depending on how I set up the runways, some for landing others for take-off, they will take-off from the correct runway but will also land there creating a long line of aircrafts waiting.Here's what I have set so far:4L: closed for take-off22R: closed for landing4R: closed for landing22L: closed for take-off...this works in most cases, but when the wind is 220, for example, they will not take-off from 22R. If I clear the check marks on runway 4R/22L, then all of a sudden AI start to take-off from 22R, but they land there also...which creates the long line of waiting aircraft.