1

AIS-AIMSG/2-SN/6
/ AIS-AIMSG/8-SN/6
04-08/11/13

AERONAUTICAL INFORMATION SERVICES TO AERONAUTICAL INFORMATION MANAGEMENT STUDY GROUP (AIS-AIMSG)

EIGTH MEETING

Montréal, 4 to 8November 2013

Agenda Item / 5: / Temporality and Distribution
5.1: / Annex 15 Chapter 5 development

Proposal for chapter 5 (Aeronautical Information Updates)

(Presented by Paul Bosman)

SUMMARY
This paper has been prepared in order to present to the members on the Study Group a proposal for the content of the future Chapter 5 of the Annex 15, after AMDT 38.
The options proposed considers the work done to date for the content and structure of chapters 4 (data scope) and 6 (products and services), both for the Annex 15 and for the PANS-AIM. These options have resulted from discussions that took place after the Friedrichshafen meeting, mainly between Eurocontrol and DSNA
TheGroup is invited to:
a) discuss the options proposed in this paper and decide on the approach to be followed for the finalisation of this chapter.

1.INTRODUCTION

1.1Chapter 5 is earmarked in AMDT 38 to contain SARPS for the update of the aeronautical data that is collected, processed and distributed by AIS.

1.2As a starting point, it needs to include the current AIRAC cycle requirements and recommendations from Annex 15, AMDT 37, Chapter 6. In addition, this chapter could contain requirements related to the update of the aeronautical information, such as for the updated of the AIP, of a data set, or of the data that is collected and distributed in general.

1.3Three options have been investigated for Chapter 5:

  • only AIRAC cycle SARPS (similar to the current Chapter 6 in Annex 15, AMDT 37);
  • AIRAC cycle SARPS and general requirements only for data update, related to Chapter 4 (data scope); this option is detailed in Annex A;
  • AIRCA cycle SARPS and specific requirements for the update of the AIS products and data sets, related to Chapter 6; this option is detailed in Annex B.
  • The three optionswill be further explained during the meeting, including the pros/cons identified for each.

2.action by the group

2.1The group is invited to:

a)discuss the options proposed in this paper and decide on the approach to be followed for the finalisation of this chapter.

Annex A – option 2 (general requirements only for data scope update)

Chapter 5 - Aeronautical information updates

5.1 General specifications

5.1.1 Aeronautical information defined in Chapter 4 shall be amended or reissued at such regular intervals as may be necessary to keep them up to date.

5.1.2 Permanent changes to the aeronautical information shall be published as AIP Amendments and/or provided as data sets.

5.1.3 Temporary changes of long duration (three months or longer) and information of short duration which contains extensive text and/or graphics shall be published as AIP Supplements and/or data sets.

5.1.4 Changes to the aeronautical information in 5.1.2 and 5.1.3 provided as datasets shall be in the form of a completely re-issued data set and/or a sub-set that includes just the differences from the previously issued complete data set.

5.1.5 Recommendation. - When provided as a completely re-issued data set, the differences from the previously issued complete data set should be clearly indicated.

5.1.6 Significant and major changes to the aeronautical information shall be distributed under the regulated system (AIRAC).

5.1.7 The information of a temporary nature and of short duration or when operationally significant permanent changes, or temporary changes of long duration are made at short notice, except for extensive text and/or graphics shall be originated and issued by NOTAM.

5.1.8 Recommendation.- When Digital NOTAM are provided, they should apply the same format, distribution channels and temporal concepts as the baseline data service.

AIC..

5.2 Aeronautical Information Regulation and Control (AIRAC)

Note: the AIRAC system synchronises the establishment, withdrawal or significant changes upon a series of common effective dates at intervals of 28 days, including 14 January 2010.

Note: the circumstances considered as having significant and major changes are identified in the PANS-AIM.

5.2.1 The information notified under the AIRAC system shall not be changed further for at least another 28 days after the effective date, unless the circumstance notified is of a temporary nature and would not persist for the full period.

5.2.2 When information has not been submitted by the AIRAC date, a NIL notification shall be originated and distributed not later than one cycle before the AIRAC effective date concerned.

5.2.3 Implementation dates other than AIRAC effective dates shall not be used for pre-planned operationally significant changes requiring cartographic work and/or for updating of navigation databases.

5.2.4 Information provided under the AIRAC system shall be distributed/made available by the AIS unit so as to reachrecipients at least 28 days in advance of the AIRAC effective date.

5.2.5 Recommendation.— Whenever major changes are planned and where advance notice is desirable and practicable, information should be distributed/made available by the AIS unit so as to reach recipients at least 56 days in advance of the AIRAC effective date.

