[RDD.CHG] Runway declared distances - change (NOTAM)

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:

the abbreviation RCP.TD. indicates that the corresponding data item must be taken from the RunwayCentrelinePoint TEMPDELTA that has been created for the Event;
the abbreviation RCP.TD.RDD. indicates that the corresponding data item must be taken from the associatedDeclaredDistance.RunwayDeclaredDistance of the RunwayCentrelinePoint TEMPDELTA that has been created for the Event;
the abbreviation RDN.BL. indicates that the corresponding data item must be taken from the RunwayDirection BASELINE associated with the RunwayCentrelinePoint;
the abbreviation RWY.BL. indicates that the corresponding data item must be taken from the Runway BASELINE associated with the RunwayDirection concerned;
the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Runway that is associated with the RunwayDirection concerned.

Note: It is assumed that all RunwayCentrelinePoint associated with the Event are also associated with the same Runway (through the RunwayDirection→ Runway association chain).

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 be generated according to the general production rules for item A using the Event.concernedAirportHeliport.

Q code

The following mapping shall be used:

Declared Distance	Corresponding Q code
Declared Distance Change	QMDCH

Scope

Insert the value ‘A’.

Lower limit / Upper limit

Use “000/999”

Geographical reference

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

the set of coordinates comprises 11 characters rounded up or down to the nearest minute; i.e. Latitude (N/S) in 5 characters; Longitude (E/W) in 6 characters;
the radius value is “005”.

Items B, C and D

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

item D shall be left empty. Note: If the declared distances are associated with a schedule, this information will be provided in item E, next to the group of declared distances concerned. This is a different approach from the current NOTAM practice where the NOTAM user is left to integrate the information that remains valid from the baseline (AIP) data with the values provided by NOTAM. In this scenario, the NOTAM generated automatically from the AIXM coded data includes all declared distances, not only the changed values.

Item E

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

EBNF Code

template = template = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")  ] "Declared distances changed as follows:" "\n" \n
"(6)" ["unpaved(4)"] "RWY" "RDN.BL.designator" ("(5)" "single declared distances group" | "multiple declared distances groups") "." {"(7)" "(6)" ["unpaved(4)"] "RWY" "RDN.BL.designator" ("(5)" "single declared distances group" | "multiple declared distances groups") "."} ["\n" "RCP.TD.RDD.annotation(8)" "."].

Reference

Data item (from coding scenario)

Rule

(1)

If AHP.BL.locationIndicatorICAO is not null, then ignore this branch.

(2)

Insert here the type of the airport decoded as follows

AHP.BL.type	Text to be inserted in Item E
AD or AH	"AD"
HP	"Heliport"
LS or OTHER...	"Landing site"

(3)

a. AHP.BL.name 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)(7)

If more than one RCP.TD is associated with the Event, then group them ascending by associated RDN.BL.designator value. If more than one RCP.TD group is detected, then use the branch (6) for each RCP.TD group and repeat (7) until all groups are processed.

(5)

Insert the word “unpaved” if RWY.BL.SurfaceCharacteristics.composition has one of the values CLAY, CORAL, EARTH, GRASS, GRAVEL, ICE, LATERITE, MACADAM, SAND, SNOW, WATER, OTHER. Otherwise do not insert anything.

(6)

If in the RCP.TD group that is being processed there is at maximum one RCP.TD.RDD descendant that has the same type value, then use the "single declared distances group", otherwise use the "multiple declared distances group" branch.

"single declared distances group":

"multiple declared distances group":

RCP.BL.role (in the order 'THR', 'DISP_THR', any other value)
(descending) RCP.TD.RDD.declaredValue.RunwayDeclaredDistanceValue.distance

()

Insert here the declared distance type decoded as follows in the order below. Only the RCP.TD.RunwayDeclaredDistance and RCP[n].BL.RunwayDeclaredDistance which do not have an associated Note with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation" shall be included.

If AHP.BL.type=AD, LS or OTHER

RCP.TD.DeclaredDistance.type	Text to be inserted in Item E
TORA	"TORA"
TODA	"TODA"
ASDA	"ASDA"
LDA	“LDA”

If AD.BLtype=HP

RCP.TD.DeclaredDistance.type	Text to be inserted in Item E
TODAH	"TODAH"
RTOAH	"RTODAH"
LDAH	"LDAH"

()

Insert here the declared distance value followed by its unit of measurement decoded according to the {{text NOTAM production rules for distances}}

()

Annotations shall be translated into free text according to the rule for {{decoding annotations}}.

Note: The objective is to fully automate generation, without human intervention. However, the implementers of the specification might consider reducing the cost of a fully automated generation by allowing the operator to fine-tune the text in order to improve its readability (with the inherent risk for human error when re-typing is allowed).

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" unless there is a new NOTAM to follow, in which case the Q code shall be “XX” and the following pattern should be used for automatically generating the E field text from the AIXM data:

EBNF Code

template_cancel = ["(1)" "AHP.BLtype (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")  ] "RWY" "RDN.BL.designator" ["."] \n
["resumed normal operations"]  ["New NOTAM to follow (9)"] ".".

Reference

Rule

(9)

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”