System Wide Information Management (SWIM)

Federal Notice to Airmen (NOTAM) System

(FNS) NOTAM Distribution Service (NDS)
Publish/Subscribe

Operational Context Document

Version 1.0

February 28, 2019

FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

SIGNATURE PAGE

Name Date
SWIM Implementation Lead

Name Date
SWIM Program Manager

Federal Aviation Administration

800 Independence Avenue, SW
Washington, D.C. 20591
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
DOCUMENT CHANGE HISTORY

Version Date Description of Changes

0.1 11/29/18 Initial Draft for SWIFT focus group review

0.2 2/12/19 Technical Edit

1.0 2/29/19 Final Draft for SWIFT focus group

FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

TABLE OF CONTENTS
1 Introduction.......................................................................................................1
2 Notice to Airmen...............................................................................................2
2.1 Introduction to NOTAMs........................................................................2
2.1.1 Automatic Data Processor................................................................2
2.1.2 Accountability, Number, Location Identifier...................................2
2.1.3 Keyword...........................................................................................3
2.1.4 Attribute and Surface Designator.....................................................3
2.1.5 Condition..........................................................................................3
2.1.6 Start/End of Activity.........................................................................4
2.2 Types of NOTAMS.................................................................................4
2.2.1 NOTAM D........................................................................................4
2.2.2 Military NOTAM.............................................................................4
2.2.3 FDC NOTAM...................................................................................4
2.2.4 Pointer NOTAM...............................................................................5
2.2.5 International NOTAM......................................................................5
2.2.6 Temporary Flight Restriction (TFR) NOTAM.................................5
2.2.7 Central Altitude Reservation Facility (CARF) and Special Activity
Airspace (SAA) NOTAMs......................................................................5
2.2.8 Field Condition (FICON) NOTAM..................................................5
2.2.9 Global Positioning System (GPS) NOTAM.....................................5
2.3 Federal NOTAM System........................................................................6
2.3.1 FNS Origination Services.................................................................6
2.3.2 FNS Distribution Services................................................................8
2.4 References...............................................................................................9
3 FNS-NDS........................................................................................................11
3.1 Service Overview..................................................................................11
3.2 NOTAM Topic Message <NOTAMTopicMessage>...........................11
4 FNS-NDS Pub/Sub Message Types................................................................13
4.1 NOTAM Topic Message <NOTAMTopicMessage>...........................13
4.1.1 beginPosition..................................................................................14
4.1.2 endPosition.....................................................................................14
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
4.1.3 Interpretation..................................................................................14
4.1.4 Scenario..........................................................................................15
4.1.5 Series..............................................................................................15
4.1.6 Number...........................................................................................15
4.1.7 Year................................................................................................15
4.1.8 Type................................................................................................15
4.1.9 Issued..............................................................................................15
4.1.10 cancelDate......................................................................................15
4.1.11 affectedFIR.....................................................................................15
4.1.12 selectionCode..................................................................................15
4.1.13 traffic..............................................................................................15
4.1.14 purpose............................................................................................15
4.1.15 scope...............................................................................................15
4.1.16 minimumFL....................................................................................16
4.1.17 maximumFL...................................................................................16
4.1.18 location...........................................................................................16
4.1.19 effectiveStart...................................................................................16
4.1.20 effectiveEnd....................................................................................16
4.1.21 schedule..........................................................................................16
4.1.22 text..................................................................................................16
4.1.23 lowerLimit......................................................................................16
4.1.24 upperLimit......................................................................................16
4.1.25 translation (type – LOCAL_FORMAT).........................................16
4.1.26 translation (type – OTHER:ICAO).................................................16
4.1.27 classification...................................................................................17
4.1.28 accoundId........................................................................................17
4.1.29 xoveraccountID..............................................................................17
4.1.30 xovernotamId..................................................................................17
4.1.31 airportname.....................................................................................17
4.1.32 originID..........................................................................................17
4.1.33 lastUpdated.....................................................................................17
4.1.34 icaoLocation...................................................................................17
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
4.1.35 snowtamCountryCode....................................................................17
Appendix A: Acronyms.........................................................................................18

