Find why flight simulator ATC won’t clear you to descend or land, then fix IFR plans, frequencies, hand-offs, approach sequencing and tower contact.
In flight simulators, ATC usually withholds descent or landing clearance because the IFR plan is not active, a frequency hand-off was missed, the destination is uncontrolled, or ATC has lost the route sequence. It may also wait beyond the aircraft’s computed top of descent; that marker does not trigger a clearance.
Why won’t ATC clear me to descend at top of descent?
The top-of-descent marker is an aircraft navigation calculation, not an ATC command. Your flight management system calculates where an efficient descent should begin, while built-in ATC uses its own route, altitude and traffic logic. The two often disagree.
Under IFR, remain at the assigned altitude until ATC gives a lower altitude or clears the approach. If the simulator offers a request for a lower altitude, use it before passing the calculated descent point. A late clearance may require speed brakes, extra track miles or a go-around; trying to rescue the approach with an unsafe dive is the wrong response.
VFR works differently. A VFR aircraft normally manages its own descent unless ATC has assigned an altitude restriction, although it still needs landing clearance at a towered airport. Our explanation of the complete simulator IFR sequence from clearance to landing covers when altitude, approach and landing clearances should occur.
Why am I not getting landing clearance?
Only the tower at a controlled airport can clear an aircraft to land. Approach control can vector you, assign an altitude and clear an instrument or visual approach, but none of those messages is permission to touch down.
Complete the hand-off to tower and check in on the assigned frequency. Merely tuning the frequency is not always enough: many built-in ATC systems require the corresponding contact or acknowledgement option before advancing to the next stage.
At an uncontrolled airport, there is no landing clearance to receive. Use the airport’s advisory frequency or the simulator’s position-announcement options, check the runway and traffic yourself, and land when safe. If a controller says continue approach, you are also not yet cleared to land.
A landing clearance may arrive on short final because traffic is still departing or vacating the runway. For realistic operation, go around rather than cross the threshold without clearance. Add-on scenery can create another mismatch: the visible runway number or tower service may differ from the airport information known to the simulator’s ATC database.
What should I check before assuming ATC is broken?
Check flight rules, clearance status, radio state, hand-offs and route synchronisation in that order.
- Confirm the flight rules. Make sure an IFR plan was filed and accepted if you expect controlled descents and an instrument approach. Filing a route is not always the same as requesting and receiving IFR clearance.
- Review the last exchange. An unacknowledged altitude, runway assignment or frequency change can stop the dialogue. If radio assistance is enabled, verify that it actually sent the response.
- Check the active COM radio. The assigned frequency must be active rather than sitting in standby, and it must be entered in a COM radio rather than a NAV receiver.
- Complete every hand-off. Contact the new centre, approach or tower controller when instructed. Waiting on the old frequency is one of the most common causes of missing descent and landing options.
- Compare the ATC route with the cockpit route. A direct-to, deleted waypoint or newly selected approach entered only in the FMS may not update the plan tracked by built-in ATC. Resolve any route discontinuity and, where necessary, amend or refile the simulator’s ATC plan.
- Verify the destination service. Check whether the airport is actually towered and whether the selected runway and approach exist in the simulator’s airport data.
- Allow for traffic sequencing. ATC may delay descent, extend the downwind or withhold landing clearance while another aircraft occupies the runway.
What do the different ATC clearances permit?
A descent clearance, approach clearance and landing clearance authorise different parts of the arrival.
| ATC message | What it means | Common mistake |
|---|---|---|
Descend and maintain… | Leave the previous assigned altitude and descend to the stated altitude. | Following the FMS profile instead of the cleared altitude. |
Cleared for the approach | Fly the specified approach and follow its applicable vertical profile once properly established. | Treating approach clearance as permission to land. |
Contact tower | Change frequency and report to the tower controller. | Tuning tower but failing to make contact. |
Report runway in sight | Tell ATC when the runway is genuinely visible so a visual approach can be issued. | Ignoring the prompt and waiting for the sequence to continue automatically. |
Cleared to land | Permission to land on the specifically named runway. | Assuming an earlier runway assignment was landing clearance. |
Do different flight simulators handle ATC differently?
Yes; each simulator’s built-in ATC tracks flight plans and radio exchanges differently.
- Microsoft Flight Simulator: ATC generally follows the simulator’s planned route, while edits made solely in sophisticated aircraft avionics may not fully resynchronise with it. Check the planner, IFR status, hand-offs and radio assistance using our Microsoft Flight Simulator ATC setup and troubleshooting steps.
- X-Plane 12: Filing the route, receiving clearance, making the required readbacks and completing hand-offs all affect the sequence. Late descents and runway changes are covered in our X-Plane 12 ATC workflow.
- FSX: Stock ATC follows the active simulator flight plan and the airport communications data. Cockpit route changes, a missing tower frequency or an add-on conflict can interrupt vectors and landing clearance; use these FSX-specific flight-plan, radio and airport checks.
What should I do if ATC still gives no clearance?
Treat an unrecoverable ATC failure as a simulator fault, not permission to descend or land. First request a lower altitude or approach if that option exists, repeat the expected controller contact, and confirm that the flight has not silently reverted from IFR to VFR.
If the ATC state remains stuck, the practical simulator-only choices are to go around, cancel IFR and continue under appropriate VFR conditions, refile the route, or restart the flight. Cancelling IFR merely to bypass a broken controller sacrifices realistic separation and procedure handling; it is a workaround, not normal aviation practice.