Radar Vectors
FAA Order Cancelled Issued Nov 14, 2023 AJV-A 162 pages Copy saved Nov 18, 2026

Order 7930.2T Notice to Airmen (NOTAM)

This order prescribes direction used to format and distribute information regarding unanticipated or temporary changes to services, components of, or hazards in, the National Airspace System (NAS). Authorized personnel assigned to facilities that collect, originate, and/or disseminate NOTAMs must be familiar with the provisions of this order that pertain to their operational responsibilities. The Notice to Airmen (NOTAM) system does not advertise published or charted data and information.

This document is cancelled. Cancelled by 7930.2U. Check the official source before relying on it.

Official source ↗ Open PDF

FAA Order 7930.2T, Notice to Air Missions (NOTAM), effective December…

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

ORDER

7930.2T

National Policy Effective Date: December 14, 2023

SUBJ: Notice to Air Missions (NOTAM)

This order prescribes direction used to format and distribute information regarding unanticipated or temporary changes to services, components of, or hazards in, the National Airspace System (NAS). Authorized personnel assigned to facilities that collect, originate, and/or disseminate NOTAMs must be familiar with the provisions of this order that pertain to their operational responsibilities. The Notice to Air Missions (NOTAM) system does not advertise published or charted data and information.

Digitally signed by NATASHA A. NATASHA A. DURKINS

Date: 2023.11.13 DURKINS 16:52:53 -05'00' Natasha A. Durkins Vice President, Mission Support Services Air Traffic Organization

Distribution: Electronic Initiated By: AJV-0 Vice President, Mission Support Services

FAA Order 7930.2T, Notice to Air Missions (NOTAM), effective December… › Explanation of Changes - Basic

Notice to Air Missions (NOTAM)

Explanation of Changes

Effective: December 14, 2023

a. SUBJ: Notices to Air Missions (NOTAM)

1−3−8. RESPONSIBILITY HIERARCHY

This change cancels and incorporates GENOT N 7930.113 (RWA 22/43) by deleting paragraph 1−3−8 in its entirety. This DCP also serves to correct the subject title to “Notice to Air Missions (NOTAM).”

b. 1−4−6. DEFINITIONS

As a result of the Chart Supplement Modernization Initiative, the Chart Supplement U.S. definition was revised and new definitions were created for Chart Supplement, Chart Supplement Alaska and Chart Supplement Pacific.

c. 5−5−1. GENERAL

5−5−3. HOURS OF OPERATION Appendix A. Examples

This change amends paragraph 5−5−1 to update the NOTAM example only; FIG 5−5−1 and the remainder of the paragraph are unchanged. This notice also amends paragraph 5−5−3, which clarifies NOTAM criteria for changes in the hours of operation of an air traffic control facility, and Appendix A, section 5−5−3, NOTAM examples.

d. Editorial Changes

Editorial changes include updating the distribution, subscription, and purchase information in Chapter 1, Section 1, and in the Distribution paragraph on the Change cover pages.

e. Entire Publication

Additional editorial/format changes were made where necessary. Revision bars were not used because of the insignificant nature of these changes.

Briefing Guide BG−1

Appendices

Comments/Corrections

Comments or corrections concerning this publication may be submitted on this form and submitted electronically to: 9−AJV−P−HQ−[email protected]

Notice to Editor

The following comments/corrections are submitted concerning the information contained in: Paragraph number Title Page Dated …

Name Street City State Zip

Comments/Corrections

Table of Contents

Table of Contents

Chapter 1. General

Section 1. Introduction

Paragraph Page 1-1-1. PURPOSE … 1-1-1 1-1-2. AUDIENCE … 1-1-1 1-1-3. WHERE TO FIND THIS ORDER … 1-1-1 1-1-4. CANCELLATION … 1-1-1 1-1-5. EXPLANATION OF CHANGES … 1-1-1 1-1-6. DISTRIBUTION … 1-1-1 1-1-7. RECOMMENDATION FOR PROCEDURAL CHANGES … 1-1-1 1-1-8. EFFECTIVE DATE … 1-1-2 1-1-9. RELATED PUBLICATIONS … 1-1-2

Section 2. Scope

1-2-1. PURPOSE … 1-2-1 1-2-2. PROCEDURAL APPLICATIONS … 1-2-2 1-2-3. AVOIDANCE OF DUPLICATION … 1-2-2

Section 3. Accountable Organizations

1-3-1. AIR TRAFFIC ORGANIZATION (ATO) … 1-3-1 1-3-2. TECHNICAL OPERATIONS … 1-3-2 1-3-3. FLIGHT STANDARDS SERVICE … 1-3-3 1-3-4. OFFICE OF AIRPORT SAFETY AND STANDARDS … 1-3-3 1-3-5. AIRPORT MANAGEMENT … 1-3-3 1-3-6. NON-FEDERAL FACILITIES … 1-3-3 1-3-7. DEPARTMENT OF DEFENSE AIRFIELD MANAGEMENT … 1-3-4

Section 4. Terms of Reference

1-4-1. WORD USE IN THIS ORDER … 1-4-1 1-4-2. NOTES … 1-4-1 1-4-3. EXAMPLES … 1-4-1 1-4-4. REFERENCES … 1-4-1 1-4-5. MANUAL CHANGES … 1-4-1 1-4-6. DEFINITIONS … 1-4-1

Chapter 2. Aeronautical Information Services

Section 1. Aeronautical Information System

2-1-1. GENERAL … 2-1-1 2-1-2. DISSEMINATION OF AIRMEN INFORMATION … 2-1-1 2-1-3. PUBLICATION CRITERIA … 2-1-1 2-1-4. DOMESTIC NOTICES AND INTERNATIONAL NOTICES … 2-1-2 2-1-5. CHART/PUBLICATION ERRORS OR OMISSIONS … 2-1-2 2-1-6. FORWARDING DATA … 2-1-2

Table of Contents i

Paragraph Page 2-1-7. ADDRESSING CORRESPONDENCE … 2-1-3 2-1-8. THE NATIONAL FLIGHT DATA DIGEST (NFDD) … 2-1-3 2-1-9. COMPUTER PRINTOUTS … 2-1-3

Chapter 3. General Operating Procedures

Section 1. General

3-1-1. NOTAM RESPONSIBILITIES … 3-1-1 3-1-2. FDC PRESIDENTIAL, SPECIAL SECURITY INSTRUCTIONS, OR EMERGENCY AIR TRAFFIC RULES TFRs … 3-1-1 3-1-3. MILITARY NOTAMs … 3-1-2 3-1-4. PERMANENT (PERM) NOTAM PROCESS … 3-1-2

Section 2. Coordination

3-2-1. COORDINATION WITH OTHER FACILITIES … 3-2-1 3-2-2. FILING NOTAM INFORMATION WITH FSSs … 3-2-1 3-2-3. NOTAM LOG … 3-2-1 3-2-4. PASSING NOTAM DATA BY PART-TIME FSS FACILITIES … 3-2-1

Section 3. Use of Terms

3-3-1. USE OF CONTRACTIONS AND ABBREVIATIONS … 3-3-1 3-3-2. EXPRESSION OF TIME IN THE NOTAM SYSTEM … 3-3-1 3-3-3. UNITS OF MEASUREMENT … 3-3-1 3-3-4. USE OF VIRGULE (/) … 3-3-2 3-3-5. RUNWAY IDENTIFICATION … 3-3-2 3-3-6. TAXIWAY IDENTIFICATION … 3-3-2 3-3-7. APRON IDENTIFICATION … 3-3-3 3-3-8. STANDARD NOTAM PHRASES … 3-3-4 3-3-9. CARDINAL DIRECTIONS … 3-3-4

Chapter 4. NOTAM D Procedures

Section 1. General

4-1-1. U.S. NOTAM OFFICE RELATIONSHIPS … 4-1-1

Section 2. Preparing NOTAMs for Dissemination

4-2-1. NOTAM COMPOSITION … 4-2-1 4-2-2. NOTAM ACCOUNTABILITY … 4-2-3

Section 3. Canceling/Extending NOTAMs

4-3-1. EXTENDING NOTAM VALIDITY … 4-3-1 4-3-2. CANCELLATION OF NOTAMs … 4-3-1 4-3-3. CANCELLING PUBLISHED NOTAM DATA … 4-3-1

Table of Contents ii

Chapter 5. NOTAM Criteria

Section 1. Movement Area NOTAMs

Paragraph Page 5-1-1. ORIGINATORS OF AERODROME NOTAMs … 5-1-1 5-1-2. HANDLING REPORTED AERODROME CONDITIONS … 5-1-1 5-1-3. MOVEMENT AREA INFORMATION … 5-1-1 5-1-4. FIELD CONDITIONS (FICON) REPORTING … 5-1-3 5-1-5. AERODROME FACILITIES … 5-1-11 5-1-6. WORK IN PROGRESS … 5-1-12

Section 2. Lighting Aid and Obstruction NOTAMs

5-2-1. LIGHTING AIDS … 5-2-1 5-2-2. OBSTACLES … 5-2-2

Section 3. NAVAID NOTAMs

5-3-1. GENERAL … 5-3-1 5-3-2. REPORTING NAVAID MALFUNCTIONS … 5-3-1 5-3-3. UNPROGRAMMED EXTENDED SHUTDOWNS … 5-3-1 5-3-4. NAVAID MAINTENANCE SHUTDOWNS … 5-3-1 5-3-5. UNMONITORED NAVAIDs … 5-3-1 5-3-6. INSTRUMENT LANDING SYSTEM STATUS … 5-3-1 5-3-7. NAVAID CONDITIONS … 5-3-2 5-3-8. SATELLITE BASED SYSTEMS … 5-3-7 5-3-9. HOURS OF OPERATION … 5-3-8

Section 4. Communications NOTAMs

5-4-1. GENERAL … 5-4-1 5-4-2. REPORTING COMMUNICATIONS OUTLET MALFUNCTIONS … 5-4-1 5-4-3. COMMUNICATION OUTLET CONDITIONS … 5-4-1

Section 5. Services NOTAMs

5-5-1. GENERAL … 5-5-1 5-5-2. CHANGES TO PUBLISHED SERVICES … 5-5-1 5-5-3. HOURS OF OPERATION … 5-5-1 5-5-4. WEATHER AND WEATHER REPORTING EQUIPMENT … 5-5-2 5-5-5. MICROBURST/WINDSHEAR DETECTION SYSTEM … 5-5-3 5-5-6. RADAR SERVICES … 5-5-3

Chapter 6. Airspace NOTAMs

Section 1. Airspace

6-1-1. AIRSPACE NOTAM FORMAT … 6-1-1 6-1-2. SPECIAL ACTIVITY AIRSPACE (SAA) … 6-1-1 6-1-3. AIRSPACE AND ALTITUDE RESERVATIONS … 6-1-2 6-1-4. SPECIAL AERIAL REFUELING … 6-1-2 6-1-5. OTHER AIRSPACE NOTAMS … 6-1-3 6-1-6. SURFACE AREA AIRSPACE … 6-1-4

Table of Contents iii

Paragraph Page 6-1-7. AREA IMPACTED TABLES … 6-1-4

Chapter 7. FDC NOTAMs

Section 1. Transmitting FDC NOTAM Data

7-1-1. GENERAL … 7-1-1 7-1-2. TEMPORARY OR PERMANENT FDC NOTAMS … 7-1-1 7-1-3. INSTRUMENT IFR FLIGHT PROCEDURES … 7-1-2 7-1-4. HIGH BAROMETRIC PRESSURE WARNING … 7-1-6 7-1-5. TEMPORARY FLIGHT RESTRICTIONS … 7-1-6 7-1-6. AIR DEFENSE EMERGENCY … 7-1-7 7-1-7. SPECIAL DATA … 7-1-7 7-1-8. LASER LIGHT ACTIVITY … 7-1-7 7-1-9. FDC NOTAM LIST … 7-1-7 7-1-10. RETRIEVING FDC NOTAMs … 7-1-8

Section 2. Cancellation/Expiration

7-2-1. FDC NOTAM EXPIRATION/CANCELLATION … 7-2-1

Chapter 8. International NOTAMs

Section 1. General Procedures

8-1-1. INTERNATIONAL NOTAMs … 8-1-1 8-1-2. INTERNATIONAL NOTAM DATA FORMAT … 8-1-1

Section 2. Procedures For Canadian NOTAMs

8-2-1. REQUEST FOR CANADIAN NOTAMs FROM THE CANADIAN NOTAM SYSTEM … 8-2-1

Appendices

Appendix A. Examples … Appendix A-1 Appendix B. International NOTAM (Q) Codes … Appendix B-1 Appendix C. ICAO Difference for the United States … Appendix C-1 Appendix D. Miscellaneous Functions … Appendix D-1 Appendix E. Computer Functions … Appendix E-1 Appendix F. Radiosonde/Unmanned Free Balloon Flights … Appendix F-1 Appendix G. Technical Operations Reference Chart … Appendix G-1

Index

Index … I-1

Table of Contents iv

Chapter 1. General › Section 1. Introduction

I

I

I

Chapter 1. General

Section 1. Introduction

1−1−1. PURPOSE

