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 what changes for Clipperton or Bouvet-type targets

ci_cover.jpg

Rare-entity pileups keep exposing the same handful of habits, so I'd like to collect ideas on what separates a workable approach from random calling. Take a Clipperton or Bouvet-style operation: a small team, a hard landing, limited time on the island, and weather that can cut things short. Targets like these tend to sit high on most-wanted lists, so the pileup is huge from the first spot and rate matters more than anything. The operator wants to log as many unique stations as possible, and every caller who ignores the instructions slows that down.

The basic sequence is probably familiar, but it's worth stating because most failed calls break it. Listen first, for a full few minutes if you can. Work out the mode, the operator's transmit frequency, and where he is listening. If he says 'up 5 to 10', he is listening in that range above his transmit frequency. If he says nothing and keeps answering stations well off his own frequency, he is working split whether he announced it or not. Set your rig to split before you transmit anything. Put the receive VFO on the DX and the transmit VFO in the clear spot you chose. Then check that you can hear the DX on the receive side while your transmit frequency is not occupied.

Next, find the pattern in how he picks stations. Does he take the strongest signal, the first complete call, a suffix, a call area or a continent? Is he working by number or only specific regions? If he is calling 'Europe only' and you are not in Europe, wait. Calling out of turn is the fastest way to become part of the QRM. Once you know the pattern, send your callsign once or twice with standard phonetics (or in clean CW) and then listen. Repeating it ten times in a row means you never hear your own call coming back.

Callsign phonetics are a real issue. Standard ITU phonetics are usually the best choice, because they are what the operator hears most often through noise and overlapping signals. Inventive phonetics may be memorable but are slower to decode, particularly across language barriers. If the DX sends back a partial call, reply only if the partial matches your call.

My questions for the group: how do you decide between calling on the DX's last-worked frequency and shifting to a new spot? How do you handle tailending and timing so you are neither late nor stepping on the previous QSO? And what do you do differently on the low bands, where hearing the DX is often the limiting factor?

  • Replies 2
  • Views 24
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On frequency selection, the usual advice is to follow the DX rather than guess. Many operators tune slowly through their listening range, so the stations they answer drift across it. If you call on a spot and get nothing after a couple of tries, move a little instead of staying put, especially when a crowd is stacked on the same offset. A quiet spot a few hundred hertz away from the main cluster can work better than the loudest part of the pile. On CW it also helps to listen to which frequency the DX operator answers. If he is replying to stations he hears clearly, a matching pitch tends to stand out from a wall of overlapping signals.

Timing is where opinions differ. Tailending means starting your call just as the previous QSO is finishing. Done cleanly, it can speed things up, and some operators work fast enough that waiting for a long gap would mean never getting in. Done badly, you step on the last exchange, the previous station has to repeat his report, and you add to the rate loss. A safer version is to wait for the DX to finish his own transmission and then call as he goes back to listening, rather than talking over the end of the QSO. You can also try calling a beat later than the first rush after a 'QRZ?' Big pileups often thin out a little after the opening blast.

One caution on etiquette: don't tune up on the DX frequency or inside his listening range. Use a dummy load or a free frequency. And keep your exchange short. If he asks for 'five nine', give the report and the call, nothing more.

  • Moderators

For the low bands, the limiting factor on 160, 80 and sometimes 40 is usually receive, not transmit. Signals from a remote island may be weaker than the local noise, so a receive antenna (Beverage, flag, pennant, small loop or similar) can matter more than extra transmit power. Propagation timing matters too. Grayline and sunrise or sunset enhancement can open short windows, and the signal may rise and fade quickly. Be ready at your own sunrise or sunset rather than assuming the band will be open all night. Check which time windows the target would be on the air at their end as well.

Spots and tools help, but they are hints, not facts. DX cluster spots can carry busted calls or wrong frequencies, so confirm by ear before calling and read the comment for split or listening details. For CW and RTTY, the Reverse Beacon Network can show whether anyone near your location is hearing the DX, which tells you when to start listening. Don't spot yourself or post speculative frequencies.

Club Log is useful before and after the event. Before, it helps you see how a target ranks for your own needs and which bands and modes you still lack. During and after, many DXpeditions upload logs to Club Log, so the log search can show whether you are in the log, though updates may lag. Avoid working the same band and mode repeatedly just to be sure, because dupes cost the operator time. If the team has an Online QSL Request System (OQRS) set up, use it according to their instructions rather than emailing individually.

Finally, on FT8, if the expedition uses Fox/Hound mode, follow the instructions in the software and on the team's page. As far as I know, hounds are expected to call above the Fox's own audio range, and you shouldn't call on the Fox's frequency. Read the team's operating notes, since details differ between events.

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.