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 and tailending, and what changes for Clipperton or Bouvet-class targets

ci_cover.jpg

Pileup technique gets argued about more than almost anything else in DXing, so here is a framework to pick apart. Rare-entity operations (Clipperton and Bouvet are good examples) are short, expensive and logistically hard. Every minute of operating time matters to the team, and every wasted call from a hundred stations makes the pileup harder to manage. Whether you get the QSO depends on four things: how well you listen, your timing, your equipment, and how disciplined you are.

Start with the basics of split. If the DX says "up" or gives a range such as "up 5 to 10" (CW) or "up 5 to 15" (SSB), set VFO A to the DX's frequency for receive and VFO B to your transmit frequency, with split enabled. Check twice that you are transmitting where you mean to. Calling on the DX's own frequency while he is listening up is the classic mistake, and it draws the "UP!" from the operator and complaints from everyone nearby. Also check the display after every band change, because many rigs drop out of split or reset the transmit VFO.

Listening up before you call. Spend time listening to where he is picking stations from. Does he work them one after another, moving up the band? Does he stay in a narrow slice, or hop around? Is he working by call area, by continent, or by the last two letters of the callsign? Many operators work the pileup in a pattern, and fitting in with it beats calling randomly. If he is working stations 1 kHz up and you keep calling 3 kHz up, you are not in his window. If he is picking stations in a narrow range, calling a little to one side of that range is often better than sitting dead on the busiest spot.

Timing and tailending. There are two distinct things people mean by tailending. One is the polite version: you send your callsign in the gap right after he finishes a QSO and before the next station would normally respond, once the exchange is nearly complete. The other is the bad version: calling over a QSO in progress, or calling repeatedly while he is trying to complete an exchange with someone else. Most of the pileup etiquette complaints are about the second one. The first one is sometimes tolerated, but only briefly and only when the operator is clearly running fast. If he asks for specific callsigns or a specific region, answer only when you fit.

Callsign and phonetics. Use the standard ITU phonetics on SSB, and send your callsign once or twice at most, not four times. On CW, send it cleanly at a speed slightly slower than your maximum. Creative phonetics ("Kilowatt Nine Zulu" or invented words) usually hurt. On a noisy or weak signal, a well-sent callsign in the clear window will beat a longer message every time. If the operator comes back with a partial ("W1 ?"), repeat only the full callsign. If you hear a partial that is not yours, wait.

DX clusters and Club Log. Spots help you find the DX and know when bands are open, but treat them as hints. A spot can be wrong, and a mis-spotted callsign or frequency can pull a crowd to the wrong place. Listen for yourself before calling. Club Log is useful at the planning stage: the Most Wanted list shows how many people are looking for each entity, and many DXpeditions publish their logs there so you can check that your QSO is in. Check the log before you start calling again. Duplicates add load for the team without helping you.

Low bands and top band. On 160 m and 80 m the game is less about shouting and more about hearing. Receive antennas (Beverages, loops, flags) often matter more than a power increase. Static crashes, local noise and grey-line timing all affect when you can work the DX. DXpeditions to remote islands often use very narrow listening ranges on 160 m because the band is crowded and the signals weak. If you cannot hear the DX but can hear his callers, it is usually better to wait for a better opening than to call blind.

Why Clipperton and Bouvet are different. Both are rare, remote, and hard to reach. Operating time may be short and the weather and landing conditions can change the schedule. That means pileups can be intense, with a lot of attention in a few days. For you, the practical points are: have your station ready before the start (antennas, filters, split, logging), know the band and mode where you have the best chance, and be patient. Do not assume that a big signal means an easy QSO; the operator may be working the weak signals in between.

What techniques have worked best for you in a big pileup, and where do you think the etiquette line is for tailending?

  • Replies 2
  • Views 31
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

A few things to add on the rig side, because a lot of failed calls are equipment problems rather than technique problems.

First, check your receive filter width. On CW a narrow filter helps you hear the DX's pattern, but if it is too narrow you will miss the stations calling around him, which are the ones that tell you where he is listening. A slightly wider setting while you work out the pattern, then a narrower one once you are in the window, is a reasonable approach. Second, check your transmit offset against the DX's actual zero beat. If your rig has RIT or XIT, do not leave them on from a previous QSO. Finally, use the rig's memory or a quick-swap function so you can jump between the DX's frequency and your call frequency without retuning.

On the digital side, if the DXpedition runs FT8 in Fox and Hound mode, follow the instructions carefully. As a Hound you generally call above the Fox's frequency range and let the software handle the exchange. Calling in the Fox's own range or sending repeated calls after you have been answered causes problems for him and for everyone else. Read the DXpedition's operating notes before the start; they usually say which modes and bands are planned, and sometimes list the frequencies.

One more point on the cluster: RBN and skimmer-based spots are good for checking whether the DX is audible at all and where, but they do not tell you whether you are in his pileup window. Use them for "is he there?", then listen.

  • Administrators

On etiquette, I would say the line is simple: if you can hear that the DX is still in a QSO, do not transmit. A short tailend call after he has clearly finished and is about to call CQ or ask for a call is a different case from calling over the final exchange, even though from the other end of the pileup they both look like tailending. The operator will usually tell you what they prefer. If they say "only call when I say", then that is what you do.

It also helps to understand the DXpedition side. Planning for a rare entity covers permits, transport, power, antennas, band plans and operating schedules. The team often has to make choices such as splitting operators across bands and modes, or favouring low bands during certain hours, because they have limited time. When they ask for certain regions or modes, that is usually a deliberate plan to share the contacts around. Respecting it makes the whole operation more efficient.

For your own approach: keep a log of what you need by band and mode. Many people chase an entity on one band and ignore the others, but on a short DXpedition you may have better chances on a band that is less crowded. Check the Club Log Most Wanted list and the operation's own notes, and plan your effort accordingly. Also know when to stop. If the pileup is huge and you are not getting through after a reasonable effort, trying a different time or band is more productive than calling continuously.

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.