The program is great, can't stop using it.Wanted to know if the program has the ability to issue random speed restrictions or just the default 250/230/210 and if it can issue a speed restriction on final (170).Also a random turn to base at different distances from the airport without using short final.If not would like to know if it's because FAA rules.Thanks in advance Shom

Hi Shom,The speed restrictions are standard for the downwind and base legs. After that it's down to the pilot to reduce speed accordingly. In the real world ATC advises speeds to fit in with other traffic. RC doesn't have that level of sophistication at present I'm afraid. Imagine the problem of trying to ascertain speeds depending on the aircraft in use. It would be a nightmare.The distance at which you're turned to base depends on your aircraft size and can be set in the Options page.V4 has many different rules for FAA and non FAA airports and will satisfy the most enthusiastic of pilots.Hope that helps,

Perhaps in a later version 4.x, IAS can be advised without breakling restrictions to allow proper merge with AI perhaps on base and on final. Since RC can see aircraft, and version 4 will have some AI control, I'm thinking of situations where it seems some aircraft are allowed (based on distance seperation) to join midstream a string of pearls situation. I've seen commuter jets appear to hot-rod in on a 30 degree merge between other aircraft on a longer merge or track to final at KMSP (from below, of course - I work at a location about ten miles from the threshold of a parallel near the extended final track). If requested to expedite by speeding up the pilot should be able to reject the request (as in real life based on aircraft performance limits).

Ronzie,You make some interesting suggestions on approach speeds and Ai aircraft. JD is the final arbiter on this of course and I think any new features for v4 would have to wait until after it's released. The main problem is that of controlling Ai aircraft. v4 does have quite a degree of control but FS is always fighting to regain it. The Ai SDK would have been very helpful but Microsoft never released it :-(Once JD returns from his break I'm sure he'll add his comments to this discussion.Cheers,

Thanks for the reply ray ,Maybe you can tell me if also in real flights approach turns you on to final only 20 miles from the airport even when it's a heavy.Also notice that if you request a short final before you are abeam the runway approach turns you base very early and leaves you a 2 mile Kai-tak approach.... gonna miss that approach.I guess I'm looking for an unpredictable approach where approach turns you final at different distances, different speeds with traffic advisories ("follow the B727 , traffic landing at parallel runway 14 oclock").That could be nice even for those who dont use AI traffic...Shom

Hi Shom,I'm not familiar with how real-world flights operate - my knowledge is only based on my experiences with RC.In respect of the turn onto finals at 20 miles or less that sounds perfectly normal with a heavy. It does depend on your approach. A straight-in approach may intercept the ILS 20+ miles out depending on the range whereas a downwind, base and finals leg will probably intercept around 13 miles. Those are my experiences with v4 and I don't think it's too different from v3 in that respect.I don't request short-finals but if I did it would only be when I felt it was safe to do so. Kai-Tek style approaches are rare these days but that was only a 47 degree turn onto finals - quite modest compared to what you're suggesting perhaps ;-)RC will never give you an unpredictable approach or one that isn't feasible to fly. That would not be satisfactory surely? The primary purpose of ATC is to get you down safely and in one piece. Complaints would flood in if we adopted that approach (no pun intended) ;-)Cheers,