So I flew a couple of flights in USA, and noticed the different terminology etc. I climbed to altitude provided and with ATC command, turned to my course, and proceded on course. Everything went AOK from there on.So I wanted to fly around the world, experience the different terminology etc... Boston to Heathrow is fine, then I try heathrow to milan, italy.I take off and ATC keeps telling me to climb to the next altitude. Never anything about turning or procedding on course. I was up to my cruise before ATC told me I was off course and to turn around (which I knew, but didnt want to get the ATC mad). Rest of the flight was ok.Milan to Ghandi International... no idea what happened. I Took off and started to climb. Again, no word about were/how/when to turn to course. ATC continues to tell me to climb, and I decide to turn on my own to my prestablished IFR plan. LNAV locks and im on my way. Then ATC tells me that I am significantly off course and to turn heading xxx until in range from navigation or something. I look at my displays, everything fine, dead on the magenta line, tracking normally. ATC continues and continues to yell at me about changing course, though I am right on.Any ideas? I have really never flowing outside the US, and havent experienced these ICAO rules etc..any ideas?thanksdan h.

I had the same problem and found that FSUIPC 3.51 was the culprit.Somehow the wrong heading is getting read. I went back to 3.50 andthe problem disappeared. 4 flights in a row A+. Look for my post"Heading or Track". Hope this helps.

Hi Dan,It sounds as if the first wp in your flighplan is within 30 miles of the departure airport.In this situation RC assumes you are flying a 'departure procedure' and departure will not give you vectors, you fly the plan as filed and make sure you pass within 2 miles of each wp.Eventually (often once contacting centre) you will be told to proceed on course.As far as the off course wd is conserned, Bob may be right and it's a problem hopefully solved with the latest FSUIPC (v5.2)However it's always worth checking that the wp showing at the top of the RC menu is the same as the one you are actually flying to.All the best,John

thanks for the response!I will have to try the flight with a WP 30 miles out!I have been doing flights w/ pretty much default options and havent really messed with any options so I dont think I would have messed something up.I creat a flight plan with fsbuild and load into FMC via 747/737 by pmdg.I have only had these probs when departing from a non US airport (italy and heathrow both threw me probs.Like you have said, I will try the WP distance trick.I have changed to FSUIPC (v5.2)ill keep you updated!thanksdan h>>edit>>Just checked my flight plans. It seems that my flights that have problems have a WP less then 30 miles. The flights that are higher have worked fine!

Hi Dan,That's the solution. wp's within the first 30 miles means departure won't vector you - they assume you are flying a dp and know what you are doing. You must pass each wp within 2 miles though or when told to resume own navigation RC will expect you to go back to any wp you missed.If this happens and you don't want to return to the wp you missed there is a menu option to request direct to a wp further on in the flightplan. If the controllers in a good mood he'll allow you to do it!All the best,John

That FSUIPC v. 3.52. Let us not rush Pete :) .I noticed when using LNAV for a DP in the PMDG 737NG-800 (out of Zurich) the path prediction for the first waypoint BREGO which indicates about a 90 degree path change on passing caused an anticipated curve for this more than 90 degree turn which brought it this once just outside the RC credit limits. The next time it was within, so it must be on the hairy edge.The options are to use HDG SEL at this stage and track a little closer as indicated on the ND or just use the extended RC menu option next waypoint when you are near there so RC waypoint credit is not an issue for these LNAV tight turn anticipations.It appears in watching my DVD of Bel-Air 757s out of Zurich that they are still hand-flying at least for yaw within this range, I expect for traffic deviations as well. It might be their policy.