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 412.9 km/s
Aurora 1
Updated 14:00 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 the pileup on a rare one: split, timing, tailending and what changes for Clipperton/Bouvet-type targets

ci_cover.jpg

Rare-entity pileups tend to reward the same few habits, and most failed attempts come down to the same few mistakes. I'd like to compare notes on the technical side, using a Clipperton- or Bouvet-class target as the model: a very rare entity, a short operating window, and a huge crowd chasing a few stations.

1. Work out the operating pattern before you transmit. Listen for several minutes first. Is the DX station working split? On CW and SSB the operator will usually say something like "up 5-10" or "listening 3 to 8 up". On FT8 and FT4, a DXpedition may run Fox/Hound mode, where hounds call above the Fox's frequency and you must not transmit on the Fox's own frequency. Whatever the mode, find out what the operator is doing: calling CQ, picking a partial call, working a region ("JA only", "NA only"), or working a list. If you aren't sure, listen for another full cycle of a few QSOs.

2. Set up split properly. Keep RX on the DX station's frequency and put TX on VFO B, offset by the announced amount. Check that your rig's split works as you expect: some rigs need a separate setting for TX monitoring, and fat-fingering a split can put you on the DX frequency or on top of the wrong signal. Test your TX frequency on a dummy load, or at least listen to where your signal lands with the TX monitor or a second receiver. Don't call on the DX frequency itself. It's the quickest way to be labeled a nuisance.

3. Timing beats power more often than people think. The pile isn't uniform. Operators often settle into a pattern: they pick signals near the bottom of the range, then work upward, or they follow a rhythm of shifting 1 kHz at a time. Watch where the last few stations came from and consider calling just outside the densest area. In a big, dense pile, a clean call at a slightly different frequency can be heard better than a perfectly zero-beat one in the middle of the crowd. Don't chase the operator's tuning too closely, though. If everyone follows him, you add to the problem.

4. Send your callsign once, then listen. On CW, a short call sent once, followed by a listening gap, is usually better than a long repeated string. You can't hear the operator if you're transmitting. On SSB, say your callsign once, clearly, with standard phonetics. Creative phonetics may be memorable, but a rare-DX operator under pressure is copying fast, and the ITU alphabet is what he expects. If he asks for a partial, send only what he asked for. Anything else costs a cycle.

5. Tailending: legitimate but easy to abuse. Calling right at the end of the previous QSO, as the operator says 73 or TU, can save time. But if you call early, you step on the final exchange and may cause a repeat, which hurts everyone. Call only when the previous QSO is clearly done, not while it's still being confirmed.

6. Pileup etiquette in short. Don't call when the operator is working a specific call or region you don't belong to. Don't tune up on the DX frequency or the listening range. Keep your audio clean; overdriven SSB or a broad CW signal splatters across the listening range and wipes out other callers. Don't answer "QRZ?" with questions about QSL routes. Check the DXpedition's website for that.

7. Spots. A DX cluster spot is only useful if it's accurate. Spot what you actually heard, include the exact frequency, and add the listening info in the comment (for example "UP 2" or "NA only"). Don't spot from a single weak copy of a call you aren't sure about, since a busted call can send hundreds of people to the wrong place. The Reverse Beacon Network and skimmer spots can help confirm that a signal is real, but they don't tell you where the operator is listening.

8. Club Log. A DXpedition's online log search lets you check if your QSO was copied correctly, which can save you a duplicate QSO and free the pile for others. Many DXpeditions upload frequently during the operation, but the upload interval varies, so don't treat "not in log yet" as a firm answer. Club Log's Most Wanted ranking is also useful for deciding where to concentrate your effort.

I'd like to hear how other people approach three things in particular: (a) how you decide when to switch from "keep calling" to "stop and listen for a few more QSOs"; (b) what changes for you on 160, 80 and 40 m compared with the higher bands; and (c) what makes Clipperton/Bouvet-style planning different from an ordinary DXpedition, such as permits, landing conditions, power, antennas and band/mode strategy.

  • Replies 2
  • Views 35
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Good list. I'd add one thing to point 3: the most useful skill is listening to the operator, not just the pile. If he's picking stations from a narrow part of the range and ignoring the rest, there's usually a reason. He might be zero-beating on the loudest callers, or his receiver might be overloaded by a strong station nearby. Calling in the same place as everyone else isn't a strategy.

On SSB, I'd stress keeping the whole call short and the delivery steady. If you're just one more voice in a wall of audio, the callsign that gets picked is the one that's easy to copy on the first attempt. That usually means a normal speaking pace, a clear voice, and no embellishments. Phonetics are worth sending only when the operator has asked for a partial or a repeat, and then you should use the standard alphabet.

On FT8, don't assume it's easier. In Fox/Hound mode, the common failures are transmitting on the wrong frequency (below 1000 Hz, or on the Fox's own frequency), leaving the program on the wrong mode setting, or not noticing that your clock has drifted. Check all of these before the opening, not during it. And don't keep calling when the Fox has already sent you a report. Let the sequence finish.

  • Moderators

For the low bands the main difference is that your receive capability matters as much as your transmit capability. A rare-DX operator on 160 or 80 m might be hearing you with a lot of QRN, and you may be hearing him on a Beverage or other receive antenna while barely audible on your TX antenna. The result is a signal you can hear but he can't hear back. It can also work the other way around if your local noise is high. If you're hearing him well but not getting through, consider whether your TX antenna is the weak part of the system.

Grayline and sunrise/sunset timing at both ends are critical. A signal that is workable for 15 or 20 minutes at the right time may be gone afterward. If you know the DX's sunrise or sunset, you can plan your time on the air and avoid wasting effort when the path isn't open. For 160 m, remember the common DX window (roughly 1830–1840 kHz) and check how the operator is using split. Don't assume it's the same as on 20 m.

On the planning side, Clipperton and Bouvet are different kinds of problem. Clipperton is an atoll with difficult landing conditions and limited shelter, and Bouvet is a remote, ice-covered island with very hard access. Both depend on ships, weather windows and permits, so operators have to decide in advance what they'll sacrifice if conditions go wrong. Typically that means deciding which bands and modes get priority, how many stations can run at once, and how to share power and antenna space. For chasers the practical advice is to check the official DXpedition site for the announced plan, listen for the actual operating pattern, and avoid trusting unverified spots or social-media posts about the callsign or QSL route.

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.