Basic CW Operating Procedures

Back when I first got on the air in 1978, CW QSO’s had a pretty standard format. That format didn’t change much until the last few years. But today there’s quite a hodgepodge of operating procedures out there. Most of the time it works, but it’s not uncommon to hear a downright jumbled mess — even from a CW operator who has been on the air long enough to send and receive at 10 wpm or more.

It’s important to learn good operating procedure, not just because it sounds polished but because it serves a practical purpose. You can get away with sloppy operating procedure under perfect conditions, but not if your signal is weak or if there’s much QRM, QRN, and/or QSB. Even under perfect conditions, you’re making the person at the other end work harder if you’re constantly surprising him with your own odd way of operating. Under poor conditions, he may miss some of what you’re trying to say. And even if he succeeds at copying what you’re saying he may well be relieved when the ordeal is over.

I’m not going to get into all of the details of good operating procedure here, but I would like to discuss some basics.

General structure
There is a general structure to a CW QSO that most operators expect. After establishing contact, the first transmission should stick to the basics — RST, QTH, and name. You don’t know yet how well the other fellow is copying you; if you’re a 329, you’re going to torture him if you go on and on about your rig, your power, your antenna, the weather, etc. Furthermore, you might lose the opportunity to hear even the basics from the other fellow if band conditions deteriorate while you’re sending all this on the first transmission. So stick to the basics — and do send them. Here’s the way we all used to do it years ago:


Note the use of BT. That seems to have fallen out of favor, but once upon a time it was the standard way of changing the subject. The most important thing I want to point out here is to preface each of the three major elements of this first transmission with their labels: RST, QTH, and NAME. It takes a few seconds longer than sending something like, “UR 579 IN GRANITE FALLS, MN OP TODD,” but it is worth it. As the FISTS club puts it, “Accuracy transcends speed.” Update: I have noticed that OP is often used instead of NAME, especially with DX stations. Since it is widely recognized it’s perfectly acceptable.

The operator replying to this first transmission sends the same three basics in the same way. If he’s inclined (and if he’s received a reasonably good RST) he will probably go on to talk about his station, the weather, etc. As it turns into a ragchewing session you can pretty much send whatever you want.

Procedure signals
Just as the use of BT has fallen out of favor, so have other procedure signals fallen on hard times. I often hear them sent incorrectly and used improperly. Remember what these are — they are procedure signals. Learn to send them well and to use them well, and your operating procedure will improve substantially. The ones most commonly used are AR, AS, BK, BT, K, KN and SK.

Notice the line that appears over each one of the two-letter procedure signals. That means you send the two letters as if they are one character. For instance, KN isn’t sent as dah-di-dah dah-dit (KN) but dah-di-dah-dah-dit (KN).

  • AR End of message: Send this after you are completely done sending everything — everything, that is, but call signs and KN. If it’s your last transmission, use SK instead.
  • AS Wait:You might hear this if you’re working an experienced operator. If you hear this, the next thing you hear will probably be silence — maybe he has to answer the phone or something. Or maybe you’ll hear him hold his key down while he fiddles with his antenna tuner. Don’t start sending — he’ll start sending when he’s ready. This is a handy procedure sign to know, if you ever need to take a break yourself.
  • BK Break: This might be used by a station who wants to enter an ongoing QSO — he’ll send BK between transmissions to see if they’ll let him in and turn their QSO into a “roundtable.” With the advent of full QSK keying, this also became popular among experienced CW operators who could interrupt one another right in the middle of a transmission (perhaps to answer a question or clarify something). But most commonly BK is used to rapidly turn the conversation over to the other station without sending any call signs. For instance, an operator might send something like “HOW CPY? BK” and then cease his transmission. If this happens to you, reply by simply sending BK and answer his question. You can go back and forth in this manner for as long as you want, but don’t forget to obey the law by identifying yourself with your call sign at least every 10 minutes.
  • BT Separator: Usually used to change the subject, even if it’s just to go from sending RST to sending QTH. (If you hear the other fellow sending BT several times, it’s because he’s trying to think of what he wants to say next!)
  • K Over: This invites anybody listening to reply. Send this after you’re done calling CQ. But if you’re in a QSO, you almost always want to use KN, not K.
  • KN Over (to specific station): Send this after signing over to the other station in a QSO, e.g. NØART DE NØIP KN. KN tells other listeners that they’re not welcome to call you yet — you just want the station you’ve named to reply. Don’t send this after calling CQ — send K instead.
  • SK End of contact: This lets the other operator know that you want to end this QSO, and this is your last transmission. Usually sent in place of AR right before signing over to the other station.

