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

Standard phonetics vs. "creative" ones on the air: what actually works for callsigns, names, numbers and nets?

ci_cover.jpg

I'm trying to tidy up my on-air habits and want to understand the reasoning behind phonetics, not just memorize a list. A few specific questions:

1. The ITU/ICAO/NATO alphabet is the standard, but plenty of hams use other words ("Kilowatt," "Lima" for L, or older ones like "Able, Baker"). Is there a real downside to using them, or is it just a matter of style?

2. When should I use phonetics at all? Every time I give my callsign, only when conditions are poor, or only when asked?

3. How do I handle spelling names and place names without turning every transmission into a long string of words?

4. Are numbers treated differently, and what about prosigns and procedure words like "over" and "clear"?

5. What changes in nets and emergency traffic, where accuracy matters most?

  • Replies 2
  • Views 27
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Start with why the standard alphabet exists. The ITU/ICAO/NATO words were chosen to be understood by speakers of many languages through noise, distortion and accents. The 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 spellings "Alfa" and "Juliett" are deliberate, to guide pronunciation. That multilingual, low-signal-to-noise design is the main advantage over improvised words.

Using non-standard words is usually not a rules problem. Regulators generally encourage a phonetic alphabet for identification without requiring one specific list, but check the wording of your own country's rules. The practical downside is that a listener has to recognize the word instantly, and a unique word they have never heard costs them time. "Kilowatt" for K may be understood by many hams, but a newcomer or a non-native English speaker may not know it. Words that sound like other letters or words are the riskiest, so improvised ones fail more often in weak-signal conditions.

For the "when" question, a sensible habit is to give your callsign in normal speech first if the signal is strong, and use phonetics when you're answering a call, being asked to repeat, working a pileup or DX, or whenever the other station has to copy it exactly. Many operators give the full callsign in phonetics every time during contests or DX because there is no room for a bad copy. In a casual chat with a strong signal, repeating phonetics every over just adds clutter.

Keep it consistent. If you use "Whiskey" for W one time and a different word the next, you add confusion rather than remove it. Pick the standard list, say the words clearly, and don't stack extra explanation on top.

  • Moderators

On names and locations, the simplest approach is to say the word first, then spell the part that might be misheard. That way the listener gets the likely sound and then the letters to confirm it. For example, say the town name normally, then "I spell" and the letters, using standard phonetics. Don't spell every word in a sentence, only the ones that carry the information: names, street names, unusual places, call signs and anything non-obvious.

When conditions are rough, slow down and keep a steady rhythm instead of shouting. Pronounce each phonetic word fully and leave a very short gap between letters. Group long strings into small chunks, such as callsign prefix, number, suffix. If the other station says "say again," repeat only the part they missed rather than the whole message. "Say again" is the usual request, and "I say again" signals that you are repeating yourself. Avoid saying "repeat" in settings where it could be read as an instruction to repeat a message or fire, though that is more common in military procedure than ham use.

Numbers can be spoken plainly in most casual ham contact. The ICAO aviation numeral pronunciations ("niner," "fife," "tree" and so on) exist to prevent confusion in poor audio. Hams often use just "niner" for 9, since "nine" can be confused with "five" or with German "nein." Using the full aviation set is optional, but clear digit-by-digit reading matters. Say numbers one digit at a time: "one two three," not "a hundred twenty-three," unless you mean a quantity.

Regarding prosigns and procedure words, the true prosigns (AR, SK, BT, KN and so on) are mostly a CW matter, where they are sent as a single run-together character. On voice you use procedure words: "over" to hand the transmission back, "clear" or "out" to end the contact. Avoid saying "over and out" together because the two meanings contradict each other.

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.