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

Getting from 5 to 20 WPM: what actually changes at each stage (plateaus, head copy, keyers, and decoders)?

ci_cover.jpg

This thread is for sorting out what to practice at each stage of CW speed building, and what to stop doing once it quits working. The pattern most people describe is that 5 to 10 WPM goes fairly quickly, 10 to 15 stalls, and somewhere past 15 the whole skill starts to feel different. It is worth asking why, because the fixes differ from stage to stage.

At 5 WPM with full-length characters, most operators are still translating sound to letter to word. Around 10 to 13 WPM that approach runs out of time. The next character arrives before the last one has been resolved, and copy falls apart. This is the classic plateau. The usual advice is to send characters at 18 to 20 WPM with extra space between them (Farnsworth-style spacing), or to use a Koch-style trainer that starts at full speed with two characters and adds new ones as you reach about 90 percent accuracy. Either way, the goal is to hear each character as a single rhythm, not as a count of dits and dahs.

Head copy is the next step. That means holding words and then phrases in your head instead of writing every letter. A common progression is to copy on paper, then write only the first letter of each word, then write nothing during common words and only jot callsigns and numbers. Many people find that putting the pencil down too early makes them panic and lose the thread, so the move has to be gradual.

There are several other areas I would like opinions on:

First, drills. Random groups build character recognition, but real-world speed comes from words, common abbreviations, and callsigns. A callsign trainer is useful because callsigns are the part of a QSO where you cannot guess from context.

Second, on-air practice. When is a new operator ready for a real QSO, a slow CW net, or a contest? What helps most in the first few contacts?

Third, sending. Paddle tension, contact gap, keyer mode (iambic A or B), weight, and sidetone pitch can all affect how comfortable sending feels at 15 to 20 WPM. What are sensible starting settings?

Finally, ear versus software. A decoder is a convenient way to check your copy, but does it get in the way of learning?

Share what has worked, what hasn't, and the daily or weekly schedule you would recommend for someone aiming at 20 WPM.

  • Replies 2
  • Views 31
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the plateau: it is usually a recognition problem, not a speed problem. If you can copy 12 WPM at 95 percent on a good day but make mistakes at 14, check how you are listening. Are you still counting elements, or waiting for a character to finish before you decide what it was? If so, the fix is to practice a bit faster than your comfort level, with slightly longer gaps. Run at about 18 to 20 WPM character speed and set the effective speed to whatever you can handle. Then close the gap over weeks. Short sessions, 15 to 30 minutes every day, usually beat a single long weekend session because recognition builds with repeated brief exposure. If a session ends with you guessing, stop. Extended sloppy copy tends to reinforce bad habits.

For drills, split the time instead of doing one thing. A reasonable weekly mix is some new-character or random-group work, some real words and common CW abbreviations, and a callsign drill. Callsigns are good practice because the letters and numbers come in random order, and you have to get them exactly right. Tools like RufzXP, which raises the speed as you succeed, are designed for this. Do not skip numbers and the punctuation used in exchanges (the slash, the question mark, and a few prosigns). They cause trouble later if you only practice letters.

On head copy, try this progression. Copy everything on paper. Then copy words but only write down the first and last letters. Then listen to whole words and write nothing but callsigns, names, and numbers. If you drop a word, let it go and keep listening for the next one. Dwelling on the missed word means you lose the next three. That habit, letting go, is probably the hardest part of getting past 15 WPM.

  • Administrators

Here is a different angle on the on-air side and the equipment. For first QSOs, standard contacts are the best preparation because they are predictable: callsigns, signal report, name, location, rig and power, then 73. If you have practiced those exchanges, you can fill in the blanks from the expected structure even when you miss letters. Practice software that simulates a contest or a ragchew helps, and so does recording a real QSO off the air and copying it later at your own pace. Slow-speed CW nets and special-event stations are good places to start, because many operators will slow down on request. The specific nets, times, and frequencies change, so check current listings from a club or organization instead of relying on old information. In contests, a good plan is to start by listening and copying callsigns without transmitting, then make a few calls once the rhythm of the exchange is familiar. Short, fixed-format exchanges make contests surprisingly friendly for building speed.

On keyers, there is no universal setting, but some starting points are reasonable. A sidetone between about 500 and 700 Hz is comfortable for most people, and matching it to the pitch you listen to in the receiver reduces fatigue. Keep standard spacing, with a dah three times the length of a dit and normal weight, before experimenting. The paddle gap should be small but not so small that you get accidental double contacts, and the tension should let you rest your fingers without the paddle triggering. For mode, iambic A and B differ mainly in whether a final element is added when you release both paddles. Try both and keep the one that gives you fewer extra dits. If your sending is cleaner than your copy, that is normal, but listen to recordings of yourself because sloppy spacing is hard to hear while you are sending.

As for software decoders, they are fine for checking an answer after you have tried to copy, or for confirming a callsign you are unsure of. The problem is using them in real time. They struggle with fading, noise, and irregular timing, and watching the screen stops you from training your ear. A good compromise is to copy first and look afterward. Software also cannot help you in a pileup or on a weak band, which is where ear-trained recognition pays off.

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.