AAABBB

I would like to report a suspected high-angle-of-attack protection issue with the iniBuilds A350 in MSFS 2024. During a high-altitude deceleration test, the aircraft continues to maintain approximately 25° nose-up pitch after I release the sidestick. A.FLOOR activates, but there is no apparent protective nose-down response as the airspeed continues to decrease into the red low-speed band on the PFD. Steps to reproduce Fly at a high altitude, for example FL360. Apply aft sidestick to raise the pitch attitude to approximately 25° nose-up. Release the sidestick to neutral and make no further pitch inputs. Observe the aircraft as its airspeed decreases. A.FLOOR activates, but the aircraft continues to maintain approximately 25° nose-up pitch. Airspeed decreases further into the red low-speed band, with no apparent pitch reduction to limit angle of attack. Expected behaviour With Normal Law and high-AoA protection available, the flight controls should intervene to limit angle of attack. With the sidestick released, I would expect the aircraft to reduce pitch as necessary to control AoA, rather than continue holding the previous high pitch attitude throughout the deceleration. Comparison with the default iniBuilds A330 When I perform a similar test in the default iniBuilds A330 in MSFS 2024, the aircraft lowers its nose and the protection appears to work. I do not observe the same sustained high-pitch behaviour. Test information Simulator: MSFS 2024. Example starting altitude: FL360. Pitch attitude before releasing the sidestick: approximately 25° nose-up. Reference and request Airbus describes high-AoA protection in Normal Law as commanding a nose-down pitch rate when the alpha-protection threshold is exceeded: Airbus Safety First: Control your speed... in cruise. Could you investigate whether the A350's high-AoA protection is engaging correctly and whether its pitch-control response is working as intended in this scenario?