AFH · AFH Chapter 7

Collision Avoidance in the Traffic Pattern

Master see-and-avoid scanning, right-of-way rules, and pattern communications to prevent midair collisions at towered and non-towered airports. AFH Ch. 7.

CFI's Whiteboard Explanation

The traffic pattern is where airplanes squeeze close together at low altitude — it's where most midairs happen. Three habits keep you alive:

  • Scan in blocks. A plane on a collision course doesn't move on your windscreen, it just grows. Pause your eyes on 10° chunks of sky.
  • Talk like everyone else. Standard CTAF calls: airport, who you are, where, what next, airport again.
  • Clear before every turn. Especially before base-to-final — peek down the extended centerline for that straight-in traffic nobody announced.

Lights on, heads up, and when in doubt, go around.

Handbook Reference
AFH Ch 7

7.collision-avoidance-in-pattern. Collision Avoidance in the Traffic Pattern

The airport traffic pattern is one of the highest-risk environments for midair and near-midair collisions because aircraft of varying performance are converging, climbing, descending, and maneuvering in close proximity at relatively low altitude. Effective collision avoidance in the pattern requires a disciplined combination of see-and-avoid scanning, standardized procedures, clear radio communication, and proper aircraft configuration for visibility.

Regulatory and Procedural Foundation

Under 14 CFR 91.113(b), vigilance must be maintained by each person operating an aircraft so as to see and avoid other aircraft, regardless of whether the operation is conducted under VFR or IFR. Right-of-way rules in the pattern are clear:

  • Aircraft on final approach have right-of-way over aircraft in flight or on the surface.
  • When aircraft of the same category are converging, the aircraft to the right has right-of-way.
  • An aircraft being overtaken has the right-of-way; the overtaking aircraft must alter course to the right.
  • A balloon has right-of-way over all other aircraft, followed by gliders, then airships, then airplanes/rotorcraft.

At non-towered airports, pilots are expected to use the recommended pattern in AC 90-66 and self-announce on the published CTAF.

Visual Scanning Technique

The human eye detects movement more readily than stationary objects, but an aircraft on a collision course will appear motionless against the windscreen — only growing larger. This is the classic constant bearing, decreasing range (CBDR) threat. To counter it:

  • Use the block scan method: divide the windscreen into 10-degree segments and pause the eyes on each block for at least one second to allow the eye to focus.
  • Scan from side to side, slightly above and below the horizon, with emphasis on the area into which the airplane is turning.
  • Move the head to clear behind the wing root and door post blind spots, especially before turning base or final.
  • Recognize that empty-field myopia causes the relaxed eye to focus only 10–30 feet ahead in haze; deliberately focus on a distant object every few seconds.

Pattern-Specific Threats

Each leg of the pattern presents unique conflict geometry:

  • Entry to downwind: Traffic entering at the standard 45° to midfield downwind may converge with aircraft on a midfield crosswind or with aircraft mid-downwind. Always look for traffic on opposing 45° entries from the other side of the field.
  • Crosswind to downwind: Climbing aircraft can be masked beneath the nose; lower the nose periodically to clear.
  • Downwind: Faster traffic may overtake from behind. Scan rearward by S-turning the head before each configuration change.
  • Base leg: The greatest risk is a long straight-in approach merging at the final approach fix. Before turning final, clear the extended centerline by banking momentarily or rolling out wings level to look down the final.
  • Final: Aircraft already on final, including straight-in IFR or NORDO traffic, have priority. Do not cut in front of slower traffic on a longer final.

Communication Best Practices

Clear, standard phraseology reduces ambiguity. At a non-towered field, position reports should include the airport name at the beginning and end of each call, aircraft type and tail number, position, altitude, and intentions:

  • "Smithville traffic, Cessna 12345, entering 45 for left downwind runway 27, Smithville."
  • "Smithville traffic, Cessna 12345, turning left base runway 27, Smithville."

Avoid non-standard calls such as "any traffic in the area please advise," which AIM 4-1-9 specifically discourages. Listen on CTAF for several minutes before entering the pattern to build a mental picture of traffic flow.

Configuration and Visibility

The airplane itself can be configured to be more conspicuous and to give the pilot a better view:

  • Turn on the landing light, taxi light, and any pulsing recognition lights when within 10 NM of the airport.
  • Keep the anti-collision (strobe and beacon) lights on whenever the engine is running.
  • Activate ADS-B Out and monitor traffic via ADS-B In if equipped, but treat it as supplemental — non-equipped aircraft will not appear.
  • Keep the windscreen clean and avoid sunglasses or visors that reduce contrast against haze.

Procedures If a Conflict Develops

If two aircraft find themselves in conflict, the following steps reduce risk:

  1. Maneuver early and visibly — a small turn at distance is far safer than a large evasive maneuver up close.
  2. Climb or turn right as a default avoidance action when no other rule applies (consistent with 91.113).
  3. Communicate position and intent on CTAF or with tower; do not assume the other pilot has seen you.
  4. If on final and a runway incursion or conflicting traffic appears, go around without delay; the missed pattern is preferable to a collision.

Midair collisions in the traffic pattern overwhelmingly involve aircraft converging from blind spots in good VMC during daylight hours. The defense is procedural discipline: fly the published pattern, communicate clearly, scan deliberately, and never let task saturation pull the eyes inside the cockpit during critical legs.

Oral Exam Questions a DPE Might Ask
Q1How do you visually scan for traffic in the pattern, and why does the technique matter?
I use the block scan method — dividing the windscreen into roughly 10° segments and pausing for at least a second on each so my eyes can focus. This matters because an aircraft on a collision course shows constant bearing with decreasing range, meaning it appears stationary on the windscreen and the eye won't pick it up without a deliberate focused scan.
Q2Two aircraft are converging on final at a non-towered airport. Who has the right-of-way?
Per 14 CFR 91.113, the aircraft on final approach has the right-of-way over aircraft on the surface or maneuvering to land. If both are on final, the aircraft at the lower altitude has priority, but the lower aircraft may not cut in front of or overtake another aircraft on final.
Q3What lights and equipment should you use in the pattern to maximize conspicuity?
Anti-collision lights (strobe and beacon) any time the engine is running, and the landing and taxi lights when operating within about 10 NM of the airport — this is the FAA's Operation Lights On recommendation. ADS-B In traffic and any pulsing recognition lights help, but they supplement, not replace, an active visual scan.
Related FAR References
More from AFH Chapter 7
Drill it, not just read it
Adaptive questions on every AFH topic.

Mock checkrides predict your DPE pass rate. Examiner Reed runs full ACS-coverage oral exams — voice-mode included.

5 questions/day free
Collision Avoidance in the Traffic Pattern: AFH Chapter 7 | GroundScholar