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 a DXpedition pileup: split, timing, tailending and what actually gets you in the log

ci_cover.jpg

Opening a thread on pileup technique, because with a Clipperton or Bouvet type target the difference between a log entry and an hour of frustration is usually procedure, not power. Rough notes below. Please correct or add to them.

1. Work out the operating pattern before you transmit. Listen for several full cycles. Is the DX on split or simplex? Is he working "up 5 to 10", a fixed frequency, or tuning around? Is he taking one call at a time, or asking for a number, a suffix or a call area? Most pileups that sound like chaos have a pattern. If the operator is picking out stations by the last two letters of the call, a full call sent on the wrong beat is wasted.

2. Set up split properly. Receive on the DX frequency and transmit in the window he announces. Use the transmit-frequency monitor function (on many rigs it is a button that swaps in the TX VFO) to check that you are where you think you are. A common mistake is leaving the rig on simplex and calling on top of the DX. Another is working the same spot on every transmission, so you sit exactly where hundreds of others are. If he is working up, listen to where the stations he answers are zero-beating, then move a little off that. Many operators drift up or down through the pileup as the cycle goes on.

3. Timing beats volume. Call when the DX is listening, not while he is still finishing a QSO. Short calls are best. On CW, send your call once or twice at roughly his speed. On SSB, give your call once, with standard phonetics. Long, repeated calls make you easy to miss and raise the noise for everyone else. If he comes back with a partial, such as "W3 ... ?", respond only if it fits you, and repeat only what is needed. Avoid adding "please", "DX" or your name, because every extra word costs a cycle.

4. Tailending. Calling as the DX finishes one QSO and hands over to the next is a normal way to get in on a fast pileup. Done carefully, it is part of the rhythm. Done sloppily, it steps on the final exchange and forces a repeat, which costs everyone time. The distinction is whether you are sending in the gap or over the end of the preceding QSO. If the operator keeps asking for repeats because of tailenders, stop and wait for a clean opening or change your timing.

5. Phonetics. Use standard ITU phonetics unless the operator's habits clearly call for something else. Creative phonetics sound clever to you and are unclear to someone copying through QSB and static. If he has picked up a partial, you can help by repeating the part he asked for in phonetics rather than resending the whole call.

6. Spots and the cluster. Cluster spots are useful for finding out the target is on the air and roughly where, but they are not gospel. Busted spots and wrong frequencies propagate. Before calling, listen for the DX itself and confirm the callsign on a source you trust, such as the expedition's official website, rather than relying on a comment in a spot. If you spot a station, only do so after hearing it yourself, and include the listening frequency if it is split (for example "up 2"). The Reverse Beacon Network can help show whether a band is open toward the target on CW and RTTY, but it tells you about a path, not about your own signal.

7. Club Log. Use the Most Wanted lists and your own band-slot matrix to decide what to chase. A new entity on any band is a different priority from a band-slot you already have on another mode. Club Log's expedition log search is handy for checking whether your QSO appears, but there can be a lag between operation and upload, so a missing entry is not always a bad contact. Wait and re-check before sending repeat QSOs. Duplicates slow the expedition down, and some operators ask that you do not make them.

8. Top band and low bands. On 160 and 80 metres, the receive system often matters more than transmit power. Many DX chasers on the low bands use dedicated receive antennas such as Beverages, loops, flags or phased verticals, because the signal you want can be below the local noise on your main antenna. Greyline timing around the target's sunrise and sunset matters a lot, and windows can be short. Low-band expeditions often use very narrow listening windows, so the discipline of not calling outside them counts for more than on 20 or 15 metres.

9. FT8 and other modes. If the expedition uses the Fox and Hound mode in WSJT-X, read its instructions and follow them carefully. Hounds are expected to call above a set audio frequency, and the software handles the sequencing. Calling in the wrong part of the passband, or on the wrong period, can interfere with the Fox's transmissions and with other Hounds.

10. Planning from the expedition side. Targets like Clipperton and Bouvet are hard because of landing conditions, weather, permits, the logistics of getting equipment and people ashore, and limited time on the island. That tends to mean compact antenna systems, careful band planning, multiple stations, and a clear published schedule or pilot arrangement. For chasers, the practical consequence is that you may only have a handful of good openings per band. Know your own path times, keep your station ready, and do not burn the opening on a bad setup.

What are the habits you think most improve a caller's chances? I'm particularly interested in how people choose where to call on split, and in whether they tailend or wait for a clean gap.

  • Replies 2
  • Views 40
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On choosing where to call: I'd say the most useful skill is working out the DX's "pattern" rather than guessing. If he's working up, listen to a few stations he picks and note whether he tends to move up, down, or hold one spot between calls. If he's hopping around within a range, calling where the last QSO happened is usually a bad bet, because everybody else is there too. A slightly offset call, within the permitted window and with a clean signal, often does better than the most obvious frequency. The caveat is that the offset must not be so wide that you sit on someone else's frequency or outside what he's listening to.

On tailending: I'd separate it into two cases. If the DX is deliberately running a fast cycle, with a short exchange and straight into "QRZ", then calling on the first beat of his listening period is normal. If it's a slower operation where he's struggling to copy, any call over the end of a QSO just makes things worse. I'd always rather miss a cycle and be copied cleanly than be a partial that costs him another repeat.

One more practical point on split: check the audio bandwidth and filters on the transmit side. If your signal has splatter or you're running a lot of processing, a split-frequency call can spill into the neighbouring slots and get you complaints even if your frequency is right.

  • Moderators

I'd add something on verification and etiquette, because those cause a lot of avoidable trouble. Always confirm the callsign and the QSL route from the official source before you start, particularly on a new or short-notice operation. Fake or mistaken spots do appear, and chasing a call that is not real wastes the band time that Clipperton or Bouvet type openings don't give you much of.

On Club Log, I'd treat it as a planning and checking tool rather than a guarantee. Use the band-slot view to decide which band is your best bet first. If you work the DX, check the log search after the operator has uploaded, and give it time. Many expeditions upload in batches, so a missing QSO right after the contact doesn't mean you need to call again. If you do think you were not in the log, wait until there has been an update, and only then consider a repeat QSO.

On the low bands, listen before you transmit for longer than you think you need to. A CW or SSB operator on 160 may be listening on a tight, specific frequency, and with the QRN and fading you can hear one half of the exchange and not the other. Knowing which stations he's actually answering is the best way to avoid calling blind. A good receive antenna lets you hear the callers and the DX's responses to them, which improves your timing more than adding transmit power.

Finally, if the operator says "QRZ" or tells you to stand by, just stop. Nothing annoys a pileup, and the operator, more than someone who keeps calling after being told they are not the one being worked.

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.