Page tree
Skip to end of metadata
Go to start of metadata

Text NOTAM production rules

This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.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 NAV.BL. indicates that the corresponding data item must be taken from the Navaid BASELINE, which is valid at the start time of the Event;
  • the abbreviation NAV.TD. indicates that the corresponding data item must be taken from the Navaid TEMPDELTA;
  • the abbreviation NEQ.BL. indicates that the corresponding data item must be taken from the NavaidEquipment BASELINE, which is valid at the start time of the Event;
  • the abbreviation NEQ.TD. indicates that the corresponding data item must be taken from the NavaidEquipment TEMPDELTA;
    • Important note: According to encoding rule ER-11, the TEMPDELTA might also include NavaidOperationalStatus elements that have been copied from the BASELINE data for compliance with the AIXM Temporality rules. The current practice is to not include such static information in the NOTAM text. Therefore, all NavaidOperationalStatus that have an associated annotation with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation" shall be excepted from the text NOTAM generation algorithm!

Several NOTAMs possible

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 can have an explicit associationEvent to AirportHeliport as defined in ER-12. If the Event has an associationEvent to an AirportHeliport, a "navaid unserviceable" NOTAM with scope AE and subsequent NOTAMs for each airport that is affected needs to be published, with the corresponding airport designator in item A.

The rules for the “first NOTAM” containing the FIR in Item A are indicated below. For any additional NOTAM, 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.

Item A

The item A shall be generated according to the geographical location of the Airspace and shall contain the Airspace.designator of the predefined FIR(s) for which a NOTAM has to be issued, except if there is an association Event to an AirportHeliport case in the AirportHeliport.designator shall be used. 

Item Q

Apply the common NOTAM production rules for item Q, complemented by the following specific rules for this particular scenario:

Q code

The mapping provided in the tables below shall be used.

NAV.BL.type

Corresponding Q codes (2nd and 3rd letters)

ILS or ILS_DME

QIC - if both the Localizer and the Glidepath components have a (E)TD associated with the Event

QID - if only its DME component has (E)TD associated with the Event

QIG - if only its Glidepath component has (E)TD associated with the Event

QIL - if only its Localizer component has (E)TD associated with the Event

QII - if only its MKR component has (E)TD associated with the Event and its (N)BL.NavaidComponent.markerPosition=INNER

QIM - if only its MKR component has (E)TD associated with the Event and its (N)BL.NavaidComponent.markerPosition=MIDDLE

QIO - if only its MKR component has (E)TD associated with the Event and its (N)BL.NavaidComponent.markerPosition=OUTER

QIY - if only its NDB component has (E)TD associated with the Event and its (N)BL.NavaidComponent.markerPosition=MIDDLE

QIX - if only its NDB component has (E)TD associated with the Event and its (N)BL.NavaidComponent.markerPosition=OUTER

MLS or MLS_DME

QIW

NDB or NDB_MKR

QNB - if NDB component (E)BL.class=ENR

QNL - if NDB component (E)BL.class=L

LOC or LOC_DME

QIN

DME

QND

MKR

QNF

VOR_DME

QNM

TACAN

QNN

VORTAC

QNT

VOR

QNV

DF

QNX

NDB_DME, TLS or OTHER

QXX

and

NAV.TD.operationalStatus

Corresponding Q codes (4th and 5th letters)

UNSERVICEABLE

AS

ONTEST

CT

INTERRUPT

LS

PARTIAL

AS

FALSE_INDICATION

XX

DISPLACED

CM

IN_CONSTRUCTION

XX

OTHER

XX   

Scope

Insert here AE. 

Items B, C and D

Items B and C shall be decoded from the values of NAV.TD.validTime following the common production rules.

If at least one NAV.TD.NavaidOperationalStatus.timeInterval exists (the Event has an associated schedule), then the associated Timesheets(s) shall be decoded 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 for automatically generating the E field text from the AIXM data: 

EBNF Code
template = ["NAV.BL.name(1)"] "NAV.BL.type(2)" ["NEQ.BL.type(3)"] ["NEQ.TD.availability.signalType(4)"] [( "NAV.BL.designator(5)" | "RWY-" "NAV.BL.runwayDirection(5)")] \n ["NEQ.BL.frequency(6)"] ["NEQ.BL.channel(7)"] "NEQ.TD.operational status(8)" "." \n
["\n" "due to" "NEQ.TD.NavaidOperationalStatus.annotation(9)" "."] \n
{"\n" "NEQ.TD.NavaidOperationalStatus.annotation(10)" "."}.

