# Aviation

Industry: Aviation

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.

## What these functions solve

- **A schedule date reads differently on a machine set to another language.** The month letters are a fixed English code. [`parseSsimDate`](/gmt/reference/aviation/parse/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](/gmt/guides/industries/aviation-message-times/), [scenario](/gmt/scenarios/an-ssim-month-read-in-the-wrong-language/), [mistakes](/gmt/mistakes/aviation/).
- **A two-digit year lands in the wrong century.** The format does not say which century it means. [`parseSsimDate`](/gmt/reference/aviation/parse/parseSsimDate/) and [`isValidSsimDate`](/gmt/reference/aviation/validate/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](/gmt/guides/industries/aviation-message-times/), [mistakes](/gmt/mistakes/aviation/).
- **A date written back reads as another year.** [`formatSsimDate`](/gmt/reference/aviation/format/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](/gmt/guides/industries/aviation-message-times/), [mistakes](/gmt/mistakes/aviation/).
- **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`](/gmt/reference/aviation/parse/parseMetarTime/) chooses the nearest month that has the day, and [`isValidMetarTime`](/gmt/reference/aviation/validate/isValidMetarTime/) is false when the reference is missing, so a stored report reads the same every month. See [guide](/gmt/guides/industries/aviation-message-times/), [scenario](/gmt/scenarios/a-metar-from-last-month/), [mistakes](/gmt/mistakes/aviation/).
- **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`](/gmt/reference/aviation/parse/parseNotamValidity/) returns each as it is, and [`isValidNotamValidity`](/gmt/reference/aviation/validate/isValidNotamValidity/) checks an item against the window you state. See [guide](/gmt/guides/industries/aviation-message-times/), [scenario](/gmt/scenarios/perm-read-as-a-date/), [mistakes](/gmt/mistakes/aviation/).

Start with the guide: [Aviation: Message Times](/gmt/guides/industries/aviation-message-times/).

## Its own functions

### [`aviation`](/gmt/reference/aviation/)

**[format](/gmt/reference/aviation/format/)**

- [`formatSsimDate`](/gmt/reference/aviation/format/formatSsimDate/): Write an ISO 8601 date as an SSIM schedule date.

**[parse](/gmt/reference/aviation/parse/)**

- [`parseMetarTime`](/gmt/reference/aviation/parse/parseMetarTime/): Parse a METAR report-time group as an ISO 8601 UTC instant, read against a reference instant.
- [`parseNotamValidity`](/gmt/reference/aviation/parse/parseNotamValidity/): Parse a NOTAM item B) or C) value as a UTC instant, an estimate, or a permanent validity.
- [`parseSsimDate`](/gmt/reference/aviation/parse/parseSsimDate/): Parse an SSIM schedule date as an ISO 8601 date.

**[validate](/gmt/reference/aviation/validate/)**

- [`isValidMetarTime`](/gmt/reference/aviation/validate/isValidMetarTime/): Return true when `value` is a METAR, SPECI or TAF time group (`YYGGggZ`) that resolves against `referenceInstant`.
- [`isValidNotamValidity`](/gmt/reference/aviation/validate/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`](/gmt/reference/aviation/validate/isValidSsimDate/): Return true when `value` is a real SSIM date (`DDMMMYY`) in the stated hundred-year window.

## Guides

- [Aviation: Message Times](/gmt/guides/industries/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.

## Tools

- [Report Time Resolver](/gmt/tools/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](/gmt/tools/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.

## Scenarios

- [A METAR from Last Month](/gmt/scenarios/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](/gmt/scenarios/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](/gmt/scenarios/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.

## Mistakes

- [Aviation](/gmt/mistakes/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.
