Radar Vectors
FAA Order Cancelled Issued Dec 15, 2015 AJR-B 108 pages Copy saved Nov 18, 2026

Order JO 7930.2Q Notices to Airmen (NOTAM)

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

Official source ↗ Open PDF

Comments/Corrections

Comments/Corrections

Comments or corrections concerning this publication may be submitted on this form and submitted electronically to: 9−AJV−8−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

JO 7930.2Q CHG 1 05/26/16

Explanation of Changes E of Chg−1

Notices to Airmen

(NOTAM)

Explanation of Changes

Effective: May 26, 2016

Change 1

a. 1−1−7. RECOMMENDATIONS FOR PROCEDURAL CHANGES

Updating order to the current nomenclature being used by the ATO. The title of paragraph 1−1−7 was changed from Revisions to Recommendations for Procedural Changes to remain consistent with other FAA Orders.

b. Entire Publication

A global search and replace was conducted on the term “A/FD − Airport/Facility Directory.” This term is now being referred to as “Chart Supplement U.S.”

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

JO 7930.2Q CHG 1 05/26/16

i 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. RECOMMENDATIONS FOR PROCEDURAL CHANGES 1-1-1 … 1-1-8. EFFECTIVE DATE 1-1-1 … 1-1-9. RELATED PUBLICATIONS 1-1-1 …

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 1-3-1 … 1-3-2. TECHNICAL OPERATIONS SERVICES 1-3-1 … 1-3-3. FLIGHT INSPECTION SERVICES 1-3-2 … 1-3-4. OFFICE OF AIRPORT SAFETY AND STANDARDS 1-3-2 … 1-3-5. FLIGHT STANDARDS SERVICE 1-3-2 … 1-3-6. AIRPORT MANAGEMENT 1-3-2 …

Section 4. Terms of Reference

1-4-1. WORD MEANINGS 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. NOTICES TO AIRMEN PUBLICATION 2-1-2 … 2-1-5. CHART/PUBLICATION ERRORS OR OMISSIONS 2-1-2 … 2-1-6. FORWARDING DATA 2-1-2 … 2-1-7. ADDRESSING CORRESPONDENCE 2-1-3 … 2-1-8. NFDC ORGANIZATION 2-1-3 …

JO 7930.2Q CHG 1 05/26/16

ii Table of Contents

Paragraph Page 2-1-9. THE NATIONAL FLIGHT DATA DIGEST (NFDD) 2-1-3 … 2-1-10. COMPUTER PRINTOUTS 2-1-3 …

Chapter 3. General Operating Procedures

Section 1. General

3-1-1. TIE-IN STATIONS 3-1-1 … 3-1-2. NOTAM RESPONSIBILITIES 3-1-1 … 3-1-3. NOTAM LOG 3-1-1 … 3-1-4. FDC PRESIDENTIAL, SPECIAL SECURITY INSTRUCTIONS, OR EMERGENCY AIR TRAFFIC RULES TFRs 3-1-1 …

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. PASSING NOTAM DATA BY PART-TIME FSS FACILITIES 3-2-1 … 3-2-4. NON-FEDERAL 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-1 … 3-3-5. RUNWAY IDENTIFICATION 3-3-1 … 3-3-6. TAXIWAY IDENTIFICATION 3-3-2 … 3-3-7. APRON IDENTIFICATION 3-3-2 … 3-3-8. STANDARD NOTAM PHRASES 3-3-2 … 3-3-9. CARDINAL DIRECTIONS 3-3-3 …

Chapter 4. NOTAM D Procedures

Section 1. General

4-1-1. ACCEPTING NOTAM D INFORMATION 4-1-1 … 4-1-2. NATIONAL 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-2 …

Section 3. Coding and Transmission of NOTAMs

4-3-1. PREPARATION FOR TRANSMISSION 4-3-1 … 4-3-2. AUTOMATIC DATA PROCESSING (ADP) CODES 4-3-1 … 4-3-3. NOTAM TRANSMISSION 4-3-1 … 4-3-4. TRANSMISSION OF NOTAMs EXCEEDING 20 LINES 4-3-1 … 4-3-5. CONFIRMING ACCEPTANCE BY THE NOTAM SYSTEM 4-3-1 … 4-3-6. TRANSMISSION BY ANOTHER FACILITY 4-3-1 … 4-3-7. RETRIEVING DOMESTIC NOTAMs 4-3-1 …

JO 7930.2Q CHG 1 05/26/16

iii Table of Contents

Section 4. Canceling/Extending NOTAMs

Paragraph Page 4-4-1. EXTENDING NOTAM VALIDITY 4-4-1 … 4-4-2. CANCELLATION OF NOTAMs 4-4-1 … 4-4-3. CANCELING PUBLISHED NOTAM DATA 4-4-1 …

Section 5. Computer-Generated NOTAM ServiceMessages

4-5-1. MONITORING 4-5-1 … 4-5-2. NOTAM SERVICE MESSAGES 4-5-1 …

Chapter 5. NOTAM Criteria

Section 1. Movement Area NOTAMs

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. REPORTING FIELD CONDITIONS 5-1-4 … 5-1-5. AERODROME FACILITIES 5-1-9 … 5-1-6. WORK IN PROGRESS 5-1-10 …

Section 2. Lighting Aid and Obstruction NOTAMs

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

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-4 … 5-3-9. HOURS OF OPERATION 5-3-6 …

Section 4. Communications Outlets 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-3 … 5-5-5. MICROBURST/WINDSHEAR DETECTION SYSTEM 5-5-4 … 5-5-6. RADAR SERVICES 5-5-4 …

JO 7930.2Q CHG 1 05/26/16

iv Table of Contents

Chapter 6. Airspace NOTAMs

Section 1. Airspace

Paragraph Page 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 …

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. INTERIM IFR FLIGHT PROCEDURES 7-1-1 … 7-1-4. HIGH BAROMETRIC PRESSURE WARNING 7-1-3 … 7-1-5. TEMPORARY FLIGHT RESTRICTIONS 7-1-3 … 7-1-6. AIR DEFENSE EMERGENCY 7-1-4 … 7-1-7. SPECIAL DATA 7-1-5 … 7-1-8. LASER LIGHT ACTIVITY 7-1-5 …

Section 2. Cancellation/Expiration

7-2-1. FDC NOTAM EXPIRATION/CANCELLATION 7-2-1 … 7-2-2. FDC NOTAM LIST 7-2-1 … 7-2-3. RETRIEVING FDC NOTAMS 7-2-1 …

Chapter 8. Military NOTAMs

Section 1. General

8-1-1. MILITARY FACILITIES 8-1-1 … 8-1-2. SUBMISSION OF MILITARY DATA FOR PUBLICATION 8-1-1 … 8-1-3. MILITARY NOTAMS NOT MEETING CRITERIA 8-1-1 …

Section 2. Military NOTAM Dissemination

8-2-1. MILITARY NOTAMs 8-2-1 … 8-2-2. ALASKAN MILITARY NOTAMs 8-2-1 …

Section 3. Military NOTAM Retrieval

8-3-1. MILITARY NOTAM AVAILABILITY 8-3-1 … 8-3-2. RETRIEVING MILITARY NOTAMs 8-3-1 … 8-3-3. SERVICE MESSAGES 8-3-1 … 8-3-4. MILITARY NOTAM CRITERIA FOR MILITARY NOTAM SYSTEM 8-3-1 …

JO 7930.2Q CHG 1 05/26/16

v Table of Contents

Chapter 9. International NOTAMs

Section 1. General Procedures

Paragraph Page 9-1-1. INTERNATIONAL NOTAMs 9-1-1 … 9-1-2. INTERNATIONAL NOTAM DATA FORMAT 9-1-1 … 9-1-3. USNS­GENERATED SERVICE MESSAGES 9-1-2 …

Section 2. Procedures For Canadian NOTAMs

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

Appendices

APPENDIX A. INTERNATIONAL NOTAM (Q) CODES Appendix A-1 … APPENDIX B. NATIONAL WEATHER SERVICE (NWS) RADIOSONDE/

UNMANNED FREE BALLOON FLIGHTS Appendix B-1 … APPENDIX C. ICAO DIFFERENCE FOR THE UNITED STATES Appendix C-1 …

Section 1. Introduction

1−1−1 Introduction

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 Notices to Airmen (NOTAM) system does not duplicate data already published or charted. Originators of airmen information are expected to inform the National Flight Data Center (NFDC) 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

The primary audience for this order is any office responsible for originating NOTAMs. The secondary audience is those who use aeronautical information.

1−1−3. WHERE TO FIND THIS ORDER

This order is available on the Federal Aviation Administration (FAA) website at http://faa.gov/ air_traffic/publications and http://employees.faa.gov/tools_resources/ orders_notices/.

1−1−4. CANCELLATION

FAA Order JO 7930.2P, Notices to Airmen (NOTAM) dated April 3, 2014 and Changes, 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, Safety and Operations Policy Group.

1−1−6. DISTRIBUTION

This order is distributed to selected offices in Washington headquarters, service area offices, the William J. Hughes Technical Center, the Mike Monroney Aeronautical Center, and air traffic operations field offices and facilities.

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), General Notices (GENOTs), and order changes. Changes/orders are published on the publications cycle.

b. Any changes to this order must be submitted to the Air Traffic Procedures Directorate.

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.

3. Procedural changes will not be made to this order until the operational system software has been adapted to accomplish the revised procedures.

1−1−8. EFFECTIVE DATE

This order is effective December 18, 2015.

1−1−9. RELATED PUBLICATIONS

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.20D, DoD Notice to Airmen (NOTAM) System. JO 7110.10, Flight Services Technical Operations – 6000.15, General Maintenance Handbook for NAS

05/26/16 JO 7930.2Q CHG 1

1−1−2 Introduction

Facilities – 8200.1, U.S. Standard Flight Inspection Manual. Flight Standards –8260.19, Flight Procedures and Airspace FAA Order 5010.4, Airport Safety Data Program JO 7210.3, Facility Operations and Administration JO 7400.2, Procedures for Handling Airspace Matters JO 7400.8, Special Use Airspace 14 CFR Parts – 77, Safe, Efficient Use, and Preservation of the Navigable Airspace

