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 actually gets you in the log

ci_cover.jpg

I'd like to collect practical thinking on pileup technique in one thread, because the same mistakes keep turning up whenever a new rare one appears on the cluster. Think of the Clipperton or Bouvet type of target: few operating days, a hard path from some locations, and hundreds or thousands of stations calling at once. The question is how to maximise your chances without becoming part of the problem.

Start with the basics, because most failed calls come from skipping them. First, work out how the DX is operating before you press the key. Is he running split? Listen for "up 5 to 10", "up 2" or "listening 7165 to 7170". Is he working by call area, by continent, or taking everything? If you can't tell after a few minutes, keep listening. Information about the operating pattern is free if you shut up and listen.

Second, set up split properly and check it. Put VFO A on the DX and VFO B on your transmit frequency, or use your rig's split-by-offset function. Then verify with the transmit-frequency monitor, or by listening on VFO B, that you really are transmitting where you think you are. Operators who call on the DX's own frequency, or who leave split on after the last band change, cause some of the worst messes.

Third, timing. Calling continuously for a minute isn't a technique. The better approach is to listen to the rhythm of the operator: how long between QSOs, whether he picks a partial call and works it, and where in the spread he is currently listening. Then call in short bursts, once or twice, listen, and move if nothing happens. On SSB, give your callsign in standard phonetics, once or twice, and nothing else. On CW, send your call once or twice and stop. Many stations send it six times, which blocks the DX from hearing a partial that could have been you.

Tailending is the point I expect to get the most discussion on. Calling at the very end of the previous QSO, as the DX signs off with the other station, can work when the operator is running a fast rate and picks up whoever is first. It's bad practice when the DX is giving reports and exchanging more than a bare minimum, because you can step on the QSO, force a repeat, and slow the whole pile. My rule of thumb: if you can hear the other station's confirmation or "QRZ" is not yet out, wait.

What approaches do you use to decide where to call when the DX is working up the band and the pileup is a wall of noise? Zero-beating, picking the quietest spot, following the pattern of the last few QSOs? And how do you handle phonetics when your call is easy to misread on a weak, fluttery path?

  • Replies 2
  • Views 28
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the "where to call" question: the usual advice is to find where the DX operator is currently listening and then work out how he moves. Some operators sweep slowly up the spread and then drop back down. Others stay on a narrow segment and pick the strongest. If it's a sweep, calling about one or two kHz above his current pickup point, so that he reaches you in a few seconds, tends to work better than burying yourself at the top of the range. Calling at the very top, out where nobody is reaching, can leave you stuck for a long time.

On phonetics, I'd say avoid inventing creative ones. Standard ITU phonetics are what a tired operator is most likely to copy, and on a marginal path the distinctive consonant sounds survive better than vowels. If the DX gets part of your call, repeat the full call once, not just the missing letters, unless he explicitly asks for a partial. On CW the same logic applies: send your whole call at a speed he can copy, not faster. Matching or slightly slowing to his sending speed is usually better than blasting at 30 wpm.

Tailending also depends on the mode. On CW with a fast operator who is using short exchanges, calling right on the last character of the previous QSO is standard behaviour. On SSB, where the exchange is longer and the operator listens to the whole thing, it's much more disruptive. Pileup etiquette also covers things not directly about transmitting: don't tune up on the DX frequency or the listening range, don't tell others to "QRZ" or comment on whether he's split, and don't call again after he has logged you. Confirm the QSO by logging what you heard, not by making a second call to be sure. A dupe QSO costs everyone else time.

  • Moderators

For low-band DXing, a lot of what works on 20 metres either doesn't apply or becomes more important. On 160 and 80 metres the limiting factor is usually receive, not transmit. A good receive antenna such as a Beverage, a flag or a small loop array can let you hear the DX out of the noise when your transmit antenna hears nothing but static. If you can't hear the DX, no amount of power is going to help you. Timing matters too: the path often opens around grey-line sunrise or sunset, so the window can be short. Watch both ends of the path and be ready on the frequency before the opening, not after.

DX cluster spots help, but treat them as leads rather than confirmation. Spots can be wrong, busted, or based on a skimmer decode of a partial call. Listen to the DX yourself before you call, and if you do spot, spot what you actually heard, with the frequency and the split information if you know it. Don't spot yourself.

For planning your own chances, Club Log is useful in a few ways. The Most Wanted list gives you a rough picture of which entities are hardest for the community, and your own log's band and mode slots help you decide where to concentrate when a DXpedition is on. Many DXpeditions upload logs to Club Log, so you can search the expedition's log after the event to check that you're in it, and use their OQRS if they offer one. That said, check the expedition's official page for how they handle QSLs, because systems and rules differ between teams.

Also, if the operation uses FT8 in Fox/Hound mode in WSJT-X, the rules are different from conventional SSB/CW. Follow the expedition's published instructions, such as keeping your transmit frequency above the stated threshold, and don't keep calling when the Fox hasn't selected you. Reading the DXpedition's instruction page carefully before the operation starts, including band plans, modes, and any pilot station information, will save more time than any trick on the day.

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.