Radar Vectors
FAA Order Cancelled Issued Oct 1, 2013 AJV-0 116 pages Copy saved Nov 18, 2026

Order JO 7930.2N Notices to Airmen (NOTAM)

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

Official source ↗ Open PDF

Text read by OCR from a scanned file (2 of 116 pages). Check the original, as some words may be misread.

FAA Order JO 7930.2N, Notices to Airmen (NOTAM), Effective 10/1/13

Distribution: ZAT-721, ZAT-464 Initiated By: AJV-0 Vice President, Mission Support Services

This order prescribes air traffic control procedures and phraseology for use by personnel providing air traffic control services. Controllers are required to be familiar with the provisions of this order that pertain to their operational responsibilities and to exercise their best judgment if they encounter situations not covered by this order.

Effective Date: October 1, 2013

Air Traffic Organization Policy

SUBJ: Notices to Airmen (NOTAM)

ORDER JO 7930.2N

DIRECTIVE NO. RECORD OF CHANGES JO 7930.2N

CHANGE

TO BASIC

SUPPLEMENTS

OPTIONAL

CHANGE

TO BASIC

SUPPLEMENTS

OPTIONAL

FAA Form 1320−5 (6−80) USE PREVIOUS EDITION

Explanation of Changes

Explanation of Changes E of Chg−1

Notices to Airmen

(NOTAM)

Explanation of Changes

Effective: October 1, 2013

a. Chapter 1

Clarifies and expands the definitions of each keyword, as well as provides definitions to keywords not previously defined in preparation for International Civil Aviation Organization (ICAO) compliant NOTAMs. The keyword “SECURITY” and definition is also added. Section 3 of Chapter 1 is renamed from “Responsibilities” to “Accountable Organization” which is more descriptive of the type of information contained in this section. Adds a new paragraph that defines and identifies who, other than Flight Service, is considered a certified source. The term “NOTAM Originator” is further defined as a result of the Safety Risk Management Document (SRMD), Digital NOTAM Originators, dated May 26, 2011, and SRMD Amended Version 1, dated October 11, 2012. Clarifies coordination and NOTAM responsibilities associated with navigational aids.

b. Chapter 2

Adds additional descriptive verbiage that addresses time critical delays, corrections, and changes. The enhanced paragraph becomes more descriptive of the happening or event.

c. Chapter 3

Paragraph 3−1−2 is renamed and reorganized to more accurately portray NOTAM responsibilities. Paragraph 3−1−3 eliminates the option to use Standard Forms 7930-1 and 7930-2 because they are outdated due to new technology; instead, the information needs to be included on a locally−approved form. Paragraphs 3−3−3 and 3−3−6 are also added.

d. Chapter 4

Section 2 further defines the standardized NOTAM sequence and the words within. Keywords are removed as they are identified in Chapter 1. NOTAM elements are standardized to reflect the digital NOTAM structure, specifically to provide guidance

for NOTAMs with altitude limits. All NOTAMs now must have an effective and expiration time, and the use of “EST” and “PERM” are further defined.

e. Chapter 5

The term “Movement Area NOTAMs” is changed to “Aerodrome Condition NOTAMs” to be more inclusive. Policy is included to help the user in creating changes to Usable Runway Length and Declared Distance NOTAMs. Updates to Field Condition Reporting are changed as a result of the SRM Panel on Changes in Contaminant Reporting dated April 2012. The contaminant table is modified to more accurately reflect Airports policy. Pilot Reported FICON is added to this section. Customs Services is added to paragraph 5−1−5. A new paragraph is added to provide the standardized NOTAM sequence for Obstructions. Technical Operations personnel are identified as the originator of the NOTAMs identified in sections 5-3 through 5-5. The responsibility is placed again on the NOTAM Originator as the disseminator of the information contained in the NOTAM.

f. Chapter 6

The term “Special Activity Airspace (SAA)” is added and defined to be inclusive of Special Use Airspace (SUA), Warning Areas, and other related airspaces.

g. Chapter 7

Paragraph 7−1−5 has been reorganized for clarity and reworded to enhance understanding of information required and better define duties.

h. Chapter 8

The Military NOTAM System is changed to its proper name, Defense Internet NOTAM Service (DINS).

i. Chapter 9

The procedure for the NOTAM Office issuing GPS-related international NOTAMs is amended, and the reference to oceanic airspace is deleted.

Explanation of Changes E of Chg−2

j. Appendices

The Appendices have been updated to reflect current word uses and policy.

k. Further guidance for NOTAM responsibilities and accountabilities is defined to reflect current practices within the Federal NOTAM System (FNS).

l. Many updates are made to transition towards ICAO compliance.

m. Updates are made to capture FAA

organizational changes and the results of those changes.

n. Paragraphs have been moved and reorganized to improve the flow and make the order more logical.

o. Examples and references are updated throughout the order to reflect current policy and updated publication information.

p. Redundancies are eliminated. q. Additional editorial/format changes are made where necessary.

10/1/13 JO 7930.2N

Page Control Chart i

PAGE CONTROL CHART Notices to Airmen (NOTAM)

REMOVE PAGES DATED INSERT PAGES DATED

Entire Order … 8/22/13 Entire Order … 10/1/13

NOTE− In accordance with GENOT N JO 7930.105, which delayed the implementation of N JO 7930.2N Basic, effective 8/22/13; this order is printed in its entirety with an effective date of 10/1/13.

Table of Contents

ii 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. REVISIONS 1-1-1 … 1-1-8. EFFECTIVE DATE 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. TRANSPORTATION SECURITY ADMINISTRATION (TSA) 1-3-2 … 1-3-7. 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. FORWARDING DATA 2-1-2 … 2-1-6. CHART/PUBLICATION ERRORS OR OMISSIONS 2-1-2 … 2-1-7. ADMINISTRATIVE MESSAGES 2-1-3 … 2-1-8. ADDRESSING CORRESPONDENCE 2-1-3 …

iii Table of Contents

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

Section 2. NOTAM System

2-2-1. NOTAM CLASSIFICATION 2-2-1 …

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

Section 2. Coordination

3-2-1. COORDINATION WITH OTHER FACILITIES 3-2-1 … 3-2-2. FILING NOTAM INFORMATION WITH FSSs 3-2-1 … 3-2-3. 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. RUNWAY IDENTIFICATION 3-3-1 … 3-3-5. TAXIWAY IDENTIFICATION 3-3-1 … 3-3-6. APRON IDENTIFICATION 3-3-2 …

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 …

iv Table of Contents

Paragraph Page 4-3-7. RETRIEVING DOMESTIC NOTAMs 4-3-1 …

Section 4. Canceling/Extending NOTAMs

4-4-1. EXTENDING NOTAM DURATION 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-5 … 5-1-5. AERODROME FACILITIES 5-1-11 … 5-1-6. WORK IN PROGRESS 5-1-12 …

Section 2. Lighting Aid and Obstruction NOTAMs

5-2-1. LIGHTING AIDS 5-2-1 … 5-2-2. TOWER LIGHT OUTAGES 5-2-2 … 5-2-3. OBSTRUCTIONS 5-2-3 … 5-2-4. MOORED BALLOONS AND KITES 5-2-4 …

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

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 …

v Table of Contents

Paragraph Page 5-5-6. RADAR SERVICES 5-5-4 … 5-5-7. AUTOMATIC DEPENDENT SURVEILLANCE BROADCAST (ADS­B) SERVICES 5-5-5 …

Chapter 6. Airspace NOTAMs

Section 1. Airspace

6-1-1. GENERAL 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. AIRCRAFT OPERATIONS 6-1-2 … 6-1-5. AERIAL REFUELING 6-1-4 … 6-1-6. PARACHUTE JUMPING/SKY DIVING (PJE) 6-1-4 … 6-1-7. UNMANNED ROCKETS, UNMANNED FREE BALLOONS, HOT AIR BALLOONS, AND HIGH ALT BALLOONS 6-1-5 … 6-1-8. OTHER AIRSPACE ACTIVITIES 6-1-5 …

