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 what changes on the low bands

ci_cover.jpg

Rare-entity operations like Clipperton or Bouvet-type targets are a good stress test of pileup technique. Operating windows are limited, the path may be marginal, and thousands of stations want the same few contacts. Most failed attempts come down to a few avoidable mistakes, not a lack of power. This thread is for comparing methods, so here is a starting framework to argue with.

1. Listen before you transmit. Spend a few minutes just listening. Work out how the operator is picking callers. Is it by call area, by suffix, by 'last two letters', or by taking whoever is loudest? Note how fast the rate is and whether they are working split. If the operator says 'up', 'up 2', or 'listening 5 to 10 up', that is where you call, not on the DX's own frequency. Calling on the DX's transmit frequency while they are working split is the quickest way to get ignored and to annoy everyone around you.

2. Set up split properly. Use the two-VFO split function of the radio, not RIT, which doesn't give you enough range. Put the receive VFO on the DX and the transmit VFO in the listening range. Check which VFO is which before you key up. A wrong split setting means you transmit on the DX's frequency and cause QRM. Many rigs also let you see the transmit frequency on a second display, so use it. After each call, check the DX's receive pattern: are they picking stations at one edge of the range, or moving up and down? If so, adjust your transmit frequency to match instead of repeating the same call on the same spot.

3. Timing and tailending. The key skill is calling when the DX is listening, not while they are still transmitting. On CW, tailending, meaning sending your call as the previous QSO ends, is widely used because the operator is about to listen anyway. It is often less welcome on SSB, where it can step on the other station's final 'thanks' or 73. Whether tailending is acceptable depends on mode and on how the operator runs the pileup. If the DX operator says 'QRZ' and waits, tailending is not needed. Short and well-timed calls usually beat long ones.

4. Your call and phonetics. Send your callsign once or twice at most, using standard ITU phonetics on SSB (or the plain letters if the DX is struggling). Skip extras like 'this is' or 'please'. If the operator copies part of your call (say 'W1?'), reply with your full callsign once, not just the missing letters, because they may have lost track of the exact sequence. Don't send your call repeatedly while the DX is already responding to someone else.

5. Using the DX cluster and Club Log. Spots tell you where to listen, but treat them as hints. A spot can be wrong, outdated, or a busted call. Confirm that the station you hear matches the callsign before you join the pileup. Club Log is also useful: its Most Wanted lists give a sense of how sought-after an entity is, and many expeditions upload logs and offer OQRS through it. Wait for the log to update before you check whether you are in it, and avoid calling again just because it hasn't appeared yet.

6. Pileup etiquette. Don't tune up on the DX's frequency, don't ask 'what's the frequency?' on the air, and don't answer the DX's questions to other stations. Avoid policing the band. A short, polite 'frequency in use?' on a clear spot is fine, but a running commentary just adds QRM. Operators often respond faster to callers who plainly follow the instructions.

7. Low-band and top-band work. On 160, 80 and 40 metres, the main difference is that the path and your receive ability matter more than your transmit power. Noise, atmospherics and a limited receive antenna often decide whether you hear the DX at all. If you can, use a dedicated receive antenna such as a Beverage, loop or flag. Grey-line timing, where the path crosses sunrise or sunset, tends to produce the best openings, and geomagnetic conditions can make or break them. DX stations on the low bands often have weak receive conditions too, so call less often and wait for them to finish.

8. Planning around a rare entity. For Clipperton and Bouvet-type targets, remoteness and weather mean an operation can be short or end early, so plan your efforts around the band and mode where you have the best chance. Use propagation prediction software to see when your path might open, and confirm whether short or long path applies. Set a cluster alert for the callsign so you don't have to monitor constantly. When the DX is on, log your contact quickly and don't try to confirm the same band and mode more than once unless you're asked to.

What techniques do you rely on that aren't covered here? And where do people disagree on tailending, calling zones or how DX operators should run split?

  • Replies 2
  • Views 8
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One point I'd add on timing is that it helps to learn the operator's cadence. Some work in tight cycles: they send their call, listen for a second, then pick a station. Others keep the transmissions longer and listen in short windows. Match your call to the gap. If you call on top of the DX's own transmission, there is no chance of being heard, however strong your signal is.

On the debate about calling on the exact spot that was used last: many operators avoid it because the person calling right on top of a strong signal gets copied. But being on the crowd's centre frequency with everyone else is a gamble. A small shift, within the stated listening range, can sometimes help, especially if the operator is working outward from a certain point. Don't wander outside the announced range, though, because that spreads the pileup and causes QRM on neighbouring frequencies.

On the digital side, if the DX uses the FT8 Fox and Hound mode in WSJT-X, follow the specific instructions. As a hound, you generally call above a certain frequency (commonly around 1000 Hz) and wait until the Fox answers. Calling in the Fox's own range just causes mutual interference. Check the operation's own web page for the exact rules because they can vary.

  • Moderators

On the low bands, I'd stress that the receive side can decide the whole contact. A DXpedition on 160 might be running a few stations in an area with high noise levels. If their receiver can only hear the strongest signals, a wall of callers makes it worse. Often the most effective approach is to call once, listen for the response, and avoid long strings of calls. It also helps to be patient in the grey-line window and be ready to switch to another band if conditions change.

For Club Log, the thing I'd point out is that it is a record-keeping and information tool and not a way to guarantee a contact. A DXpedition's log search can confirm whether your contact made it into the log, but a missing entry might just mean the upload hasn't happened yet. Keep your own timestamps (in UTC), frequency and mode so that if there is a mismatch you can check it. Also, before sending an OQRS request, check whether the operation is accepting them and whether LoTW is used.

The last thing worth saying is about spots. Posting a spot is helpful when you've verified the callsign and listening frequency, and a good spot comment mentions things like 'up 2' or 'listening 5-10 up'. A spot that just says 'DX' with a rough frequency often sends people to the wrong place. Spot only what you've actually confirmed, and don't repeat a spot that is already on the cluster.

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.