Hi,
I think the root cause is the ARINC data format doesn’t support different max altitudes depending on direction of flight. So when Jeppesen produces the ARINC records, they have to choose 1 maximum altitude to use. I’m sure they have their reasons for choosing the lower altitude versus the higher one.
There might not be anything we can do about this, but we are looking into it. SimBrief already ignores certain maximum altitudes when it’s obvious they are incorrect (for example, if the airway minimum is higher than the maximum, which happens in a lot of these cases). But it doesn’t catch this one unfortunately.
I’ve added a manual correction for this route at least (which should also affect similar routes), so it should be better now.
Best regards,