After landing at any uncontrolled airport and exiting the runway, the ATC menu only prompt is to tune to a departure airport frequency

Microsoft Store version
Developer Mode ON or OFF
Zendesk Request #144973

Since SU5 in summer 2021, after landing at an uncontrolled airport and exiting the runway, the ATC menu’s only prompt is to tune to a departure airport frequency whenever the flight originates from any other airport.

Because of this bug, one cannot announce clear of the runway or select a runway for takeoff and announce taxi and departure.

If the departure airport is a controlled airport, the prompt at the arrival airport is to tune to the departure airport ATIS.

If the departure airport is an uncontrolled airport, the prompt at the arrival airport is to tune to the departure airport traffic.

Only when the departure and arrival airports are the same will the ATC menu work correctly as it did before SU5, providing options to announce clear of the runway and for starting a new flight.

Workaround: After exiting the runway, without any announcement to the arrival airport traffic radio, taxi to a fuel pump and/or park, or take off.

Detail steps to reproduce the issue:

  1. In the World Map: Select an airport for departure Use the default departure runway or select any runway or parking (it does not matter for this issue)
  2. Select a different uncontrolled airport for arrival Use the default arrival runway or select any runway or parking (it does not matter for this issue)
  3. Take off, tune in the arrival airport traffic radio, fly, select a runway for landing, announce position, announce on final, announce position, and land at the arrival airport runway (Manually flying or using AP with an approach does not matter for this issue)
  4. While landing, have the ATC menu open so you can observe it when you exit the runway
  5. Exit the runway
  6. Observe that instead of the Announce Clear of Runway and other options, the only option is to tune to a departure airport radio frequency,

Airports tested:
Departure: KSTS, O69, OQ9
Arrival: O69, KDVO

Yes I notice this too, it’s very annoying.

1 Like

This is fixed now, as of the release of SU11, as mentioned in the release notes.

Thank you team Asobo!

:heart:

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