As mentioned above you’ve not gone into a floor situation and stalled the plane? guessing not, as it will keep accelerating and you’ll need to disconnect autothrottle to get control back again. This is intended.
Nope. Absolutely no alpha floor!!
Try it for yourself – ie Manual TOGA takeoff. A/THR light on. Nothing in MCDU & no autopilot engaged.
~ At around 400ft-500ft, level-off (using sidestick).
~ Set thrust levers to CLB detent.
~ Pull the speed knob (that you had earlier pre-set) to 170kt.
Question: Does your aircraft respond and settle at 170kt?
Or does it keep accelerating to overspeed whilst you maintain 500ft?
Just did the same as you described, and you are right it does behave like that.
But I cant tell what is the correct way it should behave? I believe only a real pilot can clarify this.
EDIT: Looking at the FBW manual SRS mode should become inactive when selecting a speed, that is not the case in the V2 so you might be right.
It seems very much like this is another bug in the A320neo v2’s autothrust / autoflight logic.
So surely this thread should be reinstated in the “Bug” section ?
Note that what you described (and I confirmed) is not related to the OP issue, so a new bug report should be submitted for this, otherwise it will be confusing.
I think this is yet another example of the IniBuild’s A320ne v2’a autothrust coding logic simply not understanding what mode it should be in – in relation to what the aircraft is doing and what the pilot wants the aircraft to do.
In that sense, they are all symptoms of the same bug ![]()
I’m having the same problem with A320 v2, when during the approach procedure the autopilot turns off and accelerates to TOGA LK. To avoid losing the approach, I turn off the Autothrottle and reduce the throttles, this is the only way I can control the aircraft.
This is discussed at length in the post.
https://forums.flightsimulator.com/t/airbus-a320neo-v2/642546/686?u=psionw
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
