Hi guys.Just now loaded a flight from the FSX startup window, choosing the JS41 at EHAM gate B93, loading fuel, setting time and date, and pressed "Fly now".Took off towards EDDF via Lunix 1V departure out of 36L. The ATC clrd me to NAPRO, and i hit the DCT to NAPRO on the FMC and switched the NAV button on. And for the first time, I also encountered the "fly north problem".After apologizing to ATC and using the HDG function to fly towards NAPRO, I read through this forum.I suddenly realized, that I had not loaded a flightplan via FSX, as I always program the FMC from scratch, or use a presaved route, that corresponds to real life procedures flying online on IVAO.In flight, I created a flight plan via the FSX flightplanner, and pressed OK, but No to locate aircraft at departure airport.And now for the great news. I pressed the NAV button, and the plane nicely as usual followed the flightplan and flew to the next waypoint according to the FMC.The standard flightplan I created was just a default one, wich was no were near the same as the one I programmed in the FMC, but still this seemed to make the FMC use the programmed route.Hope this works for everyone - it's pretty simple, just create/load any FSX flightplan, and choose not to use it.Using W7 FSX SP1 and 2, JS41 SP1, ASA.Martin

Thanks mas618!!that's really helpful!cheers!

Hi,I was having the same "turn North" issue with LNAV. I also save at each airport after landing and start from there. I just wanted to confirm that creating and saving a FSX flight plan solved the problem. As soon as I came back from saving the flight plan and hit LNAV it behaved.Thanks,Doug

To all of those who say you should load a flightplan in FSX, I have never loaded a flightplan through FSX for the J-41 and it flies perfectly every time. I don't see that there's a need. It flies perfectly fine without it, so there's no need to add extra (and potentially conflicting) information into the mix.Of those of you among the "realism first" I-want-to-fly-this-thing-like-I'm-flying-the-line (those who get to a destination and saving your situation for the next hop), are any of you taking into account that if you're saving a flight that you have misconfigured, it's going to continue to be misconfigured (noticed the comments that basically say if I run it from C&D, it's fine)? Are you following the correct shutdown procedures? Also, keep in mind that even if you're the one who shut it down, you should still run through a quicker version of the Acceptance Check. You can still make mistakes or forget something.To be honest, you should also keep in mind that even aircraft are sometimes subject to the Windows Fix (shut down and reboot). I have sat on the ramp a couple times waiting for a recycle of the nav system. As a person, if you're kept busy wherever you work, your desktop becomes cluttered and messy until you get down time to clean it up. Same goes for computers: give it time to shut down and start back up and you'll be good to go. I say that because that is also more "realistic." You may think you're being more realistic by not powering down completely, but I can tell you that in the regionals, you run the full checklist, every time (at least the ones I've experienced). The only thing that gets left on (and only if there's ground power avail) is the avionics if the crew is coming back to it for the immediately following leg, otherwise it's off. Following that, you should really load the C&D save every time, unless you are actually sitting there on the ground waiting for the next departure in 30 minutes, without exiting FS, and properly follow the checklist to put it in the C&D state on your own (FS2Crew follows this perfectly, by the way).