Section 2. Other Aeronautical Information

6-2-1. GENERAL 6-2-1 …

Chapter 7. FDC NOTAM Procedures

Section 1. Transmitting FDC NOTAM Data

7-1-1. GENERAL 7-1-1 … 7-1-2. FDC NOTAM NUMBERING 7-1-1 … 7-1-3. TEMPORARY OR PERMANENT FDC NOTAMs 7-1-1 … 7-1-4. INTERIM IFR FLIGHT PROCEDURES 7-1-1 … 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-4 … 7-1-8. LASER LIGHT ACTIVITY 7-1-5 …

Section 2. Cancellation/Expiration

7-2-1. FDC NOTAM EXPIRATION 7-2-1 … 7-2-2. CANCELING FDC NOTAMs 7-2-1 … 7-2-3. FDC NOTAM LIST 7-2-1 … 7-2-4. 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. TEMPORARY OR PERMANENT FDC NOTAMs 8-1-1 …

vi Table of Contents

Section 2. Military NOTAM Dissemination

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

Chapter 9. International NOTAMs

Section 1. General Procedures

9-1-1. RETRIEVING 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/HIBAL Flights Appendix B−1 . . . . Appendix C. FCC Field Office Fax Numbers Appendix C−1 … Appendix D. ICAO Difference for the United States Appendix D−1 …

Chapter 1. General

1−1−1 Introduction

Chapter 1. General

Section 1. Introduction

1−1−1. PURPOSE

This order prescribes procedures used to obtain, format, and disseminate information on unanticipated or temporary changes to components of, or hazards in, the National Airspace System (NAS) until the associated aeronautical charts and related publications have been amended. The Notice to Airmen (NOTAM) system is not intended to be used to advertise data already published or charted.

1−1−2. AUDIENCE

The primary audience for this notice 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 FAA Web site at http://faa.gov/air_traffic/publications and http://employees.faa.gov/tools_resources/ orders_notices/.

1−1−4. CANCELLATION

FAA Order JO 7930.2N, Notices to Airmen (NOTAM) dated August 22, 2013, 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. REVISIONS

The contents of this order will be periodically reviewed and updated, as required by NADIN GENOTs and order changes. Changes/orders are published as needed. Suggestions for revision should be forwarded through the appropriate facility/service area staff, to System Operations Services, Flight Services, Safety and Operations Policy Group.

1−1−8. EFFECTIVE DATE

This order is effective October 1, 2013.

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 SECURITY or (O).

NOTE− Examples of keywords (RWY, TWY, APRON, AD, OBST, NAV, COM, SVC) are shown in chapter 5; AIRSPACE in chapter 6; (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, signage, and other airport services or attributes associated with a specific runway.

2. TWY (Taxiway). Keyword used to describe a temporary change or hazard pertaining to taxiway, taxiway lighting, and signage.

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

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, helipad, or maneuvering area that is not associated with a specific movement area surface. Such hazards may include 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.

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

1−2−2 Scope

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.

20. (O) − Other Aeronautical Information. Aeronautical information received from any authorized source that may be beneficial to aircraft operations and does not meet defined NOTAM criteria. Any such NOTAM will be prefaced with “(O)” as the keyword following the location identifier.

NOTE− Keyword (O) should not be used for NOTAMs pertaining to a movement area as described in this Order.

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

e. The United States 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 or fall within the published data. Do not issue a NOTAM on information that duplicates or falls within published data unless a NOTAM is required by a Certificate of Waiver or Authorization from Title 14, Code of Federal Regulations (CFR) issued by the FAA.

1−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 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 airmen information regardless of source or subject matter, provided the occurrence is no more than 3 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 tie-in FSS.

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/Flight Services Program Operations specialists are responsible for issuing a NOTAM that is not covered in any example or NOTAM criteria in FAA Order JO 7930.2. Advise the USNOF when this type of NOTAM is being issued.

NOTE− Before issuing this type of NOTAM, a discussion with a NOTAM specialist (USNOF) must take place to coordinate formats and adhere to standard NOTAM procedures as best as possible.

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 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. Aeronautical Products may originate NOTAMs regarding NAVAID restrictions in accordance with 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 ARTCC (See paragraph 7-1-5f).

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.

REFERENCE− FAAO JO 7930.2, Para 4−1−2 , National NOTAM Office Relationships 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 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.

NOTE− Technical Operations personnel are expected to submit approval requests for routine maintenance shutdowns sufficiently in advance to assure that approval will be received with ample time for issuance of a NOTAM 5 hours before a shutdown will occur.

1−3−3. FLIGHT INSPECTION SERVICES

NOTAMs regarding NAVAID restriction are initiated by Flight Inspection Services under FAAO 8200.1, United States Standard Flight Inspection Manual. 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− FAAO 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.)

1−3−6. TRANSPORTATION SECURITY ADMINISTRATION (TSA)

The TSA Aviation Command Center initiates requests to establish temporary flight restrictions required by hijack situations. These requests are normally made to the service area office; however, these requests may be made directly to air traffic facilities.

1−3−7. 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

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.

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

Any illustration used which serves to explain subject material is identified as an EXAMPLE. They are representative of the format discussed in each section. Not all components of the NAS will be illustrated with an example.

1−4−4. REFERENCES

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

1−4−5. MANUAL CHANGES

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

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

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

1−4−6. DEFINITIONS

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

a. Accountable Organization. The accountable organization is responsible for accurately reporting the condition considered to be a hazard or potential hazard to flight operations. Reporting the condition must be 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.

e. Alaska Supplement. See Supplement.

f. Center Area NOTAM (CAN). CANs are NOTAMs issued on airway changes, temporary flight restrictions (TFR) and laser light activity that fall within an ARTCCs airspace. CANs will be issued in the FDC format by the USNOF.

1−4−2 Terms of Reference

g. Certified Airport. An airport certificated under 14 CFR Part 139. These airports are so indicated in the airport/facility directory.

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

i. Chart Supplement. See Supplement.

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

k. Fix/Radial/Distance (F/R/D). Is a VOR identifier followed by 3-digit degrees magnetic and 3-digit distance in nautical miles with no spaces between characters (SAC360020 would be 360-degree radial, 20NM from SAC).

l. Flight Data Center (FDC) NOTAM. FDC NOTAMS are normally used to disseminate safety of flight information relating to regulatory material as well as to all Instrument Flight Procedures and are issued through the USNOF.

m. Limited Airport Operating Certificate. A certificate issued by the FAA, pursuant to 14 CFR Part 139, to airports serving or expected to serve only unscheduled air carrier operations in aircraft with seating capacity of more than thirty passengers. These airports are maintained and operated in accordance with Airport Certification Specification .

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

o. NOTAM D. A notice distributed by means of telecommunications containing information concerning the establishment, condition, or change in any aeronautical facility, service, procedure, or hazard, the timely knowledge of which is essential to personnel concerned with flight operations.

p. NOTAM Originator. The party who submits a NOTAM to the USNS using an approved interface and is accountable for the NOTAM coordination.

q. Pacific Chart Supplement. See Supplement.

