Traffic Patterns at Towered and Non-Towered Airports
A traffic pattern is the standardized, predictable rectangular path aircraft fly around an airport when arriving or departing — and predictability is exactly what makes it useful to a remote pilot. If you know where an aircraft on a given pattern leg is likely to be and where it's headed next, you can plan your own flight path to avoid it, well before any encounter becomes a compliance concern under 14 CFR 107.37 or 107.43. This lesson explains the traffic pattern completely from first principles, with no assumed aviation background, and re-teaches the right-of-way and no-interference rules in the specific context of pattern traffic.
What a traffic pattern actually is
Picture a rectangle drawn in the sky, aligned with the runway, that aircraft fly around in a specific, standardized order every time they arrive at or depart from an airport under normal visual conditions. Instead of every aircraft approaching from a random direction and altitude, the pattern gives every pilot at that airport the same predictable structure to follow, so pilots can find and avoid each other visually without needing to talk to each other constantly (though at a towered airport, they usually do talk to each other — more on that below). The entire point of a standardized pattern is predictability: if you know the pattern's shape, you can generally predict where an arriving or departing aircraft will be next.
The four main legs of the rectangle
The pattern rectangle has four named legs, referenced relative to the runway. The upwind leg runs parallel to the runway, in the same direction as landing traffic would be heading during takeoff (departing the runway). The crosswind leg is flown perpendicular to the runway, connecting the upwind leg to the next leg. The downwind leg runs parallel to the runway again, but in the opposite direction of landing traffic — this is usually the leg where an arriving aircraft spends the most time, flying alongside the runway before turning to land. The base leg is again perpendicular to the runway, connecting downwind to the final approach. Final approach (sometimes just called "final") is the last leg, aligned directly with the runway centerline, leading straight to the threshold for landing.
Standard turn direction: left traffic unless otherwise indicated
By default, traffic pattern turns are made to the left — this is called "left traffic" and is the standard assumption unless an airport specifically indicates otherwise. Some airports use "right traffic" instead (all turns made to the right), usually because of terrain, noise abatement concerns, or another nearby airport's pattern that would otherwise conflict — this is published information specific to that airport and its individual runways, not something a pilot has to guess.
Standard pattern altitude
A commonly used reference altitude for a standard traffic pattern flown by light, propeller-driven general aviation aircraft is roughly 1,000 feet AGL (above ground level, not above sea level — a distinction covered fully in Module 4's chart-reading lessons), though the actual altitude at any specific airport is published for that airport and can vary somewhat, particularly for larger or faster aircraft, which often use a higher pattern altitude. The specific number matters less for a remote pilot than the general concept: pattern traffic concentrates at a relatively low, predictable altitude directly around the airport, which is exactly the altitude band many sUAS operations also occupy.
The standard rectangular traffic pattern: upwind, crosswind, downwind, base, and final approach, with standard left turns.
View LargerTowered airports: ATC sequences and instructs
At a towered airport, an air traffic control tower is staffed and actively directing traffic, including aircraft in the pattern. Pilots communicate directly with the tower controller, who assigns specific instructions — which runway to use, when to enter the pattern, when to turn onto each leg, and when they're cleared to land or take off. The tower's job is to sequence multiple aircraft safely, and pilots are expected to comply with those instructions rather than following the standard pattern on their own initiative.
Non-towered airports: standardized self-announcement and see-and-avoid
At a non-towered airport (sometimes called an uncontrolled airport), there is no staffed control tower, and pilots are responsible for sequencing themselves using standardized procedures and radio self-announcements on a common frequency (covered fully in the next two lessons) combined with visual scanning — often called "see and avoid." A commonly used standard entry procedure at a non-towered airport is a 45-degree entry to the downwind leg: an arriving aircraft flies to a point that lets it join the downwind leg at a 45-degree angle, at pattern altitude, rather than entering the pattern from a random direction or altitude. This standardization exists precisely because there's no controller actively sequencing traffic — the predictability has to come from the pilots themselves following the same expected procedure.
Right-of-way and no-interference, fully re-explained for the pattern context
Recall from the earlier lesson in this module: 14 CFR 107.37(a) requires a small unmanned aircraft to yield the right of way to all aircraft, giving way and not passing over, under, or ahead of another aircraft unless well clear, with no exceptions by aircraft category. 14 CFR 107.43 separately prohibits operating in a way that interferes with airport operations and traffic patterns, even without a specific close encounter. Applied to the traffic pattern specifically: an sUAS operation that flies through, near, or across any of the five pattern legs described above — upwind, crosswind, downwind, base, or final — is operating in exactly the space where manned aircraft are both concentrated and predictable, making both a right-of-way violation and an interference violation significantly more likely if the sUAS operator hasn't identified where that pattern actually is before flying.
Why the entry point itself matters, not just the pattern's shape
The rectangular pattern diagram earlier in this lesson shows the shape traffic follows once established in the pattern, but arriving aircraft don't appear evenly around that rectangle — they converge on it from a specific, standardized point: the 45-degree entry to the midfield downwind leg described above. This matters directly for the 14 CFR 107.37 right-of-way duty just explained. An sUAS operator who has only pictured the rectangle, without picturing where aircraft actually join it, may reasonably but incorrectly assume that a location outside the rectangle itself is automatically clear of traffic. In reality, the airspace along the diagonal entry leg — extending outward from the midpoint of the downwind leg at roughly a 45-degree angle — regularly carries arriving traffic that hasn't yet joined the rectangular pattern shown in the overview diagram, and is just as relevant to 107.37 compliance as the rectangle's own five legs. The entry point is where traffic first converges into the predictable structure the rest of this lesson describes, which makes it one of the highest-value places to account for when planning a flight path near a non-towered runway.
Worked scenario: identifying pattern legs before a mission near a non-towered airport
You're contracted to inspect a cell tower located roughly a half-mile from a non-towered airport's runway. Before launching, you identify the runway's orientation and standard pattern direction (left or right traffic, found on a sectional chart or airport information resource), and mentally sketch where each of the five pattern legs would fall relative to your operating area. If the cell tower sits directly under or near the downwind or base leg, your operation carries meaningfully higher risk of both interference (107.43) and a right-of-way conflict (107.37) than if it sits well clear of every leg — information you can only act on if you've actually identified where the pattern legs are, not just where the runway itself is.
The standard 45-degree entry joins the downwind leg at its midpoint, with arriving traffic converging from this specific direction before ever following the rectangular pattern shape shown earlier.
View Larger
At a towered airport, ATC actively sequences pattern traffic; at a non-towered airport, pilots self-announce and follow standardized entry procedures like the 45-degree downwind entry.
View Larger| Leg | Direction relative to runway | Purpose |
|---|---|---|
| Upwind | Parallel, same direction as landing traffic on departure | Initial climb after takeoff |
| Crosswind | Perpendicular | Connects upwind to downwind |
| Downwind | Parallel, opposite direction of landing traffic | Main leg alongside the runway before turning to land |
| Base | Perpendicular | Connects downwind to final approach |
| Final approach | Aligned with runway centerline | Final leg leading straight to the threshold for landing |
Mapping the Traffic Pattern Before a Mission Near an Airport
Complete this before any mission planned near an active runway, towered or not.
Identify the runway orientation and designator numbers
Determine which direction(s) the runway serves, using a sectional chart or airport information resource.
Confirm the standard pattern direction (left or right traffic)
Check whether the airport uses standard left traffic or a published right-traffic pattern for the relevant runway.
Sketch the five pattern legs relative to your operating area
Mentally or physically map where upwind, crosswind, downwind, base, and final approach would fall relative to your planned flight location.
Note whether the airport is towered or non-towered
This affects whether radio monitoring (covered in the next two lessons) will show you actively controlled traffic or self-announced traffic.
Plan your flight path to stay clear of every identified leg
Adjust your operating area, altitude, or timing so your flight path doesn't cross or approach any of the five pattern legs.
| Mistake | Why it happens | Correct understanding | Regulation / source |
|---|---|---|---|
| Assuming avoiding the runway itself is enough to avoid pattern traffic | The runway is the most visually obvious part of an airport | The downwind and base legs run beside the runway, not over it, and are just as much a part of the traffic pattern. | 14 CFR 107.37, 14 CFR 107.43 |
| Assuming all airports use left traffic | Left traffic is the default assumption when nothing else is specified | Some airports publish right traffic for specific runways; this is airport-specific published information, not a universal rule. | FAA Remote Pilot Study Guide |
| Assuming a non-towered airport has no organized traffic flow because no tower is staffed | "Non-towered" sounds like "unregulated" | Non-towered airports use standardized pattern entry procedures and self-announcement to maintain organized, predictable traffic flow. | FAA Remote Pilot Study Guide |
Is 1,000 feet AGL a fixed, universal traffic pattern altitude?
No. It's a commonly used reference for light, propeller-driven aircraft, but the actual pattern altitude is published per airport and can differ, particularly for larger or faster aircraft. The important concept for a remote pilot is that pattern traffic concentrates at a relatively low altitude near the airport, not the exact number at any one field.
Does a remote pilot need to fly the traffic pattern themselves?
No. sUAS operations don't fly the manned-aircraft traffic pattern. The value of understanding the pattern is predicting where manned aircraft will be, so you can plan your own separate flight path to avoid interfering with them and to satisfy the right-of-way requirement.
Is a 45-degree entry to downwind legally required at every non-towered airport?
It's a widely used, standard procedure rather than a universal legal mandate in every case, but it's the entry pattern a remote pilot should expect to see most often when predicting how arriving traffic will approach a non-towered field.
Test Your Knowledge
Answer the questions below to check your understanding. Every answer can be found in the lesson above.