hey guys, I looked this up in the search, but the answers given did not make sense. The issue: When on final (usually very short) I get a trim runaway condition. It happened today on short final into DEN in the MD-11. I am flying a visual for rwy 07 when at about 200 ft, I get a "stabilizer motion" followed by a consistent and sudden nose down pitch. I was able to easily recover given my already nose high trim/pitch. This has only happened twice before. Once in the A320, and once in the 757. Answers given in previous posts, and my rebuttals to said answers:A stall: Just not the case. Especially when the airspeed is being controlled by the autothrottle. Somebody also said something along the lines of the stick shaker pushing the nose over. That's just illogical. A stick shaker is just that. It shakes the stick (or in our case, the control column) A stick pusher, on the other hand, pushes the control column forward when a stall is imminent. The key word being imminent. Not already occurring. Remember, it's an MD-11, not a Cessna 172.Wake turbulence:If it is the AS wake turbulence effect, then they did a poor job modeling it. Wake turbulence is generated by the vortices coming off an airborne aircrafts wingtips. Those vortices sink and level off at around 900ft below the generating aircraft. With that being said, If I am at 200ft on final and the previous aircraft landed lets say 3 miles in front of me, then I would not have a wake turbulence issue. Also, if it is AS causing this, then I should be experiencing it almost all of the time.I am a rw pilot, and an avid fs pilot. This issue just confuses the crap out of me...Any thoughts??Matt

Every time that I have read about this problem it turned out to be AS wake turbulance! Rather that analyzing it to death, just turn it off. If that fixes your problem, then you can try to determine what is wrong with AS and how to correct it. R-

Sounds almost like you forgot to turn off the autopilot. Wake turbulence won't move your trim tabs, so I'm definitely with you on that one. Since this doesn't happen all the time, I doubt that it's any of your key assignments, but it can't hurt to check. Just go through real quick and make sure that nothing except the keys, or buttons on your joystick that you want are assigned to those slots, and that they aren't assigned to anything else as well.If it all works out, I'd try assigning them to either different keys or different buttons. Maybe something is messed up in the hardware where the contact sticks or something.Hopefully this helps!

What are you using for a flight controller?The older model Saitek yokes do have an issue with random button presses.

I agree with Ron, this comes up very often here and it's usually the wake effect in AS. Don't expect it to be as accurate as in real life.It could also be a flight controller issue, other than that I can't think of anything else... :(

I would lean on the possibility of a sticky button on my joystick. I am using a Saitek ST290 pro joystick with button 3 and 4 for down and up trim. My autopilot was definitely not on as I was flying a visual approach, and I have since deactivated the WT effect in AS. I also don't believe that I am over-analyzing the problem rather pointing out some obvious errors on other posters behalf.I will let you know how it goes. Thanks for the suggestions