When using Beyond ATC, after landing, and only with A220; BATC prematurely switches from ground handling to waiting for input for the next flight (as if you have parked at a gate and turned off the engines). This happen when coming to a stop for the first time after landing. For me this means when vacating the runway and coming to stop for further taxi instructions from BATC.

I brought this issue to the BATC support staff first, and found the A220 isn't correctly setting the engine sim vars.

On 8/5/2026 at 7:38 PM, Acperience7 said:

When using Beyond ATC, after landing, and only with A220; BATC prematurely switches from ground handling to waiting for input for the next flight (as if you have parked at a gate and turned off the engines). This happen when coming to a stop for the first time after landing. For me this means when vacating the runway and coming to stop for further taxi instructions from BATC.

I brought this issue to the BATC support staff first, and found the A220 isn't correctly setting the engine sim vars.

Hi,

I can confirm that Synaptic is actively aware of the issue with the simvars not being set correctly, and we’re hopeful that a fix will be included in one of the upcoming updates.

Thanks for your patience and understanding!