Simbrief Incorrectly Planning LOGAN arrivals into EGSS/EGGW

SimBrief Dispatch
1

I’ve noticed recently that several aircraft filed to EGSS/EGGW have been incorrectly assigned the LOGAN2A arrival by Simbrief, despite filing above the maximum RFL for that arrival (FL105 for EGSS, FL125 for EGGW) .

The filing of this STAR means the aircraft has necessarily been routed past a fix where it could have joined the correct STAR (RINIS/XAMAN/TOSVA), and even aircraft that file with RNAV1 equipment, and therefore can fly those arrivals, are being routed via the LOGAN2A. Routing via LOGAN for these aircraft fails IFPS validation and creates a real headache for those flying on multiplayer networks such as VATSIM and IVAO.

I would expect that, at the very least, routes are IFPS validated (where appropriate) before being suggested to users. Clearly this is not the case. Can this be looked into?

2

Unfortunately automatic IFPS validation is not an option. Eurocontrol does not permit access to their APIs for flight simulator tools like SimBrief. Some routes have been manually validated and are given priority in the route suggestions, but it isn’t realistic to expect that every city pair will have a manually validated route. Especially when these routes can change with each AIRAC cycle.

If you have knowledge of IFPS validation and are willing to submit validated routes to the SimBrief database, I can give you access to this system if you’d like. :slight_smile:

Otherwise, can you provide some specific examples of routes that used LOGAN2A? Mainly the originating airports so that I can look them up in the routes database?

Cheers,