r. Reduced. Used to denote possible communications problems that may prevent data from being delivered. If the data is received, it is good; therefore, it is reliable. However, when the coverage is reduced, the data may not be received, or there may be a loss of signal during flight; once that signal is received again it is deemed usable.

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 an airport/facility directory 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 an airport/ facility directory of all airports (including 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. 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.

Chapter 2. Aeronautical Information Services

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

2. Airport/Facility Directory (AFD).

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.

2−1−2 Aeronautical Information System

2−1−4. NOTICES TO AIRMEN PUBLICATION

a. NTAP is published by Mission Support Services, ATC Products and Publications, 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 AFD 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 Military 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. 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 AFD.

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.

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−6. CHART/PUBLICATION ERRORS OR OMISSIONS

a. Managers must review each edition of the Notices to Airmen Publication, the Airport/Facility Directory, 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.

2−1−3 Aeronautical Information System

c. If NOTAMs are published or more than 90 days old, the accountable organization must be contacted for possible cancellation.

2−1−7. ADMINISTRATIVE MESSAGES

All data forwarded to the NFDC via telecommunications for publication must be forwarded to the Washington Headquarters Telecommunications Center (RWA), attention Aeronautical Information Management.

EXAMPLE− GG KRWAYAYX 121543 KDCAYFYX DCA001 ATTN Aeronautical Information Management THE FOLLOWING INFORMATION IS SUBMITTED FOR PUBLICATION IN THE NEXT ISSUE OF THE NOTICES TO AIRMEN AND OR OTHER PUBLICATIONS AS REQUIRED. DCA VASI RWY 17 COMISSIONED. ATCT HOURS 0900−1900. SIMEONE MANAGER FSS.

2−1−8. ADDRESSING CORRESPONDENCE

All correspondence to be mailed to the NFDC for publication must be addressed to:

Federal Aviation Administration Aeronautical Information Management National Flight Data Center 800 Independence Avenue, S.W. Washington, D.C. 20591

2−1−9. 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) 267-9292.

b. Procedures and Airspace Section, telephone: (202) 267-9273.

c. Cartographic Standards Section, telephone: (202) 267-9302.

d. Aeronautical Information Management:

1. Toll Free: (866) 295-8236

2. Fax: (202) 267-5322.

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

2−1−10. 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−11. COMPUTER PRINTOUTS

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

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 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 USCG navigational aids/airports that are part of the NAS.

Chapter 3. General Operating Procedures

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, and informing the controlling facility and other facilities/offices affected by the aid, service, or hazard contained in the new NOTAM.

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− FAAO JO 7930.2, Para 5−1−2 , Handling Reported Movement Area Conditions

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

REFERENCE− FAAO 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− FAAO JO 7930.2, Para 7−2−4 , Retrieving FDC NOTAMs

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

a. The USNOF must send Title 14 CFR, Part 91, Section 139, Emergency Air Traffic Rules; Section 141, Flight Restrictions in the Proximity of the Presidential and Other Parties; Part 99, Section 7, Special 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.”

3−1−2 General

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 notify the USNOF within 15 minutes by receipt message to “KDZZNAXX.” The receipt message must include:

1. R.

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 twice a day by the USNOF to ensure that every Presidential, Special Security Instructions, or Emergency Air Traffic Rules FDC NOTAM has been received in the facility.

5. If no supervisory personnel are on duty and a controller−in−charge (CIC) is assigned to these duties, emergency situations and/or inflight services as defined in FAA Order JO 7110.10, Flight Services, must take precedence over compliance with the supervisory duties contained in this paragraph.

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.

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

REFERENCE− 14 CFR Part 171 outlines owner/operation responsibilities.

b. NOTAMs on non-Federal facilities that are not part of the NAS are not distributed in the FAA NOTAM system. FSSs receiving data on these facilities must notify the appropriate Technical Operations Service Area Director as well as Aeronautical Information Management.

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. Where an ICAO contraction is not listed, plain text is required. See Appendix D for a list (not all inclusive) of ICAO differences – words that are allowable in a NOTAM even though it is not ICAO compliant.

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.

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.

EXAMPLES− 500FT 12500LB 5NM

3−3−4. RUNWAY IDENTIFICATION

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

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

EXAMPLE− RWY 3/21, 3 or 21

c. The Department of Defense must specify the runway identification as it is published.

EXAMPLE− RWY 08

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

EXAMPLES− 3L 3C 3R

e. Where the magnetic bearing indicator has not been established, identify the runway to the nearest eight points of the compass. The forward slash “/” is used to separate runway pair designators and should not be used elsewhere to mean “and.”

EXAMPLES− NE/SW CLSD N/S N 200FT CLSD

3−3−5. 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− SHD TWY PARL TWY ADJ RWY 9/27 CLSD

2. When a cardinal direction is used to describe a taxiway condition, the word describing the

3−3−2 Use of Terms

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

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

EXAMPLES− ACY TWY ALL CLSD

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

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

EXAMPLE− DCA TWY B3,C CLSD

2. Taxiway segments separated by a comma will share only the condition; for example, multiple segments separated by commas may share the condition CLSD or WORK IN PROGRESS SNOW REMOVAL.

EXAMPLE− DEN TWY B1, B2, F, TWY B BTN TWY B10 AND TWY B8 CLSD

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

2. The use of the virgule “/” to separate large segments is not authorized.

3−3−6. APRON IDENTIFICATION

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

EXAMPLES− DCA DCA APRON ALL CLSD

FAI FAI APRON TERMINAL RAMP FICON PATCHY THIN SN

NOTE− “ALL” can be used at airports that have more than one apron to indicate all aprons are affected equally, OR where there is only one apron, to indicate its condition.

Chapter 4. NOTAM D Procedures

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.

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. 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. An exclamation point (!).

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

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

4. Keyword.

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

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

6. Surface segment (when needed).

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

8. Location description (when needed).

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

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

11. Reason (when needed).

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

13. Schedule, if needed. A single NOTAM may be originated for a scheduled condition/activity that will recur during the effective period. Specify the

schedule between the condition/activity and the effective time string. The days of the week must be specified before the scheduled time. The term “DAILY” indicates the event will occur at the same time during the stated time period. The NOTAM effective time and expiration time must be compatible with the scheduled time.

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

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

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

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

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

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

4−2−2 Preparing NOTAMs for Dissemination

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.

c. Make NOTAM accountability changes by mail, administrative message, or FAX when known sufficiently in advance. When the published accountability for a NOTAM is incorrect, change it by issuing a NOTAM under the published accountability. As soon as practicable after issuance, contact the USNOF by telephone or message and request they make the accountability change in the USNS tables. Issue all subsequent NOTAMs under the corrected accountability. If there are any current NOTAMs for the location, cancel and reissue those NOTAMs under the new accountability after the USNS tables have been changed. Notify Aeronautical Information Management of any NOTAM accountability changes.

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.

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 131345 KPIRYFYX !PIR PIR NAV VOR OUT OF SERVICE

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 131345 KPIRYFYX !EKN W22 AD AIRPORT CLSD

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 131500 KABQYFYX !ABQ C04/003 !ABQ ABQ RWY 8/26 CLSD !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 131346 KDZZNAXX !DEN 04/003 DEN NAV VOR OUT OF SERVICE

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 another facility 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 041503 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 051612 KYNGYFYX )SVC RQ DOM ACC=FOD NT=03/040

c. To request all NOTAMs for a given location:

AISR Format: GG KDZZNAXX

061832 KBZNYFYX )SVC RQ DOM LOC=DSM

d. To request all NOTAMs for a given accountability:

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

4−4−1 Canceling/Extending NOTAMs

Section 4. Canceling/Extending NOTAMs

4−4−1. EXTENDING NOTAM DURATION

a. When there is a need to extend an existing NOTAM time duration, 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. The cancellation must be formatted in the following manner:

EXAMPLE− !ABC C05/005 PUBLISHED Or !DEF C06/006 CHARTED

NOTE− A cancellation which is transmitted without an explanation means the NOTAM is canceled; for example, !GHI C07/007

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. Airport/Facility directory.

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.

NOTE− 1. NOTAMs for Prohibited Areas P-40, P-49, and P-56, even if published on a chart, will not be deleted from the database. This would also include any published FDC (TFR) NOTAMs in the Washington, DC, Special Flight Rules Area.

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

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

4−5−1 Computer−Generated NOTAM Service Messages

Section 5. Computer−Generated NOTAM

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 071356 KDZZNAXX !SVC LOCATION NOT VALID FOR CLE CLE LNN FUEL NOT AVBL

b. Invalid NOTAM accountability location.

EXAMPLE− GG KRDUYFYX 071402 KDZZNAXX !SVC NOTAM D ACCOUNTABILITY NOT FOUND NLN LNN RWY CLSD

c. Invalid affected location.

