737 NGX Autoland?

[virge 1]

Virge, just a reminder that posts should be signed with your full name.

 

What I was trying to establish for the OP was that approach was definitely armed, as it is one of the requirements to allow the second AP to be engaged.

Thanks for the heads up.

[Spin737 102]

I am a rank amateur, and in no way am I trying to contradict you, but isn't the switching on of both FD switches necessary to allow both CMD switches to be armed?

I don't think you're contradicting Ryan if he never said the opposite.

[Todd Moore 1]

Ok, first...I use FS2Crew, and the FO arms both of the FD switches.  I do not know what the HGS controller is.  I did enter the rwy heading into both of the course knobs when I attempted to do this, as well as putting the ILS freq into both of the radios.

 

I will attempt to help you.

First of all just before takeoff one thing you must do is turn on BOTH FD switches, and turn on the captains FD switch first, which will make the captains switch the master.

In the EFIS control panel, click the center knob of the BARO knob in order to return to altitudes, instead of flight levels above 6000 feet. This is assuming you were previously flying above 6000 feet. 

There are some steps that I am not including since I am assuming you know them, and have used them.

Enter ILS frequency for the specific runway you are landing at, which you can find in the FMC APPROACH REF page.

Press TFR switch to make both radios active on the ILS frequency.

If you want to use the head up display, press the RWY button on the left side of HGS controller until it shows the elevation of the runway.

Press the RWY button again and set the actual runway length. In the MCP enter the localizer front course into BOTH captain, and First Officers course window.

The ILS frequency and course should be visible on the left side of the PFD.

Press the CMB B to arm the autoland mode. Both should be lit up.

Like I already stated, I left out steps since I assume you know what you are doing, and what may be left to do.

Good flying.

P.S. I think turning on both FD switches I believe is critical in order for both CMD switches to stay activated.

I am a rank amateur, and in no way am I trying to contradict you, but isn't the switching on of both FD switches necessary to allow both CMD switches to be armed?

[markadeane 272]

Todd I'm wondering if Ryan might have been right about an ILS not existing in the FSX navdata at your chosen destination.

 

I've had this a few times where I've tuned the ILS, using the information that the NGX navdata makes reference to, but when the NGX 'looks' for the ILS in FSX and can't find it, the system reverts to Integrated Approach Navigation.

 

The giveaway for this is that instead of getting LOC/GS on the top of the PFD, you'll get FAC/GP. In FAC/GP autloand is not available and you have to land the aircraft manually.

 

Check this, and if that IS the case, then you will need to try another ILS approach for autoland.

 

If you are definitely getting LOC/GS then we might need to dig a bit further into your issue. Let us know an example flight or flights where it occurs including the route, the STAR and the approach in each case.

 

Also let us know what AIRAC cycle (nav data effective date) you have installed and where it came from (i.e. came with the NGX or updated by a third-party).

 

Step us through each single action you take and when down the approach. Don't leave anything out!

 

With that info we can definitely work out what is happening for you.

 

Cheers

[Todd Moore 1]

Sir, I in no way would even try to autoland on a runway that does NOT have an ILS.  I have told you that I am fully engaged on the ILS, both radios are tuned to the ILS freq, and the course knobs are both set to the runway heading.  I press the approach button, I line up and engage the ILS, then I try to push the second command button.  But the first one turns off...even after I do all of this. I am only one cycle behind on the AIRAC, but ILS freqs do not change that often if ever.  

[markadeane 272]

Todd, we're trying to help you here, not insult your intelligence. I've read what you've said here very carefully, and my questions are based on that report, so please try to work with me.

The NGX has it's own navdata, quite distinct from the native FSX navdata. The FSX navdata is very old, and often there is a discrepancy between the two datasets. If the NGX navdata says that there is an ILS at your destination, then outwardly it will appear as though things should work fine, but if the corresponding FSX navdata is different (e.g. there was no ILS or a different frequency at the time the FSX dataset was taken) then you can run into issues like what you've reported here.

 

So, again, if you can definitely 100% confirm that you see LOC and GS on the PFD, then we'll need all the info I asked for above to delve further. If what you actually see on the PFD is FAC/GP then we've identified your issue.

 

Make sense?

[Todd Moore 1]

Ok, I must have missed a step the last time I tried it...but now I got it to work.  Thanks so much for all of your help.

[pete_auau 1,157]

A picture of  what your  seeing  would be  great in dealing  with your problem

[markadeane 272]

No problem Todd, glad you got it working! It would be valuable to know what the issue was in order to help people with this issue in the future. If you were able to identify what it was that would be good to know!

 

The NGX is a delightfully complex beast and I learn stuff about it on every flight, even after hundreds and hundreds of hours in the saddle!

 

 

 

 

Ok, I must have missed a step the last time I tried it...but now I got it to work.  Thanks so much for all of your help.

[Todd Moore 1]

I don't know what I did.  I just followed the instructions, and I finally got it to work.

[Tabs 2,790]

I am a rank amateur, and in no way am I trying to contradict you, but isn't the switching on of both FD switches necessary to allow both CMD switches to be armed?

 

Yes, I was presupposing that he was flying with both FDs on given that major parts of the entire AFDS system won't work unless they are.

[Fabo 213]

A video, if someone wants to see how to do it.

 

[Adam T Lutley 12]

Just a couple of general thoughts.  As has been stated, both nav radios must be tuned in to the correct ILS frequency and the LOC and GS signals need to be captured to engage both AP's. The NGX has a much more recent data set than the default ATC so discrepancies exist between the two. Autolands are almost never conducted in real world commercial flying. Airlines impose operational restrictions considerably above the criteria that would necessitate an autoland. With the aircraft in its final landing configuration and established on the approach, the AP is usually always disengaged and hand flown to the runway. Large throttle/flight control inputs should not be necessary barring big crosswinds or the like, if you're correctly configured, until just prior to touchdown. I do realize its only a sim so there's no harm in doing an autoland every time if one wishes. Regards

[Spin737 102]

 

 

LOC and GS signals need to be captured to engage both AP's.

 

This is a commonly held belief, but the APP mode only need be armed before selecting the 2nd A/P.

[Adam T Lutley 12]

This is a commonly held belief, but the APP mode only need be armed before selecting the 2nd A/P.

Thanks for the clarification. Regards