Section 2. PREPARING
4-2-1. NOTAM COMPOSITION
a. NOTAMs must
contain these elements from left to right in the following order:
exclamation point (!);
Location (the identifier of the accountability location);
Location (the identifier of the affected facility or location);
4. Keyword (one
of the following: RWY, TWY, APRON, AD, COM, NAV, SVC, OBST, AIRSPACE, ODP,
SID, STAR, CHART, DATA, IAP, VFP, ROUTE, SPECIAL, or (O));
Identification (optional – this must be the runway identification for runway
related NOTAMs, the taxiway identification for taxiway-related NOTAMs, or
the ramp/apron identification for ramp/apron-related NOTAMs);
(the condition being reported); and
(identifies the effective time(s) of the NOTAM condition). Times must be
formatted in accordance with paragraph 4-2-1,
issued when the condition of a number of facilities, NAVAIDs, services, or
landing areas/runways are related to the same event (for
example, date/time, facility closing, part-timing, runway closures, etc.)
must be issued as separate NOTAMs.
c. Each NOTAM
concerning a specific aid, service, or hazard must be a complete report
including all deviations unless reference is made to other restrictions
information is published elsewhere and is still valid, reference must be
made to that publication with the statement, “PLUS SEE (publication).” A
NOTAM issued not stating “PLUS SEE (publication)” indicates the NOTAM
replaces previously published similar data.
!XYZ XYZ NAV VOR UNUSBL 010-030 BYD 10 BLW 4000 PLUS SEE AFD
e. NOTAMs must
state the abnormal status of a component of the NAS and not the normal
status. The only exception is for data that has been published and is being
replaced; for example, RWY 9/27 OPEN.
f. All NOTAMs
should have an expected time or date/time of return to service or return to
normal status. Absence of a date/time group will mean that the condition is
in effect and will continue until further notice (UFN). Do not transmit UFN
in the NOTAM text. The absence of a return to service time may be grounds
for automatic publication by NFDC.
g. The forward
slash, “/”, is used in the NOTAM text to indicate “and”; for example,
RWY 17/35 CLSD, or RWY 1/19 CLSD 12500/OVR.
The plus-sign (+) will not be used in NOTAM data.
h. Altitude and
height must be in feet MSL up to 17,999; for example, 275, 1225 (feet and
MSL shall not be written); and in flight levels (FL) for
18,000 and above; for example, FL180, FL550. When MSL is not known, specify
AGL; for example, 1304 AGL, etc.
Indicates the date/time a condition will exist or begin.
!ABC ABC NAV VOR OTS WEF 0710281600
The VOR is expected to go out of service at 1600 on October twenty-eight,
2007, and remain out until further notice.
!ABC ABC NAV VOR OTS WEF 0711281600-0711281800
The VOR is expected to go out of service at 1600 on November twenty-eight,
2007, and remain out until 1800 on November twenty-eight, 2007. At 1800, the
NOTAM will be cancelled automatically by the USNS.
Indicates the date/time a condition will expire or terminate.
!ABC ABC NAV VOR OTS TIL 0712281800
The VOR is expected to remain out of service until 1759. At that time, this
NOTAM will be cancelled automatically by the USNS.
Indicates the event will occur at the same time during the stated time
!ABC ABC AD CLSD 1100-1900 DLY WEF 0711011100-0711151900
Explanation: The airport is closed from 1100 to 1900 daily from
November 1, 2007, at 1100 until November 15, 2007, at 1900. This NOTAM will
be automatically cancelled by the USNS on November 15, 2007, at 1900.
l. A NOTAM can
contain only one effective period and/or one event/condition. If there is
more than one effective period and/or event/condition, issue separate NOTAMs.
4-2-2. NOTAM ACCOUNTABILITY
accountability (NOTAM file) for each location whose weather report is
disseminated via WMSCR and for the location of the tie-in FSS.
a. Issue NOTAMs
for a weather reporting location whose report is disseminated via WMSCR
under the location identifier of the weather report.
b. Issue all
other NOTAMs under the location identifier of the tie-in FSS. This includes
NOTAMs for weather reporting locations whose report is not disseminated via
c. Make NOTAM
accountability changes by mail, administrative message, or FAX when known
sufficiently in advance. When the published accountability for a NOTAM is
incorrect, change it by issuing a NOTAM under the published accountability.
As soon as practicable after issuance, contact the USNOF by telephone or
message and request they make the accountability change in the USNS tables.
Issue all subsequent NOTAMs under the corrected accountability. If there are
any current NOTAMs for the location, cancel and reissue those NOTAMs under the new
account-ability after the USNS tables have been changed. Notify Aeronautical
Information Management of any NOTAM accountability changes.
4-2-3. NOTAMs FOR
NAVAID IN DIFFERENT FSS FLIGHT PLAN AREA
monitoring a NAVAID located in a different FSS flight plan area, issue
NOTAMs under the accountability of that FSS or the weather reporting
location in accordance with paragraph 4-2-2.
NOTAM Accountability. Notify the other FSS of the issuance, subsequent
action(s), and cancellation.
notified of NOTAM action taken by another FSS monitoring a NAVAID located in
your flight plan area, record the information on FAA Form 7230-4, Daily
Record of Facility Operation.