Zulu time converter
Convert between Zulu and local time at any airport, in either direction. The offset comes from the airport’s own timezone rules for the date entered.
Or try one of these
Leave the date and time blank for right now. The offset comes from the selected timezone at that instant.
The NATO letter system
The Z in 1830Z is the NATO time zone letter for UTC. Each of the 25 letters (J is skipped) names a one-hour offset: A (+1) through M (+12) going east, N (−1) through Y (−12) going west. Z sits at the center. The system predates aviation — it was built for military radio — but Zulu is the only letter in routine use today, and most pilots never encounter the rest.
The NATO letters assume whole-hour offsets. India (+5:30), Nepal (+5:45), Iran (+3:30) and Newfoundland (−3:30) do not map cleanly to any letter. Those places use Zulu directly and convert, which is what this tool does.
What a handoff looks like without one clock
A westbound flight from JFK departs at 1800 Eastern, crosses into Central airspace at 1830 Eastern (1730 Central), and contacts Denver Center at 1915 Eastern (1715 Mountain). Each center would need to convert every incoming time to its own zone, and the METAR, the TAF, and the ATIS would each carry a different reference. A single wrong conversion — one hour — puts the aircraft at the wrong fix at the wrong time, which is exactly the problem Zulu eliminates by giving everyone the same number.
How this works
- Why a fixed offset is wrong twice a year
- This tool converts using the IANA timezone database — the same data the operating system uses. A lookup table gives the wrong answer twice a year at every DST transition, and it gives the wrong answer all year for India (+5:30), Nepal (+5:45), Iran (+3:30) and Newfoundland (−3:30). It also breaks silently: the result looks like a valid time, just shifted by one hour, so there is nothing to catch the mistake on the form.
- The date can change across midnight
- Zulu and local are often on opposite sides of midnight. An evening departure from the US is already tomorrow in Zulu. A morning departure from Australia is still yesterday. A flight plan with the wrong day can look correct on the form.
- The skipped hour does not exist
- On the morning the clocks go forward, the skipped hour does not match any real moment. 02:30 local in Denver on that day does not correspond to any moment in UTC. The repeated hour in autumn is different: both instants are valid because the clock shows that time twice.
20:00 local on July 15 is 02:00 UTC on July 16.
US time zones and UTC offsets
The offset changes when daylight saving time starts and ends. Arizona (except the Navajo Nation) does not observe DST. Hawaii never observes DST.
| Zone | Standard | DST | Airports |
|---|---|---|---|
| Eastern (ET) | UTC−5 | UTC−4 | KJFK, KATL, KMIA |
| Central (CT) | UTC−6 | UTC−5 | KORD, KDFW, KIAH |
| Mountain (MT) | UTC−7 | UTC−6 | KDEN, KPHX, KABQ |
| Pacific (PT) | UTC−8 | UTC−7 | KLAX, KSFO, KSEA |
| Alaska (AKT) | UTC−9 | UTC−8 | PANC, PAFA |
| Hawaii (HST) | UTC−10 | No DST | PHNL, PHOG |
Unusual offsets
Not every time zone uses a whole-hour offset. These airports require fractional-hour arithmetic that a simple “add or subtract N hours” rule cannot handle.
| Location | UTC offset | Note |
|---|---|---|
| India (VIDP) | UTC+5:30 | Half-hour offset, no DST |
| Nepal (VNKT) | UTC+5:45 | Quarter-hour offset, no DST |
| Iran (OIIE) | UTC+3:30 / +4:30 | Half-hour offset with DST |
| Newfoundland (CYYT) | UTC−3:30 / −2:30 | Half-hour offset with DST |
| Chatham Islands (NZCI) | UTC+12:45 / +13:45 | Quarter-hour offset with DST |
| Arizona (KPHX) | UTC−7 | Mountain time, but no DST ever |
Zulu time in METARs, TAFs, and NOTAMs
The timestamp is the third group in a METAR or TAF. It shows the day of the month and the four-digit time, followed by Z. For example, 231830Z means the 23rd day at 1830 Zulu.
NOTAMs use the format 2608231830 — a ten-digit string: two-digit year, two-digit month, two-digit day, four-digit time. The format implies Zulu.
Flight plans use four digits for the time and two digits for the day. The month comes from context. All times are Zulu.
Conversion examples
- Local to Zulu (summer)
- 2:00 PM Eastern Daylight Time is UTC−4. Add 4 hours: 14:00 + 4 = 1800Z.
- Local to Zulu (winter)
- 2:00 PM Eastern Standard Time is UTC−5. Add 5 hours: 14:00 + 5 = 1900Z. The same clock time converts to a different Zulu time when the offset changes.
- Zulu to local (West Coast)
- 0300Z at KSFO in summer (PDT, UTC−7). Subtract 7 hours: 03:00 − 7 = 20:00 the previous day = 8:00 PM local. The date rolled back because the result crossed midnight.
- Half-hour offset
- 1200Z at VIDP (Delhi, UTC+5:30). Add 5 hours 30 minutes: 12:00 + 5:30 = 5:30 PM local. A whole-number shortcut gives the wrong time here.
Frequently asked questions
- What is Zulu time?
- Zulu time is the aviation term for Coordinated Universal Time (UTC). The name comes from the NATO phonetic alphabet: Z is "Zulu." Aviation uses Zulu time so that every pilot, controller, and weather report worldwide references the same clock.
- Is Zulu time the same as GMT?
- For practical purposes, yes. UTC and GMT refer to the same time of day. The difference is technical: atomic clocks define UTC and adjust it with leap seconds. The rotation of the Earth defines GMT. Aviation documents use "Z" or "UTC," not "GMT."
- What does the Z mean after a time?
- The Z suffix marks the time as Zulu (UTC). A METAR stamped 1830Z means the observer recorded it at 18:30 UTC. Without the Z, a reader cannot tell whether the time is local or universal.
- How does daylight saving time affect Zulu time?
- Zulu time never changes. It is always the same worldwide. When a region moves its clocks forward or back, the offset between local time and Zulu time changes. Denver is UTC−7 in winter and UTC−6 in summer. Zulu stays the same in both seasons.
- Why does aviation use Zulu time?
- A flight from New York to Los Angeles crosses three time zones. If the departure used Eastern time and the arrival used Pacific time, every handoff between controllers would require a conversion. Zulu time removes that problem. Every time in every document refers to the same clock.
- How do I convert local time to Zulu time?
- Add the UTC offset to your local time. If you are in Eastern Daylight Time (UTC−4) and it is 2:00 PM local, Zulu time is 2:00 PM + 4 hours = 1800Z. If the result exceeds 24:00, subtract 24 and advance the date by one day.
- What time zones use half-hour or quarter-hour offsets?
- India is UTC+5:30. Iran is UTC+3:30. Nepal is UTC+5:45. Newfoundland is UTC−3:30. These fractional offsets mean you cannot convert to Zulu by adding or subtracting a whole number of hours.
- Where do I find Zulu time in a METAR or TAF?
- The timestamp is the third group in a METAR or TAF. It shows the day of the month and the time in UTC, followed by Z. For example, 231830Z means the 23rd day at 1830 Zulu.
- What is the NATO time zone letter system?
- The military uses a single letter for each time zone. Z (Zulu) is UTC. Letters A through M (skipping J) go eastward: A is UTC+1 (Alpha), B is UTC+2 (Bravo), up to M at UTC+12 (Mike). Letters N through Y go westward: N is UTC−1 (November), through Y at UTC−12 (Yankee). J (Juliet) is reserved for the observer's local time. This system predates aviation but Zulu is by far the most commonly used letter.Y−12X−11W−10V−9U−8T−7S−6R−5Q−4P−3O−2N−1Z0A+1B+2C+3D+4E+5F+6G+7H+8I+9K+10L+11M+12
- What are common mistakes when converting Zulu time?
- Three errors come up regularly. First, applying the offset in the wrong direction: UTC−5 means local time is 5 hours behind UTC, so you add 5 to go from local to Zulu and subtract 5 to go the other way. Second, forgetting that daylight saving changes the offset: Denver is UTC−7 in winter and UTC−6 in summer, and using the wrong one shifts every time by an hour. Third, mixing local and Zulu in the same logbook entry or flight plan. If the departure time is Zulu but the fuel endurance is calculated from a local clock, the result can be off by hours.
Not a substitute for an official pre-flight weather briefing.