ATC requested STAR and waypoints not in database - free SImBrief version MSFS

[1627359]

To be fair, that really would have been a bit much, especially when you consider how procedures fit into the world of aviation - what would you do about a decommissioned runway that was replaced by a new one, for instance?
I still think what I suggested in the announcement post would be a more equitable solution - after all, it very often is possible to find some workaround, the problem of outdated nav data only really becomes a problem during high traffic or in procedural airspace, but if I have three or four aircraft in surveillance airspace, e.g., I don’t need everybody to fly the STAR and can instead use vectors (and likely be significantly more efficient in the process).

@1627359

B14 seems a bit out of place as a separate rule - I feel like it would have made more sense as B8(d). However, my main point of contention here is that pilots not having the latest AIRAC has rarely been a problem. Unless a pilot is using ten years old nav data or procedures at a given airport/structures in a given airspace have recently seen a major redesign, it has usually been possible to find an adequate alternative solution - provided the pilot communicates this, of course. While I welcome the idea behind this rule, I feel that it could have been made less restrictive to pilots who may not be able to pay for a Navigraph subscription to keep their nav data up to date at all times (sure, MSFS2024 will always use the latest nav data, but not everybody will be using MSFS2024). I feel like a rule similar to B6 may have been a better compromise: permit pilots to use out of date nav data, but require them to disconnect if ATC can’t accommodate them without the latest procedures, as well as requiring pilots who are using outdated nav data to check beforehand if there are procedures they are not able to fly and inform ATC accordingly in advance.