Pltskiracer

Ok I stand corrected. The missed approach altitude on the legs page is irrelevant for the Vnav approach phase. The "on approach" logic however allows the MCP altitude to be set above the airplane altitude for the missed approach. When the MCP altitude setting is at least 300' above the current airplane altitude, Vnav continues to command a descent. As long as you meet these requirements, the aircraft will not capture Vnav ALT. You are correct, V/S and FPA has nothing to do with Vnav or approach logic. This is a basic mode function. What Blockpoint version are you using? Christian

The aircraft knows exactly what the missed approach altitude is. This altitude is already pre-programmed in the fmc database. Just look on the legs page. I really do not understand why you are having such a difficult time understanding this. Also, we never fly an Vnav approach to an MDA. We only fly a Vnav approach to a DA if it meets the validation criteria and if the Rnav or Rnav GPS minimums box on the chart (We use lido charts) includes the text "VNAV'. Most approaches do these days and it always validates. Its is the same principle for RNP AR approaches also. A circling approach is a different animal all together. It is recommended to fly an ILS to a circle using V/S. If not it is a bit difficult to change from G/S to ALT. Vnav Path works good. This automatically changes to Vnav ALT at the MDA. You then fly TRK SEL followed by TRK HLD etc during the circling phase. AT MDA set missed approach altitude when Vnav ALT or ALT is annunciated. Christian

Im a bit surprised you have not done this on a ppc or seen it when flown a vnav approach. Vnav Alt will never engage when " on approach" mode is active and you are at least 300' below the fmc missed approach altitude. It is system logic. Vnav path will follow its computed path to at DA. Airplane will even level off, fly straight to follow the computed path/ altitude restrictions. Irrespectful of what you have in the MCP Altitude window. Try it next time you are doing a vnav approach or in the sim. Thanks for the tip regarding the keyboard key. I might give that a try. Christian

I also happen to be relatively familiar with the real 777's as I have over 7000 hours flying them. About 4000 hours as a Captain. I think I have a pretty good understanding of the way the airplane is flying. I am just informing you that when in "approach mode" and with Vnav Path engaged and when 300 feet BELOW the published missed approach altitude. Vnav Alt will not capture. Its a pretty smart airplane. When you are on approach with Vnav Path and minima set followed by missed approach alt set in the MCP, you can run the altitude selector up and down, slow or fast all day as much as you want. It is "locked" in vnav path and will not level off until you get to minima. The FD's will then command level flight if AP is not disconnected. Example: Start approach at 3500 feet. Missed approach altitude is 3000'. Approx two miles prior to the FAF and with Vnav Path or Vnav Alt engaged you set the minima. (The altitude selected and displayed in the MCP window is tied to the minima selected on the PFD) and you open SPD Intervention. This is the only time you can open SPD Intervention and still have Vnav Path engaged. At 2700 feet with Vnav PTH engaged you set missed approach altitude. Christian

It should not matter how slow or fast you wind up the altitude selector on the MCP. If in Vnav path and on approach and 300 feet below missed approach altitude, the logic will never allow vnav alt to engage. I have flown several vnav approaches and every time i set the Missed approach altitude it captures Vnav alt. Again this is not correct. If you fly the approach in basic mode; VS or FPA you set the missed approach altitude approx 300 feet above MDA. ALT HLD should not capture at any time. At MDA both F/D's off and PNF's FD back on. Christian

There is an error in the approach logic when flying a VNAV approach. Normal procedure is to set the MCP missed approach altitude when aircraft altitude is minimum 300 feet below missed approach altitude and the FMC has transitioned to "on approach" mode. The FMC transitions to "on approach" mode for ANY of the following conditions: - the descent phase is active and flaps are out of up, or - the aircraft has sequenced to the first waypoint of the active approach, or - the aircraft is on a direct-to or intercept course-to the active waypoint and the distance to go is less than 12 NM, or - the missed approach point is the active waypoint and the distance to go is less than 25 NM. When the FMC is "on approach" the following features will be available: - the IAS/MACH window can be opened and the command speed can be set while Vnav remains in Vnav Path descent. - the MCP altitude can be set above the airplane altitude for the missed approach. When the MCP altitude setting is at least 300 feet above the current airplane altitude, Vnav continues to command the set speed. (this feature does not work on the PMDG B777). The PMDG B77 aircraft goes from Vnav path to Vnav ALT. Not correct and would be great to see a fix for this. Regards, Christian

The certified takeoff flap setting on the B777 models I operate is 5-20(200,200ER,LR,F,300, 300ER,ULR). It depends on the weight, temperature, wind, runway, runway intersection, runway condition, air pressure and CG(Full CG or ALT CG). We use an EFB(class 1-2-3) to calculate the takeoff performance based on the above mentioned conditions. Normal landing flap is 30. Some airlines use 25 for landing flap. Flap 20 is normally used during a single engine approach & landing. Flap 20 is also the normal landing flap setting during an overweight landing (landing above max landing weight) and in a low fuel scenario (The low fuel EICAS message will display when either main tank is below 2.1 tonns). This requires a flap 20 landing. Christian

Yes of course anybody can come along. Off to Osaka tonight if anybody wanna join. Emirates.comRegards,Christian Fretland

My apology for not using my full name.Regards,Christian Fretland

If you need any "help" with the 777 let me know. I have been a big FS fan for years now and love the 737. I am currently a Captain on the 777 and if you need any information/assistance let me know.Chris(Dubai)

No 2d throttle quadrant?? I thought that was a joke at first. I only fly in 2d, not a 3d fan at all. Hope to see a 2d throttle quadrant in the future. Great plane by the way. Christian

Thank you for the help. I will give that a try. Christian

The installer can not find the MSFS installation. How do i manually navigate the installer to the installation directory?? My FSX is in the D drive. Regards,Christian

Great thread and im enjoying reading the posts. I am a huge fan of the MD11, it really is a great simulation. Never flown the 744 or the MD11 but I have thousands of hours on the 737NG and currently on the 777. Been an FS fan for over 15 years now and a huge fan of system simulations. The MD11 really is a great simulation and probably one of the most realistic simulations out there. I think the MD11 and the "Flythemaddog" MD82 are the two most realistic simulations ever made for FS. I am really looking forward to the new 737 and hoping the 2d panel will blow me away as i'm not a fan of 3d panels. I like that i can drag/expand and resize the MD11 panel to my satisfaction. I like a large 2d panel with big, crisp and smooth displays. Currently grounded with a torn achilles tendon, so I have a few months to tweak and perfect my hobby here in the "sand box". Keep up the good work PMDG (Just wish the J41 came with a 2d panel)!Chris

I believe its a DX10 issue. The external model is correct when I enable DX10 in FSX. The external is messed up when DX10 is de-selected. I have other liveries and it is the same with them. The panels work just fine. I am using windows 7....dunno if thats the problem. Christian Fretland