Skip to content

DX-University

A Guide for DXers and DXpeditioners

Menu
  • Home
  • DXING TOOLS
    • Best Practices for Dxing
    • DX Articles
    • Videos
    • Pileup Recordings
    • Publications
      • The New Dxer’s Handbook
    • How to Work Us
  • DXPEDITION TOOLS
    • Best Practices for DXpedition Operating
    • How We Will Operate
    • How to Work Us
    • Team Leaders’ Guidelines
    • DXpedition Basics
      • DXpedition Basics-Original
      • DXpedition Basics-2013
  • DX UNIVERSITY SESSIONS
    • Upcoming DX-University Sessions
    • Previous DX-University Sessions
    • DX-University Faculty
  • File Library
  • N7NG Blog
  • Contact Us
  • DXing Codes
    • DX Code of Conduct
Menu

Best Practices for Courteous and Efficient Dxing


1.Know the DX callsign and the location of the pileup by listening carefully to the DX station and the pileup before calling.

You are frequently admonished to “Listen, listen, listen and listen some more.” Just what should you be listening for? In order to have any chance of working a DXpedition, you must know who you are calling. Spots on the various spotting networks are often wrong. You should determine who you are calling by yourself. You must be able to hear when he starts and stops transmitting, and you must be able to hear and understand his instructions. You must be able to hear if he returns to your call.

It is also important to listen to the pileup. Depending on the situation, you might want to call exactly on the frequency of the last station worked. Or, you might want to call just up or down from the frequency of that station. You might need to pick a clear frequency and call there for a short time. Where you call next depends on the situation, and you need to listen in order to make that determination.

2.Beware of erroneous spots: Copy the DX station’s call sign yourself.

Many spots shown on the various spotting networks are incorrect. The best way to determine the identity of a DX station is to listen for yourself. You should be able to copy the station in order to work it. If you can’t copy the station well enough, you probably shouldn’t call since you might not know if he returns your call. Just how well you should be able to copy is a judgment call. Use your best information.

3.Be careful never to transmit on the DX frequency – learn how to use your radio properly.

One of the most disruptive things that any DXer can do is transmit – inadvertently or not – on a DX station’s frequency in a split situation. Everyone does it at one time or another. Learn how to use your radio instinctively. Practice looking at the controls of your radio frequently so you are sure you are not on the wrong frequency. Don’t put your radio on the DX frequency to “comment” about anything. You will likely forget to put it back, and you will become part of the problem.

4.Never interfere with an existing exchange of information.

You should never transmit near the station being worked while essential information is being exchanged. This is interference, and will only serve to slow the QSO process.

5.Always send your full callsign.

Sending a partial callsign should be avoided. Sometimes it may seem that since the DX station is responding to just a few letters of a callsign, and that is what you should do. That is not correct. The DX station is responding to just a few letters – a partial callsign – because that is all he heard. If you wish him to enter your full callsign in his log, give it to him!

6.Call once and then listen. Then call again, if appropriate. Try not to call during an existing QSO.

Perhaps the best calling scheme is to use full break-in – QSK. Using QSK, you can hear the DX station between your characters and thus you can hear him when he returns to a caller. Using QSK, you can quickly terminate your calling until the next opportunity. If you cannot use full break-in the next best method of calling is to call just once and then listen. If nothing is heard, you can call again… and again. After a few calls, you should list longer as you are probably transmitting simultaneously with the DX station.

7.Respond only if the DX operator calls you. One letter or number of your call is NOT enough reason to call.

Many DXers seem to respond after hearing only one letter of their call. This response is simply not productive: It is almost always a waste of time. If you hear two or three letters in the proper sequence, you should send only your callsign. Do not send a report until you hear your full callsign.

8.If the DX operator has sent your call correctly, do not repeat it unless required by licensing regulations.

Following up on item #7, if you do hear your callsign correctly, do not send it again unless required by licensing regulations. Many QSOs have been lost under poor propagation conditions because after the DX station had the call correctly, the DXer sent his callsign again and raised the question in the mind of the DX op whether he had it right initially. If  conditions don’t improve or become worse during this exchange, the Q may well be lost. Do not repeat your call if the DX op sends it correctly (unless required). He will keep what he has if he hears nothing else.

9.Do not call if the DX operator asks for other geographic areas.

This would seem to be common courtesy, and most people won’t be discourteous. A problem will occur when the DXer doesn’t listen carefully enough – probably because of poor conditions. Listen to any and all instructions the DX operator is transmitting. On phone it should be no problem to understand what he is asking for. Listen carefully as well on CW, but if you have difficulty copying, be even more careful. Do not call if he is asking another area. Do not call if you are in doubt.

10.To encourage the most courteous and efficient operation, operate in the way that you would expect others to operate.

When listening to a pileup, it is very easy to hear DXers who have forgotten how to behave properly. Try to train yourself to operate in a way that you would approve. It can be difficult, but you can succeed!

Upcoming DX-University Sessions

Recent Posts

  • September 1, 2025 by admin DX-University/HamCon Colorado 2025
  • September 1, 2025 by admin Welcome back to the DX-University
  • August 31, 2025 by admin Tuition Grants for DXU Students
  • August 31, 2025 by admin DXpeditioning Basics - Revised
  • August 31, 2025 by admin DXU Best Practices

About DX University

Established in 2011, The DX University™ is a multi-media program offering information, instruction and varied learning opportunities for DXers and DXpeditioners alike. The DX University has presented in-person sessions in Salt Lake City, in Visalia, California at the International DX Convention, and at several ARRL division conventions. Sessions have also been held at the W9DXCC Convention in Chicago and the ARRL Centennial Celebration in Hartford, CT.

The DX University Website is part of the DXU program. The site presents ideas and techniques for DXers and DXpeditioners aimed at improving operating skills and lessening the growing chaos on the DX bands. The media includes audio and video files as well as articles and programs from previous in-person presentations. Most of the information is available for your use. Contact us for details. Your input is always welcome.

Check here or in The DailyDX(tm) from time to time to see what's new!

© 2025 DX-University | Powered by Superbs Personal Blog theme

Powered by
...
►
Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
None
►
Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
None
►
Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
None
►
Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
None
►
Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
None
Powered by