# parseSsimDate

Industry: Aviation

:::caution[Unreleased]
Not in `@northguild/gmt` 1.21.0 on npm yet. It is on `main` and ships in the next release.
:::

## Signature

```ts
parseSsimDate(value: string, options: TwoDigitYearOptions): string
```

Parse an SSIM schedule date as an ISO 8601 date.

- **What it reads.** An SSIM date is `DDMMMYY`: two digits of day, the first three letters of the month's English name in upper case (`JAN` … `DEC`), and two digits of year. The result is an ISO `PlainDate` string.
- **Locale-independent.** The month letters are a fixed code, not a translation. They are never read through `Intl`, so the platform's or the caller's locale changes nothing. Lower and mixed case (`jan`, `Jan`) and other languages (`ENE`, `JANV`) return `""`.
- **The century is the caller's.** `options.yearWindow` places `YY` in a hundred-year window: a fixed first year, for stored schedules, or `"rolling"`, for live feeds. Without `yearWindow` the result is `""`.
- **Days must exist.** A day that does not exist in that month and windowed year returns `""`. `29FEB00` is a date in a window from 2000, and not in one from 1900.
- **Sources.** The day and the month letters: SSIM Chapter 6, as two guides give it. They are ACL's _An Introductory Guide to SSIM_ (April 2021), which shows `01APR`, and AECFA's _Quick Guide to Using the IATA SSIM format_, which is no longer online. The seven-character form: EUROCONTROL's _CSST Users Guide_ §3.2 Figure 1. Avinor's SSIM description shows a two-digit year in the validity period. IATA's own Chapter 7 text was not reached.

## Parameters

| Parameter | Type | Description |
| --- | --- | --- |
| `value` | `string` | An SSIM date, `DDMMMYY` (e.g. "01JAN26") |

## Options

**options**

The hundred-year window a two-digit year is read in

Type: [`TwoDigitYearOptions`](/gmt/reference/types/TwoDigitYearOptions/).

| Option | Type | Default | Description |
| --- | --- | --- | --- |
| `yearWindow?` | `number` \| `"rolling"` | None. A value with a two-digit year returns the sentinel: no standard says which century it belongs to, so the caller states it. | The hundred-year window a two-digit year falls in. A number is the first year of a fixed window, an integer from 0 to 9900: `2000` reads `00`–`99` as 2000–2099; `1950` reads `50`–`99` as 1950–1999 and `00`–`49` as 2000–2049. A fixed window gives the same answer in any year, so it is the form for stored data, archives and anything re-processed later. `"rolling"` is the hundred years around today: from 50 years before the current UTC calendar year to 49 years after it (in 2026, 1976–2075). It is the form for live messages and never needs maintenance, but it gives a different answer for the same stored value as years pass. Any other value returns the function's sentinel. |

## Returns

the ISO date ("2026-01-01"), or "" on invalid input

## Related types

- [`TwoDigitYearOptions`](/gmt/reference/types/TwoDigitYearOptions/)

## Examples

```ts
import { parseSsimDate } from "@northguild/gmt/aviation/parse";

parseSsimDate("01JAN26", { yearWindow: 2000 }) // "2026-01-01"
```

## Source

[aviation/parse/parseSsimDate.ts](https://github.com/northguild/gmt/blob/main/packages/gmt/src/aviation/parse/parseSsimDate.ts)
