HelloFirst of all I would like to thank the Radar Contact Team for this wonderful program. I love it !When I fly these days over Europe with heavy upperwinds (50-80Kts, sometimes across) it happens that the FMC of PIC 767 turns to the next waypoint, but Radar Contact was not able to capture it.Questions:1. Am I expected to make a u-turn to intercept the waypoint RC missed and then continue with LNAV ?2. Or is there another way out to this problem ?Thanks a lot and kind regardsKurt

if you miss a waypoint, simply ask for "direct to next checkpoint" and choose the one after you missed

Kurt,Regardless of anything, you've got to progress an enroute checkpoint within 5m to get credit. This tolerance tightens to 2m for DPs.If you don't progress an enroute within 5m, at about 10m past that checkpoint RC's going to call your hand and you will in fact have to 180^ to pick it up.Next time this happens, (you'll know it's coming if you have the Checkpoint Ding box checked, and don't hear the wav file play), request the next checkpoint to save the 180^. I think it's item #1 on Page 2 of the AdvDisplay for enroute.

Kurt,Yes, you can manually ask for the next checkpoint, but that doesn't solve the real problem.I routinely fly with upper-level winds of over 100-150 knots. I never miss a checkpoint.So we need to find out what's going on with the FMC, and if the data in the FMC is different from what's being sent to RC.So - questions:- When the FMC shows you crossing the checkpoint, what does RC say is the distance to that checkpoint?- Are you using the same FS200x plan in the FMC as in RC?- Are you flying at 1x or faster?- Do you have RC set to a higher priority or is it normal?- How far do you normally pass a checkpoint before RC credits it?- Is RC playing wavs when you pass it?- What's the actual plan when this happens, and does it always happen with that one only or any plan?

Yesterday i was sent into one of the famous 360 degrees turns, just having reached cruise altitude after having taken off from Moscow. In the GPS window it had registred the next waypoint, but not RC. I then tried to request going on to the next waypoint, but wasn't allowed because of traffic..Maybe time for an update for the program? It seems a little silly to me - and annoying. I have been flying many, many times in real life and always having had a window-seat, i can assure you i haven't seen anything like this in real life.

if you ask twice, it will always be approved.real life, pilots fly the flight plan, at least i hope so :-)about 20 of us have been testing v3 for about 2 years. i can speak for myself, i have to try to miss a checkpoint. i don't think the beta testers had a problem with missing checkpoints, or i would have known about itare you flying? the rc co-pilot? an fmc? flying @ 1x, 2x, 4x?

OK - i didn't know that it would be approved after a second request. I'll try that next time... I'm sure there will be one! ;-)Hehehe - i hope so too. Will go on vacation next month in South Africa, so i definately get a chance to see if they do!! Last time i mentioned it, i had been flying myself - but the other times - and this time it was the co-pilot. Between we are on course and the cruise altitude, i hand it over to my co-pilot. I always fly 1x - everything else would be cheating.. :-) There's always at least 20 NM in my flightplan between waypoints and it was flying straight forward - no turns. There were no gusting winds and in fact it was flying up to the wind - it didn't come from the side. I had just reached the cruise altitude when it happened - FL350. (B737-400).

On arrival when the copilot asking for weather and the A/C is crossing a waypoint at the same time, RC will miss the waypoint. I would think crossing the waypoint should have preference. Asking for direct has solved it for me. On any crossing of a waypoint the change over is different. Sometimes RC will change first and then FMC and other times the opposite is true. The FMC and RC must translate the flight plan info differently.RegardsRichR