I'm a bit new but had a recurrent problem that drove me batty last night:I was trying to land an Airbus 321 in the Rome-Naples mission, with "realism" turned pretty far up (beyond my neophyte abilities to land easily).After I finally had reasonable approach I pushed the throttle up about 10% delay my sinking and to carry me a bit further toward the runway. Next thing I knew I'm launching over the runway and up to 200 knots?I restarted aproached again and had it occur a few times...eventually I realized the "Auto-Throttle" was somehow engaging? and nailing the throttle to 70% I know I didn't hit it intentionally??I use a MS Sidewinder Joystick? any idea how or why the autothrottle would engage "automatically"???TIA

If you got too slow the alpha floor would be enabled, it's like if it thinks your gonna stall the plane, the autothrottles are engaged to toga power (max power???) you need to turn off auto throttles on the console before landing...

One more thing!If you're using the GoFlight autopilot module, make sure that the A/T is compeltely disengaged and turned off before touchdown or it will stay engaged and turn your day into a bad day upon landing.Sincerely,Dennis D. Mullert

>If you got too slow the alpha floor would be enabled, it's>like if it thinks your gonna stall the plane, the>autothrottles are engaged to toga power (max power???) you>need to turn off auto throttles on the console before>landing...OK thanks, so it's not a "bug" that helps....I was very close to a "stall" on some of these landings. But thought I could hammer the throttle if I heard / saw / felt the stall indicator.Does the "alpha floor" turn on the "auto-throttle"? Because I'm about 90% certain the auto-throttles were in fact off before the approach?

>One more thing!>>If you're using the GoFlight autopilot module, make sure that>the A/T is compeltely disengaged and turned off before>touchdown or it will stay engaged and turn your day into a bad>day upon landing.>>Sincerely,>>Dennis D. MullertI assume GoFlight is an add-on? I don't think I'm using it?

That sounds like the Fly-by-wire A321 computer kicking in, to prevent a stall.I had it happen once when I was playing around with the A321. I was near the ground and going slow, and all of the sudden the throttle got hammered and the a/c pitched up.RhettAMD 3700+ (@2530 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2 GB Corsair XMS 3-3-3-8, WD 250 gig 7200 rpm SATA2, CoolerMaster Praetorian

The flight computer(s) of the A321 can be turned off on the overhead panel. On the left side, there are three buttons labeled ELAC1, SEC1, and FAC1. On the right side, there are four bottons labeled ELAC2, SEC2, SEC3, and FAC2.I have not figured out what all these do, but it seems that a lot of functions of the WFB-systems are only active if SEC1 is on (or maybe all SECs need to be on).I sometimes *cannot* disengage the autothrottle if it kicks in automatically, unless I deactivate SEC1.If you turn SEC1 off, you also lose the logic that interprets stick inputs as "attitude commands" rather than rudder deflections. This makes the A321 extremely agile.... Also, the bank limiter is deactivated and the plane can be rolled 360 degrees.happy flying.

>...Next thing I knew I'm launching over the>runway and up to 200 knots?May I assume that you could have a black-out from the high acceleration? ;-)Sorry, but it sound's really funny (and also sorry, no helpful comment from me on your reported Problem this time).Regards Heinz-Werner