UTC is the same clock as Zulu. Live clocks, the full hour chart and the daylight saving rule that catches people out.
Zulu time is UTC — the clock every flight plan, order and server log is written in, precisely because it never moves. Coordinated Universal Time (UTC) sits UTC±0, which makes it the same clock as Zulu. The two read the same, so there is nothing to add — the only thing left to get right is which clock the other side actually meant.
The converter above tracks the current time until you type into it. Enter any Zulu time — 1730Z, 17:30Z or NOW — and it renders the same instant in UTC in 24-hour, 12-hour and dated form. The chart below is the same conversion for every hour of the day, so it can be read without typing anything at all.
Every hour from 0000Z to 2300Z. One column is enough — UTC keeps the same offset all year. Where the sum crosses midnight the date moves with it, marked in the cell.
| Zulu | UTCUTC±0 |
|---|---|
| 0000Z | 00:00 |
| 0100Z | 01:00 |
| 0200Z | 02:00 |
| 0300Z | 03:00 |
| 0400Z | 04:00 |
| 0500Z | 05:00 |
| 0600Z | 06:00 |
| 0700Z | 07:00 |
| 0800Z | 08:00 |
| 0900Z | 09:00 |
| 1000Z | 10:00 |
| 1100Z | 11:00 |
| 1200Z | 12:00 |
| 1300Z | 13:00 |
| 1400Z | 14:00 |
| 1500Z | 15:00 |
| 1600Z | 16:00 |
| 1700Z | 17:00 |
| 1800Z | 18:00 |
| 1900Z | 19:00 |
| 2000Z | 20:00 |
| 2100Z | 21:00 |
| 2200Z | 22:00 |
| 2300Z | 23:00 |
There is no arithmetic. Zulu and UTC are the same clock reading, so 1730Z is 17:30 UTC; only the notation changes.
Do the arithmetic in Zulu and convert once, at the end, for whoever needs a local time. Adding en-route time to a departure slot in local time and converting afterwards is how the day boundary gets lost. The Zulu time converter does both halves in one box.
There is nothing to convert. Zulu is the spoken and written name for UTC in aviation and military use — 0800Z and 08:00 UTC are the same instant, and neither ever observes daylight saving. That is the entire reason operations are logged in it.
Because neither clock shifts, a conversion written down today is still right in six months. That is unusual — most of the abbreviations on the sibling pages have a second offset for half the year.
Every flight plan, METAR, TAF, NOTAM, satellite ephemeris and server log. UTC is the reference clock the other rows on this site are measured against.
Flight plans, METARs, TAFs, NOTAMs and ATC clearances are all in Zulu, and so are military orders, satellite passes and incident timelines. The conversion to UTC is the last step, for the people who have to be somewhere at a local hour — a briefing time, a crew report, a maintenance window. Written the aviation way it carries the day of the month too: 141730Z is the 17:30 Zulu of the 14th, which removes the last ambiguity a date shift can create. See military time for the four-digit notation itself.
UTC is the same clock as Zulu (UTC±0). 1200Z is 12:00 UTC — the two clocks read the same.
No. UTC stays on UTC±0 all year, so a single conversion works in every season. Zulu does not change either.
0000Z is 00:00 UTC.
Yes, for every practical purpose. Zulu is how UTC is written and spoken in aviation and military use — the Z suffix is the phonetic letter for the zero-offset zone. GMT is the older name for the same clock reading, though the UK itself moves to BST in summer.
The two are the same clock, so the time is unchanged — only the suffix differs, e.g. 08:00 becomes 0800Z.