Zulu time converter for pilots

Aviation runs on a single global clock. Here's why, how to convert between it and your local time, and where it bites pilots crossing time zones or DST.

"Zulu" is the phonetic for the letter Z, and Z stands for Coordinated Universal Time (UTC) — the time at zero degrees of longitude, with no daylight-saving offset. Every METAR, TAF, NOTAM, AIRMET, SIGMET, IFR clearance, and ATC instruction is timestamped in Zulu, so two pilots on opposite coasts can read the same forecast and agree on what "by 1800Z" means.

Why aviation uses UTC

One clock across time zones. A flight from Los Angeles to New York crosses three time zones — if the flight plan, NOTAMs, and ATC clearances each used local time you'd be doing time math instead of flying.
No DST drift. Daylight saving time shifts twice a year on different dates in different countries. Zulu doesn't move.
One date. Late-night and early-morning flights cross midnight UTC at different points depending on longitude. Stamping records in Zulu keeps the date stable.

The conversion shortcut

Convert by adding or subtracting the offset between your local time zone and UTC. Standard offsets for the contiguous US:

Eastern Standard Time (EST): UTC − 5. Eastern Daylight Time (EDT): UTC − 4.
Central Standard Time (CST): UTC − 6. Central Daylight Time (CDT): UTC − 5.
Mountain Standard Time (MST): UTC − 7. Mountain Daylight Time (MDT): UTC − 6. (Arizona stays on MST year-round.)
Pacific Standard Time (PST): UTC − 8. Pacific Daylight Time (PDT): UTC − 7.

So 14:00 local PDT = 14 + 7 = 21:00Z. 06:30 local EST = 06:30 + 5 = 11:30Z.

Worked example: a same-day round trip

You're departing KJFK (Eastern, in DST so UTC − 4) at 09:00 local. The flight is 6 hours to KLAX (Pacific, in DST so UTC − 7). What time is wheels-down in local, and what's the corresponding Zulu time?

Departure in Zulu: 09:00 + 4 = 13:00Z.
Arrival in Zulu: 13:00Z + 6:00 = 19:00Z.
Arrival in local at the destination: 19:00Z − 7 = 12:00 local.

The flight took six hours and the wall clock at the destination only ticked three hours, because you flew "against" the rotation of the earth. The Aero Companion pilot UTC / Zulu time converter shows origin local, destination local, UTC, and the back-at-origin clock on a single line, so you don't have to keep track of two offsets at once.

Reading METAR and TAF timestamps

METAR observations and TAF forecasts use a six-digit timestamp: DDHHMMZ. The day-of-month is the first two digits, the hour is the next two, and the minutes are the last two — all in Zulu.

METAR KJFK 201756Z ... means the observation was taken at 17:56Z on the 20th of the month.
TAF KJFK 201720Z 2018/2118 ... was issued at 17:20Z on the 20th, and is valid from 18:00Z on the 20th through 18:00Z on the 21st.

If you read those at 1:00pm local on the East Coast in summer (UTC − 4), the observation was four minutes ago and the TAF window starts in about 13 minutes.

NOTAMs and the date roll-over

NOTAMs are also stamped in Zulu and span date boundaries. A NOTAM that reads "WEF 2102000Z TIL 2112359Z" runs from 20:00Z on the 21st through 23:59Z on the 21st — a four-hour window. Where this trips pilots up is when the local date and the Zulu date disagree at the time of the flight. Late-night flights on the US West Coast cross 0000Z several hours before local midnight; check the Zulu date when you read NOTAMs.

Daylight saving traps

The US and Europe switch DST on different weekends. Plans that cross the Atlantic during March or October may straddle a DST change.
Arizona, Hawaii, and most of Saskatchewan don't observe DST. Their offset to UTC doesn't change.
Sectional charts and the AIM list runway and airspace times in local — convert to Zulu before comparing them to METAR/TAF/NOTAM windows.

Common pitfalls

"It's the same time, just in Zulu." No — Zulu doesn't shift with DST, so the local↔Zulu offset changes twice a year.
Wrong sign. US zones add to local to get Zulu; Europe and Asia (mostly) subtract.
Hour wrap-around. 23:00 local + 7 hours = 06:00Z the next day. Update the date too.
Flight log entries. Mix of local and Zulu in the same row is the easiest way to put yourself out of currency or duty-time compliance. Pick one and stay consistent.

Use this guide as a refresher, not as a regulatory source. Follow the official aviation timekeeping conventions in the AIM, in the applicable regulations, and in your operations manual. The pilot in command is responsible for confirming times against the official briefing.

Related guides and tools

Pilot UTC / Zulu time converter — origin local, destination local, UTC, and back-at-origin in one view.
VFR flight planning checklist — where the time check sits in the broader preflight flow.
Flight diversion planning guide — how to keep clocks straight when you change destinations.
Glide-aware VFR flight planner — wind-aware route planning with both local and Zulu times in the plan summary.