This order prescribes direction used to format and distribute information regarding unanticipated or temporary changes to services, components of, or hazards in, the National Airspace System (NAS). The NOTAM System does not advertise published or charted data and information. Originators of aeronautical information are expected to inform the Aeronautical Data Team in sufficient time before the effective dates of changes to permit publishing of aeronautical data on the various charts or in the appropriate publications. When time does not allow for publication of a change or an outage and if the subject matter meets NOTAM criteria, issue a NOTAM until published.

1−1−2. AUDIENCE

Audience for this order is any office responsible for originating NOTAMs and those who use aeronautical information.

1−1−3. WHERE TO FIND THIS ORDER

This order is available on the FAA’s Air Traffic Plans and Publications website at http://faa.gov/air_traffic/publications and Orders & Notices website at https://www.faa.gov/regulations_policies/orders_notices/.

1−1−4. CANCELLATION

FAA Order JO 7930.2S, Notice to Air Missions (NOTAM) dated December 2, 2021 and all changes to it are canceled.

1−1−5. EXPLANATION OF CHANGES

The significant changes to the basic order will be published and included in the Explanation of Change page(s). It is advisable to retain the page(s) throughout the duration of the basic order. If further information is desired, direct questions through the appropriate facility/service area staff to System Operations Services, Flight Services, U.S. NOTAM Governance and Operations Group.

1−1−6. DISTRIBUTION

This order is distributed electronically to all who subscribe to receive email notifications through the FAA’s website. All organizations are responsible for viewing, downloading, and subscribing to receive email notifications when changes occur to this order. Subscriptions to air traffic directives can be made through the Air Traffic Plans and Publications website at https://www.faa.gov/air_traffic/publications/ or directly via the following link: https://public.govdelivery.com/accounts/USAFAA/subscriber/new?topic_id=USAFAA_39.

1−1−7. RECOMMENDATION FOR PROCEDURAL CHANGES

a. The contents of this order will be periodically reviewed and updated, as required by National Airspace Data Interchange Network (NADIN) or NAS Messaging Replacement (NMR), General Notices (GENOTs), and order changes.

b. Any changes to this order must be submitted to the Policy Directorate Correspondence Mailbox at 9−AJV−P−HQ−[email protected].

Introduction 1−1−1

I

I

1. Personnel should submit recommended changes in procedures to facility management.

2. Recommendations from other sources should be submitted through appropriate FAA, military, or industry/user channels.

1−1−8. EFFECTIVE DATE

This order is effective December 14, 2023.

1−1−9. RELATED PUBLICATIONS

Military units issue NOTAMs pertaining to their mission based on the guidelines set forth in Air Force Instruction Interservice Publication 11-208/AR 95-10/OPNAVINST 3721.20, DoD Notice to Airmen (NOTAM) System.

FAA Order 5010.4, Airport Data and Information Management

FAA Order JO 7110.10, Flight Services

FAA Order JO 7210.3, Facility Operation and Administration

FAA Order JO 7340.2, Contractions

FAA Order JO 7350.9, Location Identifiers

FAA Order JO 7400.2, Procedures for Handling Airspace Matters

FAA Order JO 7400.10, Special Use Airspace

FAA Order JO 7610.4, Sensitive Procedures and Requirements for Special Operations

FAA Order JO 7610.14, Non−Sensitive Procedures and Requirements for Special Operations

FAA Order 8260.19, Flight Procedures and Airspace

FAA Order 8400.13, Procedures for the Evaluation and Approval of Facilities for Special Authorization Category I Operations and All Category II and III Operations

Technical Operations

− FAA Order 6000.15, General Maintenance Handbook for NAS Facilities

− FAA Order 8200.1, U.S. Standard Flight Inspection Manual

− FAA Order 6750.24, Instrument Landing System and Ancillary Electronic Component Configuration and Performance Requirements

14 CFR Parts

− 77, Safe, Efficient Use, and Preservation of the Navigable Airspace

− 91, General Operating and Flight Rules

− 139, Certification of Airports

− 157, Notice of Construction, Alteration, Activation and Deactivation of Airports

− 171, Non-Federal Navigation Facilities

Advisory Circular (AC) 99−1, Emergency Security Control of Air Traffic (ESCAT)

Advisory Circular (AC) 150/5200−28, Notices to Air Missions (NOTAMs) for Airport Operators

Advisory Circular (AC) 150/5200−30, Airport Field Condition Assessments and Winter Operations Safety

Advisory Circular (AC) 150/5300−18B, General Guidance and Specifications for Submission of Aeronautical Surveys to NGS: Field Data Collection and Geographic Information System (GIS) Standards

Introduction 1−1−2

Advisory Circular (AC) 150/5300−13, Airport Design

ICAO Annex 15, Aeronautical Information Services

ICAO Doc 7383, Aeronautical Information Services Provided by States

ICAO Doc 8400, ICAO Abbreviations and Codes

ICAO Doc 8126, Aeronautical Information Services Manual

ICAO Doc 10066, Procedures for Air Navigation Services—Aeronautical Information Management

Pilot/Controller Glossary

Introduction 1−1−3

Chapter 1. General › Section 2. Scope

Section 2. Scope

1−2−1. PURPOSE

Authorized personnel assigned to facilities that collect, originate, and/or disseminate NOTAMs must be familiar with the provisions of this order that pertain to their operational responsibilities.

a. The United States NOTAM Office (USNOF) is the final authority on NOTAM formatting. Candidate NOTAMs submitted through the NOTAM System (NS) must be in the proper format. To ensure NOTAMs are issued in accordance with NOTAM policy, NOTAM originators must comply with USNOF personnel directions.

b. All NOTAMs will be processed, stored, and distributed by the NS. In order to ensure that NOTAMs are processed and distributed properly, data for transmission must be coded as prescribed in this order.

c. The USNOF ensures the integrity of the NS by managing it for compliance 24/7.

d. NOTAMs must have one of the following keywords as the first part of the text. A keyword is used to make it easier to sort and locate the specific data needed: RWY, TWY, APRON, AD, OBST, NAV, COM, SVC, AIRSPACE, ODP, SID, STAR, CHART, DATA, DVA, IAP, VFP, ROUTE, SPECIAL or SECURITY.

NOTE− Examples of keywords (RWY, TWY, APRON, AD, OBST, NAV, COM, SVC) are shown in Chapter 5; AIRSPACE in Chapter 6; (IAP, ODP, SID, STAR, DVA, ROUTE, and SPECIAL) relating to instrument flight procedures in Chapter 7.

1. RWY (Runway). Keyword used to describe a temporary change or hazard associated with landing and takeoff surfaces to include runway lighting, markings, signage, and other airport services or attributes associated with a specific runway.

2. TWY (Taxiway). Keyword used to describe a temporary change or hazard associated with a taxiway, taxiway lighting, markings, helipads, signage and other attributes associated with a specific taxiway.

3. APRON (Apron/Ramp). Keyword used to describe a temporary change or hazard associated with an apron, ramp, or taxilane, lighting, markings, helipad, signage and other attributes associated with a specific apron.

4. AD (Aerodrome). Keyword used to describe a temporary change or hazard or potential hazard on or within 5 statute miles of an airport, heliport, or maneuvering area that is not associated with a specific movement area surface. Such hazards may include, (but are not limited to), aerodrome closures, lighting not associated with a specific movement area surface, aerodrome services (fuel, customs, ARFF), helicopter platforms, meteorological equipment (wind indicators) or services, and wildlife hazards.

5. OBST (Obstructions). Keyword used to describe a temporary change or hazard. Such hazards may include, (but are not limited to), moored balloon, kite, tower, crane, stack, obstruction, wind turbine, obstruction lighting outage, obstruction status, or telecommunication tower light outage.

6. NAV (Navigation Aids). Keyword used to describe a temporary change or hazard caused by the changes in the status of ground−based radio navigational aids and Global Navigation Satellite Systems (GNSS) (except for area navigation (RNAV) approach anomalies).

7. COM (Communications). Keyword used to describe a temporary change or hazard caused by or related to communication outlets and air−to−ground frequencies due to commissioning, decommissioning, outage, or unavailability.

8. SVC (Services). Keyword used to describe a temporary change or hazard associated with change in service levels, such as operating hours, air traffic management services, or airport services. The ICAO contraction for service (SER) is an allowable contraction in the body of the NOTAM. “SVC” is only used as the keyword contraction for Service NOTAMs.

Scope 1−2−1

9. AIRSPACE (Airspace). Keyword used to describe an airspace restriction or activity warning which impacts, restricts, or precludes use of airspace. Such restrictions and activities may include, (but are not limited to), parachute jumping, unmanned aircraft, etc.

10. ODP (Obstacle Departure Procedure). Keyword used when a NOTAM applies to a textual or graphic obstacle departure procedure.

11. SID (Standard Instrument Departure). Keyword used when a NOTAM applies to a published standard instrument departure.

12. STAR (Standard Terminal Arrival). Keyword used when a NOTAM applies to a published standard terminal arrival.

13. CHART (Chart). Keyword used to describe a U.S. Government chart correction, followed by name of chart and word “CORRECT” that becomes effective before the next publication cycle.

14. DATA (Data). Keyword used to describe a temporary change or hazard associated with a data set change followed by the name of the data set to be changed; for example, U.S. DOD DAFIF, DACS, or NFD.

15. IAP (Instrument Approach Procedure). Keyword used when a NOTAM applies to a published instrument approach procedure.

16. VFP (Visual Flight Procedure). Keyword used when a NOTAM applies to visual flight procedures such as Charted Visual Flight Procedure and RNAV Visual Flight Procedure.

17. DVA (Diverse Vector Areas). Keyword used to describe a temporary change or hazard associated with a Diverse Vector Area.

18. ROUTE (Route). Keyword used to describe a temporary change or hazard or change associated with published Air Traffic Services (ATS) routes and related information.

19. SPECIAL (Special). Keyword used when a NOTAM applies to a special instrument flight procedure.

20. SECURITY (Security). Keyword used for Department of State advisories, Special Federal Aviation Regulations (SFARs), advisories of national emergency, national security actions, special security instructions, Air Defense Identification Zone (ADIZ) procedures.

NOTE− Keyword SECURITY is not used for NOTAMs that describe a defined restricted area or TFR. Such NOTAMs would use keyword AIRSPACE.

e. (U) – Unverified. (U) is used preceding a keyword as described in paragraph 5−1−2.

f. The United States Department of Defense (DOD) will append the keywords IAP, SPECIAL, ODP, SID, and STAR with “U. S. DOD” to indicate that a published procedure is for military use only (not for civil use). For example, STAR U. S. DOD, SID U. S. DOD, IAP U. S. DOD.

1−2−2. PROCEDURAL APPLICATIONS

Apply the procedures in this order except when other procedures are contained in a Letter of Agreement or other appropriate FAA documents, provided they only supplement this order and that any standards they specify are not less than those in this order. FAA Order JO 7210.3, Facility Operation and Administration, contains administrative procedures for developing and executing those letters and documents.

1−2−3. AVOIDANCE OF DUPLICATION

Before issuing a NOTAM on any NOTAM criteria data, check all appropriate charts and publications to assure the information does not duplicate the published data. Do not issue a NOTAM on information that duplicates published data unless a NOTAM is required by a Certificate of Waiver or Authorization from Title 14, Code of Federal Regulations (CFR) issued by the FAA.

1−2−2 Scope

Chapter 1. General › Section 3. Accountable Organizations

-

Section 3. Accountable Organizations

1−3−1. AIR TRAFFIC ORGANIZATION (ATO)

a. All air traffic organization, Federal Contract Tower (FCT), and Federal Contract Flight Service Station (FCFSS) employees, regardless of position, must immediately report any situation or condition considered hazardous to flight to an air traffic facility for appropriate action.

NOTE− Situations that present an immediate hazard should be reported to the air traffic control (ATC) facility most concerned. Other situations should be reported on a first priority basis to the flight service station or appropriate accountable organization.

b. Air traffic organization, FCT, and FCFSS personnel must accept all aeronautical information regardless of source or subject matter, provided the occurrence is no more than seven days in the future. Obtain the name, title (if appropriate), address, and telephone number of the person furnishing the information and forward all data to the appropriate FSS for NOTAM issuance, if appropriate.

NOTE− Forwarding the NOTAM data to the tie−in FSS does not relieve the forwarding facility from the responsibility of coordinating the information with other affected ATC facilities.

c. The party that originates the NOTAM on behalf of the accountable organization is responsible for the accuracy, origination, and cancellation of the NOTAM. FSS personnel receiving NOTAM information that requires action by another FSS must forward the information to that FSS for appropriate action.

d. The certified source is responsible for the correct classification and format of the NOTAM and for ensuring that facilities affected by the NOTAM are aware of the new NOTAM.

e. FSS specialists are responsible for issuing NOTAMs that are not covered in any example in FAA Order JO 7930.2. If, after consulting with your management, a format cannot be determined, have management contact USNOF for assistance.

f. System Operations Services, Flight Services, has the responsibility to ensure that data submitted complies with the policies, criteria, and formats contained in this order. This responsibility is delegated to the U.S. NOTAM Governance and Operations Group.

g. Service Areas originate NOTAMs for certain FDC criteria, including Laser activities and Temporary Flight Restrictions that are issued by the USNOF through NS.