LIST OF FIGURES
Figure 1. NOTAM Example................................................................................................2

Figure 2. FNS-NDS Architecture (FNS-NDS Pub/Sub data flow highlighted in light blue)
.............................................................................................................................................9

Figure 3. AIXM Event Feature Conceptual Model...........................................................14

LIST OF TABLES
Table 1. NOTAMTopicMessage Message Headers..........................................................11

Table 3. Acronym Listing..................................................................................................18

FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

1 Introduction
The purpose of this document is to provide users of Federal Notice to Airmen
(NOTAM) System (FNS) NOTAM Distribution Service (FNS-NDS) Publish/Subscribe
(Pub/Sub) products, provided through Federal Aviation Administration (FAA) SWIM
infrastructure, background information on how the data is generated, what the data
means, and how the data can be used.

 The beginning of this document provides details on the systems, which are
the source of the FNS-NDS data.
 Next, is a brief discussion on how the data can be utilized by aviation
stakeholders to improve their operation using the FNS-NDS data.
 Finally, a detailed breakdown of the individual data elements, their
definition, and their context is provided.

FNS-NDS provides Service Oriented Architecture (SOA) interfaces for airports

and other authorized NOTAM originators to send NOTAMs to the National Airspace
System (NAS) Enterprise Message Service (NEMS) for subscription by consumers using
SWIM compliant infrastructure and interface standards.

FNS-NDS Pub/Sub offers numerous benefits over legacy NOTAM publication,

including but not limited to:

a) Uses NEMS over legacy point-to-point infrastructure for distributing

NOTAMs.
b) Uses the Aeronautical Information Exchange Model (AIXM) 5.1 as the
message payload.
c) Schema used is harmonized between both FAA and EUROCONTROL.

Digital data, including geometries of the affected features, are only available for
NOTAMs originated or transformed by the FNS. NOTAMs not originated through FNS
are still included in FNS-NDS Pub/Sub, but only contain limited data provided from the
legacy system.

While the FNS-NDS includes both Request/Reply and Pub/Sub services, this
document will only cover the Pub/Sub functionality.

1
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

2 Notice to Airmen

2.1 Introduction to NOTAMs

In this section, an overview of NOTAMs is discussed. A NOTAM is a notice
containing information essential to personnel concerned with flight operations but not
known far enough in advance to be publicized by other means. It states the abnormal
status of a component of the NAS—not the normal status. Every user of the NAS is
affected by NOTAMs because they indicate the real-time and abnormal status of a
component of the NAS. NOTAMs concern the establishment, condition, or change of any
facility, service, procedure, or hazard in the NAS. NOTAMs have a unique language
using special contractions to make communication more efficient.

As NOTAMs are used by all pilots across the world, they are standardized to
follow the same structure to make reading them consistent regardless of the location. For
example, a NOTAM may read: !DCA 06/005 AML NAV VOR/DME OUT OF SERVICE
1706082230-1706302200. This NOTAM can be broken down to its subcomponents:
Automatic Data Processor; Accountability; NOTAM Number; Affected Location;
Keyword; Attribute, Activity, or Surface Designator; Condition; Start of Activity; End of
Activity, as shown in Figure 1.

Figure 1. NOTAM Example

2.1.1 Automatic Data Processor

Automatic Data Processing (ADP) Code/Exclamation Point (!). This is a
computer code with the Aeronautical Fixed Telecommunication Network (AFTN) used to
identify the start of a new NOTAM.

2.1.2 Accountability, Number, Location Identifier

The identifier of the accountability location. Ex.: A facility (such as DCA), Flight
Data Center (FDC), Central Altitude Reservation Facility (CARF). Here, AML is the
name of the Very High Frequency Omnidirectional Range (VOR)/Distance Measuring
Equipment (DME), Armel. The Location Identifier component is the affected facility or
location (airport, Navigational Aid [NAVAID], or Air Route Traffic Control Center
[ARTCC]) appears after the NOTAM number (YY/NNN, where YY is the two-digit

2
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
year, and NNN is the three-digit number, 001). Approach controls or airspace that occupy
multiple ARTCCs must have a separate NOTAM for each ARTCC.

