ATC wants me to go to higher altitude than requested

Honestly I don’t recall. But yesterday I encountered another glitch. Hopefully some of these issues will be resolved in the Sim upgrade on March 8th.

Yesterday I had ATC mess up again. Flew from Asobo (Bordeaux/LFBD) to Microsoft (Seattle/KSEA) .

Flew the trip at FL4400. ATC started my decent late, based on what was in the FMS. After over 10 hours of flying, it brought be in higher than it should have on one of he final waypoints and then didn’t recognized that I passed it, but much higher that what I should have been at, but based on their instructions.

And we all know how much they complain if we don’t comply with their altitude request. I cancelled my IFR and and did a VFR to ILS 16L. Perfect landing other than a jet pulling on unto the runway just as I was touching down. No sure if it was an AI plane or person.

I posted a few photos of the trip on the screenshot mega thread.

ATC and ILS/RNAV sometimes mess up, but I just deal with it and do whatever it takes to get the job done.

Another bug I noticed is that when pulling up airport information from the FMS, it doesn’t always show the ILS frequencies available for runways. Maybe that is one of the ones I had problems with.

I have a folder and I download approach plates, mostly from Flightaware, and pull them up as needed. On a lot of IFR approaches I just use automatic runway and let ATC decide for me and enter the info when told which RWY to use.

Maybe some of my problems have been where I used a chart and the airport doesn’t have that ILS implemented or the chart frequency is different from the chart. I will start paying more attention and report to the Zendesk any published approaches which may be missing in the sim or not have current accurate ILS frequencies.

The missing frequencies is due to any issue mostly with third party add-ons airports, and is an issue that ASOBO is currently working on.

Missing approaches is more likely due to NavBlue data issues.
They are the supplier of navdata to MSFS and there are some issues that ASOBO and NavBlue have encountered with their data base.
It is fairly good in Europe (where most of NavBlue’s business is), but seems lacking in other areas.
Fortunately that data gets updated somewhat regularly, so hopefully these issues will get less and less as the sim matures.

If you get a third party addon like Navigraph, the approach data is much better.

1 Like

This is why I am having problems landing on an ILS or RNAV approach into Munich (EDDM), which I have recently updated using third party addon

Might try the flightplan again using Navigraph data rather than planning it on the sim itself

1 Like

That should do it. You will have the correct approach in your plan by using Navigraph data (unless they have an issue!!) :slightly_smiling_face:

When the Navigraph data package is added to the Community folder, same as any mod, the sim will use Navigraph data as well.

In the cockpit, if you have entered your flight plan arrivals, you need to check and ensure that the Nav1 or ILS frequency has automatically entered.

If it doesn’t, you will need to know what that frequency is IRL, and manually enter it.

2 Likes

Yep, the altitude assignment part of ATC has a couple of “features.” In the real world, when you file a flight plan you list the aircraft type and an equipment code. These make sure ATC doesn’t assign you an altitude of say FL230 when you’re flying a BE36 with a ceiling of 18,500’ (as is happening to me in the game right now). The equipment code tells them what avionics are on board so they don’t give you an RNAV approach if you’re in a Piper Cub, for example.
Possible suggested fixes:
– Tie the ATC altitude algorithm to the capabilities of each aircraft.
– Add an “unable” option to the ATC communications menu.
– Instead of “Request Cruising Altitude Increase/Decrease”, then another menu for how many feet increase/decrease, maybe just one menu for “Request XX,XXX feet”

1 Like