Greetings-
I am a real world (private) pilot that flies out of KBJC. The airport has three runways. Two parallel and one very short perpedicular (3/21). In the five years I’ve flown in and out of KBJC, I’ve taken off from Runway 21 three times and I’ve never landed on 3 or 21. At only 3,600 feet in length, the runway is typically used as a taxiway unless a pilot makes a specific request to use it, or if winds are exceptionally strong in favor of that runway, then smaller planes will use it. I’ve never seen a jet use it before.
With all that said, BeyondATC seems to almost be obsessed with using 3/21 for takeoff and landing. Whenver there is a slight crosswind on the main runways (30s/12s), BeyondATC will pick 3/21 as the runway to use. It is quite an immersion killer.
I understand that BeyondATC has its own internal logic to determine the runway or runways to use. And I know the BeyondATC team has added standard procedures at many (larger) airports. However, it would be REALLY helpful if we as users could “disabled” (basically close) specific runways at specific airports. If I could close runway 3/21 so BeyondATC could not choose it, it would solve so many things. I suspect that other simmers have similar issues at airports that they might frequent.
The ability for users to select runways to close could also help with immersion for things like IRL runways closed for maintenance, etc. I know Runway 7/25 was closed at KDEN for several months for resurfacing not long ago. Being able to close it in BeyondATC during that period would help with real world immersion.
Thanks for the consideration!
To further clarify…I am completely fine with BeyondATC deciding on which (open) runways to use for landing and takeoff.
This request is NOT to force BeyondATC to use specific runways for takeoff or landing. It is only to prevent BeyondATC from choosing specific runways for use. Once a runway is removed as an option, BeyondATC should use its own logic to determine the runway(s) to use.