Versions Compared

Version Old Version 5 New Version 6
Changes made by

Andreea Perca (Deactivated)

Andreea Perca (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There are several situations that can trigger the need to issue several NOTAM to ensure that the information appears in the relevant en-route and airport Pre-Flight Information Bulletins (PIB). The Event has an explicit associationEvent to AirportHeliport as defined in ER-12.

  1. if the Event has an associationEvent to an AirportHeliport, publish a "navaid unserviceable" NOTAM for each airport that is affected, with the corresponding airport designator in item A.
  2. If more the one navaid is affected, a separate NOTAM shall be created for each NAV.TD. associated with the Event for which at least one of its NavaidEquipment also has a NEQ.TD associated with the same Event;

The rules for the “first NOTAM” and the NOTAM containing the FIR in Item A are indicated below, for any additional NOTAM with scope A, refer to “several NOTAM possible” section.

Note: A better solution would be that such navaid outages are translated into one NOTAM with the FIR in item A. Then, separate Events and separate NOTAM should be published for the affected Procedures, having the airport identifier in item A. This approach will be considered for the further development of this Specification, when the scenario for Procedures unavailability will be included.

...