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/Bouvet-type targets

ci_cover.jpg

Opening a thread for the practical side of rare DX. Most pileup failures come down to a small set of mistakes: poor listening, bad timing, a lack of patience, or a receive system that can't hear the DX in the first place. I'd like to collect techniques that actually work, especially for expeditions to places like Clipperton or Bouvet. Those operations are logistically hard, often short, and tend to be high on Club Log's Most Wanted list.

Here's a starting framework. Pick it apart.

1. Work out the operating pattern before you transmit. Is the DX working split? Check the expedition's announced plan if there is one. If it isn't clear, listen for several QSOs. Typical patterns are the DX transmitting on one frequency and listening up 5 to 10 kHz on SSB, or up 1 to 3 kHz on CW. Also watch how the operator picks callers. Some go by call area, some by continent, some by number, and some just pull out whatever is loudest. If the operator says "Europe only" or "North America only," calling out of turn is wasted effort and makes the pileup worse for everyone.

2. Set up split properly. Put the DX frequency in VFO A for receive and the listening frequency in VFO B for transmit. Use your rig's proper split function, because RIT/XIT usually can't cover the offset. Before you key up, check that your transmit frequency is clear by using the rig's TX-frequency monitor, or by briefly swapping VFOs and listening. The pile will often have spread across a wide chunk of spectrum, and a quiet spot may be occupied by a station that is simply unlucky or lost.

3. Call once, short, with your callsign only. Don't send the DX station's call, "please," or your name. Send your full callsign once or twice, then listen. On SSB, use standard ITU phonetics, clearly and once. Inventive phonetics may seem to stand out, but they cost the operator time and can lead to a bust. On CW, match the DX's speed or go slightly slower if the pile is very noisy. Fast and sloppy loses to steady and clean.

4. Timing and tailending. This is where opinions differ. Tailending means calling at the very end of the previous QSO, before the DX operator has called CQ or QRZ. Some operators tolerate it. Others hate it because it clips the end of the previous exchange and can force repeats. When the DX station sends a partial call and you recognize it as yours, answer immediately. Otherwise, a call right after the final exchange may land in the gap. What is your rule of thumb, and does it change with mode or pileup size?

5. Use spots, but don't trust them blindly. A DX cluster spot tells you that someone heard something on a frequency, not that it's correct. Spots can be busted, stale, or posted for the wrong callsign. The Reverse Beacon Network can help for CW and RTTY by showing whether the DX is being heard at all near you. Then confirm by listening before you spend time calling. Please avoid chatty comments on the cluster. They clutter the spots for everyone else.

I'd especially like to hear how others handle low-band conditions on rare ones, and how you decide when to stay on a frequency and when to try another band. For Clipperton-type paths, which are more likely to be short and compressed, the choice of when to call matters as much as how you call.

  • Replies 2
  • Views 36
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On tailending, the key point is the difference between stepping on a QSO and answering the operator's signal that he's ready. If the DX is working a station and still exchanging reports, don't call. That breaks the exchange and may force a repeat, which costs time for everyone behind you. If the DX has already sent "QRZ" or "CQ," you have a clear window, and the first one or two calls are usually the best chance.

One habit that helps is to listen for the operator's rhythm. Some run a fast tempo and expect a continuous stream of calls. Others take a deliberate pause after each QSO. Match the tempo, and don't send a long string of calls just because the pile is loud. Stations that call continuously without listening are the ones who miss a partial callback, and callbacks are how the pile moves.

On SSB, resist the temptation to ask the DX "what's the call?" or to retell the operator his own information. If you're unsure of the callsign, check the cluster, the DXpedition's website or Club Log. For dupes, check your own log and the expedition's online log if one is available. Working the same station repeatedly on the same band and mode just slows the rate for others. The usual exception is a case where you think your first QSO was not logged correctly, and even then it's better to wait until the pile has thinned.

In FT8 Fox/Hound mode, the rule is different. Hounds should call above the frequency the Fox expects, usually 1000 Hz, and shouldn't sit on the Fox's own transmit frequency. Read the expedition's mode instructions first, because getting the setup wrong can leave you calling without being heard.

  • Administrators

For top-band and low-band work, I'd put receive antennas ahead of transmit power. On 160 m, 80 m and sometimes 40 m, the signal from a remote island can be barely above the noise. A Beverage, flag, loop or similar receive antenna can make the difference between hearing a faint DX station and hearing nothing. Many stations can transmit effectively with a modest setup but can't copy the DX in their local noise, so if you can't hear them, you can't work them.

Timing matters more at low frequencies. The DX path may only open during a narrow sunrise or sunset window, and grey-line enhancement can be sharp but short. Check that your own location and the DX's location are both in the right phase, and keep an eye on geomagnetic conditions. A disturbed field can degrade low-band propagation and paths that run near the poles. For places like Clipperton, the path from your side may favour certain bands at certain times of day. For Bouvet, the geography and the amount of the world that has a workable path can be very different, so look at the great-circle path, not just the distance.

Club Log is useful for planning on both sides of the pile. As a chaser, check the Most Wanted list to prioritize which entities you still need, and see whether the DXpedition uploads logs while operating. These logs are often a good reference for dupes and callsign checks, but an absent callsign doesn't prove that your QSO failed, so don't make decisions from a single check. If you're on the planning side of an expedition, think about how you'll balance bands, modes and operating hours. Rare entities usually need many hours at the right time of day on bands with good propagation to the main population centres, and the schedule has to account for weather, landing conditions and equipment failures. Operations at sites like Clipperton or Bouvet may have less time on the air than the plan suggests, so efficient pileup management matters.

Finally, on the etiquette front, keep your transmitted signal clean, don't use more power than you need, and be prepared to move on if the pile isn't working in your favour. Good conduct keeps rates high and helps the expedition team, which is ultimately what gets everyone into the log.

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.