AIRAC validation mismatch/disagreement

I’m experiencing a curious error when trying to add the following route to the database:
OKIBA N851 RIMKI Z99 LOHRE DCT MASEK DCT BERXO DCT MAKEL DCT NEPIX for EDDS-EFRO. It is IFPS compliant and when analyzing the route within SimBrief, it also returns as valid for the current AIRAC. However, when I attempt to save the route, I get an Error 400 stating that the route is not valid for the current AIRAC.

I’m not sure what could be causing this; I have added other IFPS compliant routes to this and other airport pairs without issue; I’ve only come across the error with this specific route.

Hi,

When saving the route, there are additional checks that get performed. One of them is to ensure there aren’t excessively long directs between 2 waypoints.

The segment MAKEL DCT NEPIX is 801 nm long, just outside the current limit.

I’ve increased SimBrief’s tolerances a bit, you should be able to add the route now.

Best regards,

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.