Reading in the tutorial, it says that if I want to do an autoland, I have to select both command buttons.  If I press the second command button, the first one goes out.  How can I get both to be activated at the same time?

Approach mode first.

You have to wait for the APP to engage fully.

I have waited for the approach lite to light, I thought that was all I needed.  I will try again once I am fully engaged on the ils.

You need to tune both nav radios to ILS freq, both MCP course to ILS course, and press APP button first.

What I do:

 

Set VREF and place Course and ILS frequencies in their respective locations.

On approach, set VOR/LOC until the LOC activates on the screen. Then hit the APP button until you see that G/S lights up. Then and only then do I hit the 2nd A/P button.

Ok, I just flew a short flight from KMDW to KORD.  I got on the approach for 27L, ILS fully engaged, and it still will not light the second command button.

nevermind, I didn't see the post saying I needed to tune both radios to the approach frequency....ok, back to square one...lol

Ok, I followed all of your instructions.  I tuned both radios to the ils freq, set the course to runway heading on both course settings, and I pressed the app button, then the second command button, and it STILL didn't work!

Todd,

 

What modes are annunciated at the top of your PFD when you attempt to engage the second autopilot? (both green and white modes).

 

Remember the lights on the mode control panel buttons aren't the key reference for what mode(s) the autopilot is in, the answer to your problem may lie in what is showing on the PFD.

did you remember the VOR/LOC?

 

You should only press the second AP button once the PFD says at the top:

 

LOC

 

G/S

Also make sure there's really an ILS there in the FSX world - if you see FMC SPD | FAC | G/P  or something like that in the FMA that's a good clue that you don't actually have an ILS tuned - FAC and G/P are the Integrated Approach Navigation modes - if you see them when you think you have an ILS tuned it probably means there is no ILS there in the FSX scenery or the frequency in the scenery is different from what's present in the real world and in the navdata. (you'd check the FSX map to confirm this)

 

Also guys - you don't need LOC and G/S active to be able to arm the second A/P CMD. You need both radios tuned to the ILS, both courses set and APP mode armed. The modes can be in white and it'll still allow the second A/P to arm.

Ok, I followed all of your instructions.  I tuned both radios to the ils freq, set the course to runway heading on both course settings, and I pressed the app button, then the second command button, and it STILL didn't work!

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.

Also make sure there's really an ILS there in the FSX world - if you see FMC SPD | FAC | G/P  or something like that in the FMA that's a good clue that you don't actually have an ILS tuned - FAC and G/P are the Integrated Approach Navigation modes - if you see them when you think you have an ILS tuned it probably means there is no ILS there in the FSX scenery or the frequency in the scenery is different from what's present in the real world and in the navdata. (you'd check the FSX map to confirm this)

 

Also guys - you don't need LOC and G/S active to be able to arm the second A/P CMD. You need both radios tuned to the ILS, both courses set and APP mode armed. The modes can be in white and it'll still allow the second A/P to arm.

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?

Also make sure there's really an ILS there in the FSX world - if you see FMC SPD | FAC | G/P  or something like that in the FMA that's a good clue that you don't actually have an ILS tuned - FAC and G/P are the Integrated Approach Navigation modes - if you see them when you think you have an ILS tuned it probably means there is no ILS there in the FSX scenery or the frequency in the scenery is different from what's present in the real world and in the navdata. (you'd check the FSX map to confirm this)

 

Also guys - you don't need LOC and G/S active to be able to arm the second A/P CMD. You need both radios tuned to the ILS, both courses set and APP mode armed. The modes can be in white and it'll still allow the second A/P to arm.

 

Thanks Ryan! That's news to me... maybe I'm doing too much to try to do ILS landings.

Todd,

 

What modes are annunciated at the top of your PFD when you attempt to engage the second autopilot? (both green and white modes).

 

Remember the lights on the mode control panel buttons aren't the key reference for what mode(s) the autopilot is in, the answer to your problem may lie in what is showing on the PFD.

What is annunciated at the top of the PFD should be irrelevant at the point just before landing, since when entering a valid airport, using valid nav data should have presented him with valid ILS info even before takeoff. Isn't that the case?

Thanks Ryan! That's news to me... maybe I'm doing too much to try to do ILS landings.

Isn't Todd's issue not have even occurred had he had a valid route in the first place when configuring the CDU before takeoff?  If that is the case, then Todd should have seen that he did not have a valid route even before takeoff.

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.