h. Mission Support Services, Aeronautical Information Services (AIS) is responsible for originating Flight Data Center (FDC) NOTAMs for revisions to standard instrument approach procedures (SIAP), air traffic service (ATS) routes, textual and graphic departure procedures (both ODPs and SIDs), charting (CHART) corrections, and special instrument flight procedures. AIS may originate NOTAMs regarding navigational aid (NAVAID) restrictions in accordance with FAA Order 8200.1, United States Standard Flight Inspection Manual. AIS is responsible for:

1. Formulating Instrument Flight Procedures (IFP) and ATS route NOTAMs for procedures for which they have responsibility.

2. Formulating FDC PERM NOTAMs used to correct aeronautical chart printing and compilation errors related to all U.S. Government aeronautical charting products.

3. Designating an office to develop specific internal guidance for NOTAM preparation, quality control, transmittal, cancellation, and follow−up actions for FDC NOTAMs issued by AIS. This guidance must be developed in concert with the Aeronautical Data Team and the USNOF. As a minimum, the guidance must include the following:

(a) Procedures to ensure that the airport manager at the affected location is notified whenever possible.

Accountable Organizations 1−3−1

(b) Procedures to ensure all NOTAMs are reviewed for accuracy, completeness, content, etc. prior to submission.

(c) Procedures to ensure the Aeronautical Data Team is provided information copy of all NOTAMs and cancellations.

(d) Procedures to ensure non−FAA service providers are provided an information copy of all NOTAMs and cancellations at those locations non−FAA service providers are allowed. This will ensure non−FAA service providers are aware of the condition requiring the NOTAM.

4. The Aeronautical Data Team is responsible for ensuring a hard/electronic copy of each PERM NOTAM is stored with the current amendment and maintained in the procedures archive file.

i. Mission Support Services is responsible for the development of policy guidance regarding standard terminal arrival routes (STAR). STAR NOTAMs are initiated by the Air Route Traffic Control Center (ARTCC) in the airspace where the STAR originates.

j. System Operations Services, System Operations Security (AJR−2) will provide a list of long−term, security related Temporary Flight Restrictions (TFRs) to be charted on VFR Sectional and Terminal Area Charts. These will include select Title 14 Code of Federal Regulations (CFR) Part 99.7 (Special Security Instructions), part 91.141 (Flight Restrictions in the Proximity of the Presidential and Other Parties), and Part 91.139 (Emergency Air Traffic Rules) security related TFRs of extended duration with fixed and unchanging boundaries. System Operations Security will provide Aeronautical Information Services with updates and revisions to these charted long−term, security related TFRs, as needed, to ensure the data published on the charts is current.

k. The U.S. NOTAM Governance Team is the FAA’s authoritative source for US NOTAM Policy, responsible for the maintenance, update, and publication of this order, which establishes national policy for the National Airspace System (NAS) NOTAM operations. Additionally, the team is comprised of NOTAM Subject Matter Experts for domestic and international NOTAMs. This ensures global harmonization with ICAO Annexes, Standards and Recommended Practices, and other documents. The team also provides policy guidance, oversight, and interpretations for consistent application of US NOTAM standards.

l. USNOF executes the operational compliance function. When operational personnel of the USNOF determine that NOTAM information submitted is not in compliance with the criteria or procedures as prescribed, they must call this to the attention of the transmitting party. The USNOF forwards NOTAM policy questions to the U.S. NOTAM Governance Team for decision−making in consultation with other interested program offices. The USNOF is responsible for operating the NOTAM system. USNOF originates NOTAMs, as needed. (See paragraph 4−1−1, National NOTAM Office Relationships for more detail)

NOTE− NOTAM office phone numbers: (888) 876−6826; (540) 422−4262.

1−3−2. TECHNICAL OPERATIONS

a. Operations Control Center (OCC) and Service Operations Center (SOC).

The Technical Operations Services, Operations Center manager, or representative, is responsible for:

1. Originating and canceling NOTAM information for shutdown, restoration, or any condition that affects the operations of NAVAIDs, frequencies, or other electronic aids that affect safety of flight. This includes forwarding data of programmed changes in the NAS, such as frequency changes, commissioning/ decommissioning, etc.

2. Coordinating with appropriate air traffic facilities prior to shutdown or changes that affect safety of flight.

3. When possible, approval should be obtained sufficiently in advance of the proposed shutdown time to allow dissemination of a NOTAM at least 5 hours before a shutdown will occur. A routine maintenance shutdown request must not be denied because of an inability to issue a NOTAM 5 hours in advance of the shutdown.

1−3−2 Accountable Organizations

b. Aircraft Operations Group, Flight Inspection Team

Flight Inspection Services under FAA Order 8200.1, United States Standard Flight Inspection Manual, initiate NOTAMs regarding radio and lighting NAVAID restrictions. Facility classification based on flight inspection results is the responsibility of the flight inspector.

REFERENCE− FAA Order 5010.4, Airport Safety Data Program, and 14 CFR Parts 139 and 157.

1−3−3. FLIGHT STANDARDS SERVICE

a. Flight Technologies and Procedures Division, AFS−400, is responsible for development of policy guidance and procedures for the origination, tracking, and cancellation of NOTAMs relating to instrument flight procedures. This policy applies to the following: SIAPs, ATS routes, textual and graphic ODPs, SIDs, and special instrument flight procedures (see paragraph 1−3−1 for procedures addressing STAR NOTAMs). AFS−400 is responsible for oversight of non−FAA service providers authorized to maintain SIAP and/or special instrument flight procedures. Maintenance includes issuance of FDC NOTAMs.

b. AFS−400 is responsible for coordinating non−FAA service provider NOTAM authority and access to the FAA NOTAM system with ATO Mission Support Services, Aeronautical Information Services. The division is also responsible for ensuring that specific guidance for NOTAM preparation, quality control, transmittal, cancellation, and follow−up actions are developed for NOTAMs applicable to public and Special IFPs developed by non−FAA service provider and not under the purview of AIS. As a minimum, the guidance must ensure the non−FAA service provider NOTAM originators include the following:

1. Procedures to ensure that all affected ARTCC facilities are provided notification of NOTAMs at the time of submission. The NOTAM issuing authority must also attempt to notify the airport manager at the affected location whenever possible.

2. Procedures to ensure all NOTAMs are reviewed for accuracy, completeness, content, etc. prior to submission.

3. Procedures to ensure the Aeronautical Data Team is provided an information copy of all NOTAMs and cancellations.

4. Procedures to ensure that AIS is aware of those locations where non−FAA service provider procedure development is allowed.

5. Procedures to ensure that AIS is provided an information copy of all NOTAMs and cancellations issued by other non−FAA service providers. This will ensure FAA procedure developers are aware of the condition requiring the NOTAM.

c. AFS−400 serves as the approval authority for requests that temporary NOTAMs be allowed to extend beyond the 224−day time frame.

1−3−4. OFFICE OF AIRPORT SAFETY AND STANDARDS

Though not an accountable organization, the Office of Airport Safety and Standards is responsible for enforcing the airport management responsibilities as outlined in the Code of Federal Regulations (CFR).

1−3−5. AIRPORT MANAGEMENT

Specific airport management responsibilities are outlined in 14 CFR Parts 139 and 157. Airport managers are required to abide by applicable provisions of these and pertinent regulations regardless of application of any procedure in this order.

1−3−6. NON−FEDERAL FACILITIES

a. NOTAMs on non−Federal facilities covered by FAA Order 6700.20, Non−Federal Navigation Aids, Air Traffic Control Facilities, and Automated Weather Systems are distributed through the FAA NOTAM system.

Accountable Organizations 1−3−3

I

REFERENCE− 14 CFR Part 171 outlines owner/operation responsibilities. b. NOTAMs on non−Federal facilities that are not part of the NAS are not distributed in the FAA NOTAM system. FSSs receiving data on these facilities must notify Aeronautical Information Services.

1−3−7. DEPARTMENT OF DEFENSE AIRFIELD MANAGEMENT

Specific military airport management responsibilities are outlined in Air Force Instruction Interservice Publication 11−208/AR 95−10/OPNAVINST 3721.20, DoD Notice to Air Missions (NOTAM) System.

1−3−4 Accountable Organizations

Chapter 1. General › Section 4. Terms of Reference

Section 4. Terms of Reference

1−4−1. WORD USE IN THIS ORDER

As used in this order:

a. “Must” means a procedure is mandatory.

b. “Should” means a procedure is recommended.

c. “May” or “need not” means a procedure is optional.

d. “Must not” means a procedure is prohibited.

e. Singular words include the plural.

f. Plural words include the singular.

g. Miles means nautical miles unless otherwise stated.

h. Feet means mean sea level unless otherwise stated.

1−4−2. NOTES

Statements of fact of an introductory or explanatory nature and relating to the use of directive material have been identified and worded as NOTE.

1−4−3. EXAMPLES

An illustration which serves to explain subject material is identified as an EXAMPLE which represents the format discussed in each section and is used as an aid to support policy. Not all components of the NAS will be illustrated with an example. The examples throughout Appendix A contain the keyword and the subject of the NOTAM. All other data is assumed from the NOTAM sentence structure and is eliminated from examples.

1−4−4. REFERENCES

When another paragraph of this order is referenced in the text, the referenced paragraph number will be printed out in full. When a paragraph is referenced in a Reference subparagraph, the referenced paragraph’s title, followed by its number, will be printed in regular type. When other documents and directives are referenced in a Reference subparagraph, the document/directive and the paragraph number will be printed in regular type. All references to other FAA orders reflect the current edition of the order.

1−4−5. MANUAL CHANGES

When revised, reprinted, or additional pages are issued, they will be marked as follows:

a. Each revised or additional page will show the change number and effective date of the change.

b. Vertical lines in the margin of the text will mark the location of substantive procedural, operational, or policy changes; that is, when material which affects the performance of duty is added, revised, or deleted.

1−4−6. DEFINITIONS

The terms below as used in this order are defined in this section.

a. Accountable Organization. The accountable organization is responsible for accurately reporting the condition considered to be a hazard or potential hazard to flight operations. Reporting the condition must be

Terms of Reference 1−4−1

accomplished by ensuring that procedures are developed to establish NOTAM origination and coordination responsibilities.

b. Accountability Location. This is the location identifier of the location in the NOTAM computer that keeps track of the NOTAM numbering.

c. Aeronautical Fixed Telecommunication Network (AFTN). This interface will be used to support the exchange of Aeronautical Fixed Telecommunications Network (AFTN) formatted messages between NADIN and a common set of external TCP/IP users utilizing the Communications, Flight Service and Weather Engineering Group’s (CFWG) Common Message Handling Protocol (CMHP).

d. Aeronautical Information. Any information concerning the establishment, condition, or change in any component (facility, service, or procedure of, or hazard) of the NAS. This information is published and/or disseminated by means of aeronautical charts, publications, and/or NOTAMs.

e. Airport Operating Certificate. A certificate issued by the FAA, pursuant to 14 CFR Part 139, to airports serving or expected to serve scheduled air carrier operations in aircraft with a seating capacity of more than thirty passengers. These airports are maintained and operated in accordance with an Airport Certification Manual (ACM) prepared by airport management and approved by the FAA.

f. Automatic Data Processing (ADP) Code. A computer code within the Aeronautical Fixed Telecommunication Network (AFTN) used to identify the start of a new NOTAM. The ADP equipment is programmed to accept and begin processing a NOTAM upon receipt of the ADP code, which is an exclamation point (!).

g. Certificated Airport. An airport certificated under 14 CFR Part 139. These airports are identified in the Chart Supplement.

h. Certified Source/NOTAM Originator. The party (e.g., airport, Tech Ops AIS/Service provider, FSS, etc.) who enters/submits a NOTAM to the NOTAM System (NS) on behalf of the accountable organization using an approved direct entry tool or interface.

i. Chart Supplement. A series of civil/military flight information publications issued by FAA every 56 days consisting of the Chart Supplement Alaska, Chart Supplement Pacific and Chart Supplement U.S.

1. Chart Supplement Alaska. A flight information publication designed for use with appropriate IFR or VFR charts which contains data on all airports, seaplane bases, and heliports open to the public including communications data, navigational facilities, airport diagrams, certain special notices, and non−regulatory procedures. Also included in this publication are selected entries needed to support the unique geographical operational conditions of Alaska. This publication is issued in one volume for the state of Alaska.

2. Chart Supplement Pacific. A flight information publication designed for use with appropriate IFR or VFR charts which contains data on all airports, seaplane bases, and heliports open to the public including communications data, navigational facilities, airport diagrams, certain special notices, and non−regulatory procedures. Also included in this are publication Instrument Approach Procedures (IAP), Departure Procedures (DP), and Standard Terminal Arrival (STAR) charts along with selected entries needed to support the unique geographical operational conditions of the Pacific Oceanic region. This publication is issued in one volume for the Hawaiian Islands and other selected Pacific Islands.

3. Chart Supplement U.S. A flight information publication designed for use with appropriate IFR or VFR charts that contains data on all airports, seaplane bases, and heliports open to the public including communications data, navigational facilities, airport diagrams, certain special notices, and non−regulatory procedures. This publication is issued for the conterminous U.S., Puerto Rico, and the Virgin Islands in seven volumes according to geographical area.

j. Distribution. Forwarding of NOTAM information from the NS to NADIN.

