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

Which phonetics should I use on air? Standard ITU/NATO vs. "ham phonetics", bad conditions, numbers, nets and emergency traffic

ci_cover.jpg

I'm trying to tighten up my on-air habits and keep running into conflicting advice about phonetics. Some people insist on the ITU/NATO alphabet only. Others use whatever comes to mind, like "Kilowatt" or "Sugar", and seem to get through fine. I'd like to sort out a few things.

1. Is there an official alphabet I should use for my callsign, and does it matter if I say "Alpha" and "Juliet" instead of "Alfa" and "Juliett"?

2. How do you handle numbers? I hear "niner" a lot, but I've also seen odd forms like "fife" and "tree" in aviation material. Do hams need those?

3. What's the best way to spell names and place names, including grid squares, without turning every transmission into a spelling bee?

4. When conditions are poor (QSB, QRM, weak signal, noisy repeater), what actually helps?

5. How do phonetics, prowords and prosigns differ between CW, voice nets and emergency traffic?

Practical habits are welcome. If you're quoting a regulation, please say which country's rules you mean.

  • Replies 2
  • Views 50
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the alphabet: the one most people mean by "NATO phonetics" is the same one used by ICAO and ITU: 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 the words correctly. Saying "Alpha" or "Juliet" on air is very common and almost never causes a problem. The spelling matters more in print than in speech.

On the rules, I can only speak to the US. FCC Part 97 treats a phonetic alphabet as an optional aid to identification, not a requirement. Your own country may differ, so check your licence conditions.

The real argument for sticking to the standard set is that other operators recognise it instantly, including those who don't share your first language. Improvised words work when both ends share a culture and the signal is strong. They fall apart on a long-distance contact with a weak signal. "Sugar" and "Kilowatt" aren't wrong, but a listener who has never heard them has to decode them, which defeats the purpose. Words that sound alike are another risk. Two different words that both begin with a hard consonant can blur together on a noisy channel.

A practical pattern for your callsign is to say it normally first, then give it phonetically. Many people also repeat just the suffix phonetically when calling. If someone asks for a repeat, slow down and use the standard words rather than inventing new ones, because they may be asking precisely because the first attempt was unclear.

  • Moderators

Numbers: in everyday amateur voice operation, plain digits are normal. The special forms you saw come from formal radiotelephony standards. ICAO aviation uses "tree", "fower", "fife" and "niner". The ITU maritime table uses Italian-flavoured forms like "nadazero" and "unaone". Hams rarely use those. The one exception most people adopt is "niner", because "nine" can be misheard (the German "nein" is the usual example). Say "zero" rather than "oh", and be consistent. If 5 and 9 keep getting confused, stress the vowel clearly and don't rush.

Names and places: spell only the part that's likely to be misheard. "Name is Joe" usually needs nothing. "Name is Siobhan, Sierra India Oscar Bravo Hotel Alfa November" does. For place names, give the word, then the spelling, then the word again if needed. For grid squares, say the letters phonetically and the digits plainly, e.g. FN31 as "Foxtrot November three one". If you're sending a long string of letters, pause between groups so the other person can copy.

Difficult conditions: speak slower rather than louder. Keep your cadence even and don't clip words. Don't run the phonetics together into one stream. Give the information once clearly, then once more only if asked. On SSB with QRM, repeat the callsign in standard phonetics and be ready to answer questions like "was that K or P?" with "Kilo, Papa". Over-emphasised, theatrical pronunciation can make things worse. Clean and measured works best.

Prosigns and prowords: prosigns such as AR (end of message), SK (end of contact), BT (break/pause), K (go ahead) and KN (go ahead, named station only) belong to CW. On voice you use the spoken equivalents: "over", "clear", "break", "go ahead", "say again". Avoid mixing them, like saying "AR" on SSB. Also be careful with "Roger". In many contexts it just means "received", not "yes", so use "affirmative" and "negative" for answers.

Nets and emergency traffic: nets usually run on a simple structure. Net control gives the callsign, takes check-ins (often suffix only, phonetically), and handles traffic one station at a time. Check-ins are typically short, because net control is writing them down. In formal message handling, a radiogram (as in the ARRL/NTS format) carries a precedence of Emergency, Priority, Welfare or Routine, and numbers or unusual words are often spelled out or confirmed. For emergency traffic, "Mayday" and "Pan-pan" are properly maritime and aviation distress and urgency calls. Ham nets typically use plain terms like "emergency traffic" or "priority traffic", and procedures vary by local group and served agency. Follow whatever your net's script says, and when in doubt, keep it brief, use standard phonetics, and read messages back for verification.

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.