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: plateaus, head copy, callsign drills and when to go on the air

ci_cover.jpg

Opening a thread on the 5-to-20 WPM climb, because the advice on it often contradicts itself. The trouble is that the skill changes along the way. What works at 5 WPM (learning the sounds) is not what works at 15 (copying words and phrases), and it stops working just when you need something new.

Here is a rough framework to argue with.

Sound, not dots and dashes. Start with characters sent at 18-20 WPM or faster, with extra space between them (Farnsworth spacing), or use a Koch-style trainer that adds characters one at a time at full speed. Counting dits and dahs builds a habit you will have to unlearn later. At 20 WPM a dit is 60 ms long (1200 ÷ WPM, in milliseconds), and nobody can count at that rate. You have to hear "di-dah" as a single sound, the way you hear a word.

The plateaus. Many learners stall somewhere in the low-to-mid teens. At that speed you can no longer process each letter separately, and you haven't yet learned to hear common words and letter groups as units. The usual fix is to stop pushing the speed and change what you practice: common words (THE, AND, YOU, FOR, WITH), common prefixes and endings (-ING, -ED, -TION), and callsign patterns. Another approach is to practice a little above your comfortable speed, where you miss characters and are forced to move on, then drop back to a speed where you get nearly everything.

Head copy. Writing every letter is a good way to learn, but it limits your speed because the pencil becomes the bottleneck. Try the switch when you can copy about 90% at a given speed on paper. Start with short, predictable material like callsigns, RST reports and names, then widen the material. Expect your accuracy to drop at first. Most people let the sound run a few characters ahead of the part they are actively thinking about, and stay relaxed when they miss a letter instead of dwelling on it.

Drills that target specific weaknesses. Random five-character groups are fine for learning characters. For on-air use, callsign drills (RufzXP is popular for this) and a contest simulator like Morse Runner train the exact things that matter: picking a call out of noise, handling numbers and portable/slash designators, and sending quickly in response. Practice the numerals as well, since they get less attention than letters and show up in every exchange.

Sending. A straight key is fine at the start, but past about 15 WPM many people move to paddles. Common settings to compare are iambic mode A vs. B (which affects whether you get an extra element when you release the paddles), a dah-to-dit weight near the default 3:1, and paddle contact spacing and tension that you can adjust until it feels easy. The usual rule is to set the keyer speed to what you can send cleanly, not what you can copy. Poor spacing between letters and words sounds worse on the air than a slightly slower speed.

Schedule. Short, frequent sessions generally beat long, rare ones. Twenty to thirty minutes a day is a typical target, split between a structured drill (new characters or callsigns) and something closer to real operating (listening to actual QSOs, a practice file, or a net). A fixed time of day makes it easier to keep up.

Software vs. ear. Decoders like fldigi and CW Skimmer are very useful for checking what you thought you heard, and for finding stations on a busy band. On a good, clean signal sent by a machine they do well. On a noisy band, with QSB or a hand-sent fist with uneven spacing, they often make errors a person would not. The risk is relying on the screen and never developing your own copy, so many people use software to confirm after trying to copy by ear first.

Questions for the thread: at what point did you move from a trainer to live QSOs, and how much did it help? Do slow CW nets work for building speed, or do they add pressure before you are ready? And if you are in the teens and stuck, what changed your plateau, whether that was a different drill, a different tool, or just time?

  • Replies 2
  • Views 14
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd separate two things you've lumped together: copy speed and operating speed. You can be a 20 WPM copier and still get lost in a QSO, because a real exchange is not random text. It's patterned: CQ, callsign twice, DE, your callsign, K. Name, QTH, RST, rig and weather, 73. Once those patterns are familiar, a lot of the content becomes predictable and your head copy has less to do. It's worth writing out a standard QSO template and drilling it until each element feels automatic.

For a first on-air contact, a few things tend to help. Pick a quiet part of the band rather than a busy one. Answer a CQ that is sent a bit slower than your limit. Keep your first reply short (callsign, RST, name) and use ? or AGN without embarrassment. Operators are generally used to being asked to repeat or slow down, and "QRS" is a normal request. If you freeze, a short "PSE QRS" is better than guessing.

On nets: a slow CW net, where one is available in your area or on your band, can be a low-risk way to practice because the exchange is structured and the speed is capped. I wouldn't treat it as a replacement for drills, though. It's mostly practice at the skill of staying calm while copying live, which is hard to train any other way.

  • Moderators

On plateaus, one practical point: check whether your problem is speed or noise. If you can copy a character-speed 20 WPM file with generous spacing but fall apart when the spacing shrinks, you're working at the word level. In that case more random characters won't help, but word lists, callsigns and plain text at your target speed will. If instead you drop characters when the signal is weak or the tone is different, the problem is with the sound itself. Then it helps to change the pitch, add noise or QSB in the trainer, and listen to real recordings.

A few specific things to try. Use a tone you find comfortable, usually somewhere in the 500-700 Hz range, and keep it constant between sessions. Run an easy session and a hard session on different days instead of making every session hard. Be careful with contest practice too: a speed contest is a great way to build call-sign copy and quick sending, but the exchange is so limited that it can inflate your confidence. Cut the speed back for ragchew-style listening so you also learn real conversation.

As for decoders, a fair test is to copy a file by ear first, then run the decoder on the same file and compare. The mistakes tell you where your weak characters are, which is something a plain trainer won't always show you.

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.