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 AST.BL. indicates that the corresponding data item must be taken from the AircraftStand BASELINE;
  • 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;
  • the abbreviation AST.TD. indicates that the corresponding data item must be taken from the AircraftStand TEMPDELTA that was created for the Event.


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

Note: In this table, "any" means "any value or no value (NIL)".

AST.TD.availability.ApronAreaAvailability.


timeIntervalusage.ApronAreaUsage

type

operationpriorPermission../FlightCharacteristics../AircraftCharacteristicsCorresponding Q Code
any'CONDITIONAL'anynot NILanyanyQMPAP
any'PERMIT'anyNILanyanyQMPAR
any'FORBID'anyanyanyweight not NILQMPLH
any other combinationQMXLT

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 AST.TD.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 for automatically 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 "Acft stand" "AST.BL.designator" ["(4)" ("and"|",")]{"AST.BL.designator" ["(4)" ("and"|",")]} \n 
"AST.TD.usage.type(5)" (["AST.TD.usage.flight(6)"] ["AST.TD.usage.aircraft(7)"] ["AST.TD.usage.operation(8)"] ["conditions(9)"]) { "(10)" "," (["AST.TD.usage.flight(6)"] ["AST.TD.usage.aircraft(7)"] ["AST.TD.usage.operation(8)"] ["conditions(9)"])} \n
 
template_bottom =
["\n" "due to" "AST.TD.availability.annotation(11)"] "\n" \n
{"." "AST.TD.availability.annotation(12)" "\n"} ["."].

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 more than one AircraftStand has a TEMPDELTA associated with the Event, then insert the designator of each additional AircraftStand designator preceded by ",". The word "Acft stand" need not be repeated. Insert "and" before the last entry.

(5)

conditional for

closed, except for

prohibited for

additionally allowed for

Insert here AST.TD.availability.ApronAreaAvailability.usage.ApronAreaUsage as follows:

type

Text to be inserted in item E

"CONDITIONAL""available for"
"RESERV""closed, except for"
"PERMIT""now available for"
"FORBID""prohibited for"

(6)

flight

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 in Item E

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 in Item E

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 in Item E

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.

(7)

aircraft

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.

(8)operation

Decode here the AST.TD.availability.usage.operation as follows:

AST.TD.usage.operation*

Text to be inserted in Item E

AIRSHOW

"for acft participating in air display”

ALL**

"for all operations"**

CROSSING

"for crossing"

LANDING

"for landing"

TAKEOFF

"for tkof

TAXIING

"for taxiing"

TOUCHGO

"for tgl"

TRAIN_APPROACH

"for practice low approaches"

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

**Note: if all operations are affected, then either provide the text as described above or do not provide the text at all.

(9)

PPR time

PPR details

If AST.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 " "AST.TD.usage.priorPermission(9.1)" ["AST.TD.usage.annotation(9.2)"].

Reference

Rule

(9.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}}

(9.2)

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

(10)


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

(11)reasonIf there exists a AST.TD.availability.annotation having propertyName='operationalStatus' and purpose='REMARK', then translate it into free text according to the decoding rules for annotations.

(12)

note

Annotations of AST.TD.ApronAreaAvailability shall be translated into free text according to the decoding rules for annotations.

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 [archived] Event update 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 = "AHP.BL.type (1)" ["(2)"  ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")] "Acft stand" "AST.BL.name" ["(4)" ("and"|",")]{"AST.BL.name" ["(4)" ("and"|",")]} ("resumed normal operations." | " : New NOTAM to follow.(13)").

Reference

Rule

(13)

If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to choose the "New NOTAM to follow" branch.  This branch cannot be selected automatically because this information is only known by the operator.

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

  • No labels