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.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 TWY.BL. indicates that the corresponding data item must be taken from the Taxiway BASELINE;
  • the abbreviation TWY.TD. indicates that the corresponding data item must be taken from the Taxiway TEMPDELTA that was created for the Event in case of complete taxiway closure;
  • the abbreviation TWE.TD. indicates that the corresponding data item must be taken from the TaxiwayElement TEMPDELTA that was created for the Event in case of taxiway portion closure;
  • the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Taxiway that is associated with the TaxiwayElement concerned;
    • NoteAccording to encoding rules for TWY.CLS, the TEMPDELTA(s) might also include ManoeuvringAreaAvailability 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 ManoeuvringAreaAvailability 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!

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.locationIndicatorICAO if not nil. Otherwise, the nationality letter(s) as defined in ICAO Doc 7910 followed by “XX” or “XXX”.

Q code

The following mapping shall be used:

Closure status

Corresponding Q codes

CLOSED, if Taxiway.type other than FASTEXIT and there are no associated AirportHeliportUsage.type PERMIT or CONDITIONAL

QMXLC

CLOSED, Taxiway type other than FASTEXIT but there also exist associated AirportHeliportUsage.type PERMIT or CONDITIONAL

QMXLT

CLOSED, Taxiway type=FASTEXIT and there are no associated AirportHeliportUsage.type PERMIT or CONDITIONAL

QMYLC

CLOSED, Taxiway type=FASTEXIT but there also exist associated AirportHeliportUsage.type PERMIT or CONDITIONAL

QMYLT

Scope

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:

  • 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.

If at least one TWY.TD.availability.ManouevringAreaAvailability.timeInterval or TWE.TD.availability.ManouevringAreaAvailability.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:


EBNF Code
template = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")] \n ("Rapid exit TWY(4)" | "TWY") "TWY.BL.designator(5)" {"closed_taxiway_portion(6)"}["and(7)"| ","] {("Rapid exit TWY(4)" | "TWY") "TWY.BL.designator(5)" {"closed_taxiway_portion(6)"} ["and(7)"| ","]}
\n "closed" [ "due to" "TWY/TWE.TD.availability.annotation (8)"]\n 
["(9)" "\n" "except" ["TWY/TWE.TD.usage.PPR(10)"] ["TWY/TWE.TD.usage.flight(11)"] ["TWY/TWE.TD.usage.aircraft(12)"]["flights"] {"(13)" "," ["TWY/TWE.TD.usage.PPR(10)"] ["TWY/TWE.TD.usage.flight(11)"] ["TWY/TWE.TD.usage.aircraft(12)"]["flights"]} ] \n
{"\n" "TWY/TWE.TD.availability.annotation(14)" "."} ["."].

Reference

Rule

(1)

If AHP.BL.locationIndicatorICAO=YES, 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. If 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)

if TWY.BLtype = FASTEXIT insert the words “Rapid exit". Otherwise insert "TWY".

(5)

If more than one Taxiway and/or TaxiwayElement has a TEMPDELTA associated with the Event, then insert the designator of each additional Taxiway, designator preceded by ",". Insert "and" before the last entry. 

(6)

Insert here the TWY.annotation and/or TWE.annotation note with purpose="OTHER:DESCRIPTION" stored in the BASELINE data (e.g. “between TWY A and TWY B”).

If taxiway elements are used, the automatic generation of an easy human-readeable NOTAM text is practically impossible using just the AIXM encoding. Two cases can be identified for describing the closed taxiway portion:

Case 1: use long text from descriptions, as available in the TWE.annotation. 

Example: Following the example of Fig.1 from coding rules, the text would look as follows: "between TWY B and TWY C, intersection TWY A and TWY C, between TWY C and TWY D” 

Case 2: allow the operator to manually write the text part. 

Since the operator is allowed to modify the item E text manually, the choice to simplify the text can be made. The result of manual editing could result in something as follows: "between TWY B and TWY D, including intersections between".

(7) Insert "and" before the last taxiway or taxiway portion affected by the closure (e.g. "TWY A, TWY B and TWY C") 

(8)

If there exists a TWY.TD.availability.annotation or TWE.TD.availability.annotation having propertyName="operationalStatus" and purpose="REMARK", then translate it into free text according to the decoding rules for annotations.

(9)

If there exist one or more TD.availability.usage then decode them following this branch, in the following order of priorities:

  • TD.availability.usage that have operation="ALL"
  • TD.availability.usage that have type="PERMIT"
  • ... other situations ...
  • TD.availability.usage that have priorPermission which is not NIL shall be decoded last.
(10)

If TD.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:

EBNF Code
template_PPR = "PPR " "TWY/TWE.TD.usage.priorPermission(10.1)" ["TWY/TWE.TD.usage.annotation(10.2)"].

Reference

Rule

(10.1)

