Looks to me as there’s no chance to have runway 36 at LIML be preferentially used.
This problem is both into MSFS ATC (which I don’t use anymore) or pilot2ATC.
I mostly think it’s a problem with MSFS 2020 database. Anyone know how to make just this very minor fix overriding this information somewhere?
You can.. You just need to add the runway into your flight plan. If you’re departing from LIML, you can set a departure pattern (SID) that departs from Runway 36 (if available). Similarly, if you’re on approach, you can also set the Arrival pattern (STAR) and/or Approach into Runway 36. And the ATC will take this into account and give you clearance to that runway anyway. But since you mention you’re not using MSFS ATC, What do you use?
I just realize my question wasn’t complete. If I’m selecting the STAR/SID there’s no problem. Mostly the problem is when this thing is done automatically for VFR (both if there’s a flight plan or for pattern practice).
I use pilot2ATC but actually is the same then with MSFS2020. Even with 0 wind knots they both assign to me the 18… I don’t understand the criteria they both use.
I have to explicitly request the 36 either they assign the 18 to me.
The preferred runway(s) are embedded in the BGL file that contains the airport. It’s not a user modifiable characteristic. You can see which runways are preferred by viewing the airport in an external EFB like LittleNavMap.
For VFR, there is no workaround short of predefining the runway in advance in the Flight Planner. For circuit training at a specific airport, you are limited to the preferred runway, or in rare cases when wind and ATC are in agreement, whatever runway the logic thinks should be active.
ATC revamp is a long-term project, not slated to start until 2022.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.