🚁 Potomac River Midair Collision

Separate frequencies can be workable in routine operations, but they remove a key safety layer when a conflict is developing: shared party-line awareness. When two aircraft can't hear each other's transmissions, each crew loses cues that would normally help them build the same mental picture.

• Loss of mutual situational awareness. Crews can't hear the other aircraft's readbacks, intentions, or uncertainty — the "background context" that often triggers earlier scanning and self-correction.
• Controller becomes the single point of truth. If the controller's workload spikes or a transmission is missed, there's no redundant "overhear" safety net from the shared frequency.
• Higher chance of instruction mismatch. When one side can't hear the other side's conversation, an instruction can be interpreted without the context that would normally constrain misinterpretation.
• Harder to recover from missed words. If a critical phrase is blocked or stepped-on, the aircraft that missed it won't realize it missed something — because it can't hear the other side's reactions.

Stepped-on audio isn't just an annoyance — it's a failure mode where your most important content can vanish while everything still sounds "normal" to the sender. In a seconds-to-impact scenario, there may be no second chance to restate it.

• Critical content can be selectively lost. The first half of a transmission ("pass behind…") can disappear while the rest is heard, creating a dangerous partial message.
• The receiver may not know it missed anything. Without clear garble cues, the aircraft may respond confidently while operating on incomplete instruction.
• Immediate confirmation becomes mandatory. In time-critical conflicts, controllers/dispatchers must force a readback of the operative words, not just a generic "traffic in sight."
• Workflow should assume the radio can fail. If the situation is collapsing, back-up actions (repeat, verify, use alternate phrasing, direct immediate maneuver) must happen without delay.

"In sight" is a data point, not a solution. Visual separation still requires correct identification, correct geometry, and correct maneuvering — and it can degrade quickly at night, low altitude, and high closure rates.

• Misidentification risk. "In sight" can mean the crew sees a light or aircraft but not the correct one, or sees it without understanding its flight path change (e.g., circling-to-final).
• Geometry can change faster than cognition. Even correctly identified traffic can move from safe to fatal within seconds during turns-to-final and river-route transitions.
• Requires an explicit avoidance plan. Visual separation must be paired with a clear directive ("pass behind," "move left to east bank," "maintain route altitude") and verified compliance.
• Night + low altitude reduce error margin. There's little vertical room to create separation, and collision-avoidance systems have limitations near the ground.

Altitude deviations in a low-altitude corridor collapse the only separation that might exist. When an approach path and a helicopter route occupy the same slice of air, small deviations become catastrophic because there's no time or vertical space to fix them.

• Separation margin becomes single-digit seconds. An extra 50–150 feet can move a helicopter into the same altitude band as an aircraft on final.
• Controllers lose predictability. Route altitudes only protect you if they are reliably flown. Deviations turn "expected safe" into "unknown risk" with no warning.
• Late alerts are too late. Conflict alerts and traffic advisories can trigger when the geometry is already unrecoverable at low altitude.
• Dispatch language must tighten. When altitude is life-critical, instructions must be explicit, verified, and corrected immediately when uncertain ("maintain 200 ft," "verify altitude," "turn now").