ISSUE DESCRIPTION Description of the issue: I’m new to flying the default Inibuilds Airbus series, but in SU4 I began flying the A330. Since SU5 beta began, every flight in the A330 with Live Traffic, from the moment of takeoff for the entire flight, the Vertical Speed Indicator is Red / Green indi…

Should be fixed: [image] Release Notes - Microsoft Flight Simulator 2024 Sim Update 6 [1.8.14.0] Airbus A330-300 Fixed - A330 TCAS warning permanently active with Live Traffic (never clears).

Yes, I have the same issue. I was flying the FSL321neo, taking off from runway 04 at LZIB. Shortly after takeoff, the TCAS issued a warning, and then the aircraft surged into an uncontrolled climb. Sometimes, I also encounter this problem upon landing. I wasn’t using any AI traffic, just had the on…

Sim Update 5 v1.7.6.0 Aircraft: A330-300 RR Flight: PANC to RJTT TCAS warning for an aircraft that is 60 nm away, and 2400 feet above? [20260215-a330-tcas]

had the same issue on SU4 too. so i don´t think it´s a beta issue

Moved to Bug Reporting Hub since not a SU5 regression, issue also exists in the Live version.

Having the same issue on VATSIM. Live traffic is otherwise off. [image]

I fly the A330 a lot (PC MS Store, streaming) and every flight there are non-sensical TCAS warnings. Is Inibuilds not capable of fixing this? [20260531-a330-tcas]

still there in SU6 BETA… no threat, but TCAS still active. [Microsoft Flight Simulator 2024_2026.07.20-21.36] [Microsoft Flight Simulator 2024_2026.07.20-21.38]

Just had this. Issue is still in SU6. Resolved by switching TCAS to STBY then back to TA/RA

Still an issue with latest SU 6.1 and not fixed. Also triggers the callouts. Not the first time you say it’s fixed but it wasn’t. [ini TCAS RA]

Also confirmed that the issue is still present with callouts that continue to happens : [image] Trying to reset it by going to standby then back to RA/TA do not fix the issue

A330 with Live Traffic, constant TCAS condition never clears

Bug Reporting Hub Aircraft & Systems

DementedCorn327 August 15, 2026, 5:38am 13

Should be fixed: