Text NOTAM production rules

This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.1.1 data encoding of the Event. Therefore, AIXM specific terms are used, such as names of features and properties, types of TimeSlices, etc:

In general, the ICAO DOC 8126 and the OPADD rules shall be followed. These have not been copied in this document in order to avoid duplication with those documents. Only instructions that are specific to the AIXM encoding of this event are stated here.

Item A

The item A shall contain the AHP.BL.designator if AHP.BL.locationIndicatorICAO='YES'. Otherwise, the nationality letter(s) as defined in ICAO Doc 7910 followed by “XX” or “XXX”.

Q code

Insert here QMNLC


Insert the value ‘A’.

Lower limit / Upper limit

Use “000/999”

Geographical reference

Insert the coordinate of the ARP (AHP.BL.ARP.ElevatedPoint) of the airport, formatted as follows:

Items B, C and D

Items B and C shall be decoded following the common production rules.

If at least one APE.BL.availability.ApronAreaAvailability.timeInterval exists (i.e. the Event has an associated schedule), then all such Timesheet(s) shall be represented in item D according to the common NOTAM production rules for {{Item D, E - Schedules}}. Otherwise, item D shall be left empty.

Item E

The following pattern should be used as a base for generating the E field text from the AIXM data:



old: template = ["(1)" "AHP.BL.type (2)" (" (3a)" | "AHP.BL.ARP (3b)")] \n "Apron" "" "closed" "APE.BL.annotation (4)" "\n" \n
[ "due to" "APE.BL.availability.annotation (5)"]\n 
{"\n" "APE.BL.annotation(6)" "."} ["."].

new: template = ["(1)" "AHP.BL.type (2)" (" (3a)" | "AHP.BL.ARP (3b)")] \n "Apron (4)" "" "closed" "APE.BL.annotation (5)" "\n" \n
[ "due to" "APE.BL.availability.annotation (6)"]\n
{"\n" "APE.BL.annotation(7)" "."} ["."].




If AHP.BL.locationIndicatorICAO=YES, then ignore this branch.


Insert here the type of the airport decoded as follows


Text to be inserted in Item E

AD or AH





"Landing site"


a. If is not NIL, then insert it here. Otherwise

b.insert here the text "located at" followed by the AHP.BL.ARP.ElevatedPoint decoded according to the text NOTAM production rules for aixm:Point.

(4)For the potential applications/implementations - the word "APRON" may appear twice depending on the coded (e.g. APRON MILITARY APRON or APRON APRON A1). Caution shall be exercised for NOTAM production to avoid possible duplications.
(5)Insert here the APE.annotation note with propertyName="extent" and purpose="DESCRIPTION" translated into free text according to the decoding rules for annotations. 
(6)Insert here the ApronElement/ApronAreaAvailability.annotation with propertyName="operationalStatus" and purpose="REMARK"  translated into free text according to the decoding rules for annotations. 


Other annotations of APE.BL shall be translated into free text according to the decoding rules for annotations.

Items F & G

Leave empty.

Event Update

The eventual update of this type of event shall be encoded following the general rules for {{Event updates or cancellation}}, which provide instructions for all NOTAM fields, except for item E and the condition part of the Q code, in the case of a NOTAMC

If a NOTAMC is produced, then the 4th and 5th letters (the "condition") of the Q code shall be "AK", except for the situation of a “new NOTAM to follow, in which case “XX”shall be used..

template_cancel = ["(1)" "AHP.BL.type (2)" (" (3a)" | "AHP.BL.ARP (3b)")  ] \n "Apron" "" "resumed normal operations." ["New NOTAM to follow.(7)"].

The following pattern should be used for automatically generating the E field text from the AIXM data




If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to specify "New NOTAM to follow" and this text shall be appended at the end of item E of the NOTAM C.

Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX”