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

ci_cover.jpg

This thread is for the mechanics of working a wanted station in a pileup, mostly from the chasing side, with some DXpedition-planning discussion. Rare-entity pileups are less about power than about discipline. The operators who log the DX quickly usually listen better and make fewer mistakes than everyone else. Corrections and alternative views are welcome.

Start with listening. Before you transmit, work out how the DX station is running the pile. Is he operating simplex or split? If split, where is he listening: up 1, up 5-10, or a wider range? Does he work by call area, by continent, or by the last two letters? Does he take full callsigns or partial calls? Five minutes of listening to who gets through will tell you more than the spot comment. If the DX says "up" and you can't hear the stations he is working, the pileup is spreading, and you need to work out which part of that spread he is actually hearing.

For split operation, put the DX frequency in VFO A for receive and your transmit frequency in VFO B, then use split mode rather than relying on RIT or XIT. Check that your radio's split indicator is on before you key up. Calling on the DX station's own transmit frequency when he has said "listening up" is the classic mistake, and it can draw a lot of anger. If you accidentally transmit there, stop and correct. Don't keep calling while hoping it works.

Timing matters more than most people think. Call when the DX station finishes a QSO and is looking for the next caller, usually after his "QRZ" or after he sends the previous station's 73. Don't call over an exchange in progress. Tailending, meaning sending your call right as the previous QSO ends, is argued about. Many operators consider it acceptable if you wait for the last piece of the exchange and don't step on it. Others consider it poor practice if it means stepping on the previous station's final confirmation. Calling in the gap after the DX station says "QRZ" or "next" is safer. If he is clearly running a very fast rhythm, matching it, with short calls and no long gaps, is more effective than constantly jumping in randomly.

Callsign technique is simple but widely ignored. Send your callsign once or twice, not five times in a row. If the DX station returns a partial call, send only the part that needs correcting, or your full call once if that is clearer. On SSB, use standard ITU phonetics unless the DX asks for something different. Cute or non-standard phonetics are harder to copy through noise, especially for a non-native English speaker. On CW, speed and clean spacing beat a very high speed that sounds cramped. Use a speed that matches the DX station's own speed.

DX cluster spots help you find the opportunity, not decide the frequency. A spot can be busted, off frequency, or based on a station that is actually listening somewhere else. Treat it as an alert, then listen. If you do spot, include the transmit frequency, mode, and a useful comment like "UP 2" or "QSX 14.205". Avoid empty comments such as "QRZ?" that add noise to the cluster. Reverse Beacon Network or skimmer data can help you see whether a CW signal is being heard in your direction, but it shouldn't replace listening on your own station.

Which of these habits do you think is the biggest source of QRM in real pileups: calling on the DX frequency when it is split, calling out of turn, or sending your callsign over and over without listening?

  • Replies 2
  • Views 35
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the low bands, receive often matters more than the transmit signal. On 160 and 80 meters, many stations can be heard by the DX station only because they are quiet enough to be copied on the noise floor. That means a receive antenna such as a Beverage, loop, or flag can be worth more than a few extra dB on transmit. If you can hear the DX but not the stations he is working, the problem may be your local noise or your antenna pattern, not your power. It is worth testing your station's receive performance toward the target area before the DX is on the air.

Timing also changes with the band. On top band especially, the opening may last only a short time around the gray line at one end or both. If the DX is at the right sunrise or sunset window, don't waste it by chasing a single contact on the wrong mode or frequency. Also respect the local band plan and any DX window recommendations. Operating in the wrong part of the band can cause trouble even if the DX station is well placed.

For FT8 and similar modes, remember that DXpedition operation is not the same as normal operation. If the DX is using WSJT-X Fox and Hound mode, you need to be in Hound mode and follow the instructions. The Fox generally transmits in the lower part of the passband, and Hounds should call above that range, not on the Fox frequency. Calling on the wrong frequency or in the wrong mode can slow everyone down. Also keep in mind that digital modes often make pileups feel more orderly while still being very competitive, so make sure your clock, audio level, and software settings are correct.

  • Moderators

For DXpedition planning, the most useful way to think about it is as a logistics problem first and a radio problem second. Targets like Clipperton and Bouvet are rare because access is difficult: weather, landing conditions, permits, ship time, and the cost of getting people and equipment there can all decide whether an operation happens. That means the radio plan has to be robust. Typical planning issues include power, spare antennas and cables, band filters, station separation, interference between transmitters, and how to keep multiple bands and modes active without the stations disturbing each other.

Club Log is useful on both sides. For chasers, it can help you see which entities are most needed and where your own log has gaps, and many DXpeditions upload logs so you can check whether your contact appears. For planners, it helps show where demand is, which bands and modes may need extra attention, and whether a particular continent is under-served. Still, treat it as one input. Don't send repeated questions on the air asking whether you are in the log. Check the expedition's published log search or OQRS page after upload instead.

Etiquette ties it together. Don't tune up on the DX frequency, don't call after you've been logged, and don't answer questions meant for another station. If the operator is asking for a specific call area, stay out unless it is your turn. If you made a mistake, wait a moment and then try again. A pileup that stays orderly has a better chance of making many more QSOs than one that collapses into noise and repeated calling.

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.