– 139, Certification of Airports – 57, Notice of Construction, Alteration, Activation and Deactivation of Airports – 171, Non-Federal Navigation Facilities AC 150/5200−28, Notices to Airmen (NOTAMs) for Airport Operators AC 150/5300-18B, General Guidance and Specifications for Submission of Aeronautical Surveys to NGS: Field Data Collection and Geographic Information System (GIS) Standards ICAO Annex 15

Section 2. Scope

1−2−1 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 authority ensuring NOTAM formats. To ensure NOTAMs are issued consistent with NOTAM policy, submitters must comply with USNOF personnel directions.

b. All NOTAMs will be processed, stored, and distributed by the United States NOTAM System (USNS).

c. 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, 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, 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, wildlife hazards, and meteorological equipment (wind indicators) or services.

5. OBST (Obstructions). Keyword used to describe a temporary change or hazard caused by a moored balloon, kite, tower, crane, stack, obstruction, 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 communication outlet commissioning, decommissioning, outage, unavailability, and air-to-ground frequencies.

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.

9. AIRSPACE (Airspace). Keyword used to describe an airspace restriction or activity warning which impacts, restricts, or precludes use of airspace.

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.

1−2−2 Scope

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. ROUTE (Route). Keyword used to describe a temporary change or hazard or change associated with published ATS routes and related information.

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

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

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

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

Section 3. Accountable Organizations

1−3−1 Accountable Organizations

Section 3. Accountable Organizations

1−3−1. AIR TRAFFIC ORGANIZATION

a. All air traffic 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 personnel must accept all aeronautical information regardless of source or subject matter, provided the occurrence is no more than three 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 Safety and Operations Policy Group.

g. Mission Support Services, Aeronautical Navigation Products (AeroNav Products) 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), and special instrument flight procedures. AeroNav Products may originate NOTAMs regarding navigational aid (NAVAID) restrictions in accordance with FAA Order 8200.1, United States Standard Flight Inspection Manual.

h. Mission Support Services, Airspace Services, is responsible for the development of policy guidance regarding standard terminal arrival routes (STAR). STAR NOTAMs are originated by the Air Route Traffic Control Center (ARTCC) (See paragraph 7-1-4f).

i. 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. USNOF will forward unresolved issues to the Flight Services Program Operations for clarification and further action. The USNOF is responsible for operating the NOTAM system. USNOF originates NOTAMs, as needed. (See paragraph 4-1-2, National NOTAM Office Relationships for more detail)

NOTE− NOTAM office phone numbers: (888) 876-6826; (540) 422-4262. FAX number is (540) 422-4298.

1−3−2. TECHNICAL OPERATIONS SERVICES

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

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

1−3−2 Accountable Organizations

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

c. Submitting approval requests for routine maintenance shutdowns sufficiently in advance to assure that approval will be received with ample time for issuance of a NOTAM five hours before a shutdown will occur.

1−3−3. FLIGHT INSPECTION SERVICES

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.

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

The Office of Airport Safety and Standards is responsible for enforcing the airport management responsibilities as outlined in the Code of Federal Regulations (CFR).

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

1−3−5. FLIGHT STANDARDS SERVICE

The 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 is contained in FAA Order 8260.19, Flight Procedures and Airspace, and 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

1−3−6. 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−4−1 Terms of Reference

Section 4. Terms of Reference

Section 4. Terms of Reference

1−4−1. WORD MEANINGS

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. “Will” indicates futurity, not a requirement for application of a procedure.

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

f. Singular words include the plural.

g. Plural words include the singular.

h. Miles means nautical miles unless otherwise stated.

i. Feet means mean sea level unless otherwise stated.

j. Time is shown in Universal Coordinated Time (UTC) unless otherwise stated, as in the body of Temporary Flight Restrictions.

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 this order contain the keyword and the subject of the NOTAM. All other data is assumed from the NOTAM sentence structure and are 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 para-

graph’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 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 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.

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

1−4−2 Terms of Reference

e. Certified Airport. An airport certificated under 14 CFR Part 139. These airports are so indicated in the Chart Supplement U.S.

f. Certified Source. The party who enters/submits a NOTAM to the USNS using an approved direct entry tool or interface

g. Distribution. Forwarding of NOTAM information from the USNS to NADIN.

h. 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.1NM from AML VOR/DME).

i. 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 USNS, beginning with 0001 each year. The year of issuance and the serial number are separated by a forward slash; for example, 5/1323.

j. International NOTAM. The classification of NOTAMs received from other counties and stored in the US NOTAM System. 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/15, S0002/15.

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

l. Military NOTAM. The classification of NOTAMs issued by the U.S. Air Force, Army, Marine, Navy, and Coast Guard against navigational aids and airports. These NOTAMs are numbered consecutively by accountability, location, and series beginning with S0001 each year, where S stands for a generic series the military may have. The NOTAM number and year of issuance are separated by a forward slash; for example, S0211/15, S0002/15.

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

n. 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 U.S. NOTAM Ds are numbered consecutively each month by the USNS 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.

o. NOTAM Originator. The party (airport, Tech Ops, AIS/Service Provider, FSS, etc.) who submits a NOTAM to the USNS using an approved interface and is accountable for the NOTAM coordination.

p. Out of Service. When a piece of equipment, a system, a facility or a service is not operational, certified (if required) and immediately “available” for air traffic or public use.

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

r. Prior Permission Required (PPR) means prior permission required to have full operational use of a runway, taxiway, apron, or airport facility/service.

s. Supplement (Alaska, Pacific).

1. Alaska. This chart supplement is a joint civil-military flight information publication designed for use with other flight information publications, en route charts, Alaska Terminal publication, USAF TACAN charts covering Alaska and portions of southwestern and northwestern Canada, World Aeronautical Charts, and sectional aeronautical charts. The Supplement contains a Chart Supplement U.S. of all airports (including certificated (14 CFR Part 139) airports shown on en route charts and those required by appropriate agencies), communications data, navigational facilities, special notices, and procedures applicable to the area of chart coverage.

2. Pacific. This chart supplement is a civil flight information publication, designed for use with flight information publications, en route charts and the sectional aeronautical chart covering the State of Hawaii and that area of Pacific served by U.S. facilities. The Supplement contains a Chart Supplement U.S. of all airports (including

3/15/07 7110.65R CHG 2 JO 7930.2Q CHG 1 05/26/16

1−4−3 Terms of Reference

certificated (14 CFR Part 139) airports open to the public and those requested by appropriate agencies), communications data, navigational facilities, special notices and procedures applicable to the Pacific area.

t. Taxilanes. Designed for low speed and precise taxiing. Taxilanes are usually, but not always, located outside the movement area, providing access (to and) from taxiways (usually an apron taxiway) to (and from) aircraft parking positions and other terminal areas.

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

v. United States NOTAM System. The United States NOTAM System (USNS) is a safety-critical system that collects, maintains and distributes NOTAMs for the aviation community.

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

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

05/26/16 JO 7930.2Q CHG 1

Section 1. Aeronautical Information System

2−1−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 a telecommunication system and will be 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 (DPs).

(b) Standard Terminal Arrivals (STARs).

(c) Standard Instrument Approach Procedures (SIAPs).

3. VFR Charts:

(a) Sectional Aeronautical Charts.

(b) Terminal Area Charts (TAC).

(c) World Aeronautical Charts (WAC).

b. Flight information publications outlining baseline data:

1. Notices to Airmen Publication (NTAP).

2. Chart Supplement U.S.

3. Pacific Chart Supplement.

4. Alaska Supplement.

5. Alaska Terminal.

6. Aeronautical Information Manual (AIM).

2−1−3. PUBLICATION CRITERIA

The following conditions or categories of information should be forwarded to the National Flight Data Center (NFDC) for inclusion in the flight information publications and charts. Time critical delays, corrections, or changes to 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, 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 decommissioned.

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.

05/26/16 JO 7930.2Q CHG 1

2−1−2 Aeronautical Information System

2−1−4. NOTICES TO AIRMEN PUBLICATION

a. NTAP is published by Mission Support Services, Standards and Procedures Support, every 28 days.

b. Data of a permanent nature can be published in the Notices to Airmen Publication as an interim step between publication cycles of the Chart Supplement U.S. and aeronautical charts.

c. The Notices to Airmen Publication is divided into four parts:

1. Notices in Part 1 are provided by ATC Products and Publications. This part contains selected FDC NOTAMs that are expected to be in effect on the effective date of the publication. This part is divided into three sections:

(a) Section 1, Airway NOTAMs, reflecting airway changes that fall within an ARTCCs airspace.

(b) Section 2, Procedural NOTAMs.

