Thanks for the tips gentlemen particularly JoesCrew regarding the use of simroutes.

When downloading a saved file from Simroutes it doesn't always register in the FS9 flight planner but the file is in the correct folder.Although it does get into RC4.It also loads into the LD767 FMC without problems.

Just to check something basic, sometimes if there's a lot of radio traffic RC4 may miss you overflying a waypoint (5nm past and it won't update, IIRC?) and vector you back to the waypoint you just overflew.Cheers, SLuggy

In the RC preflight application window you can scroll the route box and check your waypoints to insure RC read them correctly.When using long legs you may want to increase the heading tolerance a bit in the RC General tab having to do with great circle navigation discrepancies and RC4's calculations.

Yes Ronzie it's odd that the simroutes flight plans find their way into the various FMCs I use(PMDG and L767)and also they show in RC4 as you suggest.They must get there by way of the PLN file in FS9 but sometimes they will not load into FS from the flight planner.Even though they are in the right place and can be checked with notepad.I did wonder if there was some duplication but I can't find any.There is debate about this in other forums but the main thing is they do get to into RC4 and the FMC so the routes can be flown perfectly well.The problem is editing a route that doesn't make sense(try RJAA to PHNL) but I guess notepad may get round this.Like many long time users I use many work rounds and cheats to get round some of the restrictions in RC4.Heading tolerance is one of them.

I highly recommend you investigate a planner of your choice. I stopped using it years ago but some recommend the freeware super flight planner. Be aware that sometimes it hangs on a build with certain scenery. From AVSIM these files might be of interestsfp405.zip FS9/FSXsfp_fsx_accel.zip FSX database where sfp's build fails.sfptools.zip is an AIRAC converter if you have any laying around. You need to see what format you require. There may be one at the old navdata.at site when they used to be free but now are payware furnished by navigraph.com products. if you already have an FMC subscription see if this format is supported.There are others available.

Good advice but i have access to a vast library of charts and the like and it's only the occasional oceanic route that FS9 won't create properly which causes problems.I can edit the simroutes suggestions with notepad and save them and they then appear correctly in RC4(you must edit the flight level as well),ASE and the FMcs I use.But they still don't load up in the FS9 planner even though they are there.and there are no duplicates.As i said before it's not a problem as the aircraft will do as it's told and RC4 is happy with it too..You don't have the FS9 map view of course,nor the FS9 Navlog but you've got all you need in ASE and the FMC.

Hi.I use Super Flight Planner. I find it won't build its database unless I temporarily remove/disable all AT9*0.bgl in the main scenery folders. If I need to rebuild SFP's database I just put them in my recycle bin until I've finished. I think they are the built-in waypoint files, which may cause a bit of a problem when planning trans-Atlantic routes. Otherwise, despite the lack of documentation, it's not a bad planner for freeware.D

I don't use the FS9 planner but as noted in message #11 in this thread perhaps it is the way the NATS coordinates are formatted in simroutes.

Could be Ronzie.The FS9 planner is weird in some areas that's for sure.Sometimes oceanic waypoints/upper airways show up,sometimes they don't.I also find that the ILS(05R-23L) at NZAA(Auckland)shows up on the map some days and not others.If it doesn't show then you have to do a VOR approach as it won't show on the flight instruments.I've managed to edit the simroutes RJAA-PHNL route so that it makes sense.It's in RC4 as a saved file.Comes up in the LD767 FMC as loaded from the website even gets into ASE so you get the map.But it just won't load in FS9.Even though 2 of the above add ons get the data from it.

Here's an extract of a pond crossing converted into an FS9 plan from a flightaware route pasted into fsbuild for conversion:waypoint.7=5050N, I, N50* 00.00', W050* 00.00', +000000.00,waypoint.8=5240N, I, N52* 00.00', W040* 00.00', +000000.00,waypoint.9=5530N, I, N55* 00.00', W030* 00.00', +000000.00,waypoint.10=5520N, I, N55* 00.00', W020* 00.00', +000000.00,Note that that waypoint ID is truncated to five characters. Most applications do not care about the waypoint ID except for labeling as most just use the coordinates. If you import this plan into a nav instrument that needs to look up the ID in its database that could be a problem. It also might be that the FS planner can only take a five character waypoint ident and might unpredictably behave if the ident is longer.Here is another simroute pond crossing:[flightplan]title=KJFK to EGLLdescription=KJFK, EGLLtype = IFRroutetype = 3cruising_altitude=0departure_id=KJFK, N40* 38.39', W73* 46.74', +000013.00destination_id=EGLL, N51* 28.65', W0* 27.68', +000080.00departure_name=New_York_John_F_Kennedy_Intldestination_name=Heathrowwaypoint.0=KJFK, A, N40* 38.39', W073* 46.74', +000000.00,waypoint.1=SHIPP, I, N40* 19.77', W073* 14.84', +000000.00,waypoint.2=LINND, I, N39* 24.59', W071* 42.63', +000000.00,waypoint.3=3952N 06815W, I, N39* 31.20', W068* 09.00', +000000.00,waypoint.4=4025N 06700W, I, N40* 15.00', W067* 00.00', +000000.00,waypoint.5=4140N 06500W, I, N41* 24.00', W065* 00.00', +000000.00,waypoint.6=4307N 06000W, I, N43* 04.20', W060* 00.00', +000000.00,waypoint.7=4510N 05230W, I, N45* 06.00', W052* 18.00', +000000.00,waypoint.8=4554N 05000W, I, N45* 32.40', W050* 00.00', +000000.00,waypoint.9=4810N 04000W, I, N48* 06.00', W040* 00.00', +000000.00,waypoint.10=4926N 03000W, I, N49* 15.60', W030* 00.00', +000000.00,waypoint.11=4949N 02000W, I, N49* 29.40', W020* 00.00', +000000.00,waypoint.12=4941N 01500W, I, N49* 24.60', W015* 00.00', +000000.00,waypoint.13=ABDUK, I, N51* 38.57', W003* 48.02', +000000.00,waypoint.14=NUMPO, I, N51* 36.60', W003* 17.02', +000000.00,waypoint.15=OKESI, I, N51* 26.60', W002* 03.70', +000000.00, UP2waypoint.16=BEDEK, I, N51* 22.25', W001* 33.52', +000000.00, UP2waypoint.17=NIGIT, I, N51* 18.78', W001* 10.25', +000000.00, UP2waypoint.18=OCK, V, N51* 18.30', W000* 26.83', +000000.00,waypoint.19=EGLL, A, N51* 28.65', W000* 27.68', +000000.00, OCK1FSo, maybe some apps/nav instruments, might have trouble with the long id field. I don't know about this for sure but it is a possibility.Again simroutes export has the cruise altitude as 0. That needs to be edited because as mentioned that is a negative change when compared to airport elevations except in a few locations below sea level.