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

Phonetics on the air: ITU/NATO alphabet vs. "creative" ham phonetics, and what to do when conditions are bad

ci_cover.jpg

I'd like to sort out what actually works for phonetics on phone, because practice on the bands is all over the place. Some operators use the strict ITU/NATO alphabet and others improvise words. Here are my questions:

1. Is the ITU/NATO alphabet the best choice for callsigns, or are there good reasons to use something else?
2. How should I handle spelling names and locations without sounding like I'm reading a script?
3. What do you do about numbers? Is "niner" worth using, and what about the ITU number words like "Terra" and "Kartefour"?
4. How do phonetics and prowords change in nets and emergency traffic?
5. What helps when the signal is weak, noisy or fading?

I'm after practical habits for SSB and FM voice. CW prosigns are welcome too, if people want to compare them with the voice equivalents.

  • Replies 2
  • Views 52
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

For callsigns, the standard alphabet is the best default: 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. It was designed so the words are distinct across many accents and languages, which matters on the bands. The spellings "Alfa" and "Juliett" are the official ones, but nobody will mishear "Alpha" or "Juliet" on voice.

Improvised phonetics work fine on a local repeater where everyone knows you. They get riskier on HF and DX contacts, where the other operator may not speak English as a first language. "Lovely" or "Nancy" might not register, while "Lima" or "November" probably will. In the US, the FCC rules on station identification (Part 97) encourage a phonetic alphabet as an aid to correct identification, but they don't require a particular one. Check your own country's rules if you're elsewhere.

A few practical points on callsigns:

Say the whole call phonetically at least once, with a clear pause between characters. You don't need phonetics on every transmission in a casual QSO, but use them whenever someone has to copy the call correctly.

Be consistent. If you gave "Kilo" the first time, don't switch to "King" the second. A listener who half-copied you can then match what they heard against the same word.

Don't mix phonetics and plain letters in the same call unless you're repeating just one character for clarity. Something like "W1AW, that's Whiskey One Alfa Whiskey" is easy to follow.

The ITU number words (Nadazero, Unaone, Bissotwo, Terrathree, Kartefour, Pantafive, Soxisix, Setteseven, Oktoeight, Novenine) exist in the ITU radiotelephony tables but are rarely heard in amateur radio. Most hams just say the digits. If you want an extra margin on a bad path, say them slowly and distinctly. The aviation-style "niner" for nine is common and harmless, and it helps separate 9 from 5 in noise. Saying "fife" or "tree" is optional, and some listeners will find it affected on a casual net.

  • Moderators

On names and places: spell what can't be guessed, and be explicit about when you're spelling. Something like "My name is Sean, I spell that Sierra Hotel Echo Alfa November. QTH is Tallahassee, I'll spell that." Announcing the spelling gives the other operator time to get pen and paper ready. Spell only the part that's ambiguous. Common words like "Paul" or "Chicago" usually don't need it, but unusual place names, surnames and anything with silent or doubled letters do. After spelling, give the word again at normal speed so it lands as a word rather than just a string of letters.

In nets and traffic handling, discipline matters more than style. Net control wants short, standard exchanges. A check-in is typically just your callsign, with the suffix in phonetics and maybe your name and location if the net asks for them. Don't pad it with extra chatter. Wait for net control to acknowledge you, and use "over" or a clear pause when you hand back. Avoid "over and out" because it contradicts itself. "Out" or "clear" is the end of the exchange, while "over" invites a reply.

For emergency and priority traffic, plain language is the rule. Don't invent codes, and don't use Q-signals or ten-codes unless everyone involved knows them. Say clearly what the traffic is (emergency, priority, welfare, routine), who it's for and what's needed. For formal message handling such as ARRL radiograms, numbers and text have their own conventions. For example, "X" can stand for a period in the text, and groups are read out clearly with spelling when needed. Follow whatever your served agency or net uses.

When conditions are poor, speed isn't your friend:

Slow down slightly and keep your rhythm even. Rushing clips syllables and makes phonetic words run together.

Keep your audio moderate. Over-driving the mic or shouting adds distortion and doesn't help copy.

Lean on the words that carry the most distinction. If M and N are getting confused (Mike and November), say them with an emphasis on the first syllable. B, D, P, T and V are classic problem letters, and phonetics resolve them well.

If the other station asks for "fill" or says "say again," repeat just the part they missed, in phonetics, instead of re-sending everything.

On CW the equivalent habits apply. Prosigns like AR (end of message), SK (end of contact), BT (break) and KN (go ahead, specific station only) are sent as single run-together characters. They have no voice counterpart beyond words like "over" and "clear." Getting the spacing right is the CW version of speaking clearly.

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.