Unnecessary initial FL on EGKK routes via LAM

Hi there,

We keep getting lots of pilots cruising at FL220 from EGKK to airports such as EGPH and EGPF. See SimBrief FPL ID 65765202 as an example.

Seems to be something to do with the L10 from BPK to LAM that SimBrief is restricting to FL220 before a step climb at BPK. I’ve checked the AIP, and the L10 is established from FL75 to FL460 so I’m not sure why this would be a restriction? There are a lot of ATS routes now in the UK that don’t have an ‘U’ prefix but are still established at high levels.

None of the real world FPs via the LAM SID file this initial FL either. Could the logic be amended to prevent this artificial cap please?

(Reason I ask is that FL220 is actually very inconvenient and low on VATSIM and sometimes it takes controllers a while to explain this to pilots…)

Thank you!! :slight_smile:

1 Like

This is a long standing issue linked to the AIRAC data where available levels are split depending upon direction, so whilst LAM-BPX should be available FL100-FL430 the reverse restriction is applied capping at FL230.

The situation applies to all instances where these splits occur.

Personally if the correct levels cannot be implemented then the use of the higher level would be preferable.


I’ve manually corrected the altitude restriction on L10, it should no longer limit you to FL220 in that direction.

Agreed, but unfortunately we don’t have any control over how our data provider codes this in the source data. For now I’ll have to manually correct these on SimBrief’s end.

Do you have a list of other airways this commonly affects by any chance?


1 Like