Started using RC4 now as my default ATC now since getting the Level D 767.I am running into an issue fairly regularly though. I have my flighplan, RC reads it fine, all good there.I takeoff, fly my SID and then proceed enroute but after some stage RC tells me to return to a heading which is usually almost the opposite of what I have flown saying I went off course etc.I don't know why it does this but it's extremely annoying so what am I doing wrong to cause this?Thx

...what am I doing wrong to cause this?You've missed a flight plan waypoint - the clue is in the 180 degree turn. In order to credit you with having passed a waypoint, RC requires you to be within 2nms of it in the departure phase or within 5nms in the en-route phase.It's a simple matter to confirm that this has happened. RC shows the name, bearing and distance of what it considers to be the next waypoint on the top line of its display window. If this is different from the next waypoint in your FMC (or whatever you're using for navigation) and especially if the bearing shows it's is behind you and the distance is increasing, it means that you have not flown close enough to the waypoint and RC is still expecting you to go there.In version 4, the controller will try to turn you back (hence the 180 degree turn)so that you can progress the waypoint correctly. In the new version currently under development, this is handled differently but in V4 you will always be turned back. The workaround for V4, though, is very straightforward. When the controller turns you back, acknowledge the instruction and then immediately request direct to the active waypoint in your FMC (or any other which is ahead of you). This will be granted and you'll then be "back in synch" with RC.Pete

OK thx, I understood from the manual though that waypoints within the first 30nm were ignored if you were given to fly out using "procedures".So I understood that in a way that I didn't have to fly every waypoint.In any case thx for the workaround.

absolutely the opposite. anything within 30 miles has an even higher threshold to meet. you must pass within 2 miles of evertyhing within 2 miles.

RC uses the flightplan exported to FS from your planner. If you are using a navaid database for SIDS and STARS, you may have a discrepancy between your navigation instruments and the plan you sent to RC.Search this forum under "FMC" to find some tips for synchronizing or working around this discrepancy.To clarify departure, by default, if the first waypoint in the plan you sent to FS is within 30 nm of your departure airport, RC will not vector you for departure just giving you a fly as filed plus assigned altitudes. RC will then expect you to hit the waypoints you filed within the limits jd expressed and displayed as Pete stated. You also have an extended menu item in the RC window where you can choose your next waypoint allowing you to skip a missed waypoint.Know how to manipulate your FMC or GPS if controlling navigation and use your MCP/AP panel with HDG entries as necessary to accommodate ATC. Know how to update your FMC/GPS next waypoint to it follows the route ATC dictates until they are in synch with ATC. Consider, if possible, importing your FS flightplan into your FMC/GPS so RC and your navigation instruments are mostly in synch.Several planner applications can export to various FMCs. Use their SID/STAR database to export to the FMC and FS formats and then import that plan into the FMC. The planner will convert the SID/STAR in the plan to waypoints in the exports. You also may wish to eliminate within the 30 nm of the airports when you are accepting vectors. In a departure if applicable choose a waypoint common to all runways for the SID of choice. Do the same for arrival if you expect vectors. For arrival you can choose to fly an IAP when your runway is announced by approach in which case you will not be given vectors or altitudes but expected to fly the arrival waypoints in your filed plan including setting up your final approach.