Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Which aircraft are you using that experiences this issue?
default A320 neo
Brief description of the issue:
The cruise altitude i set in the flight plan doesn’t always match up with what ATC thinks the cruise level for my plan is.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
I planned a flight from KTPA-KMIA in the flight planner using Sids and STARs and an ILS approach. Set the cruise level for FL280. During the flight, after reaching cruise level, ATC asked me to climb to FL340. FMC said I was at cruise level at FL280. I ran the same flight twice with sane results. I saved the .flt and .pln if you would like to try and reproduce. Or you can set up the flight in the planner using default neo departing KTPA runway 1L using SID LTGNG3 01L and KMIA arrival STAR FROGZ4 09 with ILS arrival 09 for runway 9. Set the flight level to 28000 in the navlog and fly.
PC specs and peripheral set up:
Are you using DX11 or DX12?
11
Are you using DLSS?
no
For anyone who wants to contribute to this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
Are you using DX11 or DX12?
Are you using DLSS?
If relevant, provide additional screenshots/video:
I notice when I plan this flight, the FMC will show FL340a at PLOWS even though cruise level is set to 28,000. Maybe because this is a long STAR and flights from further away would be expected to be at the FL340 at PLOWS? Hmmm. I didn’t check simbrief flights so I’m sure this wouldn’t be the correct departure and arrival from Tampa but still, why is ATC telling me to climb to FL3400? I just thought it was a neat route.
You could always bypass a waypoint and fly direct to a lower one. The ATC isn’t robust enough to completely recognize that, but it happens in real life often enough.
But even if I import the above Simbrief plan, it still shows a cruise altitude of 25,000 and FL250 at Matny. So ATC should not be telling me to climb to FL340. I still think it’s a bug. I’m gonna fly it and see what I get.
Ain’t that the truth. Importing the Simbrief plan Matny doesn’t show a restraint and ATC doesn’t ask me to climb. I’ll still leave the bug open as it does happen.
According to SimBrief, the download instructions for MSFS are:
Download this file anywhere onto your PC.
Open your simulator and go to the “World Map” screen.
Click “Load/Save” at the bottom of the screen, then click “Load”.
Browse to and select the *.PLN file you downloaded in Step 1.
NOTE: After import, you may need to reselect your SID, STAR, or approach using the provided dropdown menus.
Whenever I import from SimBrief, I always reload the SID and STAR because the SimBrief flight plans (.pln file) do not contain SID and STAR waypoint altitude and speed restrictions needed by ATC.
That’s good to know. So how would you do this plan if you know you can’t reach that flight level at Matny? The flight planner doesn’t let you set a waypoint to join the airway.
If you are coming from KTPA, you would normally select the SABEE transition for the FROGZ4 STAR and thus bypass PLOWS. You would then have the first altitude constraint at KLEET with below FL280 and above FL210, so you could stay at your FL280 until then. SABEE is a special transition for traffic departing the KTPA area.
Interesting. But I wonder if you can input that into the flight planner. FMC yes but flight planner probably not. At work so can’t check at the moment.
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute to this issue, Click on the button below to use this template: