Thank you for 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
Have you disabled/removed all your mods and addons?
Yes
Brief description of the issue:
Basically, when I’m doing an IFR flight with an ILS approach set, when I reach the last waypoint of the arrival (RAXI1B33), the ATC just say to me for hold at 7.000ft (last arrival altitude), and await for the airport approach. So I normally do the approach but the ATC don’t change my altitudes of the ILS approach OPVIS (5.500ft)REPID (4.920ft), it just freeze in EDSUR(7.000ft). So, I didn’t get clear for arrival at SBCT (arrival airport), it justs mantain at 7.000ft and the last time the ATC calls me is to inform that I’m approaching the airport I set.
Provide Screenshot(s)/video(s) of the issue encountered:
As you guys can see in the screenshots, when I arrive the ILS approach, the ATC stops guiding me, even when I reach the next Waypoints (OPVIS)(REPID). (I’m Cessna XGS).
OBS: When I try to just follow the next waypoints of the approach (5.500ft) (4.920ft), the ATC starts to communicate that I’m below the designated altitude, and I end up landing without permission.
DISCLAIMER: I am extremely new to the game. I apologize in advance if my question is stupid or poorly explained.
Before I try to duplicate, do you have the approach set to “vectors to final”? If you do, MS2020 ATC is terrible for vectors. If you keep asking ATC for vector to the next waypoint, they’ll eventually get you there. Not sure ATC actually includes required altitude changes for vectors.
I’ll give it a try and see what kind of results I get.
Regards
Sorry, I didn’t understand what you meant by “vectors to final”. I presume not, considering that I didn’t activate none of this option on my airplane FMC/PFD (Don’t even know how to do it, if you can explain).
Thank you for this report. We’ve moved your topic into the User Support Hub.
The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
Hi @Gabrielhxz5745
Disregard the question about vectors. That’s not the issue in the flight. I just flew the whole route you did, with the same departure/arrival/approach. The ATC left me hanging at 7000 feet also. They kept harping at me to go back to 7000 feet right up until I landed!!
So it’s a real problem with ATC in this case.
The good news is, the descent points and altitudes generated by the flight plan are showing correctly (on mine at least) on the PFD. There were two altitudes directed by the PFD (see the red circle on my screenshot). I think I missed getting a screenshot of the one that lowered me from 7000 feet to 6000 feet. But the next altitude directed by the PFD was 4920 feet (see screenshot) for final approach.
To correctly fly the approach, when those altitudes show up in that area, you’ll have to manually descend to the altitude shown. There should be two changes, one down to 6000 feet, and one to 4920 feet. ATC will yell at you all the way to go back to 7000 feet. Ignore them!! It’s a bug!
If you follow the flight plan, and descend when the PFD shows the correct descent altitudes/and you follow them, you’ll end up on the glide slope and make the landing!!
I thought I was going crazy, but apparently not… Thank you immensely for your willingness and for helping me “solve” the problem. It’s very kind of you to redo the flight plan I mentioned just to find out the problem and try to help me, I’m really grateful! Considering it to be a game bug, I will do as advised (and as I have done before), follow the altitudes according to the FMC and ignore the tower shouting for me to gain altitude.
Only if you want to answer: do you believe it is a bug with this approach, specifically, with the aircraft or something like that? I mean, if I use this aircraft for another flight plan (which I haven’t tried yet), this shouldn’t happen, right? This is a one-off bug.
It’s a little funny to think that a simulator of this size allows this type of failure to occur, it breaks the immersion of the game a little, but that’s ok, it was made by humans, errors are to be expected
It was mentioned a while back that the ATC is so deeply buried in the code that it would be extremely hard to fix.
It also requires the flight planner to be changed.
There are plans for a whole new ATC system to be introduced later for FS2024 just for that reason.
There is a easy solution, IF you want ATC that in any way resembles a Real Work ATC experience, (without resorting to Vatsim or PIlot Edges, both of which have coverage issue)
An AI ATC addon program, and currently the ONLY AI ATC program for MSFS 2020 (and later for MSFS 2024) is SAYINTENTIONS.AI.
yeah it’s like that… i just arrived at Aspen with atrocious weather, atc cleared me to a “visual” (???) approach and flew me into a mountain
suposedly it will get better in msfs 2024
As @TheSevenflyer said, it happens sometimes, and sometimes the approach works perfectly. I’ve got several approaches I use for testing that I know work every time. But I’ll fly another one I haven’t used before, and there’s the problem again.
We all look forward to the day the in-sim ATC works right. But even real ATC screws up sometimes (no knock against the vast majority of our ATC professionals. Normally they do a stellar job under stressful situations!!).
Regards
Well, I hate to be the SmarA$$ here, but you are PIC, If you are initailly given a Visual approach, and you, as Pilot In Command, do not feel comfortable with that (as it sounds you should;nt have), you ask ATC for an Instrument Approach, or go land somewhere else,
Also, you as the Pilot, should be aware of the terrain, and not leave yourself to be 100% dependent on ATC to keep you from flying into mountains
Almost all, but the every oldest and basic GPS or FMC system, have terrain map data, and you also have access to charts that show Minimum Safe Altitudes,
I don’t think many DEAD pilot’s tombstones have the inscription.
“Here lays Captain Smith, he died because ATC had him fly into a Mountain”
BTW: Don’t be to hopeful that 2024 will have any great improvements in ATC, and anything they do have, will be very much inferior to addon AI ATC programs like SayIntentions.AI
First thing. You are flying entire approach on standard altimeter setting 2992 inHg when the local barometric pressure is 3002, see ATC message on second picture. That’s why ATC says you are at wrong altitude.
Now back to the approach. ATC clears you to CTB waypoint and is expecting you to fly over this waypoint. Only then will give you clearance to descent to 5500ft. The problem is on this particular approach you don’ fly over CTB waypoint, it’s not on the flight path as shown on the chart. I flew this approach a moment ago and had the same issue with ATC. I passed REPID at 7,000 and still nothing from ATC. I turned around for another approach maintaining altitude, vectored myself over CTB point and then ATC cleared me to 5,500ft and later for landing.
Try again but request ILS W approach (second picture) and ATC will be working fine. And remember to set you altimeter correctly.
Don’t listen to people saying default ATC is completely useless. I use it every day for IFR flights and it works fine 9 out of 10 times.
Thank you very much for the detailed explanation and for taking the time to record a video to explain. I really didn’t expect such a friendly community. I’ll watch it now.
UPDATE: Yes, you definetely right. I did with the ILS W approach and worked fine. The problem is with the ILS 33-Y.
You can find free charts using google but most likely they will be outdated. I have Navigraph subscription to have access to latest charts and also AIRAC navdata.
In any case, I will try to use the ILS W on the approaches I make to avoid problems, regardless of the airport. Or, I’ll try to use these approximations with more “direct” curves, without this arc transition. I would never have thought that the problem would be this, even because I don’t have access to this type of more detailed navigation charts.
It’s not always the case with this type of approaches. After 4 years of playing this game and landing on over 700 different airports this is the first time I saw ATC having problem with a curved approach.
Hello, my friend. I encountered the same problem in 2024 and I’m not sure if it was caused by the same issue. However, I have tried many airports and ATC almost never gives descent instructions. They just asked me to contact the control tower. May I ask if there was any operational error on my part？
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