EXAMPLE− GG KCLEYFYX 071333 KDZZNAXX

!SVC NOTAM (D) LOCATION NOT FOUND CLE VBV RWY CLSD

d. Invalid cancellation.

EXAMPLE− GG KBUFYFYX 081822 KDZZNAXX !SVC XXXXXXX DATE TIME CANCELED NOTAM NOT ON FILE FOR ABOVE ACCOUNTABILITY BGM C01/050

NOTE− X Field is internal USNS data.

e. Invalid input format.

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

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 either with a new effective 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.

Chapter 5. NOTAM Criteria

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− !CRW CRW RWY 15/33 UNSAFE BREAKS IN ASPH SE END 1304030730-130701500EST

!PIE CLW RWY 16/34 UNSAFE DISABLED ACFT 1303251800-1303261000EST

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− !ORT 6K8 (U) RWY 7/25 UNSAFE ABANDONED VEHICLE 1310122330-1310130300EST

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− !ANB A09 AD AIRPORT CLSD 1310122330-1310131300

!AOO P45 AD AIRPORT CLSD TO TRANSIENT 1310122330-1310131300EST

!CRW CRW RWY 15/33 UNSAFE BREAKS IN ASPH SE END 1304030730-130701500EST

!BET BET AD AIRPORT CLSD EXC SKI 1310122330-1310131300EST

!LOU EKX AD AIRPORT CLSD EXC 1 HR PPR DAILY

5−1−2 Movement Area NOTAMs

SS-SR 1311221500-1312221100

!AOO 29D AD AIRPORT CLSD EXC PPR MON−FRI 0330−1430 1310120330-1310171430

!BUF D67 AD AIRPORT CLSD EXC HI−WING ACFT 1310122330-1310131300 !CDB KVC AD AIRPORT CLSD 1310122330-PERM

!RIU O88 AD HELIPORT CLSD 1310122330-PERM

!DAY O12 AD SEAPLANE BASE CLSD 1309041400−1309041800

!CDB AKA AD AIRPORT OPEN 1309041800-PERM

NOTE− AKA airport was published as being closed.

EXAMPLE− !CLE 15G AD AIRPORT NOW PUBLIC 1309041800-PERM

NOTE− 15G is now open to the public and a public-use airport.

EXAMPLE− !CLE 15G AD AIRPORT NOW PRIVATE 1309041800-PERM

NOTE− 15G is now closed to the public and is no longer a public-use airport. The NFDC must contact the USNOF to have 15G 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 Movement Area - Surface

ASPH Asphalt/tarmacadam

CONC concrete

GRVL gravel

DIRT dirt

SOD sod

TBL 5−1−2 Movement Area - Lighting

LGTD lighted

NOT LGTD unlighted

EXAMPLES− !ICT ICT RWY 1L/19R COMMISSIONED 10301FT X 150FT CONC LGTD. DECLARED DISTANCES: RWY 1L TORA 10301 TODA 10301 ASDA 10301 LDA 10301. RWY 19R TORA 10301 TODA 10301 ASDA 10301 LDA 10301 1310122330−PERM

!ICT ICT TWY M8 COMMISSIONED 500FT X 75FT CONC LGTD 1310122330 - PERM

3. Closure of a movement area or portion thereof.

EXAMPLES− !BNA BNA APRON NORTH APRON CLSD 1309041800-1309062200EST

!BNA BNA APRON NORTH APRON EAST SIDE CLSD 13111221500-1312220700

!TYS TYS TWY A3, A4, A5 CLSD 1309041800-1309062200EST

!TYS TYS TWY A BTN TWY A2 AND TWY A3 CLSD 1311221500-1312220700

!EKX EKX TWY ALL CLSD 1309041800-1309062200EST

!DFW DFW TWY JS SOUTH 200FT, TWY ER WEST OF TWY K CLSD 1309041800-1309062200EST

!DFW DFW 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 1309041800-1309062200EST

!BNA BNA RWY 36 CLSD 1309131300−1309132000EST

!BDL BDL RWY 6/24 CLSD EXC 1 HR PPR 203−627−3001 1309131300−1309132000EST

NOTE− Runways 6 and 24 are closed except by 1 hour prior permission from that telephone number during the times stated.

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

5−1−3 Movement Area NOTAMs

EXAMPLES− !TYS TYS TWY C CLSD 1309041800-PERM !ICT MEJ RWY 17/35 CLSD 1310122330-PERM

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

EXAMPLE− !BNA M54 RWY 18/36 CLSD TO JET ACFT 1309131300−1309132000EST

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

EXAMPLE− !BIG BIG RWY 9/27 CLSD TO ACFT MORE THAN 13500LB 1309131300−1309132000EST

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

EXAMPLES− !ICT 3K7 RWY 17/35 CLSD TO ACFT 4000LB OR MORE 1311211450-1311211700EST

!CMH CMH RWY 10R/28L CLSD EXC ACFT 12000LB OR MORE 10 MIN PPR DAILY 1330-2200 13112111330-1311212200EST

!GNV 31J RWY 10/28 E 3800FT CLSD EXC ACFT MORE THAN 12500LB DAILY 1200−2100 1311211200-1311212100EST

!CLE CLE RWY 16/34 CLSD TO ACFT WINGSPAN MORE THAN 70FT AND TO ACFT TAIL HEIGHT MORE THAN 49FT 1309131300−1309132000EST!ICT MEJ RWY 17/35 CLSD 1310122330-PERM

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− !CLT CLT RWY 5 CLSD TO LDG ACFT 1306110300 – 206112100EST

!PDX PDX RWY 3 CLSD TO DEPARTING ACFT 1306110300-1306112100EST

!DAY I17 RWY 8/26 CLSD TO TGL 1309131300−1309132000EST

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− !MKC MKC RWY 19 THR DISPLACED 300FT NOT STD MARKING. DECLARED DISTANCES: TORA 6827 TODA 6827 ASDA 6827 LDA 6527. 130601150300–1307141600EST

!MKC MKC RWY 1 DECLARED DISTANCES: TORA 6827 TODA 6827 ASDA 6527 LDA 6527. 130601150300–1307141600EST

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

EXAMPLES− !ORD ORD RWY 28 THR DISPLACED 1500FT. DECLARED DISTANCES: TORA 13001 TODA 13001 ASDA 13001 LDA 11501. 1306110300–1306130600EST

!ORD ORD RWY 10 DECLARED DISTANCES: TORA 13001 TODA 13001 ASDA 11501 LDA 11501. 1306110300–1306130600EST

NOTE− A temporary structure becomes a controlling obstacle to the approach of Runway 28 and departure of Runway 10 resulting in the Runway 28 threshold being displaced 1500 feet resulting in changes to declared distances to Runways 10 and 28.

EXAMPLE− !CLT CLT RWY 5/23 NE 500FT CLSD. DECLARED DISTANCES: RWY 5 TORA 7002 TODA 7002 ASDA 7002 LDA 7002 RWY 23 TORA 7002 TODA 7002 ASDA 7002 LDA 7002. 1306110300–1306112100EST

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

EXAMPLE− !MEM MEM RWY 9/27 WEST 500FT CLSD FOR TKOF. DECLARED DISTANCES: RWY 9 TORA 8446 TODA 8446 ASDA 8446 LDA 8446 RWY 27 TORA 8946 TODA

5−1−4 Movement Area NOTAMs

8946 ASDA 8246 LDA 8246. 1306110300–1306112100EST

NOTE− The west 500 feet of Memphis’ Runway 9 is closed. Aircraft will enter the runway and depart Runway 9 from an intersecting taxiway. Because the NOTAM uses both runways as the runway designator, if any declared distance has changed, all declared distances for both runways must be included in the NOTAM.

