Zulu time converter: decoding the DDHHMMZ group

Tafrob editorial team · Updated · 7 min read

Short answer

Zulu is the aviation name for UTC. A METAR time group has six digits followed by Z: two for the day of the month, two for the hour and two for the minute, so 191450Z is the 19th at 14:50 UTC. The month is never coded. The converter picks the month that places the date closest to the current moment, and shows the result in UTC and in local time.

Runs in your browser. Training and planning aid only, not for operational use.

Key points

  • DDHHMMZ is the day of the month, the hour and the minute in UTC, always followed by Z.
  • The group never carries a month or a year, so the reader infers them from the moment of reading.
  • FMH-1 requires every disseminated time to use the 24-hour UTC clock, and the group always ends with Z.
  • The calculator tests the previous, current and next month and keeps the date nearest to now, skipping days that do not exist.
  • A report older or newer than about two weeks can be placed in the wrong month, and TAF groups with eight digits are not read.
Time ball on the roof of the Royal Observatory at Greenwich
Photo: Perituss, CC0, via Wikimedia Commons

What the converter does

The converter has one optional input, a day-time group, and shows its results in three or five lines. It does not need any input to give the first three lines:

  • the current UTC (Zulu) date and time, to the minute;
  • the current local time, with the time zone name taken from the browser;
  • the current time written as a METAR-style group, DDHHMMZ.

When a group is typed in the box, two more lines appear. The first is the decoded date in UTC, with the same moment in the local time of the device. The second says how long ago the moment was, or how far ahead it lies, in hours and minutes. All of it runs in the browser, using the clock of the device.

Zulu is UTC

The Federal Meteorological Handbook No. 1 states that the date and time group of a METAR always ends with a Z indicating Zulu time, or UTC, and gives the example METAR KDCA 210855Z, the 0900 scheduled report from station KDCA taken at 0855 UTC on the 21st of the month. The same handbook requires all times disseminated in observations to reference the 24-hour UTC clock, so 1:47 A.M. is 0147 and 1:47 P.M. is 1347. The times 0000 and 2359 indicate the beginning and the end of the day.

ICAO and WMO use the same writing. WMO-No. 782 shows the group as YYGGggZ and explains it as the day of the month and the time of observation in hours and minutes. CAP 746 states that all times quoted in the TREND section are UTC. A pilot who sees a time without a time zone in an aviation weather report can assume UTC. The group itself is covered with the station identifier on the time group page.

Reading the day-time group

The six digits are three pairs:

Pair Meaning Range accepted by the page
DD Day of the month 01 to 31
HH Hour, 24-hour clock 00 to 23
MM Minute 00 to 59

The page accepts the group with or without the final Z, in capitals or lower case, with spaces around it removed. Anything else is refused with a message asking for six digits. A group whose day, hour or minute is outside the ranges above returns the same message.

A METAR does not contain a month or a year. The report is meant to be read within hours of its issue, so the reader supplies the rest. For a person this is trivial. For a program, or for a pilot reading an archived report, it is a real problem, and that is the part of the page that does work.

How the month is chosen

The code builds up to three candidate dates in UTC, using the day, hour and minute of the group and the month before, the current month and the month after. A candidate whose day does not exist in that month is dropped, because the date arithmetic would otherwise roll it into the next month. Among the remaining candidates the page keeps the one closest to the current moment, in either direction.

This gives sensible answers in the cases that matter.

Group Moment of reading (UTC) Decoded date Why
191450Z 19 Nov 2026, 15:10 19 Nov 2026, 14:50 Same month, 20 minutes earlier
302350Z 1 Dec 2026, 00:10 30 Nov 2026, 23:50 The 30th of December is a month away
282330Z 1 Mar 2026, 01:00 28 Feb 2026, 23:30 2026 is not a leap year, so the 28th is the last day of February
310000Z 28 Feb 2026, 12:00 31 Jan 2026, 00:00 31 January is 28 days back and 31 March is 31 days ahead, so January wins

The third row works because dates in UTC are built with the year of the reference moment, so the calendar of that year decides the length of February. The fourth row shows why dropping nonexistent days matters: without that step, a group such as 310000Z tested against February would roll to the 3rd of March, a date that looks plausible and is wrong.