(c) Section 3, General NOTAMs, containing NOTAMs that are general in nature and not tied to a specific airport/facility (for example, flight advisories and restrictions, open duration Special Security Instructions and Special Flight Rules Area.

2. Part 2, provided by NFDC, contains Part 95 Revisions, Revisions to Minimum En Route IFR Altitudes and Changeover Points.

3. Part 3, International NOTAMs, is divided into two sections.

(a) Section 1, International Flight Prohibitions, Potential Hostile Situations, and Foreign Notices.

(b) Section 2, International Oceanic Airspace Notices.

4. Part 4, Graphic Notices, compiled by ATC Products and Publications from data provided by FAA service area offices and other lines of business, contains special notices and graphics pertaining to almost every aspect of aviation; such as, military training areas, large scale sporting events, air show information, Special Traffic Management Programs (STMPs) and airport−specific information. This part is comprised of 6 sections:

(a) Section 1, General.

(b) Section 2, Special Operations.

(c) Section 3, Airport and Facility Notices.

(d) Section 4, Major Sporting and Entertainment Events.

(e) Section 5, Airshows.

(f) Section 6, Special Notices.

NOTE− Notices in Parts 3 and 4 of the NTAP are submitted to and processed through ATC Products and Publications, not NFDC. Cutoff dates and requirements for notices in Parts 3 and 4 are in the NTAP.

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

a. Managers must review each edition of the Notices to Airmen Publication, the Chart Supplement U.S., and other publications and charts to ensure that all required data is included and correct. Inform NFDC promptly of errors or omissions in any publication or chart. Notification of errors in the NTAP parts three and four should be sent to ATC Products and Publications.

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 NFDC. NFDC 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 U.S.

c. When time does not permit notification to NFDC by mail, forward the data via administrative message, FAX, or contact the appropriate NFDC section by telephone during administrative hours.

3/15/07 7110.65R CHG 2 JO 7930.2Q CHG 1 05/26/16

2−1−3 Aeronautical Information System

d. Information received by NFDC for publication that meets publication criteria and will be current on the effective date of the next available AFD publication or aeronautical chart will be published.

2−1−7. ADDRESSING CORRESPONDENCE

Federal Aviation Administration Aeronautical Information Services 1575 I Street, NW. Washington, D.C. 20005

2−1−8. NFDC ORGANIZATION

The NFDC is divided into the following sections listed below. Questions and data should be referred directly to the appropriate section.

a. Airports and NAVAIDs Section telephone: (202) 385−7474.

b. Procedures and Airspace Section, telephone: (202) 385−7473.

c. Cartographic Standards Section, telephone: (202) 385−7456.

d. Aeronautical Information Management:

1. Toll Free: (866) 295-8236

e. Web Page: https://nfdc.faa.gov.

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

The NFDD is used to transmit data from NFDC 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−10. 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.

Section 2. NOTAM System

2−2−1 NOTAM System

Section 2. NOTAM System

2−2−1. NOTAM CLASSIFICATION

When changes occur so rapidly that time does not permit issuance on a chart or in an appropriate publication, they are publicized as NOTAMs. Originators of airmen information are expected to inform the NFDC in sufficient time before the effective dates of changes to permit publishing of aeronautical data on the various charts or in the appropriate publications. NOTAMs are classified into four groups in accordance with instructions in this order. The groups are:

a. NOTAM D. Information that meets the criteria of this order and requires wide dissemination via telecommunication and pertains to en route navigational aids, civil public-use airports listed in the AFD, facilities, services, and procedures.

b. FDC NOTAM. Flight information that is

normally regulatory in nature including, but not limited to, changes to IFR charts, procedures, and airspace usage.

c. Pointer NOTAM. Issued by a flight service station to highlight or point out another NOTAM; such as an FDC or Parachute Jump Exercise (PJE) NOTAM. This type of NOTAM will assist users in cross-referencing important information that may not be found under an airport or NAVAID identifier. Keywords in pointer NOTAMs must match the keywords in the NOTAM D that is being pointed out. Keywords in pointer NOTAMs related to temporary flight restrictions (TFR) must be AIRSPACE. (See chapter 6 for an example.)

d. Military NOTAM. NOTAMs pertaining to U.S. Air Force, Army, Marine, Navy, and Coast Guard navigational aids/airports that are part of the NAS.

Section 1. General

3−1−1 General

Chapter 3. General Operating Procedures

Section 1. General

3−1−1. TIE−IN STATIONS

a. Flight Service Program Office 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.

b. Letters of agreement between facilities or other agencies and the FSS should be executed to assure proper handling of NOTAMs.

c. The tie−in FSS is responsible for forwarding the NOTAM data to the NFDC for publication in accordance with the procedures in this order.

3−1−2. NOTAM RESPONSIBILITIES

a. The party that enters the NOTAM data is responsible for classifying, formatting, canceling, 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 office which receives information is responsible for the accuracy, currency, and validity of the NOTAM. When an office 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 JO 7930.2, Para 5−1−2 , Handling Reported Aerodrome Conditions

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

REFERENCE− FAA Order JO 7930.2, Para 6−1−2 Special Activity Airspace (SAA)

3−1−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/ DTG, and Canceled 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 Canceled 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 you receive an FDC NOTAM and the previous number(s) have not been received, obtain the NOTAM on request-reply.

REFERENCE− FAA Order JO 7930.2, Para7−2−3 Retrieving FDC NOTAMs

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

a. The USNS must send Title 14 CFR, Part 91, Section 139, Emergency Air Traffic Rules; Section 141, Flight Restrictions in the Proximity of the

3−1−2 General

Presidential and Other Parties; Part 99, Section 7, Special Security Instructions NOTAMs; and any revisions, modifications, or cancellations, directly to all flight service stations via NADIN using the flight service group address of “KXXXAFSS.”

b. Upon receipt of these messages, the watch supervisor at each flight service station hub or parent facility must ensure that the NOTAM is received at each of their subordinate facilities. The hub or parent facility must send notification within 15 minutes by receipt message to “KDZZNAXX.” The receipt message must include:

1. R or RGR.

2. The FDC number, including the letters FDC.

3. The initials of the watch supervisor.

NOTE− Only the hub or parent facility need to acknowledge the NOTAM. For automation processing, the receipt message must adhere to the following format: R FDC 4/1234 XX

c. The USNOF must make a record of all receipt messages received.

d. If no receipt message is received by the USNOF within 90 minutes of issuance of the FDC Presidential, Special Security Instructions, or Emergency Air Traffic Rules NOTAM, the USNOF will

follow−up with a phone call to the facility watch supervisor.

e. The watch supervisor of the flight service station must be responsible for:

1. Logging the Presidential, Special Security Instructions, or Emergency Air Traffic Rules FDC NOTAM in the facility log.

2. Notifying the specialists on duty that a Presidential, Special Security Instructions, or Emergency Air Traffic Rules FDC NOTAM has been issued.

3. Putting the Presidential, Special Security Instructions, or Emergency Air Traffic Rules FDC NOTAM in the facility status information area.

4. As part of the FSS supervisor’s watch checklist, the watch supervisor must check the FDC list that is issued by the USNOF to ensure that every Presidential, Special Security Instructions, or Emergency Air Traffic Rules FDC NOTAM has been received in the facility.

NOTE− The purpose of this procedure is to ensure that: 1. All flight service specialists know about the Presidential, Special Security Instructions, or Emergency Air Traffic Rules TFRs so that pilots are briefed appropriately. 2. All affected air traffic facilities receive immediate notification when these TFRs are issued.

Section 2. Coordination

3−2−1 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-800-WX-BRIEF) prior to 3 days before the expected condition is to occur. A NOTAM must be transmitted as soon as practical but not more than 3 days before the expected condition is to occur.

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

a. Before closing, part-time facilities must give the following NOTAM data to the FSS responsible for handling their NOTAMs during the period the facility is closed:

1. Any known NOTAMs that will require dissemination during the hours the facility is closed.

2. All current NOTAMs.

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

3−2−4. NON−FEDERAL FACILITIES

a. NOTAMs on non-Federal facilities that are part of the NAS are distributed through the FAA NOTAM system. Letters of agreement covering FSS notification procedures for these facilities should be executed whenever possible. The owner/sponsor or non-Federal technician must contact the appropriate Certified Source to ensure the NOTAM is originated

REFERENCE− 14 CFR Part 171 and FAAO 6700.20, Non-Federal Navigational Aids and Air Traffic Control Facilities, 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 the appropriate Technical Operations Control Center as well as Aeronautical Information Services.

Section 3. Use of Terms

3−3−1 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, 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, a hyphen may be used 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. The Pilot/Controller Glossary must be used to define terms in the NOTAM system.

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

e. Contractions and abbreviations published on instrument flight procedure charts may be used 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.

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, and must be stated in 10 digits for the year, month, day, hour, and minute (YYMM- DDHHMM).

c. Sunrise-Sunset (SR-SS) is allowed when describing a daily schedule.

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 20MIN 1HR 330DEG 402646N0795856W 402646.25N0795856.95W

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

The use of virgules should be limited to separate runway pairs (RWY 3/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 0.

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

c. Use runway pair when applicable.

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

EXAMPLE− RWY 3/21 RWY 3 RWY 21

e. Parallel runways are differentiated by using the runway designators.

EXAMPLE− RWY 03L RWY 03C RWY 03R

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

3−3−2 Use of Terms

EXAMPLES− …RWY NE/SW CLSD…

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.

EXAMPLE− …TWY PARL TWY ADJ RWY 09/27 CLSD… …TWY PARL TWY CLSD…

NOTE− One unnamed parallel taxiway exists at this airport.

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 C HELIPAD 3 CLSD…

b. Keyword TWY may be followed by designator “ALL.”

EXAMPLES− …TWY ALL CLSD…

…TWY ALL EDGE LGT WEST OF RWY 16L/34R OUT OF SERVICE…

…TWY ALL EDGE LGT OUT OF SERVICE…

NOTE− This can also be used when an airport has only one taxiway or apron. See Paragraph 4-2-1, NOTAM Composition.

c. For multiple taxiways, each taxiway need not be prefaced with contraction TWY;

1. Taxiway segments must be separated from each taxiway or taxiway segment with a comma and preceded by contraction TWY followed by the taxiway designator. The use of “BTN” and “AND” signifies a segment, such as TWY B BTN TWY B10 AND TWY B8. A hyphen used in a TWY NOTAM indicates all taxiways between the first and last descriptors.

EXAMPLE− …TWY B3,C CLSD… …TWY A1-A6 CLSD…

NOTE− The example includes taxiways A1, A3, A5 and A6. …TWY F AT INT TWY C CLSD…

2. Multiple segments separated by commas share the same condition for example: CLSD or WIP (work in progress) SN REMOVAL.

EXAMPLE− …TWY B1, B2, F, TWY B BTN TWY B10 AND TWY B8 CLSD… …TWY C BTN APCH END RWY 04R AND 350FT SOUTH APCH END RWY 04L CLSD…

NOTE− The originator may originate multiple NOTAMs to ensure clarity.

3−3−7. APRON IDENTIFICATION

a. Identify aprons with the prefix APRON followed with the apron designator.

EXAMPLES− …APRON TERMINAL RAMP FICON PATCHY THIN WET SN… …APRON MAIN TAXILANE C CLSD… …APRON ALL CLSD…

NOTE− “ALL” is used to describe every APRON at an airport OR can be used for an airport with a single APRON.

…APRON MAIN RAMP HELIPAD A1 CLSD…

NOTE− This example describes a helipad that resides on the Main Ramp.

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 CLSD…

3−3−8. STANDARD NOTAM PHRASES

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

3−3−3 Use of Terms

UNL (unlimited)

TO POINT OF ORIGIN OBSC (obscured)

UNREL (unreliable)

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)

