So ATC is useless in mountains?? What’s wrong with this picture…
I sure hope they improve the intelligence of Air Traffic Control.
Had the same problem
In flight HTNG to HKAM, ATC indicates me FL 140, when you have to pass mount Kilimanjaro at least at FL200. I do to listen the ATC indications if I don´t want to crash.
I had a similar experience in the past.
Today I got a rollercoaster altitude change, one after the other. MSA (minimum safe altitude) in my area was 14,500. I was still descending when I got the following… Look at ATC communications.
It kept going so I canceled IFR then resumed it when I was closer to the airport.
ATC currently is rudimentary at best. I had better ATC with a FS2002 addon.
They are also ridiculously inept at guiding you to an airport. Try landing at LOWI just via ATC. You’ll either crash into a mountain or end up 10000ft too high for an approach ![]()
So never blindly accept what they tell you. Request altitude changes if you know better or if you must: ignore them. ![]()
After takeoff from KTEX ATC advises decent to 7000ft to overcome this mountain ridge… At this moment I was at 12,000 ft.
From VNKT to OPSD at a FL300 cruising altitude, on my way for landing, the ATC is giving me an altitude that leads the A320 directly into the mountains, which are high in the whole flight.
Further more, the ATC is constantly changing my altitude for FL180, FL190, FL180, FL190, etc. during descent.
Has anyone found a way around ATC flying you into a mountain? Flying to KDVT in Phoenix and ATC dropped me to 4200 feet where the terrain was over 5000. Needless to say it wasn’t pretty. Has anyone found an alternate ATC system?
use terrain radar if you fly a plane equipment with that and yes had two close calls while flying in norway but terrain radar saved them
stick to fl190 for example and when atc ask to switch approach it usually stop switching altitudes as well
There is “Pitot to ATC” as an addon, but I don’t know if that will help in this respect.
I had similar issues coming into KJAC, and others.
As mentioned above, the Terrain Radar is your best friend in this scenario, as well as approach charts.
Even the default MSFS approach STARS can take you into a mountain.
ATC has a heck of a time routing from Denver over the Rockies.
Three crashes into mountains this week.
The AI also followed ATC into a mountain.
lol
I always find that if I disagree with ATC instructions in the sim, I ignore it and trust my own instruments and gut feeling.
Same here. Go with your gut until the sim smartens up. I also don’t understand why ATC constantly wants you to change FL. Before you get to their designate elevation they change it on you. I think they like just jerking our chain. ![]()
There is only on solution. You have your flightplan in mind and know your MDA or you can see it on a second monitor. And the most important thing is, ignore ATC.
and the lesson we learn here is:
Ignore the ATC when flying near mountains
That is part of the problem
I’m sure you’ve seen how MSFS plots STARS, they are nothing like the real ones in a lot of cases.
MSFS re-routed the STAR I was using into the side of a mountain!!!
That’s right. MSFS has some strange STAR procedures. They should build a API to get the real ones from jeppesen. That would be nice.
Until something better happens, I probably should practice “terrain avoidance procedures” more often!!
Little NavMaps (free!) supports terrain elevation based upon the created Flightplan. It has only failed me once (around the world twice now).
The failure was easy to fix. There is a Global Data file that can be downloaded for free, that has higher resolution data in it. The default data that comes with LNM didn’t have a few mountains in China and I tagged one at the top. The new global data file solved that issue. See AVSim.com for more details. That is where a support forum exists for LNM (Alex).



