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 412.9 km/s
Aurora 1
Updated 14:00 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 wpm to 20 wpm: plateaus, head copy, drills, and what's worth practicing

ci_cover.jpg

Starting a thread on the 5-to-20 wpm climb, because advice on it tends to be scattered across blog posts, club handouts, and old forum arguments. Here is a rough framework. Poke holes in it.

The first stretch (about 5 to 12 wpm) is mostly about making character recognition automatic. The usual advice is to learn characters at a fast character speed, around 18 to 20 wpm, with extra space between characters and words (Farnsworth timing). The Koch method works on the same idea: start with two characters at full speed and add one at a time once you reach about 90 percent copy. Either way, you want to hear "di-dah" as the sound of A, not count dits and dahs.

The plateau most people report is somewhere around 10 to 15 wpm. That is where translating each character consciously stops working, because the next character arrives before you have finished decoding the last one. Pushing harder at the same method tends to stall. What usually helps is copying in short bursts slightly above your comfort speed, so you have to let go of individual letters and catch common words and patterns.

Head copy is the goal on the far side of that plateau. At first it means you do not write every letter down. You keep a few words in your head and write only numbers, callsigns, or names. Starting with common short words (the, and, you, rig, name, QTH, RST) and frequent prefixes and suffixes helps a lot, since those become single sounds instead of strings of letters.

Questions for the thread:

1. For people who got past the mid-teens, what changed your practice? More drilling, a different method, or on-air time?

2. How much do you rely on software decoders, either while learning or as a check on what you copied?

3. What keyer and paddle settings made sending feel natural without pushing you to send faster than you can copy?

  • Replies 2
  • Views 37
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the plateau: it is often not one problem but two, and they need different fixes. One is character recognition that is still not automatic for the less common letters (Q, J, X, Z, numbers, punctuation). The other is word-level processing. A quick test is to take a plain text file with the 100 or so most common English words and have a trainer send it at your usual speed with normal spacing. If you copy it fine but struggle on real QSOs, the issue is probably the lack of context and noise tolerance, not the characters.

A practice schedule that holds up for most people is short and regular, not long and occasional. Fifteen to thirty minutes a day beats a two-hour weekend session, because the recognition skill consolidates with repetition and sleep. A simple split for a half hour: ten minutes of new or weak characters, ten minutes of word or callsign drills just above your comfortable speed, and ten minutes of ordinary text at a speed where you get roughly 90 percent without strain. Keep the fast material as a stretch, not the main diet.

For callsign drills, look at tools built for them, such as RufzXP, which sends callsigns and adapts speed to your accuracy, or Morse Runner, which simulates a contest pileup with noise and QSB. Callsigns are good practice because there is no context to guess from. You either got the characters or you did not. A simple method is to type the callsign, check it, and repeat the ones you missed.

Also, don't switch to full-speed everything too early. Dropping the speed of the whole session to mimic on-air conditions can reinforce counting. Keeping the characters fast while stretching the spacing preserves the sound shape of each letter.

  • Moderators

On decoding by ear versus software: they are useful for different things. Decoders like fldigi's CW mode or those built into some rigs and apps do reasonably well on clean, steady, machine-sent code. They fall apart on fading, noise, irregular spacing, and hand-sent code with variable weighting. Many operators use them as a cross-check on callsigns they are unsure of, but if you lean on the screen while learning, you tend to look instead of listen, which defeats the point. A reasonable rule is to copy first, then check.

For sending, a few settings are worth thinking about. Standard timing is a dah three times a dit, with one dit of space inside characters, three between characters, and seven between words. Most keyers default to that, and heavy weighting makes your code harder for others to read. Set the keyer speed to about the speed you can comfortably copy, so you do not end up sending faster than you receive. Otherwise the person answering will probably send back at your speed and you will be lost.

On paddles, iambic mode A versus B is mostly a matter of what you learned on. Mode B adds an extra element when you release the paddles after squeezing, and mode A does not. If you notice stray dits or dahs at the end of letters like C or K, check the mode and paddle tension before blaming your fingers. Contact spacing and tension that are too tight or too loose are common causes of sloppy sending. Adjust gradually and give yourself a few sessions to adapt.

For on-air practice, slow-speed nets and CW practice sessions are a good step between drills and real contacts, since the exchanges are predictable and the other operators expect beginners. After that, relaxed contest exchanges (short, formulaic, repeated) are a good bridge. You hear the same structure over and over, so it builds confidence faster than rag-chewing does. Check each event's own rules and current schedule from its sponsor, because those change.

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.