2.1.3 Keyword
Include one of the following keywords:

 RWY – Runway
 IAP – Instrument Approach Procedure
 VFP – Visual Flight Procedure
 DVA – Diverse Vector Area
 TWY – Taxiway
 AD – Aerodrome
 OBST – Obstruction
 NAV – Navigation
 COM – Communication
 SVC – Services
 ODP – Obstacle Departure Procedure
 SID – Standard Instrument Departure
 STAR – Standard Terminal Arrival Route
 CHART
 DATA
 AIRSPACE
 SPECIAL
 SECURITY
 ROUTE
 APRON

2.1.4 Attribute and Surface Designator

In the above example, the Armel VOR/DME (attribute) is out of service for a
specified time frame. A surface designator is required with the keywords RWY, TWY,
and APRON.

2.1.5 Condition
The condition of the Attribute.

 OUT OF SERVICE

3
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
 OPN – OPEN
 ACT – ACTIVE
 CLSD – CLOSED (may be followed by TO [limitation] or EXC
[exception])

2.1.6 Start/End of Activity

A 10-digit date/time group (YYMMDDHHMM) Coordinated Universal Time
(UTC) indicating: The time at which the NOTAM comes into force (the date/time a
condition will begin). The time at which the NOTAM ceases to be in force and becomes
invalid (the expected time of return to service, return to normal status, or the end of the
activity).

2.2 Types of NOTAMS

2.2.1 NOTAM D
These are NOTAMs containing information concerning the establishment,
condition, or change of any:

 Aeronautical facility
 En Route NAVAIDS
 Services
 Procedures
 Hazards
 Civil public-use airports listed in the U.S. Chart Supplement

NOTAM Ds are numbered consecutively each month by the NOTAM System

starting with 001 for each accountability.

Most NOTAM Ds are originated via FNS, however a few that are external.
Within FNS there is a capability to use digital or free-text scenarios to create NOTAMs.
When digital NOTAM scenarios are used, three types of translations are created.  That is,
domestic (FAA) format, ICAO format and also plain language.  Of these, only the
domestic format is the official one, others are provided as part of the capability of FNS.
All these formats are created at the time of NOTAM creation and published at the same
time. Due to the automated creation of the ICAO and plain language NOTAMs, the
NOTAM office has no role in creating them.  

4
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
To the extent possible, FNS-NDS includes geometries/polygons of locations
(e.g., taxiway, movement area, runway closure, etc.). Geometries are primarily included
for digital NOTAMs.

2.2.2 Military NOTAM

Military NOTAMs are issued by the U.S. Air Force, Army, Marines, Navy, and
Coast Guard against NAVAIDS and airports. These NOTAMs are numbered
consecutively by accountability, location, and series (beginning with “S0001” each year,
where “S” stands for a generic series the military may have). The NOTAM number and
year of issuance are separated by a forward slash.

2.2.3 FDC NOTAM

These NOTAMs contain flight information that is normally regulatory in nature,
including but not limited to:

 Changes to Instrument Flight Rules (IFR) charts

 Procedures
 Airspace usage

FDC NOTAM numbers are assigned consecutively by the United States NOTAM
System (USNS), beginning with “0001” each year. The year of issuance and the serial
number are separated by a forward slash (Y/NNNN).

2.2.4 Pointer NOTAM

A Pointer NOTAM is a NOTAM D issued to point to another NOTAM. The
keyword in the pointer NOTAM must match the keyword in the original NOTAM.

2.2.5 International NOTAM

International NOTAMs are received from other countries and are also generated
by the U.S. NOTAM Office (USNOF). International NOTAMs are stored in the NOTAM
System.

2.2.6 Temporary Flight Restriction (TFR) NOTAM

A TFR is a type of NOTAM that defines an area restricted to air travel due to a
hazardous condition or a special event, or that distributes a general warning for the entire
FAA airspace.

5
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

2.2.7 Central Altitude Reservation Facility (CARF) and Special

