It would be nice if we could set certain variables before a flight in the UI, for example a RW/SID and destination parking, so that the controller then issues these instructions instead of what it would have done on its own.
This would not just help to recreate historic flights but also create some consistency between real world and simulation. Currently I also experience it a lot that BeyondATC’s ATIS decleares one runway and the controller then assigns the direct opposite of that which leads to adhoc replanning and frustration.
Also the random parking at destination could be avoided by this, leading to better planability and realism. The same goes for STARs and approaches.
This would be an optional feature for people who want to enforce certain segments on their flightpath, if you don’t use it, BeyondATC does its thing as if there were no user settings.