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 in noise, nets and emergency traffic?

ci_cover.jpg

I'm putting together a short guide for newer operators in our local group and I want to check my thinking before I write it. The questions I keep running into:

1) Is the ITU/ICAO ("NATO") alphabet the right default for ham radio, or are the older or creative phonetics fine? 2) How should I handle callsigns in a pile-up or when the band is rough? 3) What is the best way to spell names and place names without turning a QSO into a spelling bee? 4) How do numbers and prosigns fit in, especially "niner," "zero" vs. "oh," and the difference between CW prosigns and voice procedure words? 5) What changes on a net or during emergency traffic?

My working rule is: use the standard alphabet by default, spell only what needs spelling, and keep the words consistent. Is that too simplistic?

  • Replies 2
  • Views 50
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

That rule is a good foundation. The alphabet most people call NATO is the same one the ITU and ICAO use: 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 speakers of other languages pronounce them correctly. Saying "Alpha" and "Juliet" on the air is common and rarely causes confusion.

The main advantage of the standard set is that it was designed to survive different accents and poor audio. Many operators on a given band will recognize it, which matters most when you are talking to someone whose first language isn't yours. Creative phonetics like "Kilowatt" or "Texas" are widely used and often understood, especially among regulars. The risk is that they can be ambiguous or unfamiliar, so on a weak path or with a non-native listener they are a gamble. Mixing sets within one callsign (for example, standard for the first letters and something improvised for the suffix) is where problems start, so pick one approach per transmission.

For callsigns in a pile-up or noisy conditions: give the full callsign phonetically once, clearly, at a steady pace, rather than repeating it five times in a rush. If the other station still gets it wrong, repeat only the part that was wrong, for example "the suffix is Kilo Echo Tango", and then confirm the whole call. Keep the exchange short and give the other station room to answer. Slow, clean, and consistent usually works better than loud and fast. If you are using a different phonetic for a letter that keeps being missed, switch to the standard word for that letter. Many people find that the letters that get confused (B/D/P/T, M/N, F/S) are fixed by using a distinctive standard word.

One more habit: say the callsign phonetically, but don't make the phonetics the only way people hear it. On a good path, "W1ABC" said in plain letters is fine, and phonetics only need to appear when conditions or the listener's accent call for them.

  • Administrators

Adding to that, with a focus on names, numbers and nets.

For names and places, spell only the part that is likely to be misheard, and announce it: "The name is Moira, I spell: Mike Oscar India Romeo Alfa." For a place, give the whole word first, then spell the unusual portion. If it's a long location, break it into chunks and pause between them so the listener can write. When copying, repeat it back and let the other station confirm. This matters more than which phonetic words you use.

For numbers, the common voice convention is to say each digit separately, with "zero" instead of "oh" in callsigns and messages, and "niner" for nine if there is any chance of confusion with the German "nein" or with five. Aviation uses "tree," "fower," "fife" and "niner," but in ham radio most people just say the numbers normally unless conditions are poor. The ITU also defines a special set of number words (Nadazero, Unaone, Bissotwo and so on) but they are essentially never used on amateur bands, so you can skip them in a guide. For a callsign with a slash, "stroke" or "slash" works, and "portable" or "mobile" can be used for the suffix when appropriate.

Prosigns are different on CW and voice. On CW, prosigns like AR (end of message), SK (end of contact), BT (break), KN (go ahead, specific station) and AS (wait) are sent as run-together characters. On voice you use procedure words instead: "over," "go ahead," "say again," "standing by," "clear" or "out." Avoid saying "over and out" because they contradict each other, as "over" invites a reply and "out" ends the exchange. Many hams just skip "over" on a repeater with a clear turnaround, but on HF with a weak path it can be useful.

On nets, the net control station (NCS) sets the procedure and you follow it. Many nets ask for check-ins using just the suffix of the callsign, said phonetically, for example "Kilo Echo Tango." NCS then calls back with the full callsign. Wait to be called, give your callsign once, and don't hold the frequency for conversation. Emergency and priority traffic is typically signalled with words such as "emergency" or "priority" and often "break" to interrupt, depending on the net's rules. Communication in organized emergency work usually favors plain language rather than 10-codes or slang, because served agencies and operators may not share the same code meanings. For message traffic, read digits slowly and separately, spell anything unusual, and ask for a readback of critical items such as addresses, names, quantities and times. Follow your local group's or served agency's written procedures where they exist, as those take priority over general advice.

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.