k. Fix/Radial/Distance (F/R/D). Is a VOR identifier followed by 3−digit degrees magnetic and minimum of a 3−digit distance in nautical miles with no spaces between characters (AML360020.1 would be 360−degree radial, 20.1 NM from AML VOR/DME).

Terms of Reference 1−4−2

l. Flight Data Center (FDC) NOTAM. The classification of NOTAMs containing flight information that is normally regulatory in nature including, but not limited to, changes to IFR charts, procedures, and airspace usage. FDC NOTAM numbers are assigned consecutively by the NS, beginning with 0001 each year. The year of issuance and the serial number are separated by a forward slash; for example, Y/1323.

m. International NOTAM. The classification of NOTAMs received from other counties and stored in the NS. These NOTAMs are numbered consecutively by accountability, location, and series beginning with S0001 each year, where S stands for a generic series a country may have. The NOTAM number and year of issuance are separated by a forward slash; for example, S0211/YY, S0002/YY.

n. Location Identifier. Used to designate an affected airport, air route traffic control center (ARTCC), or facility.

o. Military NOTAM. The classification of NOTAMs issued by the U.S. Air Force, Army, Marine Corps, Navy, and Coast Guard against navigational aids and airports. Military units issue NOTAMs pertaining to their bases and airspace based on the guidelines set forth in Air Force Instruction Interservice Publication 11−208/AR 95−10/OPNAVINST 3721.20, DoD Notice to Airmen (NOTAM) System. 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; for example, S0211/15, S0002/15.

p. Movement Area. The term Movement Area as used for the purpose of NOTAMs, include Runways, Taxiways, Ramps, Aprons, helipads, heliports and maneuvering areas.

q. NADIN. The National Airspace Data Interchange Network (NADIN), also referred to as NMR (NAS Messaging Replacement), Message Switch Network (MSN) receives, processes, and distributes domestic and international flight planning, flight movement, weather observation/forecast, NOTAM, and search and rescue messages between the NAS, commercial/general aviation, U.S. Government agencies, aviation information service providers, and international Civil Aviation Authorities.

r. NAVAID. Any visual or electronic device airborne or on the surface which provides point−to−point guidance information or position data to aircraft in flight.

s. NMR. NAS Messaging Replacement also known as NADIN.

t. NOTAM D. The classification of NOTAMs containing information concerning the establishment, condition, or change in any aeronautical facility, en route navigational aids, services, procedures, hazards and civil public−use airports listed in the Chart Supplement. NOTAM Ds are numbered consecutively each month by the NS starting with 001 for each accountability, for example: DAY 01/001 would be the first NOTAM in the month of January for Dayton Accountable Location.

u. NOTAM System. A safety−critical system that collects, maintains and distributes NOTAMs for the aviation community.

v. Out of Service/Unserviceable (U/S). When a piece of equipment, a NAVAID, a facility or a service is not operational, certified (if required) and immediately “available” for air traffic or public use.

w. Pointer NOTAM. NOTAM D issued to point to additional aeronautical information. When pointing to another NOTAM, use the affected facility/location of the original NOTAM. The keyword in the pointer NOTAM must match the keyword in the original NOTAM. If the NOTAM is pointing to a publication, choose the most appropriate keyword for the situation. For example, a pointer NOTAM at a specific airport is used to highlight or “point out” an FDC NOTAM, or additional aeronautical information from the Domestic Notices or Chart Supplement. At the request of an Air Traffic facility, a NOTAM originator, or as deemed necessary by FSS, issue Pointer NOTAMs to highlight events of significance. Pointer NOTAMs should be issued for, but are not limited to, TFRs, Airshows, Temporary SUA, major NAS system interruptions, etc.

x. Prior Permission Required (PPR) means prior permission required to have full operational use of a runway, taxiway, apron, or airport facility/service. Means of communication to the airport can be telephone and/or radio. If PPR and another exception are used in same NOTAM, the PPR should come first.

Terms of Reference 1−4−3

y. Radio Navigation Aid. As used in this policy, the word radio is added further describe those navigation aids such as ILS, LOC, VOR or other NAVAID that is used in assisting the pilot with approaches, departures, and enroute operations.

z. Supervisory Authority. The supervisory authority is the organization responsible for managing the regulatory standards for the particular hazard being advertised in a NOTAM. The supervisory authority establishes organizational responsibilities to include particular or potential hazards, time parameters for origination, cancellation, and/or duration of NOTAMs, and particularly, exceptions to the policies and procedures provided in this document. Each supervisory authority must ensure that the authoritative provider is notified of all offices to which accountable and certified source authority has been granted. The supervisory authority is responsible for ensuring compliance with this directive.

aa. Taxilanes (TXL). Designed for low speed and precise taxiing. Taxilanes usually provide access (to and) from taxiways (usually an apron taxiway) to (and from) aircraft parking positions and other terminal areas.

ab. Tie−In Station. A flight service station designated to provide prescribed services for civil, military, national and international facilities; for example, NOTAM purposes and flight information messages.

ac. Unusable. The NAVAID is not available for operational use because it may provide potentially unsafe or erroneous signals, or signals of unknown quality.

ad. Virgule (/). For US NOTAM purposes − a diagonal symbol used to separate similar alternatives.

ae. Visual Navigation Aid. As used in this policy, the word visual is added to further describe those navigation aids such as PAPI, ALS, VASI, etc., or any other lighting aid that is used in assisting the pilot with approaches or departures.

af. WMSCR. Weather Message Switching Center Replacement is one of the FAA’s gateway for the receipt and distribution of weather within the National Airspace System (NAS).

Terms of Reference 1−4−4

Chapter 2. Aeronautical Information Services › Section 1. Aeronautical Information System

Chapter 2. Aeronautical Information Services

Section 1. Aeronautical Information System

2−1−1. GENERAL

The system for disseminating aeronautical information is made up of two subsystems, the Aeronautical Information System (AIS) and the NOTAM System. The AIS consists of charts and publications. The NOTAM system is discussed in later paragraphs.

2−1−2. DISSEMINATION OF AIRMEN INFORMATION

Airmen information is disseminated by the following methods:

a. Aeronautical charts depicting permanent baseline data:

1. IFR Charts:

(a) Enroute High Altitude Conterminous U.S.

(b) Enroute Low Altitude Conterminous U.S.

(c) Alaska Charts

(d) Pacific Charts

2. U.S. Terminal Procedures:

(a) Departure Procedures

(b) Standard Terminal Arrivals (STARs)

(c) Standard Instrument Approach Procedures (SIAPs)

3. VFR Charts:

(a) Sectional Aeronautical Charts

(b) Terminal Area Charts

(c) Helicopter Route Charts

(d) Caribbean Charts

(e) Wall Planning Charts

b. Flight information publications outlining baseline data:

1. Domestic Notices and International Notices

2. U.S. Chart Supplement (formally Airport/Facility Directory)

3. Pacific Chart Supplement

4. Alaska Supplement

5. Aeronautical Information Manual (AIM)

2−1−3. PUBLICATION CRITERIA

The following conditions or categories of information should be forwarded to the Aeronautical Data Team for inclusion in the flight information publications and charts. Time critical delays, corrections, or changes to

Aeronautical Information System 2−1−1

previously published data that cannot be republished before occurrence must be issued as a NOTAM, providing they meet the criteria set forth in this order.

a. NAVAIDs. Commissioning, decommissioning, shutdown, restrictions, frequency changes, changes in monitoring status and monitoring facility used in the National Airspace System (NAS). NAVAID outage NOTAMs must remain active until the NAVAID is returned to service or, if being decommissioned, published as shut down or removed from all applicable publications.

b. Commissioning, decommissioning, changes in hours of operation of FAA air traffic control facilities.

c. Surface areas/airspace. Changes in hours of operations.

d. Remote Communication Outlets and Remote Communication Air Ground. Commissioning, decommissioning, changes in voice control or monitoring facility.

e. Weather reporting stations. Commissioning, decommissioning, failure, nonavailability or unreliable operations.

f. Public airports. Commissioning, decommissioning, openings, closings, and abandonment.

g. Airport Rescue Fire Fighting (ARFF) capability. Restrictions to air carrier operations.

h. Changes to runway identifiers, dimensions, threshold placements, and surface compositions.

i. NAS lighting systems. Commissioning, decommissioning, outages, change in classification or operation.

2−1−4. DOMESTIC NOTICES AND INTERNATIONAL NOTICES

Domestic Notices and International Notices are published by Mission Support Services, Policy, Publications and Administration. See Appendix D for further information.

2−1−5. CHART/PUBLICATION ERRORS OR OMISSIONS

a. Managers must review each edition of the Domestic Notices and International Notices, Chart Supplement, and other publications and charts to ensure that all required data is included and correct. Inform the Aeronautical Data Team promptly of errors or omissions in any publication or chart. Notification of errors in the Domestic Notices and International Notices should be sent to Mission Support Services, Policy, Publications and Administration via 9−ATOR−HQ−[email protected].

b. Managers must review all current NOTAMs issued by their facility on a quarterly basis for currency.

c. When NOTAMs are published, or more than 30 days old, contact the accountable organization for possible cancellation.

2−1−6. FORWARDING DATA

a. When notice is received of a temporary condition which is expected to be corrected before information can be published, issue a NOTAM if it meets criteria.

b. NOTAM or aeronautical information concerning an extended (more than 30 days) shutdown or closure affecting components of the NAS must be forwarded in advance of the occurrence to the Aeronautical Data Team. The Aeronautical Data Team must publish data received in accordance with existing policies, criteria, and publication cutoff deadlines. The schedule of publication cutoff dates is contained in the Chart Supplement.

c. Information received by the Aeronautical Data Team for publication that meets publication criteria and will be current on the effective date of the next available Chart Supplement publication or aeronautical chart will be published.

d. Refer questions and data changes to https://www.faa.gov/air_traffic/flight_info/aeronav/aero_data/.

2−1−2 Aeronautical Information System

2−1−7. ADDRESSING CORRESPONDENCE

Federal Aviation Administration Aeronautical Information Services address: Aeronautical Information Services 1305 East−West Highway SSMC4, Suite 4531 Silver Spring, MD 20910−3281

2−1−8. THE NATIONAL FLIGHT DATA DIGEST (NFDD)

The NFDD is used to transmit data from the Aeronautical Data Team to chart and publication producers. It may be used to update records. However, it must not be used as a basis to cancel NOTAMs.

2−1−9. COMPUTER PRINTOUTS

Computer printouts listing all navigational aids and public use civil landing areas by flight plan area may be obtained from Aeronautical Information Services.

Aeronautical Information System 2−1−3

Chapter 3. General Operating Procedures › Section 1. General

Chapter 3. General Operating Procedures

Section 1. General

3−1−1. NOTAM RESPONSIBILITIES

a. The certified source (NOTAM originator) that enters the NOTAM data is responsible for classifying, formatting, cancelling, and informing the controlling facility and other facilities/offices affected by the aid, service, or hazard contained in the new NOTAM. Flight Service Stations are exempt from the requirement to inform the controlling facility when an alternate means of coordination is approved by the Flight Service Safety and Operations Group, AJR−B1.

b. Any certified source that receives information is responsible for the accuracy, currency, and validity of the NOTAM. When a certified source receives information that is outside their area of responsibility, they will inform the accountable organization.

c. FSSs must accept all aeronautical information. Information obtained from other than authorized personnel must be confirmed before issuance. NOTAM data received from state inspectors or state contracted inspectors must be confirmed by airport managers or appropriate authority before issuance of NOTAMs except in case of data that presents an immediate hazard to aircraft operations. If a NOTAM is issued without confirmation, advise the airport manager as soon as possible. In case of conflict between airport management and the named state airport inspector, contact FAA regional airports personnel for resolution. Conditions requiring a NOTAM should be coordinated with the appropriate air traffic facilities.

REFERENCE− FAA Order 7930.2, Para 5−1−2, Handling Reported Aerodrome Conditions.

d. Tie−in Stations. The Flight Service Directorate must designate an FSS as tie−in point for NOTAM purposes for all facilities in the NAS. The facilities assigned should normally be within the confines of the FSS’s flight plan area. Letters of agreement between facilities or other agencies and the FSS should be executed to assure proper handling of NOTAMs.:

e. Inform the controlling facility of all Obstruction Light Outage NOTAMs that meet one of the following criteria:

1. The obstruction is located 6 NM or less from an airport.

2. The obstruction is more than 400 feet AGL.

3. Identified by the terminal facility as one not meeting the criteria stated in d1 or d2 above; however, has been deemed necessary for the safety of operations (for example, depicted on the radar video map).

f. A Domestic NOTAM will auto−reject if it is over 20 lines. Ensure the NOTAM meets AFTN capability prior to originating NOTAM.

g. When a NOTAM is rejected, it is not distributed. It will not be stored in the NOTAM master file, and it will not be available by request−reply. Error messages are not stored in the master file.

h. ARTCCs are responsible for forwarding FDC and special activity airspace (SAA) NOTAM information to the affected terminal facilities.

3−1−2. FDC PRESIDENTIAL, SPECIAL SECURITY INSTRUCTIONS, OR EMERGENCY AIR TRAFFIC RULES TFRs

See Appendix D for further information.

