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: when to use standard ITU, when ham-style alternatives help, and how to handle callsigns, names, numbers and nets

ci_cover.jpg

I'd like to settle a few habits on phonetics, because the advice I see is inconsistent. Some people insist on strict ITU/NATO phonetics every time. Others use whatever word comes to mind. The questions:

  • Is the ITU alphabet the same as the NATO alphabet, and is it "required" for amateur radio?
  • Are ham-style phonetics ("Kilowatt", "Sugar", "Radio", or invented words) ever better than the standard set?
  • What is the best way to give a callsign when conditions are poor?
  • How should names, towns and other unusual spellings be handled?
  • What about numbers, prosigns and procedure words on voice versus CW?
  • Does anything change on a net or during emergency traffic?

For reference, the standard letter 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. Where do people go wrong, and what is a sensible default?

  • Replies 2
  • Views 72
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

The short version is that "ITU", "ICAO" and "NATO" phonetics all refer to essentially the same spelling alphabet. It was designed so the words are distinguishable across many native languages and bad audio. That is why the spellings are odd: "Alfa" and "Juliett" are written that way so speakers of other languages pronounce them correctly. Amateur practice usually just calls it "the standard phonetic alphabet".

On requirements: I would check your own regulator's rules rather than rely on a forum summary. In general, amateur rules tend to encourage or permit phonetic identification rather than require it for every transmission. The practical reason to use the standard set is that the listener, not the rulebook, decides whether you are understood. A word that is familiar to many operators in many countries is the safest choice.

Ham-style alternatives are fine in good conditions and with familiar stations, but they cost you in three ways:

  • The listener has to decode an unexpected word and may mishear it. "Kilowatt" for K is understood by many hams, but it is not part of the standard set.
  • Cute or invented words can be impossible to place for non-native speakers, or someone who just tuned in.
  • Different words for the same letter ("Mexico", "Mike"; "Nancy", "November") make it harder for the listener to settle on one letter.

A decent rule: use the standard alphabet when the contact matters (DX, contest exchanges, weak signal, a net, traffic). Use something lighter only when you are chatting with a regular and the audio is clean. If you do use an alternative and the other station asks for a repeat, switch to the standard word straight away.

  • Moderators

On callsigns in poor conditions, the main trick is to avoid saying the whole thing the same way twice. Give the callsign with phonetics once, then give it again at a measured pace, rather than stringing it together faster each time. If the other station answers with a partial copy ("W-something-something-ZED"), fill in only the missing letters rather than starting over. Many QSOs go wrong because both sides keep repeating the full call instead of fixing the one unclear character.

Some practical details:

  • Numbers: say them clearly. In callsigns, "zero" is generally better than "oh", and "niner" is common for 9 because plain "nine" can be mistaken for "five" in noisy audio, and has historically been confused with the German "nein". Formal ITU number pronunciations such as "tree" and "fife" exist, but most hams use normal English numbers with "niner" being the common exception.
  • Portable/mobile suffixes: "stroke" or "slash" are both widely understood. Many operators say "portable" or "mobile" if they are announcing the operating condition.
  • Names: say the name normally first, then spell it only if needed. "I spell" is a useful procedure phrase before you begin spelling, because it tells the listener the next words are letters.
  • Locations: do not spell the whole town. Spell the confusing part. For example, with a name that has a silent or unusual letter, spell only that part, then say the name again.
  • Grid squares and signal reports: these are short, so they benefit from phonetics for letters, with digits spoken separately and clearly.

Prosigns are mainly a CW matter. Characters such as AR, SK, BT and KN are sent run together as a single unit. On voice you use words instead: "over" to return the transmission, "clear" or "out" to end it, "say again" for a repeat, and "break" to interrupt. Avoid saying "over and out" because the two words mean different things and normally are not used together in careful procedure.

On nets, shorter is better. Net control usually gives instructions in a fixed pattern: call for check-ins, ask for stations with traffic, then close. Check-ins should give the callsign in phonetics once, and any extra information (name, location, status) only when asked. For emergency or priority traffic, keep to the net's own rules and the plan the group has agreed in advance. Plain language is preferred over improvised codes, and the message text should be read in a steady pace with names and numbers repeated or spelled, as the receiving station may be writing it down. If a message contains an important number, repeating it as individual digits is better than saying it as a large number.

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.