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

NATO phonetics on the air: when to use the standard alphabet, when improvised words are OK, and how to handle bad conditions

ci_cover.jpg

Question for the group: how strict should we be about phonetics on the air? Most operators know the standard alphabet (Alfa, Bravo, Charlie and so on), yet in practice you hear a mix of it, "cute" words, and old police-style lists like Adam-Boy-Charles. I'd like to sort out what is actually best practice and what is only habit.

Some specific points I'd like opinions on:

1. The NATO, ICAO and ITU alphabets are essentially the same list for letters. Is there any practical difference for hams? I understand the spellings "Alfa" and "Juliett" are deliberate, so that non-English speakers pronounce them correctly.

2. For callsigns, do you give the phonetics every time, or only once and then switch to the plain callsign?

3. What do you do about numbers? Some people say "niner" and "fife", and others just say "nine" and "five".

4. What should change on a weak band, in a pileup, or on a net handling emergency or priority traffic?

5. How do you spell names and place names without turning the QSO into a drill?

Any rules of thumb that you'd give a new licensee would help.

  • Replies 2
  • Views 16
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the alphabet itself, the letters are the same list across NATO, ICAO and ITU use. The ITU form is the one the amateur service points to. The full list is 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. These words were chosen because they stay distinguishable across many languages and through poor audio. In the US, Part 97 encourages a standard phonetic alphabet for station identification, but as I read it, it does not require one. Other countries' rules differ, so check yours.

The practical trouble with improvised words is that they only work when both ends share the same mental list. "Nancy" for N is fine between two people who grew up with it. A listener who has never heard it, or who is copying in a second language, may hear nothing useful. Using the standard words keeps the other station from having to decode your choice as well as your callsign.

Numbers work differently. The formal radiotelephony pronunciations (tree, fower, fife, niner) come from aviation and maritime use. On amateur voice, most people say the digits normally. "Niner" is the one that has spread widely, since "nine" can be mistaken for "five" in noise and sounds like the German "nein". If you are working a station that is struggling, switching to clear, separated digits helps more than any special pronunciation.

  • Moderators

For callsigns, a workable habit is to give the full callsign in standard phonetics at the start of a contact, and then only the plain callsign for routine exchanges. When conditions are bad, go back to phonetics. That includes QRM, QSB, a weak signal, a noisy mobile, or a station that has asked for a repeat. If the other operator asks for "the last two letters" or "the suffix again," give just that part slowly, in phonetics, rather than repeating the whole call faster.

In a pileup, the usual advice is to send your callsign once, clearly, and listen. Repeating it ten times does not help, because the DX operator is trying to pull out one partial and cannot copy a stream. If you are asked to repeat only part of it, repeat only that part.

For names and places, spell only the part that is likely to be misunderstood. "My name is Jon, J-O-N: Juliett Oscar November." For a location you can give the name, the state or region, and then spell it if asked. Mixing in a known landmark often helps more than spelling does. If you spell something, pause between letters, and say "I spell" or "phonetics follow" first so nobody mistakes a letter for a word.

On nets, especially emergency or priority traffic, net control normally wants standard words and no experiments. Names, street addresses, and medical or supply quantities are the items where an error does real harm. A good method is to say the item, spell it in phonetics, and ask for a readback. On CW, phonetics are not used; instead, prosigns and procedure matter. AR ends a transmission, SK ends a contact, BT separates sections, and K invites the other station to transmit. On voice, say "over" when you hand the frequency back and "out" when you are finished, but not "over and out" together, since the two mean opposite things. For urgent traffic, state clearly that you have emergency or priority traffic, and follow what net control asks for. Terms like Mayday and Pan-pan are for real distress or urgency, so keep them out of drills unless the exercise rules say how to mark them.

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.