Activity Airspace (SAA) NOTAMs
CARF NOTAMs contain airspace and altitude reservations transmitted by the
USNOF after receipt of the candidate NOTAM from the CARF office. SAA includes
special use airspace (SUA) (restricted area, military operations area [MOA], warning
area, and alert area airspace), instrument and visual military training routes, and aerial
refueling tracks and anchors.

2.2.8 Field Condition (FICON) NOTAM

A FICON NOTAM contains information on the surface conditions of landing
runways, taxiways, and aprons.

2.2.9 Global Positioning System (GPS) NOTAM

GPS interference missions are conducted to meet national security requirements
and normally cover a wide geographical area. During the testing, GPS signals may
become unavailable. A NOTAM is issued to describe the affected area(s).

2.3 Federal NOTAM System

The FNS is the modernized NOTAM management system designed to digitize the
collection, dissemination, and storage of NOTAMs. The goal is to create a single
authoritative source for NOTAM entry and dissemination to improve the efficiency,
safety, and data quality of NOTAM information.

Within the modernized NOTAM concept of operations, the entire NOTAM

process has been re-engineered to support improved NOTAM origination, management,
and distribution. The basic concept behind FNS is to have the NOTAM originator
generate and submit the NOTAM using a web-based standard template. The inputs from
the standard template will be validated against policy-driven business rules and
immediately published. The NOTAM information will also ultimately be distributed in
digital format to external users.

The FNS consists of an ecosystem of services and applications that, together,

bring this modernized NOTAM concept to life.

2.3.1 FNS Origination Services

Modernized NOTAM origination (collection) is focused on re-engineering the
business process of creating and submitting for publication candidate NOTAMs. The new

6
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
process moves the responsibility for creating NOTAMs to those who directly observe the
hazardous condition(s) within the NAS. By allowing the information describing the
NOTAM condition to be directly captured at the source in a standardized and digital
manner, FNS enables automated validation of the submitted information against a set of
policy-driven business rules. A digital NOTAM describes the temporary status change of
a static feature caused by an event within the NAS in a standardized manner enabled by
AIXM. The FNS Origination Services are comprised of three applications/services for
originating NOTAMs: NOTAM Manager (NM), NOTAM Origination Service, and
eNOTAM II.

2.3.1.1 NOTAM Manager

The NM application is a web-based user interface that enables authorized

NOTAM originators to manage their NOTAMs. NM allows originators to create digital
NOTAMs through template-driven event scenarios1 that link to the applicable
authoritative source(s) of static baseline feature data. NM submits candidate digital
NOTAMs created within NM directly to the USNS for numbering and publication within
seconds of submission. NM currently supports the origination of airport operations and
technical operations NOTAMs.

2.3.1.1.1 FNS Airport Self-Certification

The FNS Airport Self-Certification application supports a streamlined process for

activating NM at airports throughout the NAS. Before an airport can begin issuing digital
NOTAMs, there are several standard activities that must take place, such as registration,
signing of required agreements, review of an airport’s static baseline data, and provision
of NOTAM originator training. The FNS Airport Self-Certification application provides
the airport authority representative and the FAA a common platform for communicating
and working through this activation process in a standard workflow.

Event scenarios are specific cases of NOTAM origination described by the FAA. The FAA
provides documentation for General Rules for All Event Scenarios, Airport Operations Event Scenarios,
FAA Technical Operations Event Scenarios, and Tower Light Outage Event Scenarios.

7
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
2.3.1.2 NOTAM Origination Service

The NOTAM Origination Service (NOS) is a web service that uses the same
event scenarios defined for use within NM to issue digital NOTAMs. The NOS allows
third parties to submit candidate NOTAMs to the FNS using this system-to-system
interface that can integrate with their existing systems. A typical use case for the NOS
involves integration with remote monitoring software used by tower companies, which
would enable automatic submission of the tower light outage information to the FAA for
NOTAM publication.

2.3.1.3 eNOTAM II

As part of the NOTAM modernization transition to the FNS, incremental