(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 were published and need to be corrected.

EXAMPLE− !CLT CLT RWY 5/23 DECLARED DISTANCES: RWY 5 TORA 7502 TODA 7502 ASDA 7202 LDA 7202. RWY 23 TORA 7502 TODA 7502 ASDA 7202 LDA 7202. 1307140300–PERM

NOTE− A temporary or permanent situation at an airport with non-standard Runway Safety Areas or Object Free Area leads to defining declared distances.

EXAMPLE− !JAX JAX RWY 8/26 DECLARED DISTANCES: RWY 8 TORA 10000 TODA 10500 ASDA 10000 LDA 10000RWY 26 TORA 10000 TODA 10000 ASDA 10400 LDA 11000. 1306110300–PERM

NOTE− A NOTAM is required to correct an error in the Airport Facility Digest (AFD) until the next AFD publication date.

EXAMPLE− !JAX JAX RWY 8/26 NOW 10000FT X 150FT . DECLARED DISTANCES: RWY 8 TORA 9000 TODA 9500 ADSA 9000 LDA 9000. RWY 26 TORA 9000 TODA 9000 ASDA 9400 LDA 10000. 1306110300–PERM

6. Change of runway identification.

EXAMPLE− !PRC SJN RWY 13/31 CHANGED TO RWY 14/32

1308151200-PERM 7. Change of traffic pattern.

EXAMPLE− !PRC PRC RWY 3L RIGHT PATTERN DAILY 1300-1800 1309151300-1309201800

8. Runway Visual Range (RVR). When originating a NOTAM on RVR, RVR touchdown (RVRT),

RVR midpoint (RVRM), and RVR rollout (RVRR), the originator may specify the runway pair designators, if applicable, only when the entire RVR system is out of service.

EXAMPLES− !BWI BWI RWY 10/28 RVR OUT OF SERVICE 1310090815-1310151500

!BWI BWI RWY 10 RVR OUT OF SERVICE 1310090815-1310151500

9. Surface Markings and Signage.

(a) Exclamation point (!).

(b) Accountability.

(c) Airport designator.

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

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

(f) Geographical Relationship of surface from relevant intersection/point of reference, (NORTH OF, EAST OF), if needed.

(g) Name of sign/surface marking.

(h) Sign/surface marking location from users’ perspective (LEFT/RIGHT SIDE), as needed.

(i) Condition. For example, NOT STD, NOT LGTD, OBSC.

(j) Remarks (optional).

(k) Schedule, if needed.

(l) Effective time/expiration time.

EXAMPLES− !IAD IAD TWY U7 HOLDING POSITION SIGN FOR RWY 1L/19R NOT LGTD 1305112300-1305131200EST

!MBS MBS TWY ALL SURFACE PAINTED HOLDING POSITION SIGNS NOT STD DUE TO REPAINTING 1309271200-1309302300EST

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.

EXAMPLES− !MLT MLT RWY 16/34 UNMARKED

5−1−5 Movement Area NOTAMs

1311121450-1401051800EST

!MDW MDW RWY 31C ENGINEERED MATERIAL ARRESTING SYSTEM NOT STD 1305141320-1305202200EST !MDW MDW RWY 31C ENGINEERED MATERIAL ARRESTING SYSTEM OUT OF SERVICE 1309151335-1309301200EST

!ILI ILI AD CARIBOU NEAR MVMT AREAS 1309251300-1309262200EST

!CAK CAK AD BIRD ACTIVITY NW SIDE 1309151335-1309301200EST

!FAI FAI RWY 2R/20L S 2600FT FROST HEAVES 1302271930-1304302200EST

!ORT TSG RWY 12/30 NUMEROUS 5IN CRACK 1312050100-1404301700EST

!TAL TAL RWY 6/24 W 1000FT 4IN RUTS 1312051400-1403301200EST

NOTE− NOTAM format for temporary field conditions (FICON) caused by weather phenomena, such as ruts in a snow covered runway, 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.

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.

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.

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.

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.

1. Use the word “THIN” for reporting contaminant depths of less than ⅛ inch.

2. The contaminant depth is specified in feet and inches.

TBL 5−1−3 Reportable Depth Measurements

Use value “1/8IN” 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−4. The contaminant depth is optional for taxiway and apron/ramp conditions.

e. Reporting the contaminants.

1. Only the contaminants marked with an “*” are to be accompanied by a depth. When reporting a

5−1−6 Movement Area NOTAMs

runway condition, a depth is mandatory with those contaminants marked by an asterisk, “*”, in TBL 5−1−4.

TBL 5−1−4 Reportable Contaminants

Water (⅛ inch and greater)

Frost

Slush*

Ice

Wet ice

Water* over ice

Wet snow*

Wet snow* over ice

Dry snow*

Dry snow* 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 to describe a surface that has been plowed or swept and has a surface condition that is different than the surrounding area. If other than the full width or length is treated, report the width and/or length and the condition of the treated portion of the surface. The treatment is omitted when the entire surface has been treated. When known, the surrounding area items will be specified as “REMAINDER.”

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

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.

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,” 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. 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 given to the flight service specialist.

g. CONDITIONS NOT MONITORED. When the field conditions will not be monitored, follow the most recent observation with the words “CONDI- TIONS NOT MONITORED (date/time) (date/time).” The time parameters specified must fall within the effective/expiration times.

h. Effective time/expiration time. FICON NOT- AMs are considered temporary, therefore an estimated expiration time for FICON NOTAMs must not exceed24 hours from the effective time, except:

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

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

3. When the FICON is “PILOT REPORTED,” the expiration time must not exceed 12 hours. Unless the NOTAM is canceled, the NOTAM will auto-expire, therefore “EST” is not permitted. The “PILOT REPORTED FICON” NOTAM must not cancel or otherwise affect a NOTAM advertising “CONDITIONS NOT MONITORED.”

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

1. Snow and ice.

EXAMPLE− !FOE FOE RWY 13/31 FICON WET ICE OBSERVED

5−1−7 Movement Area NOTAMs

AT 1301040230 CONDITIONS NOT MONITORED 1301040300-1301041045. 1301040253-1301041115EST

NOTE− The field conditions are not monitored from 0300UTC- 1045UTC. The airport operator expects to have a new NOTAM submitted by 1115UTC.

EXAMPLE− !FOE FOE RWY 13/31 PILOT REPORTED FICON 1/2IN WET SN OVER ICE OBSERVED AT 1301040738. 1301040745-1301041115

NOTE− A pilot has reported a field condition that was observed at 0738UTC during a period when a NOTAM was in effect stating “CONDITIONS NOT MONITORED.” The NOT- AM originator entered the PILOT REPORTED FICON NOTAM into the NOTAM system at 0745UTC and established an expiration time that matches the expiration time of the NOTAM advertising CONDITIONS NOT MONITORED. The originator must not establish an expiration time that exceeds 12 hours.

EXAMPLE− !MIV MIV RWY 10/28 FICON 1/4IN DRY SN OVER ICE OBSERVED AT 1312201200. 1312201202-1312201600EST

NOTE− Millville Runway 10/28 has ¼ inch of dry snow over ice. The depth of the ice layer is not reported. The conditions were observed at 1312201200.

EXAMPLE− !MOT MOT TWY C, C1, C6, D BTN RWY 13/31 AND TWY C FICON 1/2IN DRY SN OVER ICE OBSERVED AT 1312202200. 1312202203-1312210000EST

NOTE− Minot Airport has reported a number of taxiways to have ½ inch of dry snow over ice. The depth of the dry snow has been reported, however the depth of the contaminant is not required when reporting the conditions of taxiways or aprons/ramps. In this example, the depth of the dry snow is not required.

2. Plowed/swept.

EXAMPLE− !OQU OQU RWY 16/34 FICON SWEPT ICE SANDED OBSERVED AT 1311132112. 1311132115-1311140600EST

NOTE− Quonset State’s runway 16/34 has been swept. It is ice covered and has been sanded.

EXAMPLE− !OQU OQU RWY 16/34 FICON PLOWED 100FT WIDE DRY REMAINDER 1/2IN WET SN OVER ICE OBSERVED AT 1311132112. 1311132115-1311140600EST

NOTE− Quonset State’s runway 16/34 is wider than 100 feet and the area inside the center 100 feet has been plowed and is free of contaminants. The remainder of the runway is covered with ½ inch of wet snow over ice.

EXAMPLE− !FAI INR RWY 16/34 FICON PLOWED 50FT WIDE 4IN WET SN REMAINDER 18IN WET SN OBSERVED AT 1311132300. 1311132300-1311141200EST

NOTE− McKinley National Park Airport 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− !OQU OQU RWY 16/34 FICON PLOWED 100FT WIDE WET REMAINDER 1/2IN WET SN OVER ICE OBSERVED AT 1311132112. 1311132115-1311140500EST

NOTE− Quonset State’s 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− !FAI FAI RWY 1/19 NORTH 2700FT FICON SWEPT 75FT WIDE PATCHY THIN COMPACTED SN REMAINDER 8IN DRY SN OBSERVED AT 1310131530. 1310131530-1310131930EST

NOTE− Fairbanks’ Runway 1/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 thin compacted snow while the remainder of the runway has 8 inches of dry snow.

EXAMPLE− !MOT MOT TWY ALL FICON PLOWED 50FT WIDE DRY REMAINDER DRY SN OBSERVED AT 1312202200. 1312202200-1312210900EST

NOTE− Minot Airport taxiways were plowed 50 feet wide and are dry The part that has not been plowed has dry snow. The depth of the dry snow is not required for conditions on taxiways.

EXAMPLE− !OQU OQU RWY 16/34 FICON PLOWED 75FT WIDE COMPACTED SN REMAINDER 1/2IN WATER OVER COMPACTED SN OBSERVED AT 1311132112. 1311132120-1311141000EST

NOTE− Quonset State Airport’s 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 water

5−1−8 Movement Area NOTAMs

over compacted snow. The depth is not reported for compacted snow.

3. Snowbanks.

EXAMPLE− !OQU OQU RWY 16/34 FICON COMPACTED SN 12IN SNOWBANKS OBSERVED AT 1311132112. 1311132120-1311141000EST

NOTE− Quonset State’s 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− !BTV BTV RWY 15/33 FICON PLOWED 100FT WIDE COMPACTED SN 24IN BERM OBSERVED AT 1310091411. 1310091415-1310092200EST

NOTE− Burlington International Airport’s 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− !BGR BGR TWY ALL FICON WET 4FT SNOWBANK OBSERVED AT 1312121149. 1312121200-1312130000EST

NOTE− Bangor International Airport reports all taxiways as being wet with snowbanks reaching 4 feet in depth.

4. Ice.

EXAMPLE− !MKC MKC RWY 1/19 NORTH 2000FT FICON ICE REMAINDER 1IN SLUSH OBSERVED AT 1302241100. 13022241107-1302241700EST

NOTE− The north 2000 feet of Kansas City Downtown Airport’s runway 1/19 is covered with ice. The remainder has 1 inch of slush.

EXAMPLE− !MEM MEM APRON FEDEX FEEDER RAMP WEST 700FT FICON ICE OBSERVED AT 1311220815. 1311220818-1311221200EST

NOTE− The west 700 feet of the FedEx Feeder Ramp at Memphis International Airport is covered with ice. The depth of ice is not reported.

EXAMPLE− !ENA BGQ RWY 7/25 WEST 1200FT FICON PATCHY ICE REMAINDER WET OBSERVED AT 130131910. 130131919-1302010400EST

NOTE− The west 1200 feet of runways 7/25 are covered by patchy ice. The remainder of runways 7/25 has visible moisture, described as “WET.”

EXAMPLE− !ENA BGQ RWY 7/25 FICON PLOWED 50FT WIDE 1/2IN WET SN OVER ICE REMAINDER 2IN WET SN OVER COMPACTED SN OBSERVED AT 1301311910. 130131915-1302010400EST

NOTE− The full length of Big Lake airport runways 7/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.

EXAMPLE− !CLE CLE RWY 10/28 FICON 1/2IN WATER OVER ICE OBSERVED AT 1310241700. 1310241707-1310250100EST

NOTE− Cleveland’s runway10/28 has up to ⅜ inch of water over ice observed on the runway. Contaminant depths exceeding ¼inch to and including ½ inch are reported as ½ inch.

5. Wet.

EXAMPLE− !CLE CLE RWY 10/28 FICON WET OBSERVED AT 1311231400. 1311231400- 1311241400EST

NOTE− Cleveland’s runway 10/28 has visible moisture but less than ⅛ inch of water.

6. Frost.

EXAMPLE− !JNU JNU TWY ALL FICON FROST OBSERVED AT 1309132315. 1309132315-1309140400EST

NOTE− Frost is observed on all taxiways at Juneau Airport.

7. Snow.

EXAMPLE− !ENA 5HO RWY 16/34 FICON PATCHY COMPACTED SN OBSERVED AT 1309131520. 1309131527-1309141527EST

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

EXAMPLE− !ENA CLP RWY 8/26 FICON THIN WET SN OBSERVED AT 1312132300. 1312132310-1312142300EST

5−1−9 Movement Area NOTAMs

NOTE− Clarks Point’s runway 8/26 is covered by less than ⅛ inch of wet snow.

EXAMPLE− !ANI ANI RWY 10/28 FICON 2IN DRY SN OVER COMPACTED SN OBSERVED AT 1311132000. 1311132004-1311132200EST

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

EXAMPLE− !MEM MEM APRON FEDEX FEEDER RAMP FICON DRY SN OBSERVED AT 1312292345. 1312292348-1312300200EST

NOTE− The FedEx Feeder ramp at Memphis International Airport is covered by dry snow. The depth of the contaminant on an apron/ramp is not required.

EXAMPLE− !BNA BNA APRON AIR CARGO APRON EAST 500FT FICON PLOWED 1IN WET SN OBSERVED AT 1312202000. 1312202003-1312210400EST

NOTE− The east 500 feet of Nashville Airport’s Air Cargo apron has been plowed. An inch of wet snow has accumulated since being plowed.

8. Slush.

EXAMPLE− !TYS TYS TWY ALL EXC TWY G FICON SLUSH OBSERVED AT 1312231220. 1312231220-1312231400EST

NOTE− All of the taxiways at the McGhee Tyson Airport, except taxiway G, are covered by slush. The depth off the contaminant is not required when reporting the conditions of taxiways or aprons/ramps. In this example, the depth is not required.

9. Drift.

EXAMPLE− !SFF SFF RWY 3R/21L FICON 4IN DRY SN 9IN DRIFT OBSERVED AT 1311071900. 1311071906-1311080001EST

NOTE− Spokane’s Felt Field’s Runway 3R/21L is covered with 4 inches of dry snow and 9 inch snow drifts.

EXAMPLE− !AVP AVP RWY 4/22 FICON DRY 5IN DRIFT OBSERVED AT 1312201600. 1312201609-1312210400EST

NOTE− The Wilkes Barre/Scranton International Airport’s Runway 4/22 is contaminant free, however there are 5 inch snow drifts on the surface.

10. Sanded.

EXAMPLE− !MGW MGW RWY 18/36 FICON ICE SANDED OBSERVED AT 1311021254. 1311021300-13111031300EST NOTE− Morgantown Municipal Airport’s Runway 18/36 is covered by ice and has been treated with sand. The depth of ice is not reported. EXAMPLE− !YAK YAK RWY 11/29 FICON THIN DRY SN OVER ICE SANDED 80FT WIDE OBSERVED AT 1312061524. 1312061530-1312062000EST NOTE− Yakutat Airport’s Runway 11/29 is covered with less than ⅛inch 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.

11. Deiced.

EXAMPLE− !IAD IAD RWY 12/30 FICON WET DEICED LIQUID OBSERVED AT 1312172057. 1312172100-1312180800EST NOTE− Dulles International Airport’s Runway 12/30 is wet and has been treated with a liquid deicing chemical. EXAMPLE− !IAD IAD RWY 12/30 FICON DRY DEICED SOLID 100FT WIDE REMAINDER ICE OBSERVED AT 1312172058. 1312172100-1312180800EST NOTE− Dulles International Airport’s 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.

12. Miscellaneous (ruts, soft edge, mud, ash, rubber).

EXAMPLE− !TAL TAL RWY 6/24 FICON 6IN COMPACTED SN 3IN RUTS W 1000FT OBSERVED AT 1312051352. 1312051400-1312061400EST NOTE− Ralph Calhoun Memorial Airport’s Runway 6/24 is covered with compacted snow. Airport activity has created 3 inch ruts in the west 1000 feet of the runway. The depth of the compacted snow is not reportable. EXAMPLE− !TAL TAL RWY 6/24 FICON WET SOFT EDGES

5−1−10 Movement Area NOTAMs

OBSERVED AT 1311051615. 1311051622-1311061600EST

NOTE− Ralph Calhoun Memorial Airport’s Runway 6/24is wet and has soft edges.

EXAMPLE− !ENA ENA RWY 1R/19L N 700FT FICON 2IN MUD OBSERVED AT 1310132135. 1310132140-1310140600EST

NOTE− Kenai Municipal Airport’s Runway 1R/19L north 700 feet is covered with 2 inches of mud.

EXAMPLE− !ENA ENA RWY 1L/19R FICON THIN ASH OBSERVED AT 1309132210. 1309132213-13309141200EST

NOTE− Kenai Municipal Airport’s Runway 1L/19R is covered with less than ⅛ inch volcanic ash.

EXAMPLE− !MKC MKC RWY 1/19 N 800FT FICON RUBBER OBSERVED AT 1307191056. 1307191103-1308302000EST

NOTE− The north 800 feet of Kansas City Downtown Airport’s Runway 1/19 is covered by rubber. The depth of rubber is not reportable. Although the rubber is observed only at the approach end of Runway 1, 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.

3. NOTAMs for MU values may 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.

EXAMPLES− !DCA DCA RWY 18 FICON RFT MU 40/30/40 OBSERVED AT 1312211100. 1312111105-1312111500EST

!RIC RIC RWY 36 FICON TAP MU 20/20/20

OBSERVED AT 1309011200. 1309011213-1309011400EST

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

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.

6. Use the following abbreviations (not all encompassing) to indicate the type of friction measuring device used.

TBL 5−1−5 Friction Measuring Devices

BOW Bowmonk Decelerometer (Bowmonk Sales)

BRD Brakementer – Dynometer

ERD Electronic Recording Decelerometer (Bowmonk)

GRT Griptester (Findlay, Irvine, LTD)

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

NAC Neubert Aero Corp

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

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)

