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

From 5 to 20 WPM: what actually moves the needle, and how do you get past the plateaus?

ci_cover.jpg

Going from about 5 WPM to 20 WPM is a common goal, and the advice for it is often contradictory. Some people say to copy everything on paper, others say never to write anything down. Some say to use a decoder, others say to ban software entirely. This thread is meant to sort out which habits matter at which stage, so please add your own methods and the reasoning behind them.

Here is a rough framework to argue with.

Characters first, speed second. The usual advice is to send characters at a fairly high speed (many people use 18 to 25 WPM character speed) and stretch the gaps between characters and words to get a slow overall rate. This is the Farnsworth approach. The Koch method is a related idea: start with two characters at full speed and add one at a time once you hit roughly 90 percent accuracy. The goal in both is to hear each character as a single sound, not as a count of dits and dahs. Counting works at 5 WPM and falls apart somewhere around 10 to 12.

Plateaus. Many learners stall between about 10 and 15 WPM. At that point you are no longer limited by knowing the alphabet. You are limited by how fast your brain turns sounds into letters, and then into whole words. If you are still thinking about each letter as it arrives, you fall behind. The fix usually involves practicing slightly above your comfortable speed, so you have to let go of individual letters and catch word shapes instead.

Head copy. Copying in your head without writing is a skill that comes in stages. First you write everything. Then you write only callsigns, names, and numbers. Then you hold short phrases in your head. Common QSO words like RST, QTH, NAME, RIG, and 73 are great early targets, because once they sound like words rather than letter strings, you gain a lot of slack.

Drills versus real QSOs. Word lists and callsign drills build recognition quickly. Real on-air contacts add QSB, QRN, drifting tones, and uneven timing, which no clean practice file reproduces. Most people need both.

Questions to get things going:

1. What do you do when you hit a plateau: drop back and consolidate, or push faster and accept errors?
2. At what point did you stop writing everything down, and what made that switch work?
3. Is a decoder a useful check on your copy, or does it become a crutch?
4. What practice schedule is realistic? Does 20 minutes daily beat a long weekend session?

  • Replies 2
  • Views 39
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the plateau question, it helps to figure out what kind of plateau it is. If your copy is clean at 12 WPM but falls apart at 15, that is usually a processing-speed problem, not a character-knowledge problem. In that case, a useful pattern is a few short sprints at 2 to 4 WPM above your comfortable speed, followed by a return to your normal speed. Errors during the sprint are fine. The point is to train yourself to stop dwelling on a missed letter, because dwelling is what makes you miss the next two.

If instead you are missing specific characters (the usual suspects are pairs like B/6, D/7, and the similar-sounding ones like F/L or Q/Y), then fix those directly. Koch-style trainers let you drill the weak characters in isolation, so you are not wasting time on ones you already know.

For head copy, one common progression is: 1) write everything, 2) write only the callsign, name, and signal report, and 3) try to hold the first few words of a sentence in your head while the next ones arrive. Since the exchanges in typical rag chews and contacts are predictable (RST, name, QTH, rig, weather), you can train your brain to expect them. Expectation is a big part of how experienced operators appear to copy at "impossible" speeds.

On schedule, short and frequent usually beats long and rare. Something like 20 to 30 minutes a day, with a mix of new material and review, tends to work better than a single two-hour session on the weekend, because fatigue degrades copy quickly. If you only have a longer window, break it into blocks with breaks in between.

For callsign drills specifically, practice that simulates pileups and contest exchanges, whether through trainer software or recorded contest audio, builds the exact skill you need for fast callsign capture. Callsigns are random strings with no context to help, which is why they feel harder than plain text at the same speed.

  • Moderators

On the keying side, a few settings are worth getting right early because they affect how your sending sounds, which affects how well other operators copy you (and how well you can copy your own sending in practice).

Keyer speed. Set your sending speed to something you can copy, not to your aspirations. Sending faster than you can receive tends to produce sloppy spacing, and if you send badly it is hard to get good practice from it.

Iambic mode. Most keyers offer Mode A and Mode B, and they differ in what happens when you release the paddles during a squeeze. Neither is objectively correct, and the choice mostly comes down to what you learned on. If you switch rigs or keyers, it is worth checking the mode, because mismatches cause extra or missing elements that feel like your own errors.

Paddle adjustment. Contact gap and tension are worth experimenting with. A very light, narrow setup can cause double-dits and accidental contacts, while a stiff, wide one slows you down. Make small changes and give each one a few days before judging it.

Decoding by ear versus software. A software decoder is handy as an occasional check, for example to see which characters you keep missing in a recorded file. As a real-time crutch it has two problems. First, it tends to struggle with fading, noise, and irregular hand-sending, so it produces garbage exactly when conditions get hard. Second, if you look at the screen you stop training your ear. A reasonable compromise is to copy first, then compare against the decoder or the original text afterward.

Contests and nets. Contests are excellent for speed building because the exchanges are short, repetitive, and predictable, so you can practice at a higher speed than a rag chew would allow. Many people start by just listening and copying callsigns, then make a few contacts, then go in properly. Slow-speed CW nets and practice sessions exist too; check current schedules and rules with the sponsoring group before joining, since they 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.