Desperate for help, inexplicable ATC issues!

The last couple days, inexplicably, ATC communication is no longer working for initiating IFR clearances.

I reinstalled the game completely and I am still having the issue. No mods, no .locPak changes…SHOULD be 100% stock.

  • In the screenshot above, you can see that after I request IFR clearance…I get nothing back from ATC despite the “Acknowledge…” prompt appearing.

  • if I do acknowledge, the ATC window gives no other options (can’t get clearance to taxi, can’t get atis, etc.)

  • If you proceed and takeoff, it acts as if you need to “Retry IFR…”

Please help me troubleshoot this.

  • I made sure to completely delete the /Official and /Community folders (MS Store Install), /AppData/Local/Packages/Microsoft.FlightSimulator_8wekyb3d8bbwe is also clean. not sure if there are other spots where settings could be stored?

  • I toggled off Azure TTS to see if that was the problem (it wasn’t)

  • My internet connection is stable

Any help troubleshooting this would be GREATLY appreciated. Thank you!

My issues with ATC. I will get instruction to for example TAXI and then ATC will go on for 6 to 8 minutes talking to other planes but I’m greyed out from acknowledging. Sometime I will be waiting for take off and I never get cleared to take off but I do get a message asking to acknowledge the take off instructions.
It’s been real busy at major airports.
I think they are working on ATC right now.

I wonder if it’s because you’re also tuned in to the ATIS? I can see that text underneath the options which I think is the ATIS broadcast.

Try to pick a different tab use the COM2, see if that works out.

Also, what I found that if you create a flight plan from the world map, then you change the flight plan BEFORE you get clearance, the ATC gets stuck sometimes. So what I usually do is I create a flight plan from the world map, start my flight. Then I immediately ask for the IFR clearance. Once the response works fine, then I can change the flight plan, and off I go. I usually don’t request another clearance because the cruising altitude gets reset and no longer using the cruising altitude that was created initially. So I just leave it alone.

Even if you do, you can just ask for a cruising altitude increase anyway, so it’s okay.

1 Like

So, I think I may have found the issue? It was luck because I had but ONE mod, which was “Tiny Taxi Ribbons” from flightsim . to . Removing it is currently allieviating my issue. Will report back if it doesn’t solve but…maybe this thread can be a cautionary tale for someone else.

I’ve been using Tiny Taxi Ribbons as well since last year, and I never came across your issue, other than doing the steps I mentioned above, if I did get a similar case…

Yeah I’ve been using it too, and it only became an issue within the last 48 hours. Weird.

Yeah, weird… Just did a couple of flights, a few hours ago and they’re fine with the tiny taxi ribbon mod.

Nevermind…you’re right. That is not the issue. Still need help :frowning:

I have the same problem. This happened after the windows update, and nvidia driver.

Do you by any chance use Lorby AAO or Navigraph? Currently investigating whether the SimLink program for navigraph has introduced some weird issue…

edit: nevermind, completely disabled these programs and still having the issue

I have also experienced this issue. I came to the same conclusion as Neo4316. It has addressed the issue for me.

  • create your flight plan in the World Map planner as usual
  • Once you press “Fly Now” and turn on your batteries/APU, request IFR clearance (before going any further on your checklist/procedures.)
  • Once ATC gives you clearance and confirms your readback, you can then continue to enter/change your IFR flight plan.

I think I’ve also just taken off under VFR to work around the “bug”, then requested IFR clearance from ATC after leaving the departure airport’s airspace and contacting the handoff controller (the same as if you depart from an non-towered airfield)

Although the above workaround works for me on departure, I’m not sure if the above workaround is the cause of me not being able to request/respond to the ground controller after exiting the arrival runway. I only get the option to transmit “Say Again”.

Prior to writing this response, I hadn’t considered if the two issues were related. I’ll have to make a note to see if changing my IFR flight plan on departure is related to the inability to request anything from the ground controller after arrival.

1 Like

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