Do you have any add-ons in your Community folder? If yes, please remove and retest before posting. NO
Are you using Developer Mode or made changes in it?NO
Brief description of the issue: In the flight plan I follow all the waypoints, altitude change according to ATC, but on the approach, ATC stops giving me instructions to align with the runway. And the altitude is too high for a good approximation. Then I have to improvise the landing. Why is this happening?
Provide Screenshot(s)/video(s) of the issue encountered:
Detail steps to reproduce the issue encountered:
PC specs for those who want to assist (if not entered in your profile)
Build Version # when you first started experiencing this issue:
Are you on the Steam or Microsoft Store version?
Did you submit this to Zendesk? If so, what is your ticket #?
Tower “you are clear to land runway 27”
me landing runway 27
tower “you did not have clearance for runway 27 !!”…wtf ???
Another day, not any option available to talk to tower, have to take off and land for having options to appear.
Or 2 different centers sending me to each other, a 10-minute ping pong.
and like you some approach abandonned,
and so many others.
ATC doesn’t need fixes, it needs a total revamping.
ATC is working perfect for me in this sim. Except the ATC in Bucharest airport. When I landed there and made a turn around to go back to Dublin, ATC stopped working and there was no option to request takeoff, taxi. I had to give clearance by myself haha. Overall I have no problems with ATC I’m this sim.
Can confirm! My first approach into LAX would’ve resulted into a head on collision with the surrounding mountains if I had stuck with ATC requests! Kind of ■■■■■■me off honestly. “Please expedite you decent to 6000 feet!” as I’m realizing I need to make an emergency ascent to 8000+ to clear the mountains in front of me! Not cool Los Angeles Approach!
I can only imagine! lol . I was flying IFR at night but Luckily was in the Citation Longitude and was able to realize what they were getting me into before it was too late! Left a bad taste in my mouth though and haven’t tried that particular approach since. If I remember correctly I was coming in from the northeast for the LAX ILS 25R approach. Didn’t help that the game started stuttering as soon as I got on final lol.
You don’t mention who created the flight plan: World Map, SimBrief, Little Nav Map, Navigraph, etc. Recently I created flight plans in rhe various apps using the same Departure and Arrival airports. The same SID, STARs, and Approach where possible. I was thinking the flight plans would be identical but there were minor differences probably impacting ATC communication.
The World Map had crossing restrictions for waypoints matching the appropriate SID, STAR, and Approach plates. Surprisingly when I used this flight plan, ATC gave me accurate instructions to put me on the approach.
I used the same flight plan imported from another app. It did not have any waypoint crossing restrictions. When I flew the flight plan, ATC gave me weird instructions to climb to 15,000 ft followed by command to descend. Since there were no waypoint crossing restrictions, ATC assumed it can give you instructions to climb or descend between some arbitrary floor and the cruising altitude in the flight plan. This is the “broken” ATC.
There are several options to consider: 1) create from scratch the flight plan created by other apps. World Map will put the crossing restrictions into the flight plan, 2) import the flight plan created by another app. Gather all the appropriate SID, STAR, and Approach plates. Request climbs and descents from ATC to follow the published procedures. 3) Ignore ATC.
In FSX the ATC control was more precise and the altitudes were correct to avoid collisions with the mountains. Also, it always left you well focused on the ILS approach. I wonder if I am doing something wrong in this new MSFS.
I think FSX probably had good underlying navigational data. Jeppesen I think.
What they currently have seems to be messy. You’re almost forced to buy a Navigraph subscription if you really want to get into it in a serious way. Maybe then ATC will start to behave a bit more?
The ATC often stops working on approach. This issue exists since months now, I think since Wold Update 4, and it has been reported in many threads here.
Asobo stays silent on it however.
I guess predending the problem does not exists is their “solution” here.
I agree that this problem is most likely caused by the exports from LittleNavmap et al. not having matching MSFS’ natively-generated flight plans. I even exported a plan recently from LittleNavmap that could not be loaded by the sim at all until I modified it by hand. I don’t remember exactly which value was wrong, unfortunately.
I might also suggest another workaround: modify the flight plan slightly while in the cockpit, e.g. select a different departure, arrival, and/or approach, then change them back to the original intended ones and request clearance for the “new” plan. I haven’t tested this myself, but I suspect it would work.
Make sure you have both an arrival and approach selected in the world planner. Some people find that default ATC behaves better (in terms of giving top of descent instructions as well) if a plan is imported from simbrief rather than generated via the world planner, so that’s another option to consider.
ATC has been working fine for me issuing the correct altitudes for the SIDs, STARs, and Approaches. Lately they’ve been issuing speed restrictions as well. But ATC only works correctly if flight plans are generated by the World Map. Flight plans imported seem to be missing information ATC needs.
