I've been flying the PMDG 737's for some time, and despite a few gripes, I really like them. One thing I've wondered about, though, is whether or not the autothrottle is designed to retard to idle at 50ft AGL or so even if not in full autoland. I will generally hand-fly the final approach but trying to handle the throttle and fly at the same time can be difficult without a FO...Anyway, in my experience, when hand-flying the approach the autothrottle doesn't seem to idle and I am forced to deactivate it myself; certainly a bit of a distraction when trying to control the flare.-Eric SchultzEDIT: I had a hypothesis, and it turns out it was correct. The autopilot mode must be showing VOR/LOC and G/S on the PFD in order for the autothrottle to know it's in an approach setting and should retard when you reach the runway. I'm not seeing a "delete" option for my post edit, so moderators can either delete it or leave it for future reference. Cheers!

EDIT: I had a hypothesis, and it turns out it was correct. The autopilot mode must be showing VOR/LOC and G/S on the PFD in order for the autothrottle to know it's in an approach setting and should retard when you reach the runway. I'm not seeing a "delete" option for my post edit, so moderators can either delete it or leave it for future reference. Cheers!

Hi Eric,AFAIK, this is not enough : for the autothrottle to automatically retard at the flare, you must be in "autoland" mode ie with VOR/LOC and G/S selected as you mentioned, but also with BOTH autopilots selected ON.Someone pls correct me if I am wrong on this.Bruno

If autoland (FLARE) is not armed, and the autothrottle is engaged the thrust levers will not retard at 50' to idle. Instead autothrottle will attempt to maintain target bug speed. The proper technique when flying this airplane would be to disengage the autothrottle and autopilot prior to landing if doing a manual landing. The only time the autothrottle will retard to idle at 50' is when autoland (FLARE) is armed.J. Floyd

If autoland (FLARE) is not armed, and the autothrottle is engaged the thrust levers will not retard at 50' to idle. Instead autothrottle will attempt to maintain target bug speed. The proper technique when flying this airplane would be to disengage the autothrottle and autopilot prior to landing if doing a manual landing. The only time the autothrottle will retard to idle at 50' is when autoland (FLARE) is armed.J. Floyd

This appears to be incorrect. I just did a test, no weather, with the 737-600 and it does indeed seem to retard under certain circumstances. I'm not sure what exactly these conditions are; perhaps being in a total landing configuration with flaps and gear extended, autobrakes and spoilers armed, whatever. I do know that if you just slew into the air and try a landing, it won't do it...but whatever the conditions are, I just did a simple flightplan in the FMC (origin KSEA, destination KSEA), with ILS 34R as the approach. Set both the NAV frequencies to the ILS, set the course identical to the one laid out in approach page (343 degrees), etc. Followed LNAV in to the final approach course but armed APP mode before the localizer came alive. Under manual control, MCP SPEED, LOC, and G/S modes feeding to the flight director, at about 50 feet the green MCP SPEED switched to a green RETARD, and it was a beautiful landing.I tried recording it as a flight video but in the recording the instrumentation is all wrong. Perhaps the developers could shed some light on what conditions must be met for the autothrottle retard mode to arm.Eric Schultz

I think FLARE is 50' and RETARD is 27'. Or should be.

This appears to be incorrect. I just did a test, no weather, with the 737-600 and it does indeed seem to retard under certain circumstances. I'm not sure what exactly these conditions are; perhaps being in a total landing configuration with flaps and gear extended, autobrakes and spoilers armed, whatever. I do know that if you just slew into the air and try a landing, it won't do it...but whatever the conditions are, I just did a simple flightplan in the FMC (origin KSEA, destination KSEA), with ILS 34R as the approach. Set both the NAV frequencies to the ILS, set the course identical to the one laid out in approach page (343 degrees), etc. Followed LNAV in to the final approach course but armed APP mode before the localizer came alive. Under manual control, MCP SPEED, LOC, and G/S modes feeding to the flight director, at about 50 feet the green MCP SPEED switched to a green RETARD, and it was a beautiful landing.I tried recording it as a flight video but in the recording the instrumentation is all wrong. Perhaps the developers could shed some light on what conditions must be met for the autothrottle retard mode to arm.Eric Schultz

One thing to keep in mind here when discussing implimented simulator systems is the user's mode of operation in relation to actual flight operations and or limitations. While its nice to be able to know what something does for every system (engage A @ = ), one has to keep in mind the amount of programing that would be required for each and every 'possible' system enaged 'non-standardly'. While some of these abnormalities are indeed helpful and justified most are not and fall into the realm of non usefulness. But to the question at hand. There is no autothrottle "retard" availible without a 2 channel APP landing simply because the FLARE maneuver is not availible for single-channel APP landings. FLARE is initiated 50' RA with A/T MODE to RETARD about 27' RA and continues until TD and will disengage appox 2 seconds after T/D.