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 where to actually call

ci_cover.jpg

This thread is for practical pileup technique, mostly aimed at the "Clipperton or Bouvet" scenario: a rare entity, a short operating window, a lot of people, and propagation that may only favour you for a short time. Most advice on this is a mix of good habits and folklore, so it would be useful to separate the two.

Here is a starting framework. Add to it or argue with it.

1. Hear before you transmit. Before touching the TX side, listen for several minutes. Work out whether the DX is operating split, how they are choosing callers (by call area, by continent, by the last two letters, or just taking whatever is loudest), and how fast they are turning contacts around. The DX station's pattern tells you more than the spot does.

2. Know your split setup before the pileup starts. On most rigs that means VFO A for receive on the DX and VFO B for transmit offset, with split on, and a quick way to check which VFO is which. Many missed contacts in the first minutes are operator error: transmitting on the DX frequency, or calling on a frequency the DX never listens to. Check the setup into a dummy load or by reading the display carefully, not by guessing.

3. Find the listening range. When the DX says "up 5 to 10" or "listening up 1 to 5", that means the range above their transmit frequency. It does not mean one exact offset. A narrow window concentrates everybody into a few hundred hertz, while a wider window spreads callers out. Many operators move around inside the range to find the clear spots, which is more effective than parking on the busiest one.

4. Timing and tailending. Tailending, which means calling at the end of the previous QSO, works only if you stop calling when the DX stops and answers someone else. If you come in over a QSO in progress you are adding QRM to a contact you might later be waiting on. Whether to call during the exchange or after is something operators on different modes disagree about, and DX operators sometimes state their own preference. My question is how people decide when to throw their callsign into the gap: right at the end of the other station's final transmission, or after hearing the DX's first transmission following it.

5. Callsign discipline. On CW, send your call once or twice at a steady speed and then listen. A lot of the time the DX is trying to pull out a partial call, and a long string of repeats hides that. On SSB, use standard phonetics. Creative phonetics make it harder for someone with weak signals and a language barrier to copy you. On either mode, if the DX sends a partial, answer with only your call and nothing else.

What I would like to hear: how you decide where to call in a split pileup, whether you favour a fixed offset or changing it, and what has worked for you with CW versus SSB at similar pileup sizes.

  • Replies 2
  • Views 36
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On choosing where to call: the useful thing to watch is the DX station's own receive behaviour. If they keep picking callers from one narrow part of the pileup, there is usually a reason, such as the DX antenna's directivity, a noise null at their site, or simply that they leave the receiver parked there. If instead they sweep slowly up and down, the best approach is often to be slightly off the biggest cluster, with a signal that is cleanly zero-beat on whichever offset you choose. On CW, a frequency that is off by a hundred hertz can make your call sound like the tail of someone else's. A sharp, stable signal on a slightly quiet spot often beats a louder one in the middle of the crowd.

On tailending, the common-sense rule is to listen for the rhythm. When the DX operator is running tight exchanges, with callsign, report and then the next call, there is only one short gap per QSO, and everyone is competing for it. In that case calling just after the final DX transmission is the only practical choice. If the rate is slow, wait for the clear end and let the DX decide, instead of calling on top of their exchange. And stop calling whenever you hear the DX transmitting. It sounds obvious, but a lot of lost time in a pileup comes from people who keep sending through the DX's reply.

For FT8 pileups, check the DXpedition's own instructions first. Some use Fox and Hound mode, where the DX transmits in a defined range of the audio passband and hounds are supposed to call above a set frequency. Calling on the fox's frequency harms the whole operation, so follow the published procedure exactly.

  • Administrators

Two more areas where the thread could go: low-band conditions and the tools around the pileup.

On 160, 80 and 40 metres, the biggest gains often come from receive improvement, not from more transmit power. A rare entity on top band might be audible only in very weak peaks, and a receive antenna such as a Beverage, loop or other directional system can be the difference between hearing the DX and not hearing them. If you cannot hear them through the noise, you cannot tell whether the DX is calling you. Grey-line timing matters too: sunrise and sunset at both ends of the path often create the best short windows, so predicting those windows is worth the time. Check where the DX is listening, since on the low bands operators often use the recommended DX windows and may also listen outside them in split.

For tools, a DX cluster spot is a hint, not a guarantee. Spots can be wrong, outdated, or busted, and a spotted frequency may be the DX transmit frequency while the actual listening range is somewhere else. Check the DX station's information page or announcements for the listening plan. For preparation, Club Log's tools can help you see how wanted an entity is, check which bands and modes you still need, and, where the DXpedition has chosen to publish them, check whether you appear in the online log after a contact. Most DXpeditions that use Club Log publish a log search so you do not have to call repeatedly to be sure of a QSO.

The etiquette side comes down to a few habits. Do not call when the DX is not listening for your region. Do not use spotting as a replacement for listening. Do not ask for repeats of information that was just given. Once you have worked the DX on that band and mode, move on to let someone else have a chance, unless the DX is asking for extra contacts. For DXpedition planning from the operator side, the important thing to remember is that the operation has limited time, power and antenna capacity, and a well-behaved pileup makes the whole team's schedule more likely to be completed.

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.