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 pileups on rare DX: split, timing and listening habits for Clipperton and Bouvet-class targets

ci_cover.jpg

This is a thread for the technical side of working rare DX. It covers what to do in the seconds before you press the key or PTT, and what to do in the days before an operation starts. Clipperton and Bouvet are good reference targets because they show how different rare operations are from a routine DX station. Both are remote, logistically hard and usually activated for a limited time, so the operators work under pressure and you may get only a few usable openings per band. (Check the team's official page for dates, modes, frequencies and QSL policy. Anything you read here about a specific operation could be out of date.)

Start with the basic loop: listen, identify the pattern, set up split, then call. Most failed attempts come from skipping the first two steps. Before transmitting, find out whether the DX station is working split or simplex, and where he is listening. On CW the operator might send "UP" or "UP 2", or the pile-up may spread a few kHz above him. On SSB, 5 to 10 kHz up is common, but the operator may also announce a window such as "listening 10 to 15 up". If you can't hear a pattern, wait. Calling on the DX frequency is the one thing that is clearly wrong.

With split set, you need to hear the DX and the pile separately. A second receiver or a band scope helps, because you can see where the operator is picking callers: a clump near one frequency, a drifting range, or a region the operator is sweeping slowly. If the operator keeps working stations in a narrow slice, putting your transmit frequency in that slice often works better than being in the middle of the largest pile of callers.

Timing matters as much as frequency. A common approach is to call only after the DX has finished a QSO and sent his ID or "QRZ". Tailending is a gray area: calling at the very end of the previous exchange, before the operator has a chance to ask for the next station. Some operators accept it as part of a fast pile-up rhythm, and some discourage it, because it clutters the ending of the previous contact and can cause repeats. A safer habit is to learn the operator's rhythm, wait for the end of his transmission, and call once. Then listen. Don't keep sending when he is already answering someone else.

For callsigns, send or say only what is needed. On CW, send your call once or twice, cleanly and at a speed the operator is already using. If he sends a partial, such as "W1?" or "K5 QRZ", answer with your full callsign unless he has asked for something else. On SSB, use standard ITU phonetics rather than creative ones. If the operator gets part of your call, repeat just the part he needs. Save any "please" or "DX, DX" for never.

Spots are useful but unverified. Treat a DX cluster spot as a prompt to listen, not as proof of the frequency, the mode or even the callsign. Look for the QSX or "listening" info in the spot comment, and cross-check against CW Skimmer or Reverse Beacon spots if the mode supports them. A bad spot can pull people to the wrong frequency very quickly, so don't spot something you haven't heard yourself.

Questions for the thread: what is your workflow when the DX station is weak and the pile is strong? And do you treat tailending as acceptable timing or as bad practice?

  • Replies 2
  • Views 70
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd separate two things that get lumped together: tailending as a timing strategy and calling over an exchange that's still in progress. Calling in the gap right after the DX operator has finished the previous QSO and before he sends QRZ is just good timing. Calling while the previous station is still sending the report is what actually costs everyone, because the operator has to ask for repeats. If you want a simple rule, listen to the DX's cadence for a few minutes. If he leaves a consistent gap, call into it. If he doesn't, nothing you do will fit, so wait for a pause.

On the low bands the receive side is usually the limiting factor, much more than the transmit side. For 160 m and 80 m, a receive antenna such as a Beverage, a flag, or a small loop array often matters more than extra power. Most rare-DX openings on 160 are short and tied to gray-line timing, with sunrise or sunset at one end or both. Quiet geomagnetic conditions also help a lot. Use the traditional DX window near the bottom of the band, but check your band plan, because it differs by region. A narrow CW filter helps, but in a big pile it can also hide the thing you need to hear, which is where the DX is actually transmitting. Keep a wider setting for the first listen, then narrow down.

On the cluster: set your own filter so that spots from your area or on your needed bands are the ones you see. Otherwise you'll see a stream of spots that don't match your path and can't be worked from your location.

  • Moderators

Preparation is a big part of this. If you use Club Log, check your needs for the entity by band and mode before the operation starts, and decide which slots are actually worth your time. A Most Wanted list can help you rank targets, but it shows a snapshot of what other users have worked, so check the current version and don't treat it as a fixed order. Online log search from the team, where available, is also worth using for your own contacts. Check it before you call again for a dupe, because every extra call you make for a QSO you already have costs time for someone who needs it. A dupe at the end of a long band opening is not harmless.

For the target itself, remember what makes places like Clipperton and Bouvet hard. Clipperton is an uninhabited French possession in the eastern Pacific, and Bouvet is a remote Norwegian subantarctic island. Both have difficult landing conditions, limited time on site, weather risk and tough power and antenna logistics. That means the operating plan can change quickly, with bands or modes dropped or added depending on conditions. If you want to be ready, watch the team's own updates rather than relying on forum rumors, and leave room in your schedule for the first few days, when the operators typically have the most gear running.

For FT8 operations that use a DXpedition mode, read the team's instructions carefully. Fox/Hound mode in WSJT-X is the standard example. Hounds call at a different frequency than the Fox transmits, and the Fox answers in a different way than normal, so the usual call-and-reply sequence doesn't apply. Using the wrong settings can make you invisible to the Fox or put you in the way of other callers.

On etiquette: if you can't hear the DX station, don't call. If you think you are the only one hearing him, wait, listen and look for confirmation. Don't tune up on his frequency. Don't answer him on his transmit frequency if the operation is split. And if someone is plainly on the wrong frequency, a short note on the cluster or a single clear message is better than starting an argument on the air.

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.