A QSO with a station in Tokyo on 20 meters lands clean: signal report 59 both ways, the exchange crisp, the frequency quiet. You glance at the clock above the rig and log 8:15 PM. The next morning, the online logbook shows your Japanese counterpart logged the same exchange at 9:15 AM. The entries do not match. The QSL card you need for that DXCC award now hinges on a 12-hour ambiguity that could take weeks to resolve.
This is why ham radio operators use Zulu time, and why the 24-hour clock is the only honest way to record a QSO.
One clock to rule them all
Amateur radio is a global hobby. Spin the dial and you can reach someone on the other side of the planet in seconds. But those seconds happen in different local times. Your 8:15 PM in New York is 9:15 AM the next morning in Tokyo. Log using local time and every exchange becomes a math problem. Log using Zulu and it becomes a fact.
Zulu time is the military and aviation name for UTC, Coordinated Universal Time. It is the time at the prime meridian, and it does not change. No daylight saving shifts, no AM/PM, no "is that Eastern or Central?" confusion. When a ham in Germany logs a QSO at 1430 Zulu and a ham in California logs the same QSO at 1430 Zulu, those two logs match exactly. That is the entire point.
The military time zone letter for UTC+0 is Z, spoken as "Zulu" in the NATO phonetic alphabet. That is where the name comes from. Not from any military branch, not from aviation, from the letter Z. And because Zulu time never observes daylight saving, it stays constant all year while local times around the world shift around it.
The 24-hour clock removes the ambiguity
Here is the core problem with 12-hour time in radio communications: AM and PM sound too similar over a crackling signal. "Is that 8 PM or 8 AM?" is a question that has ended many promising QSOs. The 24-hour clock eliminates the question entirely.
In military time, the day runs from 0000 to 2359. Midnight is 0000, which equals 12:00 AM. Noon is 1200, which equals 12:00 PM. 1:00 PM becomes 1300. 8:15 PM becomes 2015. There is no such thing as 8:15 PM in military time. There is only 2015, and it is unambiguously evening.
The conversion is simple once you know the pattern. From midnight through 11:59 AM, military time matches the 12-hour clock with a leading zero. 1:00 AM is 0100, 9:30 AM is 0930. From noon onward, add 12 hours. 1:00 PM is 1300, 2:00 PM is 1400, all the way up to 11:00 PM, which is 2300. The most common mental error is subtracting 12 from 1200, which should be noon, not zero. Do not do that.
How to say it on the air
Spoken military time follows a specific pattern. You say the digits in groups, then add "hours" or "Zulu" for clarity. 2015 becomes "twenty fifteen hours" or "two zero one five Zulu." 0930 becomes "zero nine thirty" or "oh nine thirty." The leading zero is always pronounced. You never say "two thousand fifteen hours" for 2015; that is a common mistake. It is "twenty fifteen."
For Zulu time specifically, you usually drop the word "hours" and just say the time followed by "Zulu." "One four three zero Zulu" is how a pilot would file it, and it is exactly how a ham should log it. The word "Zulu" signals to everyone listening that you mean UTC, not your local time.
The lettered military time zones
Zulu is the most important letter, but it is not the only one. NATO established a system of lettered time zones that correspond to specific UTC offsets. The zones go from A through M, skipping J, and then N through Y. Each letter represents a one-hour increment from UTC.
The letter J is reserved for Juliett, which is the operator's local time. It sounds like "local" over poor radio, which is why it was chosen. The remaining letters cover the globe. Alpha is UTC+1, Bravo is UTC+2, all the way up to Mike at UTC+12. On the other side, November is UTC-1, Oscar is UTC-2, down to Yankee at UTC-12.
Here is the catch that trips up new operators: these letters are tied to the UTC offset, not the geographic location. When a region observes daylight saving time, its zone letter shifts. A station in New York, normally at UTC-5, which is Romeo, becomes Quebec at UTC-4 during summer. This is technically correct, but it is also confusing. Most amateur radio operators skip the letters entirely and just say "Zulu" or give the offset directly.
Logging QSOs the right way
Every serious logging program, from the free ones to the contest-grade software, uses UTC as its internal clock. You set your radio's clock to Zulu time once, and it stays there. Your logbook entries are then comparable with every other station on Earth, regardless of where either of you lives.
When you make a QSO, the routine is the same. You exchange call signs, signal reports, names, and locations. Then you log the time. In Zulu. Not in your local time, not in "military time" as a general concept, but in the specific, unambiguous UTC time that both stations can verify.
The date matters too. A QSO at 0030 Zulu on the 15th of July happened at 7:30 PM on the 14th in New York. If you log the date as the 15th, you are correct. If you log the local date, you have created a discrepancy that will take someone else time to resolve. Use the Zulu date. Write it down. Move on.
Why this matters more than ever
Digital modes like FT8 and RTTY embed timestamps in the transmission. When you decode a signal, the software logs the time automatically. But that time is only useful if your computer's clock is set to UTC. Many new operators leave their computers on local time and wonder why their digital QSOs never match the online databases. The answer is always the same: you logged the wrong time.
The same applies to contests. Every major contest uses UTC for scoring. A QSO logged at 2359 on Saturday is valid. The same QSO logged at 0001 on Sunday might fall outside the contest window. In a contest, minutes matter. In a logbook, minutes always matter.
The one-sentence mental model
Here is the entire concept in one reusable idea: Zulu time is the single, fixed reference that lets hams in different time zones agree on when a QSO happened. The 24-hour clock is the format that removes AM/PM confusion. Use both, every time, and your logs will always be correct.
The easiest way to build the habit is to set your clock to Zulu. Your phone, your computer, your radio, all of them can display UTC. Do it for a week and the 24-hour format will feel natural. Then do the same with your logging software.