Reference

Rule

(1)

The name of the Navaid shall be included if present in the NAV.BL data

(2)

Insert the type from the Navaid baseline, according to the following decoding rule:

NAV.BL.type

Text to be inserted in item E

VOR

"VOR"

DME

"DME"

NDB

If (E)BL.class=N then use the word "LOCATOR", otherwise use the word "NDB"

TACAN

"TACAN"

MKR

If used as NavaidComponent of an ILS or ILS_DME Navaid, then insert (N)BL.markerPosition first followed by "MKR", otherwise insert just the word "MKR"

ILS

"ILS"

ILS_DME

"ILS"

MLS

"MLS"

MLS_DME

"MLS"

VORTAC

"VORTAC"

VOR_DME

"VOR/DME"

DNB_DME

"NDB/DME"

TLS

"Transponder Landing System"

LOC

"LOC"

LOC_DME

"LOC/DME"

NDB_MKR

"NDB/MKR"

DF

"DF service"

SDF

"Simplified Directional Facility eqpt"

OTHER

None

(3)

If the Navaid Baseline has several Navaid components and only one of its primary component NavaidEquipment has a NEQ.TD associated with the Event, then insert the type of that equipment, according to the following decoding rule:

NEQ.BL

Text to be inserted in Item E

DME

"DME part"

VOR

"VOR part"

TACAN

"TACAN part"

Glidepath

"GP part"

Localizer

"LOC part"

Azimuth

"azm signal"

Elevation

"elev signal"

SDF

"Simplified Directional Facility eqpt"

DirectionFinder

"DF"

NDB

If (E)BL.class=N then use the word " LOCATOR", otherwise use the word "NDB"

MarkerBeacon

If used as NavaidComponent of an ILS or ILS_DME Navaid, then insert (N)BL.NavaidComponent.markerPosition first followed by "MKR", otherwise insert just the word "MKR"

(4)

If NAV.BL is TACAN or VORTAC and its (TACAN)TD.availability.signalType is specified, then insert its value here.

(5)

The following rules apply:

  • If NAV.BL.type has the value ILS, ILS_DME, LOC, LOC_DME, MLS or MLS_DME, then insert the RunwayDirection.BL.designator of the associated NAV.BL.runwayDirection, if available;
  • Otherwise, insert the NAV.BL.designator, if available.

(6)

Apply the following rules:

NAV.BL.type

Use the following value

VOR, VOR_DME, VORTAC

(VOR)BL.frequency followed by its uom value

NDB, NDB_MKR, NDB_DME

(NDB)BL.frequency followed by its uom value

SDF

(SDF)BL.frequency followed by its uom value

any other

leave empty

(7)

Apply the following rules:

NAV.BL.type

Use the following value

VOR_DME, DME, NDB_DME

(DME)BL.channel

TACAN, VORTAC

(TACAN)BL.channel

any other

leave empty

(8)

Insert the NEQ.TD.operationalStatus decoded as follows:

NEQ.BL.availability/operationalStatus

Text to be inserted in Item E

UNSERVICEABLE

"unserviceable"

ONTEST

"On test, do not use. False indication possible."

INTERRUPT

"subject to interruption"

PARTIAL

"unserviceable" (note that this should only occur for TACAN components)

FALSE_INDICATION

"do not use, false indication"

DISPLACED

"displaced"

IN_CONSTRUCTION

"in construction, do not use"

OTHER

"operational status is affected"

(9)

If specified, insert here only the NEQ.TD.NavaidOperationalStatus.annotation that has propertyName="operationalStatus" and purpose="REMARK", translated into free text according to the following encoding rules.

(10)

Annotations shall be translated into free text according to the rules for annotations decoding.

Note: The objective is to full automatic 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 NOTAM C

If a NOTAM C 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.

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

EBNF Code
template_cancel = ["NAV.BL.name(1)"] "NAV.BL.type(2)" ["NEQ.BL.type(3)"]\n
[( "NAV.BL.designator(5)" | "RWY-" "NAV.BL.runwayDirection(5)")] \n
["NEQ.BL.frequency(6)"] ["NAV.BL.channel(7)"] "resumed normal operations""."\n
["New NOTAM to follow(11)"].

Reference

Rule

(11)

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”

  • No labels