royski

Hi... no HGS or hotkey in the 2D panel. No 2D throttle quadrant either.

Pressing and HOLDING the period key (1-2 secs) twice is more simple.

Hello, please check my post. This might help you: http://forum.avsim.net/topic/343627-how-to-perform-an-autoland/

In the case of the PMDG 747, can engage the 2nd AP even after localizer capture. In the case the of NGX that is not possible - the 2nd AP engages after the G/S capture. I've tried this many times.Another important item, make sure the NGX is setup as follows:

You're welcome! Glad to help... Correct! Have fun!

Hi Brian! Please check this link - here: http://forum.avsim.net/topic/343627-how-to-perform-an-autoland/ Have fun!

Hi! Please check my post, here - http://forum.avsim.net/topic/343627-how-to-perform-an-autoland/ Have fun!

Hello, please check my other post, here - http://forum.avsim.net/topic/343627-how-to-perform-an-autoland/ Have fun!

Hi all! Based on the past few days of flight testing and learning about the NGX, I successfully made an autoland and put the necessary steps in mind. I would like to share such to my fellow NGX pilots to clarify and clear their doubts. I'm not a real world pilot nor an "expert" but this information may help you. Here are two screenshots of my flight from SPIM-MPTO on final. The FMA and ND displays have been in "zoom mode" for clarity purposes. Autolanding sequence (important points only): 1. Place plane on landing configuration; gear down, spoilers, armed, autobrakes armed, flaps deployed in relation to final speed in FMC. Personally I use Vref + 5 as my final speed. 2. Verify that both FDs are active. 3. Make sure that BOTH NAV1 and NAV2 radios are tuned to the same ILS frequency. As per the manual, this is required for a dual AP autoland. 4. There is NO NEED to set the final rwy course as this will happen automatically once the LAND 3 mode is activated. 5. Upon glideslope intercept, engage the second AP, and the APP light will extinguish. "LAND 3" mode should appear in the FMA. Flare and rollout modes will be armed. Note: You will NOT be able to engage the second AP before the g/s intercept. 6. Make sure that the heading selector is set to runway heading and altitude is set to the missed approach altitude, in case of a go-around. 7. At this time, the final course will be shown on BOTH captain and F/O course displays. This is now "locked" and you cannot adjust the course value manually. 8. On final descent, your will hear the altitude callouts (as set in options menu in FMC). 9. Just before touchdown, flare mode becomes active and rollout mode will follow. At this time, engage reverse thrust and verify that spoilers have been deployed. 10. Autobrakes will also kick in and at 80 kts place the thurst levers in idle. At 40-60 kts, press and HOLD the period key (for 1-2 secs) TWICE disengage the autobrakes. 11. Exit the active runway and perform the after landing checklist.

Hi Jim, Still ASE is the best weather program for FSX, never had a problem with any PMDG product, even the NGX.

Are they really pilots? What were they trying to do? A flapless approach? The plane would warn them "too low flaps."

If you want the AP (single channel use) to guide you down to the localizer then plan to disengage and perform a manual landing, the following are ONLY required: - both FDs are on- ILS frequency tuned to NAV1 VHF radio- arm APP as glideslope become alive In this case, entering the course on either one or both OBS and entering the runway altitude are not necessary. I have done my first test flight using this.

According to the FCOM Manual V2 page 199:

Thanks for the info.

On that last flight I had "LAND 3" display on the FMA. It felt great at that time (due to very poor visibility and low overcast ceiling).

Today on a flight from SCEL-SPIM, I was able to perform an autoland (due to limited visibility) with both AP engaged. Just check and verify that both VHF NAV1 and NAV2 radios are tuned to the same ILS frequency. Check that both FDs are on. I engaged the right AP switch after the glideslope was captured. I'm not sure if this was a factor though, but I will try to engage it prior to glideslope capture on my next flight.

Thanks for your advice! Had a flight from SCEL-SPIM today. Armed the autobrakes to setting "2" and did an autoland with 2 autopilots engaged. Upon rollout autobrakes kicked in, engaged reverse thrust then as IAS drops to 60 pressed and HOLD the period key (for about 2 secs) TWICE. Entered the taxiway at about 25-30 kts before holding short for taxi directions. I just loved the sound of the spoilers and reverse thrust upon touchdown!

Had a flight from SCEL-SPIM, tuned the ILS frequency on NAV1 and NAV2 VHF radios. Hand "LAND 3" displayed on the FMA and was able to arm the two APs.

Based on my memory after reading the manual, there is NO autotuning feature for FMS (unlike PMDG 747 and LDS 767). Even if such is actually present in the real aircraft (as you say so)... Therefore in the NGX, you have to actually tune the frequencies manually. Such limitations in these aircraft I can accept as in every plane, there are pros and cons.

Why use the HUD when doing an autoland? Assuming you are landing in low visibility/IMC weather conditions. In my opinion, HUD landing is only done when visibility is good and you are performing a MANUAL landing.

FCOMV2 page 228 (40.20.16) (Operating Manual Vol 2) This has also been a reason on why I could not perform a dual AP autoland... What I usually do back in the 747 is to confirm that ILS frequency is tuned on NAV1 and the nearest VOR tuned on NAV2. Now I don't really see the point why you have to tune the ILS frequency on BOTH NAV1 and NAV2...

Unbelievable... What I would usually do back in the 747-8i is to tune the VHF NAV 2 to the nearest VOR station and NOT with the same ILS frequency... That's the reason I'm not able to make a dual AP autoland...

I guess I'm not alone to discover about this autobrake problem... I was just surprised that they would not disengage even after rotating the switch to OFF position.

Looks like another NGX glitch... I will try to do so on the next flight - max reverse thrust needed then to slow the plane down...

The brake command does not work, even if it was mapped in FSX as the period "." key. Another problem I've noticed after landing, during rollout, the autobrakes kick in but I'm not able to disarm them by pressing the period key or rotating the selector back to OFF. The word "brakes" does not disappear in the lower left part of the screen.To remedy the problem I'm forced to set the parking brake then press the period key to disengage.Is there a way to fix this problem?