ATC approach instructions issues (too late and high altitude)

What does this mean?

1 Like

So, leaving the destination airport set to default automatic values in world map, it means you have to wait for ATC once nearing the destination airport to assign you an approach and runway, you then input it into the onboard computers.

I like doing it this way as it feels more realistic, it doesn’t always go smoothly though, there is an issue, such as plane turning around and flying 10 miles back to the last waypoint before starting the approach I just inserted into flight plan.

Anyway Happy Christmas all.

2 Likes

Agree dependant on approach definitely. Hence the need to look at charts or constraints.

1 Like

It can certainly lead to interesting arrivals and fingers crossing that ATC is awake & working.

Hope you all have a good Christmas too.

1 Like

Gotcha thanks. I do what your referring to a good bit, just didn’t realize what you were describing until now.

Lately I’ve been just starting cold dark from a gate, no destination on the world map prior to flight. I use auto engine start. Then Enter Departure and arrival airport into the FMS only, then request IFR from clearance. I’ve actually had good luck with this other than cruise altitude. For example I hop from Charlotte KCLT to Atlanta KATL a good bit. ATC will sometimes only give a cruise altitude of less than 10,000 which in the airbus and if being realistic and obeying speed limits means a slow flight. I usually request cruise altitude increase. That’s the only issue ive had lately. When approaching the destination I usually get good ATC directions for arrival and decent.

2 Likes

+1000

I have the same problem. Airliner flight is really unimmersive that way. I voted here because it´s a really important topic.

This needs to be fixed soon.

Despite the usual problems with ATC and late calls for approach which I suffered pretty often, yesterday I found another annoying issue.

I was flying from DTNH to DTKA, a short 40min trip with the King Air 350.

The ATC told me to ascend to FL200. I thought OK, I will ascend and then ask to decrease altitude. But then, while slowly ascending the ATC told me to maintain 11000 feet, so I’ve changed and tried to descend to that. Then the ATC started to ask again for the FL200, I went up, and again it said 11000 feet. It was like if he wanted me to fly both altitudes at the same time.

On one of the FL200 requests I’ve asked to decrease but he wanted me to ascend anyway, while I was already pretty near to the destination airport.

In the end I’ve ignored everything and tried to go for a correct ILS altitude but this is pretty annoying and totally brokes the immersion.

Is there any fix planned?

1 Like

This is still a brutal and constant issue for me. I have been completely ignoring ATC since sept of last year because their approach instructions are nonsense and totally break the immersion of the game.

3 Likes

Same issue here. I think it is of tremendous importance and needs to be fixed.

I don’t think it has to do with buggy minimums, at least not always. Sometimes I am flying an STAR which has all minimums correct. The ATC simply instructs me to descend way too late. In order to catch up with it, I had to descend at unsafe and unrealistic vertical speeds while jamming on the spoilers to keep speed under control. 5,000 fpm descent and I barely made it to the right altitude to intercept the glideslope.

MSFS is killing me right now. It’s not too much to ask to be able to fly a normal IFR flight in a 747/787 with ATC. Seriously, this stuff should be bare minimum. Get it together, Asobo. Stop ignoring issues like this because most people have moved on and decided to ignore ATC.

2 Likes

This still happens btw… 2 out of 3 flights…

2 Likes

Yes, this totally still happens and it’s pretty annoying as the ATC it’s a fundamental mechanic in a flight sim.

Despite some nonsense calls like to ascend and fly at FLC350 with a King Air for example, it stills calling late and bad, so you cannot trust the ATC. It maybe asks you to drop 15000ft in 10 miles for example.

Is there any patch or fix on the way?

Also, is there any mod that could help to reduce this?

Personal Comments

I use an EFB with my flight plan like Little Nav Map. The reason LNM is useful to me in vertical navigation is it it gives a step down profile at each waypoint past the TOD. Instead of waiting for ATC to step me down, I request the nearest altitude in 1000s increment to the waypoints after calculated TOD. This includes STARs. By the time I’m issued the Approach, I’m usually on the STAR and descending to the IAF altitude fix. Sometimes, I’ll end up listening to ATC telling me to return to cruise, but that only lasts about two waypoints before the IAF. Then it’s all synched again.

On Xbox, I very often just ignore the ATC on approach. With my 1000+ hours of flight time, I believe to have a descent amount of experience on how to handle altitudes etc. Most of the time. But very tricky approaches on mountain terrain can be a challenge.

1 Like

It’s about time they fixed this, the whole ATC needs a rework, instead of doing little tweaks here and there some of which i have not even noticed, having ATC services that work should be a priority.
Enough people have mentioned it, it’s almost like our voices are falling on deaf ears.

3 Likes

Agree with you. Feel kinda cheated when I bought the Premium Deluxe and ATC went bonkers some or most of the time with either airports, even default or add-on aircraft. Other features are excellent, don’t get me wrong… Hope MSFS team will prioritise on ATC improvements in the next update…

3 Likes

I was flying IFR in the DC-3 yesterday cruise altitude was set for low altitude airways 6000ft, was just a short hop from my local airport across the channel to Jersey, when I should have been told to start descending I was asked to climb to 20,000ft In a DC-3, yeah right!

2 Likes

Sheesh, this bug has 58 votes, been around for over a year, yet MSFS/Asobo hasn’t even logged it as feedback. Meanwhile bugs with just 6 votes that have only been around a couple days get logged.

Further evidence that Asobo chooses to ignore issues that they can’t fix easily. And customers are left in the dark. A bug thread titled “Arrival parking preselected in the World Map not used by ATC since SU6” shares a similar fate, just for example. (EDIT: that thread has finally been tagged “feedback logged”! Perhaps they’ll even realize that it is indeed a bug. Baby steps.)

At least log it already, Asobo! You get to choose whether to fix it or not either way. Your customers are feeling ignored! The “if I pretend I don’t see it it’s not there” approach is unprofessional.

(PS: Not just an Xbox issue, BTW. Same for PC. Should add that tag to the bug.)

3 Likes

Have to chime in and say that after 2 years, I finally graduated myself to flying the A320neo and sad to say this ATC issue still exists. Approaching an airport for landing and regardless of whether I’m using a Flight Sim flight plan or Little Navmaps, as I’m on approach, ATC will tell me I’m 700 feet below my flight level. I hate flying without ATC as it’s too quiet but I’m loving flying the neo too much to go back to my beloved CJ4 and Longitude. ATC reacts properly on approach in those planes.

Same here, ATC is way to late and one is way to high and close to the destination when (or better: if) any ATC instruction comes…

Complete immersion killer for this kind of flying (guided, IFR) for me.