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 to do about plateaus, head copy, and whether to trust a decoder

ci_cover.jpg

This thread is for comparing practice methods for the 5 to 20 WPM stretch, which is where a lot of people stall. The early gains come fast, then progress flattens somewhere in the low teens and practice starts to feel like work. Here is a rough map of the problem, with some questions to argue about.

Character speed versus overall speed. Most structured methods, whether Koch-style or Farnsworth-spaced, send characters at 18 to 20 WPM or faster and stretch the gaps between characters and words. The goal is to learn each letter as a sound pattern ("dah-di-dit-dit" is wrong, it should simply be B) rather than a dot-and-dash count. If you learn characters at 5 WPM with normal spacing, the individual letters are so slow that you tend to count elements, and that habit is hard to unlearn later.

The usual plateau. The wall around 10 to 13 WPM is commonly attributed to a switch from letter-by-letter copy to word-level recognition. At that speed a letter is over so quickly that you can't consciously identify it and still keep up, but you haven't yet learned to hear whole words and common chunks like THE, ING, AND, or CQ. Typical ways through it:

  • Drop the spacing stretch gradually while keeping character speed fixed.
  • Practice short, high-frequency words and common prefixes and suffixes so you start hearing chunks.
  • Run sessions slightly above your comfort speed, accept losing characters, and keep going instead of dwelling on the miss. Dwelling on a missed letter usually costs you the next three.
  • Alternate sessions: one pushing speed, one at a comfortable speed focused on accuracy.

Head copy. Writing every letter is a fine training stage, but it caps speed because your pencil becomes the bottleneck, and many people write more slowly than they can hear. Moving to head copy is usually gradual: start with callsigns and signal reports in your head, then short words, then whole phrases, then full exchanges. Letting go of the pencil is uncomfortable, so it helps to do it in low-stakes practice before attempting it on the air.

Drills. Word lists and random callsigns train different skills. Callsign trainers (RufzXP is a well-known one) build quick, accurate recognition of mixed letter-number strings, which is exactly what you need in contests and pileups. Plain-text and word drills build the chunking that makes ragchew-speed copy possible. Ideally you do both, but which should come first?

Paddles and keyer settings. If you send with a keyer, a few settings matter more than people expect:

  • Set sending speed near your copying speed so you aren't sending faster than you can understand the reply.
  • Keep weighting near the default ratio (about 3:1 dash to dot) until your timing is solid. Odd weighting can make your code harder for others to read.
  • Pick one iambic mode (A or B) and stay with it long enough to build muscle memory. Switching constantly hides whether the problem is you or the mode.
  • Adjust paddle spacing and tension so that you can squeeze without effort and release cleanly. Fighting the paddles produces sloppy characters, and sloppy sending makes every QSO harder to copy.
  • A sidetone in the 500 to 700 Hz range is common, but choose a pitch that doesn't tire you.

Decoding by ear versus software. Software decoders can be handy for checking what you sent or confirming a callsign. As a learning tool for copy, though, they have a trap: they're weakest in exactly the conditions you need to learn, such as noise, QSB, hand-sent irregular timing, and overlapping signals. Relying on a screen also keeps your ear from developing the tolerance it needs. Generators and trainers (LCWO, Morse Elmer, and similar) are different, since they produce clean practice rather than decode live signals.

Schedules. Short daily sessions generally beat occasional long ones. Around 15 to 30 minutes a day, perhaps split into two blocks, is a common recommendation, with fatigue as the signal to stop. Within that you might rotate: new characters or speed push, callsign drills, then some real or simulated on-air material.

On-air practice. Slow-speed CW nets and QSO partners with a similar speed are useful for practicing the full exchange structure (calls, RST, name, QTH, 73) under realistic conditions. Contests are a good source of fast, repetitive exchanges where you hear the same format over and over. If you try one, check the current schedule and rules of the specific event yourself, since they change. Many operators suggest listening first, then answering only stations you can copy comfortably.

Questions to get things going: What changed things for you when you hit the low-teens wall: speed, spacing, or the kind of material? Do you move to head copy early or late? And is there a point where software helps instead of hurts?

  • Replies 2
  • Views 94
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the plateau, the single most common fix described for it is changing what you practice, not practicing more of the same. If every session is random five-letter groups, you build letter recognition but never train word-level hearing. Mixing in real text, common words, and callsigns forces your brain to predict, and prediction is what carries you past 15 WPM. Plain text also makes the head-copy transition easier, because you start recognizing words before you finish hearing them.

On paddle settings, I'd add one caution about keyer speed: it's tempting to set it to a speed that feels impressive and then send sloppy code. A clean 15 WPM is far more useful on the air than a messy 22. If a partner has to ask for repeats, you lose more time than you gained. Record yourself sending a short exchange and play it back. It shows up uneven spacing, doubled dits, and clipped dahs very quickly.

  • Administrators

I'd push back a little on starting callsign drills before word drills, or at least on treating it as an either/or. Callsigns are a closed, high-value set of patterns, and they're the part of a QSO where you can't guess from context. Missing a letter in a word is forgiving, but missing one in a callsign means you can't reply. So even at modest speeds, a short daily callsign block is worth it. Word and text practice can fill the rest of the session.

On decoders: a reasonable middle ground is to copy first, by ear, and only then check with software if you want to verify. Doing it in that order keeps your ear in charge. If you glance at the screen mid-copy, you'll start waiting for it to confirm each character, and that dependence is hard to break. Also keep in mind that decoders tend to struggle with fists that have uneven timing, so a garbled screen doesn't necessarily mean you missed anything. It may just mean the software can't handle that sender.

For nets and QSO practice, slow nets are a good place to rehearse the standard exchange when nerves are the main obstacle. Having the structure memorized frees up attention to copy the one or two items that actually change, such as name and location.

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.