Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Breaking pileups on rare DX: split, timing, tailending and low-band tactics for Clipperton and Bouvet-type targets

ci_cover.jpg

A rare-entity pileup rewards good technique and a good station, and technique is the cheaper of the two to improve. I'd like to compare notes on the operating side, using targets like Clipperton and Bouvet as the mental model: remote, logistically hard, usually a short operation, and with a lot of callers chasing a handful of band/mode slots.

Here is a starting framework. Please poke holes in it.

1. Listen before you transmit. Before touching the key or PTT, work out how the operator is running the pileup. Is it split, and by how much? The DX station announces it, for example "up 5 to 10" or "listening up 2", and often the spot comment tells you too, but always verify by ear. Is the operator picking whole callsigns, partial calls, a call area, or a region ("Europe only", "North America")? Is the pace fast, with a rhythm of call, report, next? Or slow, with long searches through noise? If you can't describe the pattern after a minute or two, you aren't ready to call.

2. Set up split properly. Put the DX frequency on VFO A for receive and the listening frequency on VFO B for transmit, and confirm on a dummy load or by watching your rig's display that TX really is where you think it is. Many accidental QRM incidents come from a rig left in simplex, or a split offset applied in the wrong direction. If the DX says "up", you transmit higher than the frequency you're listening on. Also check your transmit bandwidth. A wide SSB signal or heavy processing on a crowded split range makes you more QRM than signal.

3. Find the DX's pattern and call where it's going next. Operators working "up 5 to 10" usually sweep the range. Some stations drift to a clear spot, and some DX operators will tune slowly through the pileup. Rather than sitting on the same crowded frequency, find where callers are thinning out and where the operator's receive pointer seems to be heading. On CW, zero-beating a station that has just been worked is often a bad idea if the operator is only listening in a narrow window. On SSB, small frequency changes matter too, because a few hundred hertz can put you in a quieter pocket.

4. Timing and tailending. Tailending means sending your call as the previous QSO ends, so the DX hears it on the next receive period. It can be effective when the operator is running a fast, disciplined pileup, and it is common on CW. It is bad practice when it cuts off the exchange (before the DX has finished his report or the other station has confirmed) or when you do it to a station that is clearly struggling to copy. Wait for the full sequence to be finished unless the operator is clearly encouraging rapid calls. A related habit is to send your call once or twice, then listen. Constant calling without listening is the classic way to miss the DX saying your call, or to miss that he is now only working a particular continent.

5. Callsign phonetics. Use standard ITU phonetics on SSB for the suffix and keep them consistent. Fancy or humorous phonetics are slower to decode in noise. Say your call once or twice at most, at a steady pace, and then stop. If the DX gets part of your call, send only what is needed to fix it (often the full call again, once), not a long explanation. On CW, send your call without "DE" or extra words, match the operator's speed, and be ready to send it again in a cleaner way when asked for a repeat.

6. Spots and tools. DX Cluster and Reverse Beacon Network spots help you see when an operation is active and which band and mode, but spots can be stale, mislabeled, or wrong about the split. Treat a spot as a prompt to listen, not as proof. Don't spot an entity you haven't copied yourself, and avoid spotting a busted callsign. Club Log is useful on two fronts. The Most Wanted list gives a sense of which entities are in highest demand, and the log search lets you confirm that a QSO is in the log after the operation. When an expedition uses online OQRS, requesting through the official channel and not by email or on the air saves everyone time.

7. Top band and low bands. On 160, 80 and 40 m the limiting factor for the average station is often receive, not transmit power. A signal from a remote island may be buried under local noise, so a separate receiving antenna such as a Beverage, flag, or small loop and a rig with a second receiver can matter more than additional power. Know the grey-line timing for your path. For a place like Bouvet, openings on low bands to many locations may be short, so being ready on the right frequency, with the right split, at sunrise or sunset on both ends is much of the battle. Check the band plan for DX windows on 160 m before you transmit, and don't call outside them for a station that's listening elsewhere.

8. DXpedition considerations behind the pileup. Remote entities such as Clipperton or Bouvet put a lot of constraints on the team: landing permissions, sea conditions, power and antennas, and limited operating days. This shapes what you hear on air. Teams may favor certain bands in certain hours to maximise unique band-slots, run FT8 in a Fox/Hound style, or restrict operation by region to spread QSOs around. If you want to understand why the operator is doing something odd, read the operation's own website and announcements first.

Open questions for the thread. What do you do when a pileup is huge and the DX is working only the stations calling on the exact listening frequency? How do you decide when to stop calling and move to another band? And for the low-band folks, which receiving antennas gave you the best gains on a limited lot, and which were not worth the trouble?

  • Replies 2
  • Views 8
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Good outline. I'd add one point on FT8 and the Fox/Hound mode, because the etiquette is quite different from CW/SSB. In WSJT-X, Hound mode is meant for calling the Fox, and Hounds are supposed to transmit above roughly 1000 Hz while the Fox transmits below it. If you call the Fox on its own frequency you can make it harder for the Fox to decode anyone. Also, once the Fox replies to you, follow the sequence in the software and don't keep calling, as repeated calls waste a slot that another station might have used. If the operation has published instructions, those override general habits, so read them before the first opening.

On spots, the thing to be careful about is the "up" instruction. A busy cluster can carry spot comments that conflict with each other, like "up 1" and "up 5-10". Listen for the DX saying it himself. If he doesn't announce on voice, he'll often tell you in the CW exchange or in the next announcement.

  • Moderators

On tailending, I think the key difference is who benefits. If the operator is running one-hit-and-gone exchanges, a short call timed at the end of the previous QSO is part of how that operation works. If instead you hear a weak station still repeating the exchange, jumping in on top of it only adds a failed QSO for him and delays the next one for everyone. A decent rule of thumb is to wait until you can hear that the previous contact has been confirmed (a "73", "TU" or a clear "QRZ"), then call.

On the low-band question, a receive antenna is often worth more than anything else, but only if the noise you're fighting is local and directional. A Beverage needs space, and a small loop or a pair of verticals may be more realistic on a small lot. Whatever you choose, test it on real signals: compare the S/N ratio, not just the S-meter, between your transmit antenna and the receive antenna on the same station. Sometimes the improvement is large, sometimes it's just a lower signal and lower noise at the same ratio. That test also tells you whether to make split operation easier by using the second receiver on the receive antenna and keeping the main receiver on the DX frequency.

For deciding when to move on: if you've called a reasonable number of times and the operator is working stations well off your pattern (a different call area or a particular suffix), your time is better spent changing something, like frequency, timing, or band, and not repeating the same call.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.