Totally delighted with the 777 in my FLY!2K.I load the flightplan, (which I've generated and saved in FLY) in the FMC, activate and execute, and take off. I point the plane, with the AP HDG select, towards the desired flight path by using the vector map as a reference.When the plane hits the desired path at a shallow angle, I press LNAV but nothing happens. If anything , the plane starts turning away from the flight path. Not even the armed LNAV message comes on.What am I missing here?Happy but frustrated...Eytan Ornstein

Been a while since I last flew this one but from what I remember you have to be careful with the distances between waypoints. Try it with no more than 200 miles between waypoints.Andrew Luck18 miles SW EGSH

Will try and report back.Shouldn't this kind of thing be mentioned in the manual?Eytan

This was a limitation of the Fly! autopilot that LNAV relied upon. Hope it works for you.Andrew Luck18 miles SW EGSH

Still cannot get it to work. I follow The 777 guide by Jerome Zimmerman to the letter, but the damn LNAV is totally unresponsive.Does the FMC need to be programmed any special way in order for this to work?Or maybe I have to engage LNAV at the point of departure, because, strictly speaking, that's the first point in the fpl.I hate it when things don't work the way they're supposed to.I started out with the Pilot in Command B767 in FS2000, and that was an educational experience. the FMC there is 99% functional, and just programming it prior to take-off takes a good 10 minutes.Eytan 40km NE of LLHA.

Just remembered something else about the Fly! autopilot. When you start the flight, check on where the airplane thinks it is. Very often I used to find that the airplane thought it was already at the destination and LNAV would subsequently fail. What I never found was a way of getting around this problem.Hope this helpsAndrew Luck18 miles SW EGSH

I've flown several transPacific hops and not a few long flights overland, with few or no waypoints. The FMC will fly a Great Circle between these points when they are far apart. The GC route from Japan to Las Vegas, NV, USA goes through the Aleutian Islands off Alaska, so any resemblance to the more familiar rhumb line tracks on a standard Mercator map is small. On long hops primarily eastbound or westbound, my LNAV intercept course is nearly north (in the northern hemisphere); get on the side of your departure point toward the destination, south of the rhumb line and then fly north. Then wait, and the LNAV will eventually intercept.As the route that shows up on the PND is the rhumb line, this means you often won't see that reassuring magenta line except near the departure and arrival points. It takes an effort of will to get used to it, but I've negotiated some really long non-stop hops flying point to point, and it works.I hope this helps -- Dave Reed KLAS

Dave,I understand what you're saying. One can see the discrepancy between great circle track and rhumb line by watching the a/c icon in the FLY vector map. Between distant waypoints, esp. halfway, the a/c is on LNAV, but the icon is further south than the white track line displayed in the vector map.I've just a nother hop between KLAX and KDFW, with many close waypoints,(50-90mls.), and still the LNAV refuses to engage. I can't even see the 'ARMED' mode on inthe PND. When LNAV is pressed, the a/c just follows the direction chosen in the HEADING SELECT mode.So what's wrong. Is this a bug or something? My PMDG B757's LNAV works just fine, BTW.Eytan