a. The NS must send NOTAMs referencing Title 14 CFR, Part 91, Section 139, Emergency Air Traffic Rules; Section 141, Flight Restrictions in the Proximity of the Presidential and Other Parties; Part 99, Section 7, Special

General 3−1−1

Security Instructions; and any revisions, modifications, or cancellations, directly to all flight service stations via NADIN (NMR) using the flight service group address of “KXXXAFSS.”

3−1−3. MILITARY NOTAMs

a. See Appendix D for further information regarding military NOTAMs/functions/facilities.

b. See Appendix E for further information with regard to retrieving military NOTAMs and service messages.

3−1−4. PERMANENT (PERM) NOTAM PROCESS

a. When a NOTAM is originated for a permanent change to published aeronautical information, “PERM” must be inserted in lieu of a ten−figure date−time group end of validity time. Prior to issuance of a PERM NOTAM, the accountable organization must demonstrate that the publication process has been initiated. The originator is required to enter a temporary NOTAM until they are able to confirm the initiation of the publication process.

b. To submit aeronautical data for publication, go to: https://www.faa.gov/air_traffic/flight_info/aeronav/aero_data/Submitting_Data/.

General 3−1−2

Chapter 3. General Operating Procedures › Section 2. Coordination

Section 2. Coordination

3−2−1. COORDINATION WITH OTHER FACILITIES

When a shutdown or an outage/closure of a component of the NAS will affect another facility’s operation, the facility serving as the approval/ controlling authority must coordinate with other facilities concerned.

3−2−2. FILING NOTAM INFORMATION WITH FSSs

NOTAM information should not be filed with an FSS (1−877−4−US−NTMS or 1−877−487−6867) prior to 7 days before the expected condition is to occur. A NOTAM must be transmitted as soon as practical but not more than 7 days before the expected condition is to occur.

3−2−3. NOTAM LOG

FSS air traffic managers must ensure that NOTAMs originated by their facility and FDC NOTAMs received must be accounted for as follows:

a. Log all NOTAMs on a locally approved form containing at least the same data for each accountability (NOTAM file) location. Information to include on the form: month, facility, NOTAM number, condition description, transmitted by/day time group (DTG), and cancelled by/DTG.

b. Incoming FDC NOTAMs and cancellations must be logged on a locally approved form, containing at least the same data. Information to include on the form: FDC NOTAM receipt log, NOTAM number, sending facility, affected facility, number cancelled by, and remarks. The remarks section should contain enough information to identify the location and NAS component affected.

c. Electronic NOTAM logs are acceptable and can replace any paper log.

d. When an FDC NOTAM is received and the previous number(s) have not been received, obtain the NOTAM on request−reply.

REFERENCE− FAA Order 7930.2, Appendix E, Para 7−2−3, Retrieving FDC NOTAMs.

3−2−4. PASSING NOTAM DATA BY PART−TIME FSS FACILITIES

a. Before closing, part−time facilities must give any known NOTAMs that will require dissemination during the hours the facility is closed to the FSS responsible for handling their NOTAMs during the period the facility is closed.

b. Immediately upon resuming the daily operation, part−time facilities must obtain all current NOTAMs, as well as pertinent FDC NOTAMs issued.

Coordination 3−2−1

Chapter 3. General Operating Procedures › Section 3. Use of Terms

Section 3. Use of Terms

3−3−1. USE OF CONTRACTIONS AND ABBREVIATIONS

a. Contractions and abbreviations designated for ICAO usage as specified in FAA Order JO 7340.2, Contractions, and ICAO Document 8400, ICAO Abbreviations and Codes, must be used in the NOTAM system. When an ICAO−usage contraction is not available, plain text is required, except for the list of differences in Appendix C.

b. For indicating abbreviated days of the week, use a hyphen to indicate successive days or each day can be specified individually separated by a single space; for example, MON−FRI means Monday through Friday, whereas MON WED FRI means Monday, Wednesday, and Friday.

c. Use the Pilot/Controller Glossary to define terms in the NOTAM system.

d. Location identifiers used in the NOTAM system are those contained in FAA Order JO 7350.9, Location Identifiers.

e. Use applicable contractions and abbreviations published on instrument flight procedure charts in the text of FDC NOTAMs relating to approach and departure procedures.

f. Contractions written in the singular form decode to mean both the singular and plural.

g. Contractions written in the past tense decode into both the past and present tense.

3−3−2. EXPRESSION OF TIME IN THE NOTAM SYSTEM

a. The day begins at 0000 and ends at 2359.

b. Times used in the NOTAM system are Coordinated Universal Time (UTC/Zulu) unless otherwise stated, as in the body of Temporary Flight Restrictions, and must be stated in 10 digits for the year, month, day, hour, and minute (YYMMDDHHMM).

c. When describing a daily schedule, Sunrise−Sunset (SR−SS) may follow the day(s) or “DLY”.

EXAMPLES− MON−FRI SR−SS DLY SS−SR DLY SR−1800 TUE 2300−SR

3−3−3. UNITS OF MEASUREMENT

Specify the unit of measurement in distance, height, altitude, or weight. When using an abbreviation, do not add a space between the measurement and the unit of measurement. At a minimum, latitude must be 6 digits and longitude must be 7 digits.

EXAMPLES− 500FT 12500LB 5NM 6.2NM 20MIN 1HR 330DEG 305DME 402646N0795856W 402646.25N0795856.95W

Use of Terms 3−3−1

3−3−4. USE OF VIRGULE (/)

The use of virgules should be limited to separate runway pairs (RWY 03/21), combining positions and affected frequencies (LOCAL CTL/CD), and equipment, affected components and frequencies (ILS GP/OM/MM, VOR/DME 111.0/CH77).

3−3−5. RUNWAY IDENTIFICATION

a. Specify the runway identification as it is published, including the leading zero (0).

b. List the runway identifications in clockwise order beginning from the 1 o’clock position.

c. Use runway pair when applicable.

d. Indicated runways should be in feet for sections, closure of a movement area, or portion thereof. Partial runway closures must be indicated by feet, for example, E 500FT.

e. Identify runways with the prefix RWY followed by magnetic bearing indicator.

EXAMPLES− RWY 03/21 RWY 03 RWY 21

f. Differentiate parallel runways by using the runway designators followed by L (left), R (right), and C (center). Use L, R, and C with runway designators only.

EXAMPLES− RWY 03L RWY 03C RWY 03R

g. Where the magnetic bearing indicator has not been established, identify the runway to the nearest eight points of the compass.

EXAMPLE− …RWY NE/SW…

3−3−6. TAXIWAY IDENTIFICATION

a. Identify taxiways with the prefix TWY followed with the taxiway designator letter or letter/number as assigned.

1. Describe a taxiway that does not have an assigned designator as adjacent to a runway or direction from runway.

EXAMPLES− …TWY PARL TWY ADJ RWY 09/27… …TWY PARL TWY… …TWY EAST/WEST TWY CLSD…

2. When a cardinal direction is used to describe a taxiway condition, the word describing the direction must be spelled out in full to ensure that the cardinal direction is not mistaken for a taxiway designator; for example, “EAST,” “WEST,” “SOUTHWEST.”

3. Describe a helipad located on a taxiway as: …TWY HELIPAD 3…

4. Describe a runup pad located on a taxiway as: …TWY A RUNUP PAD… …TWY C RUNUP PAD FOR RWY 27…

b. Keyword TWY may be followed by designator “ALL” to indicate every taxiway at an airport, even if there is only one taxiway as: (Can be used as “TWY ALL EXC TWY X” if needed.) …TWY ALL…

Use of Terms 3−3−2

c. For multiple taxiways, use a comma between each designator. Do not add “TWY” prior to each individual taxiway identifier.

EXAMPLE− …TWY B3, C…

1. Taxiway segments may be identified using geographic points, cardinal directions or by feet.

(a) Geographic. Identify geographic segments using “BTN” and “AND”.

EXAMPLE− …TWY A BTN TWY B AND RWY 01/19…

(b) Cardinal Direction. Identify directional segments using a cardinal direction.

EXAMPLE− …TWY C NORTH OF RWY 09/27…

(c) Dimension. Identify the amount of a taxiway affected by feet.

EXAMPLES− …TWY DD NORTHEAST 500FT… …TWY A BTN TWY L AND 300FT WEST OF TWY L…

(d) Multiple taxiways. Indicate a series of taxiways using a hyphen between the first and last descriptors.

EXAMPLE− …TWY A1−A6…

NOTE− The example includes taxiways A1, A2, A3, A4, A5 and A6.

(e) Multiple segments. Indicate all taxiway segments by starting with the contraction “TWY”, and then add the segment description separated by commas.

EXAMPLES− …TWY A BTN TWY C AND TWY G, TWY B NORTH 100FT, TWY ALL NORTH OF RWY 09/27… …TWY A BTN RWY 01L/19R AND RWY 01R/19L, TWY B BTN RWY 01L/19R AND RWY 01R/19L, TWY C BTN RWY 01L/19R AND RWY 01R/19L CLSD…

(f) Multiple segments (Single Taxiway). Indicate multiple segments of a single taxiway with each portion beginning with TWY.

EXAMPLE− …TWY A EAST OF RWY 01L/19R, TWY A WEST 100FT…

2. Full taxiways and taxiway segments separated by commas share the same condition for example: CLSD, NOT MARKED, WIP SN REMOVAL, etc.

NOTE− Snow removal must only be issued when snow removal is actually occurring.

EXAMPLES− …TWY B1, B2, F, TWY B BTN TWY B10 AND TWY B8 WIP SN REMOVAL… …TWY C BTN APCH END RWY 04R AND APCH END RWY 04L CLSD…

NOTE− The originator may always issue multiple NOTAMs to ensure clarity.

3−3−7. APRON IDENTIFICATION

a. Identify aprons with the keyword APRON followed with the apron designator. There is no requirement for RAMP or APRON to be part of the name of the surface. Keyword may be followed by designator “ALL” to indicate every APRON at an airport, even if there is only one APRON as: (“APRON ALL” or “APRON ALL EXC WEST APN” if needed.)

Use of Terms 3−3−3

EXAMPLES− …APRON TERMINAL APN… (Where the name is Terminal Apron) …APRON MAIN TXL C… (Where the name is Main) …APRON ALL… …APRON J RUNUP PAD… …APRON HELIPAD A1…

NOTE− This example describes a helipad (A1) that resides on a ramp. Only this helipad (A1) has an abnormal condition.

b. SPOTS, GATES, HARDSTANDS, etc., can be used as geographical reference points to delineate a section on aprons or taxiways, but do not meet NOTAM criteria as its own “attribute”.

EXAMPLE− …APRON TERMINAL RAMP BTN GATE 3 AND SPOT 4…

3−3−8. STANDARD NOTAM PHRASES

The following are a listing (not inclusive) of standard terms used in NOTAMs.

TBL 3−3−1 NOTAM Phrases

UNL (unlimited)

TO POINT OF ORIGIN OBSC (obscured)

UNREL (unreliable)

AVBL or NOT AVBL CENTERED AT UNUSABLE CLSD

IRREGULAR SFC (lips, dips, bumps, holes,

ruts, breaks, etc.)

NOW (temporary)

CHANGED TO

(permanent)

UNSAFE

TO EXC NEAR BTN and AND

PLUS SEE… NOT STD NOT LGTD FLAGGED

FOR/AT (RWY) WI AN AREA

DEFINED AS

LGTD USABLE (Used in conjunction with a restriction; not by

itself)

