Transition altitude does not work?

Could it be that the reason for all the “expedite your climb” and “expedite you descent” (since several versions) is simply that the AI/ATC does not know transition altitude or something like that (or it doesn’t always work or depends only on the difference between QNH and standard).
I noticed this because the most of the aircraft above 18000 feet get the instruction “expedite your climb” (if in climb, depends of course on the previous air pressure) and all aircraft that seem to be in descent get the message “expedite your descent”.
Or the “controller” (ATC) always takes the pressure that is currently prevailing there (on ground) and not what is above 18000 feet (i.e. standard).
With myself, when QNH is changed to standard @18000 feet, there are basically no problems - I noticed it because I made a test flight with PF3 (ATC tool) and the “controller” remained at the initial QNH, in this case 998 hPa !
This is not about the error with PF3, but about the already known error - to me it looks like either ATC or the AI stays at the air pressure they have when injecting into the SIM !

Personally I’m finding the opposite. I get nagged if I’ve forgotten to set it to standard (I do that a lot :grin:).

Yes that can be :slight_smile: , but then the ATC or AI Traffic does not recognise the transition altitude !

To the best of my knowledge, the built-in ATC presumes transition alt to be 18.000 feet worldwide.

I already know that my point was that it doesn’t work, at least not for AI traffic!

Whenever I use PF3, set std past transitional Altitude, ATC nags to go to my assigned alttitude either 500 ft below or above. Oncourse said its MS bug.

1 Like

For AI traffic the issue is likely that the AI planes might be leveling off 300ft below/above the designated altitude. Somebody pointed out a while back when the discussions were raging about the ATC altitude bug affecting us that the AI pilot (for us) is doing that. If it is based on the same code that they use for standard AI planes, it might very well be the reason.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.