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 what just feels productive?

ci_cover.jpg

Going from 5 to 20 WPM is rarely a smooth line. Early gains come quickly, then there is usually a stretch somewhere around the low-to-mid teens where more practice seems to change nothing. Practice advice is also split. Some people say to drill characters, others say to get on the air, and others say to turn the decoder off. Here is the problem broken into parts, to see where people disagree.

Character speed versus overall speed. A common trap is learning characters at a slow sending speed, such as 5 WPM with normal spacing. That teaches you to count dits and dahs instead of hearing a rhythm. The usual fixes are Farnsworth timing (characters sent fast, with extra space between them) or the Koch method (start with two characters at full speed and add one at a time once you hit about 90% accuracy). Either way, the goal is to recognize each character as a single sound, not assemble it.

The plateau. At some point you stop translating sound to letter to word and start hearing whole words. Until that happens, you can feel stuck. Common ways through it:

  • Practice a bit above your comfortable speed, so you miss characters and learn to let go of them instead of dwelling on them.
  • Copy a character or two behind, so your brain isn't scrambling to name each letter the instant it ends.
  • Use word lists and common words, not only random groups. Real CW is full of repeated words and abbreviations that you eventually hear as units.
  • Stop writing every letter. Moving from full copy to jotting only the callsign, name and location is how head copy usually begins.

Callsign and QSO drills. Callsigns are a different skill from plain text because there is no context to help you guess. Tools like Morse Runner and RufzXP are built for this, and contest-style practice trains you to catch a callsign on the first or second pass. For QSO practice, write out a standard exchange (CQ, signal report, name, QTH, 73) and drill it until the structure is automatic. After that, a real QSO is mostly listening for the variable parts.

Paddles and keyer settings. Your sending should not run ahead of your receiving, because sloppy sending is hard to fix later. Practical points: set the keyer to a speed where you send cleanly, not where you can barely hang on. Keep the standard 3:1 dah-to-dit ratio unless you have a reason to change it. Adjust paddle tension and contact gap so you aren't fighting the paddle. Iambic mode A or B is mostly personal preference, but pick one and stick with it long enough to build muscle memory.

Ear versus software. Decoders are fine for confirming what you thought you heard, but they struggle with fading, QRM, noise and irregular spacing, which is the normal state of the bands. Relying on one early can also stop you from committing to a guess. Many learners use software for generating practice and checking answers, and keep the decoder off for actual listening.

Schedule. The general consensus is that short daily sessions beat long weekly ones. Something like 15 to 30 minutes a day, split between receive drills, sending and some on-air or recorded listening, is more sustainable than marathon sessions that end in fatigue.

Where do you disagree? Which of these has helped people most past the plateau, and when does it make sense to move from drills to slow CW nets, CWops-style practice sessions or a first contest?

  • Replies 2
  • Views 41
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

The biggest factor is probably when you start real on-air listening. Drills build recognition, but they don't prepare you for QSB, a drifting fist, or someone who runs words together. If you can copy a trainer at 18 WPM but fall apart on the air at 12, the gap is usually exposure. Even listening to a strong station and trying to pick out just the callsigns and RSTs helps.

On the plateau: it's often less a speed wall than a habit wall. The point where you are still consciously naming letters is the point where you have to let some of them slip by. It feels worse for a while, because your copy gets patchy before it gets better. That's normal. If you only ever practice at a speed where you get 100%, you may never need to make the switch to hearing words.

For contests, the low-pressure way in is to listen first and log callsigns only, or work a few stations at the slow end of the band. Weekly short sprint-style events are more forgiving than a full weekend, since you can quit when you're tired.

  • Moderators

I'd add something about sending, because it gets less attention than receiving. If you send with a keyer set well above what you can copy, you'll get replies at that speed, and you won't be able to read them. A good rule is to send at or slightly below the speed you can reliably copy. Clean spacing between characters and words matters more than raw speed. A lot of people sound faster than they are because they rush the dits and shorten the gaps, which makes them harder to copy.

On decoders, I think the useful distinction is between using one as a crutch and using it as a check. Recording a session, copying it by ear, and then running the audio through software or comparing against a known text tells you where your errors actually are. That's different from watching the screen while you listen, because then you aren't training your ear at all.

One practical thing: write down which characters you keep missing. It's usually a short list, often similar-sounding ones like 6/B or sets with the same rhythm, and targeted drills on those pay off faster than general practice.

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.