The two weeks limit

Picking the nearest date works only if the report is close in time to the moment of reading. A month is 28 to 31 days, so a group more than about half a month away is nearer to a different month. For instance, a group 030000Z read on 19 November is 16 days before 3 November but only 14 days before 3 December, so the page decodes it as 3 December and says it is 14 days ahead. A report that old is not a current observation, and the result is a wrong guess, not an error message.

The practical rule is simple: use the page for reports from the last day or two, which is what a METAR and a TAF are. An archive search needs the date from the file name or the database, not from the group.

What the page does not read

The converter accepts exactly six digits. It does not accept:

  • a TAF validity period such as 1307/1316, which uses the form DDHH/DDHH; WMO-No. 782 decodes the example TAF LUDO 130530Z 1307/1316 as an aerodrome forecast issued at 0530 UTC on the 13th and valid from 0700 to 1600 UTC on the 13th;
  • the FMddhhmm change group of a TAF, which has no Z;
  • the hour 24, which the converter rejects because the hour must be 23 or less. WMO-No. 782 notes that a change forecast at midnight UTC is written as 0000 after FM and AT, and as 2400 after TL in a TREND forecast;
  • the hhmm times of a TREND, such as FM1530, which carry no day.

The issue time of a TAF, which is the six-digit group after the station, is accepted. The validity of a TAF is explained on the TAF validity period page, and the TREND times on the TREND page.

Zulu in other aviation messages

The same notation appears in other products. The Aeronautical Information Manual shows convective SIGMET validity as VALID UNTIL 1455Z, lists scheduled AIRMET issue times such as 0245, 0845, 1445 and 2045 UTC, and calls an AIRMET type "Zulu" because the letter has the same name as the time standard. The word is a coincidence of the phonetic alphabet, not a time: AIRMET Zulu describes moderate icing and freezing level heights.

Radio phraseology also uses it. The AIM shows an automated weather observation broadcast read as "one four five six zulu", meaning 1456 UTC. In a local time zone the same moment would be a different number, which is why the reference is fixed. The ATIS content is covered on the ATIS page.

A schematic report

METAR LXXX 191450Z 27008KT 9999 SCT040 12/04 Q1018

The group is 191450Z. Typed into the converter with the current time at 19 November 2026, 15:10 UTC, the page returns 2026-11-19 14:50 UTC, the equivalent local time of the device, and "That was 0 h 20 min ago". A pilot at UTC-5 would see 09:50 on the local clock and a pilot at UTC+1 would see 15:50, but both read the same group.

A second line shows the rollover:

METAR LXXX 302350Z 00000KT 9999 FEW250 05/02 Q1022

Read at 00:10 UTC on 1 December 2026, the report is 20 minutes old and belongs to 30 November, not to a December 30th that has not happened yet. The converter makes this choice because 30 November 23:50 is 20 minutes from the reading and 30 December 23:50 is a month away.

In real reports

In real reports the time group is the second or third item of the report, after the type and the station, and it is the only part of the date that appears. US scheduled reports are stamped a few minutes before the hour, as the FMH-1 example 0855 for the 0900 report shows. The scheduled time and the time of observation can therefore differ, and the group gives the observation time. For a full METAR, the order of all groups is on the how to read a METAR page.

Method and limits

The meaning of Z and the 24-hour UTC rule are from the Federal Meteorological Handbook No. 1, sections 2.6.4 and following. The YYGGggZ form, the TAF example and the midnight rule are from WMO-No. 782, and the statement that TREND times are UTC is from CAP 746. The AIM examples are those printed in its chapter 7 section 1. The month selection is an implementation choice of the calculator and is not part of any standard: the standards leave the month to the reader. The method fails for groups more than about 15 days from the reference date, for groups with eight digits, and for the hour 24. The local time shown depends on the device clock and time zone. The METAR lines are schematic, not real reports. The photograph shows a time ball and is not related to a report. The page must not be used for operational time keeping.

Source code of this tool (MIT)
// Tafrob calculators - pure functions, MIT licence (c) Tafrob.
// Every formula is documented on the tool page with its source.

