Logan's Runways Were Built for Props. The Near-Miss Was Built Into the Geometry.

Two runways meet at a fixed point on Boston Harbor's edge. That intersection doesn't move. It doesn't adapt to traffic volume. It simply exists — and every aircraft cleared across it is threading the same needle that was cut into landfill decades before jets existed.

Last week, Delta flight crew identified a conflicting ATC clearance that had placed an American Airlines aircraft in their path at Logan's 4R/9 intersection. They rejected it. A collision was avoided. The instinct is to call that heroism — but the more precise word is symptom.

Logan compresses everything. The airport handles over 400 daily movements squeezed into roughly 2.4 square miles on a peninsula that cannot grow outward. Where major hubs use fully parallel runway systems to isolate traffic flows, Logan's intersecting layout forces controllers to sequence aircraft across shared ground paths. There is no geometric workaround. The intersection is structural.

The physics matter here. At taxi speed, two aircraft closing on an intersection might have 30 seconds of reaction time. Once one aircraft begins a takeoff roll, that window collapses toward single digits. ATC decision-making — already managing radio frequency congestion across multiple active surfaces — has to be correct on the first transmission. There is no second look built into the geometry.

FAA runway incursion data bears this out. Intersecting runway configurations account for a disproportionate share of Category A and B events — the classifications where a collision was narrowly avoided or only luck separated the outcome from catastrophe. Procedure upgrades help. Surface radar helps. But they are filters applied to a funnel that was never designed for this throughput.

When pilots catch what the system missed, the system should ask why it needed catching.