improvements can also be made on the legacy NOTAMs to improve the near term
business process for originating NOTAMs. FNS also includes an eNOTAM II application
that improves the process for Flight Services to review, approve, and coordinate analog
NOTAMs. Originators can use this application while they prepare their appropriate
requirements for transitioning to issuing digital NOTAMs. During this transition period,
users of eNOTAM II can gain near term improvements in managing their NOTAMs,
which will be able to be reviewed and approved more efficiently by Flight Services,
followed by direct submission to USNS for numbering and publication.

2.3.2 FNS Distribution Services

Modernized NOTAM distribution focuses on improving the ability for end users,
such as air traffic control, airlines, and general aviation pilots, to receive NOTAMs that
are relevant for their needs. Between the combined efforts of moving forward to change
NOTAM formats in policy and to transitioning to the origination of more NOTAMs
digitally, the degree of standardization in the NOTAM text and underlying digital data
enables improved filtering and querying of NOTAMs by end users. The FNS is
comprised of two methods of distributing NOTAMs: NOTAM Search and the FNS
NOTAM Distribution Service.

2.3.2.1 NOTAM Search

The NOTAM Search application is a web-based user interface for querying

NOTAMs, and it is available to the public. NOTAM Search provides end users with
query tools such as location, geographic, accountability, and free text searching, as well
as NOTAM filtering and sorting tools. NOTAM Search also provides additional

8
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
contextual information alongside the details of an individual NOTAM to provide end
users with the beginning of a one-stop-shop for NOTAM information.

2.3.2.2 FNS NOTAM Distribution Service

The FNS-NDS is a web service that provides digital NOTAM messages in AIXM
in response to requests by end users. The FNS-NDS is a system-to-system interface that
enables end systems to receive digital NOTAMs from FNS. The FNS-NDS uses the event
schema developed by the international Digital NOTAM Focus Group jointly led by
EUROCONTROL and the FAA. Digital NOTAM messages exchanged through the FNS-
NDS include static baseline features as well as the temporary changes due the NOTAM
event, and enables the graphical display of NOTAMs. The FNS-NDS supports the
distribution of all NOTAMs to include the digital NOTAMs originated through the FNS
as well as legacy NOTAMs originated through the legacy system.

Figure 2 below shows the data flow between the various NOTAM originators and
the FNS-NDS subscribers.

9
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

Figure 2. FNS-NDS Architecture (FNS-NDS Pub/Sub data flow highlighted in light blue)

2.4 References
Additional information pertaining to FNS-NDS and its capabilities can be found
at:

 https://nsrr.faa.gov/node/7682/profile2 – FNS-NDS Pub/Sub NAS Service

Registry and Repository (NSRR) Page
o FNS-NDS Concept of Operations
o FNS-NDS Java Messaging Service Description Document
(JMSDD)
o FNS-NDS eXtensible Markup Language (XML) schema
 https://notams.aim.faa.gov
o Event Scenario documentation – provide AIXM mapping of
specific NOTAM events
2

Requires access to FAA NAS Service Registry and Repository (NSRR), new accounts can be
requested at https://nsrr.faa.gov/user/register

10
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
o NOTAM Search
o FNS NOTAM Manager
o FNS Airport Self-Certification
o eNOTAM II
 https://www.faa.gov/about/initiatives/notam/media/NOTAM_101_Primer.
pdf – NOTAMs 101 primer presentation
 http://aixm.aero/document/aixm-51-xml-schema-xsd
o AIXM 5.1 data model and schema
 http://aixm.aero/sites/aixm.aero/files/imce/AIXM51/aixm_uml_to_aixm_x
sd_mapping-1.1.pdf
o AIXM UML to AIXM schema mapping

11
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

3 FNS-NDS

3.1 Service Overview

The FNS-NDS Pub/Sub is a Java Messaging Service interface for
publishing/distributing NOTAMs. It supports all NOTAMs, legacy and digital, published
in the USNS. The digital NOTAMs are implemented using the concept of event
scenarios.

3.2 NOTAM Topic Message <NOTAMTopicMessage>

The FNS-NDS publishes one message type, the NOTAMTopicMessage. This
message includes message headers describing specific properties of the NOTAM, and the
payload of the message is coded an AIXM message.

