Effective Dates
Required roles:
AIS PIB API— Roles
Base endpoint:https://ais-pib-api.ibosoft.net.tr:2087/eff-dates
Reference documents: ICAO Annex 15, Ed. 16 (Amend. 41) (8/11/18) · ICAO Doc 8126 Aeronautical Information Services Manual, Ed. 7, Amend. 1 (30/07/24) · Jeppesen Airway Manual
Attribution: showibonav.aerowherever this data is displayed
Data sources: none — calculated.
Last updated: 17 OCT 2026About the reference documents: Related Documents and Resources
AIRAC cycles and Jeppesen bi-weekly cycles: the current cycle, the effective date of a cycle or of a date, and the AIRAC advance dates (28, 42 and 56 days before the effective date). Calculated on request; all dates are UTC.
Endpoints
| Endpoint | Description |
|---|---|
GET /eff-dates/airac-current |
Current AIRAC cycle |
GET /eff-dates/airac-effective |
AIRAC cycle and effective date for a cycle or a date |
GET /eff-dates/airac-advance-28 |
28 days before the AIRAC effective date |
GET /eff-dates/airac-advance-42 |
42 days before the AIRAC effective date |
GET /eff-dates/airac-advance-56 |
56 days before the AIRAC effective date |
GET /eff-dates/jepp-biweek-current |
Current Jeppesen bi-weekly cycle |
GET /eff-dates/jepp-biweek-effective |
Jeppesen cycle and effective date for a cycle or a date |
Parameters
The -current endpoints take no parameters. The others take exactly one of:
| Parameter | Description |
|---|---|
cycle |
AIRAC: YYNN (e.g. 1812). Jeppesen: NN-YYYY (e.g. 01-2026) |
date |
UTC date, YYYY-MM-DD or ISO 8601 date-time; gives the cycle in effect on that date |
Supported range: AIRAC from 1 November 1964 to 2099; Jeppesen from 1 January 1970 to 2099.
How cycles are counted
- AIRAC: common effective dates at 28-day intervals (Annex 15, Chapter 6; Doc 8126, 3.5), counted from the reference 8 November 2018 = AIRAC
1812.YYis the year,NNthe number of the cycle within that year. - Jeppesen bi-weekly: the 14-day revision cycle of the Jeppesen Airway Manual, from the reference 2 January 2026 =
01-2026.NNis the number of the cycle within the year.
Response
/airac-current, /airac-effective, /jepp-biweek-current, /jepp-biweek-effective
GET /eff-dates/airac-effective?cycle=1812
GET /eff-dates/airac-effective?date=2018-11-08
{"cycle": "1812", "effective_date": "2018-11-08", "effective_date_fmt": "08 NOV 2018"}
GET /eff-dates/jepp-biweek-effective?cycle=01-2026
{"cycle": "01-2026", "effective_date": "2026-01-02", "effective_date_fmt": "02 JAN 2026"}
/airac-advance-28, -42, -56
{"advance_date": "2018-10-11", "advance_date_fmt": "11 OCT 2018"}
Errors
Invalid input gives 422:
{"valid": false, "error": "Invalid or out-of-range AIRAC cycle: '1814'."}
| Case | error |
|---|---|
| Both parameters | Provide either 'cycle' or 'date', not both. |
| Neither parameter | Either 'cycle' or 'date' query parameter is required. |
| Invalid cycle | Invalid or out-of-range … cycle: '…'. |
| Unreadable date | Cannot parse date: '…'. Expected YYYY-MM-DD or ISO datetime. |
| Date too early | Date is before the minimum supported date (…). |
| Year too late | Date exceeds the maximum supported year (…). |