Insert here the value of the priorPermission attribute followed by its unit of measurement decoded according to the {{text NOTAM production rules for duration}}

(10.2)

Decode here the annotation with propertyName="priorPermission" and purpose="REMARK", according to the decoding rules for annotations.

(11)

Decode here each FlightCharacteristics property that was specified, as detailed below. If more than one FlightCharacteristics property was used, insert blanks between consecutive properties.

FlightCharacteristics.type*

Text to be inserted in Item E

OAT

"Operational Air Traffic"

GAT

"General Air Traffic"

ALL

"Operational Air Traffic/General Air Traffic"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

*Note: type is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


FlightCharacteristics.rule

Text to be inserted in Item E

IFR

"IFR"

VFR

"VFR"

ALL*

"IFR/VFR"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


FlightCharacteristics.status

Text to be inserted

HEAD

"Head of State"

STATE

"State acft"

HUM

"HUM"

HOSP

"HOSP"

SAR

"SAR”

EMERGENCY

"EMERG"

ALL

"State acft/HUM/HOSP/SAR/EMERG"

OTHER:MEDEVAC

“MEDEVAC”

OTHER:FIRE_FIGHTING

“fire fighting”

OTHER:MY_TEXT

"my text" (replace "_" with blanks and convert to lowercase)

FlightCharacteristics.military

Text to be inserted in Item E

MIL

"MIL acft"

CIVIL

"civil acft"

ALL*

"civil/MIL acft"

OTHER:MY_TEXT*

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


FlightCharacteristics.origin

Text to be inserted

NTL

"domestic"

INTL

"intl"

HOME_BASED

"home based"

ALL*

"domestic/intl"

OTHER:MY_TEXT*

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


FlightCharacteristics.purpose

Text to be inserted

SCHEDULED

"scheduled"

NON_SCHEDULED

"not scheduled"

PRIVATE*

"private"

AIR_TRAINING

"training"

AIR_WORK*

"aerial work"

PARTICIPANT

"participating acft"

ALL*

"scheduled/not scheduled/private/training/aerial work/participating acft"

OTHER:MY_TEXT*

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.

(12)

Decode here each AircraftCharacteristics property that was specified, as detailed below. If more than one AircraftCharacteristics property was used, insert blanks between consecutive properties.

AircraftCharacteristics.type

Text to be inserted in Item E

LANDPLANE

"landplanes"

SEAPLANE*

"seaplanes"

AMPHIBIAN

"amphibians"

HELICOPTER

"hel"

GYROCOPTER

"gyrocopters"

TILT_WING

"tilt wing acft"

STOL

"short take-off and landing acft"

GLIDER*

"gliders"

HANGGLIDER*

"hang-gliders"

PARAGLIDER*

"paragliders"

ULTRA_LIGHT*

"ultra lights"

BALLOON*

"balloons"

UAV*

"unmanned acft”

ALL*

"all acft types"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


AircraftCharacteristics.engine

Text to be inserted in Item E

JET

"jet acft"

PISTON

"piston acft"

TURBOPROP

"turboprop acft"

ELECTRIC**

“electric engine acft”

ALL

"all engine types"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

**Note: new in AIXM 5.1.1.


AircraftCharacteristics.wingSpan - insert the value followed by the value of the uom attribute. Prefix with the value of AircraftCharacteristics.wingSpanInterpretation, decoded as indicated in the following table:

AircraftCharacteristics.wingSpanInterpretation

Text to be inserted in Item E

ABOVE

"acft with wingspan more than"

AT_OR_ABOVE

"acft with wingspan equal to or more than"

AT_OR_BELOW

“acft with wingspan equal to or less than"

BELOW

"acft with wingspan less than"

OTHER:MY_TEXT*

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


AircraftCharacteristics.weight - insert the value followed by the value of the uom attribute. Prefix with the value of AircraftCharacteristics.weightInterpretation, decoded as indicated in the following table:

AircraftCharacteristics.weightInterpretation

Text to be inserted in Item E

ABOVE

"acft mass heavier than"

AT_OR_ABOVE

"acft mass equal to or heavier than"

AT_OR_BELOW

"acft mass equal to or lighter than"

BELOW

"acft mass lighter than"

OTHER:MY_TEXT*

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.

(13)

If TD.usage.selection.logicalOperator=OR (there are more than one flight/aircraft combinations that are excepted), then select and decode each FlightCharacteristics/AircraftCharacteristics consecutively.

(14)

Annotations of TD.ManoeuvringAreaAvailability 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.

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

EBNF Code
template_cancel = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")  ] "\n" \n ("Rapid exit TWY(4)" | "TWY") "TWY.BL.name" {("," | "and(5)") ("Rapid exit TWY(4)" | "TWY") "TWY.BL.name"} "resumed normal operations." ["New NOTAM to follow.(15)"].

Reference

Rule

(15)

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