December 20, 201114 yr I thought it was FS2Crew but just did a flight without it and got the same result...When on final approach, on full manual control, for some reason my throttles go to TOGA at about 100ft....granted, I am just below VREF, but not stalling...What am I doing wrong? and no, I am NOT pressing TOGA. Will Reynolds Flight Sim Addict
December 20, 201114 yr I thought it was FS2Crew but just did a flight without it and got the same result...When on final approach, on full manual control, for some reason my throttles go to TOGA at about 100ft....granted, I am just below VREF, but not stalling...What am I doing wrong? and no, I am NOT pressing TOGA.I'm not sure, but try to press "CTR+R" tvice(or button you use to disconnect the autothrottle). First time you disconnect the autothrottle, and second time you disconect a protection... Zeljko Budovic
December 20, 201114 yr I had that issue only once, out of nowhere. I flew the missed approach and turned back for another try and everything went normal. It was quite weird. Check the button assignments. Maybe you unadvertedly activaded a TO/GA button combination either in the MD-11 controls or in FSX's controls which you happen to be pressing on final, although I think this shouldn't be the case here. And also, check every possible control you have which accepts button combinations. Everything. Joystick or any other hardware, FSX controls, PMDG controls, FS2Crew controls, FSUIPC if you have it... Just to make sure.Also double check if A/T is deactivated.Other than that, I don't have more ideas of what it could be. Matheus Mafra
December 20, 201114 yr Author Thanks guys, is it ctl-r or shift-r to remove the autothrottle?I have shift-r programmed but will check my fsuipc for any conflicts Will Reynolds Flight Sim Addict
December 20, 201114 yr By default it's CTRL + R. Don't forget to click it twice: first to desengage and second to cancel the alarm. Matheus Mafra
December 21, 201114 yr Thanks guys, is it ctl-r or shift-r to remove the autothrottle?I have shift-r programmed but will check my fsuipc for any conflictsIt's SHIFT+R, my mistake. And ensure that you have set landing altitude(destination in FMC), autopilot need to know when you are at 50ft Zeljko Budovic
December 21, 201114 yr And ensure that you have set landing altitude(destination in FMC), autopilot need to know when you are at 50ftOne thing has nothing to do with the other. Either in a visual or an autoland approach, airport elevation above sea level is not important. The altimeter is basically used just for reference there. The altitude callouts you hear are based on radio altimeter readings. This system can not be manipulated by the pilots. It's basically a radar antenna on the belly of the airplane, which emmits radio waves that reflect on the ground back to the antenna. The system then calculates the distance the plane is from the ground using the time the radio waves take to return to the antenna. Nothing to set there. Even if the FMC is not initialized at all or if the barometric altimeter is 1 inHg off the correct setting, the radio altimeter will still work properly. That's where the height (notice I didn't say altitude) callouts come from and that is what the autopilot uses as reference when in autoland mode. The barometric altimeter is inprecise and unsafe to a certain extent because of passiveness for incorrect setting by the pilots. Matheus Mafra
December 21, 201114 yr I've had it go around on me before...in the plane's defense, I was fighting to stay on the localizer, and maybe it decided it didn't like they way I was flying, and engaged TOGA.
December 22, 201114 yr Author Thanks everyone, I have assigned Z and Shift-R in the PMDG Keyboard commands and disabled the same in FSX as Shift-R is Autothrottle Toggle, so if I hit it twice it actually conflicts.Happy Flying! Will Reynolds Flight Sim Addict
Create an account or sign in to comment