WOW what a program. I LOVE IT! ATC constantly gives me attitude about my heading, I have the proper heading set and heaed in the correct heading but ATC says im of track. Does anyone else has this problem or is it just me?Erik Z

Hi Erik, I have the same problem. I have a message below that I sent yesterday. Every flight I take with RC I get flack from the ATC even when I am on the coarse they have given to me. I wish I had two way radio, I would burn some ears.Dave Lusty

Yea ya gotta love it. I fell like im on FS restriction.

Last night I missed the HRV intersection as I always do and turn too soon, and was on my way to the PEKON intersection when ATC asked if I was still there that I was off course and gave me another heading which was a 360 back to the HRV intersection. I use FSNavigator but I always miss the HRV intersection. I fly real life flight plans that ExpressJet "Jet Link" flies.

The heading you are expected to be on is in the RC window including the next waypoint you are expected to cross. If you are on departure or approach at lower altitudes you have to be within a two mile radius of the waypoint. Using the extended menu you will find in the menu an option to go direct to a selected waypoint on your plan. Enroute at higher altitudes you have a five mile radius around the waypoint to hit it.If you are using a soft waypiont (i.e. a fly-by rather than a fly-over) in a departure in the controller page choose with or without altitude restrictions if you wish to navigate your own DP. You will still have to eliminate that waypoint off the RC credit list by instructing RC to skip it but RC will not care if you are off heading and you will not get vectors.I find it is best to leave those close to the runway departure waypoints out of the plan exported to RC and use the NOTAMS option to give me departure flexibility on headings to the waypoint RC wants me to cross that is still in the plan. You still need to cross waypoints on the list but you will gain heading and altitude latitude if needed. The controller will remain quiet.If you use NOTAMS on arrival you'll still get vectors if you do not select an IAP, but the controllers will remain silent if you are off course. The negative side is that without controller off-course warnings you could get into never-never land (lost) without knowing it.

if you keep having the problem, follow the directions at the top of the forum, and generate a .logit is very important to click debug BEFORE loading the .plnron has gone through some of the gotchas that you have to know about.but if you are new to rc, i strongly suggest you read the tutorials in the manual, and fly them. they were written with the sole purpose to educate you.and another generality, get your head out of the fmc. atc doesn't tell the fmc what to do, atc tells you what to do. and there isn't an fmc in the world that takes precedence over what atc tells you to do (maybe air force one is an exception :-))if you have a departure procedure, you have to fly it pretty tight. you may have a departure procedure defined in your .pln and not even know it, and you're letting the fmc fly the plane. have some fun, live a little, fly the plane. let the autopilot take over when you are at cruise, and it's boring. don't let the machine take away your fun.if you are told to resume own navigation, that doesn't mean you press a button, and let the fmc turn to intercept the little green/orange/pink/blue line on the display. that isn't what resume own navigation means. it means fly to the next checkpoint.in v5, we're going to take care of that.if you have long .pln, and the checkpoints are hundreds of miles apart, you should still be fine with v4.3 - which now calculates desired heading based on the great circle route.also, atc doesn't care when your fmc says you should start your descent. most likely rc will tell you to start down earlier than the fmc will say. i do that, so you stand a fighting chance of meeting the crossing restriction. but you have the option to take that initial descent clearance at pilots discretion, which means you can stay at cruise until your fmc says to start down. but you won't get any slack on meeting the crossing restriction. also that pilot's discretion option for initial descent is not available if the rc copilot is handling the comms.in approach, unless you ask for an iap approach, you do what approach tells you to do. it's usually a very nice direct to airport, downwind, base, intercept and final approach. depending on the heading you're approaching the chosen runway, you may be turned directly to base. you may not even be turned to base. you may be approaching the airport so close to the runway heading, you're left to joing the ils when it comes into range.all these intricacies are explained, and highlighted in the tutorials. i know they aren't the most glorious plans, to the prettiest airports, but they serve a purpose. to get you up to speed in the shortest period of time.the sophisticated users that install rc, and start flying their .plns, are missing out on a wonderful learning experience, one that will open their eyes to the possibilites and little things (qnh instead of inches, "fly heading 240 degrees" vs "fly heading 240" (can anyone tell me why/where one phrase is used as opposed to the other?)sorry for the long post, but it was as good a time as any to beg y'all (southern term for "everyone") to fly the tutorials, learn, and enjoy.jd

Being a Southern Boy I definately understod everything especially he YALL. Great Tutorial, it really answerd many of my questions.ThanksEZ

Hi All, Earlier I complained about getting flack from ATC about my being off coarse. I blamed RC as being at fault. But as the saying goes "If all else fails--follow instructions" I read the manual and did some more flights following insructions and found that Radar Contact is a great add-on and makes things more "As Real As It Gets"My heading problems were my fault and not Radar Contact.Dave Lusty