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 moves the needle, and where do people stall?

ci_cover.jpg

Starting a thread on the 5-to-20 WPM climb, because the advice on it tends to be scattered across a dozen sites and the same few questions keep coming up. Here is a rough framework, and I'd like to hear where it breaks down for people.

First, the foundation. Whatever method you use, the goal is to hear a character as a single sound, not as dits and dahs you count and translate. That is why the Koch method (characters sent at full speed, starting with just two and adding one at a time) and Farnsworth spacing (characters at 18 WPM or more with extended gaps) both work. The character speed stays high enough that counting is impossible. If you learned at a slow character speed and are now stuck around 8 to 10 WPM, the habit of counting elements is often the cause, and the cure is to go back and relearn the shapes at a higher character speed.

Second, plateaus. Many people report slowing down somewhere around 10 to 13 WPM, and again in the high teens. The usual explanation is that you are moving from recognizing letters to recognizing whole words and common patterns, and that transition feels like going backward before it clicks. Things that tend to help: short sprint sessions at a speed slightly above where you are comfortable, then a drop back to a comfortable speed so the sprint speed starts to feel easier. Another is to stop trying to copy 100 percent and accept missing a letter. If you stop to puzzle over a missed character, you lose the next three.

Third, head copy. Writing every letter is a fine way to learn, but it caps you at your pencil speed, and it often caps you well below your ear speed. A common way to transition is to stop writing letters and write only words, then only numbers and callsigns, then nothing. Common words such as THE, AND, FOR, YOU and RIG, plus prosigns and Q-signals, are good first targets because you start hearing them as units. Try to stay a character or two behind the sender instead of racing to decode each letter the instant it ends.

Fourth, drills. Callsign practice is its own skill, because callsigns are random strings with no context to help you guess. RufzXP is built for this and adapts its speed to your results. Morse Runner simulates a contest pileup, which is a good way to practice pulling a call out of noise. LCWO.net and the CWops CW Academy materials are other widely used resources. A mix of plain-text words, random groups, callsigns and real on-air recordings works better than any one of them alone.

Fifth, on the air. A standard QSO is quite formulaic: CQ, callsigns, RST, name, QTH, rig and weather, then 73 and a closing prosign. Knowing the skeleton means you only have to copy the variable parts. If the other station is too fast, QRS is the standard polite request. Slow nets and practice sessions exist for exactly this reason, so it is worth checking what is active in your region. Short weekly mini-contests and full weekend contests are good for speed because the exchange repeats constantly. You can run in search-and-pounce mode, copy a few exchanges, and ask for repeats without embarrassment.

Sixth, sending. Paddle setup matters more than people expect. Iambic mode A and mode B differ in what happens when you release the squeeze, with mode B adding one extra element, so choose one and stay with it long enough to build muscle memory. Keep weight near the default at first, set sidetone somewhere comfortable (500 to 700 Hz is typical), and adjust paddle gap and tension so you are not fighting the paddle. Try not to let your sending speed run ahead of your receiving speed, because sloppy sending trains sloppy habits and makes you harder to copy.

Finally, software decoders. They can be useful for checking your copy afterward, especially when you record a QSO, copy it by ear and then compare. As a primary tool they struggle with QSB, noise, an uneven fist and drifting speed, and watching the screen pulls your attention away from the sound. Most people who want head copy find that relying on a decoder works against them.

A few questions for the group. What speed range gave you the biggest wall, and what got you through it? Do you split your practice time between receiving and sending, or focus on one? And how long did it take you to go from writing everything down to copying in your head?

  • Replies 2
  • Views 8
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing I'd add about schedules: frequency beats duration. Fifteen to thirty minutes a day tends to do more than one long weekend session, because fatigue sets in fast and copy gets worse once you are tired. A split like this is reasonable: roughly a third on new characters or speed pushes, a third on words and callsigns at a comfortable speed, and a third on real or recorded QSOs. Change the proportions as your weak spot changes.

For the plateau itself, it helps to have a way to measure it. Pick a fixed test, for example a set of 50 random callsigns or a standard text, and score it weekly at the same speed. Otherwise a plateau can just be a feeling, and you can't tell whether you are stuck or only copying harder material. If the score is flat but you feel better on air, that matters too, since real QSOs reward context in a way drills don't.

On the paddle question, mode A versus mode B matters less than consistency. If you switch keyers or radios and your sending suddenly feels off, check the mode and the memory settings first.

  • Administrators

I'd push back a little on dropping the pencil early. Writing is not what limits most people at 10 to 12 WPM. Their recognition is still letter by letter, and if you take the pencil away before that changes, you just lose characters faster. A middle step is to copy only the first letter of each word, or only digits and callsigns, while listening to the rest as words. That forces word-level listening without leaving you with nothing.

On decoders, I'd use them as a feedback tool, not as a reference during the session. Record the QSO, copy it by ear first, then run the recording through the decoder and look at the differences. Where your copy and the decoder disagree, listen again. Sometimes you misheard, and sometimes the decoder choked on a bad fist or a fade, which is also useful to know. Just keep the screen out of sight while you are actually listening.

For nets, listen before you transmit. Hearing how experienced operators handle fills, repeats and prosigns teaches you the rhythm of the exchange, and most people there are happy to slow down if you ask politely with QRS.

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.