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

Stuck between 5 and 20 WPM: what actually moves the needle (plateaus, head copy, drills, nets, keyer setup)?

ci_cover.jpg

I'd like to collect practical advice on the 5 to 20 WPM stretch, since most of the common questions seem to land here: why progress stalls, how to get off pencil-and-paper copy, and whether to trust a decoder. Here is the framework I'd start from, and I'd like to hear where people disagree.

Character speed first. The usual advice is to learn characters at a real sending speed of around 18 to 20 WPM and stretch the spacing between characters and words, rather than slowing the characters themselves down. This is the Farnsworth idea. A dit at 20 WPM is about 60 ms, while at 5 WPM it is 240 ms. If you learn the 5 WPM sound, every character is a long melody you have to count, and that habit is hard to unlearn later. The Koch method follows the same logic: start with two characters at full speed and add one at a time once you copy about 90 percent of a session.

Plateaus. Two seem common. One shows up around 10 to 13 WPM, where you can no longer count dits and dahs and must recognize the whole character as a sound. The other shows up in the high teens, where copying letter by letter costs you more and more, and you have to start hearing whole words and common prefixes. Both usually respond to the same fix: practice a bit above your comfortable speed, accept some missed characters, and don't stop to puzzle over a miss. Dwelling on one dropped letter usually costs you the next three or four.

Head copy. It tends to come in stages. Start with short, very common words (the, and, you, name, rig, antenna) and say them silently as they arrive. Then move to callsigns and short exchanges like RST, name, and QTH, then to full phrases. Writing everything down isn't wrong, but if you only ever write, your brain stays in character-by-character mode. A decent compromise is to write only the callsign and numbers during practice QSOs and let the rest go by in your head.

Drills. Random-character drills build raw recognition. Word and callsign drills build the pattern-matching you actually use on the air. Callsigns are useful because they are short, irregular, and carry real stakes in a contest or pileup. Programs like Morse Runner simulate pileups and let you adjust speed and noise. Spend a short block of each session on callsigns only.

Keyer and paddles. Poor sending can hold back your copying more than people expect, because you learn to hear your own mistakes. Set the keyer speed to a pace you can send cleanly, not the fastest you can hit. Keep weight near the default (about 3:1 dah-to-dit) until your timing is solid. Sidetone pitch is personal, but somewhere in the 500 to 700 Hz range is a common comfortable choice. Keep paddle spacing and tension light enough that you aren't fighting the paddle at speed. Iambic A and B differ in whether the keyer adds a final element when you release both paddles. Try both, and use whichever matches your hand rather than whichever someone says is better.

Ear versus software. A decoder is fine for checking your copy afterwards and for confirming a callsign. As a primary tool it has real limits. Fading, noise, QRM, and irregular spacing (many operators have a distinctive fist) can all produce garbage. If you always glance at the screen, you also won't develop the skill you are trying to build. A reasonable rule: copy by ear first, then check with software only after the fact.

Schedule. Short daily sessions of 15 to 30 minutes usually beat one long weekly session, especially because the skill consolidates between sessions. A sample week might mix new-character or speed-push drills, callsign practice, listening to real on-air CW, and one low-pressure QSO or net check-in. Rest days are fine.

Getting on the air. Slow-speed CW nets and structured events like short timed contest sessions can bridge the gap between drills and real operating. Contests are good for speed building because the exchange is predictable, so you learn to copy the parts that matter. Starting by only answering stations calling CQ at your speed, and sending a standard exchange, lowers the pressure.

So what's worked best for you at each stage, and what advice do you think is overrated?

  • Replies 2
  • Views 32
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

One thing I'd add to the plateau discussion is that the plateau is sometimes a measurement problem. If you test yourself with random five-character groups and then listen to real QSOs, the two speeds can differ a lot. Real text has redundancy. You can guess a missing letter from context, so real-world copy is often easier than a random-group test, but it also lets you hide weaknesses. It helps to keep both kinds of practice in the schedule and track them separately, so you can tell whether you have a character problem or a word and context problem.

On the keyer, I agree about not setting the speed higher than you can send cleanly. A practical test is to record a minute of your own sending and play it back at the same speed. If you can't copy your own recording easily, slow down. Spacing errors between letters are the most common culprit, and they make your sending harder for others to copy, especially the sloppy gap that turns 'ME' into 'ANT' or similar mix-ups.

  • Moderators

On the decoder question, I'd separate two uses. Using software as a training aid, like a generator that sends you text and lets you check your copy against the answer, is a good idea. Using a decoder to read a live signal while you're trying to learn is different, because it replaces the listening. The first builds the skill, the second can quietly stand in for it. That said, decoders are handy for checking whether a weak callsign you thought you heard was right, and some people use them to double check while logging in a contest.

For head copy, one tip that people often suggest is to stop trying to hear letters at all once you hit the mid-teens and just listen for rhythm. Common words and callsign suffixes have a distinct shape. It feels like you're giving up accuracy, but it's usually the point where you start to move forward. Pair that with short, regular sessions on callsigns and common exchange items, and nets or a contest weekend become a good test of whether it's working. If you drop a lot of characters in your first contest, that's normal, not a sign you should go back to 10 WPM.

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.