7. Braking action is reported as fair, poor, or nil, as received from airport management. Classify according to the most critical term used.

EXAMPLES− !ANC Z15 RWY 1/19 FICON BA NIL OBSERVED AT 1309041300. 1309041303-1309041500EST

5−1−11 Movement Area NOTAMs

!AKN AKN RWY 18/36 FICON BA POOR OBSERVED AT 1308051400. 1308051400-1308051600EST

!ANC ANC RWY 1/19 FICON BA FAIR OBSERVED AT 1310061500. 1310061500-3210061800EST

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.

3. Combining airport management and PIREP information is appropriate only with airport management authorization.

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 A/FD, which lists indices and ARFF equipment requirements.

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

REFERENCE− Title 14 CFR Part 139

EXAMPLES− !FTW FTW AD ARFF VEHICLE OUT OF SERVICE INDEX UNCHANGED 1310242100-1310262100EST

!FTW FTW AD ARFF VEHICLE OUT OF SERVICE 1310021200-1310121200EST

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− !FTW FTW AD ARFF NOW INDEX A 1309072300-1309092300EST

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

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

EXAMPLES− !STS STS AD ARFF NOT AVBL 1310021200-1310121200EST

!STS STS AD AIRPORT CLSD TO AIR CARRIER MORE THAN 30 PAX 1310021200-1310121200EST

