I'm using FSX Windows 7 64 bit. I've been flying RC with a PMDG 737-900ngx and an Eaglesoft Citation X, both with the same problem. Around every four flights I will be in the enroute portion of the flight, on track well within the heading allowance and out of the blue ATC will advise I am off course and issue me a new heading about 180 degrees from the heading I am on. I am acknowledging the new heading and then going to the Direct to Checkpoint menu selection as fast as I can. Sometime this is fairly quick and easy, sometime it is a real hazzle to get to. As soon as I can request direct to the next checkpoint, it is approved and the crises is over. This is the only problem I have had with RC. Is this something RC is programmed to do to just play with you or what? This is totaly unrealistic. First, I'm right on course, and second ATC would be on you long before you got 180 degrees off course. ???? Mike

do you have a sid in your pln file? if so, you have to meet a closer passage distance.

 

to figure why you're missing the checkpoints, i'd need a log. instructions on how to make one, is pinned at the top of the forum. be sure to click debug before loading the .pln

 

jd

The 180 is returning you to a path or a more likely missed checkpoint. Make sure you have received credit for all passed checkpoints by looking in the status area of the RC in flight window. Depending on IAS and bank limitations of the aircraft, and the phase of flight indicating waypoint tolerance, if you have a course change greater that 60 degrees the navigation system might start an advanced turn causing the turning path to fall outside of the 4 nm or 2 nm waypoint tolerance.

 

If navigating by FMC or FPS be sure flight plans are in sync between RC and and the nav equipment. There also have been cases where the magnetic declaration (deviation) file has been replaced by an add-on resulting in nav gear to have an offset to the correct path.

 

If this occurs on very long legs this can be a conflict between direct and great circle navigation. In such cases increase slightly the heading allowance in the RC general options tab.

 

The crossing restriction at 40 nm from destination is still in the enroute portion at 11,000 feet or FL110, or 12,000 feet or FL120 depending on your arrival direction. If missed you'll get delay vectors until you are on the correct altitude. Be sure you have the altimeter set to local or standard pressure depending on transition altitude.

jd, I've printed out the log instructions, and will send you one (hopefully), the next time this happens. Mike

I have had this same problem twice now. At first, I thought I had missed a checkpoint, so I went back a few days later (today) and flew it again. Flight plan from FS Commander, weather from FSMeteo, IFR, low level, KSFB to KABE, in the Lear 45. Loaded the 2-d cockpit, opened the GPS and flew right down the track, checkpoint to checkpoint, using the AP and heading bug. Halfway through the flight, I get chewed out for busting my route (while I'm still dead-nut on the track, and told to turn 60º off-course "until safe to resume."

 

At that point, nothing I could do seemed to correct the problem. I turned to 30º, and was told to turn to 130º, and then to 170º. That's when I dumped the flight. I was more than an hour into this flight, so it gets frustrated when this happens.

 

BTW, I am running Win 7 64-bit w/4 Gb of RAM, and also running (of course) FS Commander and FSMeteo, with nothing else in the system. HELP!

A work around is to request a "direct to" the next checkpoint listed in your RCV window.

Compare in the RC in-flight window the heading RC expects and the heading you are flying. See if the next checkpoint agrees with your GPS next checkpoint on the route. Be sure you are flying at normal FS speed.

 

Some of the magnetic deviations especially in Pennsylvania are up to 13 degrees East currently. Have you installed any scenery that modifies the magdecl.bgl in FS? That can cause errors in GPS and FMC navigation.

 

Are you being guided by FSC maps during flight. It also seems that FSC has yielded problems in the plan coordinates as I recall. FSC now uses AIRAC data from from navigraph.com. I'm not sure if that updates magnetic deviation for its functions.

 

For enroute RC pulls coordinates from your plan for checkpoints and applies trigonometry. Then it looks at your heading. Try increasing your heading allowance in the general options of RC to 25 degrees to calm the warnings. If you encounter string crosswinds your heading could also be beyond allowance after crabbing for the wind correction.

Compare in the RC in-flight window the heading RC expects and the heading you are flying. See if the next checkpoint agrees with your GPS next checkpoint on the route. Be sure you are flying at normal FS speed.

 

Some of the magnetic deviations especially in Pennsylvania are up to 13 degrees East currently. Have you installed any scenery that modifies the magdecl.bgl in FS? That can cause errors in GPS and FMC navigation.

 

Are you being guided by FSC maps during flight. It also seems that FSC has yielded problems in the plan coordinates as I recall. FSC now uses AIRAC data from from navigraph.com. I'm not sure if that updates magnetic deviation for its functions.

 

For enroute RC pulls coordinates from your plan for checkpoints and applies trigonometry. Then it looks at your heading. Try increasing your heading allowance in the general options of RC to 25 degrees to calm the warnings. If you encounter string crosswinds your heading could also be beyond allowance after crabbing for the wind correction.

 

I might have found out the problem - I may have loaded an FSX flight plan into the flight and then loaded an FSC plan into RC. I have just discovered that FSX will not load a FSC plan, any plan. I even tried loading one of their preset plans, and FSX will not load it. So what I think may have happened was that I was flying the FSX plan, and it deviated from the FSC plan loaded into RC.

 

I have a request into FSC to figure out what the problem is with their program and FSX. I'll keep you informed.