OUT OF SERVICE FLAGGED AND LGTD ADJ (adjacent)

NONMOVEMENT

AREA

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.

Section 1. General

4−1−1 General

Chapter 4. NOTAM D Procedures

Section 1. General

4−1−1. ACCEPTING NOTAM D INFORMATION

FSS facilities must accept and document all aeronautical information regardless of source, provided the occurrence is no more than 3 days in the future. Information from other-than-authorized authorities must be verified prior to NOTAM issuance.

4−1−2. NATIONAL NOTAM OFFICE RELATIONSHIPS

a. The USNOF is charged with monitoring the USNS. The USNOF must monitor the NOTAM system 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 USNOF is the authority to ensure NOTAM formats. To ensure NOTAMs are issued consistent with policy, NOTAM originators and certified sources must comply with USNOF personnel guidance.

b. Discrepancies in procedures or format must be recorded, and Aeronautical Information Management must forward a list of the discrepancies to Flight Services, Safety and Operations Support, Operational Procedures, and the service area office.

c. 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 Products Office under the Flight Standards Service policy contained in FAA Order 8260.19, chapter 2, section 6. 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.

Section 2. Preparing NOTAMs for Dissemination

4−2−1 Preparing NOTAMs for Dissemination

Section 2. Preparing NOTAMs for Dissemination

4−2−1. NOTAM COMPOSITION

NOTE− For FDC NOTAM examples, see chapter 7.

a. 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 (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 5NM Radius of the airport.

(b) The nearest VOR when any of the activity is more than 5NM from the nearest public use airport but completely within 25NM 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.

6. Surface segment (when needed).

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

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) Heights AGL may be added when required or when MSL is not known, for example, SFC-450FT AGL.

10. Condition. The changed condition or status being reported, when needed. When the conditions includes 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.

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. For example : 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 should be used.

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 “-.”

(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

4−2−2 Preparing NOTAMs for Dissemination

will expire at the end of validity time regardless of EST. FDC NOTAMs relating to instrument flight procedures must not be canceled and reissued. (Reference FAA Order 8260.19, chapter 2, section 6.)

(b) When a NOTAM is originated to advertise a permanent condition that will be published in a publication, chart or database (see paragraph 4-4-3), “PERM” should be inserted as the expiration date in lieu of a 10-digit date-time group. In addition, PERM is used as the end of validity in lieu of a 10-digit date–time-group for certain NOTAMs that pertain to or support national security, law enforcement, and aviation security requirements and for NOTAMs that contain flight prohibitions for U.S. operators and U.S. airmen regarding operations in particular areas of non-U.S. controller airspace due to weapons-related hazards or other hostile threats to civil aviation, regardless of whether the NOTAM will be published in a publication, chart, or database. The NOTAM originator is responsible for canceling the NOTAM upon publication, as PERM will not auto-expire.

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

b. NOTAMs issued when the condition of a number of facilities, NAVAIDs, services, or landing areas/runways are related to the same event (for example, date/time, facility closing, part−timing, runway closures, etc.) must be issued as separate NOTAMs.

c. Each NOTAM concerning a specific aid, service, or hazard must be a complete report including all deviations unless reference is made to other restrictions already published.

d. If information is published elsewhere and is still valid, reference must be made to that publication with the statement, “PLUS SEE (publication).” A NOTAM issued not stating “PLUS SEE (publication)” indicates the NOTAM replaces previously published similar data.

e. NOTAMs must state the abnormal status of a component of the NAS and not the normal status. The only exception is for data that has been published and is being replaced; for example, RWY 9/27 OPEN.

4−2−2. NOTAM ACCOUNTABILITY

Maintain separate accountability (NOTAM file) for each location whose weather report is disseminated via WMSCR and for the location of the tie-in FSS.

a. Issue NOTAMs for an FAA-monitored weather reporting location whose report is disseminated via WMSCR under the location identifier of the weather report.

b. Issue all other NOTAMs under the location identifier of the tie-in FSS. This includes NOTAMs for weather reporting locations whose report is not disseminated via WMSCR.

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

c. Make NOTAM accountability changes by mail, 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 USNS tables have been changed. Notify Aeronautical Information Services of any NOTAM accountability changes.

Section 3. Coding and Transmission of NOTAMs

4−3−1 Coding and Transmission of NOTAMs

Section 3. Coding and Transmission of NOTAMs

4−3−1. PREPARATION FOR TRANSMISSION

In order to ensure that NOTAMs are processed and distributed properly, data for transmission must be coded as prescribed in this order.

4−3−2. AUTOMATIC DATA PROCESSING (ADP) CODES

The ADP equipment is programmed to accept and begin processing a NOTAM upon receipt of the ADP code, which is an exclamation point (!).

4−3−3. NOTAM TRANSMISSION

a. The following examples illustrate the proper coding of NOTAM data for transmission by stations entering their own NOTAM data in the system.

EXAMPLE− AISR Format: GG KDZZNAXX DDHHMM KPIRYFYX !PIR PIR NAV VOR OUT OF SERVICE EFFECTIVE-EXPIRATION

b. The following example illustrates the proper coding of NOTAM data for transmission by a station entering NOTAM data into the system for a tie-in location.

EXAMPLE− AISR Format: GG KDZZNAXX DDHHMM KPIRYFYX !EKN W22 AD AP CLSD EFFECTIVE-EXPIRATION

c. When two or more new NOTAMs or cancellations, or combinations of new NOTAMs and cancellations are transmitted in the same message, they must be separated by the ADP code and a new line.

EXAMPLE− AISR Format: GG KDZZNAXX DDHHMM KABQYFYX !ABQ C04/003 !ABQ ABQ RWY 8/26 CLSD EFFECTIVE-EXPIRATION !ABQ C02/057

NOTE− No confirmation will be received on cancellations.

4−3−4. TRANSMISSION OF NOTAMs EXCEEDING 20 LINES

If the text of a NOTAM is expected to exceed 20 lines, you must call the USNOF (1−888−876−6826) for assistance in composition and guidance.

4−3−5. CONFIRMING ACCEPTANCE BY THE NOTAM SYSTEM

a. When a new NOTAM is accepted into the NOTAM file, a copy of the NOTAM with the NOTAM number will be returned back to the originating facility and sent to WMSCR for distribution.

EXAMPLE− (Confirmation)

GG KDENYFYX DDHHMM KDZZNAXX !DEN 04/003 DEN NAV VOR OUT OF SERVICE EFFECTIVE-EXPIRATION

b. If the NOTAM is rejected, a USNS-generated service message will be relayed back to the facility of origin indicating the reason for rejection as shown in Paragraph 4−5−2, NOTAM Service Messages.

4−3−6. TRANSMISSION BY ANOTHER FACILITY

When unable to transmit a NOTAM directly into the system due to equipment failure or other situation, relay the information to an FSS and request that the data be transmitted into the system.

4−3−7. RETRIEVING DOMESTIC NOTAMs

Domestic NOTAMs must be retrieved via National Airspace Data Interchange Network (NADIN) using the following formats:

a. When the location identifier and number are known:

AISR Format: GG KDZZNAXX DDHHMM KTUSYFYX )SVC RQ DOM LOC=CID NT=02/020

4−3−2 Coding and Transmission of NOTAMs

b. When the accountability identifier and number are known:

AISR Format: GG KDZZNAXX DDHHMM KYNGYFYX )SVC RQ DOM ACC=FOD NT=03/040

c. To request all NOTAMs for a given location:

AISR Format: GG KDZZNAXX

DDHHMM KBZNYFYX )SVC RQ DOM LOC=DSM

d. To request all NOTAMs for a given accountability:

AISR Format: GG KDZZNAXX DDHHMM KBZNYFYX )SVC RQ DOM ACC=FOD

Section 4. Canceling/Extending NOTAMs

4−4−1 Canceling/Extending NOTAMs

Section 4. Canceling/Extending NOTAMs

4−4−1. EXTENDING NOTAM VALIDITY

a. 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−4−2. CANCELLATION OF NOTAMs

a. To cancel a NOTAM, use the same NOTAM/ serial number assigned to the original NOTAM by the USNS computer, preceded by the letter “C.” If the serial number of a NOTAM cancellation is invalid (number not in a master file), no action is taken within the NOTAM system. A cancellation must receive the same dissemination as the NOTAM it cancels. Do not carry the NOTAM text in the cancellation.

EXAMPLE− !ABC C05/005

b. Stations canceling NOTAMs must check the NOTAM data to ensure the NOTAM’s deletion. Retransmit cancellations not acted upon.

c. 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−4−3. CANCELING 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 current until the data is published in one or more of the following, with the exception of NAVAID NOTAMs, which must remain in effect until the NAVAID is returned to service or decommissioned:

1. Chart Supplement U.S.

2. En route low altitude charts.

3. En route 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 en route chart.

5. Supplements (Alaska and Pacific).

6. Charts (VFR):

(a) Sectional charts.

(b) World aeronautical charts.

(c) Terminal area charts.

c. The Notice to Airmen Publication (NTAP) conveys NOTAMs to the public until printed correctly on publications listed in subparagraph b above. The NTAP does not cancel NOTAMs but may supplement briefings. The NTAP must not be used as a basis to cancel NOTAMs.

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

05/26/16 JO 7930.2Q CHG 1

4−5−1 Computer−Generated NOTAM Service Messages

Section 5. Computer−Generated NOTAM

Section 5. Computer-Generated NOTAM Service Messages

Service Messages

4−5−1. MONITORING

a. All input transmissions from a facility are monitored by the USNS computer for the presence of an ADP code. The validity of the station identifier, format, and times are also checked before the USNS computer assigns a number and updates the NOTAM master file.

b. Errors in the station identifier or the format will result in a computer−generated service message being sent to the facility of origin. (See paragraph 4-5-2 for examples). The service message will identify the NOTAM parameter which was in error. A rejection (R) requires corrective action as soon as possible.

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

4−5−2. NOTAM SERVICE MESSAGES