const rad = (d: number) => (d * Math.PI) / 180;

/** Wind components on a runway. dir/heading in degrees (same reference: both true or both magnetic). */
export function windComponents(windDir: number, speed: number, runwayHeading: number) {
  const angle = ((windDir - runwayHeading + 540) % 360) - 180; // -180..180, + = from the right
  const cross = speed * Math.sin(rad(angle));
  const head = speed * Math.cos(rad(angle));
  return { angle, cross, head }; // cross > 0: from the right; head < 0: tailwind
}

/** Saturation vapour pressure (hPa), Magnus formula with Alduchov & Eskridge (1996) coefficients. */
export const satVap = (tC: number) => 6.1094 * Math.exp((17.625 * tC) / (tC + 243.04));

/** Relative humidity (%) from temperature and dew point (deg C). */
export const relHumidity = (tC: number, tdC: number) => (100 * satVap(tdC)) / satVap(tC);

/** Dew point (deg C) from temperature (deg C) and relative humidity (%). */
export function dewPoint(tC: number, rh: number) {
  const g = Math.log(rh / 100) + (17.625 * tC) / (243.04 + tC);
  return (243.04 * g) / (17.625 - g);
}

/** Convective cloud base estimate above ground (ft) from the temperature/dew point spread (deg C). */
export const cloudBaseFt = (tC: number, tdC: number) => ((tC - tdC) / 2.5) * 1000;

/** Pressure altitude (ft) from field elevation (ft) and altimeter setting (inHg). FAA rule: 1,000 ft per inHg. */
export const pressureAltitude = (elevFt: number, altInHg: number) => elevFt + (29.92 - altInHg) * 1000;

/** ISA temperature (deg C) at a pressure altitude (ft). */
export const isaTemp = (paFt: number) => 15 - (1.98 * paFt) / 1000;

/** Station pressure (inHg) from altimeter setting (inHg) and elevation (m), NWS formula. */
export const stationPressure = (altInHg: number, elevM: number) => altInHg * Math.pow((288 - 0.0065 * elevM) / 288, 5.2561);

/**
 * Density altitude (ft), NWS method (WFO El Paso): station pressure and virtual temperature (humidity included).
 * e = 6.11 * 10^(7.5 * Td / (237.3 + Td)) hPa; DA = 145366 * (1 - (17.326 * P / Tv)^0.235), P in inHg, Tv in degrees Rankine.
 * Same constants as the NWS page, so results can be checked against it (a dry ISA sea level case gives about 18 ft, not 0).
 */
export function densityAltitude(elevFt: number, altInHg: number, tC: number, tdC?: number) {
  const p = stationPressure(altInHg, elevFt * 0.3048); // inHg
  const pHpa = p * 33.8639;
  const e = tdC === undefined ? 0 : 6.11 * Math.pow(10, (7.5 * tdC) / (237.3 + tdC)); // NWS vapour pressure
  const tK = tC + 273.15;
  const tvK = tK / (1 - (e / pHpa) * (1 - 0.622));
  const tvR = tvK * 1.8;
  const da = 145366 * (1 - Math.pow((17.326 * p) / tvR, 0.235));
  const pa = pressureAltitude(elevFt, altInHg);
  const thumb = pa + 120 * (tC - isaTemp(pa)); // rule of thumb: 120 ft per deg C above ISA
  return { da, pa, thumb, isa: isaTemp(pa), stationInHg: p };
}

/** Pressure conversions. */
export const HPA_PER_INHG = 33.8639;
export const HPA_PER_MMHG = 1.333224;
export const hpaToInhg = (h: number) => h / HPA_PER_INHG;
export const inhgToHpa = (i: number) => i * HPA_PER_INHG;
/** METAR A group: hundredths of inHg rounded down (FMH-1 11.5.1); the epsilon absorbs float error (29.92 -> 2991.9999...). */
export const aGroup = (hpa: number) => 'A' + String(Math.floor(hpaToInhg(hpa) * 100 + 1e-6)).padStart(4, '0');
/** Pressure altitude offset (ft) from 1013.25 hPa with the AIM rule of 1,000 ft per inHg (about 29.5 ft per hPa). */
export const pressureOffsetFt = (hpa: number) => ((1013.25 - hpa) / HPA_PER_INHG) * 1000;

