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 to 20 WPM: what actually moves the needle, and how do you break a plateau?

ci_cover.jpg

Reaching 5 WPM is mostly memorization. Reaching 20 WPM is a different skill. Somewhere in between, the job changes from decoding dits and dahs to recognizing sounds, then whole words, then phrases. That change is why many people stall. This thread is for comparing methods, so here is a framework to argue with.

Learn at real character speed. The usual advice is to send characters at 18-20 WPM and stretch out the spacing between them (Farnsworth timing) rather than slowing everything down. If you learn the letters at 5 WPM, you tend to count elements, and that habit has to be unlearned later. Koch-method trainers add characters one at a time at full speed. Many people run them until they hit about 90% copy on the current set before adding the next character. LCWO, G4FON's Koch trainer and similar tools all work this way.

Expect plateaus in two places. The first is often around 10-13 WPM. Characters are solid, but you are still translating each one into a letter, and the next one arrives before you finish. The second tends to show up in the mid-teens. Pencil copy becomes the bottleneck, and you need to start copying in your head. The fixes differ. For the first plateau, shrink the extra spacing and drill the characters you still hesitate on. For the second, stop writing every letter, write only numbers and callsigns, and then try to write nothing.

Head copy is a practice mode, not a talent. Start with short, predictable material such as common words, then QSO phrases like "UR RST 579" and "NAME IS". Your brain will begin to hear them as units. Callsign drills (RufzXP is a popular one) build the habit of holding a string in memory while the next one comes in. The same goes for contest exchanges, which are short and repetitive. You can run Morse Runner as a pileup simulator long before you are ready for the real thing.

Paddles and keyer settings matter more than people expect. Poor sending and poor copying feed each other. If you use iambic paddles, you will choose between Mode A and Mode B. Mode B adds one extra element when you release both paddles, and it is worth trying both to see which matches your squeeze timing. Keep the weight near default at first, around a 3:1 dash-to-dot ratio, since odd weighting makes your own sending hard to judge. Set the sidetone to a pitch you can listen to for an hour, commonly somewhere in the 500-700 Hz range. Set paddle tension and contact gap light enough to avoid fatigue but firm enough to avoid accidental double dits.

Schedule: short and often beats long and rare. One workable pattern is 20-30 minutes a day, split into a few blocks. For example, spend 10 minutes on new or weak characters, 10 on words or callsigns slightly above your comfort speed, and 10 on real or simulated QSO copy. Then add one longer session a week. Push the speed up in small steps. Work at a speed where you copy about 90% and your errors are clustered rather than random. Dropping back a notch when you get tired is fine.

Real on-air practice. Sooner or later you need live signals with QSB, noise and different fists. Slow CW nets, club code practice sessions and the short weekly contest-style sessions some CW groups run are good low-pressure starting points. Check the current schedules with your local club or the sponsoring group, since they change. For speed contests, one approach is to listen first and just copy callsigns and exchanges without making any QSOs. When that feels comfortable, begin answering.

Decoding by ear versus software. A decoder can be a useful check. It lets you compare what you thought you heard against a transcript, and it can show you which characters you consistently miss. But it struggles with fading, noise, bad timing and irregular spacing, which describes plenty of real-world CW. If you lean on it too early, you may never build the ability to copy in your head. A reasonable compromise is to do your practice by ear and use software only for review afterward.

Questions to get things going: Where did your own progress stall, and what got you through it? Do you prefer Koch with Farnsworth spacing or a fixed overall speed? Straight key, bug, or paddles for building a good fist? What would you tell someone at 8 WPM who wants to get on the air this month?

  • Replies 2
  • Views 40
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the plateau question, it helps to work out what kind of plateau it is before changing the plan. If you are missing specific characters, that is a recognition problem, and a Koch-style drill on just those characters is the answer. If you recognize every character in isolation but fall apart in running text, that is a buffering problem. You are still decoding letter by letter and cannot hold the previous letters while the next ones arrive. Drilling words and callsigns attacks that directly, because it forces you to chunk.

One concrete tip on head copy: when you stop writing, leave the first few words or letters unrecorded and just listen. Most people find that the first thing to go is the urge to write each letter, and they get lost when they miss one. Practice letting a missed character go and picking the thread back up with the next word. Real QSOs are full of missed characters, and recovering quickly is half of copying.

On keyers: if you are building speed on iambic paddles, record your own sending and listen back. Spacing errors that feel fine while you send often sound uneven on playback, and that is a good way to catch problems before they become habits.

  • Moderators

I'd push back a little on treating software decoding as something to avoid altogether. It depends on how you use it. Used as an answer key after a practice session, it is useful, because you can compare it against your own copy and see exactly where you went wrong. Used live as a replacement for your ears, it will probably slow you down. Also keep in mind that decoder output is often wrong on weak or fading signals, so a mismatch does not always mean you made the mistake.

For getting onto the air, I'd suggest a stepped approach rather than waiting until you feel ready. Start by listening to real QSOs and copying only the callsigns and the signal reports. Then answer a slow CQ. Many CW operators will slow down for a newcomer if you tell them you are still learning. A short exchange with a standard structure (callsign, RST, name, QTH) is a good first target, because you already know what is coming and can focus on hearing it.

Contests are worth trying early for the same reason. The exchange is predictable and repeated hundreds of times, which makes them one of the better ways to build callsign copy at speed. Just don't set a speed goal for your first one. Treat it as listening practice and log whatever you can.

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.