If data is entered incorrectly, it will be rejected. Each rejection will be preceded with a service message (SVC) explaining the cause for the rejection. Below are some examples of the type of reject messages received.

a. Invalid accountability location for a specific affected facility and missing keyword.

EXAMPLE− GG KCLEYFYX DDHHMM KDZZNAXX !SVC LOCATION NOT VALID FOR CLE CLE OMN FUEL NOT AVBL EFFECTIVE-EXPIRATION

b. Invalid NOTAM accountability location.

EXAMPLE− GG KRDUYFYX DDHHMM KDZZNAXX !SVC NOTAM D ACCOUNTABILITY NOT FOUND NLN LNN RWY CLSD EFFECTIVE-EXPIRATION

c. Invalid affected location.

EXAMPLE− GG KCLEYFYX DDHHMM KDZZNAXX

!SVC NOTAM (D) LOCATION NOT FOUND CLE VBV RWY 4 CLSD EFFECTIVE-EXPIRATION

d. Invalid input format.

EXAMPLE− GG KDRIYFYX DDHHMM KDZZNAXX !SVC INVALID SPACE BEFORE ACCOUNTABILITY

e. Missing FICON

EXAMPLE− GG KDRIYFYX DDHHMM KDZZNAXX !MISSING FICON JNU JNU APRON ALL PATCHY 1/2IN SLUSH 12IN SNOWBANK BA FAIR OBSERVED AT…

f. Unclear times.

EXAMPLE− GG KCOUYFYX 081822 KDZZNAXX

!UNCLEAR DURATION OR EFFECTIVE TIME MCI MCI NAV VOR OUT OF SERVICE 1301251330-1301251500EST

NOTE− The NOTAM was inserted after 1330 on the 25th of January and the NOTAM system cannot determine whether the NOTAM is for the present day after the fact. The NOTAM must be reissued with a new effective and expiration time.

EXAMPLE− GG KOAKYFYX 232323 KDZZNAXX !UNCLEAR DURATION OR EFFECTIVE TIME OAK OAK NAV DME OUT OF SERVICE 1301231630−1301230000

NOTE− The time of 0000 can only be used as an effective time. The NOTAM must be issued with a correct expiration time.

EXAMPLE− GG KCXOYFYX 191632 KDZZNAXX !UNCLEAR DURATION OR EFFECTIVE TIME CXO CXO AD AIRPORT CLSD 1301262300−1301261600

NOTE− Any NOTAM issued with an expiration time less than the beginning time must have a ten-digit date/time group later than the effective time.

Section 1. Movement Area NOTAMs

5−1−1 Movement Area NOTAMs

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.

EXAMPLE− !CLE CLE TWY L UNSAFE BREAKS IN ASPH 1512010001-1512312359

NOTE− As this is the first example, all elements are shown. Subsequent examples will begin with keyword and end prior to the schedule, unless it is deemed helpful for clarity. …RWY 16/34 UNSAFE DISABLED ACFT SE END…

NOTE− Only airport management can close any portion of an airport.

REFERENCE− 14 CFR Part 139

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 USNS. Subsequent to USNS 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.

EXAMPLE− …(U) RWY 07/25 UNSAFE ABANDONED VEHICLE…

5−1−3. MOVEMENT AREA INFORMATION

a. When the condition includes a limitation, follow the condition with “TO” or “EXC;” for example, “CLSD EXC SKI” or “CLSD TO TRANSIENT.”

b. Originate a NOTAM D for the following reported conditions:

1. Aerodrome conditions.

EXAMPLES− …AD AP CLSD… …AD AP CLSD TO TRANSIENT… …AD AP CLSD EXC SKI… …AD AP CLSD EXC 1HR PPR… …AD AP CLSD EXC PPR MON−FRI 0330−1430 1310120330-1310171430 …AD AP CLSD EXC HI−WING ACFT… …AD HELIPORT CLSD… …AD SEAPLANE BASE CLSD… …AD AP OPEN…

5−1−2 Movement Area NOTAMs

NOTE− OPEN is only an acceptable condition when the airport is published as being closed.

EXAMPLE− …AD AP NOW PUBLIC…

NOTE− This airport is now open to the public as a public-use airport.

EXAMPLE− …AD AP NOW PRIVATE…

NOTE− This airport is now closed to the public and is no longer a public-use airport. The NFDC must contact the USNOF to have the airport deleted from the NOTAM tables after the NOTAM has been canceled.

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

(a) Lighting status; for example, LGTD, NOT LGTD.

(b) Length and declared distances required for only runway commissioning.

TBL 5−1−1 Contractions

Movement Area - Surface:

ASPH asphalt/tar/macadam

CONC concrete

GRVL gravel/cinders

Movement Area - Lighting:

LGTD lighted

NOT LGTD unlighted

EXAMPLES− …RWY 01L/19R COMMISSIONED 10301FT X 150FT CONC LGTD. DECLARED DIST: RWY 01L TORA 10301FT TODA 10301FT ASDA 10301FT LDA 10301FT. RWY 19R TORA 10301FT TODA 10301FT ASDA 10301FT LDA 10301FT… …TWY M8 COMMISSIONED 500FT X 75FT CONC LGTD…

3. Closure of a movement area or portion thereof. Partial runway closures must be indicated by feet – E 500FT.

EXAMPLES− …APRON ALL CLSD… …APRON NORTH APN E 50FT CLSD… …TWY A3, A4, A5, TWY A BTN TWY A2 AND TWY A3

CLSD… …TWY ALL CLSD… …TWY B, C, D, TWY P BTN TWY EL AND TWY B, TWY P BTN TWY A AND TWY ER, TWY ER BTN RWY 17C/35C AND TWY Q CLSD… …RWY 36 CLSD… …RWY 02 FIRST 1000FT CLSD EXC TAX…

NOTE− The first 1000 feet for runway 02 is closed, except it is available for taxiing aircraft. This is used for single runway only. If both runways were affected, the NOTAM would state N 1000FT …RWY 06/24 CLSD EXC 1HR PPR 303−627−3001…

NOTE− Runways 06 and 24 are closed except by 1-hour prior permission from that telephone number during the times stated. …APRON NORTH APN CLSD RESURFACING…

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

EXAMPLES− …TWY C CLSD 1309041800-PERM

…RWY 17/35 CLSD 1310122330-PERM

(b) Temporary Nonmovement Area. If a taxiway is temporarily designated as Non Movement in a NOTAM, issue it as …TWY Y BTN TWY Q AND 10/30 NONMOVE- MENT AREA…

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

EXAMPLE− …RWY 18/36 CLSD TO JET…

NOTE− Runways 18 and 36 are closed to jet aircraft.

EXAMPLE− …RWY 09/27 CLSD EXC ACFT MORE THAN 13500LB…

NOTE− Runways 09 and 27 are closed to all aircraft weighing less than 13,500 pounds. Do not use class of aircraft when closing runways. Always use aircraft weight.

JO 7930.2P 4/3/ 14

7110.65R CHG 2 3/15/ 07 JO 7930.2Q 12/18/15

5−1−3 Movement Area NOTAMs

EXAMPLES− …RWY 10/28 E 3800FT CLSD TO ACFT LESS THAN 12500LB…

NOTE− Runways 10 and 28 east 3800 feet are closed to all aircraft weighing less than 12,500 pounds. …RWY 16/34 CLSD TO ACFT WINGSPAN MORE THAN 70FT AND TAIL HEIGHT MORE THAN 49FT…

NOTE− Runways 16 and 34 are closed to aircraft with a wingspan more than 70 feet and is also closed to aircraft with tail height more than 49 feet.

EXAMPLES− …RWY 05 CLSD TO LDG… …RWY 03 CLSD TO TKOF… …RWY 08/26 CLSD TO TGL… …RWY 01/19 CLSD EXC XNG…

5. Changes to usable runway length and declared distances.

(a) 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), accelerated 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.

EXAMPLES− …RWY 19 THR DISPLACED 300FT MARKING NOT STD. DECLARED DIST: TORA 6827FT TODA 6827FT ASDA 6827FT LDA 6527FT. …. …RWY 01 DECLARED DIST: TORA 6827FT TODA 6827FT ASDA 6527FT LDA 6527FT. …

NOTE− Runway 19 threshold is displaced 300 feet, therefore the Runway 19 landing LDA is shortened by 300 feet. The LDA and ASDA for Runway 1 are also shortened by 300 feet.

EXAMPLES− …RWY 05/23 NE 500FT CLSD. DECLARED DIST: RWY 05 TORA 7002FT TODA 7002FT ASDA 7002FT LDA 7002FT. RWY 23 TORA 7002FT TODA 7002FT ASDA 7002FT LDA 7002FT. …

NOTE− Construction on Runway 05 requires 500 feet to be closed to protect a construction area thus changing declared distances to Runways 05 and 23.

(b) 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.

EXAMPLE− …RWY 08/26 CHANGED TO 10000FT X 150FT. DECLARED DIST: RWY 08 TORA 9000FT TODA 9500FT ADSA 9000FT LDA 9000FT. RWY 26 TORA 9000FT TODA 9000FT ASDA 9400FT LDA 10000FT…. 6. Change of runway identification.

EXAMPLE− …RWY 13/31 CHANGED TO RWY 14/32…

7. Change of traffic pattern.

EXAMPLE− RWY 03L RIGHT TFC PATTERN

8. 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 out of service, issue a NOTAM using the keyword AD.

EXAMPLES− …RWY 10/28 RVR OUT OF SERVICE …

…AD AP RVR OUT OF SERVICE…

9. Surface Markings and Signage. Follow 4-2-1 b 1-3, including:

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

(b) Surface designator. Specify the designator of the surface on which the sign/marking is located.

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

(d) Name of sign/surface marking. Signs follow runway identification guidance.

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

(f) Condition. For example, NOT STD, NOT LGTD, OBSC, MISSING

(g) Follow 4-2-1 b 11-14 to complete the NOTAM.

4/3/14 JO 7930.2P

5−1−4 Movement Area NOTAMs

