How do I fly a correct traffic pattern in a simulator?
To fly a correct traffic pattern in a simulator, use the published or ATC-assigned circuit for the active runway, hold the specified height and direction, stabilise speed and spacing on downwind, descend and configure in good time, then turn onto final without rushing. Go around whenever the approach is not stable.
For Aviation & Real-World Flying practice in a flight simulator, traffic pattern and aerodrome circuit describe the same basic visual procedure. At Fly Away Simulation, a mistake we see repeatedly is trying to rescue a poor final when the real error occurred on downwind: excessive speed, incorrect spacing or checks completed too late.
Before take-off: identify the runway, circuit side and height
The correct traffic pattern is the published local circuit or the pattern assigned by ATC, not a universal rectangle flown the same way at every airport.
- Active runway: use the runway assigned by ATC or established by local traffic and procedures. When practising offline, the runway most nearly into wind is normally the starting choice, subject to runway length and published restrictions.
- Circuit direction: confirm left-hand or right-hand traffic. All normal pattern turns are made in that direction unless ATC or a published procedure says otherwise.
- Circuit altitude or height: use the published figure and its stated pressure reference.
- Local restrictions: noise-abatement routes, terrain, parallel runways, gliding and military operations can alter the shape or prohibit turns over particular areas.
- Aircraft data: know the climb, downwind, approach and flap-limiting speeds from the aircraft checklist or operating information.
A METAR helps you identify the wind and local pressure setting, but it does not by itself assign an active runway or tell you the circuit direction. Our guide to extracting wind, pressure and runway information from a METAR explains what to check before starting the circuit.
How do circuit height, altitude, QNH and QFE differ?
Use the pressure reference attached to the published figure; mixing height above the aerodrome with altitude above mean sea level can put the entire pattern at the wrong level.
If a circuit is specified as 1,000 feet above aerodrome level and your altimeter is set to QNH, add the airfield elevation. At a field 500 feet above mean sea level, that gives an indicated circuit altitude of about 1,500 feet. With QFE, where supported and correctly set, the altimeter reads approximately height above the airfield.
If no local data exists and you are conducting offline light-aircraft practice, roughly 800 to 1,000 feet above the airfield is a common training approximation. It is not a worldwide rule and should never replace published information.
How do I fly each traffic pattern leg?
Fly each leg by visual ground track, speed and position rather than treating the circuit as five fixed headings.
- Take off and maintain runway track.
After lift-off, establish the aircraft's climb attitude and speed, correct for crosswind and remain on the extended runway centreline. Do not turn merely because you have passed the runway end; use the safe turning height or local procedure applicable to that airport.
- Turn onto crosswind.
Make a coordinated turn towards the circuit side while continuing the climb. Allow for drift so the crosswind leg follows the intended ground track instead of being blown towards or away from the runway.
- Level at circuit altitude and establish downwind.
Turn parallel to the runway in the opposite direction to landing. Set an appropriate power and downwind speed, level accurately and trim before beginning landing checks. Flying downwind too fast creates most of the workload that appears later.
- Complete checks and judge the spacing.
Use the aircraft's checklist for fuel, mixture, propeller, carburettor heat, fuel pump, harnesses, undercarriage and flaps as applicable. Keep the runway at a repeatable visual distance, but remember that wing references vary between aircraft and are distorted by unusual cockpit camera positions or fields of view.
- Begin the descent abeam the touchdown area.
When abeam the intended touchdown point, or at the point specified by the aircraft procedure, reduce power and begin the descent. Select flap in stages if required, maintain the target speed and retrim after each power or configuration change.
- Turn base using position and wind, not a timer.
The threshold appearing roughly 45 degrees behind the wing is a useful initial cue in many trainers, but it is only a cue. A tailwind on downwind or wind pushing the aircraft towards final requires an earlier turn; wind pushing it away may require a later one.
- Roll onto final close to stable.
Use a coordinated turn and avoid excessive bank close to the ground. Final should begin with the aeroplane close to the correct speed, descent path and landing configuration. If the turn will carry you through the centreline, go around rather than tightening the bank or using inside rudder to skid onto final.
The headings will change with wind even when the rectangular ground track remains correct. A constant heading on every circuit is therefore not evidence of accurate flying.
How big should the traffic pattern be?
The pattern should give your aircraft enough room to descend, configure and make an unhurried base-to-final turn without producing an unnecessarily long final.
A slow trainer can use a relatively compact circuit. A faster single, twin or transport aircraft needs more distance to slow and configure, although published local limits still take priority. If base feels rushed and the turn to final is steep, you are probably too close, too fast or both. If every circuit produces a long, flat, power-on final, downwind is probably too far from the runway or the base turn is too early.
Wind changes the required turn points. With the usual headwind on final, downwind carries a tailwind and the aircraft covers ground quickly, so the base turn often needs to begin earlier. A crosswind on base can either accelerate an overshoot or hold the aircraft away from final. Watch the runway's movement through the windscreen rather than repeating the same turn timing.
Why do simulator pilots overshoot final?
A base-to-final overshoot usually begins with excessive speed, poor downwind spacing, a late base turn or failure to account for crosswind.
| What happens | Likely earlier cause | Correction for the next circuit |
|---|---|---|
| Final is overshot | Late turn, excessive speed or wind pushing along base | Slow and trim earlier; begin the final turn sooner |
| Base turn feels steep and rushed | Downwind too close or aircraft not configured | Allow more spacing and complete checks before descent |
| Final is very long and flat | Downwind too wide or base turned too early | Use a more compact circuit and a later base turn |
| Aircraft arrives high and fast | Descent started late or power reduction delayed | Begin the descent at a consistent visual point |
| Speed varies throughout final | Aircraft was never trimmed after power and flap changes | Set attitude, power and trim after every configuration change |
Do not force alignment with rudder while holding the wings nearly level. That creates a skid and teaches a dangerous habit: in a real aircraft, a skidding turn close to the stall can develop into a spin with almost no height available for recovery.
What does a stable final approach look like?
A stable final has the aircraft configured for landing, close to its target speed, tracking the runway centreline and following a controllable descent path with only small corrections required.
- The landing checklist is complete.
- Flap and undercarriage are set as required.
- Airspeed is within the aircraft's prescribed approach tolerance and not trending away from it.
- The runway remains in a steady position in the windscreen.
- Bank, pitch, power and sink rate are manageable.
- Centreline alignment and crosswind correction are under control.
There is no single stabilisation height or speed tolerance suitable for every light aircraft. Choose a clear short-final decision point before the flight and use the aircraft or operator criteria where provided. Our explanation of judging the runway picture on a visual approach covers the transition from final approach to flare without duplicating the whole circuit.
In wind, correct the ground track on every leg and expect the required heading to change. On final, use the appropriate crab, de-crab or wing-low method; the detailed control sequence is covered in our simulator crosswind landing technique.
When should I go around from the pattern?
Go around as soon as the approach requires large, rushed or unsafe corrections rather than waiting to see whether the landing can still be forced.
Typical triggers include a badly overshot centreline, excessive or decaying speed, unstable sink rate, incorrect configuration, a runway obstruction, conflicting traffic or loss of the required visual reference. A go-around is also the correct response to a bounced or badly misaligned touchdown when a safe landing is no longer assured.
- Apply the aircraft's specified go-around power and control the pitch change.
- Arrest the descent and establish the correct climb attitude and speed while maintaining directional control.
- Retract flap and undercarriage in the prescribed sequence. Do not remove all flap at once while low and slow.
- Follow the published or ATC go-around path. If practising offline without a special procedure, climb safely and re-enter the circuit predictably while checking for traffic.
How should I join a traffic pattern from outside?
Join using the published local method or the route assigned by ATC, while remaining clear of aircraft already established in the pattern.
- 45-degree join to downwind: common at many North American aerodromes, but not a worldwide default.
- Overhead join: specified at some aerodromes so pilots can inspect the runway, traffic and wind before descending to circuit height.
- Crosswind, base or downwind join: acceptable when published or assigned and when it fits safely with existing traffic.
- Straight-in approach: useful in some situations, but it is not a normal circuit entry and must not disrupt aircraft already flying the pattern.
Never cross the active side of the circuit at circuit altitude without a recognised procedure. If no ATC or local method is available in an offline session, use a recognised convention consistently, look for traffic and avoid inventing a route that cuts through base or final.
How can I practise traffic patterns accurately?
Repeat circuits in one forgiving aircraft and change only one variable at a time.
- Start with daylight and light wind.
Learn the visual shape, speeds and workload before adding turbulence or a strong crosswind.
- Use one aircraft and one runway.
Repeatability lets you recognise how power, flap and wind alter the sight picture. Tailwheel aircraft require extra directional-control discipline, described in our taildragger take-off and landing guidance.
- Keep a consistent cockpit view.
Changing seat height or field of view changes where the runway appears against the wing and windscreen, making visual turn cues unreliable.
- Trim after each change.
Continuous control pressure is a warning that the aeroplane is not stabilised and that attention is being taken away from lookout and spacing.
- Use instruments to confirm, not replace, the outside view.
Scan airspeed, altitude and vertical trend, then return outside. A moving map is useful for reviewing the ground track after the circuit, but chasing a rectangular line on the map defeats the visual exercise.
- Review the leg before the visible error.
If final was unstable, inspect downwind speed, spacing, configuration and base timing. Correcting the originating mistake is more useful than practising heroic recoveries close to the runway.