b. Fuel services.

EXAMPLES− !CXO ARM AD FUEL 100LL NOT AVBL 1311011200-1311041800EST

!CLE CLE AD MOBILE JET A FUEL NOT AVBL 1311041600-1311151800EST

!LAX LAX AD HYDRANT FUEL NOT AVBL 1312011200-1312312359

c. MU-Friction Measuring Device.

EXAMPLE− !MSP MSP AD FRICTION MEASURING DEVICE OUT OF SERVICE 1309141000-1309211000EST

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

EXAMPLE− !BDL BDL AD CUSTOMS PROCESSING DELAYED DUE TO CAPACITY, INTERNATIONAL CARRIERS MAY EXPERIENCE SIGNIFICANT DELAYS IN CLEARING CUSTOMS, CONTACT AIRPORT MANAGEMENT AT XXX-XXX-XXXX 1310021200-1310121200EST

e. Aerodrome beacon (ABN). If either of the lights is out of service, the whole system is down.

EXAMPLE− !SPA SPA AD ABN OUT OF SERVICE 1310021200-1310121200EST

5−1−12 Movement Area NOTAMs

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

EXAMPLES− !ACY ACY AD WDI NOT LGTD 1308151200-1308152000

!SGF SGF AD WINDCONE NOT LGTD 1310051430-1310101200

!ACY ACY AD WDI FOR RWY 4 NOT LGTD 1311221500-1311251200

!MCI MCI AD WDI NOT AVBL 1309070700-1309101500

!BKL BKL AD WIND SOCK NOT AVBL 1303010600-1303071200EST

!DEN DEN AD WDI LEFT SIDE RWY 17L OUT OF SERVICE 1303010600-1303071200

5−1−6. WORK IN PROGRESS

Any NOTAM associated with work in progress on or adjacent to a runway, taxiway, apron/ramp, or aerodrome must be formatted as follows:

a. Exclamation point (!).

b. Accountability.

c. Airport designator.

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, BTN TW A AND TWY B.

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; “WORK IN PRO- GRESS.”

NOTE− Any NOTAM associated with snow/ice removal must be described as “WORK IN PROGRESS (reason);” for example, SNOW REMOVAL, ICE REMOVAL. Airport operators must ensure this NOTAM remains active only

when actual snow and ice removal operations are taking place.

h. Reason (optional). 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.

i. Remarks, if needed.

j. Schedule, if needed; for example, “DAILY 1200-1800.”

k. Effective time/expiration time.

EXAMPLES− !IAD IAD RWY 1L/19R WORK IN PROGRESS RESURFACING 1309070700-1309101500

!SBY SBY TWY E BTN RWY 5/23 AND TWY A WORK IN PROGRESS TRENCHING 1309070700-1309101500

!SBY SBY TWY E BTN RWY 5/23 AND TWY A WORK IN PROGRESS TRENCHING SOUTH SIDE 1309070700-1309101500

!MEM MEM APRON FEDEX FEEDER RAMP WORK IN PROGRESS RESURFACING WEST HALF 1309070700-1309101500

!CHO CHO RWY 21 WORK IN PROGRESS RWY LGT REPLACEMENT NORTHEAST TWY E 1309070700-1309101500

!IAD IAD RWY 1L/19R WORK IN PROGRESS MOWING ADJ NE 500FT 1309070700-1309101500

!IAD IAD RWY 1L/19R WORK IN PROGRESS MAINTENANCE VEHICLES EAST SIDE OF RWY 1309070700-1309101500

!MEM MEM APRON FEDEX FEEDER RAMP WORK IN PROGRESS RESURFACING WEST HALF 1309070700-1309101500

!ICT ICT AD ALL SURFACES WORK IN PROGRESS SNOW REMOVAL 1312070700-1312101500EST

!MCI MCI RWY 1L/19R WORK IN PROGRESS SNOW REMOVAL 1312070700-1312101500

!DSM DSM TWY D4, D5, D6, TWY B BTN RWY 13/31 AND TWY D, TWY D WEST OF RWY 5/23 WORK IN PROGRESS SNOW REMOVAL 1312070700-1312101500

!FAI FAI APRON EAST RAMP WORK IN PROGRESS