EXAMPLES− …AD AP SIGNS ALL OBSC… …RWY 21 4000FT DIST REMAINING SIGN NOT LGTD… …TWY U7 HLDG PSN SIGN FOR RWY 01L/19R NOT LGTD… …TWY ALL SFC PAINTED HLDG PSN SIGNS NOT STD DUE TO REPAINTING… …RWY 01/19 MARKING NOT STD…

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

(a) When SNOWBANKS, BERMS, DRIFTS, WINDROWS and SN PILES are not on the movement areas, they may be issued without the FICON descriptor.

(b) When it is determined that no surface condition reports will be taken for longer than a 24-hour period, issue a single NOTAM (Keyword AD) for the entire time-period. Use the phrase “SFC CONDITIONS NOT REPORTED”, as this differs from Conditions Not Monitored.

EXAMPLES− …RWY 01/19 3FT SNOWBANKS ADJ… …APRON MAIN RAMP 6FT SN PILES ADJ E SIDE… …TWY A 3FT SNOWBANKS NORTH 500FT… …AD AP SFC CONDITIONS NOT REPORTED… …RWY 31C ENGINEERED MATERIAL ARST SYSTEM NOT STD… …RWY 31C ENGINEERED MATERIAL ARST SYSTEM OUT OF SERVICE… …AD AP CARIBOU NEAR MOVEMENT AREAS… …AD AP BIRD ACT INCREASED NW SIDE… …RWY 02R/20L S 2600FT FROST HEAVES… …RWY 12/30 NUMEROUS 5IN CRACK… …RWY 01/19 SAFETY AREA BTN TWY C AND TWY B IRREGULAR SFC… …RWY 01/19 SOFT…

NOTE− Runway 01/19 is a turf runway that gets soft during the melting of snow or rainy seasons. …RWY 06/24 W 1000FT IRREGULAR SFC 4IN DPT X 12IN WID X 24FT LEN…

NOTE− In this example, the irregular surface affects the west 1000ft and is 4 inches deep, 12 inches wide and 24 feet long- within the surface itself. NOTAM format for

temporary field conditions (FICON) caused by weather phenomena are covered in Paragraph 5-1-4, Reporting of Field Conditions.

5−1−4. REPORTING FIELD CONDITIONS

Field condition (FICON) NOTAMs are used to report surface conditions, braking action, and friction values on runways, taxiways, and aprons/ramps. Keyword AD must not be used with descriptor FICON, except for Heliport.

a. FICON. Insert “FICON” after the surface designator(s) and surface segments, and before the field condition.

b. Pilot-reported field conditions. During periods when field conditions are not being monitored, a FICON NOTAM may be originated for a pilot-reported condition. The words “PILOT REPORTED” must precede the word “FICON.”

REFERENCE− AC 150/5200−28, Notices to Airmen (NOTAMs) for Airport Operators

c. Reporting surface conditions.

1. Coverage. 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. The term “PATCHY” can be used to describe either a layered or a non-layered contaminant. For example: “patchy wet snow”; “patchy wet snow over ice” – patchy indicates both layers.

2. Use the term “DRY” to describe a surface that is neither wet nor contaminated. A FICON NOTAM must not be originated for the sole purpose of reporting a dry runway. A dry surface must be reported only when there is need to report conditions on the remainder of the surface or when reporting segments of the runway surface as being dry when other contaminants are present.

3. Use the term “WET” to describe a surface that is neither dry nor contaminated but has visible dampness, moisture, and/or water less than ⅛ inch in depth or less. “WET” can also be reported as a standalone contaminant. .

4. A surface condition must be reported in each FICON NOTAM when reporting the condition on any part of the surface; for example, edges, remaining length.

d. Reporting contaminant depths.

5−1−5 Movement Area NOTAMs

1. Other than “WET”, use the word “THIN” for reporting contaminant depths of ⅛ inch or less.

2. Water is only reported as greater than ⅛ inch depth.

3. Specify the contaminant in feet and inches.

TBL 5−1−2 Reportable Depth Measurements

Use value “THIN” to report ⅛ inch

Use value “1/4IN” to report > ⅛ inch to and including ¼ inch

Use value “1/2IN” to report > ¼ inch to and including ½ inch

Use value “3/4IN” to report > ½ inch to and including ¾ inch

Use value “1IN” to report > ¾ inch to and including 1 inch

(a) 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.

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

(c) The runway contaminants for which depth is mandatory when reporting runway surface conditions are specified in TBL 5−1−3. Part 139/Federally obligated airports are required to report depth on taxiways and aprons. It is optional for other airports to report depths on taxiways and aprons.

e. Reporting the contaminants.

1. Only the contaminants marked with an “*” are to be accompanied by a depth. When reporting a runway condition, a depth is mandatory with those contaminants marked by an asterisk, “*”, in TBL 5−1−3.

TBL 5−1−3 Reportable Contaminants

Wet

Water* (⅛ inch and greater)

Frost

Slush*

Ice

Wet ice

Water* over ice

Wet snow*

Wet snow* over ice

Dry snow*

Dry snow* over ice

Slush* over ice

Compacted snow

Water* over compacted snow

Wet snow* over compacted snow

Dry snow* over compacted snow

Ash*

Mud*

Rubber

Oil

Sand

REFERENCE− AC 150/5200−28, Notices to Airmen (NOTAMs) for Airport Operators

2. PLOWED, SWEPT. The terms “PLOWED” and “SWEPT” are used when indicating that a portion of a surface has been plowed or swept and is different than the surrounding area. When known, the surrounding area items will be specified as RE- MAINDER and listed after the PLOWED or SWEPT information. PLOWED and SWEPT are omitted when the entire runway, taxiway, or apron has been plowed.

3. Use the term “SANDED” after the surface contaminant to report when a surface has been treated with sand.

4. Use the terms “DEICED LIQUID” or “DEICED SOLID” after the surface contaminant to report the presence of liquid or solid deicing material, as this may have operational significance to the pilot. DEICED LIQUID/SOLID is acceptable.

5. Use the term “DRIFT” to describe one or more drifts. When the drifts are variable in depth, report the greater depth.

6. Use the terms “SNOWBANKS,” “BERMS,” “SN PILES” or “WINDROWS” after the surface condition. Snowbanks must be assumed to be at the edge of a movement surface or, when plow/sweeper is used, at the edge of the plowed/swept area.

7. Use the term “RUTS” to report ruts in a contaminant after the surface contaminant.

8. Use the word “REMAINDER” to provide additional information about the surface condition.

4/3/14 JO 7930.2P 4/3/14 JO 7930.2P

5−1−6 Movement Area NOTAMs

For example, the runway surface conditions vary significantly on one end of the runway or a runway has been treated, resulting in differing field conditions on the untreated parts of the surface.

f. Observation time. Every FICON NOTAM must have the time that the conditions were observed. If unable to obtain a time, use the time when the NOTAM information is received.

g. CONDITIONS NOT MNT. 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 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 “CONDITIONS NOT MNT (date/time) (date/time).” The time parameters specified must fall within the effective/ expiration times

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

1. When the reported contaminant is RUBBER, SAND, or OIL.

2. When appended with remarks “CONDI- TIONS NOT MNT.”

3. When the FICON is “PILOT REPORTED,” the expiration time must not exceed 12 hours. The “PILOT REPORTED FICON” NOTAM must not cancel or otherwise affect a NOTAM advertising “CONDITIONS NOT MNT.”

i. The following are example NOTAMs (not inclusive):

1. Snow and ice contaminants.

EXAMPLE− !LGA LGA RWY 13/31 FICON WET ICE OBSERVED AT 1301040230. CONDITIONS NOT MNT 1501040300-1501061045. 1501040253-1501061115

NOTE− 1. The field conditions are not monitored from January 4, 2015 0300UTC January 6, 2015 1045UTC. The airport operator expects to have a new NOTAM submitted by January 6, 2015 1115UTC.

2. This will be the only example reflecting times. All FICON NOTAMs have “OBSERVED AT” and effective/

expiration times but not all have “CONDITIONS NOT MNT”.

EXAMPLE− …RWY 13/31 PILOT REPORTED FICON 1/2IN WET SN OVER ICE…

NOTE− A pilot has reported a field condition that was entered as a NOTAM. The originator must not establish an expiration time that exceeds 12 hours.

EXAMPLE− …RWY 10/28 FICON 1/4IN DRY SN OVER ICE…

NOTE− Runway 10/28 has 1/4 inch of dry snow over ice. The depth of the ice layer is not reported.

EXAMPLE− …TWY C, C1, C6, TWY D BTN RWY 13/31 AND TWY C FICON DRY SN OVER ICE…

NOTE− A number of taxiways to have ½ inch of dry snow over ice. In this example, the depth of the dry snow was not reported, however it could have been entered as: 1/2IN DRY SN OVER ICE

EXAMPLE− …RWY 16/34 FICON ICE SANDED…

NOTE− Runway 16/34 is completely ice covered and has been sanded to treat the surface of the runway. …RWY 16/34 FICON PATCHY COMPACTED SN…

NOTE− Runway 16/34 is 25 percent or less covered with compacted snow. The depth of the compacted snow is not reported

EXAMPLE− …RWY 08/26 FICON THIN WET SN…

NOTE− Runway 08/26 is covered with ⅛ inch (3mm) depth or less of wet snow.

EXAMPLE− …RWY 10/28 FICON 2IN DRY SN OVER COMPACTED SN…

NOTE− Runway 10/28 is covered by 2 inches of dry snow over compacted snow. The depth of compacted snow is not reported.

EXAMPLE− …APRON FEDEX FEEDER RAMP FICON DRY SN…

NOTE− The FedEx Feeder ramp is covered by dry snow. The depth of the contaminant on an apron/ramp is not required when reporting the conditions of non-part 139 airports or not federally obligated.

5−1−7 Movement Area NOTAMs

EXAMPLE− …APRON AIR CARGO APN E 500FT FICON PLOWED 1IN WET SN…

NOTE− The east 500 feet of the Air Cargo apron has been plowed. An inch of wet snow remains on the surface.

2. Plowed/swept.

EXAMPLE− …RWY 02/20 FICON DRY PLOWED 100FT WID REMAINDER 1/2IN WET SN OVER ICE…