export type Category = 'VFR' | 'MVFR' | 'IFR' | 'LIFR';
/** US flight category (NWS / Aviation Weather Center definitions). ceiling in ft AGL (Infinity if none), visibility in statute miles. */
export function flightCategory(ceilingFt: number, visSm: number): { cat: Category; byCeiling: Category; byVis: Category } {
  const c: Category = ceilingFt < 500 ? 'LIFR' : ceilingFt < 1000 ? 'IFR' : ceilingFt <= 3000 ? 'MVFR' : 'VFR';
  const v: Category = visSm < 1 ? 'LIFR' : visSm < 3 ? 'IFR' : visSm <= 5 ? 'MVFR' : 'VFR';
  const rank: Category[] = ['LIFR', 'IFR', 'MVFR', 'VFR'];
  const cat = rank[Math.min(rank.indexOf(c), rank.indexOf(v))];
  return { cat, byCeiling: c, byVis: v };
}

/** Speed conversions (from knots). */
export const KT = { mps: 0.514444, kmh: 1.852, mph: 1.150779 };

/** Interpret a METAR/TAF day-time group DDHHMMZ relative to a reference date (UTC). */
export function dayTimeGroup(group: string, ref = new Date()) {
  const m = group.trim().toUpperCase().match(/^(\d{2})(\d{2})(\d{2})Z?$/);
  if (!m) return null;
  const [d, h, mi] = [Number(m[1]), Number(m[2]), Number(m[3])];
  if (d < 1 || d > 31 || h > 23 || mi > 59) return null;
  // Choose the month that puts the date closest to the reference date.
  let best: Date | null = null;
  for (const off of [-1, 0, 1]) {
    const c = new Date(Date.UTC(ref.getUTCFullYear(), ref.getUTCMonth() + off, d, h, mi));
    if (c.getUTCDate() !== d) continue;
    if (!best || Math.abs(+c - +ref) < Math.abs(+best - +ref)) best = c;
  }
  return best;
}

Training and reference only. For flight planning, always use official briefing sources (your national weather service, AIS or approved provider).

Frequently asked questions

What does the Z mean in a METAR time?

The Z means Zulu time, which is UTC. The Federal Meteorological Handbook No. 1 says the date and time group always ends with a Z indicating Zulu time or UTC, and it gives METAR KDCA 210855Z as the 0900 scheduled report taken at 0855 UTC on the 21st. No local time zone ever appears in the group.

How do you read 191450Z?

Read it in three pairs: 19 is the day of the month, 14 is the hour and 50 is the minutes. The report was made on the 19th at 14:50 UTC. The month and year are not written, so they come from the date on which the report is read. The converter shows the full date and the local equivalent.

How does the converter find the month?

It builds the date in the previous, the current and the next month, drops any date that does not exist such as the 31st of a 30-day month, and keeps the one closest to the current time. A group of 302350Z read just after midnight on the 1st is therefore placed on the 30th of the previous month.

Can it read the eight-digit groups of a TAF?

No. The converter accepts exactly six digits, DDHHMM, with an optional Z. A TAF validity such as 1307/1316 has the form DDHH/DDHH and is not accepted. The issue time of a TAF, for example 130530Z, uses the same six-digit form as a METAR and can be typed in.

Is 2400 a valid time?

Not in this converter, which rejects an hour above 23. WMO-No. 782 uses 2400 in one case: the end of a TREND forecast period at midnight when it follows TL, while FM and AT use 0000. A TAF validity can also end at hour 24. The tool does not decode those groups.

Sources

  1. Office of the Federal Coordinator for Meteorology (2019). Federal Meteorological Handbook No. 1 (FCM-H1-2019)
  2. World Meteorological Organization (2025). Aerodrome Reports and Forecasts, A Users' Handbook to the Codes (WMO-No. 782)
  3. UK Civil Aviation Authority (2023). CAP 746, Requirements for Meteorological Observations at Aerodromes
  4. Federal Aviation Administration. Aeronautical Information Manual, chapter 7, section 1