Section 1. Transmitting FDC NOTAM Data


FDC NOTAMs refer to information that is normally regulatory in nature and includes, but is not limited to, the following:

  1. Interim IFR flight procedures.
  1. Air traffic service route changes.
  2. Instrument flight procedure changes to include special instrument flight procedures, Standard Instrument Approach Procedures (SIAP), textual and graphic Obstacle Departure Procedures (ODP), Standard Instrument Departures (SID), and Standard Terminal Arrivals (STAR). Refer to FAA Order 8260.19, Flight Procedures and Airspace, for policy guidance and procedures for the issuance, tracking, and cancellation of FDC NOTAMs relating to instrument flight procedures.
  3. Airspace changes in general. For FDC NOTAMs that are generated due to unforeseen events, use keyword/title “AIRSPACE…NOTICE”.
  1. Temporary flight restrictions.
  1. Disaster/hazard areas.
  2. Aerial Demonstrations.
  3. Hijacking.
  4. Flight restrictions in the proximity of the President and other parties.


Presidential aircraft includes the aircraft and the entourage of the President, the Vice President, or other public figures designated by the White House.


FAA Order JO 7210.3, Chapter 5, Section 1, Presidential Aircraft.

  1. 14 CFR Part 139 certificated airport condition changes.
  2. Air defense emergencies.
  3. Emergency flight rules
  4. Substitute airway routes.
  5. Special data.
  6. U.S. Government charting corrections
  7. Laser activity.
  1. Instrument flight procedure FDC NOTAMs may, at the direction of the Aeronautical Information Services and Flight Inspection Services Group personnel, be used for either temporary or permanent conditions.
  2. NOTAMS for temporary conditions must be identified by the addition of “EST” following the expiration date/time group. NOTAMs for permanent conditions must be identified by inserting “PERM” in lieu of an expiration date/time group.
  3. FDC NOTAMs of a permanent nature, relating to instrument approach and obstacle departure procedures and airways, must remain current until published in the Terminal Procedures Publication or applicable en route chart.
  1. Instrument Flight Procedure (IFP) NOTAMs. Changes to IFPs that have been charted and distributed, are processed as FDC NOTAMs and issued through the NS. Procedural NOTAMS are originated by FAA Flight Operations and FAA Flight Inspection and Procedures personnel. When these revisions cannot be published in advance of their effective date, the NOTAM is transmitted as an FDC NOTAM. The applicable keyword (ODP, SID, STAR, CHART, DATA, IAP, VFP, ROUTE, or SPECIAL) will be included immediately following the location identifier designator.


The USNOF is responsible for Quality Control on Interim IFR Flight Procedure NOTAMs.

  1. Procedural minimums must not be lowered by NOTAM unless fully justified as a safety of flight issue or after returning the minimums to their previously published level at the end of the NOTAM.
  2. Both temporary and permanent conditions may be promulgated via an FDC NOTAM at the direction of AIS.
  1. Temporary conditions. NOTAMS for temporary conditions whose expiration time is uncertain and approximate, must be identified by the addition of “EST” following the NOTAM date/time group. The “EST” suffix may be used with all IFP T-NOTAMs.
  1. When it is known that the condition requiring a NOTAM will be effective for more than four chart cycles (224 days), a procedure amendment [revised 8260-series form] or permanent NOTAM must be submitted as soon as possible to allow publication of the change within the 224-day timeframe.
  2. When the timeframe for temporary conditions requiring NOTAM action is unknown or cannot be determined and the condition is beyond the control of the NOTAM issuing authority; e.g., airport construction, NAVAID restrictions, temporary obstructions, etc., the NOTAM issuing authority will ensure the line of business (LOB) approving the temporary condition is advised (copy the Flight Technologies and Procedures Division, AFS-400) of the procedural impact and the necessity of reconciling the condition as soon as possible so the temporary NOTAM can be canceled within the 224-day timeframe.
  3. If the condition cannot be corrected within 224 days, the NOTAM issuing authority must obtain Flight Standards approval from AFS-400 for the NOTAM to remain in effect beyond the 224-day limitation. It is important that NOTAMs not be allowed to remain active for excessive periods of time; therefore, an FDC IFP NOTAM must not be canceled and re-issued without Flight Standards approval.