Note: the circumstances considered as major changes are identified in the PANS-AIM.

5.2.6 When changes to aeronautical information are published / made available in accordance with AIRAC procedures, a “Trigger NOTAM” shall be originated giving a brief description of the contents.

Annex B – option 3 (specific requirements for each product/service are also included)

Chapter 5 - Aeronautical information updates

5.1 Aeronautical information mentioned in chapter 4 and the products and services defined in chapter 6 shall be amended or reissued as necessary to keep them up to date.

5.2 Aeronautical Information Regulation and Control (AIRAC)

5.2.1 Information concerning circumstances with high operational significance shall be distributed under the regulated system (AIRAC).

Note: the AIRAC system synchronises the establishment, withdrawal or significant changes upon a series of common effective dates at intervals of 28 days, including 14 January 2010.

Note: the circumstances considered as having high operational significance are identified in the PANS-AIM.

5.2.2 The information notified under the AIRAC system shall not be changed further for at least another 28 days after the effective date, unless the circumstance notified is of a temporary nature and would not persist for the full period.

5.2.3 When information has not been submitted by the AIRAC date, a NIL notification shall be originated and distributed not later than one cycle before the AIRAC effective date concerned.

5.2.4 Implementation dates other than AIRAC effective dates shall not be used for pre-planned operationally significant changes requiring cartographic work and/or for updating of navigation databases.

5.2.5 Information provided under the AIRAC system shall be distributed/made available by the AIS unit so as to reachrecipients at least 28 days in advance of the AIRAC effective date.

5.2.6 Recommendation.— Whenever major changes are planned and where advance notice is desirable and practicable, information should be distributed/made available by the AIS unit so as to reach recipients at least 56 days in advance of the AIRAC effective date.

Note: the circumstances considered as major changes are identified in the PANS-AIM.

5.3 Specifications for AIP updates

5.3.1 Permanent changes to the AIP shall be published as AIP Amendments.

5.3.1.1 Recourse to hand amendments or annotations shall be kept to the minimum.

5.3.2 Temporary changes of long duration (three months or longer) and information of short duration which contains extensive text and/or graphics shall be published as AIP Supplements.

Note.— The requirements for NOTAM apply when time constraints do not allow sufficient time for the distribution of an AIP Amendment or an AIP Supplement.

Note.— Guidance material on the use of AIP Supplements together with examples of such use is contained in the Aeronautical Information Services Manual (Doc 8126).

5.3.4 AIP Amendments and AIP Supplements that contain information concerning the circumstances mentioned in [5.2.1] shall be distributed/made available under the AIRAC system.

5.3.5 The AIP update interval shall be specified in the AIP, Part 1 — General (GEN).

Note.— Guidance material on the establishment of intervals between publication dates of AIP Amendments is contained in the Aeronautical Information Services Manual (Doc 8126).

5.3.6 When an AIP Amendment will not be published at the established interval or publication date, a NIL notification shall be originated and distributed by the monthly printed plain-language list of valid NOTAM required by 5.2.13.3.

5.3.7 When an error occurs in an AIP Supplement or when the period of validity of an AIP Supplement is changed, a new AIP Supplement shall be published as a replacement.

5.2.6 A checklist of valid AIP Supplements shall be issued at intervals of not more than one month. This information shall be issued through the medium of the monthly printed plain-language list of valid NOTAM required by 5.2.13.3.

5.4 Specifications for NOTAM

5.4.1 A NOTAM shall be originated and issued promptly whenever the information to be distributed is of a temporary nature and of short duration or when operationally significant permanent changes, or temporary changes of long duration are made at short notice, except for extensive text and/or graphics.

5.4.1 When an AIP Amendment or an AIP Supplement is published in accordance with AIRAC procedures, a “Trigger NOTAM” shall be originated giving a brief description of the contents.

5.5 Specifications for digital data sets

5.5.1 The update shall be in the form of a completely re-issued data set and/or a sub-set that includes just the differences from the previously issued complete data set.

5.5.1.1 Recommendation. - When provided as a completely re-issued data set, the differences from the previously issued complete data set should be clearly indicated.

5.5.2 Data set updates that contain information concerning the circumstances mentioned in [5.1.1] shall be distributed/made available under the AIRAC system.

5.5.3 Recommendation.- When Digital NOTAM are provided, they should apply the same format, distribution channels and temporal concepts as the baseline data service.

Note.— Detailed specification covering Digital NOTAM is contained in PANS-AIM