...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Item A
The item A shall be generated according to the general production rules for item A using the Event.concernedAirportHeliport,
Item Q
Apply the common NOTAM production rules for item Q, complemented by the following specific rules for this particular scenario:
Q code
The following mapping shall be used:
...
If RWY.BL.type = RWY:
...
RDN.TD.availability.ManoeuvringAreaAvailability.usage
...
Corresponding Q codes
...
none specified
...
QMRLC
...
a unique one, having AirportHeliportUsage.type=”PERMIT” and a descendant flight.FlightCharacteristic.military=”MIL”
...
QMRAM
...
at least one AirportHeliportUsage.type=”CONDITIONAL”
...
QMRAP
...
any other combination
...
QMRLT
If RWY.BL.type = FATO:
...
RDN.TD.availability.ManoeuvringAreaAvailability.usage
...
Corresponding Q codes
...
none specified
...
QFPLC
...
a unique one, having AirportHeliportUsage.type=”PERMIT” and a descendant flight.FlightCharacteristic.military=”MIL”
...
QFPAM
...
at least one AirportHeliportUsage.type=”CONDITIONAL”
...
QFPAP
...
any other combination
...
QFPLT
Scope
Insert the value ‘A’.
Lower limit / Upper limit
Use “000/999”
Geographical reference
...
Note: In this table, "any" means "any value or no value (NIL)".
RDN.TD.availability.ManoeuvringAreaAvailability. | Corresponding Q code | ||||||
|---|---|---|---|---|---|---|---|
| timeInterval | usage.ManoeuvringAreaUsage | RWY.BL.type | |||||
type | operation | priorPermission | ../FlightCharacteristics | ../AircraftCharacteristics | 'RWY' | 'FATO' | |
| not NIL | 'PERMIT' | 'ALL' | NIL | NIL | NIL | QMRAH | QFPAH |
| any | 'RESERVE' | any | any | only military='MIL' | any | QMRAM | QFPAM |
| any | 'CONDITIONAL' | any | not NIL | any | any | QMRAP | QFPAP |
| any | 'PERMIT' | any | NIL | any | any | QMRAR | QFPAR |
| any | 'RESERVE' | any | any | only origin='HOME_BASED' | any | QMRLB | QFPLB |
| any | 'FORBID' | any | any | any | weight not NIL | QMRLH | QFPLT |
| any | 'FORBID' | any | any | rule = 'IFR' | any | QMRLI | QFPLI |
| any | 'CONDITIONAL' | any | any | any | wingSpan not NIL | QMRLL | N/A |
| any | 'FORBID' | any | any | rule = 'VFR' | any | QMRLV | QFPLV |
| any other combination | QMRLT | QFPLT | |||||
Scope
Insert the value ‘A’.
Lower limit / Upper limit
Use “000/999”
Geographical reference
Insert the coordinate of the ARP (aerodrome reference point) of the airport (AHP.BL.ARP.ElevatedPoint), 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 RDN.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 for automatically generating the E field text from the AIXM data:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
template = ["(1)" "AHP.BL.type(2)" ("AHP.BL.name(3a)" | "AHP.BL.ARP(3b)") ] "\n" \n
["unpaved(4)"] "RWY.BL.type(5)" "RDN.BL.designator(6) |
...
" "RDN.TD. |
...
usage. |
...
type(7)" |
...
\n (["RDN.TD.usage.flight(8)"] |
...
["RDN.TD.usage.aircraft(9)"] "RDN.TD.usage.operation( |
...
10)" ["conditions( |
...
11)"] |
...
) { "(12)" "," (["RDN.TD.usage.flight(8)"] ["RDN.TD.usage.aircraft(9)"] "RDN.TD.usage.operation( |
...
10)" ["conditions( |
...
11)"] |
...
)} |
...
\n |
...
template_bottom = ["\n |
...
" |
...
|
...
" |
...
Reference
...
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)
...
If AHP.BL.name is not NIL, then insert it here. Otherwise:
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)
...
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.
...
due to" "RDN.TD.availability.annotation(13)" "\n"] \n
{"." "RDN.TD.availability.annotation(14)" "\n"} ["."]. |
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 |
...
|
...
|
...
|
...
|
...
| |
( |
...
3) |
...
If more than one RunwayDirection has a TEMPDELTA associated with the Event, then insert the designator of each additional RunwayDirection, preceded by "/", starting with the one with the lower designator number. In general, a runway has two landing directions but there may exist very rare situations with 3-4 landing directions.
...
(7)
...
If there exists a RDN.TD.availability.annotation having propertyName="operationalStatus" and purpose="REMARK", then translate it into free text according to the decoding rules for annotations.
...
(8)
...
If there exist one or more RDN.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.
...
(9)
Decode here the TD.availability.usage.operation as follows:
...
TD.usage.operation
...
Text to be inserted in Item E
...
LANDING
...
"for landing"
...
TAKEOFF
...
"for tkof”
...
TOUCHGO
...
"for tgl"
...
TRAIN_APPROACH
...
"for practice low approaches"
...
TAXIING
...
"for taxiing"
...
CROSSING
...
"for crossing"
...
AIRSHOW
...
"for acft participating in air display”
...
ALL
...
"for"
...
(10)
If the RDN.TD.availability.usage.ManoeuvringAreaUsage includes values for priorPermission or selection, then decode them here as follows:
| Code Block | ||||
|---|---|---|---|---|
| ||||
template_condition = ["RDN.TD.usage.priorPermission(11)"] ["RDN.TD.usage.flight(12)"] ["RDN.TD.usage.aircraft(13)"]
{"(14)" "," ["RDN.TD.usage.priorPermission(11)"] ["RDN.TD.usage.flight(12)"] ["RDN.TD.usage.aircraft(13)"]}. |
...
(11)
If RDN.TD.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:
| Code Block | ||||
|---|---|---|---|---|
| ||||
template_ppr = "PPR " "RDN.TD.usage.priorPermission(11.1)" ["RDN.TD.usage.annotation(11.2)"]. |
...
Reference
...
Rule
...
(11.1)
...
(11.2)
...
Decode here the annotation with propertyName="priorPermission" and purpose="REMARK", according to the decoding rules for annotations.
...
(12)
Decode here each FlightCharacteristics property that was specified, as detailed below. If more than one FlightCharacteristics property was used, insert blanks between consecutive properties.
...
| airport name |
| |||||||||||||||||||||||||||||||||||||||||||||
(4) | runway surface composition | 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. | ||||||||||||||||||||||||||||||||||||||||||||
(5) | runway | Insert here the type of the Runway decoded as follows
| ||||||||||||||||||||||||||||||||||||||||||||
(6) | runway direction | If more than one RunwayDirection has a TEMPDELTA associated with the Event, then insert the designator of each additional RunwayDirection, preceded by "/", starting with the one with the lower designator number. In general, a runway has two landing directions but there may exist very rare situations with 3-4 landing directions. | ||||||||||||||||||||||||||||||||||||||||||||
(7) | conditional for closed, except for prohibited for additionally allowed for | Insert here RDN.TD.availability.ManoeuvringAreaAvailability.usage.ManoeuvringAreaUsage as follows:
| ||||||||||||||||||||||||||||||||||||||||||||
| (8) | 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.
*Note: type is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
|
...
|
...
|
...
|
...
|
...
|
...
|
...
*Note: |
...
value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
EMERGENCY
...
|
...
SAR
...
"SAR”
|
...
OTHER:MEDEVAC
...
“MEDEVAC”
...
OTHER:FIRE_FIGHTING
...
“fire fighting”
...
OTHER:MY_TEXT
...
|
...
OTHER:MY_TEXT*
...
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake. | ||||
(9) | 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.
|
...
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"
*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*
...
(13)
Decode here each AircraftCharacteristics property that was specified, as detailed below. If more than one AircraftCharacteristics property was used, insert blanks between consecutive properties.
...
|
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
...
OTHER:MY_TEXT
...
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:
|
...
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"
*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:
*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:
...
. | ||||
(10) | operation | Decode here the RDN.TD.availability.usage.operation as follows:
|
...
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
...
|
...
*Note: |
...
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.
...
(14)
...
If there exists RDN.TD.usage.selection.logicalOperator=OR (there are more than one flight/aircraft combinations that are excepted), then select and decode each FlightCharacteristics/AircraftCharacteristics consecutively.
...
if all operations are affected, then either provide the text as described above or do not provide the text at all. | |||||||||||||||
(11) | PPR time PPR details | If RDN.TD.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:
| |||||||||||||
(12) | If more than one RDN.TD.availability.ManoeuvringAreaAvailability.ManoeuvringAreaUsage.type element is present, then select and decode the additional ManoeuvringAreaUsage branch consecutively. | ||||||||||||||
| (13) | reason | If there exists a RDN.TD.ManoeuvringAreaAvailability.annotation with propertyName="operationalStatus" and purpose='REMARK' (the reason for limitation, according to the coding rules), then translate it into free text according to the decoding rules for annotations. | |||||||||||||
(14) | note | Annotations of RDN.TD.ManoeuvringAreaAvailability 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
...
...
...
, 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:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
template_cancel = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)") |
...
|
...
] ["unpaved(4)"] "RWY.BL.type(5)" "RDN.BL.designator( |
...
6)" ("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 |
...
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”. |