U/S (Out of Service/Unser­

viceable

FLAGGED AND LGTD ADJ (adjacent)

NONMOVEMENT

AREA

BARRICADED (means any type of

barricade)

LGTD AND BARRICADED

OPN or CLSD MARKED or NOT

MARKED

3−3−9. CARDINAL DIRECTIONS

Cardinal directions (excluding TAXIWAY usage) is in abbreviation format. This includes N, NNE, NE, ENE, E, ESE, SE, SSE, S, SSW, SW, WSW, W, WNW, NW, and NNW. Also included are directions for high altitude balloons – northbound – NB, northeast bound – NEB; eastbound – EB; southeast bound – SEB; southbound – SB, southwest bound – SWB; westbound – WB; northwest bound – NWB.

Use of Terms 3−3−4

Chapter 4. NOTAM D Procedures › Section 1. General

Chapter 4. NOTAM D Procedures

Section 1. General

4−1−1. U.S. NOTAM OFFICE RELATIONSHIPS

a. The USNOF is charged with monitoring the NS. The USNOF must monitor the NS for compliance with the criteria and procedures set forth in this order. When questions arise on NOTAM dissemination, formats, contractions, or other aspects of the distribution system, the USNOF should be consulted. The authority for NOTAM formats is the USNOF, who will ensure that issued NOTAMs are consistent with FAA policy. NOTAM originators and certified sources must comply with USNOF personnel guidance. Discrepancies in procedures or format must be recorded, and Aeronautical Information Services must forward a list of the discrepancies to Flight Services, Safety and Operations Support, Operational Procedures, and the service area office.

b. Editing:

1. The USNOF may edit any NOTAM (except FDC NOTAMs relating to instrument flight procedures) that does not conform to the formats and/or examples contained in this order. The contents of a NOTAM must not be changed without notifying the originating facility.

NOTE− FDC NOTAMS relating to instrument approach and departure procedures are originated by the Mission Support Services – Aeronautical Information Services under the Flight Standards Service policy. ARTCCs must ensure the origination of NOTAMs pertaining to a Standard Terminal Arrival (STAR).

2. Should the USNOF edit a NOTAM and change the intent, the NOTAM must be canceled by the issuing facility and reissued as a new NOTAM, after consultation with the USNOF.

General 4−1−1

Chapter 4. NOTAM D Procedures › Section 2. Preparing NOTAMs for Dissemination

~ .,_At-t-,i-bu_t_•,_•_ct_iv_it_y_o_, ,. ~ surface designator

- - - - '1 - - - - '1 I - - - '1 I - - - - '1

I Surface Segment ~ I

Facility or Service ~ I loc.ation ~ I Lower limit L I L I L I L - - - - - - - - - - - T "1--1--------------------------------------------

T

End of Validity

Section 2. Preparing NOTAMs for Dissemination

4−2−1. NOTAM COMPOSITION

NOTE− For FDC NOTAM examples, see Appendix A.

FIG 4−2−1 NOTAM Diagram

Where the solid lines indicate mandatory and the dashed lines indicate as needed or optional.

a. The purpose of the NOTAM diagram is to provide a basic outline of what constitutes a NOTAM. Not all NOTAMs will contain all of the elements. For detailed explanation, consult the applicable paragraph sections for further NOTAM composition assistance.

b. NOTAMs may contain these elements from left to right in the following order:

1. An ADP code/exclamation point (!).

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

3. Location identifier {the affected facility or location, for example, (airport, NAVAID, or ARTCC) appears AFTER the NOTAM number}. Approach controls or airspace located within multiple ARTCC must have a separate NOTAM for each ARTCC.

(a) The nearest public use airport when the full activity is completely within a 5 NM Radius of the airport.

(b) The nearest VOR when any of the activity is more than 5 NM from the nearest public use airport but completely within 25 NM Radius of a VOR

(c) When the activity doesn’t fall within either (a) or (b), use the ARTCC.

4. Keyword.

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

NOTE− A surface designator is required with keywords RWY, TWY, and APRON. For example, a surface designator is RWY 14/32, TWY A, APRON FedEx Ramp.

6. Surface segment (when needed).

7. Facility, feature, service, system, and/or components thereof (when needed). Spell out facility names when used in the body of the NOTAM.

Preparing NOTAMs for Dissemination 4−2−1

(

MAY 14, 0000-2359

A

MAYlS

A I

2200-0900 2200-0900

MAY 16 MAY17

A )

2200-0900

8. Location description (when needed).

9. Lower limit then upper limit, or height, (when needed). Limits must be specified, as:

(a) For SFC, or 1 to 17,999FT with the unit of measurement (AGL or MSL). 50FT, 1275FT AGL, 10500FT.

(b) For 18,000FT and above, express in flight levels (FL), FL180, FL550, FL850, or UNL (altitudes greater than 99,900FT).

(c) Include heights AGL when required (obstacle NOTAMs) or when MSL is not known, for example, SFC−450FT AGL.

(d) The term UNKNOWN may be used in lieu of the MSL or AGL altitudes if not known; however, one altitude must be identified.

10. Condition. The changed condition or status being reported, when needed. When the conditions include a limitation or an exception, follow the condition with “TO” or “EXC”; such as, “CLSD EXC SKI” or “CLSD TO TRANSIENT” or “CLSD EXC TAX BTN APCH END RWY 10 AND TWY C.”

11. Reason (when needed).

12. Remarks (when needed). Other information considered important; for instance, a frequency (134.72), or an expected altitude for unmanned free balloons (NEB TO 150000FT)

13. Schedule, (when needed). A NOTAM may be originated for a scheduled condition/activity that will occur during the period. Specify the schedule between the condition/activity and the valid time string. The days of the week must be specified before the scheduled time. The term “DLY” (daily) indicates the event will occur each day at the same time during the stated time period. The start time of the schedule must correspond to the start of activity time. The end of the last schedule must correspond to the end of validity time.

EXAMPLES− DLY 1200−2000 YYMMDD1200−YYMMDD2000 MON WED 0900−1300 YYMMDD0900−YYMMDD1300 TUE THU 0900−2000 YYMMDD0900−YYMMDD2000

If the active time of a NOTAM corresponds to sunrise or sunset, the actual times of sunrise on the first day of validity and of sunset on the last day of validity must be used.

FIG 4−2−2 NOTAM Schedule

SUN MON TUE WED

!GNV 12/018 F95 AIRSPACE MIL ACT WI AN AREA DEFINED AS 3NM RADIUS OF F95 SFC−14000FT DLY 2200−0900 YY05142200 − YY05170900

This military activity occurs Sunday (May 14) between 2200UTC and 0900UTC, again on Monday and again on Tuesday at 2200UTC then ends on Wednesday (May 17) at 0900UTC.

14. Start of Activity/End of Validity. This is a 10−digit date−time group (YYMMDDHHMM) used to indicate the time at which the NOTAM comes into force (the date/time a condition will exist or begin) and the time at which the NOTAM ceases to be in force and becomes invalid (the expected return to service, return to normal status time, or the time the activity will end). These times must be separated by a hyphen “−.” For

4−2−2 Preparing NOTAMs for Dissemination

example, …RWY 15 CLSD YY12031400−YY12051359…indicates that runway 15 will close at 1400UTC on December 3rd. It is expected to reopen at 1359 UTC on December 5th.

(a) If the NOTAM duration is expected to return to service prior to the End of Validity time, express the time by using a date−time group followed immediately by “EST” (estimate). Any NOTAM that includes an “EST” must be canceled or replaced before the NOTAM reaches its End of Validity time. If the NOTAM is not canceled or replaced, it will expire at the end of validity time regardless of EST. FDC NOTAMs relating to instrument flight procedures must not be canceled and reissued.

(b) The NOTAM Originator is responsible for validating that any NOTAM that is coming to its End of Validity time can auto−expire. If the condition is still valid, the NOTAM must be canceled and reissued with a new Start/Stop time, PRIOR to the NOTAM reaching its End of Validity time.

(c) 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. PERM is also used as the end of validity for certain NOTAMs that 1) pertain to or support national security, law enforcement, and aviation security requirements, and 2) contain flight prohibitions for U.S. operators and U.S. airmen regarding operations in particular areas of non−U.S. controlled airspace due to weapons related hazards or other hostile threats to civil aviation. The NOTAM originator is responsible for canceling the NOTAM upon publication, as PERM will not auto−expire.

(d) All NOTAMs will auto−cancel at their End of Validity time, except PERM.

(e) For an uncontrolled airport, when a NOTAM originator submits a candidate NOTAM to the NOTAM System to advertise an Airport or Runway condition with a Start of Activity less than 60 minutes before the beginning of an activity that impacts/closes a runway or an airport, the activity must be reported to the Air Traffic Control (ATC) facility that has control jurisdiction.

c. 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.

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

e. 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.

f. NOTAMs must state the abnormal status of a component of the NAS and not the normal status. Exception − Temporarily extending hours of use beyond published times, for example: RWY 09/27 OPN.

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 7930.2, Chapter 2, Aeronautical Information Services.

c. Make NOTAM accountability changes by mail, email or other electronic means when known sufficiently in advance. 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 NS tables have been changed. Notify Aeronautical Information Services of any NOTAM accountability changes.

Preparing NOTAMs for Dissemination 4−2−3

Chapter 4. NOTAM D Procedures › Section 3. Canceling/Extending NOTAMs

Section 3. Canceling/Extending NOTAMs

4−3−1. EXTENDING NOTAM VALIDITY

When there is a need to extend an existing NOTAM time validity, cancel the original NOTAM, and reissue the data as a new NOTAM with the new time.

4−3−2. CANCELLATION OF NOTAMs

a. Stations canceling NOTAMs must check the NOTAM data to ensure the NOTAM’s deletion. Retransmit cancellations where no action was taken.

b. Cancel NOTAMs containing erroneous information, and reissue. Originate a new NOTAM when data is received amending a current NOTAM, and cancel the previous NOTAM.

4−3−3. CANCELLING PUBLISHED NOTAM DATA

a. When data appearing in a NOTAM is printed correctly in a publication or on a chart, cancel the NOTAM.

b. NOTAMs must remain active until correctly published in all applicable publications/charts, except NAVAID NOTAMs, which must remain in effect until the NAVAID is returned to service, published as shutdown, or decommissioned. Review all publications listed below:

1. Chart Supplement

2. Enroute low altitude charts

3. Enroute high altitude charts

4. Terminal procedures publications

NOTE− FDC NOTAMs relating to instrument approach and obstacle departure procedures and airways must remain current until published in the Terminal Procedures Publication or applicable enroute chart.

5. VFR Charts:

(a) Sectional charts

(b) Terminal area charts

c. NOTAMs concerning Army airfield operations, in addition to the above listed sources, must be researched in the Army Aviation Flight Information Bulletin, if applicable.

Canceling/Extending NOTAMs 4−3−1

Chapter 5. NOTAM Criteria › Section 1. Movement Area NOTAMs

Condition limitation -----•: Exceptions/PPR -: __ ,. .. ~ Other Comments

Chapter 5. NOTAM Criteria

Section 1. Movement Area NOTAMs

5−1−1. ORIGINATORS OF AERODROME NOTAMs

a. Airport management is responsible for observing and reporting the condition of the aerodrome services, facilities, and movement area. The FSS air traffic managers must coordinate with appropriate airport managers to obtain a list of airport employees who are authorized to originate NOTAMs.

b. At public airports without an airport manager, the FSS air traffic manager must coordinate with the appropriate operating authority to obtain a list of persons delegated to provide NOTAM information.

NOTE− Letters of agreement should be executed between airport management and ATC facilities outlining procedures to be used for originating NOTAMs.

5−1−2. HANDLING REPORTED AERODROME CONDITIONS

a. Copy any information received verbally, and record the name, title (if appropriate), address, and telephone number of the person submitting the information. Information obtained from other than an authorized airport or FAA employee must be confirmed before issuance. If you are informed of or observe a condition that affects the safe use of a movement area, relay the information to the airport management for action.

NOTE− This includes data received from airport inspectors.

b. If unable to contact airport management, classify and issue a NOTAM publicizing the unsafe condition always stating the condition and including the word “UNSAFE;” for example, RWY number or TWY letter or letter/number “UNSAFE DISABLED ACFT.” Inform airport management of the action taken as soon thereafter as practical.

c. (U) – Unverified aeronautical information (for use only where authorized by letters of agreement). Movement area or other information received that meets NOTAM criteria and has not been confirmed by the airport manager or designee. If Flight Service is unable to contact airport management, Flight Service must forward (U) NOTAM information to the NS. Subsequent to NS distribution of a (U) NOTAM, Flight Service will inform airport management of the action taken as soon as practical. Any such NOTAM will preface the keyword with “(U)” and must include the condition and cause.

5−1−3. MOVEMENT AREA INFORMATION

FIG 5−1−1 Movement Area Diagram

…AD AP CLSD EXC PPR MON−FRI 0330−1430 YYMMDD0330−YYMMDD1430

Movement Area NOTAMs 5−1−1

•RWY" designator

"TORA_Fr … "TOOA_FT" ~ "ASDA_Fr --+ "LDA_FT"

"RWY" designator "TORA_FT" … "TODA _Fr ~ "ASDA _ FT" --+ "LDA _ FT"

See Appendix A for examples.

Originate a NOTAM D for:

a. Aerodrome conditions. Use the keyword “AD” immediately followed by the facility: “AP”, “HLP”, or “SEAPLANE BASE”, followed by the condition. When the condition includes a limitation, follow the condition with “TO” or “EXC;” for example, “CLSD EXC SKI” or “CLSD TO TRANSIENT.”

b. Commissioning of a movement area or portions thereof. State the type of surface, length and width of the surface, lighting status, and declared distances.

1. Lighting status; for example, LGTD, NOT LGTD.

2. Length and declared distances required for only runway commissioning.

c. Closure of a movement area or portion thereof. Partial runway closures must be indicated by feet, for example, E 500FT.

1. Permanent closure (decommissioning). State the surface description and the condition “CLSD” with expiration time “PERM.”

2. Temporary Nonmovement Area. Use this feature when a taxiway is temporarily designated as Non Movement in a NOTAM.

d. Operational limitations on the use of any portion of a runway, a taxiway, a ramp, an apron or a waterway. Weight bearing capacity of a runway can be changed only by authorization of the Manager, Airports Division (appropriate region). Include reference to ACFT when describing limitations associated – wing, weight, tail, engine, taxi speed, etc. Do not refer to the Airplane Design Group in the NOTAM.

e. Changes to usable runway length and declared distances.

FIG 5−1−2 Sentence Structure

1. When a runway condition restricts or precludes the use of any portion of a runway resulting in a change to the declared distances, include the published take−off run available (TORA), take−off distance available (TODA), accelerate− stop distance available (ASDA), and landing distance available (LDA) in the NOTAM. Ensure that a second NOTAM is originated for the reciprocal runway with all declared distances if any value has changed. Declared distances can only be authorized by the FAA Office of Airport Safety and Standards, Airport Design Division, AAS−100.