5−1−13 Movement Area NOTAMs

SNOW REMOVAL EAST HALF 1312070700-1312101500EST

5−2−1 Lighting Aid and Obstruction NOTAMs

Section 2. Lighting Aid and Obstruction NOTAMs

5−2−1. LIGHTING AIDS

Originate NOTAMs on lighting aids for public-use civil landing areas listed in the A/FD. NOTAMS regarding lighting aids are originated as follows:

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

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

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

EXAMPLES− !ANB EUF RWY 36 ALS DECOMMISSIONED 1306011300-PERM

!ANB EUF RWY 18 ALS OUT OF SERVICE 1310112300-1310131200EST

!CLE CLE RWY 6L ALS OUT OF SERVICE EXC SSALR 1307112300-1307131200EST

b. Lead off /lead on lights.

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.

EXAMPLES− !IAD IAD RWY 1C LEAD OFF LGT FOR TWY Y4 OUT OF SERVICE 1309112300-1309131200EST

!IAD IAD RWY 1C LEAD ON LGT FOR TWY Y9 OBSC 1305112300-1305131200EST

c. Runway status light system.

EXAMPLE− !MCO MCO RWY 18L RUNWAY STATUS LGT SYSTEM OUT OF SERVICE 1300111200-1303311830EST

1. Runway entrance lights.

EXAMPLES− !PHL PHL TWY ALL RUNWAY ENTRANCE LGT FOR RWY 9L SOUTH SIDE OUT OF SERVICE 1302011200-1302031500EST

!PHL PHL TWY K5, K6, T RUNWAY ENTRANCE LGT FOR RWY 9L OUT OF SERVICE 1311232300-1315251200EST

2. Take-off hold lights.

EXAMPLE− !BWI BWI RWY 28 TKOF HOLD LGT OUT OF SERVICE 1311232300-1315251200EST

d. Sequence flashing lights/runway alignment indicator lights.

EXAMPLES− !ANB EUF RWY 18 SEQUENCED FLASHING LGT OBSC 1305112300-1305131200EST

!ANB EUF RWY 18 RAI LGT OUT OF SERVICE 1305112300-1305131200EST

e. Visual approach lighting.

1. Visual approach slope indicator (VASI).

EXAMPLES− !SBY SBY RWY 5 VASI OUT OF SERVICE 1309111200-1309131200EST

!RIC RIC RWY 22 VASI LEFT SIDE OUT OF SERVICE 1305112300-1305131200EST

!BTL BTL RWY 13 VASI UNUSABLE 5 DEG LEFT OF COURSE 1311041400-1312301930

2. Precision approach path indicator (PAPI).

EXAMPLE− !IAD IAD RWY 1L PAPI OUT OF SERVICE 1311031200-131142200EST 3. Runway end identifier lights.

EXAMPLE− !DCA DCA RWY 18 RUNWAY END IDENTIFIER LGT OUT OF SERVICE 1305112300-1305131200EST

4. Threshold lights (THR LGT).

EXAMPLES− !SAV SAV RWY 27 THR LGT OUT OF SERVICE 1305112300-1305131200EST

f. Runway edge lights (EDGE LGT).

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

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

EXAMPLE− !BNA BNA RWY 13/31 EDGE LGT OUT OF SERVICE 1305112300-1305131200EST 3. Runway lights obscured due to snow and ice.

5−2−2 Lighting Aid and Obstruction NOTAMs

EXAMPLE− !BTV BTV RWY 15/33 EDGE LGT OBSC 1310131300−1310141300EST

NOTE− 1. All runway 15/33 edge lights 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− !ATL ATL RWY 8R/26L RCLL OUT OF SERVICE 1305112300-1305131200EST

h. Touchdown zone lights (TDZ LGT).

EXAMPLE− !ATL ATL RWY 8R TDZ LGT OUT OF SERVICE 1305112300-1305131200EST

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

EXAMPLE− !DCA DCA RWY 18 RLLS OUT OF SERVICE 1305112300-1305131200EST

j. Airport lighting total power failure.

EXAMPLE− !SPA SPA AD LGT ALL OUT OF SERVICE 1305112300-1305131200EST

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

EXAMPLES− !SBY SBY SVC PCL ALL OUT OF SERVICE 1305112300-1305131200EST

!JLN JLN SVC PCL RWY 18/36 EDGE LGT OUT OF SERVICE 1305112300-1305131200EST

!ANB EUF SVC PCL RWY 18 VASI OUT OF SERVICE 1305112300-1305131200EST

!JLN JLN SVC PCL RWY 18 ALS OUT OF SERVICE 1305112300-1305131200EST

!JLN JLN SVC PCL RWY 18/36 OUT OF SERVICE EXC LOW INTST 1305112300-1305131200EST

NOTE− If the lights are set on continuous as result of the PCL outage, the PCL OUT OF SERVICE NOTAM must be canceled and a new NOTAM originated regarding the condition/status of the affected lighting system.

EXAMPLES− !BFD 8G5 SVC PCL RWY 14/32 COMMISSIONED FREQ 122.7 DAILY 0200-1100 1305110200-1305131100EST

!SBY SBY SVC PCL FREQ CHANGED TO 122.8 1305112300-PERM NOTE− PCL frequency need not be an ATC frequency.

l. Taxiway lighting.

1. Taxiway edge lights.

EXAMPLE− !SHD SHD TWY K, L EDGE LGT OUT OF SERVICE 1305112300-1305131200EST 2. Runway lights obscured due to snow and ice.

EXAMPLE− !ROA ROA TWY E CL LGT BTN TWY E1 AND RWY 15/33 OUT OF SERVICE 1305112300-1305131200EST 3. Runway guard lights.

EXAMPLE− !MCI MCI TWY ALL RUNWAY GUARD LGT FOR RWY 1L/19R OUT OF SERVICE 1305112300-1305131200EST 4. Stop bar lights.

EXAMPLE− !SEA SEA TWY C STOP BAR LGT FOR RWY 16R/34L AND FOR EAST SIDE RWY 16L/34R OUT OF SERVICE 1305112300-1305131200EST

5. Taxiway lights obscured due to snow and ice.

EXAMPLE− !BTV BTV TWY C EDGE LGT OBSC 1310131300−1310141300EST 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−2. TOWER LIGHT OUTAGES

a. The NOTAM text for telecommunication antenna tower light outages must be formatted as follows:

1. Exclamation point (!).

2. Accountability.

3. Location designator.

4. Keyword “OBST.”

5. Specify the attribute “TOWER LGT.”

6. The FCC antenna structure registration (ASR) number in parentheses.

5−2−3 Lighting Aid and Obstruction NOTAMs

7. Obstruction location by latitude and longitude to the nearest one hundredth of a second.

8. Plain language location in parentheses.

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

(b) When the tower is within 500 feet either side of the centerline of a charted helicopter route (see 14 CFR Section 77.23), 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).

9. Specify the altitude MSL with the unit of measurement (FT).

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

NOTE− Height of tower lights on terrain (hills) are identified as MSL only.

11. Specify the condition “OUT OF SER- VICE.” A light condition of OUT OF SERVICE refers to a top light or flashing obstruction light regardless of its position.

12. Effective time/expiration time.

(a) When a notice of light outage is received without an expiration time, inform the sponsor that you will be adding 15 days to the current time for the expiration time, at which time the NOTAM will be auto canceled. Advise the sponsor that a NOTAM must be canceled in the event that the return-to-service time is earlier than 15 days.

(b) When a tower light outage NOTAM is auto canceled after 15 days, the canceled NOTAM, including the tower’s ASR number will be forwarded to the appropriate FCC field office.

NOTE− Appendix C lists FCC Field Office FAX numbers.

EXAMPLES− !GSP GSP OBST TOWER LGT (ASR 1234567) 345313.12N0815744.34W (3NM SSW SPA) 1528FT (564FT AGL) OUT OF SERVICE 1310291200-1311131200

Continue reading ↓ 120 of 227 passages shown