July 17, 200322 yr I dont what I did wrong, VNAV wont engage. I did my usual FMC pre-flight planning with entries for all the waypoints, cost index, OAT and performance/thrust profile. When I took off, I had no problem engaging LNAV at about 1000 ft. But VNAV wont engage. It always says UNABLE NEXT ALT. And yet the plane is climbing on its own, no LVL CHG nor V/S. Can someone spot my error?ThanksMichael TanCanberra http://forums.avsim.com/user_files/23800.jpg AMD Ryzen 7 3700X Nvideo 970 GTX FSX + MegaScenery
July 17, 200322 yr Hi there Down Under !Alt restrictions show FL if they're entered as FLs.The FMC thinks those alt are in feet.So he says : AC above next constraint, VNAV unable.Instead of 100, input 10000 or FL100cheersanthonyPS the patch will make constraint input more realisticAnthony MertonPrecision Manuals Developmenthttp://www.precisionmanuals.com
July 17, 200322 yr Author Hi AnthonyIs that all? I have been pulling my hair for nothing (I need a wig now ;( ). Wish the manual/tutorial could be more specific on this point.ThanksMichael TanCanberraIt's minus 3 overnight....not too bad AMD Ryzen 7 3700X Nvideo 970 GTX FSX + MegaScenery
July 17, 200322 yr Were those altitudes entered with three digits? If so, they are supposed to be interpreted as flight levels by the FMC. Is the PMDG FMC getting this right?xxx is xxx00'.xxxx is xxxx'.xxxxx is xxxxx'.Altitudes below the transition altitude (e.g., 18,000 in US) are displayed as xxxxx', and above as FLxxx.Source, Continental 737 flight manual, but I'm pretty sure this is common. 767PIC and DF737, two other Boeings, do it this way as well.Lee Hetherington (KBED)
July 17, 200322 yr Commercial Member Dear Lee-did you read Anthony's post?I quote:"PS the patch will make constraint input more realistic"Thanks for the suggestion, but it's already been taken care of. Lefteris Kalamaras - Founder www.flightsimlabs.com
July 17, 200322 yr Sorry. I missed the PS.Note to self: next time read before writing.Lee Hetherington (KBED)
Create an account or sign in to comment