Requests for Flight Standards approval must be coordinated with AFS-400 as soon as the requirement is known. For example, it is known that a temporary crane affecting an IFP(s) will be in place for 10 months as soon as it is erected; therefore, forward the approval request for extension immediately.

  1. Permanent conditions. When the condition requiring NOTAM action is known to be permanent or is expected to be effective for more than four charting cycles (224 days), a permanent NOTAM is used to promulgate amended SIAPs and textual ODPs as well as correction information for U.S. Government aeronautical charts.
  1. Identify permanent NOTAMs by inserting “PERM,” meaning the condition is permanent, instead of an actual date/time group. Procedural amendments may be charted from the permanent NOTAM information and may also be used as a substitute for the abbreviated amendment process within the limitations specified in Order 8260.19.
  2. IFP permanent NOTAMs contain information that is complete for charting purposes and are promulgated in the bi-weekly Transmittal Letter (TL) with a specified procedure amendment date that is coincidental with an international Aeronautical Information Regulation and Control (AIRAC) charting date.
  3. Permanent NOTAMs may only be used for SIAPs, textual ODPs, and to correct U.S. Government charting printing and compilation errors. Permanent NOTAMs must not be used for changes to Special IFPs, ATS routes, graphic ODPs, SIDs, and STARs.
  4. Permanent NOTAMs may be used to amend procedures without a complete review of the procedure. The amendment will be indicated by an alphanumeric identifier; e.g., Orig-A, Amdt 3B, Amdt 4C, etc.
  5. Only one procedure may be addressed per Permanent NOTAM except that a single P NOTAM may be used for ILS CAT I/II/III and SA CAT I /II procedures to the same runway. A single Permanent NOTAM may also address multiple procedures at a single location when correcting a common printing error on U.S. Government charts.
  6. A hard/electronic copy of each Permanent NOTAM must be stored with the current amendment and maintained with the procedure filed by AIS specialists.
  7. Permanent NOTAMs must not be used for RNAV/database driven procedures when the change(s) will affect waypoint coordinates, course (track), distances, or bearings.
  8. The Permanent NOTAM originator must coordinate a procedure amendment date with AIS for inclusion in the Transmittal Letter. This will ensure that all charting agencies publish the amended procedure on the same AIRAC chart cycle and with the same procedure amendment date.
  9. Each AIRAC cycle is limited to no more than 150 Permanent NOTAMs, except for Flight Standards directed safety initiatives or national implementation processes. Whenever the 150 P NOTAM limit must be exceeded, AIS is responsible for coordinating with other charting agencies; e.g., Jeppesen, LIDO, etc., to ensure they can accommodate the necessary changes on the required AIRAC date.
  10. Permanent NOTAMs must be canceled when the applicable procedural change has been published.
  11. When a Permanent NOTAM is originated to permanently amend a SIAP or textual ODP, “PERM” must be inserted as the expiration date in lieu of a 10-digit date-time group. The NOTAM originator is responsible for cancelling the NOTAM upon publication.
  12. A NOTAM will auto-expire at the expiration DTG unless “PERM” is used.
  1. NOTAM Procedures:
    The applicable keyword (ODP, SID, STAR, CHART, DATA, IAP, VFP, ROUTE, DVA, or SPECIAL) will be included immediately following the location identifier designator.
  1. Standard instrument approach procedure and special instrument flight procedure format:
  1. For SIDs and STARs serving multiple airports, a separate FDC NOTAM must be prepared for each airport affected by the procedure. Permanent NOTAMs must not be used as a source to effect charting changes for these procedures. Procedural NOTAMS are originated by FAA Flight Operations and FAA Flight Inspection and Procedures personnel and are transmitted to the NS. When these revisions cannot be published in advance of their effective date, the NOTAM is transmitted as an FDC NOTAM.
  2. Permanent procedural changes to graphic ODPs and SIDs must be made via a new or amended 8260-15 series form [see 8260-17 series forms for STARs] within 224 days of the issuance of the associated NOTAM.
  1. Form 8260-17.1, Standard Terminal Arrival [and Form 8260-17.2, STAR (Data Record) for RNAV STARs] must be submitted for permanent charting changes. NOTAMs on STARs must not exceed 224 days [see paragraph 2-6-3.a].
  1. Instrument Flight Procedure NOTAMs. A complete review and a new amendment are the preferred methodology for permanent procedure changes, particularly when applying new or revised Order 8260.3 criteria. However, it is recognized that this may not always be possible due to time constraints, workload, staffing level, etc. Abbreviated 8260-series forms and/or Permanent NOTAMs have proven to be an effective means of updating aeronautical charts and amending instrument flight procedures within the following guidelines:
  1. Whenever the need for a NOTAM to a procedure arises, AIS, or the non-FAA service provider must review the procedure and ascertain that there is no other safety of flight changes required. If a Permanent NOTAM is required to amend a SIAP or textual ODP for safety reasons, other items may be included in the NOTAM to simultaneously update procedure charts.
  2. Procedural minimums must not be lowered by NOTAM except when returning minimums to their previously published level at the end of a temporary condition. Refer to Order 8260.19, Flight Procedures and Airspace, chapter 8, for conditions pertaining to IFP NOTAMs when amending an instrument flight procedure.
  3. Exercise caution in initiating or adding a NOTAM to a procedure when there is already a current NOTAM in effect for the procedure. In many cases close follow-up action, including canceling and reissuing NOTAMs, will be necessary to ensure there is no confusion for pilots and chart producers. All FDC NOTAMs must be issued against the currently published procedure.
  4. When a NOTAM D is issued closing an airport permanently, an FDC NOTAM need not be issued denying use of an IFP. A routine procedure cancellation should be processed.
  5. When a NOTAM D is issued to shut down a facility permanently, only routine cancellations of procedures predicated on that facility are required. FDC NOTAMs may be required for other procedures supported by the affected facility.
  6. When a NOTAM D is issued closing a runway, an FDC NOTAM need not be issued denying approach or departure minimums to that runway. If the closing is permanent, routine procedure cancellations, including takeoff/departure procedures, must be processed immediately.
  7. When a NOTAM D is issued for a facility shutdown or outage, an FDC NOTAM denying IFP use is not required for those IFPs using only that facility. However, other IFPs in the vicinity must be reviewed to determine if that facility supports courses or fixes; in such cases, those IFPs require an FDC NOTAM. Particular attention must be given to fixes supporting stepdown minimums and missed approach procedures, which are predicated on the out of service facility. It is not necessary to issue NOTAMs for fixes and terminal route segments that are related to unusable airway segments from the subject facility. Do not issue “Radar Required” NOTAMs on unusable or restricted ATS route segments. Also, see Order 8260.19, paragraph 4-3-3, for ILS CAT II/III NOTAM restrictions.
  8. When a NOTAM D removes a localizer from service, the ILS approach is unusable. If the glide slope (GS) is out, the precision approach is unusable. If other ILS components are out, the inoperative table applies. In these instances, an FDC NOTAM for the ILS approach is not required.
  9. When Final Approach Segment (FAS) data problems are reported and LPV minimums must be restricted, also restrict use of the WAAS VNAV.  The NOTAM must read: "LPV MINIMUMS AND WAAS VNAV NA."


