A standard traffic pattern exists to make an airport's immediate airspace predictable: every aircraft flying it moves through the same sequence of legs, at the same general altitude, in the same direction, so pilots who can't see each other's flight plan can still build an accurate mental picture of who's where, purely from a standard shape everyone's expected to fly.
Without a shared, expected shape to fly, every aircraft near an airport would be approaching from an unpredictable direction, at an unpredictable altitude, making it far harder for other pilots (and, at towered airports, controllers) to build an accurate picture of traffic. A standard pattern trades a small amount of individual routing efficiency for a large amount of shared predictability, exactly the same tradeoff standard phraseology makes for radio communication.
| Leg | Description |
|---|---|
| Departure | Straight ahead from takeoff, climbing, until reaching pattern altitude or a turn point |
| Crosswind | A turn (typically 90°) away from the runway heading, climbing to pattern altitude |
| Downwind | Parallel to the runway, opposite direction of landing, at pattern altitude |
| Base | A 90° turn from downwind, perpendicular to the runway, beginning descent |
| Final | Aligned with the runway centerline, descending to land |
Flown in sequence, departure into crosswind into downwind into base into final traces a rectangle around the runway, with the runway itself forming one long side of that rectangle.
Pattern altitude for propeller aircraft is commonly 1,000 feet above ground level (AGL) at non-towered airports, though the specific published altitude for a given airport (found in the Chart Supplement) should always take precedence over the generic default, since local terrain, noise abatement, or other traffic patterns can call for a different published altitude.
Standard pattern turns are to the left unless otherwise published, a convention that (among other reasons) matches the traditional left-seat pilot's better visibility of the runway during a left turn. An airport with right traffic for a given runway will note it explicitly, on the sectional chart with an "RP" segmented circle symbol and in the Chart Supplement, and it's usually driven by terrain, noise abatement, or nearby conflicting airspace on the left side.
The standard recommended entry at a non-towered airport is a 45° entry to the downwind leg, at pattern altitude, giving arriving traffic a clear, predictable, and visible way to merge into the existing flow rather than cutting directly across other legs. Overflying the field first, above pattern altitude, to observe the windsock and existing traffic before descending and entering, is standard practice, particularly at an unfamiliar airport.
Each leg has a specific job: crosswind gains altitude to reach pattern altitude before turning downwind; downwind is flown at a consistent distance from the runway (close enough that a total engine failure could still glide to the runway, a real safety consideration, not just tradition) while completing pre-landing checks and configuring; base begins the descent and requires judging the turn to final to avoid overshooting or undershooting the runway centerline; final is flown stabilized, on speed and on the intended touchdown point.
Position reports on CTAF typically happen at predictable points: entering the pattern (often on the 45° to downwind), turning base, and turning final, each stating the airport name, aircraft identification, and position, so other pilots can build a mental picture of the traffic flow purely from those calls (see our Radio Communications guide for the full phraseology pattern).
Maintaining appropriate spacing behind other traffic, extending the downwind, adjusting pattern size, or in some cases making an S-turn on downwind or base, is a routine and expected part of flying a busy pattern safely, not a sign something's gone wrong. The goal is consistent, predictable spacing that gives everyone enough room to complete their own approach without last-second maneuvering.
A go-around, adding power and climbing away rather than continuing an approach that isn't working out, is a completely normal part of pattern operations and should be initiated early and decisively whenever the approach isn't stabilized, spacing behind another aircraft is inadequate, or anything about the landing environment looks wrong. It should be flown back into the same pattern structure (typically climbing straight ahead or along the runway heading before turning crosswind again) rather than improvised.
Arriving at a non-towered airport with published left traffic for runway 27: overfly at 500 ft above pattern altitude to check the windsock and existing traffic, descend on the far side, and enter on the 45° to a left downwind for 27 at pattern altitude, announcing the entry on CTAF. Complete pre-landing checks abeam the numbers, turn base with a call, adjust spacing behind a slower aircraft ahead by extending downwind slightly, turn final with a call, and fly a stabilized approach to landing, ready to go around if spacing or the approach isn't working out.
Want more free guides like this one?
This guide is intended for educational and training purposes only. It is not a substitute for official FAA publications, an authorized ground school, or qualified flight instruction, and should not be used as a sole source for real-world flight planning, dispatch, or operational decisions.