Table 1. NOTAMTopicMessage Message Headers

Property Name Description Permissible Values

NOTAM classification values:
 Domestic (D)
Specifies the NOTAM  FDC (F)
SourceType  Military (M)
classification
 Local Military (L)
 International (I)
 Others (O)
NOTAM location designator of Any active NOTAM location
LocationDesignator
the affected airport/heliport or identifier
facility
Function of the NOTAM  NOTAMN
 New  NOTAMR
NOTAMFunction
 Replacement  NOTAMC
 Cancelled

12
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
Property Name Description Permissible Values
 AD
 APRON
 AIRSPACE
 CHART
 COM
 IAP
 NAV
 OBST
 ODP
Keyword associated with the  ROUTE
NOTAMKeyword
NOTAM  RWY
 SECURITY
 SID
 SPECIAL
 STAR
 SVC
 TWY
 VFP
 CONSTRUCTION
 LTA
AirspaceUsage Additional message property to  TFR
filter airspace related NOTAMs  SUA
 CARF
NOTAMStatus Status of the NOTAM  ACTIVE
 CANCELLED3

All data provided by the FNS-NDS Pub/Sub conforms to the AIXM 5.1 Model
with available extensions. All data elements provided by the FNS-NDS Pub/Sub conform
to definitions, syntax, and constraints as defined in the AIXM XML schema.

The specific content of the AIXM message differs based on the scenario. The
event scenario documentation listed under Section 2.4 ReferencesError: Reference source
not found contains the details of the event scenarios and data elements supported by FNS.

“Cancelled” status indicates a NOTAM has been manually de-activated or removed from the
USNS prior to its end time by a NOTAM Issuer. “Expired” do not receive a specific status in FNS-NDS, as
expired NOTAMS indicate a NOTAM that was active until its end time, at which time the NOTAM was
automatically deactivated by the USNS.

13
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

14
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

4 FNS-NDS Pub/Sub Message Types

The only message types published by FNS-NDS is the NOTAMTopicMessage.

4.1 NOTAM Topic Message <NOTAMTopicMessage>

The only common AIXM element in all the NOTAM messages is the Event
feature. The conceptual model for the Event feature and the data elements are described
in Figure 3, and the associated FNS-DS data elements are included below. As the payload
of the NOTAMTopicMessage is fully AIXM compliant, readers are encouraged to
reference existing AIXM documentation in Section 2.4 References for more information.

15
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

Figure 3. AIXM Event Feature Conceptual Model

4.1.1 beginPosition
Start date/time of the AIXM Event Feature (which coincides with the start date of
the NOTAM).

4.1.2 endPosition
End date/time of the AIXM Event Feature (which coincides with the expiration
date of the NOTAM, if known).

4.1.3 Interpretation
AIXM Temporality model attribute for the Event TimeSlice and applies to all new
Events: BASELINE.

16
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

4.1.4 Scenario
Identifier of the event scenario used for digital encoding. The mapping can be
found in the Event Scenario documents identified in Section 2.4 References.Error:
Reference source not found

4.1.5 Series
NOTAM series value per International Civil Aviation Organization (ICAO)
Annex-15.

4.1.6 Number
NOTAM number value per ICAO Annex-15.

4.1.7 Year
NOTAM year values per ICAO Annex-15.

4.1.8 Type
NOTAM type value per ICAO Annex-15. Accepted values are: New (N), Replace
(R), Cancel (C).

4.1.9 Issued
Issue date/time of the NOTAM.

4.1.10cancelDate
Cancel date/time of the NOTAM.

4.1.11affectedFIR
Flight Information Region (FIR) that is impacted by the NOTAM.

4.1.12selectionCode
Q Code value for the NOTAM.

4.1.13traffic
NOTAM traffic value per ICAO Annex-15.

4.1.14purpose
NOTAM purpose value per ICAO Annex-15.

17
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

4.1.15scope
NOTAM scope value per ICAO Annex-15.

4.1.16minimumFL
NOTAM minimum flight level value per ICAO Annex-15.

