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 changes at each stage, and where do people stall?

ci_cover.jpg

Progress from about 5 wpm to 20 wpm isn't one steady climb. The skill changes along the way, and most of the frustration seems to come from using a method that fits the previous stage. Here is a rough breakdown, and I'd like to hear where others see it differently.

Below about 10 wpm: The job is learning the sound of each character as a unit, not counting dits and dahs. This is why Farnsworth timing (characters sent at 18-20 wpm with extra space between them) and the Koch method (full-speed characters, adding one at a time) are popular. Either way, the character rhythm is the same from the start, so you never have to unlearn a slow, counted version of the letter.

10 to 13 wpm: This is the classic plateau. Copying letter by letter stops working because the next character arrives before you've finished processing the last. The fix is usually to stop hunting for letters and start recognizing common words and fragments (THE, AND, ING, CQ, DE, 73) as single sounds. Short-word drills and listening to real text at a speed slightly beyond comfortable tend to help more than more letter drills.

13 to 20 wpm: This stage is mostly about head copy. Writing every letter becomes the bottleneck, so you start copying in your head and writing only callsigns, names, and numbers. Staying a few characters behind the sender, instead of chasing each one, keeps you from losing the whole word over one missed letter. Missing a character and moving on, without dwelling on it, is a skill in itself.

Practice structure. Short daily sessions (15 to 30 minutes) usually beat one long weekend session. A session might mix a few minutes of new material, some callsign or word drills, and some copying of real or simulated QSOs. Receive speed generally runs ahead of send speed, so don't let sending practice stall your copy practice.

Tools. Trainers like LCWO and RufzXP (callsign copying that adapts speed to your accuracy) cover the drill side. Morse Runner simulates contest pileups. Structured courses such as CW Academy from CWops are worth a look if you want a schedule and a group. For on-air practice, many clubs and groups run slow-speed CW nets or code practice sessions, and the ARRL has run code practice transmissions from W1AW. Check current schedules directly, since these change.

Software decoding. Decoders such as fldigi can help you confirm what you heard, but they struggle with hand-sent code, QSB, and noise, and leaning on one can keep you from building real copy skills. A reasonable compromise is to copy first and use software only to check afterward.

Gear and sending. Iambic paddles with a keyer let you send cleanly, but the settings matter: contact gap, tension, weight, and iambic mode A versus B all change how the keyer behaves. A sidetone around 500 to 700 Hz is a common comfortable range. Recording your own sending and playing it back is a good way to catch uneven spacing.

So where do you see the biggest stall: the 10 to 13 wpm wall, the jump to head copy, or the move from drills to live QSOs? And do you think contests are good practice or too fast to learn from?

  • Replies 2
  • Views 27
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

The wall at 10 to 13 wpm is mostly about how you handle mistakes, in my reading of how learners describe it. If a missed letter makes you stop and puzzle over it, you lose the next two or three characters and your copy collapses. Practicing the habit of dropping a blank and carrying on tends to help more than another round of letter drills.

For head copy, one gradual way in is to copy on paper but stop writing the easy words. Write only callsigns, numbers, and names, and let everything else go by in your head. Another is to listen to text slightly above your comfort speed without writing at all, and treat it as exposure instead of a test. Comprehension comes before accuracy.

On software: it makes a useful answer key. Send yourself or a trainer's text, copy by ear, and compare. Having a decoder running live while you listen is where the crutch problem tends to start.

  • Moderators

On sending and live practice, a few points. If you use iambic paddles, check the squeeze behavior in your keyer. Mode A and mode B differ in whether an extra element is added when you release both paddles, so the same hand movement can send a different character. A slightly tighter contact gap and light tension help reduce accidental doubled dits, but it's personal, so adjust one thing at a time.

Slow QSO practice is worth doing even if it feels awkward. A standard exchange (CQ, callsign, RST, name, QTH, 73) is predictable, so you can use context to fill gaps, which is exactly what you'll rely on at 20 wpm. A slow net or a code practice session lets you do this without the pressure of a pileup.

Contests are good for callsign copying and for hearing a lot of exchanges quickly, but they can be discouraging early on because the speed is high and the exchanges are rigid. Running Morse Runner or listening to a contest weekend before entering is a way to test the water. Many contests also have slower-speed or low-power categories where beginners won't feel out of place.

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.