I'm slowly being driven mad by discrepancies in the FMC database/FS9 scenery/approach plates with the 737NG. None of them seem to agree. I've dutifully updated the Aerac cycle to 1005, and downloaded the relevant plates, only to find on numerous occasions that the actual information in FS9 is different - runway designators are different and occasionally ILS frequencies and more.I'm not particularly interested in realism (as in having the latest up-to-date nav info) but would simply like everything to match up - any suggestions?What I'm really trying to do is to find a short, north-american route (c400 miles) that I can operate without having to print off a blizzard of SID/STAR/Plates, and that has everything matching: I'd like to fly it a couple of times for practise, before starting to learn the FS2Crew procedures - -this is proving more difficult than I had expected.

If you are using default scenery, then no wonder, the data predates 2003 at least.

Thanks - Ummm - It's not immediately clear what the solution would be from your post?

Full names here please.Andrew pointed out the obvious. You have to expect current data to not always agree with MSFS default scenery that is about a decade old. There's lots of things you can do, you can pick locations that don't have changes in freq or runway numbers, you can update the MSFS scenery, you can update the AFCAD, etc. Your choice.A good medium distance trip for practice is KDFW-KATL. The entire route is simply a SID connected to a STAR, both of which are RNAV. A shorter one is KLAS-KLAX, there's lots of these out there.

Hi there,Why not use an older Airac. I use the older freeware 0608, because it matches all my charts and Afcad files. Works perfectly most of the time.I also rewrite the procedures files if there are changes that cannot be overcome by fiddling with the FMC.