Some avionics use the LPV FAS data information to establish the glideslope for the LNAV/VNAV. Baro VNAV is not affected.

  1. Chart correction NOTAMs. FDC NOTAMs to correct U.S. Government chart printing or compilation errors are issued by AIS. If the NOTAM is used to correct an IFP, specify the location identifier of the airport affected by the procedure, the full procedure title and amendment number (if applicable). If the NOTAM is used to correct a chart; e.g., VFR sectional chart, IFR enroute chart, etc., use “FDC” as the location identifier. The first word in the NOTAM text should be “correct.”
  2. RNAV substitution. Properly equipped aircraft may substitute RNAV systems for inoperative ground NAVAIDs; however, RNAV systems must not be substituted for NAVAIDs providing final approach course guidance on instrument approach procedures.
  1. When the use of an instrument approach procedure, departure procedure (SID or ODP), or STAR is restricted or prohibited by NOTAM because of a NAVAID (VOR, TACAN, NDB, compass locator, or DME) outage, the NOTAM does not apply to aircraft equipped with suitable global positioning system (GPS) RNAV. For clarification, state the reason for the restriction in the text of the procedural FDC NOTAM.
  2. In certain circumstances, AFS-400 may determine that the use of RNAV systems that utilize DME/DME/inertial reference unit (IRU) inputs should be allowed [see Order 8260.19, paragraph 4-6-9, for additional information/requirements]. In these instances, AFS-400 will advise AIS by e-mail or memorandum to insert the phrase “OR DME/DME/IRU” after “SUITABLE RNAV SYSTEM WITH GPS.” Include in the NOTAM any required DME facilities, as provided by AFS-400 to support DME/DME/IRU operations.
  1. Air Traffic Service Route NOTAMs. Under 14 CFR Part 71.13, the term “ATS route” refers to a variety of routes, including airways, jet routes, and RNAV routes. When a restriction or a change to an ATS route requires a NOTAM, AIS must prepare and forward an FDC T-NOTAM following the procedures in paragraph 7-1-3. b.
  1. ATS Route changes involving a single state and one or more ARTCCs must be issued with the ARTCC identifier followed by the two-letter state code. The two-letter state code must also follow all NAVAID and fix designators.
  2. If the ATS Route NOTAM affects one, two, or three ARTCCs and multiple states, issue a separate NOTAM for each affected ARTCC. Do not include two-letter state codes if more than one state is involved.
  3. If the NOTAM affects four or more ARTCCs, send one NOTAM using “FDC” as the facility identifier.
  4. If the restriction will exceed the 224-day time limit, a procedure amendment (revised 8250-series form or permanent NOTAM) must be submitted as soon as possible to allow publication of the change within the 224-day timeframe.
  1. FDC NOTAMs for Special Instrument Approach Procedures (Specials). FDC Temporary NOTAMs may also be used to promulgate safety of flight information relating to Specials provided the location has a valid landing area identifier and is serviced by the NS.
  1. If the Special is maintained by AIS or a non-FAA service provider and the location is in the NS, then procedures for NOTAM processing will be similar to the procedures used for public, 14 CFR part 97 instrument approach procedures. When preparing the NOTAM for submission, include the keyword “Special” immediately following the three or four character location identifier. (!FDC PAJN SPECIAL)
  2. AIS/non-FAA service providers will notify the Regional NextGen Branch (RNGB) as soon as practicable when a NOTAM has been issued.


