I’m not sure how that’s encoded in AIRAC, but I’d guess it is not airport specific but rather airspace specific.
The transition altitude is important for departure/arrival and center controllers, so I’d assume the TL to change from one airport to another would be quite confusing in between of them.
I agree they should somehow figure that out, it is probably provided with the data.
For the A32NX you can set transition altitude via MCDU, but ingame ATC won’t care - especially annoying for GA in Europe where you state for longer periods between the actual TL and the default of 18.000 that ingame ATC assumes.
Are you on Steam or Microsoft Store version?
MS Store
Are you using Developer Mode or made changes in it?
No
Brief description of the issue:
The transition altitude/FL seems to be 18000ft/FL180 everywhere, but in Europe it’s actually somewhere between 8000-10000ft for transition altitude and transition FL varies.
Also, the ATC sometimes wants me to fly with local QNH even when given clearance to FL180. I was flying at FL180 with standard baro when the ATC told me I was too high and told me to descend.
Provide Screenshot(s)/video(s) of the issue encountered: N/A
Detail steps to reproduce the issue encountered:
Fly IFR from an controlled airport in Europe. You should be able to ask for FL100 but the ATC keeps using QNH up to FL180.
Then fly around at FL180 with standard baro setting. ATC will sometimes ask you to climb or descend if local QNH differ from std baro enough to make your altitude differ more than let’s say 300-500 ft.
PC specs and/or peripheral set up of relevant:
Not relevant
Build Version # when you first started experiencing this issue:
1.21.18.0
Yes I agree this would be a simpler solution. Or an alternative would be to have the ability to set the departure and arrival transition altitudes in the Nav Log on the world map. This then gets picked up by ATC from the flight plan.
As a former Former employee of Navblue I know the data is defiantly exists. Its usually coded into the procedure or airport record as per ARINC 424 specifications.
So AI MFS ATC always insists that change from feet to FL should happen at 18 000 / 19 000 feet. Is there any way to teach it / force it to use the ones we use in EU (aka the proper way)? Like FL50/60/70?
Please we really need this at least for 2024, it’s absurd it can’t be implemented 20+ years later, this american defaultism really kills immersion when flying anywhere else.