NOTE− Runway 02/20 is wider than 100 feet and the area inside the center 100 feet is dry. The remainder of the runway is covered with ½ inch of wet snow over ice.

EXAMPLE− …RWY 16/34 FICON 4IN WET SN PLOWED 50FT WID REMAINDER 18IN WET SN…

NOTE− Runways 16/34 have been plowed 50 feet wide, which is less than the full runway width, and is covered by 4 inches of wet snow. At the highest measurement of the remainder of the runway, which has not been plowed, is covered with 17.5 inches of snow, which is rounded up to 18 inches.

EXAMPLE− …RWY 16/34 FICON WET PLOWED 100FT WID REMAINDER 1/2IN WET SN OVER ICE…

NOTE− The runway is wider than 100 feet and the area inside the center 100 feet is wet. The ½ inch of wet snow over ice is outside of the plowed area.

EXAMPLE− …RWY 01/19 N 2700FT FICON PATCHY COMPACTED SN SWEPT 75FT WID REMAINDER 8IN DRY SN…

NOTE− Runway 01/19 is wider than 75 feet. A portion of the runway 2700 feet in length and 75 feet wide has been swept. The swept area has compacted snow while the remainder of the runway has 8 inches of dry snow.

EXAMPLE− …TWY ALL FICON DRY PLOWED 50FT WID REMAINDER DRY SN…

NOTE− All taxiways are plowed 50 feet wide and are dry. The part that has not been plowed has dry snow.

EXAMPLE− …RWY 16/34 FICON COMPACTED SN PLOWED 75FT WID REMAINDER 1/2IN DRY SN OVER COMPACTED SN…

NOTE− Runway 16/34 has been plowed 75 feet wide. The plowed

portion is covered by compacted snow The area that has not been plowed has ½ inch dry snow over compacted snow. The depth is not reported for compacted snow. EXAMPLE− …RWY 10/28 FICON DRY 120FT WID REMAINDER COMPACTED SN… NOTE− The center 120ft of runway 10/28 is dry. The remainder has compacted snow.

3. Snowbanks, berms.

EXAMPLE− …RWY 16/34 FICON COMPACTED SN 12IN SNOWBANKS… NOTE− Runway 16/34 has been plowed and swept in its entirety; therefore, neither “PLOWED” nor “SWEPT” is used. The runway is covered with compacted snow and has 12- inch snowbanks. EXAMPLE− …RWY 15/33 FICON COMPACTED SN PLOWED 100FT WID 24IN BERM… NOTE− Runway 15/33 has been plowed 100 feet wide leaving compacted snow on the runway. The depth of the compacted snow is not reported, however 24-inch berms are also observed along the edges of the surface. EXAMPLE− …TWY ALL FICON WET 4FT SNOWBANK… NOTE− All of the taxiways as wet with snowbanks reaching 4 feet in depth.

4. Ice contaminants.

EXAMPLE− …RWY 01/19 N 2000FT FICON ICE REMAINDER 1IN SLUSH… NOTE− The north 2000 feet of runway 01/19 is covered with ice. The remainder has 1 inch of slush. EXAMPLE− …APRON FEDEX FEEDER RAMP W 700FT FICON ICE… NOTE− The west 700 feet of the FedEx Feeder Ramp is covered with ice. The depth of ice is not reported. EXAMPLES− …RWY 07/25 W 1200FT FICON PATCHY ICE REMAINDER WET… NOTE− The west 1200 feet of runways 07/25 are covered by patchy ice. The remainder of runways 07/25 has visible moisture, described as “WET.”

5−1−8 Movement Area NOTAMs

EXAMPLE− …RWY 07/25 FICON 1/2IN WET SN OVER ICE PLOWED 50FT WID REMAINDER 2IN WET SN OVER COMPACTED SN…

NOTE− The full length of runways 07/25 have been plowed 50 feet wide. The plowed portion has ½ inch of wet snow over ice while the remainder of the runway has 2 inches of wet snow over compacted snow. Contaminant depths are not reported for ice or compacted snow.

5. Wet.

EXAMPLE− …RWY 10/28 FICON WET…

NOTE− Runway 10/28 has visible moisture with 1/8in (3mm) depth or less of water

6. Frost.

EXAMPLE− …TWY ALL FICON FROST…

NOTE− Frost is observed on all taxiways.

7. Slush Contaminants.

EXAMPLE− …RWY 07/25 FICON 1IN SLUSH OVER ICE…

NOTE− Runway 07/25 has 1 inch of slush over ice.

EXAMPLE− …TWY ALL EXC TWY G FICON 3IN SLUSH…

NOTE− All of the taxiways except taxiway G, are covered by3-inches of slush. The depth of the contaminant is not required when reporting the taxiways or aprons/ramps conditions of non-part 139 airports or not federally obligated.

8. Drift.

EXAMPLE− …RWY 03R/21L FICON 4IN DRY SN 9IN DRIFT…

NOTE− Runway 03R/21L is covered with 4 inches of dry snow and 9inch snow drifts.

EXAMPLE− …RWY 04/22 FICON 5IN DRIFT…

NOTE− Runway 04/22 is contaminant free; however, there are five-inch snow drifts on the surface.

9. Sanded, as a treatment of the surface.

EXAMPLE− …RWY 18/36 FICON ICE SANDED…

NOTE− Runway 18/36 is covered by ice and has been treated with sand. The depth of ice is not reported. EXAMPLE− …RWY 11/29 FICON THIN DRY SN OVER ICE SANDED 80FT WID… NOTE− Runway 11/29 is covered with ⅛ inch (3mm) depth or less of dry snow over ice and has been sanded 80 feet wide. The depth of dry snow is reported, however the depth of ice is not reportable.

10. Deiced, as a treatment of the surface.

EXAMPLE− …RWY 12/30 FICON WET DEICED LIQUID… NOTE− Runway 12/30 is wet and has been treated with a liquid deicing chemical. EXAMPLE− …RWY 12/30 FICON DRY DEICED SOLID 100FT WID REMAINDER ICE… NOTE− Runway 12/30 is dry 100ft wide as result of a solid deicing material being applied. The remainder of the runway is covered with ice. The depth of the ice is not reported.

11. Miscellaneous (mud, ash, rubber).

EXAMPLE− …RWY 01R/19L N 700FT FICON 2IN MUD… NOTE− Runway 01R/19L north 700 feet is covered with 2 inches of mud. EXAMPLE− …RWY 01L/19R FICON ASH… NOTE− Runway 01L/19R is covered with volcanic ash. EXAMPLE− …RWY 01/19 N 800FT FICON RUBBER… NOTE− The north 800 feet of runway 01/19 is covered by rubber. The depth of rubber is not reportable. Although the rubber is observed only at the approach end of Runway 01, FICON NOTAMs are reported using both runway designators.

j. FICON NOTAMs are used by airport management to report braking action and MU values.

1. Runway friction measuring values are reported in thirds of a runway for landing runway(s) only. A MU value for the thirds of a runway should be reported when contaminant(s) are present or there is precipitation occurring.

2. Do not combine runways into a single NOTAM.

5−1−9 Movement Area NOTAMs

3. NOTAMs for MU values must be issued as value 40 if readings are 40 or above.

4. If a NOTAM was issued and the airport manager advises that the readings are above 40, the MU value NOTAM may remain as 40 or canceled.

EXAMPLE− …RWY 36 FICON TAP MU 20/20/40…

NOTE− A MU value of 40 indicates 40 or greater. Current friction measurement technologies are not reliable in determining braking effectiveness of a contaminated surface condition above measurements of 40. (Advisory Circular 150/5200-30C, Airport Winter Safety and Operations).

…RWY 18 FICON RFT MU 40/40/40…

NOTE− Runway 18 MU readings are all 40 or above and the airport manager requested this NOTAM be issued to indicate that the friction testing was completed. A NOTAM is not required, but is allowed.

5. Friction measuring reports are to be expressed using the name of the FAA-approved device, followed by the word “MU” (pronounced “mew”), followed by the reported values, then followed by the actual time of the measurement.

TBL 5−1−4 Friction Measuring Devices

BOW Bowmonk Decelerometer (Bowmonk Sales)

BRD Brakementer – Dynometer

ERD Electronic Recording Decelerometer (Bowmonk)

GRT Griptester (Findlay, Irvine, LTD)

MK3 TES ERD MK3 Decelerometer

MUM Mark 4 Mu Meter (Bison Instruments, Inc.)

NAC Neubert Aero Corp

RFT Runway friction tester (K.J. LAW Engineers)

RT3 Halliday RT3−FAA−Model: 1000

SFH Surface friction tester (high pressure tire) (SAAB, Airport Surface Friction Tester AB)

SFL Surface friction tester (low pressure tire) (SAAB, Airport Surface Friction Tester AB)

SKH Skiddometer (high pressure tire) (AEC, Airport Equipment Co.)

SKL Skiddometer (low pressure tire) (AEC, Airport Equipment Co.)

TAP Tapley Decelerometer (Tapley Sales)

VER Vericom (VC3000)

6. Report braking action on movement areas as fair, poor, or nil, as received from airport management. Classify according to the most critical term used. 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.

EXAMPLE− …TWY G FICON BA FAIR… …RWY 18/36 FICON COMPACTED SN BA POOR… …RWY 14/32 FICON WET ICE BA NIL…

NOTE− 1. Do not include the type of vehicle in the NOTAM.

2. A braking action report from a landing aircraft should be processed as a PIREP.

5−1−5. AERODROME FACILITIES

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 out of service. 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 Chart Supplement U.S., which lists indices and ARFF equipment requirements.

2. At certificated airports listed in the Chart Supplement U.S., the certificate holder (airport management) is required to notify air carriers by NOTAM when required ARFF equipment is inoperative/unavailable and replacement equipment

05/26/16 JO 7930.2Q CHG 1

5−1−10 Movement Area NOTAMs

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

EXAMPLE− …AD AP ARFF VEHICLE OUT OF SERVICE INDEX UNCHANGED…

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

EXAMPLE− …AD AP ARFF NOW INDEX A…

NOTE− Even though the ARFF index is now A, four or less Index B aircraft may still operate into the airport.