For AIS maintained procedures, after duty hours, contact the stand-by AIS representative at (405) 954 8260.

  1. If the Special procedure location is not in the NS, whoever is responsible for maintaining the procedure will notify the applicable RNGB of the change/outage. The RNGB must contact the user(s) of the procedure to disseminate appropriate action; (e.g., NA the procedure, raise applicable minimums, etc.)
  2. Non-FAA service providers must notify Flight Inspection Services of the change/outage if flight inspection is responsible for conducting flight inspection/validation activities.
  1. NOTAM content.
  1. FDC SIAP and textual departure NOTAMs must identify the procedure being amended and the current amendment number. NOTAMs for graphic ODPs, SIDs, and STARs must reflect the current procedure identification, including number. The NOTAM must be as concise as possible.
  2. The issuing authority must prepare the NOTAM using plain language text and those contractions found in Order JO 7340.2 and those contractions and abbreviations used on IFP charts. Specialists must keep in mind that the NOTAM is directed to the pilot, and should be worded so that the intended change will not be misinterpreted. Avoid the use of internal cartographic instructions that have no meaning to pilots. Spell out NAVAID names in clear text followed by the identifier. If it appears that the NOTAM length will exceed 20 lines, call the USNOF at (888)-876-6826 for assistance and guidance.
  3. For temporary obstructions, include the type, elevation, distance, and direction from the airport or runway threshold, as appropriate, as the last line of the NOTAM text. Do not preface this information with “Chart”
  4. Include a reason for the NOTAM following the NOTAM text. This information will not be transmitted as a part of the NOTAM text, but will inform the NFDC and the USNOF of the basis for the NOTAM. It will also ensure the data is retained in the NOTAM historical files.

When requested by a Flight Standards District office, the USNOF will ensure an FDC NOTAM is issued.


