I notice when I'm holding for takeoff, the aircaft in front of me will not taxi in position when the inbound aircraft is cleared to land by ATC, this is usually about 7nm outside the inner-marker (way too far). In real-world ops aircraft are cleared to land about 3nm outside the threshold (even shorter in some cases) while another aircraft is on takeoff roll on the same runway. Okay my question is this, is there any way to shorten the distance for landing clearences so the holding aircaft are able to taxie onto the active faster? Thereby reducing congestion on the ground.PS. IS MY MISSION TO CREATE AFCADS WHERE AI AIRCAFT BEHAVE LIKE REAL-OPS! IM ALMOST THERE, I JUST HAVE TO GET OVER THIS HUMP :-spacecraft

There is a program, freeware, called Ai smooth, check the library, with this you can somewhat adjust the seperation of the Ai.DouglasFirst Ai :-bat ..................3nm.................... :-rotor second Ai

Ok Douglas, I'll give it a try, thanks for writing back, I'll let you know my findings.

is there any way to shorten the distance for landing clearencesNoAFCAD only controls about 1/2 of the AI aircraft behavior on the ground at airports. Much is controlled (and often broken) by the approach system and scenery designers.FS9 "locks" the runway for the landing aircraft when the trigger event "cleared for landing" occurs.It's a real pain in the rear - but as MS says - "As real as it gets" meaning - the program cannot be made to work any more realistic.

Is the Cleared To Land event itself triggered do you think by placement of the outer marker (if present) or just by distance from the threshold.

I'm not certain Ron, if had to guess, I'd say the outer-marker being that its ~7nm from the runway?

I believe it's distance but it's one of many things burried in multiple .DLL files which no one has yet deciphered.One additional impact is voice file play time. This occurs only upon the frequency which is playing sounds (ATC).Trigger event actions occur quicker and in a smoother flow when the frequency is not "active" - just computer codes passing back and forth.When the system has to pause for the wav files to play before moving to the next event in sequence - it can create log jams.It can also have AI and user aircraft fly past trigger waypoints - and get out of sync with the voice playback system.It can even make aircraft get "lost" by the system because they failed to respond at the appropriate time.

"Okay my question is this, is there any way to shorten the distance for landing clearences so the holding aircaft are able to taxie onto the active faster?"In a word.......VATSIM!kevin