U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION

ORDER
JO 7930.2P
Effective Date:
April 3, 2014
 
     
Subject:  Notices to Airmen
 

Section 2. Preparing NOTAMs for Dissemination

4-2-1. NOTAM COMPOSITION

NOTE-
For FDC NOTAM examples, see chapter 7.

a. NOTAMs must contain these elements from left to right in the following order:

1. An exclamation point (!).

2. Accountability (the identifier of the accountability location; for example, JFK, FDC, CARF).

3. Location designator (the identifier of the affected facility or location – located AFTER the NOTAM number).

4. Keyword.

5. Attribute, activity, or surface designator(s) (when needed).

NOTE-
A surface designator is required with keywords RWY, TWY, and APRON.

6. Surface segment (when needed).

7. Facility, feature, service, system, and/or components thereof (when needed).

8. Location description (when needed).

9. Lower limit/upper limit, or height, when needed. Limits must be specified as SFC (surface). Up to 17,999, express in feet MSL; for example, 275FT, 1225FT (MSL must not be written). For 18,000 and above, express in in flight levels (FL); for example, FL180, FL550, or UNL (unlimited). Heights AGL may be added in parentheses (125FT AGL).

10. Condition. The changed condition or status being reported, when needed; for example: CLSD, OUT OF SERVICE, NOT AVBL, NOT LGTD, FLAGGED, OBSC, UNREL, ON CONS.

11. Reason (when needed).

12. Remarks (optional). Other information considered important to the pilot.

13. Schedule, if needed. A single NOTAM may be originated for a scheduled condition/activity that will recur during the effective period. Specify the schedule between the condition/activity and the effective time string. The days of the week must be specified before the scheduled time. The term “DAILY” indicates the event will occur at the same time during the stated time period. The NOTAM effective time and expiration time must be compatible with the scheduled time.

14. Effective/expiration time. A 10­digit date­time group (YYMMDDHHMM) must be used to indicate the effective time and expiration time of the NOTAM. The effective time and expiration time must be separated by a hyphen “­.” The effective time indicates the date/time a condition will exist or begin. The expiration time is the expected return to service, return to normal status time, or the time the activity will end.

(a) If the NOTAM duration is uncertain, the approximate expiration time must be indicated by using a date­time group followed immediately by “EST” (estimate). Any NOTAM which includes an “EST” must be canceled or replaced before the expiration time specified in the NOTAM, as the NOTAM will not auto­expire. FDC NOTAMs relating to instrument flight procedures must not be canceled and reissued. (Reference FAA Order 8260.19, chapter 2, section 6.)

(b) When a NOTAM is originated to advertise a permanent condition that will be published in a publication, chart or database, “PERM” should be inserted as the expiration date in lieu of a 10­digit date­time group. The NOTAM originator is responsible for canceling the NOTAM upon publication.

(c) If neither “EST” nor “PERM” is used, the NOTAM will auto­expire at the expiration date.

b. NOTAMs 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 already published.

d. If 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.

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.

4-2-2. NOTAM ACCOUNTABILITY

Maintain separate 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 an FAA­monitored 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 WMSCR.

REFERENCE-
FAA Order JO 7930.2, Chapter 2, Aeronautical Information Services

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 accountability after the USNS tables have been changed. Notify Aeronautical Information Management of any NOTAM accountability changes.

 

Return to Chapter 4 Section 1 Go to Chapter 4 Section 3
Return to Air Traffic Publications Library Return to JO 7930.2 NOTAM Home Page