I’m getting across the pond… so why can’t I hear anything back?
If you’ve spent any time on HF digital modes, you’ve probably lived this exact moment.
You call CQ (or answer one), and a minute later PSKReporter (or the WSJT-X “Callers” list) shows your signal being decoded in places you’ve always wanted to reach. You watch your call pop up over the Atlantic (or the far side of an ocean) and you think: “Great — the band is open!”
…and then you look at your own screen (or put on the headphones) and hear… nothing. No return decode. No “RR73.” No weak CW. No SSB. Just a stubbornly empty noise floor.
That’s not bad luck. It’s the core truth of HF DX:
Pushing RF out is often easier than hearing RF come back.
A QSO is not a “who has the stronger signal” contest. It’s a “who has the better signal-to-noise ratio (SNR) at their receiver” contest.
(On modes like FT8, decoding can succeed at very low SNR values. Exact thresholds vary with bandwidth, interference, and the decoder’s state during a QSO.)
So yes: you can absolutely be “heard” (decoded) over the pond while being unable to “hear” (decode/copy) the station that heard you.
Reciprocity: true in the textbook… and easy to misapply on HF
Antenna reciprocity is one of those beautifully clean ideas from theory: the gain, pattern, directivity, and impedance of a passive antenna are the same whether you transmit or receive.
That part is real.
But where many hams get tripped up is the next assumption:
“If my signal is getting there, then I should be able to hear them.”
That leap is where the real world kicks the textbook.
The signal path can be reciprocal while the noise is not
Even if path loss is effectively the same both ways, the noise floor at each end almost never is. One station may be in a quiet rural location; the other may be under power lines, solar inverters, switch-mode supplies, Ethernet hash, and a dozen noisy consumer devices.
The result is one-way “DX” that feels like a reciprocity violation… but it’s really an SNR mismatch.
Why transmit feels easy and receive feels hard on HF
Transmit is mostly an ERP problem
To “be seen” across the pond you need enough effective radiated power (ERP) into the right angles at the right time. You can often brute-force that with:
- modest power
- a reasonable antenna
- a modern mode that can decode weak signals
That’s why people are shocked how far a basic station can “reach.”
Receive is mostly a noise problem
On receive, you don’t get to turn up their power. You’re stuck with:
Readable signal = (signal at your antenna) – (noise at your antenna + noise your station injects)
In many suburban setups, the limiting factor is not receiver sensitivity. It’s local noise and interference, and how efficiently your antenna system delivers that junk into the receiver.
The RX side has two silent killers: pattern and unwanted current
If there’s a single theme that shows up again and again in serious low-band and DX work (ON4UN, W8JI, K9YC, and many others), it’s this:
Your receive performance is usually being limited by what you pick up that you don’t want.
Two concepts matter a lot here: RDF (pattern advantage on receive) and CMRR (immunity to unwanted pickup via feed lines and station wiring).
RDF: why “gain” is often the wrong metric on receive
RDF (Relative/Receiving Directivity Factor) is a figure of merit designed specifically for receiving antennas. It’s essentially about how well the antenna emphasizes the desired direction compared with its average pickup of everything else.
The “aha” moment for many hams is this:
A receive antenna can have terrible absolute gain and still be a killer DX antenna — because if it reduces pickup of noise and QRM more than it reduces the signal, your SNR improves and the DX becomes readable.
That’s why serious low-band stations use antennas that look “inefficient” on paper.
CMRR: when your station is “receiving on the coax” and you don’t even know it
If RDF is about pattern, CMRR is about immunity.
In real HF stations, unwanted current on the outside of coax shields (often lumped under “common-mode,” and frequently driven by imbalance as stray return current) can turn the feed line into an unintended receiving antenna. That picked-up noise can then couple into your receiver and even fill in the nulls of a directional receive antenna.
This is exactly why you can install a “directional” receive antenna and still think it “doesn’t null much” — because the feed line and shack wiring are quietly undoing the pattern.
(If you want the practical version of this problem, the fix is almost always the same: isolate the antenna from the feed line with proper choking and keep noisy wiring out of the antenna system.)
“But my rig is good!” — receiver dynamic range still matters
Even if you solve noise pickup, your receiver still has to survive the real HF environment: strong adjacent signals, broadcast stations, contest pileups, and intermod products.
So “hard to receive” can also mean:
- the band is full of strong nearby signals
- your front end or LO phase noise effectively raises the noise floor (reciprocal mixing)
- the weak DX disappears under a fog of IMD, AGC action, and close-in noise
Why dedicated receive antennas work (and why they’re not “cheating”)
If you read ON4UN’s low-band work, the message is consistent: receiving antennas deserve their own focus — and for good reason. In real DXing, the receive side is often the limiting half of the link.
The classic receive toolbox
When we talk about “receive antennas,” we’re really talking about a few fundamental families:
- Loops (especially small magnetic loops / shielded loops)
- Dipoles (short or full-size, sometimes dedicated RX-only)
- Verticals / whips (often active E-field probes)
- Beverages (and other traveling-wave antennas)
- Terminated compact directionals (EWE/FLAG/Pennant, K9AY, etc.)
- Arrays / phasing systems (to steer lobes and nulls)
A great example of the “compact but directional” category is the K9AY terminated loop — designed specifically as a practical directional receiving antenna system for low-band work in real yards.
What active receive antennas really buy you
An active receive antenna (loop, active dipole, active whip/E-field probe — including RF.Guru’s own range) typically buys you one or more of these advantages:
- Practical placement: small antennas can be placed away from the house and noisy wiring, which can be worth more than any “gain.”
- System-level balance and isolation: good designs prioritize high CMRR so the feed line doesn’t become part of the antenna.
- SNR improvement (not S-meter improvement): the goal is not to make the band louder — it’s to make DX clearer by reducing pickup of everything else.
Explore RF.Guru receive antennas
Looking for practical ways to improve SNR in real noise environments? Browse our RF.Guru active RX antenna collection, and if you want the deep-dive data, start with the technical overviews below:
- Octaloop 1.2 m active magnetic loop: technical overview
- SkyTracer active E-dipole: technical overview
- EchoTracer active E-field probe: technical overview
- VerticalVortex active vertical/whip: technical overview
- TerraBooster Mini/Medi/Maxi/Xtreme: technical overview
- PulseRoot active Beverage RX system: technical overview (beta)
Interested in steerable receive patterns and deeper nulls? Our phased receive arrays are still in development, but you can already read about the design philosophy here: Clever phasing: why we chose these arrays.
(Active RX antennas are not about making the band “louder”... they’re about improving SNR through placement, isolation, and controlled pickup.)
Putting it all together: why you get spotted but don’t copy
When your FT8 signal gets decoded over the pond, that tells you:
- propagation supports the path (at least one-way, at least some of the time)
- your transmit ERP is adequate
- the other station (or a remote receiver site) has enough SNR to decode you
When you can’t decode them back, it often means:
- your local noise floor is higher than theirs
- your antenna system is coupling local noise (feed line pickup, imbalance-driven stray return current, station wiring)
- your receive pattern isn’t helping (low RDF for your noise situation)
- your receiver is being desensed by strong adjacent signals (dynamic range / reciprocal mixing)
None of that violates reciprocity. It just means receiving is the harder half of the link.
The uncomfortable (and useful) conclusion
If you want more DX in the log, you can’t only build a station that “gets out.”
You need a station that hears.
If your signal is already popping over the pond, you’ve proven the transmit side is working.
Now you’re at the real DX upgrade point: lower the noise, improve RDF where it matters, and protect the system with high CMRR.
That’s when the pond stops being one-way.
Mini-FAQ
- Why can I be decoded overseas but not decode them back? Because the other station’s receive SNR is good enough to decode you, while your local noise floor (or desense) may be too high to decode them.
- Doesn’t reciprocity guarantee “if I get out, I should hear them”? Reciprocity applies to passive antenna behavior, but your QSO success is dominated by SNR... and noise is local and rarely equal at both ends.
- What matters more on receive: gain or noise rejection? Most of the time, noise rejection. If an antenna reduces noise pickup more than it reduces the desired signal, your SNR improves and DX becomes readable.
- What is RDF in plain terms? A receive-focused way to describe how strongly an antenna favors the desired direction compared to its average pickup of everything else.
- How does the coax make my receive worse? If the feed line and shack wiring pick up noise and couple it into the receiver, it can raise your noise floor and even “fill in” the nulls of directional receive antennas.
- What’s the fastest practical upgrade for better RX? Improve isolation and placement: add effective feed line choking where it matters, and place a dedicated receive antenna away from the house and noisy wiring when possible.
Interested in more technical content? Subscribe to our updates for deep-dive RF articles and lab notes.
Questions or experiences to share? Feel free to contact RF.Guru via our RF.Guru contact page for technical questions and support.