4.1.17maximumFL
NOTAM maximum flight level value per ICAO Annex-15.

4.1.18location
NOTAM location designator of the affected airport/heliport or facility.

4.1.19effectiveStart
Start date/time of the NOTAM in UTC.

4.1.20effectiveEnd
End date/time of the NOTAM in UTC in YYYYMMDDHH24MI format. If the
end date is an estimate, the effectiveEnd will be appended with “EST.” If the NOTAM is
a permanent NOTAM, the value of this element will be “PERM.”

4.1.21schedule
Contains a schedule of activity/outage if the hours of effect are less than 24 hours
a day.

4.1.22text
NOTAM condition text.

4.1.23lowerLimit
Specifies the lower height restriction of the NOTAM.

4.1.24upperLimit
Specifies the upper height restriction of the NOTAM.

4.1.25translation (type – LOCAL_FORMAT)

NOTAM in domestic format. This is the format that should be used for
classification types: Domestic, FDC.

18
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

4.1.26translation (type – OTHER:ICAO)

NOTAM in ICAO format. This is the format that should be used for classification
types: International, Military, and Local Military.

4.1.27classification
NOTAM classification: Domestic (DOM), FDC (FDC), Military (MIL), Local
(LMIL), International (INTL).

4.1.28accoundId
NOTAM accountability designator.

4.1.29xoveraccountID
NOTAM crossover account identifier (for linking domestic to international
crossovers with the original domestic NOTAM).

4.1.30xovernotamId
NOTAM crossover identifier (for linking domestic to international crossovers
with the original domestic NOTAM).

4.1.31airportname
Published name of the airport/heliport or facility.

4.1.32originID
Origin identifier for NOTAMs originated outside of FNS, if available.

4.1.33lastUpdated
Date/time of last update to the NOTAM record.

4.1.34icaoLocation
ICAO location designator, if published.

4.1.35snowtamCountryCode
Country Code of snow related NOTAM (SNOWTAM).

19
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19

Appendix A: Acronyms
Table 2. Acronym Listing

Acronym Definition
ACT Active
AD Aerodrome
ADP Automatic Data Processing
AFTN Aeronautical Fixed Telecommunication Network
AI Aeronautical Information
AIXM Aeronautical Information eXchange Model
ARTCC Air Route Traffic Control Center
CARF Central Altitude Reservation Facility
CLSD Closed
COM Communication
DME Distance Measuring Equipment
DOM Domestic
DVA Diverse Vector Area
EST Estimate
FAA Federal Aviation Administration
FDC Flight Data Center
FICON Field Condition
FIR Flight Information Region
FNS Federal NOTAM Service
FNS-NDS Federal NOTAM Service NOTAM Distribution System
GPS Global Positioning System
IAP Instrument Approach Procedure
ICAO International Civil Aviation Organization
IFR Instrument Flight Rules
INTL International
JMSDD Java Messaging Service Description Document
LMIL Local Military
MIL Military
MOA Military Operations Area
NAS National Airspace System
NAV Navigation
NAVAID Navigational Aid
NDS NOTAM Distribution System
NEMS NAS Enterprise Messaging Service
NM NOTAM Manager
NOS NOTAM Origination Service

20
FNS-NDS Pub/Sub Operational Context Document Version 1.0
2/28/19
Acronym Definition
NOTAM Notice to Airmen
NSRR NAS Service Registry and Repository
OBST Obstruction
ODP Obstacle Departure Procedure
OPN Open
PERM Permanent
Pub/Sub Publish/Subscribe
RWY Runway
SAA Special Activity Airspace
SID Standard Instrument Departure
SNOWTAM Snow Related NOTAM
SOA Service Oriented Architecture
STAR Standard Terminal Arrival Route
SUA Special Use Airspace
SVC Services
SWIM System Wide Information Management
TFR Temporary Flight Restrictions
TWY Taxiway
USNOF US NOTAM Office
USNS United States NOTAM Service
UTC Coordinated Universal Time
VFP Visual Flight Procedure
VOR Very High Frequency Omnidirectional Range
XML eXtensible Markup Language

21