Gate Assignment Workflow Feedback#1837

I think the current gate assignment system works well for users who want BeyondATC to automatically assign a realistic gate based on its airline/gate database. I would not want to see that functionality removed. However, I think the manual gate selection workflow could be improved.

Currently, after vacating the runway, the pilot must choose between accepting the automatically assigned gate, or requesting a specific gate and then navigating another menu to select it.

This is one of the busiest phases of flight. After landing I’m cleaning up the aircraft, retracting flaps, disarming spoilers, managing APU and engine shutdown procedures, monitoring taxi instructions, and maintaining situational awareness. Having to stop and navigate multiple ATC menus at that point interrupts the flow of the simulation.

I think a better approach would be to separate gate selection from receiving taxi instructions.

My suggestion is to allow the pilot to optionally specify a preferred arrival gate at any point before landing. If no gate is specified, BeyondATC should continue using the existing automatic assignment system exactly as it does today.

If a gate has already been selected, then after vacating the runway ATC should simply issue taxi instructions immediately, without requiring any menu interaction. The simulator would already know the intended destination.

This preserves the current behavior for users who prefer automatic assignments while providing a much smoother workflow for users who enjoy planning their arrival in advance or flying into a specific gate. It also better reflects real-world operations, where the assigned stand or gate is typically known before landing rather than being decided after the aircraft has exited the runway.

In short, I’d like to see gate selection become an optional pre-arrival planning task instead of a post-landing decision.