JohnnyTam

I've discovered two issues in the current version of the A350 model: 1. Pitch trim indication during touch and go training During a touch and go, when initiating a continuous take‑off, the pitch trim indication should appear on the PFD as soon as the thrust levers are moved out of idle. However, the iniBuilds A350 does not behave as expected. As a result, the aircraft does not automatically pitch trim to the take‑off position, and it begins to auto‑rotate before reaching Vref speed without any sidestick input. According to the real‑world A350 FCOM, the pitch trim indication on the lower right PFD should appear during a continuous take‑off under any of the following conditions: move the thrust lever out of idle detent disarm the spoilers retract the flap for one detent flight crew press the PITCH TRIM button The aircraft should then auto‑trim back to the take‑off position, but it should not rotate without sidestick input. 2.Brake temperture After a normal full‑stop landing with the MED autobrake(no BTV, disconnect the autobrake and use very light mannual brake when slow down to 50kt ), the brake temperature rises from the normal 30‑40 °C to over 200 °C, which seems unrealistic. Even stranger, with the brake fan turned on, the temperature still continues to increase. According to the FCOM and FCTM, the brake temperature should drop immediately when the brake fan is activated. Could anyone leave me some solutions or help to pass the feedback to the develop team?

Recently I’ve encountered an issue on the A350. It occurs at the beginning of the flare phase. Without any input on the thrust levers, the A/THR automatically switches from normal active mode to armed mode (FMA A/THR changes from white to blue). At the same time, the FMA throttle mode changes from SPEED to MAN THR, and the thrust increases from the normal approach N1 (51%) to 86%. It feels as if the system is forcing a go-around. I’ve experienced this twice: the first time during a very normal and stable flare, right after passing 50 ft. The second time happened when the aircraft was descending with a relatively high sink rate. I checked the A350 FCOM but couldn’t find any explanation for this behavior. Has anyone else experienced the same issue? Is this a bug or something else?