reference
Why the NATO Alphabet Spells It Alfa and Juliett (and Says Niner)
Why Alfa has an f, why Juliett has two t's, and how to say TREE, FIFE and NIN-er: the ICAO spelling alphabet checked against Annex 10 and ITU Appendix 14.
Most people learn the phonetic alphabet from films and customer-service calls, so the first time they see the official list they assume it has typos. “Alfa” with an f? “Juliett” with two t’s? They aren’t typos. The alphabet was designed for people who don’t speak English as a first language, so a few words are spelled the way they sound instead of the way English dictionaries spell them. The numbers work the same way: the standard writes “nine” and tells you to say NIN-er. Here’s what the standards actually say, with every claim checked against ICAO Annex 10, the ITU Radio Regulations and the FAA’s Aeronautical Information Manual, and a note wherever a popular explanation isn’t in any of them.
Our NATO phonetic alphabet converter spells any text this way, and the Morse code translator covers the other half of radio spelling at the end of this post.
Where the alphabet came from
The official name is the radiotelephony spelling alphabet. “NATO alphabet” is a nickname, because the alphabet came out of civil aviation. ICAO’s own history of Annex 10 gives the sequence:
- 1927–1932. The ITU adopted a spelling alphabet for ships, revised it in Madrid in 1932, and ICAO’s predecessor used that version for aviation until World War II. It was built from place names: Amsterdam, Baltimore, Casablanca, Danemark.
- WWII to 1946. The Allied militaries standardised on the Able Baker alphabet (Able, Baker, Charlie, Dog, Easy, Fox…). Civil aviation kept using it after the war, and ICAO adopted it in 1946.
- The problem. Able Baker only worked for English speakers. ICAO says South American pilots struggled with it, so ICAO approved a separate Spanish-based “Ana Brazil” alphabet for South America and the Caribbean. Two alphabets in service was worse than one.
- 1948–1949. Professor Jean-Paul Vinay of the Université de Montréal worked on the problem with ICAO’s Language Section, testing “sounds, words and whole alphabets.” A word qualified only if it was a live word in English, French and Spanish with similar spelling in all three, was easy to say and hear over a radio, and had no negative meaning.
- 1951. The result went into Annex 10 for implementation on 1 November 1951 (in civil use from 1 April 1952). Its C, M, N, U and X words were Coca, Metro, Nectar, Union and Extra.
- 1956. Users complained, and ICAO ran more tests with speakers from 31 countries. Words like Delta, Nectar, Victor and Extra were getting confused with each other, so five words were replaced: Charlie, Mike, November, Uniform, X-ray. ICAO implemented the final version on 1 March 1956. NATO’s history page says Allies were told on 21 February 1956 that “the new Phonetic Alphabet is to be made effective in NATO 1 March 1956.”
The same list is now in Annex 10, Volume II, §5.2.1.3 and Figure 5-1 for aviation and in ITU Radio Regulations Appendix 14 for maritime and other radio services. Annex 10 has a note pointing out that the two match. Annex 10 says the alphabet is for “proper names, service abbreviations and words of which the spelling is doubtful”. It’s a way to spell things out, not a way to speak normally.
Why Alfa, and why Juliett
ICAO’s history page gives the reasoning:
Alfa is spelled with an f as it is in most European languages because the English and French spelling alpha would not be pronounced properly by native speakers of some other languages – who may not know that ph should be pronounced as f. Juliett is spelled with a tt for French speakers, because they may otherwise treat a single final t as silent.
The logic works. To a Spanish or Italian reader, “ph” isn’t an obvious f sound, while “alfa” is how those languages already spell the Greek letter. In French, a final t is usually silent (chat, petit), so “Juliet” would lose the sound that separates it from other words. “Juliett” makes a French reader say the t.
One caveat. Neither Annex 10 nor ITU Appendix 14 explains the spellings. They just list them. The explanation above comes from ICAO’s history page, and its wording closely matches the Wikipedia article, so it’s hard to tell who copied whom. It’s a sensible and widely repeated explanation, but I couldn’t find it in a 1950s working paper. The spellings themselves are not in doubt: ICAO, the ITU, NATO and the FAA all print Alfa and Juliett.
The full table, with official pronunciation
This is ICAO Figure 5-1. The respellings are from Annex 10’s “Latin alphabet representation” column. The standard underlines the stressed syllables; here they’re in bold.
| Letter | Code word | Pronunciation (ICAO) |
|---|---|---|
| A | Alfa | AL FAH |
| B | Bravo | BRAH VOH |
| C | Charlie | CHAR LEE or SHAR LEE |
| D | Delta | DELL TAH |
| E | Echo | ECK OH |
| F | Foxtrot | FOKS TROT |
| G | Golf | GOLF |
| H | Hotel | HO TELL |
| I | India | IN DEE AH |
| J | Juliett | JEW LEE ETT |
| K | Kilo | KEY LOH |
| L | Lima | LEE MAH |
| M | Mike | MIKE |
| N | November | NO VEM BER |
| O | Oscar | OSS CAH |
| P | Papa | PAH PAH |
| Q | Quebec | KEH BECK |
| R | Romeo | ROW ME OH |
| S | Sierra | SEE AIR RAH |
| T | Tango | TANG GO |
| U | Uniform | YOU NEE FORM or OO NEE FORM |
| V | Victor | VIK TAH |
| W | Whiskey | WISS KEY |
| X | X-ray | ECKS RAY |
| Y | Yankee | YANG KEY |
| Z | Zulu | ZOO LOO |
A few things English speakers usually get wrong:
- Hotel, Papa and Quebec are stressed on the last syllable: ho-TELL, pah-PAH, keh-BECK. Quebec starts with a K sound, not “kwuh.”
- Juliett has two stresses, JEW-lee-ETT, which fits the reason for the second t.
- Oscar and Victor end in “cah” and “tah.” The respellings avoid a hard English r.
- The ITU table differs from ICAO in small ways. It writes Hotel as HOH TELL and stresses both syllables of ECKS RAY. The FAA’s AIM table 4-2-7 also writes HOH-TEL.
Annex 10 also says pronunciation “may vary according to the language habits of the speakers”. The respellings are a target, not a pass/fail test.
Numbers: TREE, FOW-er, FIFE, NIN-er
The part people get most wrong is that the aviation standard doesn’t replace the digit words. You still write one, two, three. What changes is how you say them. From Annex 10 §5.2.1.4.3.1:
| Digit | ICAO word | ICAO pronunciation | ITU maritime code word | ITU spoken as |
|---|---|---|---|---|
| 0 | Zero | ZE-RO | Nadazero | NAH-DAH-ZAY-ROH |
| 1 | One | WUN | Unaone | OO-NAH-WUN |
| 2 | Two | TOO | Bissotwo | BEES-SOH-TOO |
| 3 | Three | TREE | Terrathree | TAY-RAH-TREE |
| 4 | Four | FOW-er | Kartefour | KAR-TAY-FOWER |
| 5 | Five | FIFE | Pantafive | PAN-TAH-FIVE |
| 6 | Six | SIX | Soxisix | SOK-SEE-SIX |
| 7 | Seven | SEV-en | Setteseven | SAY-TAY-SEVEN |
| 8 | Eight | AIT | Oktoeight | OK-TOH-AIT |
| 9 | Nine | NIN-er | Novenine | NO-VAY-NINER |
| . | Decimal | DAY-SEE-MAL | Decimal | DAY-SEE-MAL |
| Hundred | HUN-dred | — | — | |
| Thousand | TOU-SAND | — | — | |
| (full stop) | — | — | Stop | STOP |
Annex 10 says the capitalised syllables are stressed: ZE-RO gets equal stress on both syllables, FOW-er is stressed on the first. ITU Appendix 14 says each syllable of its code words is “equally emphasized.”
So there are two official number systems. Aviation uses English digit words said in a particular way. The ITU table for spelling out figures uses compound code words: a Latin-ish prefix plus the English number, so the digit still comes through if half the word is lost. Appendix 14 also has Stop for a full stop and Decimal for a decimal point, and it lets stations of the same country “use any other table recognized by their administration.” You’re far more likely to hear TREE and NIN-er on the radio than Terrathree.
Some related number rules from Annex 10:
- Every digit is said separately by default: runway 27 is “two seven,” heading 080 is “zero eight zero” (§5.2.1.4.1.1).
- Round hundreds and thousands use HUNDRED and THOUSAND in specific cases, such as flight levels (“flight level two hundred”), altitudes (“three thousand four hundred”) and squawk 1000 (“one thousand”).
- A decimal point is DECIMAL: “100.3” is ONE ZERO ZERO DECIMAL THREE (§5.2.1.4.1.7). US practice differs. The FAA says the decimal in a frequency is spoken as “POINT” and adds that “ICAO procedures require the decimal point be spoken as ‘DECIMAL’”, which the FAA honors for aircraft following ICAO procedures.
Why niner and fife? The standards don’t say. The usual explanations are that “nine” sounds like German nein and “five” sounds like “fire” in a military setting. They make sense, but I found neither in Annex 10, Appendix 14 or the FAA manual, so treat them as folklore. What the documents do support is the general aim of pronunciations that work across accents and on noisy channels.
Common mistakes
- “Alpha” and “Juliet.” They’re wrong in a strict sense, but everyone understands them over the radio. It matters in writing: training material, checklists, a UI label. ICAO’s history page itself says the alphabet “is commonly referred to as the Alpha/Bravo/Charlie alphabet,” so the misspelling is everywhere.
- “X-ray” vs “Xray.” ICAO Figure 5-1, ITU Appendix 14 and NATO’s history page all write X-ray with a hyphen. The FAA’s AIM table writes Xray. Both show up in official US documents. The hyphenated form is what the international standards print.
- “Whiskey” vs “Whisky.” The 1951 list, as reproduced on ICAO’s history page, used Whisky. The current ICAO and ITU tables use Whiskey.
- “Zero” pronunciation. ICAO respells it ZE-RO. The FAA’s table says ZEE-RO. Close enough, but the two tables don’t match exactly.
- Treating NIN-er as the word. Written down, it’s “nine.” NIN-er is how you say it.
- Inventing words. “A as in Apple, B as in Boy” is the kind of mixed-up spelling the 1956 alphabet was meant to replace.
What our converter does
Here’s exactly what the code in the NATO phonetic tool does:
- Letters map to the ICAO words with ICAO spelling: Alfa, Juliett, Whiskey, X-ray. Upper and lower case give the same result.
- Digits map to the ICAO written words Zero … Nine. That’s the correct written form per Annex 10. The output does not add pronunciation guides like NIN-er, and it doesn’t use the ITU maritime words (Nadazero, Unaone). Say the digits using the table above.
- Spaces become
/so word breaks are visible. - Everything else passes through unchanged, including punctuation.
121.5becomesOne Two One . Five, so you read the dot as DECIMAL (or POINT in the US) yourself. The converter doesn’t pick a convention for you.
It runs in your browser, so pasting in a booking reference or an account number is fine.
The Morse side: prosigns and the 1:3:7 ratio
The spelling alphabet is for voice. Morse is the older way of sending letters without ambiguity, and the ITU still maintains it in Recommendation ITU-R M.1677-1. Two parts of it are relevant here.
Timing is relative to the dot. Section 2 defines the whole rhythm using the dot as the unit: a dash equals three dots, the gap inside a letter is one dot, the gap between letters is three dots, and the gap between words is seven. That 1 : 3 : 7 ratio is what makes Morse sound like Morse. Speed is a separate choice. Our Morse translator uses the common PARIS convention (one dot = 1200 ÷ WPM milliseconds). That formula is an operator convention and isn’t in M.1677-1, but the 1:3:7 spacing it plays is exactly what the ITU specifies.
Some signals are one character, not several letters. M.1677-1 §1.1.3 defines procedure signals alongside punctuation: understood ...-., error (eight dots), invitation to transmit -.-, wait .-..., end of work ...-.- and the starting signal -.-.-. ITU-R M.1172 writes these with a bar over the letters (AR, AS, BT, KA, VA) and explains that “a bar over the letters composing a signal denotes that the letters are to be sent as one signal”, with no letter gap. That’s why ITU’s VA and the amateur SK are the same signal: ...- + .- and ... + -.- both come out as ...-.- when run together.
Our Morse decoder recognises several of these when they’re pasted as one unbroken sequence: SOS, the eight-dot error, end of work, the starting signal and understood. The encoder uses the full M.1677-1 character table plus five common characters that aren’t in that Recommendation (! & ; _ $). The tool’s FAQ labels those five as extensions.
Neither system hides anything. Like the toy ciphers in our XOR and ROT13 post, they’re encodings, not encryption.
To spell something now, paste it into the NATO phonetic converter. To hear it as Morse, use the Morse code translator.