The Handshake
It has long been customary to send “dit dit” at the very end of a QSO, like a final handshake. On the very last transmisssion, the sending station sends “dit dit” and then the other station replies “dit dit,” and that’s the end. Or (like we did in the old days) you’ll hear the first station send “dit di-di-dit dit” and wait for the second station to send “dit dit” (“shave and a haircut, two bits!”).

But this is often fumbled. Here’s how it usually goes wrong. The first station to send his final farewell, e.g. TNX FER QSO HPE CU AGN 73 73 SK NØART DE NØIP KN, knowing full well that the other station still plans on bidding him farewell in the same manner, goes ahead and sends “dit dit” at the end of his transmission. Naturally, the other station ignores this faux pas, goes on to send his last transmission, and only when he is done does he finally offer “dit dit” for the other operator to send his own “dit dit” again.

Now, this is obviously not the most important point of operating procedure, but why not do it right? No need to be socially awkward at the end of a good QSO!

I’ve only covered a few basics here. For more on CW operating procedures, it’s worth checking out something like But the best way to learn good operating procedures is simply to pay attention to what proficient operators are doing — especially as you get into more advanced operation, like handling DX pileups. The more listening you do before you wade in, the better operator you will be.



Filed under CW, Operating Practice & Procedure

8 responses to “Basic CW Operating Procedures

  1. Good morning, great run down of the CW QSO and the way to go about it. I am the first to admit I may not use all the proper AR and SK’s….but is sure is a learning curve. Great post that has cleared up some questions on my part. As for sending of the code no and then I come across code that seems to have no break between letters. It all just flows into one long confusing letter. Those are the hardest op’s I have understanding. Anyway great post and nice blogs.
    dah dah dah dit dit dit dit dit dah dah

  2. Todd Mitchell

    Thanks for the encouragement, Mike!

    You’re right, there are some pretty sloppy fists out there today. One of the problems I’ve observed is improper use of bugs — rapid, perfect dits mixed with variable-length dahs sent at seemingly random intervals between the other dits and dahs. I certainly don’t want to discourage these operators! On the contrary, these operators deserve our admiration for keeping the ol’ bug alive. But bugs do require more skill than iambic paddles.

    It wouldn’t hurt to listen to ourselves send code once in a while to see if we’ve slipped into bad habits. Even after several decades of experience, I recently caught myself sending overly-long dahs with my straight key. Anybody know of a convenient way to record our own code?

  3. Oh and the dah dah dah dit dit dit dit dit dah dah was meant as a funny as that was sent to me instead of the dah dah dit dit dit dit dit dit dah dah….:)

  4. Todd Mitchell

    Maybe that’s the new “Best 73,” eh?

  5. Pingback: CW Abbreviations | Elmering

  6. Nolan Kienitz

    Mike – Great article as I continue to improve my lagging CW skills. Been licensed since early 1970s and progressed to Extra during ‘code required’ years, but just didn’t get serious about CW until past year or so. I’m retiring now and want to spend time exercising my CW. 73 – Nolan K. – KI5IO

  7. William Hansen

    Great article on cw. One correction on the use of AR. That is used at the end of a message as in traffic handling. When a station had several messages to send they were separated by AR. Rag chewing is not a message but conversation. You don’t need to tell someone you are done talking – they will know it! Keep bounding that brass!

  8. Don Evilsizor

    Great to read info on CW for some re-education.
    Concerning the AR at the end of a Radiogram or message I usually send
    ARN if no further traffic from my station or ARB 1, 2 or 3 whichever the
    case may be to indicate more to follow. Still have my old Novice Straight Key, but my CW has sadly deteriorated over the years. I have a Y connector for the old key and also going to my keyboard. So mostly send via the keyboard but
    can tap the old key at any time. I copy on my notebook paper for most QSO’s.
    My FIST nr is 5668 & usually stop by the FIST table at Fort Wayne hamfest or Dayton. Also Indiana has QIN on 3535 KHZ, 8 am EST 7 days a week. And the ICN (Indiana Code Net) for slow code at 7 pm EST. More info on
    I used to copy a lot of code on my first army hitch in Germany starting in 1960 as that was my job in the Army Security Agency (ASA). Later on 2nd hitch and more went to copying teletype. 73 all es tnx for post abt CW.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s