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 what changes on the low bands

ci_cover.jpg

This is a thread for the practical side of working rare DX when a few hundred stations are calling at once. A Clipperton-type or Bouvet-type operation shows why it matters. The entity is rare because access is hard, the operating window is short, and there may be only a few days of usable propagation to your part of the world. Whether you get in the log usually depends on your receive setup, your timing and your discipline, rather than on raw power.

Here is a basic framework to argue with or add to.

1. Work out the operating mode before you transmit. Check the DX station's info and the DX cluster comments to see whether the operation is simplex or split. If it is split, set it up correctly: receive on the DX frequency, transmit on your chosen offset, and verify that the rig is really transmitting where you think it is. Many a pileup has been made worse by a split that was not actually engaged. A quick check into a dummy load or a second receiver is worth the effort. If the DX says 'up 5 to 10', that means roughly 5 to 10 kHz above his transmit frequency on SSB. On CW the spread is often narrower. Never transmit on the DX's own frequency when he is listening up.

2. Listen before you call. Spend a few minutes just listening. Does the operator work stations in a pattern (up one, then next one up, then back down)? Does he pick out partial calls, or does he work only complete callsigns? Does he work by call area or by continent ('North America only')? Is he answering the loudest callers, or the ones that fall in a quiet gap? The most useful thing a caller can do is reduce his own random factor and fit into the operator's pattern.

3. Choose your transmit frequency deliberately. Do not just park where the pileup is thickest. Look at the receive passband and find a place where the DX is actually responding. If he has been working stations around a certain offset, the next few he works will probably be near it. Some operators move around, so keep following him with the receiver. A sensible habit is to change your transmit frequency slightly now and then instead of calling on the same frequency forever and hoping the DX station happens to land on it.

4. Timing. The single most common error is calling while the DX is transmitting, or calling at the wrong point in the exchange. A good rule: call only after the DX has finished a QSO and sent his QRZ or 'up' prompt, or after a pause long enough to show he is ready. Send your callsign once or twice, not five times. On SSB, the full callsign in standard ITU phonetics, once, is generally better than three versions of it. On CW, send your call at a speed no faster than he is sending, and do not keep sending once you hear someone else answered.

5. Tailending. This is where opinions differ. Tailending means calling just as the previous QSO ends, so that your call lands in the gap before the DX sends QRZ. Done carefully, it can be efficient on a fast CW operation. Done by someone who cannot hear the end of the QSO because he is off frequency, or who sends over the 73, it just adds to the mess. If you cannot actually hear both sides of the exchange, wait for the QRZ. It is also poor practice to tailend a QSO that has not yet been confirmed, because the DX may still be repeating a call.

6. Callsign discipline. If the DX sends a partial call ('K1?' or 'W6 something'), answer only if you match it. If he gets two letters of your call, send your full call only once and do not add extra information. If you are asked to repeat, then repeat. Avoid inventive phonetics. Standard ITU phonetics are better understood across languages and bad conditions. Use the same phonetics each time so that the DX can match what he has already partly copied.

7. DX cluster and Reverse Beacon spots. Spots are helpful for finding the station, but they also pull in a crowd. Do not spot a DX station unless you are sure of the callsign and frequency. Include whether he is listening up or down. Repeated self-spotting and wrong frequencies cause real trouble. When using the cluster, remember that a spot shows where someone heard the DX, which is not necessarily where he is transmitting. For split operation, the spot frequency can be the DX's transmit frequency, so check the comment.

8. Club Log and logs. Club Log's DXCC Most Wanted list and the expedition's own online log can help you decide where to put effort. Many operations upload their logs frequently, so you can check whether you are already in the log. If you are, do not keep calling for extra QSOs on the same band and mode unless you need a new slot. Calling after you have been logged wastes the operator's time and everyone else's chance. Note that upload delays can occur, so a brief absence from the log does not always mean the QSO was not made. Wait before deciding.

9. Top band and low bands. On 160, 80 and 40 metres, receive capability can matter more than transmit power. Noise is often the limiting factor, so receive antennas such as Beverages, loops, flags or phased verticals can help. Timing is critical, with grey-line and sunrise or sunset paths often the best opportunities. On 160 metres, the DX window is often kept clear for DX operation, and many operations announce their transmit and receive frequencies in advance. Many 160 m DX stations listen on a different frequency, and a quiet moment is easy to miss. Because signals on these bands can be at or below the noise, many DXers keep their CW weak-signal copy skills in training, and use digital modes where they are available.

10. FT8 and Fox/Hound. In WSJT-X's Fox/Hound mode, a DXpedition (the Fox) can work many stations at once. If you are a Hound, you should follow the instructions: stay above the stated frequency limit, do not call on the Fox's own transmit frequency, and wait for the Fox to answer you. Sending constantly on the Fox's frequency does not help, and may block other stations.

11. Rare entities and planning. Bouvet and Clipperton are in different logistics categories: remote, hard to land on, weather-dependent, and subject to permits. Those that are planned get a lot of attention months ahead: transport, safety, power, antennas, band plans and a log upload plan. The result is that a DXpedition may have a short time on each band, so the callers who prepare in advance (antennas checked, band and mode slots planned, cluster alerts set) have a better chance than those who just show up.

12. Etiquette. Do not tune up on the DX frequency. Do not answer with only your call if he asked for something else. Do not argue on frequency about who was first. Do not call out of order after being told the DX is working a specific region. If you hear a deliberate interferer, do not respond on frequency. Let the operator or his net control deal with it.

What do others consider the biggest single improvement to their pileup success: better receive antennas, better timing, or better knowledge of operator patterns? And where do you stand on tailending: acceptable skill, or just a source of QRM?

  • Replies 2
  • Views 27
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On tailending, my view is that it depends on the mode and on the speed of the operator. On a fast CW operation where the DX sends his callsign and a report and then goes straight to the next call, the gap is only a fraction of a second, and stations who wait for a full QRZ will often be too late. But the technique only works if you can actually hear the end of the exchange cleanly. In practice that means a good receive audio chain and a transmit-receive switchover that is fast enough, with no relay delay. If your rig or amplifier needs time to switch, you will land on top of the last part of the QSO and annoy everyone.

For SSB, I would be more conservative. The pauses are longer and the DX is more likely to be affected by overlapping speech. A short, clear call right after the QRZ usually works better than a clever tail-end call.

One more point on split: it is also worth checking your transmit filter and audio bandwidth. If you are transmitting a wide SSB signal while the DX is listening up, you could splatter into neighbouring callers. Keeping processing moderate and bandwidth narrow is a real courtesy at a time when many people are calling inside a few kilohertz.

  • Administrators

On the low bands, I would put receive antennas first, ahead of timing. A station that can hear the DX is a station that can follow his pattern, find a gap and identify when he is calling for a particular call area. On 160 and 80, you may have a very weak signal one moment and a good one a few minutes later as the grey line moves, so there are only short windows. Being ready at the right moment matters more than calling the whole time.

It also helps to separate the DX's transmit and receive information in your head. Often the DX is on one frequency, and the callers are spread over a range that can be several kilohertz wide. Using a second receiver or the sub-receiver for the transmit frequency lets you hear both at once, so you know the DX frequency and where the pileup is.

As for Club Log: I would treat it as an aid for planning, not as a promise. Check the expedition's own page for log search rules and for any OQRS details, because they differ from one operation to another. If you want to confirm that a QSO was logged, wait a reasonable time before you try again, and do not assume a missing entry means a failed contact until the logs are fully uploaded.

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.