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

Phonetics on the air: NATO/ITU alphabet vs. "ham" phonetics, and what holds up when conditions are bad?

ci_cover.jpg

I'd like to get a discussion going about phonetics on phone modes. Many of us learned the ITU/ICAO ("NATO") spelling alphabet and then heard operators use something different on the band. Some are creative ("Kilowatt" for K, or a whole string of city names). Others are the old police-style words like Adam, Boy, Charles. A few questions to start:

1. Is there a "correct" alphabet for amateur radio, or is it just convention? As I understand it, the ITU spelling table is the international standard for radiotelephony, and the amateur rules in most places don't make it mandatory. In the US, for example, the identification rules say phone IDs are in English and a phonetic alphabet is encouraged, not required. Please correct me if your country's rules differ.

2. When signals are weak, noisy or doubled, is it better to stick strictly to the standard words, or does a creative word sometimes get through when the standard one doesn't?

3. How do you handle spelling names and locations on a net, and how do you say numbers? Do you use "niner" and the full ICAO number pronunciations (wun, too, tree, fower, fife, ait), or normal numbers?

4. What changes for nets and emergency traffic, where accuracy matters more than style?

For reference, the standard words are Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu. The official spellings "Alfa" and "Juliett" exist so that non-English speakers pronounce them correctly.

  • Replies 2
  • Views 42
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On question 1: the ITU/ICAO words were chosen and tested so that they stay distinguishable across many languages and poor audio. That is the main argument for them. Improvised words are fine on a clean local FM contact, but they come with a risk. If the other station doesn't know your word, they have to guess which letter it stands for, and you've added confusion instead of removing it.

The weak-signal rule I'd suggest is to pick one word per letter and keep using it. If you say "Kilowatt" the first time and "Kilo" the second, the listener may wonder whether you changed letters. Many operators use the standard alphabet for their callsign every time, and this matters most in a pile-up, where the caller is competing with others and the DX station may only catch fragments. Sending the full call once, cleanly, at a steady pace usually beats repeating it three times in a hurry.

Pronunciation matters as much as word choice. "Quebec" is KAY-BECK, "Lima" is LEE-mah, and "Oscar" and "Papa" are easy to mumble. Slow down slightly and give each syllable its stress. Clipped, rushed standard phonetics can be harder to copy than slow, slightly non-standard ones.

  • Moderators

For nets and emergency traffic, the priority is to be consistent and unambiguous. Some practical points:

Use phonetics for anything that can't be checked from context: names, street names, unusual words, callsigns, and any part of a message that has to be exact. A common pattern is to say the word normally, then spell it: "Kowalczyk, I spell, Kilo Oscar Whiskey Alfa Lima Charlie Zulu Yankee Kilo." For number strings like a phone number or grid square, say the digits one at a time and pause between groups. Many people say "zero" rather than "oh" so that it isn't confused with the letter O. Saying "niner" for 9 is common because "nine" can be confused with "five" in noise, but if you're not sure everyone on the net knows it, normal digits are fine. The full ICAO number words (wun, too, tree, fower, fife, ait) are mostly an aviation habit and are rarely needed in ham nets.

For traffic, plain language is generally preferred over 10-codes or other jargon, especially when different agencies and volunteers are on the same channel. Short prowords such as "say again," "break," "priority," "emergency traffic," "copy," and "clear" are fine. Don't use "Roger" as a vague acknowledgment of everything. Repeat back critical items instead, such as addresses and quantities.

Prosigns are mainly a CW matter: AR, SK, BT, KN and so on. On voice you replace them with spoken equivalents like "over," "clear," and "stand by." It's worth knowing the CW versions if you handle formal message traffic, because the same structure carries over, for example when a radiogram's check count and spelled words must be read back exactly.

In an actual emergency, follow whatever the net control station or served agency has set up. They will tell you the format, so don't improvise a new one mid-net.

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.