Skip to content

Aviation

  • Airline schedule dates in IATA SSIM files, METAR and TAF report times with no month, and NOTAM validity times.

Airlines exchange schedules in IATA’s SSIM files, and their dates are not ISO. A date there is a day, three English month letters and a two-digit year. This layer reads and writes that date without the platform’s language settings and without picking a century for you.

  • A schedule date reads differently on a machine set to another language. The month letters are a fixed English code. parseSsimDate reads them from a constant table and never asks the platform’s language, so the same file gives the same date everywhere. See guide, scenario, mistakes.
  • A two-digit year lands in the wrong century. The format does not say which century it means. parseSsimDate and isValidSsimDate take the hundred-year window you state, a fixed start for an archive or a rolling one for a live feed, and give nothing without it. See guide, mistakes.
  • A date written back reads as another year. formatSsimDate writes upper-case letters and refuses a year outside your window, so reading its output back with the same window gives the same date. See guide, mistakes.
  • A weather report names a day and no month, and the wrong month is chosen. A METAR time needs a reference instant you state, and is never read against now. parseMetarTime chooses the nearest month that has the day, and isValidMetarTime is false when the reference is missing, so a stored report reads the same every month. See guide, scenario, mistakes.
  • A NOTAM end of PERM is stored as a date. PERM is a state, not a far-future date, and EST keeps its instant. parseNotamValidity returns each as it is, and isValidNotamValidity checks an item against the window you state. See guide, scenario, mistakes.

Start with the guide: Aviation: Message Times.

format

parse

  • parseMetarTime: Parse a METAR report-time group as an ISO 8601 UTC instant, read against a reference instant.
  • parseNotamValidity: Parse a NOTAM item B) or C) value as a UTC instant, an estimate, or a permanent validity.
  • parseSsimDate: Parse an SSIM schedule date as an ISO 8601 date.

validate

  • isValidMetarTime: Return true when value is a METAR, SPECI or TAF time group (YYGGggZ) that resolves against referenceInstant.
  • isValidNotamValidity: Return true when value is a NOTAM item B) or C) value (YYMMDDHHMM, the same followed by EST, or PERM) in the stated hundred-year window.
  • isValidSsimDate: Return true when value is a real SSIM date (DDMMMYY) in the stated hundred-year window.
  • Aviation: Message Times: Read the SSIM schedule date, the METAR report time and NOTAM validity — English month letters that ignore the platform’s language, a century the caller states, and a reference instant for a time that names no month.
  • Report Time Resolver: Read a METAR, SPECI or TAF time such as 302350Z against a reference you state, see the candidate months on a strip, and read NOTAM items B) and C) in a window you state.
  • SSIM Date Reader: Read an IATA SSIM date such as 01JAN26 in a window you state, see why a locale pattern parser reads the same text differently, and write an ISO date back.
  • A METAR from Last Month: A report received at 00:05 on 1 July carries 302350Z, and a reader that assumes the current month puts it 30 days ahead.
  • An SSIM Month Read in the Wrong Language: A schedule import runs on a server set to Spanish, and a parser that reads month names through the locale rejects 01JAN26 and accepts 01ENE26.
  • PERM Read as a Date: A NOTAM ends in PERM, a parser turns it into 9999-12-31, and an “is it in force?” check is right until that day.
  • Aviation: Common mistakes with SSIM schedule dates, METAR report times and NOTAM validity — the month letters, the century, the window, the reference month, PERM and EST — in GMT’s Aviation layer.
© 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.