According to the NOTAM, the route to URWA should be: NIMTA B105 NATIT DCT MOLED N50 LIDUS G242 AST G242 ZG G242 TEREK DCT ZG.
To clarify: there is a waypoint ZG between LIDUS and TEREK. However, due to restrictions, the NOTAM requires overflying waypoint AST (located on airway G242) at FL210 or higher. Consequently, we begin descending below FL210 after passing AST; this means that after reaching ZG, we must proceed to TEREK and then make a left turn back to ZG. SimBrief does not understand this logic and removes the TEREK waypoint. Is there a way to fix this so that it doesn’t alter the specified route?
Hi,
This routing is generally invalid (at least in this effective AIRAC cycle) due to the N50 airway, which is a one-way airway from LIDUS → MOLED, but besides that, when I make a direct between MOLED and LIDUS to avoid the restriction, this should work:
There is currently a NOTAM in effect requiring us to use route N50 in the opposite direction. Furthermore, the route you proposed is incorrect: after waypoint LIDUS, the sequence is OMIRA, then AST (which we must cross at FL210 or higher, per the NOTAM I shared earlier), then ZG, then TEREK, and finally back to ZG. This routing ensures compliance with the NOTAM.
All these NOTAMs exist; it would be great if SimBrief could take active NOTAMs into account and automatically generate routes based on them. Currently, within the URRV FIR, specific routes are in effect for arrivals and departures at various aerodromes—such as URSS, URMM, URWA, and others.
This is NOTAM U0183/26; it is also available in SimBrief.