14 CFR Part 91.144 and FAA Order JO 7110.10, Flight Services, Chapter 3.

  1. Through system interface, the NOTAM requestor must forward the NOTAM information directly to the USNOF for FDC NOTAM issuance and to the FSS nearest the incident site for coordination purposes. The NS disseminates FDC NOTAMs, and the FSS must act as “coordination facility” for preflight briefings for the ARTCC. The NOTAM must follow 4-2-1 b 1-2, including
  1. ARTCC designator/location (mandatory) followed by the state(s) abbreviation; for example: ZDC VA.
  2. Keyword “AIRSPACE.”
  3. City/Location(s), State(s) for each area; for example: Detroit, MI Ann Arbor, MI..; Beale AFB, CA..; Libby AAF, AZ..; Hibbing, MN..; Fargo, ND.
  4. Description of activity: “TEMPORARY FLIGHT RESTRICTIONS.”
  5. Plain language effective date; for example, February 26, 2014 LOCAL (applicable to 14 CFR Sections 91.141 and 99.7 only).
  6. The phrase “PURSUANT TO TITLE 14 CFR SECTION 9X.XXX…(the appropriate paragraph and sub-paragraph number) (plain language text, as needed). Include the phrase “PURSUANT TO 49 USC (section)…” as required for 14 CFR Sections 91.141 and 99.7 only.
  7. Description of area or areas impacted; each area will contain:
  1. Stated as “WI AN AREA DEFINED AS…” and if appropriate “…TO POINT OF ORIGIN.” The area is defined as a nautical mile radius of a latitude/longitude, or an area defined by latitude/longitude or fixes. As necessary, include an alternate description as a fix/radial/distance in parentheses, to help clarify the location. For example, X (alt X) TO Y (alt Y) TO Z (alt Z).
  2. Lower limit then upper limit, or height, (when needed). Limits must be specified, as:
  1. For SFC, or 1 to 17,999FT with the unit of measurement (AGL or MSL). 1275FT AGL, 10500FT MSL.
  2. For 18,000FT and above, express in flight levels (FL), FL180, FL250, FL850, or UNL (altitudes greater than 99,900).
  3. Heights AGL may be added, for example, SFC-450FT AGL.
  1. Schedule of individual area, if needed. For example, EFFECTIVE YY02271900 UTC (1400 LOCAL 2/27/YY) UNTIL YY02280200 UTC (2100 LOCAL 2/27/YY). If a daily (or MON WED FRI) time is required, DLY 1900-0200 (1400-2100 LOCAL).


Repeat 7 (a)-(c), as necessary, for each defined area.

  1. Reason or purpose (when needed).
  2. The FAA coordination facility and commercial telephone number.
  3. Remarks (when needed). Include other information that is required or considered to be important to the pilot. Do not use the 1-800-WX-BRIEF telephone number for the flight service stations.
  4. Start of Activity/End of Validity.
  1. Flight restrictions in the proximity of the President or other parties (14 CFR Section 91.141) or Special Security Instructions (14 CFR Section 99.7) will be issued by System Operations Services, System Operations Security, and System Operations Support Center (SOSC). Operational requirements may necessitate a change in format to Presidential and Special Security Instructions TFRs at any time.
  1. Multiple areas may be specified in one NOTAM when the areas are in the same ARTCC airspace.
  2. The requirement for one effective period per NOTAM is waived for NOTAMs advertising flight restrictions in the proximity of the President or other parties. See paragraph 4-1-1.

When an air defense emergency is declared and Emergency Security Control of Air Traffic (ESCAT) has been implemented, an FDC NOTAM will be issued in accordance with procedures in FAA Order JO 7610.4, Special Operations, Chapter 6, Emergency Security Control of Air Traffic. NOTAMs advertising an air defense emergency must use accountability FDC, location identifier FDC, and be preceded by keyword “SECURITY.”


FAA Order JO 7610.4, Chapter 6, Emergency Security Control of Air Traffic (ESCAT), and Appendix 17, Emergency Security Control of Air Traffic (ESCAT).


When special data NOTAMs must be issued (for example, Department of State information and special air traffic programs for national security, aviation security, and law enforcement, etc.), an FDC NOTAM is issued by the USNOF using the keyword “SECURITY.” Issue the NOTAM with PERM instead of a cancellation date and cancel the NOTAM only at the request of the originating office, System Operations Security.


See information on use of the System Operations Security KICZ Accountability/Location Code for United States International Security NOTAMs in Chapter 8.


The service area office where the laser activity will occur must notify the USNOF via telephone (888) 876-6826 or email (9-AWA-NOTAMS@FAA.GOV) within 7 days of a proposed activity. Additionally, service area offices, when coordinated with their respective ATC facilities, may delegate notification responsibility. The USNOF will transmit the appropriate FDC NOTAM. If the event is canceled prior to the scheduled ending date/time, the service area office or their designee must notify the USNOF to cancel the NOTAM.

Follow 4-2-1 b 1-2, including:

  1. ARTCC designator (mandatory) followed by the state abbreviation.
  2. Keyword “AIRSPACE.”
  3. City/state.
  4. Description of activity; for example, “LASER LGT ACT.”
  5. Description of area impacted; describe the area using radius and latitude/longitude.
  6. Alternate description. In parentheses, specify area impacted in reference to a fix/radial/DME.
  7. Altitudes impacted. Must include lower limit and upper limit.
  8. Follow 4-2-1 b 11-14 to complete the NOTAM.
  1. The NS transmits a list of FDC NOTAM numbers issued during the previous 24 hours. The NS transmits the list between 1715 and 1745 UTC.

Upon issuance, all FDC NOTAMs are given all circuit distribution and are stored in the NS. See Appendix E for further information.