Est.

Midair Collision Risk at Non-Towered Airports

Pattern geometry, blind spots, and missing coordination explain why.

· 9 min read · Updated
Cover illustration for “Midair Collision Risk at Non-Towered Airports”
Airport Safety · September 30, 2026 · 9 min read · 2,104 words

The most dangerous airspace in the United States is the rectangle of sky directly around a small airport, the traffic pattern, where airplanes descend, turn, slow down, and converge on the same runway from different directions at the same time. That convergence is the single location in the National Airspace System where the structural conditions for a midair collision come together most reliably. AOPA Air Safety Foundation data show that 45 percent of all midair collisions happen in the traffic pattern, and two-thirds of those occur during approach and landing, on final or directly over the runway. The numbers point to a specific phase of flight, a specific altitude band, and a specific set of maneuvers, repeated at thousands of airports every day. Understanding why that patch of airspace carries so much risk means looking first at its shape, then at the eyes trying to navigate it, and finally at what is missing to help those eyes succeed.

Most midair collisions happen in the traffic pattern because that is where several airplanes descend, slow down, and converge on one runway with no one assigning them a sequence. AOPA data show 45 percent of midair collisions occur in the pattern, and two-thirds of those happen on final or over the runway. The base-to-final turn is the worst moment: the pilot is rolling out of a bank, losing altitude, and splitting attention between the runway and the cockpit, which leaves the narrowest window for scanning outward. Blind spots and the rear-closure problem make it worse, since 82 percent of collisions happen from behind, the direction pilots are least likely to be looking.

Why do most midair collisions happen in the traffic pattern, and what makes the base-to-final turn so dangerous?

A standard traffic pattern asks several aircraft to fly the same rectangular path around a runway, descending through downwind, base, and final, all while merging toward one point in space. Fixed-wing aircraft generally follow this shape, but helicopters often fly a lower, tighter pattern on the opposite side of the runway, and gliders follow a geometry suited to their own descent profile. Several valid pattern types can be active over the same runway at the same time, with no outside authority assigning each one a lane or a sequence. The highest-risk moment in that shape is the turn from base to final: an aircraft is rolling out of a bank, losing altitude, and splitting attention between the runway picture outside and the instruments inside, which leaves the narrowest possible window for scanning outward. Sequencing confusion, disagreements or misunderstandings about who is landing first, tends to start earlier in the pattern on downwind or base, but it comes to a head, for better or worse, on final. Speed differences make the geometry worse rather than better: a faster airplane closing on a slower one ahead of it in the pattern can produce a closure rate that outpaces what a human scan can pick up and react to in time. Most tellingly, AOPA's data show that 82 percent of collisions happen from the rear, the one direction pilots are least likely to be looking. The overtaking scenario built into pattern geometry is structurally hard to detect before it becomes a collision. None of this requires a pilot to make a mistake. It only requires the pattern to be flown as designed, by more than one airplane, at once.

Diagram: Where Pattern Collisions Cluster: By Phase of Flight. Visualizes: Show how midair collision risk concentrates within the traffic pattern by phase of flight.

How visual blind spots make self-separation structurally unreliable

Pattern geometry explains where the risk concentrates. The physical design of the aircraft flying through it explains why even a careful, well-trained pilot can fail to see the airplane that is about to hit them. A low-wing airplane descending from above and a high-wing airplane already established in the pattern below form a textbook blind-spot pairing: the descending airplane's wing blocks the view of traffic underneath it, and the established airplane's wing blocks the view of traffic above it, so neither pilot sees the other until they are already too close to separate safely. It is a mechanical consequence of how airplanes are built, and no amount of scanning habit removes it. AOPA's own guidance recommends banking periodically to clear blind spots and checking behind and below while on final, but those are maneuvers that require breaking the scan away from the direction of travel at precisely the moment workload is highest. Compounding the blind-spot problem is a separate quirk of human vision: an airplane on a true collision course does not appear to move across the windscreen. It only grows larger, slowly, with no lateral motion to catch the eye, which makes it easy to miss entirely during the demands of approach and landing. Two documented near-midair-collision reports illustrate how this plays out in practice, discussed in the sections that follow, where instructors and captains alike describe aircraft that were simply never seen until evasive action became the only option. The task of self-separation, by eye alone, asks the human visual system to do something it is not built to do reliably, in the exact phase of flight where the cost of failure is highest.

The structural root of the problem: absence of external coordination

At a towered airport, a controller holds the whole picture, sequencing traffic, resolving conflicts, and issuing instructions that remove the guesswork pilots would otherwise face. At a non-towered airport, that role simply does not exist. Every pilot in the pattern is flying the airplane, navigating, talking on the radio, and scanning for traffic at the same time, often with only a partial and uncertain picture of who else is out there. The Common Traffic Advisory Frequency system, where pilots announce their own position and intentions, is the only coordination mechanism available, and it carries limits that cannot be engineered away. Aircraft without radios are legal to operate in the pattern, and no other pilot can know one is there until it is seen. A pilot might transmit on the wrong frequency, use a non-standard call, or simply say nothing, and nothing in the system catches the omission. A radio call describes where a pilot believes they are, which does not always match where the airplane actually is relative to everyone else. The collision-avoidance technology that protects airline passengers does not help here either. TCAS II, the certified system airliners carry, is largely absent from the light aircraft that make up most pattern traffic, and even when it is present, it suppresses resolution advisories below roughly 1,000 feet above ground level because commanding a descent that close to the ground is itself dangerous. Research from the PCAS project identifies this as the central technical gap: pattern altitude is exactly the altitude band where TCAS II goes quiet, so the phase of flight with the highest collision risk is also the one phase flying without any automated warning. The NASA ASRS dataset captures what the absence of coordination produces in practice: in June 2026, an air carrier captain approaching an airport after the tower had closed reported a near-midair collision on an approach path opposite a non-communicating aircraft. It was to extend the tower's hours of operation. That instinct, coming from a professional flight crew in the moment after a near-collision, points to where the real fix lies: not in asking pilots to separate themselves more carefully, but in restoring the coordination that disappeared when the tower went dark.

