it's a week that I try to solve my problem without success:half of the times I try to land in a full autoland configuration,just a little bit before touching, the autopilot disconnects and the trim starts to work (I think it tries to mantain the glideslope...).I read a post few days ago about this problem; the user said that perhaps the problem was the imported flight plan...I tried making directly the flight plan in the FMC but it did'nt solve;...naturally, the setting of all the parameters for the autoland is right when the autopilot disconnection happens....soI hope that someone could help me!thank you very much albertoPS: is not possible to to set the gear in the off position from the virtual cockpit?

If you are using ActiveSky it may be it.In order to simulate the wake turbulences, it acts on the control surfaces.This probably (as it is so in many other panels) disconnects the autopilot.

Hello and welcome, you will need to sign your real name to your posts sir in our forum, thank you."the autopilot disconnects" If the A/P disconnects it would certainly not being applying the bias trim at 400RA so when you say that it disconnects do you mean that the APP light goes out? If so this is correct behaviour and only means that G/S is now active. Look at your FMA, does it have a green G/S? Why don't you let it go all the way down and see if it really auto lands..[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/forum/betaimg.jpgAMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | WD SATA 80 GIG | 512 DDR 400 |

thank you for the answer!no, I don't say the approach light, but really the autopilot! when the disconnection happens Or I try to land manually or I crash!!"Erups" says that it is possible that this happens if I use activesky:I use activesky! But do you know if there is in activesky a workaroundfor avoiding the turboulences that affect surfaces?thank you Alberto VaranoP.S excuse my bad english!

To Mr Randy J. Smith.I'm not an owner of any PMDG product, but i'm interested in them, and i was browsing the forum to gather information about them (onestly at the moment i'm discouraged by the high price of the entire series).In fact you can see that i have no specific information about PMDG autopilot, i spoke about autopilots in general.So at the moment i don't feel the need to use my real name.While browsing the forum i found that i could be of some help in this matter and posted about it.Hope this is no problem for you.To Alberto:in ActiveSky options, there is a voice"Wake Turbulence Simulation", just de-mark it.

>>>>So at the moment i don't feel the need to use my real name<<<

I didn't know it.Sorry.And it was not irony how i called Mr Smith.Best regardsClaudio

do you think that is possible that the wake turboulence on the control surfaces can disconnect the autopilot always just at the same point of flight (a little bit before touching down)?perhaps one or three times this fact happened also in different moments but always in the approach face!I don't remember the autopilot disconnection (using activesky naturally)in other panels; it never happensed for example using the pmdg 600/700!!thank again Alberto

Erm - point of order Anthony - that is your REAL name isn't it?Just wondering!Neil (that is my real name - or at least one of them and given I am an identical twin I often get away with Iain and Kevin)

Alberto:ActiveSky in order to simulate the effects of the wake turbulences, practically places a firm hand on your controls and stirr them.It is equal to haveing your stick fully deflected.Usually this situation is stabilized by you takeing control of the wheel, and the default FS autopilot is not affected.But complex autopilots may be (i've seen this happen in other commercial products) because of other things.It may be seen as a failure in the command surfaces, and thus the autop would disconnect, or whatever.Regarding the actual "where" you experience this:AS mainly simulates the WT approaching the runway, because it's there that it is easier to encounter one.The WT is somewhat like a heavy object:if you fly in it, you'll have problems, but it is subject to the gravity, so after being generated, it slowly fells.This means that on takeoff, the delay between airplanes (and the scheduling of them done by ATC: a cessna is not allowed to t/o 2mins after a 747!) allows for the WT to loose altitude, so that the next airplane won't encounter it.On the contrary, while landing, there is not much space for the WT to descend, and so, even if it disspates over time, you will surely feel it, especially in case you have a heavy ahead.AS is not perfect in simulating WT, and i'd rather leave it disabled until the system will be overdone to more decent behaviour.Claudio

thank you very very much for your clear explanations!!So it's possible that with the WT disabled I solve my problem!?Is'nt it? Alberto

Yes, it's probable.Claudio

AlbertoWhy don't you try to do a autoland without the AS2004 and see if this is the problem? Easy fix eh? Just a thought,

I think that AS2004 is the best weather engine I have tried so I should'nt like don't use it!! But naturally (if I don't solve the problem unchecking the weak turboulence simulation) I'll try without ASBye Alberto

AlbertoI only suggested you try one flight without AS2004 to see if it is the AS2004 influences that makes your A/P disconnect. Not to stop using it!! It's basic trouble shooting logic! Take away one part you think is messing things up and try running it again. Once we've established what is making your A/P disconnect we can start looking for a solution.Just trying to help out,