ATC tells me to descend, then ascend, and then descend?

[SquarishBacon68]

I flew into O’Hare airport in Chicago yesterday with the Beechcraft King Air. I was ultimately instructed to descend to 3700 ft. Then I was given the transition instructions to a waypoint called GIBNS, which takes me west of the airport for a landing to the east. I probably spent 15 minutes traveling to GIBNS at an altitude of 3700 ft. When I arrived there, I was then instructed to ascend to 9000 ft. At first this made no sense to me, but I later realized that this is the highest altitude at which you can capture the GS. I recall seeing that on the aviation chart for that particular runway. Then ATC proceeded to give me the instructions to step down my altitude just as shown on the aviation chart.

I found this not only unrealistic but also rather annoying. There must be a way to smooth out the descent instructions so you would never have to ascend after you’ve already descended, except for a missed approach. Either have me descend to the highest altitude to catch the GS prior to arriving at GIBNS (9000 ft), or have me descend to 3700 ft and I can capture the GS closer to the airport at that altitude.

I’m still new to MSFS, so please let me know if I’m missing something here. Thanks as always for your feedback.

[sqlmike]

Is a bug.

Into LSZH (Zurich, +1495 MSL), I had a descent to 7000 feet, then given the transition and told to climb to 7600. The initial descend was too low, technically MSA for that sector, but below MSE for the next one.

[SquarishBacon68]

Thanks for your response. I also sent this issue to the Zendesk. Hopefully they will do something about it in the near future.

[Rob0002018]

A lot of ATC altitude problems, when trying to request a decrease of 4000ft My co requested an increase of 14000ft???

[HeavyWeather832]

Same issue in many routes, descend then climb when you are very close to the airport, in this case i usually ignore the ATC.

[HeavyWeather832]

true but they should also call the crazy ATC controller