Strange problem: All was fine until I crossed LOONS and then ATC started to be persistent to put me into a circle. I did not turn around again after the first time, I got back on course and then used the Dir Ckpt command to request the next waypoint from where I was, which at the time was KONGO. This seemed to satisfy ATC and they quit nagging me to go in circles. I did nothing to make it do this and I have not had this problem before. My flightplan was as follows: KSLKSYRAUDILEXTOLCNTERSFK04ZUUCSPSBEJOCYLOONSGEFFSHVQKONGOTONIOVXVCALCOVUZDELBEMEIAny idea what was up with that? Thanks in advance.

Strange problem: All was fine until I crossed LOONS and then ATC started to be persistent to put me into a circle. I did not turn around again after the first time, I got back on course and then used the Dir Ckpt command to request the next waypoint from where I was, which at the time was KONGO. This seemed to satisfy ATC and they quit nagging me to go in circles. I did nothing to make it do this and I have not had this problem before. My flightplan was as follows: KSLKSYRAUDILEXTOLCNTERSFK04ZUUCSPSBEJOCYLOONSGEFFSHVQKONGOTONIOVXVCALCOVUZDELBEMEIAny idea what was up with that? Thanks in advance.

it's always helpful to have a log, any troubleshooting is just speculation on this part. how far is SYR fro KSLK?did clearance delivery say "...via departure procedure..."?did tower give you a heading to fly when clearing you for take off?did departure give you a heading to fly?my guess would be a departure procedure, that you didn't fly correctly. departure procedures documented in the manual. if you still have a problem, make a log (instructions pinned to the top of the forum) and send it to me. make sure you click debug before loading the .plnjd

I placed your plan into FSBuild (I used KMEI for a destination). What planner are you using and did you export to an FS9 .pln file or (if FSX) a .pln or xml version. I ask because we have had sdome reports of an FSX XML type file export from earlier versions of FSBuild.It appears EJOCY through HVQ (Charleston VOR) is MOSTLY a straight course followed by a turn to KONGO. I extracted a map attached here and the extracted route direction. (The heading column is from the waypoint to the next.) These headings include a crosswind compensation so they may slightly different from yours.Since the is around the middle of your plan we should not have crossing restrictions issued I would think. I used FL280 to generate a plan.That leaves navigation. As you crossed LOONS did the RC status window advance to GEFFS? If not you were off-course missing the waypoint by more than five miles. Another reason you may have not received credit is that if you were doing the comms there might have been an outstanding ack which would prevent a waypoint credit.Did the RC status window show similar headings to the waypoints involved as in my attached image and did you fly those headings?A log file sent to jd will tell all if I did not catch anything just from my estimate here.

Thanks for the replies. I did not do anything differently last night than I ever do. I was flying the Eaglesoft Citation X 2.0 for FSX and input my flight plan manually, which was created by the FSX flight planner. I just have never had RC turn me around in circles before and it surprised me. I admit that I don't go to the trouble of using departure procedures or STARs. I rely on RC to tell me what to do. I know, lame. But there is much I don't understand and I just wanna fly, man.I did notice that I am off a bit from the FMS presecribed route when following my flight with Plan-G on a separate computer. I saw this in the past but chalked it up to database errors.I will watch things and send more info to JD as instructed if it happens again.Thanks again.

FYI:Eaglesoft has released a patch version 1.83 for both FS9 and FSX users as I understand it.It would not hurt to check your version of FSUIPC4 against the latest version, links at the top. Apparently from what I see the Citation X requires it. If it uses it to determine the location of the aircraft as does RC I'd check it.Some complex aircraft users such as PMDG were reporting course differences in the FMC. Insure your registry correctly defines FS as FSX. A free tool in the free downloads section of flight1.com will correct that.You are correct in suggesting possible database differences between the FMC and the FSX plan waypoint coordinates. Not having the Eaglesoft product, I don't know if it will import an FSX .pln format into the FMS using those coordinates or in reverse export an FMC route to an FSX format. That would insure that RC and the FMC would have the same waypoint coordinates. According to the Eaglesoft web site the Citation X is delivered with AIRAC cycle 0711 (November, 2007). The FSX database is much older. Another way if it exists is to use a third party flightplanner that exports in the Eaglesoft FMC format and the FSX format if the FMC can import a plan.If RC gives you a resume own navigation after pointing you in a correction heading remember that is from your present position direct to the next waypoint as shown in the RC status window.Thanks for responding.

Thanks Ronzie. I check the ESDG forum often and I am running Hotfix 1.83. I had some issues in the past by importing the flightplan from FSX into the FMS, so I always enter the waypoints manually as suggested by one of the ESDG developers (Bill I think). Anyway, I checked into updating the database and I am unwilling to pay for something like that. It is my firm belief that the database supplied should be one that works. I don't care if things change in the real world, they don't change in FSX so I am ignoring the possibility that the AIRAC is off by that much. Perhaps to my peril. Thanks for the suggestions. I also fly another complex plane, this one not even as far along as the Citation X. That is the ATR 72-500 from FlightOne. Between these two planes, perhaps something will shake out as a culprit. Who knows. I took a long flight last night with debug enabled just in case, but nothing happened out of the ordinary. If I ever fly the same route as I reported in this thread, I will run with debug on. I am all over the map because I fly with Flyteline and almost never do the same route twice. So I will chalk it up to a fluke I guess. I am very pleased with the purchases I have made so far (hundreds of dollars) to make my simming experience the best it can be. A New Year resolution might be to learn to use departure and approach plates properly. How hard can it be? 8^)

http://www.faa.gov/library/manuals/aviation/I have both instrument manuals. They are quite a bit to digest online in the links above.Browse the Instrument Procedures one. It is newer and covers airliner and large airport procedures. Chapters 2, 3, 4, and 5 cover all the flight phases including how to read charts and the relative operations. Most of this pertains to ICAO (outside of FAA territory) procedures as well. The most noted difference is that in FAA land the transition altitude is fixed at 18,000 feet with the transition level at FL180. In other areas it can vary with the locality. (The "B" key in all FS versions is harded coded to 18,000 feet globally and RC uses the local standard as explained in the RC 4.3 manual. Using the B key to set altimeter may cause you to be at the incorrect altitude outside of FAA airspace.) The Instrument Procedure Handbook delves deeper into RNAV which the FAA and other jurisdictions are moving toward.I get my FAA charts as free bundled by airport downloads from flightaware.com. Use airport info or the resources tab to navigate to them.The latest version is listed on Amazon:http://www.amazon.com/Instrument-Procedure...7921&sr=1-1at about $14 US. You'll also may find that in bookstores like Borders or Barnes and Noble. I have the previous year's one.In the meantime read the RC tutorials. I noticed that chart examples and interpretations start on page 88 of the RC 4.3 manual.

A New Year resolution might be to learn to use departure and approach plates properly. How hard can it be? 8^)

Very helpful thanks. I have read the tutorials and am practicing. Thanks a lot Ronzie. See you in the skies.