ⓘ 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 — 70cmvia PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHzDXSpotterInfo
Recent spots—
Select a band above to load spots
Ready — select a band to fetch live spots
Breaking pileups on rare DX: split operation, timing, and knowing when to stay quiet
Here is a discussion starter on pileup technique for rare entities, especially the Clipperton or Bouvet type of target. These are places with few operating days, short band openings, and a huge number of callers. I would like to compare notes on what actually works and what only feels like it should.
1. Listen first, longer than feels necessary. Most failed calls come from not knowing how the operator is working the pileup. Listen for several minutes. Does he say "up 5 to 10" or "up 1 to 5"? Does he work by call area, by continent, or by the last two letters of the suffix? Is he taking a call, confirming it, and moving on, or letting the pileup run? Every one of these answers changes what you should do. If you did not hear the DX say where he is listening, find out before you press the key. On SSB, tune your second VFO across the split window and see where the callers are stacking up.
2. Split operation basics. The DX transmits on one frequency and listens on others, so callers do not sit on top of him. You need RX on the DX frequency and TX in the window he announced. Check that your rig really is in split mode and that the TX VFO is where you think it is. Before calling, confirm you are not transmitting on the DX's own frequency. Accidental transmission on the DX frequency is one of the fastest ways to get a pileup annoyed. Some operators use a wide window to spread callers out. Others use a narrow one and shift it often. Pick a spot in the window, and do not simply copy the loudest cluster.
3. Timing and tailending. The usual advice is to call when the DX has finished a QSO and is about to listen again. Tailending means starting your call just as the previous QSO is ending. Done a beat too early, it steps on the contact in progress. Done well, it saves a few seconds in a pileup where every second counts. On CW, a short call sent once or twice is usually better than a long string of repeats, and you should listen between calls. A long CQ-style repeat sent without stopping can cover the very answer you are waiting for. On SSB, say your call once or twice, cleanly, with standard phonetics. Avoid inventive phonetics. A well-known phonetic alphabet is much easier to copy through QRM than a clever one.
4. Do not send unnecessary extras. The DX needs your callsign, then a report if he asks. Skip "please," the DX's own callsign repeated over and over, or your name and QTH unless he requests it. If he sends a partial call, such as "K1?" or just your suffix, answer only when your call fits the partial. Calling when you do not fit the partial causes more QRM and slows everybody down.
5. DX cluster spots: useful, but not gospel. Spots tell you something is on the air and approximately where. They do not tell you the DX's listening frequency or whether the spotted frequency is correct. Spot errors happen, and a busy pileup can lead to a busted spot spreading. Use the spot to find the signal, then confirm by ear. If you spot a station yourself, include the frequency, the call, and the mode, and note "UP" or the split information only if you actually heard it.
6. Top band and low-band DXing. On 160 m, 80 m, and 40 m, the challenge is often noise rather than raw power. A separate receive antenna (Beverage, flag, loop, or similar) can make the difference between hearing the DX and not hearing him. Gray-line timing and the path over the DX's sunrise or sunset help a lot. DX windows exist for good reason on the low bands, and there is generally an agreed practice of keeping the DX portion clear. Check your local band plan rather than assuming it. On 160 m particularly, quiet listening matters. If someone is calling on top of a weak DX signal, nobody gains.
7. Digital modes and Fox/Hound. For FT8 DXpedition mode, read the WSJT-X guidance and the DXpedition's own instructions before you transmit. Fox/Hound has its own conventions about where Hounds call, what frequency range to use, and what to do after a report. Doing something different from the instructions slows the whole operation. If the team states its rules, follow them to the letter.
8. Club Log and planning. Club Log's most-wanted data can show which entities are statistically hard to work, and an expedition's log search can show whether you are already in the log. That is useful for the "did I get in?" question without sending needless repeat calls. For planning your own chase, check which bands and modes you still need for the entity, and use propagation prediction tools to find realistic windows. Then be ready at those times. For Clipperton or Bouvet type targets, weather, landing conditions, and short operating windows can change a schedule quickly, so expect last-minute changes. Do not build your plan around a single announced date.
9. Etiquette. Do not tune up on the DX's frequency. Do not call after the DX has said "QRZ" without your suffix being included. If you are told to stand by, do. Do not argue on frequency about who was calling when. Keep your comments off the DX frequency entirely. If you are not hearing him, the cause is probably propagation or your station, not the DX operator.
What techniques have you found most useful on a hard-to-work band or entity? Is there anything you would add to or disagree with above?
Here is a discussion starter on pileup technique for rare entities, especially the Clipperton or Bouvet type of target. These are places with few operating days, short band openings, and a huge number of callers. I would like to compare notes on what actually works and what only feels like it should.
1. Listen first, longer than feels necessary. Most failed calls come from not knowing how the operator is working the pileup. Listen for several minutes. Does he say "up 5 to 10" or "up 1 to 5"? Does he work by call area, by continent, or by the last two letters of the suffix? Is he taking a call, confirming it, and moving on, or letting the pileup run? Every one of these answers changes what you should do. If you did not hear the DX say where he is listening, find out before you press the key. On SSB, tune your second VFO across the split window and see where the callers are stacking up.
2. Split operation basics. The DX transmits on one frequency and listens on others, so callers do not sit on top of him. You need RX on the DX frequency and TX in the window he announced. Check that your rig really is in split mode and that the TX VFO is where you think it is. Before calling, confirm you are not transmitting on the DX's own frequency. Accidental transmission on the DX frequency is one of the fastest ways to get a pileup annoyed. Some operators use a wide window to spread callers out. Others use a narrow one and shift it often. Pick a spot in the window, and do not simply copy the loudest cluster.
3. Timing and tailending. The usual advice is to call when the DX has finished a QSO and is about to listen again. Tailending means starting your call just as the previous QSO is ending. Done a beat too early, it steps on the contact in progress. Done well, it saves a few seconds in a pileup where every second counts. On CW, a short call sent once or twice is usually better than a long string of repeats, and you should listen between calls. A long CQ-style repeat sent without stopping can cover the very answer you are waiting for. On SSB, say your call once or twice, cleanly, with standard phonetics. Avoid inventive phonetics. A well-known phonetic alphabet is much easier to copy through QRM than a clever one.
4. Do not send unnecessary extras. The DX needs your callsign, then a report if he asks. Skip "please," the DX's own callsign repeated over and over, or your name and QTH unless he requests it. If he sends a partial call, such as "K1?" or just your suffix, answer only when your call fits the partial. Calling when you do not fit the partial causes more QRM and slows everybody down.
5. DX cluster spots: useful, but not gospel. Spots tell you something is on the air and approximately where. They do not tell you the DX's listening frequency or whether the spotted frequency is correct. Spot errors happen, and a busy pileup can lead to a busted spot spreading. Use the spot to find the signal, then confirm by ear. If you spot a station yourself, include the frequency, the call, and the mode, and note "UP" or the split information only if you actually heard it.
6. Top band and low-band DXing. On 160 m, 80 m, and 40 m, the challenge is often noise rather than raw power. A separate receive antenna (Beverage, flag, loop, or similar) can make the difference between hearing the DX and not hearing him. Gray-line timing and the path over the DX's sunrise or sunset help a lot. DX windows exist for good reason on the low bands, and there is generally an agreed practice of keeping the DX portion clear. Check your local band plan rather than assuming it. On 160 m particularly, quiet listening matters. If someone is calling on top of a weak DX signal, nobody gains.
7. Digital modes and Fox/Hound. For FT8 DXpedition mode, read the WSJT-X guidance and the DXpedition's own instructions before you transmit. Fox/Hound has its own conventions about where Hounds call, what frequency range to use, and what to do after a report. Doing something different from the instructions slows the whole operation. If the team states its rules, follow them to the letter.
8. Club Log and planning. Club Log's most-wanted data can show which entities are statistically hard to work, and an expedition's log search can show whether you are already in the log. That is useful for the "did I get in?" question without sending needless repeat calls. For planning your own chase, check which bands and modes you still need for the entity, and use propagation prediction tools to find realistic windows. Then be ready at those times. For Clipperton or Bouvet type targets, weather, landing conditions, and short operating windows can change a schedule quickly, so expect last-minute changes. Do not build your plan around a single announced date.
9. Etiquette. Do not tune up on the DX's frequency. Do not call after the DX has said "QRZ" without your suffix being included. If you are told to stand by, do. Do not argue on frequency about who was calling when. Keep your comments off the DX frequency entirely. If you are not hearing him, the cause is probably propagation or your station, not the DX operator.
What techniques have you found most useful on a hard-to-work band or entity? Is there anything you would add to or disagree with above?
Link to comment
https://www.hamradiobase.com/forums/topic/11729-breaking-pileups-on-rare-dx-split-operation-timing-and-knowing-when-to-stay-quiet/Share on other sites