2. In the event the published TORA, TODA, ASDA, and LDA need to be reported without reference to the runway condition that caused the change, report declared distances or changes to published declared distances. For example, when the published runway length is changed, report the declared distances, or erroneous declared distances that were published and need to be corrected.

f. Change of runway identification.

g. Change of traffic pattern.

h. Runway Visual Range (RVR). When originating a NOTAM on RVR, RVR touchdown (RVRT), RVR midpoint (RVRM), and RVR rollout (RVRR), specify the single runway affected. When all the RVRs are unserviceable, issue a NOTAM using the keyword AD.

Movement Area NOTAMs 5−1−2

~-K_E_vw_o_Ro _ __.----.. ..il Svrfai;e Name/ _ _ Designator 1---1 .. ►: Surface Segment :---1 .. ► "FICON"

RCC ~ PRCT . . '• •· …

Condition/Contaminant

,••······ ···· ········ ···. . . Action 4i Width of Treatmentfs :,---.. . . . . … • '••··················· ···

Additional Surface

Information ~ ·oeSERVEDAT(time)" _ _,.._~ OtherComments

• • ••• • ••• • ••• • ••• • M•• • •••

i. Surface Markings and Signage. Follow 4−2−1 b 1−3, including:

1. Keyword. Specify the keyword for the type of surface on which the sign/marking is located.

2. Surface designator. Specify the designator of the surface on which the sign/marking is located.

3. Geographical Relationship of surface from relevant intersection/point of reference, (N OF, E OF), if needed.

4. Name of sign/surface marking. Signs follow runway identification guidance.

5. Sign/ marking location from users’ perspective (LEFT/RIGHT SIDE; FOR RWY; AT RWY), when needed.

6. Condition. For example, NOT STD, NOT LGTD, OBSC, MISSING, NOT MARKED

7. Follow 4−2−1 b 11−14 to complete the NOTAM.

j. Other reportable conditions. The airport operator must ensure that a NOTAM is submitted for conditions considered to be hazardous or potentially hazardous to the aircraft operator. Permanent changes in surface conditions must be coordinated for publication in accordance with paragraph 2−1−3, Publication Criteria.

1. When SNOWBANKS, BERMS, DRIFTS, and SN PILES are not on the movement areas, issue them without the FICON descriptor.

2. When it is determined that no surface condition reports will be taken and no current observation exists, issue a single NOTAM (Keyword AD) for the entire time−period. Use the phrase “SFC COND NOT REP”, as this differs from Conditions Not Monitored.

3. Wildlife.

(a) Wildlife NOTAMs are to be issued for abnormal events, not as general information, and must specify the type of wildlife event.

(b) If wildlife events are expected on a regular basis, submit this information for publication in the Chart Supplement.

(c) Wildlife NOTAMs must not be issued as PERM, unless the publication process has been initiated per paragraph 3−1−4, Permanent (PERM) NOTAM Process.

(d) Once published, do not submit information as a NOTAM.

5−1−4. FIELD CONDITIONS (FICON) REPORTING

FIG 5−1−3

FICON

…RWY 33 FICON 4/4/4 100 PRCT COMPACTED SN PLOWED 100FT WID 24IN BERMS…

See Appendix A for examples.

Movement Area NOTAMs 5−1−3

a. Report surface conditions on runways, taxiways, and aprons using the FICON NOTAMs. The keyword AD must not be used with descriptor FICON, except for heliport.

EXAMPLES− …AD HLP FICON 4IN DRY SN… …AD HLP FICON 2IN DRY SN PLOWED 50FT WID 4FT SNOWBANKS…

1. Runway. Takeoff and Landing Performance Assessment (TALPA) FICONs are reported in thirds of the landing runway. Runways are described using the RWY keyword followed by a single runway direction designator, FICON and condition, except when reporting Slippery When Wet use the dual runway designator. Airport condition reports (FICON) must not be issued for a closed runway.

EXAMPLES− …RWY 04/22 FICON 3/3/3 SLIPPERY WHEN WET… …RWY 04 FICON…

2. Taxiway. Taxiways are described using the TWY keyword followed by a surface name/designator, FICON and condition. Depth is required and a width is optional.

EXAMPLES− …TWY A FICON 1/2IN WET SN… …TWY A FICON 1/2IN WET SN 50FT WID REMAINDER COMPACTED SN…

3. Apron. Aprons are described using the APRON keyword followed by a surface name/designator, FICON and condition. Depth is required and a width is optional.

EXAMPLE− …APRON MAIN RAMP BTN RWY 13/31 AND TWY C FICON 1IN DRY SN…

4. Helipad. Helipads are described using TWY or APRON keywords followed by HELIPAD (surface designator) FICON and condition.

EXAMPLES− …APRON HELIPAD H1 FICON 2IN DRY SN… …TWY HELIPAD C FICON DRY PLOWED 50FT WID REMAINDER COMPACTED SN…

b. When there is a significant change in conditions, issue an updated FICON NOTAM.

c. Airport operators use the Runway Condition Assessment Matrix (RCAM − See TBL 5−1−4) to create the Runway Condition Code (RwyCC) for Paved Surfaces, which include asphalt, asphalt−concrete, concrete, and porous friction course. Non−paved surface NOTAMs do not include the RwyCC. The NS generates the RwyCC based on airport operator input of the contaminants present. Per AC 150/5200−30, Airport Field Condition Assessments and Winter Operations Safety, airport operators have the capability, in accordance with specific action and protocols, to downgrade or upgrade the runway condition code.

d. Each field of the NOTAM is described below. Follow the NOTAM composition in 4−2−1 a 1−4 to include:

1. Surface Designator (RWY 04)

2. FICON. Insert “FICON” after the surface designator and before the field condition.

3. RwyCC. When generated, it will be illustrated as values between 0 and 6 and look similar to this for runway thirds (3/4/2). The RwyCC will only be provided for paved runways when the percentage coverage of the full runway that is contaminated is greater than 25 percent. Report RwyCCs based on the direction of the assessment. Report only one set of RwyCCs per runway surface. For example, do not report two runway condition reports (one from each end) for a runway.

4. Condition. Report the contaminants per TBL 5−1−2, including the percentage of coverage for runways, in thirds. For taxiways and aprons, do not express the condition in terms of percentage of coverage. Use the word “PATCHY” to describe a contaminant that covers 25 percent or less of the reported portion of the surface of a taxiway, apron, heliport or airport.

Movement Area NOTAMs 5−1−4

TBL 5−1−1 Reportable Depth Measurements

Use Value To Report

1/8IN ⅛ inch or less

1/4IN >⅛ inch to and including ¼ inch

1/2IN >¼ inch to and including ½ inch

3/4IN >½ inch to and including ¾ inch

1IN >¾ inch to and including 1 inch

TBL 5−1−2 Reportable Contaminants

Wet (includes damp and ⅛ inch depth or less of water)

Compacted snow

Water* (greater than ⅛ inch depth) Water* over compacted snow

Frost Wet snow* over compacted snow

Slush* Dry snow* over compacted snow

Ice Slush* over Ice

Wet ice Slippery When Wet

Wet snow* Ash

Wet snow* over ice Rubber (taxiways only)

Dry snow* Oil

Dry snow* over ice Sand

Mud* (See AC 150/5200−30)

TBL 5−1−3 Percent Coverage of a Contaminant

10 10% or less

20 11% − 20%

25 21% − 25%

30 26% − 30%

40 31% − 40%

50 41% − 50%

60 51% − 60%

70 61% − 70%

75 71% − 75%

80 76% − 80%

90 81% − 90%

100 91% − 100%

(a) Runways, including ski strip and waterlane.

(1) RWY: Each third (touchdown, midpoint, and rollout) will include percentage, depth (when required), and type of contaminant. Up to two separate contaminants can be reported per runway third.

(2) A runway is dry when it is neither wet, nor contaminated. A FICON NOTAM must not be originated for the sole purpose of reporting all thirds of a runway are dry. A dry surface must be reported only when there

Movement Area NOTAMs 5−1−5

is need to report conditions on the remainder of the surface. When describing a dry surface, it is considered the full length and width of the runway third. DRY can be reported in two thirds and the remaining third have a different contaminant.

EXAMPLE− …RWY 04 FICON 10 PCT 1IN WET SN, 10 PCT 1/8IN DRY SN OVER ICE AND 10 PCT 1/8IN DRY SN, DRY…

(3) A runway is wet when there is any visible dampness or water that is 1/8 inch or less in depth. When describing a wet surface, include the percentage.

(4) If all three thirds are identical percentage, depth (when required) and type of contaminant, it is shown in the NOTAM once.

EXAMPLE− …RWY 03 FICON 4/4/4 75 PCT COMPACTED SN…

(b) Taxiways and Aprons. The condition includes depth and type of contaminant.

NOTE− Free−form is an acceptable means of entering FICONs for TWY and APRONs.

(c) Reportable values

(1) Report depths in measurement of fractions as indicated in TBL 5−1−1 above. When 1 inch is reached, report values in multiples of 1 inch and discontinue the use of fractions. When a snow depth of 35 inches is reached, report values in multiples of feet only. Round depths greater than 1 inch to the next higher reportable depth.

(2) Report the highest depth of the contaminant along the reported portion of the surface.

(3) The only reportable contaminants and contaminant combinations authorized for use are found in TBL 5−1−2 above. These contaminants marked by an “*” must be accompanied by a depth for all Part 139/Federally obligated airports. For all other airports, the depths on taxiways and aprons is optional.

5. Action. Action taken to treat the contaminated surface.

(a) Includes the treatment method (Up to three treatments permitted for full length of runway/taxiway/apron.) Treatment includes plowed, swept, sanded, deiced liquid, deiced solid, scarified (for runways, each third must be contaminated with only ice and the total surface coverage must be >25%). A treatment width of 50FT is considered 25ft on each side of the centerline.

Movement Area NOTAMs 5−1−6

,___~_ared_Wid_th _ __,I 1..--I __ Cle_arcd_W~_th_~I l~-'~•_•~_=_t h _ __,

I Cleared width I I Oeared width I

FIG 5−1−4 Cleared and Remaining Width

(b) Includes width of PLOWED or SWEPT treatment if not the full width. The treatment is omitted when the entire surface has been plowed or swept.

(c) Includes SANDED when a surface has been treated with sand.

(d) Includes DEICED LIQUID or DEICED SOLID or both to report the presence of liquid or solid deicing material, as this can have operational significance to the pilot.

(e) Includes ridges (when applicable) to describe the accumulation at the edge of the movement area or of the treated area when the surface has been plowed/swept. Ridges include SNOWBANKS, BERMS (containing earth/gravel), WINDROWS (ridge of snow created by mechanical means), and DRIFTS (deposit of snow sculpted by wind action into a mound). Use the term “DRIFTS” after any treatments (when applicable) to describe one or more drifts. When the drifts are variable in depth, report the greater depth.

Movement Area NOTAMs 5−1−7

On RWY Edge ' " ~ •• • • ··. . … ;,, ;

Publl!:hed Width

FIG 5−1−5 Distance of Snow Bank from Runway Edge

EXAMPLE− …FICON 5IN DRIFTS…

(f) Includes “Remainder” (see example above that refers to cleared and remaining width) to describe the non−treated depth and type of contaminant for full length of runway/taxiway/apron to provide additional information about the surface condition. For example, a runway has been treated, resulting in differing field conditions on the untreated parts of the surface.

EXAMPLES− …FICON 4/4/4 50 PCT COMPACTED SN PLOWED 75FT WID REMAINDER 1/2IN DRY SN… …FICON 25 PCT COMPACTED SN AND 10 PCT ICE, 25 PCT 2IN DRY SN, DRY PLOWED 75FT WID REMAINDER 1/2IN DRY SN… 6. Braking Action (BA). (APRONs, TWYs and Non−Paved RWYs). Report braking action on movement areas as good to medium; medium; medium to poor; poor; or nil, as received from airport management. The worst runway braking action is shown by contaminant type and RwyCC.

(a) Reporting of a “NIL” braking condition is not permissible by Federally Obligated Airports or those airports certificated under 14 CFR part 139. A “NIL” braking condition at these airports must be mitigated by closure of the affected surface.

NOTE− A “NIL” braking action NOTAM can be issued at airports not receiving federal money and non−part 139 airports on taxiway or apron surfaces only. No aerodrome can issue a runway NIL braking action.

(b) Paved surfaced runways cannot have a stand−alone BA NOTAM.

(c) Non−Paved surfaced runways can have BA, but as a stand−alone NOTAM.

(d) TWY/Apron can have BA as stand−alone or appended to field condition NOTAM.

NOTE− A braking action report from a landing aircraft should be processed as a PIREP. EXAMPLES− …TWY A FICON BA GOOD TO MEDIUM… …TWY A FICON 1/8IN WET SN BA MEDIUM…

7. Observation Time. The time airport management observed the conditions.

8. Conditions Not Monitored (when applicable). When an airport operator cannot monitor the condition of the movement area or airfield surface, this information is issued as a NOTAM. Usually necessitated due to

Movement Area NOTAMs 5−1−8

staffing, operating hours or other mitigating factors associated with airport operations. When the field conditions will not be monitored, follow the most recent observation with the words “COND NOT MNT (date/time) (date/time).” The time parameters specified must fall within the start of activity/end of validity times.

