Report Time Resolver
A weather report writes its time as DDHHMMZ, such as 302350Z. There is a day, an hour and a minute, and no month. To read it you need a reference: the time you received the report, or another time you trust. A NOTAM is different. Items B) and C) carry the year, the month and the day, in a two-digit year that needs a window, and item C) can be PERM or end in EST.
Section 1 reads a group against a reference you type and draws the candidate months on a strip. A slider moves the reference across a month end. Section 2 reads items B) and C) in a window you state. Every instant, month, gap and distance on the page is a library result, and each section prints the calls it made.
METAR reads. parseMetarTime takes the group and the reference you state, and returns the instant of the nearest month that has the day. A tie goes to the earlier. It never reads the clock, so the same report gives the same answer in any month.
METAR valid. isValidMetarTime is true exactly when the read returns an instant. With no reference it is false, because a group alone is not a time.
NOTAM reads. parseNotamValidity reads a ten-digit item as an instant in the window you state, reads EST as an instant that is estimated, and reads PERM as a state with no date.
NOTAM valid. isValidNotamValidity is true exactly when the read returns a result. With no window it is false for every item, PERM included.
The strip. The seven slots are the months around the answer, from three back to three forward. Each one is addUtc with overflow: "reject", so a month without the day is a gap and not a shifted date. The chosen candidate is the one equal to the library’s answer, and the page marks it with a ring as well as a colour.
See Aviation message times, a METAR from last month, PERM read as a date and Aviation mistakes. The time formats follow WMO and ICAO, with EUROCONTROL’s OPADD for the NOTAM rules ICAO leaves out.
Worth trying:
- A report across a month end —
302350Zreceived just after midnight on 1 July reads as 30 June, not July. - 31 near February —
312359Zat 1 March: February has no 31st, so the strip shows a gap and the answer is 31 January. - Equally near — two candidates sit the same time from the reference. A tie goes to the earlier.
- A reference with an offset — months are counted in UTC, so a reference of
00:05+02:00on 1 July is still on 30 June. - No reference — a report time names no month, so with no reference nothing is read, and the page says why.
- An estimated end —
1407031230ESTis an instant that is estimated, not a different kind of value. - Permanent —
PERMis a state with no date, shown as “permanent, no date” and not as a far-future instant. - No window — nothing says which century
25is, so with no window there is no date, andPERMis refused too. - EST in item B) — the library reads it, and a note says ICAO allows
ESTin item C) only. - Write the end of a day as 2400 —
2506152400is refused: ICAO writes the end of a day as 2359.
© 2026 NorthGuild · Licences
Code examples: MIT-0. Packages: MIT. Third-party data and components: their own licences, credited where they appear. Everything else: © 2026 NorthGuild, all rights reserved.