...
Note that if an ad-hoc ATS area is located in the vicinity of one or more airports or affects more than one FIR, there are special provision in the OPADD (Ed. 4.0, section 2.3.9.2) with regard to the NOTAM that need to be issued in order to ensure that the NOTAM appear correctly in the relevant en-route and airport Pre-Flight Information Bulletins (PIB). From a Digital NOTAM point of view, this requires that an Event can have several NOTAM associated, which is supported by the AIXM Event schema. In order to facilitate the work of the operator, the Digital NOTAM data provider interface should include the following functionality:
...
The Event has an explicit associationEvent to AirportHeliport as defined in ER-09.
- if the Event has an associationEvent to an Airspace of type=FIR generate a NOTAM with scope W. If more of such Airspace feature(s) are identified, their identificator shall be listed in item A.
- if the Event has an associationEvent to an Airspace of type CTR or TMA, identify the AirportHeliport feature(s) that are located in those CTR/TMA and that also have locationIndicatorICAO="YES"; according to the OPADD rules, propose that a single NOTAM with scope AW and/or additional NOTAM with scope A are issued for these airports;
- if the
...
- Event has an associationEvent to an AirportHeliport that have their ARP
...
- located within 5 NM (
...
- configurable parameter)
...
- and have locationIndicatorICAO="YES", propose that a single NOTAM with scope AW and/or additional NOTAM with scope A are issued for these
...
- airports
...
The rules for the “first NOTAM” and the NOTAM containing one or more FIR in Item A are indicated below, for any additional NOTAM with scope A, refer to “several NOTAM possible” section.
...