In the Route between airports tool, sometimes a constraint is added that was not given.
eg for LFPG-EIDW with route ATREX UT225 VESAN UL613 SOVAT L613 SANDY OKSAW TEWXI LANON L18 ABLIN
if you enter an altitude restriction of 99999, the resulting route will be
You need to enter 99999/ATREX/99999 as an altitude constraint to get the route N0443F410 ATREX UT225 VESAN UL613 SOVAT L613 SANDY DCT OKSAW DCT TEWXI DCT LANON L18 ABLIN
which is IFPS compliant
Where is the constraint at VESAN coming from and how to get rid of it?
Since SimBrief can’t actually parse the entire RAD document, it instead has to “learn” about these restrictions based on routes other users have added. In this case, a user had previously added a route between LFPG-BIKF and correctly capped the airway at FL305. Note how the route below does not validate if you plan VESAN UL613 SOVAT above FL305:
So now that a previous user entered this restriciton, SimBrief thinks that all routes between VESAN UL613 SOVAT need to be below FL305. SimBrief will also cap the airway in your route unless you specifically tell it not to.
Entering only 99999 will be considered as an overall max-altitude for the route, but won’t override individual airway caps. So you need to be more specific and enter 99999/ATREX/99999 so that SimBrief understands you also want to uncap the airways.
In general, when adding new routes, simply override any restrictions that SimBrief isn’t correctly following. There are a few possibilities where it is getting them from, but normally you should just override them as needed.