4. If the ARFF Index is listed in the Chart Supplement U.S. as A and the ARFF vehicle is out of service, the NOTAMs would be issued using the following format:

EXAMPLE− …AD AP ARFF INDEX A NOT AVBL AND AP CLSD TO AIR CARRIER OPS…

b. Fuel services.

EXAMPLE− …AD AP 100LL FUEL NOT AVBL…

…AD AP MOBILE JET A FUEL NOT AVBL…

…AD AP HYDRANT MOGAS FUEL NOT AVBL…

…AD AP SELF SERVE 100LL FUEL NOT AVBL…

…AD AP FUEL NOT AVBL…

c. MU-Friction Measuring Device.

EXAMPLE− …AD AP FRICTION MEASURING DEVICE OUT OF SERVICE…

d. Customs Services. Describe the change of services by using “CUSTOMS,” followed by plain language.

EXAMPLE− …AD AP CUST PROCESSING DLA DUE TO CAPACITY, INTL CARRIERS MAY EXPERIENCE SIGNIFICANT DLA IN CLEARING CUST, CTC AP MANAGEMENT AT XXX-XXX-XXXX…

e. Aerodrome beacon (ABN). If any of the lights are out of service, the whole system is considered out of service.

EXAMPLE− …AD AP ABN OUT OF SERVICE…

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

EXAMPLE− …AD AP WDI UNREL…

…AD AP WINDCONE LGT OUT OF SERVICE…

…AD AP WINDCONE FOR RWY 17L LEFT SIDE OUT OF SERVICE…

5−1−6. WORK IN PROGRESS

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.

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:

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

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

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

g. Condition or activity; “WIP.”

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

h. Reason or purpose.

3/15/07 7110.65R CHG 2 JO 7930.2Q CHG 1 05/26/16

5−1−11 Movement Area NOTAMs

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

j. Follow 4-2-1 b 13 and14 to complete the NOTAM.

EXAMPLE− …RWY 01L/19R WIP…

…TWY E BTN RWY 05/23 AND TWY B WIP RESURFACING…

…TWY B BTN RWY 14/32 AND TWY A WIP TRENCHING ADJ EAST SIDE…

…APRON FEDEX FEEDER RAMP W 1000FT WIP RESURFACING…

…RWY 03/21 NE 1000FT WIP LGT REPLACEMENT…

…RWY 01L/19R NE 500FT WIP MOWING ADJ…

…RWY 01L/19R SAFETY AREA WIP MAINT VEHICLES E SIDE…

…AD AP ALL SFC WIP SN REMOVAL…

…RWY 01L/19R WIP SN REMOVAL…

…TWY D4, D5, D6, TWY B BTN RWY 13/31 AND TWY D, TWY D WEST OF RWY 05/23 WIP SN REMOVAL…

Section 2. Lighting Aid and Obstruction NOTAMs

5−2−1 Lighting Aid and Obstruction NOTAMs

Section 2. Lighting Aid and Obstruction NOTAMs

5−2−1. LIGHTING AIDS

Originate NOTAMs on operational status of lighting aids for public use civil landing areas listed in the Chart Supplement U.S. 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.

EXAMPLE− …RWY 12 MALSR COMMISSIONED…

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

EXAMPLE− …RWY 36 ALS DECOMMISSIONED…

…RWY 18 ALS OUT OF SERVICE…

…RWY 22 CHANGE ALL REF ALSF-1 TO SSALR…

NOTE− ALSF-1 is the type of approach lighting at that airport.

…RWY 22 ALS OUT OF SERVICE EXC MEDIUM INTST ON CONS…

b. Lead off /lead on lights. NOTAMs issued using keyword RWY

NOTE− Lead off and lead on light will be the standardized verbiage for lead off/on lights, which are sometimes referred to as turnoff lights.

EXAMPLE− …RWY 01C LEAD OFF LGT FOR TWY Y4 OUT OF SERVICE…

…RWY 01C LEAD ON LGT FOR TWY Y9 OBSC…

c. Runway status light system.

EXAMPLE− …RWY 18L RWY STATUS LGT SYSTEM OUT OF

SERVICE…

…AD AP RWY STATUS LGT SYSTEM OUT OF SERVICE…

…RWY 18L/36R RWY STATUS LGT SYSTEM OUT OF SERVICE…

1. Runway entrance lights. NOTAMs issued using keyword TWY

EXAMPLE− …TWY ALL RWY ENTRANCE LGT FOR RWY 09L SOUTH SIDE OUT OF SERVICE…

…TWY K5, K6, T RWY ENTRANCE LGT FOR RWY 09L OUT OF SERVICE…

2. Take-off hold lights.

EXAMPLE− …RWY 28 TKOF HOLD LGT OUT OF SERVICE…

d. Sequence flashing lights/runway alignment indicator lights.

EXAMPLE− …RWY 18 SEQUENCED FLG LGT OBSC…

…RWY 18 RAI LGT OUT OF SERVICE…

e. Visual approach lighting.

1. Visual approach slope indicator (VASI).

EXAMPLE− …RWY 05 VASI OUT OF SERVICE…

…RWY 13 VASI 5DEG LEFT OF RCL UNUSABLE

…RWY 13 VASI BEYOND 5DEG LEFT AND RIGHT OF RCL UNUSABLE…

2. Precision approach path indicator (PAPI).

EXAMPLE− …RWY 01L PAPI OUT OF SERVICE…

…RWY 10 PAPI BEYOND 5DEG LEFT AND RIGHT OF RCL UNUSABLE…

…RWY 28 PAPI COMMISSIONED…

…RWY 30 PAPI COMMISSIONED GPA 3.15DEG…

…RWY 12 PAPI GPA CHANGED TO 3.2DEG…

3. Runway end identifier lights.

05/26/16 JO 7930.2Q CHG 1

JO 7930.2P 4/3/ 14

7110.65R CHG 2 3/15/ 07 JO 7930.2Q 12/18/15

5−2−2 Lighting Aid and Obstruction NOTAMs

EXAMPLE− …RWY 18 RWY END ID LGT OUT OF SERVICE…

4. Threshold lights (RTHL).

EXAMPLE− …RWY 27 RTHL OUT OF SERVICE…

f. Runway edge lights (REDL).

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

EXAMPLE− …RWY 13/31 HIRL COMMISSIONED…

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

EXAMPLE− …RWY 13/31 REDL OUT OF SERVICE…

…RWY 01/19 REDL OUT OF SERVICE EXC MEDIUM INTST ON CONS…

3. Runway lights obscured due to snow and ice.

EXAMPLE− …RWY 15/33 REDL OBSC…

NOTE− 1. All edge lights for runway 15/33 are completely obscured. The reason for the obscuration should not be reported.

2. Lights that are partially obscured should not be reported.

g. Runway centerline light (RCLL).

EXAMPLE− …RWY 08R/26L RCLL OUT OF SERVICE…

h. Touchdown zone lights (RTZL).

EXAMPLE− …RWY 08R RTZL OUT OF SERVICE…

i. Runway lead-in lighting system (RLLS).

EXAMPLE− …RWY 18 RLLS OUT OF SERVICE…

j. Airport lighting total power failure.

EXAMPLE− …AD AP LGT ALL OUT OF SERVICE…

k. Pilot-controlled lighting (PCL) frequency when it controls approach lights or runway lights.

EXAMPLE− …SVC PCL ALL OUT OF SERVICE…

…SVC PCL RWY 18/36 REDL OUT OF SERVICE

…SVC PCL RWY 18 ALS OUT OF SERVICE…

…SVC PCL RWY 18/36 MEDIUM/HIGH INTST OUT OF SERVICE…

NOTE− All the PCL services for runway 18/36 only have low intensity operating.

…SVC PCL RWY 14/32 COMMISSIONED KEY FREQ 122.7 7 TIMES HIGH, 5 TIMES MEDIUM, 3 TIMES LOW INTST…

…SVC PCL FREQ CHANGED TO 122.8…

NOTE− PCL frequency need not be an ATC frequency.

l. Taxiway lighting.

1. Taxiway edge lights.

EXAMPLE− …TWY K, L EDGE LGT OUT OF SERVICE…

2. Taxiway centerline lights.

EXAMPLE− …TWY E CL LGT BTN TWY E1 AND RWY 15/33 OUT OF SERVICE…

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

EXAMPLE− …TWY ALL RWY GUARD LGT OUT OF SERVICE…

…TWY A4 RWY GUARD LGT FOR RWY 01L/19R OUT OF SERVICE…

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

EXAMPLE− …TWY C STOP BAR LGT FOR RWY 16R/34L OUT OF SERVICE…

5. Taxiway lights obscured due to snow and ice.

EXAMPLE− …TWY C EDGE LGT OBSC…

…TWY ALL LGT ALL OBSC…

NOTE− 1. OBSC can be used to describe the physical state of airport infrastructure, including signs and markings.

2. All taxiway C edge lights are completely obscured. The reason for the obscuration should not be reported.

3. Lights that are partially obscured should not be reported.

5−2−3 Lighting Aid and Obstruction NOTAMs

5−2−2. OBSTACLES

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,” “BUILDINGS,” “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).

(b) When the obstacle is within 500 feet either side of the centerline of a charted helicopter route, or 5SM or more from an airport and more than 200 feet AGL, describe the plain language location by using the bearing, distance, and aerodrome designator of the nearest public-use airport; for example, (12NM SSW SPA).

7. Specify the altitude MSL with the unit of measurement (FT), if known. Otherwise state UNKNOWN. For wind turbine farms, use the tallest height of a turbine within the farm.

8. In parentheses, specify the height with the unit of measurement (FT) and reference datum (AGL).

NOTE− Report the height of obstruction lights on terrain (hills) in MSL only, as the terrain is the obstacle, not the light on the terrain

9. Specify the condition:

(a) “OUT OF SERVICE” for FCC obstructions. A light condition of OUT OF SERVICE refers to a top light or flashing obstruction light regardless of its position.

(b) “NOT LGTD,” “LGTD,” “FLAGGED” for non-FCC obstructions, for example.

10. Effective time/expiration time. FCC receives notification upon ASR NOTAM issuance.

Continue reading ↓ 120 of 219 passages shown