ATC-zero events and the boundary between controlled and uncontrolled airspace

It can shift without warning. In each case, any aircraft already in the pattern or on approach under the assumption that a controller was watching lost that coordination mid-operation, with no notice. The FAA's 2026-2028 Workforce Plan lowered its own certified controller staffing target from 14,633 to 12,563, attributing the change to modern staffing models, a revision that critics have read as adjusting the benchmark to match the shortage rather than closing it. Read that way, the 334 ATC-zero events are not a string of isolated failures. They are evidence of a system under sustained pressure, where the boundary between controlled and non-towered airspace is set less by the design of the airspace than by whether enough controllers show up to staff it on a given day. The pool of effectively non-towered airports, in other words, is not fixed. It grows every time a tower goes dark.

Limits of the Per-Airport Collision Data

A 2026 analysis published under the title "Are Non-Towered Airports Safe? The Data Says Yes," written by Mariah Aguilar of West Houston Airport, found that towered airports recorded roughly 41 times more midair collisions per airport than non-towered airports over a ten-year period, once the counts were normalized by number of facilities. On its face, that number seems to invert everything argued above. It deserves to be taken seriously rather than waved off, and the analysis itself is transparent about what it can and cannot show. It normalizes by the number of airport facilities, not by the number of flights that actually pass through them. Towered airports handle far more aircraft movements than non-towered ones, so comparing raw collision counts facility-by-facility measures how many collisions happen per building, not per flight. The analysis acknowledges that limitation openly rather than claiming to resolve it. What the comparison would need to settle the safety question is a per-operation denominator, the number of collisions divided by the number of actual flights at each airport type, and neither Aguilar's analysis nor any publicly available dataset in the current research supplies that figure. Without it, there is no way to say whether a given flight at a non-towered airport carries a higher or lower collision risk than the same flight at a towered one. The AOPA and NTSB pattern data take on a different question entirely, one the per-airport comparison was never built to answer: where, geographically and procedurally, collision risk concentrates within the system as a whole. That question has an answer that holds regardless of how the facility-normalization debate gets resolved: the traffic pattern at non-towered airports, and specifically the approach and landing phase within it.

Who bears the risk at non-towered airports

The risk inside that pattern does not fall evenly across the pilot population. It concentrates heavily among student pilots, flight instructors, and low-experience aviators, because non-towered airports are overwhelmingly where primary flight training happens. One instructor reported a near-midair collision on approach to GDK, a non-towered airport, that required evasive action to avoid impact. The concentration of training activity at these airports means the pilots most often in the pattern are, on average, the ones with the least experience scanning for traffic, the least automatic command of cockpit workload, and the least spare attention to devote to threat detection while they are still learning to fly the airplane itself. A separate group faces a related but distinct exposure: instrument-rated crews flying under IFR into non-towered fields. The risk inside the non-towered environment is concentrated in the training environment and in the gap between instrument procedures and visual self-separation, making the exposure systemic rather than incidental.

Why traditional manned towers cannot close the coverage gap at small airports

If the traffic pattern at non-towered airports carries this much concentrated risk, the obvious answer would seem to be building more towers. The airports where this risk is worst are, with rare exception, the ones least able to pay for that answer. The coverage gap is a product of economics rather than oversight. Johnston Regional Airport in Smithfield, North Carolina, and Raleigh Executive Jetport have both secured FAA approval to build air traffic control towers, at an estimated cost of between $10 million and $20 million apiece, with much of that cost falling to taxpayers. Airports at this scale depend on FAA Airport Improvement Program grants for most of the capital they have access to at all, which ties any major infrastructure project to the timing of federal appropriations and the outcome of competitive grant cycles rather than to local need or local funding. The FAA's own multi-year nationwide airport planning assessment puts total airport development needs nationwide in the tens of billions of dollars, a figure that places the cost of a single small-airport tower in the context of a funding system already stretched across far more demand than it can meet. A conventional staffed tower, at $10 million to $20 million per facility, is simply not a solution that scales to the thousands of non-towered airports where the pattern risk described throughout this piece plays out every day. The gap between where the risk concentrates and where the money to staff a tower exists is the baseline condition that any real fix has to work within.

Sources

  1. GitHub - basharfkhan/pcas: Predictive Collision Awareness System: learned conflict warning for non-towered airports, where TCAS is inhibited and most midairs happen · GitHub
  2. ASRS Database Report Set Non-Tower Airport Incidents
  3. U.S. Department of Transportation Federal Aviation Administration Advisory
  4. COLLISION AVOIDANCE AT NONTOWERED AIRPORTS Teresa Ann Sloan
  5. Reducing the collision risk around non-towered airports | ATSB
  6. Mid-Air Collision Risk and Areas of High Benefit for Traffic ...
Filed underAirport Safety

More in Airport Safety