xfa

To give you an idea on take off you would select Flaps 1 at V2+15 and Select Flaps UP at 1. On landing you would usually select Flaps 1 downwind or approaching base at about 220 - 210 kts slow down to about 180 knots and flaps 5 turning final then gear down and flaps 15 capturing glideslope select Vapp for Flap30 and select Flap 30 on the 15 tape mark. There are variations to this but this is fairly usual.

No problems just the pilots side FMC blank out as reported above.

Since the cost index affects climb, cruise and descent performance/economy. Profile speeds may still need to be manually adjusted on descents to meet common ATC expected profiles. It isn't a case of just plug in a 'set and forget' CI figure, this especially for some of the low CI figures quoted above, for sure airlines do not fly these figures on descent.

LM won't be getting a cent from me. I'm happy where PMDG have taken FS with more products to come, that will do me nicely thank you.

It may be used as part of a take-off sequence, as follows: Above 400' RA call for roll mode (HDG SEL or LNAV). At thrust reduction height 800' set climb thrust PUSH N1 switch. Verify climb thrust. At acceleration height say 1000' set flaps UP speed. After retraction call VNAV. Then engage autopilot. There may be variations of this sequence but this will give you an idea of where N1 switch may be used. Btw don't try this on the NGX (post HF4) because it won't work, at least the FD bars will not command the MCP speed you select. I believe this is a bug for an SP1 remedy.

yep great plane, nothing else comes close. Thanks PMDG. john topo

I suggest submit a ticket for support. It could well be xml.dll issue this file gets corrupted by other add ons try to use a backed up if you have it see if that makes a difference. john topo

Brisbane ybbn to Melbourne ymml using Orbx scenery.

My guess KORD KDENjohntopo