I'm trying to practice my landings with the new bird, so all I do is fill out the performance data in the CDU, leaving out any route, takeoff, then turn around and try to fly the approach. Ideally I'd have a saved flight right for the approach but I get the CTD at 4% load error so that will have to wait. Anyway, I'm having trouble shooting the approach with the A/P. I don't want to perform a CATIII autoland, I just want the plane to set itself up on the approach (tracking the glideslope and localiser) then disengage when I want it to so I can hand-fly the final. Problem is it won't capture the glideslope. After capturing the localiser I press the Approach button on the MCP, but rather than going to G/S mode on the PFD and flying the glideslope, it goes on straight and level and annunciates, from memory, 'CWS' and goes into V/S mode. Both F/Ds are on and the Captain's NAV radio is tuned and course set. What am I doing wrong? Cheers, Mike Gibson

I'm trying to practice my landings with the new bird, so all I do is fill out the performance data in the CDU, leaving out any route, takeoff, then turn around and try to fly the approach. Ideally I'd have a saved flight right for the approach but I get the CTD at 4% load error so that will have to wait. Anyway, I'm having trouble shooting the approach with the A/P. I don't want to perform a CATIII autoland, I just want the plane to set itself up on the approach (tracking the glideslope and localiser) then disengage when I want it to so I can hand-fly the final. Problem is it won't capture the glideslope. After capturing the localiser I press the Approach button on the MCP, but rather than going to G/S mode on the PFD and flying the glideslope, it goes on straight and level and annunciates, from memory, 'CWS' and goes into V/S mode. Both F/Ds are on and the Captain's NAV radio is tuned and course set. What am I doing wrong? Cheers, Mike Gibson

do you arm app as soon as your gs is alive.

Yeah I hit the approach button when the diamond turns colour and starts moving down. Cheers, Mike Gibson

The yellow CWS indicator that your are getting suggest that the AP wasn't engaged properly. Make sure that the aircraft is properly trimmed out and that you don't make any control inputs while engaging the AP.

You have to enter the runway orientation on both course indicators on the MCP, and the ILS frequency on both radios (Two may not be necessary if you don't want to do an autoland - if you do then when the glideslope is grabbed you have to turn on both autopilots). Maybe you have to turn the EFIS dial to app (not sure). You must intercept the glideslope from below flying at a constant altitude ( 3000ft is good) and speed. When the needle starts to move is the time to press the "app" button and the plane should then be grabbed by the glideslope. I am not sure if this is necessary, but make sure you have entered the runway altitude on the pedestal. Henri

I don't know about needing to enter the runway course into both MCP course indicators. Both autopilots need to be active for autoland... I saw in another thread what is needed for autoland... Andrew

You have to enter the runway orientation on both course indicators on the MCP, and the ILS frequency on both radios (Two may not be necessary if you don't want to do an autoland - if you do then when the glideslope is grabbed you have to turn on both autopilots). Maybe you have to turn the EFIS dial to app (not sure). You must intercept the glideslope from below flying at a constant altitude ( 3000ft is good) and speed. When the needle starts to move is the time to press the "app" button and the plane should then be grabbed by the glideslope. I am not sure if this is necessary, but make sure you have entered the runway altitude on the pedestal. Henri

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.

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.

Yeah I knew that was the case so I didn't understand why it wasn't working. Anyway, problem solved. Another forum member was kind enough to PM me saying that he'd had a similar problem. It turns out the 'G/S' setting on the Approach CDU page defaults to 'Off'. Switching it to 'On' has it working as advertised, the plane captures the glideslope. I don't know why the setting defaults to 'Off', it must be a setting for the livery. Thanks for your help, guys. Cheers, Mike Gibson

It turns out the 'G/S' setting on the Approach CDU page defaults to 'Off'. Switching it to 'On' has it working as advertised, the plane captures the glideslope. I don't know why the setting defaults to 'Off', it must be a setting for the livery.

Mike, What kind of approach was it? Certain approaches cause the G/S to default to off.

I haven't programmed any sort of route in, no STAR or anything like that. As I said in my OP I just takeoff, then turn the plane around and intercept the localiser and glideslope. Cheers, Mike Gibson

Ok I have the same problem, first app is fine and all but after another run the AP always stays on ALT HOLD mode and doesn't capture the GS but VOR/LOC is captured so It's not that I'm outof trim or anything. I'm using the Pro flight yoke from saitek..W7 64 bit Dennis Meijer

Is your GS turned to ON in the FMC?

Ok the solution was indeed simple, the GS was turned off in the FMC in the ref page... Thx Drumcode and p_7878(private message) Dennis Meijer