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 actually moves the needle, and how do you get past the plateaus?

ci_cover.jpg

I'd like to collect what works for building CW speed from beginner level (around 5 WPM) to a comfortable 20 WPM, and how people handle the stalls along the way. Here is the general framework as I understand it, and I'd like to hear where it breaks down.

The first stage is learning characters as sounds, not as dots and dashes. If you have to think 'dah-dit-dah-dit' to get to C, you will hit a wall at about 8 to 10 WPM, because the counting takes more time than the character itself. The Koch method and Farnsworth spacing both address this. Characters are sent at 18 to 20 WPM or faster, with extra space between characters and words so the overall speed is slow. You learn the rhythm of each letter at its real speed. Then you shrink the gaps as copy gets easier. Whichever tool you use (LCWO, a Morse trainer app, or the CWops CW Academy program), the principle is the same: never train on slow, stretched-out characters.

The second stage is where plateaus show up. Many learners describe a stall somewhere around 10 to 13 WPM, when single letters are solid but you are still copying letter by letter. Another stall tends to appear around 18 to 25 WPM, when you have to stop writing everything down and begin recognizing whole words and common phrases. That is the transition to head copy, where you hear the word, not the letters. Putting the pencil down, even when it feels like a step backward, is usually part of getting through it.

For drills, I think the useful ones are:

Common words and short phrases (the, and, name, rig, ant, QTH, 73) sent as units, so you learn them as shapes of sound. Callsign drills, since callsigns are random strings with no context to lean on, and tools like RufzXP are built for exactly that. And simulated contest exchanges such as Morse Runner, which put you under realistic pressure with overlapping stations.

On the hardware side, the questions I'd like opinions on: iambic A vs. B, how much weight and spacing adjustment matters, and when it makes sense to move from a straight key to paddles. I'd also like to hear how people split time between decoding by ear and using software decoders as a check.

Questions for the thread: What is a realistic practice schedule? Do short daily sessions beat longer, less frequent ones? When is it time to start making QSOs, and are slow CW nets a good bridge between drills and real on-air contacts?

  • Replies 2
  • Views 35
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On schedule: the usual advice, which matches how skill learning works generally, is that frequent short sessions beat occasional long ones. Fifteen to thirty focused minutes a day, ideally split from other sessions, is easier to keep up than a two-hour block on Sunday. Fatigue also matters. When your copy starts falling apart halfway through a session, extra minutes after that point mostly practice mistakes.

For plateaus, one common approach is to work slightly above your comfortable speed. If you copy 100 percent at 15 WPM, spend part of the session at 18 or 20, accepting that you'll miss characters. Don't chase the missed character. If you stop to puzzle over it, you lose the next three. Let it go and stay with the stream. Then drop back to your comfortable speed and it will feel easier. Some people also alternate between a character-speed push and a spacing push, so they aren't always raising the same variable.

On head copy, it helps to stop writing before you feel ready. A practical way is to copy only every few words on paper, then fewer, and eventually just listen and keep a sentence in your head. The first stage of that will feel worse, and that's normal. Your brain is trading letter-by-letter certainty for word-level recognition.

As for decoding by software: decoders can be handy for confirming a callsign you weren't sure of, but they are unreliable when there is fading, static crashes, hand-sent timing that drifts, or two signals close together. Relying on one for training also gets in the way of building your own ear. A reasonable use is to copy by ear first, then check against the decoder afterward, not the reverse.

  • Moderators

Paddles and keyer settings are worth a separate look because they affect your sending, and bad sending habits can slow your receive progress too. Start with a sidetone around 500 to 700 Hz, whatever is comfortable for you. Set the keyer speed to match what you can send cleanly, not what you can copy. Sending clean at 15 is better than sending sloppy at 22. Paddle tension and contact gap are personal. Too light and you get accidental double dits, too heavy and your hand tires. Iambic mode A vs. B mostly comes down to how the keyer handles the last element when you release the paddles. Mode B gives an extra element on release, and people who learned on one tend to prefer it. If you get unexpected extra dits or dahs, try the other mode before blaming your hands.

Weighting and spacing: the standard is a dah that is three dit lengths, with one dit of space inside characters and three between. Many keyers let you adjust weight, but if you don't have a reason to change it, leave it near the default. Odd spacing makes your sending hard to copy, and it also trains your ear to expect the wrong rhythm.

For first QSOs, many people find it easiest to start with a prepared structure: callsign exchange, signal report, name, QTH, and a sign-off. Those are predictable, so you can copy them even when you miss a character. Slow-speed CW nets can also be a gentle step, since net control usually keeps a structure, though the speeds and schedules vary a lot, so check current listings before relying on one.

Contests can be a speed-building tool, not just a test. The exchanges are short and repetitive, and you hear the same callsign formats over and over. If you want a low-pressure way to start, listen first, copy callsigns without transmitting, then try answering a few stations at a pace you can manage. Always check each contest's current rules and times, and don't expect to match the top operators right away. Making two or three contacts in a contest still counts as 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.