9. Start of Activity/End of Validity. FICON NOTAMs are considered temporary, therefore the End of Validity time for FICON NOTAMs must not exceed 24 hours from the Start of Activity time, except:

(a) When the reported contaminant is ASH, MUD, OIL RUBBER (taxiway only), or SAND.

(b) When appended with remarks “COND NOT MNT.”

e. Rubber as a contaminant/Slippery When Wet.

1. Rubber is used on Taxiways only to describe the accumulation of rubber.

EXAMPLE− …TWY A FICON RUBBER…

2. Slippery When Wet is a stand−alone NOTAM, used only on runways, where a friction survey (conducted for pavement maintenance) indicates the averaged Mu value at 40 mph on the wet pavement surface failed to meet the minimum friction level classification. This is the only FICON that is described using both runway ends.

REFERENCE− AC 150/5200−30, Airport Field Condition Assessments and Winter Operations Safety. EXAMPLE− …RWY 02/20 FICON 3/3/3 SLIPPERY WHEN WET…

NOTE− May be downgraded to 2/2/2 or 1/1/1 with all numbers matching.

Movement Area NOTAMs 5−1−9

Condition Assessment Matrix (RCAM)

Assessment Criteria Downgrade Assessment Crit eria

Deceleration Or Pilot

Runway Condit ion Description Code Mu Directional Control Reported M Observation Braking

Action

• Dry 6 --- --- -

• Frost • • Wet (Includes Damp and1/8" depth or less of 0 Water) ~ Braking deceleration is :c s q normal forthewheel braking Good 118" (3 mm) depth or less of: ~ effort applied AND • Slush directional control is normal. • Ory Snow • Wet Snow -

c., U)

5° F (•15°C) and Colde.routside. air te.mpe.rsture: Braking deceleration OR Good 4 directional control is to • Compacted Snaw between Good and Medium. Medium

• SlipperyWhenWet(wetrunway) 0 • Ory SnoworWetSnow(Anydepth) over Compacted Snow Braking deceleration is noticeably reduced for the Greater than 118" (3 mm) depth of: 3 wheel braking effort applied Medium • Ory Snow OR directional control is • Wet Snow - noticeably reduced.

Warmer than 5° F (•15°C) outside air temperatuna: c., • Compacted Snaw 0 ., U) -

Greater than 118" (3 mm) depth of: Braking deceleration OR Medium • Water 2 0 directional control is to • Slush between Medium and Poor. Poor

!::! Braking deceleration is significantly reduced for the • Ice 1 wheel braking effort applied Poor

~

OR directional control is - significantly reduced.

• Wet Ice Braking deceleration is • Slush over Ice minimal to non 4 existent for 0 the wheel braking effort Nil • Water on top of Compacted Snow applied OR directional • 0ry SnoworWetSnawover lce control is uncertain.

TBL 5−1−4 Runway Condition Assessment Matrix Runway

Movement Area NOTAMs 5−1−10

KEYWORD

Condition

Feature, Service, Facility or System

Other Comments

Descriptive comments about Feature, Facility, Service or System :

5−1−5. AERODROME FACILITIES

FIG 5−1−6 Aerodrome Facilities

…AD AP CLSD EXC PPR MON−FRI 0330−1430 YYMMDD0330 – YYMMDD1430

See Appendix A for examples.

Issue a NOTAM if any aerodrome service availability has changed from that which is published.

a. Certified Aircraft Rescue and Fire Fighting (ARFF).

1. Issue a NOTAM D on airports (not runways) certificated under 14 CFR Part 139, when notified by airport management that required ARFF equipment is inoperative/unavailable and replacement equipment is not available. Except as indicated in paragraph 5−1−5a 3, airport management has 48 hours to replace or substitute equipment before the index changes. Air carriers and others must be notified that ARFF equipment is unserviceable. Each NOTAM must have an expiration time as obtained from airport management. If unable to obtain an expiration time, add 48 hours to the time of receipt and advise airport management.

NOTE− The ARFF Index for each certificated airport is published in the U.S. Chart Supplement, which lists indices and ARFF equipment requirements.

2. At certificated airports listed in the U.S. Chart Supplement, the certificate holder (airport management) is required to notify air carriers by NOTAM when required ARFF equipment is inoperative/unavailable and replacement equipment is not available immediately. If the required Index level of capability is not restored within 48 hours, airport management is required to limit air carrier operations.

REFERENCE− Title 14 CFR Part 139

3. If the ARFF vehicle is still unserviceable after 48 hours, the airport manager must notify the FSS of a temporary index change and approximate duration time.

4. If the ARFF Index is listed in the U.S. Chart Supplement, as A and the ARFF vehicle is unserviceable, the NOTAMs must indicate that index A is not available and the airport is closed to air carrier operations.

b. Fuel Services.

c. Custom Services.

d. Aerodrome Beacon (ABN). Describe the beacon status as accurately as possible. For example, ABN NOT ROTATING; ABN NOT STD GREEN ONLY

e. Wind direction equipment, including wind cones, wind direction indicator, wind sock, etc.

f. Airplane Design Group. For those airports capable of permitting Group VI (A−380, B747−8) aircraft but have a limit on the capacity, issue a NOTAM when the capacity is reached so other aircraft won’t attempt to land. Do not refer to the Airplane Design Group in the NOTAM.

REFERENCE− AC 150/5300−13, Airport Design

Movement Area NOTAMs 5−1−11

KEYWORD

Condition

Feature, Service, Facility or System

Other Comments

Descriptive comments about Feature, Facility, Service or System :

5−1−6. WORK IN PROGRESS

FIG 5−1−7 Work in Progress

…TWY C WIP TRENCHING ADJ EAST SIDE…

See Appendix A for examples.

a. Work in Progress (WIP) describes any work being done on the airport surface, including construction, mowing, snow/ice removal, etc. WIP does not close a movement area; therefore, if the movement area is restricted, another NOTAM identifying that restriction is needed. For example, a WIP with snow removal requires a closure NOTAM with 15 minute PPR in order to use the surface.

b. WIP (reason) is mandatory for describing construction and snow/ice removal NOTAMs. Other WIP reasons are optional.

c. Any NOTAM associated with work in progress on or adjacent to a runway, taxiway, apron/ramp, or aerodrome must be formatted as follows 4−2−1 b 1−3, including:

1. Keyword. RWY, TWY, APRON, or AD.

2. Surface name/designator. Specify the name/ designator of the surface on which the work is being conducted.

3. Surface segment description must be specified in feet or from a specific point to point; for example, TWY A SOUTH 76FT or TWY A BTN TWY B AND TWY C.

NOTE− A surface segment differs from the optional plain language description of the work areas in that the surface segment description can be captured and depicted graphically in a digital environment. The optional plain language comments will be delivered in text form only.

4. Condition or activity; “WIP.”

NOTE− Airport operators must ensure this NOTAM remains active only when actual snow and ice removal operations are taking place.

5. Reason or purpose.

6. Remarks. The work area may be described in plain language text after the reason by specifying the area by cardinal direction in relationship to the work area, by an intersection, or distance from an intersection.

7. Follow 4−2−1 b 13 and14 to complete the NOTAM.

Movement Area NOTAMs 5−1−12

Chapter 5. NOTAM Criteria › Section 2. Lighting Aid and Obstruction NOTAMs

KEYWORD

Condition

Feature, Service, Faclllly or System

:· •• , ·o~~'riPii~~- ~~~~~·~t~· ~~~t •••• : ; • G·eograpn,ca1·re1atroriSfliP ·: : Feature, Facility, SeMce or System ►, of surface to relevanl

. .. , , , , , .. , .. , , . . , .. , .. , , .. , … , , . . ,: ; ~· ,, .. , .1~ !,r~,~ !1,q ry , , .. , .. ,;

Other Comments

Section 2. Lighting Aid and Obstruction NOTAMs

5−2−1. LIGHTING AIDS

FIG 5−2−1 Lighting Aids

…RWY 27 RTHL U/S…

See Appendix A for examples.

Originate NOTAMs on operational status of lighting aids for public use civil landing areas listed in the U.S. Chart Supplement. Each type of lighting requires separate NOTAMs. Technical Operations must be made aware of any runway lighting outages, as this is the office that maintains the equipment. When describing restrictions, use Runway Centerline (RCL) with visual navigational aids. NOTAMS regarding lighting aids are originated as follows:

a. Approach light systems (ALS). Only use the runway direction for which the equipment pertains.

1. When commissioning approach light systems, indicate the exact type of system; for example, MALSR, MALSF, etc.

2. Once commissioned and published, approach light systems need only be shown as ALS.

3. When the ALS has been changed to the simplified, short ALS with with runway alignment lights, issue the condition as temporarily changed (“NOW”). Do not use out of service/unserviceable.

b. Lead off /lead on lights. NOTAMs issued using keyword RWY. Lead off and lead on light will be the standardized verbiage for lead off/on lights, which are also referred to as turnoff lights.

c. Runway status light system.

1. Runway entrance lights. NOTAMs issued using keyword TWY

2. Take−off hold lights.

d. Sequence flashing lights/runway alignment indicator lights.

e. Visual approach lighting.

1. Visual approach slope indicator (VASI).

2. Precision approach path indicator (PAPI).

3. Runway end identifier lights.

4. Threshold lights (RTHL).

NOTE− Technical Operations issued, when associated with Approach Lighting System (ALS).

f. Runway end lights (RENL).

NOTE− Airport Operations issued, not associated with Approach Lighting System (ALS).

Lighting Aid and Obstruction NOTAMs 5−2−1

r

PARTIALLY OBSC

Type of Obstruction

AltJI\Jde

PARTIALLY OBSC

Obstruction

Identifier

Height "AGL"

Coordinates

Condition

OBSC

, … 1--t~: Alternate Location : : Description ---. …

Other Comments

g. Runway edge lights (REDL).

1. When commissioning runway edge light systems, indicate the exact type of system; for example, LIRL, MIRL, HIRL, etc.

2. Once commissioned and published, runway edge lights must only be shown as REDL.

3. Runway lights obscured due to snow and ice.

h. Runway centerline light (RCLL).

i. Touchdown zone lights (RTZL).

j. Runway lead−in lighting system (RLLS).

k. Airport lighting total power failure.

l. Pilot−controlled lighting (PCL) frequency when it controls approach lights or runway lights.

m. Taxiway lighting.

1. Taxiway edge lights.

2. Taxiway centerline lights.

3. Runway guard lights. NOTAM issued using keyword TWY.

4. Stop bar lights. NOTAM issued using keyword TWY.

5. Taxiway lights obscured due to snow and ice.

FIG 5−2−2 Obscured or Partially Obscured Runway Edge Lights

NOTE− Lights that are partially obscured are not reported as a NOTAM.

5−2−2. OBSTACLES

FIG 5−2−3 Obstacles "08S

5−2−2 Lighting Aid and Obstruction NOTAMs

…OBST CRANE (ASN 20YY−ACE−5−NRA) 345140N0804506W (1.44NM SW N52) 580FT (195FT AGL) NOT LGTD…

See Appendix A for examples.

a. Obstructions to include telecommunications antenna tower lights, cranes, stacks, wind turbines, non−FCC towers, power lines, moored balloon, kites, natural growth/terrain, etc.

b. Any failure or malfunction which affects a top light or flashing obstacle light regardless of its position is a condition for a NOTAM.

c. Commercial tower light operators must report the operating status of tower lights and ensure that a NOTAM is originated via a direct entry tool or contacting FSS.

d. The NOTAM text for obstructions to air navigation must be formatted as follows 4−2−1 b 1−2, including:

1. Location Identifier: For wind turbine farms, use the ARTCC under which the farm falls.

2. Keyword “OBST.”

3. Specify the attribute; for example, “TOWER LGT”, “CRANE,” “STACK,” “ACFT TAIL,” “BLDG,” “MOORED BALLOON”, “KITE” etc.

4. Assigned obstruction identifier.

(a) For FCC Towers, the Antenna Structure Registration (ASR), if known, in parentheses. If the ASR is not known, indicate by (ASR UNKNOWN) in the NOTAM.

(b) For Cranes, Stacks, etc., the Aeronautical Study Number (ASN), if known, in parentheses. If the ASN is not known, indicate by (ASN UNKNOWN) in the NOTAM. Do not include the ASN for wind turbine farm NOTAMs, see examples.

(c) For Moored Balloon, which requires a waiver to 14 CFR Part 101, the assigned obstruction identifier is not required.

5. For FCC Tower Obstructions, enter the location by latitude and longitude to the nearest one hundredth of a second. For wind turbine farms, if using latitude and longitude, provide the coordinates for the center point of the wind farm, or the coordinates for one of the turbines closest to the center. If the latitude and longitude is not known, use “UNKNOWN”. For all other obstacles, use the latitude and longitude to the nearest second, or fix/radial/distance, or a nautical mile radius of a NAVAID.

6. Plain language location in parentheses.

(a) When the obstacle is within 5SM of an airport, describe the plain language location in feet or nautical miles using 16 points of compass from a specified location on the airport; for example, (.5NM E APCH END RWY 18) (2000FT SSE DEP END RWY 20) (2NM SSW ACY).

Continue reading ↓ 120 of 325 passages shown