Wrong Altitude constraints unmodifiable

Bug Reporting Hub ATC, Traffic & NAVAIDs
, ,
1

ISSUE DESCRIPTION

Description of the issue:

The altitude constraints are ridiculous.
How can a flight plan be automatically created in such a wrong way that I cannot modify it at least using the EFB before sending it to ATC and Avionics?

According to the automatic flight plan you should go to altitude 339-760-1150-4600 (or above) BUT at ML624 you MUST descend to 2800 and then you have to climb to 6000 or above.

At EKPAL you must be @ FL195 or above BUT at PRT you must be at 13100 to go after at 20000.

This is ridiculous.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

100% of the times

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Free flight

  2. Create a flight plan from LIML to LIRN and

  3. then ‘find route’-> this automatically choose the departure procedure ABSE6A via LOG7A with no constraints in enroute portion

  4. Then change it choosing Depart procedure (Keep runway 35) from LIML using TOVS6J via EKP6A

  5. Immediately after this check that altitude constraints appears both on the departure procedure and in the enroute portion.

  6. Check Altitude constraints in the picture in the media

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it?

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

IMG20260613123434
IMG202606131234341792×3904 1.27 MB
2

This is not a constraint (no bars), but a calculated altitude based on the selected aircraft. It may be that the performance data for the plane is incorrect or missing.

3

the calculation of the altitudes reflects what it is the SID for that airport. If for some bug they don’t report the correct altitudes then you have situations like the one I am reporting: going to 7000feet, the due to a bug it sends you to 26000 feets and then going back to 9000feet.

This problem is specific to the SID of an airport which is incorrectly managed by the msfs2024.

In my case you can try your self at LIML SID From rwy 35 via TOVS6JA.