Aviation & Real-World Flying 6 min read

How do I follow ATC landing instructions in a flight simulator?

Ian Stephens
In short

Learn how to follow ATC landing instructions in a flight simulator, from vectors and descent clearances to final approach, landing and go-around.

To follow ATC landing instructions in a flight simulator, read back the assigned runway, heading, altitude and approach; fly each clearance exactly; configure before final; and distinguish an approach clearance from permission to land. If the approach becomes unstable, the runway is occupied or landing clearance never arrives, go around.

In aviation and real-world flying, ATC controls traffic sequencing while the pilot remains responsible for flying safely. Built-in simulator ATC follows the same broad pattern, although its vectors and descent timing can be imperfect. Our overview of how simulator ATC sequences an arrival and hands it between controllers explains the wider system.

What do ATC landing instructions mean?

ATC arrival instructions are separate clearances, and each one authorises a specific action rather than the entire landing.

ATC instructionWhat you should do
Fly heading 240Turn to and maintain magnetic heading 240 until given another heading or navigation clearance.
Descend and maintain 3,000 feetDescend to 3,000 feet and level off there. Do not continue down merely because the runway is visible.
Expect ILS runway 27Prepare that approach, but do not treat “expect” as clearance to fly it.
Cleared ILS runway 27Intercept and fly the ILS subject to any altitude restriction. This is not permission to land.
ContinueContinue the approach while ATC resolves traffic. You still need landing clearance before touchdown.
Cleared to land runway 27Land on runway 27 if the approach and runway remain safe.

How do I follow the clearance from arrival to touchdown?

Handle the arrival in a fixed order so that radio work does not overtake aircraft control.

  1. Copy and acknowledge the clearance. Note the runway, approach type, heading, altitude, speed restriction and next frequency. With menu-based ATC, selecting the correct response normally generates the readback; with voice ATC, repeat the safety-critical details and your callsign.
  2. Prepare the approach. Load the correct runway and transition, set the altimeter pressure, tune and identify any required navigation aid, set the inbound course and review the missed approach. Confirm that the loaded procedure matches the runway ATC assigned.
  3. Fly the latest heading and altitude. Set the heading and altitude selectors, choose the appropriate autopilot mode, and verify the flight mode annunciator. Turning the heading knob does nothing if NAV remains active, while setting a lower altitude does not guarantee that a descent mode has engaged.
  4. Reduce speed and configure in stages. Use flap and landing gear within their permitted speed ranges. Aim to reach final already established, on speed and largely configured rather than making large changes close to the runway.
  5. Intercept the cleared approach. For an ILS, approach the localiser at a manageable angle and capture the glideslope from below. For RNAV, verify the active waypoint, GPS navigation source and leg sequencing. For a visual approach, keep the runway in sight and fly a stable visual path.
  6. Contact tower when instructed. Change frequency, report as requested and listen for your runway and callsign. Do not switch early, because the approach controller may still have another vector, altitude or speed instruction.
  7. Land only when cleared. A clearance for an ILS, RNAV or visual approach authorises the approach, not the touchdown. Confirm the runway is correct and unobstructed even after receiving “cleared to land”.

When am I allowed to descend on the approach?

Descend only when ATC has issued a descent clearance or when you are established on a cleared published approach and its procedure permits further descent.

A moving glideslope indicator is not, by itself, permission to descend. If ATC says “maintain 3,000 until established, cleared ILS”, remain at 3,000 until established, then follow the glideslope unless another restriction applies. If you intercept from above, do not force a steep descent to catch it; request another vector or go around.

Regional phraseology and published procedures differ, so obey explicit altitude restrictions over any general rule. For the cockpit side of an instrument arrival, our guide shows how to turn an FSX ILS clearance into localiser and glideslope tracking.

What changes for a visual approach?

A visual approach replaces much of the instrument procedure with visual positioning, but it does not remove ATC control or the requirement for landing clearance.

Report the runway or relevant traffic in sight when requested, maintain visual reference and turn onto a sensible final rather than aiming directly at the threshold from an awkward angle. Use our explanation of visual approach alignment, speed control and go-around criteria for the flying technique.

Why is the aircraft not following the ATC vector?

The usual cause is an incorrect autopilot mode rather than a faulty ATC instruction.

  • Wrong lateral mode: select HDG for radar vectors. Do not expect NAV or LNAV to follow a heading clearance.
  • Wrong vertical mode: setting an altitude is only the target. Engage an appropriate descent mode and manage thrust so the aircraft can reach it.
  • Approach mode armed too early: arm APR when positioned for a proper intercept, normally from below the glideslope. An approach capture from above is unreliable and often produces an unstable descent.
  • Incorrect runway or frequency: a late runway change requires the approach, navigation frequency and course to be checked again.
  • Conflicting automation: an AI radio assistant or co-pilot may acknowledge instructions or alter frequencies without making the corresponding cockpit changes.

What if simulator ATC gives a bad or late instruction?

Do not dive, overspeed or make an extreme turn merely to satisfy faulty or late simulator ATC.

With a human controller, request clarification, another vector or say “unable” when the aircraft cannot safely comply. Built-in ATC may occasionally leave an aircraft too high, vector it through final or delay the approach clearance. Maintain control, continue at the last valid altitude and heading where practical, or abandon the approach and reposition.

A useful simulator target is to be on the correct path, at the planned speed and in landing configuration by about 1,000 feet above the runway in instrument conditions or 500 feet in visual conditions. These are common stable-approach gates rather than universal limits; aircraft and operator procedures take precedence.

When should I go around?

Go around whenever the approach is unstable, the runway is occupied, visual reference is lost when required, or landing clearance has not arrived before touchdown.

Apply go-around thrust, control pitch, retract drag devices in the correct sequence and fly the published missed approach or the heading and altitude assigned by ATC. Announce the go-around when workload permits. Aviating comes before finding the correct ATC menu option.

What happens after landing?

After touchdown, slow under control, vacate at a suitable taxiway and contact ground only when tower instructs you to do so.

Do not stop on the active runway to change frequencies or manipulate the flight-management system. Once clear, cross the holding line completely, stop if necessary and copy the taxi route. Our guidance on braking, runway exit and safe post-landing control covers that final phase.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members