Radar Vectors
Advisory Circular Current Issued May 25, 2022 AAS-300 72 pages Copy saved Nov 18, 2026

AC 150/5200-28G Notice to Air Missions (NOTAMs) for Airport Operators

This AC contains standards and guidance for airport operators on the issuance of Notice to Air Missions (NOTAM). It provides guidance on using the NOTAM system for airport condition reporting and procedures used to describe, format, and disseminate information on unanticipated or temporary changes to components of, or hazards in, the National Airspace System (NAS).

Official source ↗ Open PDF

U.S. Department of Transportation Federal Aviation Administration

Advisory Circular

Subject: Notice to Air Missions (NOTAMs) for Airport Operators

Date: 5/25/2022 Initiated By: AAS-300

AC No: 150/5200-28G

1 Purpose. This Advisory Circular (AC) contains the Federal Aviation Administration (FAA) standards and guidance for airport operators on the issuance of Notice to Air Missions (NOTAM). This AC provides guidance on using the NOTAM system for airport condition reporting and procedures used to describe, format, and disseminate information on unanticipated or temporary changes to components of, or hazards in, the National Airspace System (NAS). The NOTAM system is not intended to be used to advertise data already published or charted.

2 Cancellation. This AC cancels AC 150/5200-28F, Notices to Airmen (NOTAMs) for Airport Operators, dated December 30, 2016.

3 Applicability. The FAA standards and guidance in this AC is provided for airport operators, or their agents, who monitor and manage the day-to-day operation of the airport and who may also have operational responsibility for certain airport-related facilities. The audience for this AC is any office responsible for originating airport related NOTAMs. The standards and guidance in this AC are not legally binding in their own right and will not be relied upon by the FAA as a separate basis for affirmative enforcement action or other administrative penalty. Conformity with this AC is voluntary only and nonconformity will not affect rights and obligations under existing statutes and regulations, except as follows:

1. Use of the standards and guidance in this AC is mandatory for airports that receive funding under Federal grant assurance programs, including the Airport Improvement Program (AIP). See Grant Assurance #34.

2. Use of the standards and guidance in this AC is mandatory for projects funded by the Passenger Facility Charge (PFC) program. See PFC Assurance #9.

ii

3. This AC provides an acceptable means of meeting the requirements of 14 Code of Federal Regulations (CFR) Part 139, including § 139.339, Airport Condition Reporting.

4 Principal Changes. This AC adds new language on the use of PERM NOTAMs (interim NOTAMs associated with the publishing of permanent airport related information). This language clarifies the responsibilities and the overall process associated with the use of PERM NOTAMs. A list of information that should not be issued via NOTAM is being included to help NOTAM originators determine what information is acceptable as a NOTAM. A summary of changes is included below:

1. AC title changed from Notices to Airmen (NOTAMs) for Airport Operators to Notice to Air Missions (NOTAMs) for Airport Operators.

2. Paragraph 1.4 – PERM NOTAM language information added describing the occurrence when extend period NOTAMs are surpassed.

3. Paragraph 1.6 – Added new information to the airport operator responsibilities.

4. Paragraph 1.6.2 – Added new information on Flight Service Stations (FSS) responsibility to contact users on validity of NOTAMs lingering in the NOTAM system.

5. Paragraph 1.6.3 – Airports District Office (ADO) responsibilities identification changed to Regional Offices (Safety and Standards Branch) throughout the Advisory Circular.

6. Paragraph 1.6.4 – Added new information on United States NOTAMs Office (USNOF) responsibilities.

7. Paragraph 1.8.3 – Additional information added on determining NOTAM issuance criteria.

8. Paragraph 2.3.13 – New language added on the PERM NOTAM process and tools for moving PERM NOTAMs from the NOTAM system to the appropriate chart or publication.

9. Paragraph 2.3.14.4 – Added clarification language and examples on how to apply NOTAM information for spots, gates, or hardstands.

10. Paragraph 3.2.5 – Added new language on preventing surface condition NOTAMS on a closed runway and multiple NOTAMs for surface condition codes on the same runway.

11. Paragraph 3.15.2.5 – Added new language and NOTAM example for Runway End Light (RENL).

12. Paragraph 3.17.3 – Added new language on moving declared distance NOTAMs from the NOTAM system to the appropriate flight publication.

13. Paragraph 3.19 – Added new language and NOTAM examples for bird and wildlife activities.

iii

14. Appendix D – Added new Appendix D to illustrate the available tools and processes for publishing PERM NOTAM information.

5 Related Code of Federal Regulations (CFRs) and Reference Materials. The following are FAA regulations and publications (see current versions) used during the preparation of this AC and may provide useful supporting and/or supplemental information to airport operators, or their agents, in understanding and implementing this AC. Electronic versions of these documents are available online.

1. Electronic CFRs are available at www.ecfr.gov.

a. 14 CFR Part 77, Safe, Efficient Use, and Preservation of the Navigable Airspace

b. 14 CFR Part 139, Certification of Airports

c. 14 CFR Part 152, Airport Aid Program

d. 14 CFR Part 157, Notice of Construction, Alteration, Activation, and

Deactivation of Airports

e. 14 CFR Part 161, Notice and Approval of Airport Noise and Access Restrictions

f. 47 CFR Part 17, Construction, Marking, and Lighting of Antenna Structures

g. 49 CFR Part 1542, Airport Security

h. 49 CFR Part 1544, Aircraft Operator Security: Air Carriers and Commercial

Operators

2. Air Traffic publications are available at www.faa.gov/air_traffic/publications/.

a. FAA Order JO 7110.10, Flight Services

b. FAA Order JO 7110.65, Air Traffic Control

c. FAA Order JO 7210.3, Facility Operation and Administration

d. FAA Order JO 7340.2, Contractions

e. FAA Order JO 7350.9, Location Identifiers

f. FAA Order 7930.2, Notices to Air Missions (NOTAMs)

3. Aeronautical Information Manual (AIM). https://www.faa.gov/air_traffic/publications/atpubs/aim_html/

4. Pilot/Controller Glossary (P/CG). https://www.faa.gov/air_traffic/publications/media/pcg_10-12-17.pdf

5. Airport ACs (150 series) are available at www.faa.gov/airports/resources/advisory_circulars/.

a. AC 150/5200-30, Airport Field Condition Assessments and Winter Operations Safety

b. AC 150/5300-13, Airport Design

c. AC 150/5370-2, Operational Safety on Airports during Construction

iv

6. Other FAA ACs are available at www.faa.gov/regulations_policies/advisory_circulars/.

a. AC 70/7460-1, Obstruction Lighting and Marking

b. AC 91-79, Mitigating the Risks of a Runway Overrun Upon Landing

c. AC 120-57, Surface Movement Guidance and Control System

d. AC 121.195-1, Operational Landing Distances for Wet Runways; Transport

Category Airplanes

7. Other FAA Orders and Notices are available at http://www.faa.gov/regulations_policies/orders_notices/.

e. FAA Order 8900.1, Flight Standards Information Management System

f. FAA Order 5190.6, FAA Airport Compliance Manual

8. The Chart Supplement is available at http://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/dafd/.

9. Domestic/International Notices at http://www.faa.gov/air_traffic/publications/notices/.

10. NOTAM Search is available at http://notams.aim.faa.gov/notamSearch/.

11. Airport Improvement Program Grant Assurances are available at: https://www.faa.gov/airports/aip/grant_assurances/media/airport-sponsorassurances-aip-2020.pdf.

12. Passenger Facility Charge Program Assurances are available at: https://www.faa.gov/airports/pfc/media/pfc-assurance.pdf.

6 Questions and Comments. Use the Advisory Circular Feedback form at this end of this AC to send comments or suggestions for improving this AC. If you have questions about this AC, contact:

Federal Aviation Administration Office of Airport Safety and Standards, AAS-300 800 Independence Avenue, SW Washington, DC 20591 Telephone (202) 267-8731

John R. Dermody Director of Airport Safety and Standards

CONTENTS

Paragraph Page

v

Chapter 1. Background and Responsibilities … 1-1

Use of this AC … 1-1

Function of the NOTAM System … 1-1

Improper Use of NOTAM System … 1-1

Extended Period NOTAMs … 1-1

Airport Records and Controls … 1-2

Responsibilities … 1-2

Compliance … 1-5

Dissemination of NOTAMs … 1-6

Chapter 2. NOTAM Process … 2-1

Authority to Initiate a NOTAM … 2-1

NOTAM Criteria … 2-1

NOTAM Composition … 2-2

NOTAM Submission … 2-10

Verification Information … 2-11

NOTAM Management … 2-11

Chapter 3. Airport Condition NOTAMs and Reporting Process … 3-1

Reporting Tools … 3-1

Reporting Conditions … 3-1

Reportable Contaminants … 3-2

Reportable Depths … 3-5

Reporting Runway Percentage … 3-5

Runway Condition Assessment Matrix (RCAM) … 3-6

Examples of System Capabilities Associated Field Condition (FICON) NOTAMs … 3-9

Plowed and Swept Reporting … 3-15

Miscellaneous FICON (Mud, Ash) … 3-16

Slippery When Wet Runway Procedures … 3-16

Braking Action (Taxiways, Aprons, and Holding Bays) … 3-17

AC 150/5200-28G 5/25/2022

CONTENTS (CONTINUED)

Paragraph Page

vi

Pilot Reported Braking Action (PIREP) … 3-18

“Conditions (COND) Not Monitored (MNT)” NOTAMs … 3-18

“Surface (SFC) Conditions (COND) Not Reported (REP)” NOTAMs … 3-19

Runway Light Obscuration or Outages … 3-20

Other Reportable Conditions … 3-22

Runway Thresholds and Declared Distances … 3-23

On or Off Airport Obstructions and Obstruction Lights … 3-25

Birds and Other Wildlife … 3-28

Chapter 4. Select NOTAM Requirements Criteria … 4-1

Work In Progress (WIP) … 4-1

Certificated Airport Aircraft Rescue and Fire Fighting (ARFF) … 4-3

Engineered Materials Arresting Systems (EMAS) … 4-4

Sample NOTAM Log … A-1

Runway Condition Assessment Matrix (RCAM)* … B-1

Friction Measuring Equipment Abbreviations and Names … C-1

PERM NOTAM Publication Process Flowchart … D-1

FIGURES

Figure 2-1. Basic Outline of a NOTAM Content … 2-2

Figure 3-1. NOTAM Elements to Address Runway Light Obscuration or Outages … 3-20

Figure 3-2. NOTAM Elements to Address Runway Thresholds and Declared Distances … 3-23

Figure 3-3. NOTAM Elements for an Obstruction … 3-26

Figure 4-1. Work-in-Progress NOTAM Elements … 4-1

Figure 4-2. ARFF-related NOTAM Elements … 4-4

AC 150/5200-28G 5/25/2022

CONTENTS (CONTINUED)

Paragraph Page

vii

TABLES

Table 2-1. NOTAM Keywords / Definitions … 2-8

Table 3-1. Reportable Contaminant Definitions … 3-3

Table 3-2. Reportable Depth Measurements … 3-5

Table 3-3. Reporting Runway Percentage … 3-5

viii

Page Intentionally Blank

Figure 2-1: picture of page 6Figure 2-1 · page 6
Picture of the page from the copy saved here

Chapter 1. Background and Responsibilities › 1.4 Extended Period NOTAMs.

Chapter 1. Background and Responsibilities

Use of this AC. The Federal Notice to Air Missions (NOTAMs) System (FNS) as discussed in this Advisory Circular (AC) is tailored to airport condition and facility reporting needs. Additionally, it describes the preferred NOTAM system, in this case NOTAM Manager, airport operators should use. See paragraph 1.6.1.7 for information on NOTAM Manager.

Function of the NOTAM System. The FNS provides essential information to all airport users concerned with flight and airport operations. Using the FNS satisfies the requirements of 14 CFR § 139.339. The essential information functions associated with NOTAMs are:

Providing timely information on unanticipated or temporary changes to components of, or hazards in, the National Airspace System (NAS). Component changes may pertain to infrastructure, facilities, services, procedures, or hazards in the NAS.

Providing information that becomes available too late to publicize in the associated aeronautical charts and related publications.

Improper Use of NOTAM System NOTAMs should not be used to impose restrictions on airport access for the purpose of controlling or managing noise or to advertise data already published or charted.1

Extended Period NOTAMs. In general, NOTAMs are intended to be issued for temporary and short-term conditions and should remain in effect for 90 days or less when possible. Should an airport need a NOTAM longer than 90 days, the airport operator should submit the NOTAM information to the Federal Aviation Administration (FAA) via the PERM NOTAM process in paragraph 2.3.13, to have the information published in an appropriate FAA publication(s) and/or chart(s). The originator of the NOTAM should cancel the PERM NOTAM promptly after the relevant information is published elsewhere by the FAA.

1 After October 1, 1990, noise restrictions for airports are typically cleared through the FAA’s notice and review process, as required by the Airport Noise and Capacity Act of 1990. The process for compliance with this law is set forth in 14 Code of Federal Regulations (CFR) Part 161, Notice and Approval of Airport Noise and Access Restrictions. Contact the Regional Offices (Safety and Standards Branch) for guidance on complying with 14 CFR Part 161.

Chapter 1. Background and Responsibilities › 1.6 Responsibilities.

Airport Records and Controls.

Airports certificated under Part 139 and federally obligated airports have requirements for maintaining records. Specifically, under 14 CFR 139.339(d), airport operators must maintain “for at least 12 consecutive calendar months, a record of each dissemination of airport condition information to air carriers prescribed by this section,” including the dissemination of information using the NOTAM system for origination, modification, or cancelation of NOTAMs.

Airports may use information derived from the Federal NOTAM System (NOTAM Manager or E-NOTAM II (ENII), to create its own electronic archive of the system confirmation emails they receive when issuing, modifying, or cancelling a NOTAM. The airport operator is ultimately responsible for maintaining these records (as specified by Part 139) and therefore the Federal NOTAM System itself should only serve as a backup to the airport’s primary method of record retention for purposes of demonstrating compliance with part 139 recordkeeping requirements.

A sample NOTAM log is provided in Appendix A. Airport operators can use this sample form as a template to ensure basic NOTAM information is captured, distributed, and archived, including air carrier notification. Airport operators can modify the form to meet unique requirements at their facilities.

The NOTAM status of an airport should be checked and recorded daily, or more often if necessary, especially during inclement weather conditions.

Responsibilities.

Airport Operators. Airport operators have the following responsibilities under the FNS:

Making known, as soon as practicable, any condition, existing or anticipated, within five miles from the Airport Reference Point that will prevent, restrict, or present a hazard during the arrival or departure of aircraft. Local coordination with airport users such as air carriers and other commercial operations should be conducted as far in advance as possible to minimize the impact of construction projects, planned surface closures, or other conditions affecting operations on the airport.

Coordinating the issuance/cancellation of NOTAMs with the Air Traffic facility responsible for providing clearance to aircraft at the airport. This applies to both towered and non-towered airports and the coordination may include an enroute air traffic control facility (ARTCC), terminal radar approach control (TRACON) facility, Flight Service Station (FSS), or the airport traffic control tower (ATCT).

Reporting and updating airport field conditions, the condition of airport services, facilities, movement areas, parking areas, loading aprons, and

holding bays. Specific airport operator management responsibilities are outlined in Part 139, Certification of Airports; Part 152, Airport Aid Program; and Part 157, Notice of Construction, Alteration, Activation, and Deactivation of Airports.

Note: It is recommended that airport personnel operating on the airfield monitor the local traffic and air traffic frequencies. This will enable personnel to identify approaching aircraft, which may pose an operational safety risk, and allow time to avoid a conflict. For example, air traffic control and /or the pilots may not be aware of a runway closure at the nontowered airport. That is, sometimes a NOTAM is issued after an aircraft becomes airborne and the pilot did not receive the latest update, especially at an uncontrolled airport. The FAA recommends that NOTAMs for runway closures, snow removal operations, and any other lengthy maintenance activities at uncontrolled airports be directly coordinated with the overlying air traffic control facility (TRACON or ARTCC) when the operation will begin in less than 60 minutes.

Ensuring notifications are made no more than 7-days before an expected condition will occur. Public notification is accomplished through the NOTAM system. This same notification system should be used when the condition has been corrected or otherwise changed. Airport operators are also responsible for ensuring NOTAMs are current and cancelled when the conditions that prompted the NOTAMs no longer exist.

Acknowledging responsibility for facility components such as pavements, runway lights, and airport guidance sign systems. Other components, such as navigation facilities and approach lights, are usually the responsibility of the FAA. To avoid confusion, airport operators must initiate a NOTAM on a facility when its operation and maintenance are clearly within their area of responsibility. However, airport operators will make every effort to alert the responsible party when outages/discrepancies are observed for facilities that fall outside their area of responsibility.

Being aware, along with pilots, of Temporary Flight Restrictions (TFR) that may affect airport operations. TFR information is available at https://tfr.faa.gov/tfr2/list.html, 1800wxbrief.com, or by calling any FSS for a pilot briefing.

Keeping informed of NOTAM technology as advancements in NOTAM delivery capabilities change. Currently, the FAA web-based Digital NOTAM Manager is the preferred system for initiating NOTAMs. See paragraph 3.1.2. For information on obtaining NOTAM Manager or to access the FAA’s NOTAM Manager Self-Cert program, please go to https://notams.aim.faa.gov/ and select “Applications”.

Note: Whenever NOTAM modernization occurs, the FAA usually establishes a grace period during which the previous legacy system is phased out.

Keeping training programs up-to-date and maintained. As changes occur, airport staff must be trained on new processes and procedures, and training material must be updated, as provided under 14 CFR § 139.303.

Using the optional NOTAM Log (electronic or paper) in Appendix A or a downloaded history from the NOTAM Manager or ENII system, to be used as the primary or backup method for maintaining records of the origination, modification, cancellation, or tracking, of NOTAM activity, for purposes of demonstrating compliance with part 139 recordkeeping requirements.

Inputting Pilot Weather Report (PIREP) information into NOTAM Manager or E-NOTAMII, when received from aircraft operators or the ATCT, in order to assist in comparing PIREPs and airport operator condition assessments. See paragraph 3.12.2 for application.

Providing an up-to-date list of airport employees who are authorized to access and issue NOTAMs through NOTAM Manager, ENII, or to the FSS air traffic manager.

Respond to NOTAM inquiries from Regional Airport offices (Safety and Standards Branch), United States NOTAM Office (USNOF), and FSS or FSS representatives on matters pertaining to the NOTAM process.

Review and approve any NOTAMs which are expected to be in effect at the airport for 90 days or longer, for accuracy and necessity. NOTAMs associated with published information, which are intended to be a permanent change, should follow the PERM NOTAM process outlined in paragraph 2.3.13. The airport operator will need to monitor publishing dates to confirm the submitted information has been updated. Once the information has been published in an appropriate FAA publication or chart, the airport operator will need to cancel the corresponding NOTAM in the system.

Note: NOTAM information for permanent changes will not auto-cancel out of the NOTAM system when the alternate FAA publication is updated and requires action by the airport operator to be cancelled.

Flight Service. Flight Services System Operations Services, Flight Services, is responsible for ensuring that data submitted for NOTAM origination complies with the policies, criteria, and formats contained in this AC and FAA Order 7930.2. This responsibility is delegated to the Safety and Operations Policy Group, which oversees the FSS and FSS representatives. If there are questions on the validity of a NOTAM, a FSS

Chapter 1. Background and Responsibilities › 1.7 Compliance.

representative will attempt to contact the airport operator. When there is no response from the airport operator after 30 calendar days of multiple contact attempts, (e.g., phone and email), then FSS will inform the appropriate FAA Regional Airport office of the issue for assistance.

Regional Offices (Safety and Standards Branch). When requested by FSS, the regional office communicates with the airport operator to confirm if a NOTAM is still valid and, if needed, may ask the airport operator to submit a change to the FAA via the process in the PERM NOTAM paragraph 2.3.13.

U.S. NOTAM Office (USNOF). The USNOF is responsible for NOTAM formatting compliance. NOTAMs submitted through the FNS must be in the proper format. (See paragraph 2.3 for proper NOTAM format.) To ensure NOTAMs are issued in accordance with NOTAM policy pursuant to FAA Order 7930.2, USNOF will:

Maintain the integrity of the NOTAM system by managing it for compliance 24/7/365.

Process, store, and distribute NOTAMs through the NOTAM system.

Provide quality control during the review, processing, and origination of NOTAMs.

Notify the transmitting party when the USNOF determines that NOTAM information submitted is not in compliance with the criteria or procedures.

Ensure NOTAM policy questions are forwarded to the US NOTAM Governance Team for decision-making in consultation with other interested program offices.

To submit a NOTAM policy questions, go to: https://www.faa.gov/air_traffic/flight_info/aeronav/aero_data/Aeronautical_Inquiries/

Compliance.

Certificated Airports. The Office of Airport Safety and Standards is responsible for enforcing the airport operator responsibilities, as outlined in Part 139. Additionally, Office of Airport Safety and Standards has responsibility to collaborate with the USNOF on NOTAM criteria challenges and other concerns that will assist in improving the overall functionality and use of the NOTAM system.

Federally Obligated Airports. The Office of Airport Compliance and Management Analysis is responsible for enforcing those responsibilities at all airports with federal obligations, which includes

federal property transfer requirements and grant assurances. For the general compliance requirements of federally obligated airports that are not certificated under Part 139, see Part 152, Appendix D, and the current FAA Order 5190.6. A fundamental obligation on the sponsor is to keep the airport open for public use. Grant Assurance 19, Operation and Maintenance, requires the sponsor to protect the public using the airport by adopting and enforcing rules, regulations, ordinances, or policies as necessary to ensure safe and efficient flight operations. This obligation includes the following:

Chapter 1. Background and Responsibilities › 1.8 Dissemination of NOTAMs.

Field Lighting. If field lighting is installed, the sponsor must ensure the field lighting and associated airport beacon and lighted wind and landing direction indicators are operated every night of the year, or when needed. (See paragraph 7.12, Part-time Operation of Airport Lighting, in FAA Order 5190.6.) Properly maintaining marking, lighting, and signs can reduce the potential for pilot confusion and prevent a pilot deviation or runway incursion.

Warnings. If any part of the airport is closed, or if the use of any part of the airport is hazardous, the sponsor must provide warnings to users by issuing NOTAMs.

Safe Operations. The airport will be operated at all times in a safe and serviceable condition. The sponsor should adopt and enforce adequate rules, regulations, ordinances, or policies, as necessary, to ensure the safety and efficiency of aircraft operations and to protect the public using the airport. When a proposed action directly impacts the flight of an aircraft, that action should be coordinated with FAA Flight Standards and/or ATC.

Dissemination of NOTAMs.

Determining NOTAM Distribution. The USNOF is charged with monitoring the FNS for compliance with the criteria and procedures set forth in policy. When questions arise about NOTAM dissemination, formats, contractions, or other aspects of the distribution system, consult the USNOF.

Domestic NOTAMs. NOTAM (D) information is distributed for all public use airports, seaplane bases, and heliports listed in the Chart Supplement U.S. and all navigational facilities that are part of the NAS. The NOTAM (D) criteria of FAA Order 7930.2 requires wide dissemination of NOTAM (D) information via telecommunication and pertains to enroute navigational aids, facilities, services, and procedures, as listed in the Chart Supplement U.S.

Determining NOTAM Issuance Criteria.

NOTAMs should not be issued contrary to standards or guidance. This includes (but not limited to) NOTAMs with websites, commercial information, or non-safety critical changes.

The following examples typically would not meet criteria for issuance of a NOTAM, unless determined by the Office of Airports and the USNOF supervisory authority that it impacts safety:

1.8.3.2.1 The lack of ramp or apron marshalling services and road traffic control.

1.8.3.2.2 Activities such as parachuting, gliding, acrobatics, and training when conducted in uncontrolled airspace under Visual Flight Rules (VFR) conditions and when the activity is already published.

1.8.3.2.3 Electronic Navigational Aid (NAVAID) operating on or without emergency backup power or standby transmitter, except when applicable to Category (CAT) II/III Instrument Landing Systems (ILS).

1.8.3.2.4 When Air Traffic Services (ATS) are made available using contingency plans transparent to the users, such as call re-routing and remote monitoring.

1.8.3.2.5 Training activities by ground units (e.g., military operations at the airport).

1.8.3.2.6 Unavailability of back-up and secondary systems if these do not have an operational impact.

1.8.3.2.7 Announcement or warnings about possible/potential limitations without any operational impact.

1.8.3.2.8 General reminders on already published information.

1.8.3.2.9 Availability of equipment for ground units without containing information on the operational impact for airspace and facility users. (e.g., military operations at the airport).

1.8.3.2.10 Information about laser emissions without any operational impact or fireworks below minimum flying heights.

Page Intentionally Blank

Chapter 2. NOTAM Process › 2.2 NOTAM Criteria.

Chapter 2. NOTAM Process

Authority to Initiate a NOTAM.

Airport operators are responsible for observing and reporting the condition of airport facilities when temporary changes or outages could impact the NAS. See 14 CFR § 139.339(c)(9) and Grant Assurance 19. Airport operators are also responsible for initiating NOTAMs to report runway condition assessments and field condition (FICON). See 14 CFR § 139.339(c)(9) and Grant Assurance 19. FICONs are used to report surface conditions and braking action on runways, taxiways, and aprons/holding bays. The Runway Condition Assessment Matrix (RCAM) is the assessment tool airport operators use to identify and report runway surface conditions into the FNS. See Appendix B.

All airport operators are responsible for providing an up-to-date list of airport employees who are authorized to issue NOTAMs to the FSS air traffic manager. See 14 CFR § 139.339(e). At public airports without an airport manager, the FSS air traffic manager will coordinate with the appropriate airport operating authority to obtain a list of persons delegated to provide NOTAM information. Using authorized airport personnel will help expedite NOTAM processing because information obtained from unauthorized personnel will have to be confirmed and authenticated by the FSS before a NOTAM will be issued.

Authorized airport personnel who do not have access to NOTAM Manager, ENII, or applicable FNS technology can submit information for NOTAMs to FSS.

The airport operator should execute and maintain a Memorandum of Agreement (MOA), which is required before using NOTAM Manager, between the airport operator and the FAA outlining procedures used for originating NOTAMs. The Aeronautical Services Group (AJM-336) will provide the MOA template to the parties involved.

NOTAM Criteria. For airport operators awareness, FAA personnel tasked with accepting NOTAM information must use the official International Civil Aviation Organization (ICAO) contractions and abbreviations specified in FAA Order JO 7340.2 and the allowed exceptions found in FAA Order 7930.2 when composing NOTAMs. Plain language text is required when there is not an approved ICAO contraction.

Criteria for Publishing Airport NOTAMs. NOTAMs may be published to address the following conditions or categories of information:

Surface areas. Changes in hours of operations and hazards such as pavement issues, wildlife conditions, surface conditions, airport

Chapter 2. NOTAM Process › 2.3 NOTAM Composition.

construction, airport infrastructure deficiencies, airspace obstruction, and other hazardous conditions.

Public airports. Commissioning, decommissioning, openings, closings, and abandonments.

Aircraft Rescue and Fire Fighting (ARFF) capability. Restrictions to air carrier operations.

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

NAS lighting systems. Commissioning, decommissioning, outages, changes in classification or operation, as defined in AC 150/5340-30, Design and Installation Details for Visual Aids.

References: Aeronautical Information Manual (AIM), FAA Order JO 7930.2, and AC 120-57.

NOTAM Composition. The purpose of the NOTAM diagram below is to provide a basic outline of the content of a NOTAM. The elements keyword, attribute, activity or surface designator; condition, start of activity, and end of validity are mandatory. All other elements are included, as needed. The paragraphs below provide some examples for each of the elements of the NOTAM composition.

Figure 2-1. Basic Outline of a NOTAM Content

Keyword

Attribute, activity,

or surface designator

Surface Segment

Facility or

Service Location Lower Limit

Upper Limit Condition Reason Remarks Schedule Start of Activity

End of Validity

Exclamation Point (!). System-generated character that indicates the beginning of a NOTAM sentence.

Example: !

Accountability. Affixed by the NOTAM system (the identifier of the accountability location; for example, JFK, FDC,).

Example: ! JFK

Location Identifier. Location identifier for the facility the NOTAM will affect [the affected facility or location (airport, NAVAID, or Air Route Traffic Control Center (ARTCC)) appears after the NOTAM number]. Approach controls or airspace located within multiple ARTCC must have a separate NOTAM for each ARTCC.

Example: ! JFK JFK

Keyword. See Table 2-1 for keywords and definitions.

Example: ! JFK JFK RWY

Attribute, Activity, or Surface Designator(s) (when needed). A surface designator is required with keywords RWY, TWY, and APRON. Enter surface identification for runway-related NOTAMs, the taxiway identification for taxiway-related NOTAMs, or the apron identification for apron-related NOTAMs.

Note: If a facility component has not been given a specific identifying designation, such as an unnumbered or unlettered parking apron, associate it with a component that does have a positive identification.

Example: !JFK JFK RWY 04L/22R

Example: !JFK JFK TWY A, A1

Example: !JFK JFK APRON PRKG APN ADJ TWY A

Surface Segment (when needed).

Example: !JFK JFK TWY B BTN TWY C AND TWY D

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

Location description (when needed).

Lower Limit then Upper Limit or Height (when needed). Specify the limits as follows:

For Surface (SFC), use 1 to 17,999 with the unit of measurement (above ground level (AGL) or mean sea level (MSL)). For example, 50FT, 1275FT AGL, 10500FT MSL.

For 18,000 feet and above, express in flight levels (FL). For example, FL180, FL550, or UNL (unlimited; altitudes greater than 99,900 feet).

Heights AGL may be added when required or when MSL is not known. For example, SFC-450FT AGL.

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

Example: !JFK JFK RWY 12/30 CLSD

Example: !JFK JFK TWY A, A1 EDGE LGT U/S

Reason (when needed).

Remarks (when needed). Other information. This identifies other information considered important to the pilot.

Schedule (when needed).

A NOTAM may be originated for a scheduled condition/activity that will occur during the period. Specify the schedule between the condition/activity and the valid time string using the universal coordinated time (UTC). To ensure NOTAM system compatibility, the days of the week must be specified before the scheduled time. The term “DLY” (daily) indicates the event will occur each day at the same time during the stated time period. The start time of the schedule must correspond to the start of activity time. The end of the last schedule must correspond to the end of validity time. For example: DLY 1200-2000 YYMMDD1200- YYMMDD2000; MON WED 0900-1300 YYMMDD0900- YYMMDD1300, TUE THU 0900-2000 YYMMDD0900-YYMMDD2000.

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

Example: ! JFK JFK RWY 12/30 CLSD DLY 1400-0100

Example: ! JFK JFK RWY 12/30 CLSD MON WED FRI 1730-2130

Example: ! JFK JFK RWY 12/30 CLSD MON-FRI 0900-2359

Start of Activity/End of Validity.

This is a 10-digit date/time group (YYMMDDHHMM) used to indicate the time at which the NOTAM comes into force (the date/time a condition will exist or begin) and the time at which the NOTAM ceases to be in force and becomes invalid (the expected return to service, return to normal status time, or the time the activity will end). To ensure NOTAM system compatibility, these times must be separated by a hyphen “-”.

Example: ! JFK JFK RWY 12/30 CLSD YYMMDD2330- YYMMDD1300

When the NOTAM duration is certain, it should be reflected with a selfcancelling expiration time.

Example: ! JFK JFK RWY 12/30 CLSD YYMMDD2330- YYMMDD1300

When the NOTAM duration is citing a condition that is expected to return to service at an estimated period of time, it should reflect the estimated nature of the time with the suffix “EST”.

Note: Any NOTAM that includes an “EST” must be cancelled or replaced before the NOTAM reaches its End of Validity time. If the NOTAM is not cancelled or replaced, it will expire at the end of validity time regardless of EST.

Example: !JFK JFK RWY 12/30 CLSD YYMMDD2330- YYMMDD1300EST

When a NOTAM advertises a permanent condition that will be published in text, chart, or database, insert “PERM” as the expiration date in lieu of a 10-digit date-time group. The NOTAM originator is responsible for canceling the NOTAM and ensuring the NOTAM data gets published in the appropriate publication. See PERM NOTAM information in paragraph 2.3.13.

Example: !JFK JFK RWY 12/30 CLSD YYMMDD2330-PERM

NOTAMs will auto-expire at the end of validity unless PERM is indicated.

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.), issue separate NOTAMs for each facility.

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

If information is published elsewhere and is still valid, make references 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.

PERM NOTAMs Publication Process.

PERM NOTAMs are NOTAMs issued for airport facilities, features, or infrastructure alerting users of a permanent condition and that a NOTAM will be in effect until the information is published in an appropriate FAA publication(s) and/or chart(s).

When a NOTAM is originated for a permanent change to published aeronautical information, “PERM” must be inserted in lieu of a ten-figure date-time group end of validity time.

2.3.13.2.1 When issuing a PERM NOTAM, the originator must also submit the required information through the publication process.

2.3.13.2.2 The originator should enter a temporary NOTAM until they are able to confirm the initiation of the publication process.

Generally, PERM NOTAMs should not exceed a period of 90 days.

Obstacle NOTAMs should not be issued as PERM. To initiate the publication process of obstacles, contact the FAA Obstacle Data Team at [email protected].

Once PERM information is published or charted, the PERM NOTAM should be immediately cancelled.

A PERM NOTAM for wildlife hazards should not be issued if the information is already published in the remarks section of the Airport Master Record or Chart Supplement.

2.3.13.6.1 PERM NOTAMs for wildlife activity can be issued, if it is new permanent wildlife information.

2.3.13.6.2 Immediate action should be pursued to publish new information or activity in the appropriate FAA publication.

A flowchart diagram at Appendix D illustrates what tools can be used to complete the PERM NOTAM process and which tool is the preferred method for accepting certain airport information. Additionally, the following link can be accessed for addressing PERM NOTAMs: https://www.faa.gov/air_traffic/flight_info/aeronav/aero_data/Submitting_ Data/. Once the PERM NOTAM is issued, follow the process specified

below to publish the information in appropriate FAA charts or Chart Supplement:

2.3.13.7.1 Airport Data Information Portal (ADIP). NOTAM information dealing with airport 5010 data changes can be submitted through this application to receive Regional Airport Offices (Safety and Standards Branch) approval. Typically, the Regional Airport Offices (Safety and Standards Branch) concurrence on the airport name change is needed before submitting the name change through ADIP. In addition, declared distances, wildlife, and any other 5010 data changes should be submitted through ADIP.

2.3.13.7.2 Aeronautical Information Portal (AIP). The remainder of PERM NOTAM changes can be submitted by the airport operator or Regional Airport Offices (Safety and Standards Branch) to the AIP as either a chart or data change. If it is not a 5010 data change, then AIP should be used. The following website provides access to AIP: https://nfdc.faa.gov/nfdcApps/.

2.3.13.7.3 Aeronautical Chart Change (ACC). NOTAM for taxiway changes, closed, or any other information that impacts the airport diagram will be submitted to the ACC Portal.

2.3.13.7.4 Aeronautical Data Changes (ADC). NOTAMs for any other data changes that do not go through ADIP are sent through the ADC.

Table 2-1. NOTAM Keywords / Definitions

Keyword Definition

AD

(Aerodrome)

Used to describe a temporary change or hazard or potential hazard on or within 5 statute miles of an airport, heliport, or maneuvering area that is not associated with a specific movement area surface. Such hazards may include 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. Note: When using AD, ensure it is accompanied by the acronym for Airport (AP) if a complete aerodrome closure is implied.

APRON Used to describe a temporary change or hazard associated with an apron, ramp or taxi lane, lighting, markings, helipad, signage and other attributes associated with a specific apron.

COM

(Communications)

Used to describe a temporary change or hazard caused by communication outlet commissioning, decommissioning, outage, unavailability, and air-to-ground frequencies. Note: Airport operators may not have rights to submit NOTAMs using this keyword.

NAV

(Navigation Aids)

Used to describe a temporary change or hazard caused by changes in the status of ground-based radio navigational aids and Global Navigation Satellite Systems (GNSS) (except for area navigation (RNAV) approach anomalies). Note: Airport operators may not have rights to submit NOTAMs using this keyword.

OBST

(Obstructions, including obstruction lighting outages)

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.

RWY (Runway) 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. Identify runways with the prefix RWY followed by the magnetic bearing indicator, e.g., RWY 12/30, RWY 12, or RWY 30.

TWY (Taxiway) Used to describe a temporary change or hazard associated with a taxiway, taxiway lighting, markings, helipads, signage, and other attributes associated with a specific taxiway. Applies to single or multiple taxiways. Identify taxiways with the prefix TWY followed by the taxiway identifier letter or letter/number as assigned, e.g., TWY C, B3 CLSD, TWY PARL TWY ADJ RWY 09/27 CLSD.

SVC

(Services)

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.

NOTAM examples and translations. The paragraphs below provide some examples for various categories and plain text translations illustrating the structure of certain keyword NOTAMs. NOTAMs will not always contain all of the NOTAM composition elements.

Runway.

…RWY 09/27 CLSD TO ACFT MORE THAN 12500LB YYMMDD1300- YYMMDD2000

Translation: Runways 09 and 27 are closed to all aircraft weighing more than 12,500 pounds during the time period specified.

…RWY 13/31 CHANGED TO RWY 14/32 YYMMDD1200-PERM

Translation: Runway designation 13/31 now permanently changed to 14/32.

…RWY 16/34 CLSD TO ACFT WINGSPAN MORE THAN 70FT AND TO ACFT TAIL HEIGHT MORE THAN 49FT YYMMDD1300−YYMMDD2000

Translation: Runways 16 and 34 are closed to aircraft with a wingspan more than 70 feet and is also closed to aircraft with a tail height more than 49 feet during the specified time period.

Taxiway.

…TWY A3, A4, A5 EDGE LGT U/S YYMMDD1800-YYMMDD2200

Translation: Taxiway(s) A3, A4, and A5 taxiway edge lights are out of service during the specified time period.

…TWY ALL CLSD YYMMDD1800-YYMMDD2200

Translation: All taxiway(s) are closed during the time period specified.

…TWY A WIP ELECTRICAL LINE TRENCHING YYMMDD0800- YYMMDD1400

Translation: Taxiway A has work in progress for electrical line trenching for a specific time period.

Aprons/Holding Bay.

… APRON NORTH APN E 50FT CLSD YYMMDD2150-YYMMDD0700

Translation: The east 50 feet of the north apron is closed during the specified time period.

Chapter 2. NOTAM Process › 2.4 NOTAM Submission.

…APRON SOUTH CARGO APN CLSD YYMMDD1300-YYMMDD1300EST

Translation: South cargo apron is closed during the specified time period with an estimated return to service time.

Spots, Gates, Hardstands, Etc.

Can be used as geographical reference points to delineate a section on aprons or taxiways, but do not meet NOTAM criteria as its own individual “attribute”.

…APRON SOUTH TERMINAL RAMP APN BTN GATE 3 AND SPOT 4 CLSD YYMMDD1300 – YYMMDD1300EST

Translation: South terminal ramp apron is closed during the specified times between gate 3 and spot 4 with an estimated return to service time.

…APRON EAST TERMINAL RAMP APN BTN SPOT 23 AND HARDSTAND 4 CLSD YYMMDD0900 – YYMMDD2300

Translation: East terminal ramp apron is closed during the specified times between spot 23 and hardstand 4.

Aerodrome. …AD AP CLSD YYMMDD2330-PERM (Note: See paragraph 2.3.13 for the PERM NOTAM process before issuing a PERM NOTAM.)

Translation: Airport is now permanently closed.

…AD AP CLSD EXC 2HR PPR MON-FRI YYMMDD1000-YYMMDD1200

Translation: Airport closed except for two hours prior permission required for days of week and timeframe given.

Services.

…SVC ATIS NOT AVBL YYMMDD1600-YYMMDD1800

Translation: ATIS is not available for an established time period.

…SVC TWR CLSD YYMMDD2100-YYMMDD2300

Translation: Airport tower is closed for an established time period.

NOTAM Submission. Airport operators should use NOTAM Manager as the preferred and most effective method for entering NOTAMs into the system. See paragraph 3.1.2. NOTAM Manager uses dropdown menus, which standardizes entry and improves consistency. It

Chapter 2. NOTAM Process › 2.6 NOTAM Management.

also reduces or eliminates time-consuming free form NOTAMs that need human intervention and interpretation before issuing.

Connecting to NOTAM Manager.

Contact the National Airspace System Integration Support Contract (NISC) NOTAM Manager Deployment Team at 816-329-2550.

Register online at https://notams.aim.faa.gov/scert and a member of the NISC NOTAM Manager Deployment Team will contact you once your registration is received.

Using Other Methods to Issue NOTAMs.

Contact the appropriate Air Traffic facility for your airport if you encounter difficulty in contacting the FSS identified in the Chart Supplement.

FSS facility managers are required to ensure that lists of airport employees authorized to issue NOTAMs are available and kept current. To avoid delays in NOTAM dissemination, you must keep your airport’s list of authorized personnel up-to-date as changes occur, but not less than once annually.

Verification Information.

When issuing a NOTAM via the FSS, provide the name, position, title (if appropriate), address, and telephone number of a responsible airport official who the FSS should contact if confirmation of the NOTAM information is required. If you call in your NOTAM, you should ask for the operating initials of the FSS specialist who receives your call and the number assigned to the NOTAM. Allow sufficient time for the FSS specialist to format and input the NOTAM into the NOTAM system. Call the FSS back to get the current NOTAM and NOTAM number. Each specialist is officially identified in the facility by operating initials. Knowing the initials and NOTAM number will make follow-up or other reference easier.

Airport personnel can review their NOTAMs on the FAA website at https://notams.aim.faa.gov/notamSearch/

NOTAM Management. Consistent with the requirement to disseminate airport condition information to air carriers in 14 CFR § 139.339, airport operators are responsible for issuing NOTAMs as well as updating NOTAMs when the underlying condition has changed, or promptly cancelling NOTAMs that are no longer applicable to airport conditions.

Page Intentionally Blank

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.2 Reporting Conditions.

Chapter 3. Airport Condition NOTAMs and Reporting Process

Reporting Tools.

The airport operator is responsible for using all available methods, tools, and procedures to ensure timely and accurate information is being provided about airport conditions. See 14 CFR § 139.339. The airport operators should utilize the FNS as the primary method for collection and dissemination of airport information to aircraft operators and other airport users.

When disseminating airport condition information there are three methods available to airport operators. The first and preferred method is NOTAM Manager, a digital, directentry system. The second alternative method is the ENII system. The third method to issue a NOTAM is via telephone. This method is the least preferred due to the amount of time required to communicate airfield conditions to Flight Service, and the manual recording of notifications and disseminations in airport logs.

Note: If supplemental or secondary systems are used, the airport operator should ensure they are compatible and consistent. See 14 CFR § 139.339(b). Supplemental systems used for dissemination of NOTAM information are not recommended due to the potential to advertise outdated information which may be in conflict with current NOTAMs.

Reporting Conditions.

Use the term “DRY” to describe a surface that is neither wet nor contaminated. A FICON NOTAM should not be originated for the sole purpose of reporting a dry runway. See 14 CFR § 139.339(c)(3). A dry surface is reported when there is a need to report conditions on the remainder of the surface.

Use the term “WET” to describe a surface that is neither dry nor contaminated but has visible dampness, moisture, and/or water 1/8 inch (3mm) depth or less. Wet can also be reported as a stand-alone contaminant and in conjunction with other contaminants.

Use the word “REMAINDER” to provide additional information about the surface condition. For example, the runway surface conditions vary significantly according to the width, on one third of the runway, or a runway has been treated, resulting in differing field conditions on the untreated parts of the surface.

When assessing runway conditions, the airport operator should be aware that information reported will need to be divided into thirds, which represent the Touchdown, Midpoint, and Rollout portions of the runway. The conditions are reported based on the direction of the assessment, and typically correlates with the runway end in use.

The issuance of a Runway Condition Code (RwyCC) NOTAMs applies as follows:

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.3 Reportable Contaminants.

RwyCC NOTAMs are not allowed on a runway with an active closure NOTAM in effect. This prevents any confusion on whether the runway is open or not.

The issuance of multiple RwyCC NOTAMs for the same runway, e.g., one for each end, is also not permitted. This prevents confusion about which runway direction is available and what the conditions are on the surface for that particular landing runway.

RwyCCs can be read in reverse for situations permitting opposite direction landing.

Reportable Contaminants.

The listed contaminants are those recognized and used for reporting purposes. The application and order of precedence is illustrated on the Runway Condition Assessment Matrix (RCAM). When reporting a runway condition, a depth is mandatory, and only included, with those contaminants marked by an asterisk (*).

• Wet (water 1/8 inch depth or less)

• Water* (greater than 1/8 inch depth)

• 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

• Slush* over Ice

• Slippery When Wet

• Mud*

• Oil

• Sand

• Ash

A wet contaminant can have an impact on the performance of some aircraft; therefore, the FAA highly encourages airports to report “Wet” conditions (1/8 inch depth or less of water) when it is the only condition present on the runway. Equally important, the airport operator must be aware of its responsibility to monitor conditions during periods of heavy rainfall, which may cause depths to increase to greater than 1/8 inch of water (even on grooved runways). Airplane operators indicate this is critical information to report given the impact on airplane performance. Airport operators must report “Wet” conditions when associated with other winter contaminants in any particular third of the runway. See 14 CFR 139.339(c)(3). Additionally, when a runway has been treated with chemicals to mitigate a specific contaminant and the resulting surface is now “Wet”, this condition should be reported. The airport also has the option to report the chemical treatment within the same NOTAM.

Table 3-1. Reportable Contaminant Definitions

Term Definition

Contaminant

A deposit (such as frost, any snow, slush, ice, or water,) on an aerodrome pavement where the effects could be detrimental to the friction characteristics of the pavement surface.

Contaminated runway

For purposes of condition reporting and airplane performance, a runway is considered contaminated when more than 25 percent of the runway surface area (within the reported length and the width being used) is covered by frost, ice, and any depth of snow, slush, or water. Note: While ash, sand, oil, and rubber (see “Slippery When Wet” definition) are reportable contaminants, there is no associated airplane performance data available, and a depth would not be reported.

Ash

A grayish white to black soft solid residue of combustion normally originating from pulverized particulate matter ejected by volcanic eruption.

Compacted snow

Snow that has been compressed and consolidated into a solid form that resists further compression such that an airplane will remain on its surface without displacing any of it. If a chunk of compressed snow can be picked up by hand, it will hold together or can be broken into smaller chunks rather than falling away as individual snow particles.

Dry runway

A runway is dry when it is neither wet, nor contaminated. For purposes of condition reporting and airplane performance, a runway can be considered dry when no more than 25 percent of the runway surface area (within the reported length and the width being used) is covered by visible moisture or dampness, frost, slush, snow (any type), or ice.

Term Definition

Dry snow

Snow that has insufficient free water to cause it to stick together. This generally occurs at temperatures well below 32 degrees F (0 degrees C). If when making a snowball, it falls apart, the snow is considered dry.

Frost

Frost consists of ice crystals formed from airborne moisture that condenses on a surface whose temperature is below freezing. Frost differs from ice in that the frost crystals grow independently and therefore have a more granular texture.

Ice The solid form of frozen water.

Layered contaminant

A combination of the definitions for each of the contaminants. For example, the definition of “Wet Snow over Ice” is “Snow that has grains coated with liquid water, which bonds the mass together, but that has no excess water in the pore space” over “the solid form of frozen water.”

Mud Wet, sticky, soft earth material.

Oil A viscous liquid derived from petroleum or synthetic material, especially for use as a fuel or lubricant.

Rubber A tough elastic polymeric substance made from the latex of a tropical plant or from synthetic material.

Sand A sedimentary material, finer than a granule and coarser than silt.

Slippery when wet A wet runway where the surface friction characteristics would indicate diminished braking action as compared to a normal wet runway.

Slush

Snow that has water content exceeding a freely drained condition such that it takes on fluid properties (e.g., flowing and splashing). Water will drain from slush when a handful is picked up. This type of water-saturated snow will be displaced with a splatter by a heel and toe slap-down motion against the ground.

Slush Over Ice

Snow that has water content exceeding a freely drained condition such that it takes on fluid properties (e.g., flowing and splashing) over the solid form of frozen water.

Water Water in a liquid state. For purposes of condition reporting and airplane performance, water is greater than 1/8 inch (3 mm) in depth.

Wet ice Ice that is melting or ice with any depth of water on top.

Wet runway

A runway is wet when it is neither dry, nor contaminated. For purposes of condition reporting and airplane performance, a runway can be considered wet when more than 25 percent of the runway surface area (within the reported length and the width being used) is covered by any visible dampness or water that is 1/8 inch (3 mm) or less in depth.

Wet snow

Snow that has grains coated with liquid water, which bonds the mass together, but that has no excess water in the pore space. A wellcompacted, solid snowball can be made, but water will not squeeze out.

Reportable Depths. Specify the estimated contaminant depth in inches and feet.

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.5 Reporting Runway Percentage.

Table 3-2. Reportable Depth Measurements

Use Value To Report

1/8IN 1/8 inch or less

1/4IN > 1/8 inch to and including 1/4 inch

1/2IN > 1/4 inch to and including 1/2 inch

3/4IN > 1/2 inch to and including 3/4 inch

1IN > 3/4 inch to and including 1 inch

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. Round depths greater than 1 inch to the next higher reportable depth.

Report the highest depth of the contaminant along the reported portion of the surface.

The runway contaminants for which depth is mandatory when reporting runway surface conditions are specified in paragraph 3.3. The contaminant depth should also be reported for taxiway and apron/ramp conditions using the same reference paragraph.

Reporting Runway Percentage. Percent coverage (PRCT) is used to represent an approximate coverage on a runway. It is used in conjunction with contaminant type and depth. Percent coverage also plays a major role in the application of the RCAM and the calculation of RwyCCs. As indicated by the range of percentages, it should be noted that the reported percent value is not intended to be an exact measurement. The value reported, should be a conservative estimate.

Note: Percentages only apply to runways, not any other surface.

Table 3-3. Reporting Runway Percentage

Percent Range Percent Reportable

10% or less 10%

11% to 20% 20%

21% to 25% 25%

26% to 30% 30%

31% to 40% 40%

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.6 Runway Condition Assessment Matrix (RCAM).

Percent Range Percent Reportable

41% to 50% 50%

51% to 60% 60%

61% to 70% 70%

71% to 75% 75%

76% to 80% 80%

81% to 90% 90%

91% to 100% 100%

Runway Condition Assessment Matrix (RCAM). Upon completing an assessment of a runway surface, the next step is determining how the RCAM applies. The threshold for determining RwyCC applicability is 25%. The airport operator must first determine whether the overall runway length and width is contaminated greater than 25%. If the contaminant noted is greater than 25%, RwyCCs will be applicable. If 25% or less of the runway is contaminated, then a RwyCC will not be generated.

Using the Runway Condition Assessment Matrix (RCAM). The RCAM is the method an airport operator uses to assess and report conditions on a runway surface when contaminants are present. Use of the RCAM is only applicable to paved runway surfaces. Once an assessment has been performed, the RCAM defines the format by which the airport operator reports and determines a Runway Condition Code “RwyCC” (when applicable). This function is automatically calculated in the FNS. Below are the basic steps for obtaining a RwyCC and some examples of how it will appear as a NOTAM. Consult AC 150/5200-30, Airport Field Condition Assessments and Winter Operations Safety, for current guidance for assessing and reporting airport surface conditions using the RCAM.

Determining Runway Condition Codes (RwyCC). Upon identifying that a runway is contaminated greater than 25%, use the RCAM (Appendix B) to determine the type of contaminant present. Upon selecting the appropriate type of contaminant, assign the corresponding RwyCCs based upon the RCAM and the following criteria. Once the RwyCCs have been assigned, the airport operator may elect to downgrade the assigned RwyCCs, based upon observations and judgment. Conversely, the airport operator may also upgrade RwyCCs in limited scenarios, when specific criteria are met, as detailed below.

Note: The bolded contaminants in some of the runway third diagrams below take precedence in determining the RwyCC for that third.

Single Contaminant Criteria.

1. If a runway third contains a single contaminant that is greater than 25%, the RwyCC for that third is based directly on the code associated with that contaminant.

Runway Third: Touchdown Midpoint Rollout

RwyCC:

04

5 5 5

22

Contaminant: 70% 1/8 inch Wet Snow

70% 1/8 inch Wet Snow

70% 1/8 inch Wet Snow

2. If a runway third contains a single contaminant that is less than or equal to 25%, the RwyCC for that third will be a RwyCC of “6”. This is due to the runway condition being primarily Dry (or greater than 25%).

Runway Third: Touchdown Midpoint Rollout

RwyCC:

04

6 6 6

22

Contaminant: 20% 1/8 inch Wet Snow

20% 1/8 inch Wet Snow

20% 1/8 inch Wet Snow

Multiple Contaminants Criteria.

1. When two contaminants are present in a runway third and the percent coverage for at least one of the contaminants is greater than 25%; the RwyCC for that third will be based on the contaminant with the lowest RCAM code that has a percent coverage greater than 25% in that third.

Runway Third: Touchdown Midpoint Rollout

RwyCC:

04

2 2 2

22

Contaminant:

20% 1/8 inch Wet Snow 30% 1/4 inch Slush

20% 1/8 inch Wet Snow 30% 1/4 inch Slush

20% 1/8 inch Wet Snow 30% 1/4 inch Slush

Total Coverage 50% Total Coverage 50% Total Coverage 50%

Runway Third: Touchdown Midpoint Rollout

RwyCC:

04

1 1 1

22

Contaminant: 30% Ice 60% 1/4 inch Slush 30% Ice 60% 1/4 inch Slush 30% Ice 60% 1/4 inch Slush

Total Coverage 90% Total Coverage 90% Total Coverage 90%

2. When two contaminants are present in a runway third and the percent coverage for each individual contaminant is less than or equal to 25%

(and the total coverage for that runway third is greater than 25%); the RwyCC for that third will be based on the contaminant with the higher percentage for that third.

Runway Third: Touchdown Midpoint Rollout

RwyCC:

04

2 2 2

22

Contaminant: 10% Ice 20% 1/4 inch Slush 10% Ice 20% 1/4 inch Slush 10% Ice 20% 1/4 inch Slush

Total Coverage 30% Total Coverage 30% Total Coverage 30%

3. When two contaminants are present in a runway third and the percent coverage for each individual contaminant is equal and the total coverage for that runway third is greater than 25%, the RwyCC for that third will be based on the contaminant with the lowest RCAM value (if the RCAM values are not equal).

Runway Third: Touchdown Midpoint Rollout

RwyCC:

04

1 1 1

22

Contaminant: 20% Ice 20% 1/4 inch Slush 20% Ice 20% 1/4 inch Slush 20% Ice 20% 1/4 inch Slush

Total Coverage 40% Total Coverage 40% Total Coverage 40%

4. When two contaminants are present in a runway third and the total percent coverage for that runway third is less than or equal to 25%, the RwyCC for that third will be a RwyCC of “6”. This is due to the runway condition being primarily Dry (or greater than 25%).

Runway Third: Touchdown Midpoint Rollout

RwyCC:

04

6 6 6

22

Contaminant: 10% Ice 10% 1/4 inch Slush 10% Ice 10% 1/4 inch Slush 10% Ice 10% 1/4 inch Slush

Total Coverage 20% Total Coverage 20% Total Coverage 20%

Downgrade of RwyCC. The airport operator may downgrade a RwyCC when Continuous Friction Measuring Devices (CFME)/deceleration devices, pilot reports, or other observations suggest conditions are worse than indicated by the contaminant present. The airport operator should exercise good judgment and, if warranted, report a lower RwyCC than the contamination type and depth would indicate when generating an initial RwyCC. The NOTAM system has prompts and built-in protocols that must be addressed before completing a downgrade action.

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.7 Examples of System Capabilities Associated Field Condition (FICON)…

Upgrade of RwyCC. Generally, the FAA does not recommend that the airport operator upgrade a RwyCC from what is defined by the RCAM. Given the friction variability of certain contaminants, there are circumstances when a RwyCC of “0” or “1” (Ice, Wet Ice, Slush over Ice, Water over Compacted Snow, or Dry/Wet Snow over Ice) may not be as slippery as the RwyCC generated by the RCAM. In these very specific circumstances, the airport operator may upgrade the RwyCC to no higher than a RwyCC of “3”. The NOTAM system has prompts and built-in protocols that must be satisfied before completing an upgrade action. Specific information for both the downgrade and upgrade instructions can be found in AC 150/5200-30, Airport Field Condition Assessments and Winter Operations Safety.

Note: When contaminants which are not listed in RCAM are reported individually, or combined with contaminants listed in the RCAM, a RwyCC should not be generated. This function is automatic within the NOTAM System. Additionally, this criteria will not be used for Nil pilot reported braking action reports.

Examples of System Capabilities Associated Field Condition (FICON) NOTAMs. In the examples of a FICON NOTAM shown below, the first example includes all elements for a particular surface. Subsequent examples for that surface begin with a keyword and end prior to the scheduled time, unless including that information is helpful for clarity. Any translation will follow the same guideline. The following examples illustrate the systems capability to report varying complexities associated with runway conditions.

Uniform Coverage for All Runway Thirds.

!ORD ORD RWY 04L FICON 5/5/5 50 PCT 1/8IN DRY SN OBSERVED AT YYMMDD1620. YYMMDD1625-YYMMDD1625

Translation: Chicago O’Hare airport assessment using the RCAM produced a RwyCC of 5/5/5 with uniform contaminant coverage of 50% 1/8 inch dry snow on all thirds of the runway. Since there is uniform coverage for all runway thirds, the NOTAM will illustrate just the 50% coverage, depth, and type to show uniform coverage and the valid times.

Runway Third: Touchdown Midpoint Rollout

RwyCC:

04L

5 5 5

22R

Contaminant: 50% 1/8 inch Dry Snow

50% 1/8 inch Dry Snow

50% 1/8 inch Dry Snow

A Single But Different Contaminant Exists In Each Runway Third.

!DEN DEN RWY 25 FICON 5/3/5 50 PCT WET, 50 PCT 1/8IN WET SN OVER COMPACTED SN, 50 PCT 1/8IN SLUSH OBS AT YYMMDD1655. YYMMDD1700- YYMMDD2000

Translation: Denver airport assessment using the RCAM produced a FICON of 5/3/5 with contaminants consisting of 50% Wet, 50% 1/8in Wet Snow over Compacted Snow, and 50% 1/8in Slush. The overall coverage is more than 25% of the entire length and width so a RwyCC was generated for each third based on contaminant types and depths. With the addition of valid times, this becomes the NOTAM sentence.

Runway Third: Touchdown Midpoint Rollout

RwyCC:

25

5 3 5

07

Contaminant: 50% Wet 50% 1/8 inch Wet Snow over Compacted Snow

50% 1/8 inch Slush

Two Different Contaminants in Each Runway Third.

!SLC SLC RWY 34L FICON 3/5/2 50 PCT WET AND 50 PCT 1/8IN WET SN OVER COMPACTED SN, 50 PCT WET AND 25 PCT 1/8IN WET SN OVER COMPACTED SN, 10 PCT 1/4IN SLUSH OVER ICE AND 75 PCT 1/4IN SLUSH OBS AT YYMMDD1855. YYMMDD1900-YYMMDD2200

Translation: Salt Lake City airport assessment using the RCAM produced a FICON of 3/5/2 with contaminants consisting of 50% Wet and 50% 1/8in Wet Snow over compacted Snow, 50% Wet and 25% 1/8in Wet Snow over compacted Snow, 10% 1/4 inch Slush over Ice and 75% 1/4 inch Slush. The overall coverage is more than 25% of the entire length and width so a RwyCC was generated for each third based on contaminant type and depth. With the addition of valid times, this becomes the NOTAM sentence.

Runway Third: Touchdown Midpoint Rollout

RwyCC:

34L

3 5 2

16R

Contaminant:

50% Wet 50% 1/8 inch Wet Snow over Compacted Snow

50% Wet 25% 1/8 inch Wet Snow over Compacted Snow

10% 1/4 inch Slush over Ice 75% 1/4 inch Slush

Total Coverage 100% Total Coverage 75% Total Coverage 85%

Runway FICON.

!LGA LGA RWY 13 FICON 3/3/3 100 PCT COMPACTED SN OBS AT YYMMDD0230. COND NOT MNT YYMMDD0300-YYMMDD1045.

Translation: LaGuardia airport Runway 13 is the landing runway and has a Runway Condition Code of “3” in all thirds and is 100% covered by compacted snow. The temperature is warmer than 5°F (-15°C). The field conditions are not monitored during a specified timeframe as illustrated.

Note 1: All FICON NOTAMs have “OBSERVED (OBS) AT” and effective/expiration times but not all have “COND NOT MONITORED” (MNT).

Note 2: The percentage of coverage described in each example falls within the ranges found in paragraph 3.5.

Runway Third: Touchdown Midpoint Rollout

RwyCC:

13

3 3 3

31

Contaminant: 100% Compacted Snow

100% Compacted Snow

100% Compacted Snow

…RWY 31 FICON 25 PCT COMPACTED SN...

Translation: Runway 31 is the landing runway and has 25% coverage of compacted snow. A RwyCC is not displayed because there is ≤25% total surface coverage by the contaminant.

Runway Third: Touchdown Midpoint Rollout

RwyCC:

31

6 6 6

13

Contaminant: 25% Compacted Snow

25% Compacted Snow

25% Compacted Snow

…RWY 29 FICON 4/4/4 50 PCT COMPACTED SN...

Translation: Runway 29, the landing runway, has a RwyCC of “4” in all thirds and is 50% covered by compacted snow. The temperature is warmer than 5°F (-15°C). The depth of the compacted snow is not reported.

…RWY 08 FICON 5/5/5 100 PCT 1/8IN WET SN...

Translation: Runway 08 is the landing runway, has a RwyCC of “5” in all thirds, and is 100% covered with 1/8 inch (3mm) depth or less of wet snow.

…RWY 28 FICON 3/3/3 100 PCT 2IN DRY SN OVER COMPACTED SN...

Translation: Runway 28 is the landing runway, has a RwyCC of “3” in all thirds, and is completely covered by 2 inches of dry snow over compacted snow. The depth of compacted snow is not reported.

…RWY 34 FICON 5/5/5 100 PCT WET PLOWED 100FT WID REMAINDER 4IN WET SN....

Translation: Runway 34 is the landing runway, has a RwyCC of “5” in all thirds, and is 150 feet wide. The center 100 feet has been plowed leaving the plowed surface completely wet. The remaining surface outside of the plowed area is covered by 4 inches of wet snow.

…RWY 01 FICON 4/4/3 25 PCT COMPACTED SN, 25 PCT COMPACTED SN, 100 PCT 2IN DRY SN SWEPT 75FT WID REMAINDER 4IN DRY SN...

Translation: Runway 01 is the landing runway and has a RwyCC of “4” in the first two thirds and “3” in the last third. The runway is 100 feet wide, and the center 75 feet has been swept. The temperature is 5°F (-15°C) or colder. The touchdown and midpoint of the runway have 25% coverage of compacted snow. The rollout portion of the runway is completely covered by 2 inches of dry snow. The remaining area of Runway 01 is completely covered by 4 inches of dry snow.

Runway Third: Touchdown Midpoint Rollout

Remainder: 4 Inches Dry Snow

RwyCC:

01

4 4 3

19

Contaminant: 25% Compacted Snow

25% Compacted Snow

100% 2 Inches Dry Snow

Remainder: 4 Inches Dry Snow

…RWY 16 FICON 4/4/4 100 PCT COMPACTED SN PLOWED 75FT WID REMAINDER 1/2IN DRY SN OVER COMPACTED SN...

Translation: Runway 16 is the landing runway, has a RwyCC of “4” in all thirds, is wider than 75 feet, and the center 75 feet has been plowed. The temperature is 5°F (-15°C) or colder. The plowed portion is 100% covered by compacted snow. The area that has not been plowed has 1/2 inch dry snow over compacted snow. The depth is not reported for compacted snow.

…RWY 16 FICON 3/3/3 100 PCT COMPACTED SN 8IN SNOWBANKS...

Translation: Runway 16 is the landing runway, has a RwyCC of “3” in all thirds, and has been completely plowed and swept. Therefore, the terms PLOWED or SWEPT are not used. The temperature is warmer than 5°F (-15°C). The runway is 100% covered with compacted snow and has 8 inch snowbanks.

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

Translation: Runway 33 is the landing runway, has a RwyCC of “4” in all thirds, and has been plowed 100 feet wide leaving 100% coverage of compacted snow on the runway. The temperature is 5°F (-15°C) or colder. The depth of the compacted snow is not reported, however 24 inch berms are also observed along the edges of the plowed area.

…RWY 01 FICON 1/2/2 90 PCT ICE, 100 PCT 1/2IN SLUSH, 100 PCT 1/2IN SLUSH...

Translation: Runway 01 is the landing runway, the RwyCC is “1” in the first third, and “2” in the middle and last thirds, and the touchdown is 90% covered with ice. The midpoint and rollout are 100% covered in 1/2 inch of slush.

Runway Third: Touchdown Midpoint Rollout

RwyCC:

01

1 2 2

19

Contaminant: 90% Ice 100% 1/2 inch Slush 100% 1/2 inch Slush

…RWY 10 FICON 2/2/2 100 PCT WATER...

Translation: Runway 10 is the landing runway, has a RwyCC of “2” in all thirds, and is 100% covered by water with greater than 1/8 inch (3mm) depth of water.

Note: It is important that airport operators maintain a heightened awareness of runway conditions during periods of heavy rainfall.

…RWY 36 FICON 1/1/1 100 PCT ICE SANDED...

Translation: Runway 36 is the landing runway, has a RwyCC of “1” in all thirds, is 100% covered by ice and has been treated full length and width with sand. The depth of ice is not reported.

…RWY 11 FICON 5/5/5 100 PCT 1/8IN DRY SN SANDED 80FT WID...

Translation: Runway 11 is wider than eighty feet, is the landing runway, has a RwyCC of “5” in all thirds, and is 100% covered with 1/8 inch (3mm) depth or less of dry snow and also has been treated with sand eighty feet wide.

…RWY 30 FICON 5/5/5 100 PCT WET DEICED LIQUID...

Translation: Runway 30 is the landing runway, has a RwyCC of “5” in all thirds, is 100% wet and has also been treated with a liquid deicing chemical.

Note: When reporting a runway treated by sanding or deicing, the entire published dimensions of the surface are assumed to be treated unless qualifying length/width information is also given. When reporting deicing, also report the material used as either solid or liquid, as this may have operational significance to the pilot.

Taxiway/Apron/Holding Bay FICON.

!LGA LGA TWY C, C1, C6, TWY D BTN RWY 13/31 AND TWY C FICON 1/2IN DRY SN OVER ICE OBS AT YYMMDD0230 YYMMDD0300- YYMMDD0430.

Translation: The specified LaGuardia taxiways have 1/2 inch of dry snow over ice.

Note: The depth of the contaminant on an apron/ramp/holding bay is not required when reporting the conditions of airports that are not certificated under Part 139 or not federally obligated.

…TWY ALL FICON DRY PLOWED 50FT WID REMAINDER 6IN DRY SN...

Translation: All taxiways are plowed 50 feet wide and are dry. The edges that have not been plowed have 6 inches of dry snow.

…TWY ALL FICON WET 18IN SNOWBANKS...

Translation: All of the taxiways are wet, with snowbanks reaching 18 inches in depth off the edge of the paved surface.

Note: When reporting snowbanks, indicate the depth and location of the snow bank. Use the terms “SNOWBANKS,” “BERMS,” or “WINDROWS”, each defined as a ridge of snow created by mechanical means, after the surface condition. Snowbanks are assumed to be at the edge of a movement surface or, when plow/sweeper is used, at the edge of the plowed/swept area.

…TWY ALL FICON FROST...

Translation: Frost is observed completely covering all taxiways.

…TWY ALL EXC TWY G FICON 1/4IN SLUSH...

Translation: All of the taxiways except taxiway G are completely covered by 1/4 inch of slush.

Note: The depth of the contaminant is not required when reporting the conditions of airports that are not certificated under Part 139 or not federally obligated.

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.8 Plowed and Swept Reporting.

…APRON FEDEX FEEDER RAMP FICON 2IN DRY SN...

Translation: The FedEx Feeder ramp is covered by 2 inches of dry snow.

…APRON FEDEX FEEDER RAMP FICON ICE...

Translation: The FedEx Feeder Ramp is covered with ice. The depth of ice is not reported.

Note: The depth of the contaminant on an apron/ramp is not required when reporting the conditions of airports that are not certificated under Part 139 or not federally obligated.

Plowed and Swept Reporting.

When reporting a portion of a runway as being plowed, give the width plowed in feet and the runway’s condition if not entirely cleared.

…RWY 16 FICON 3/3/3 100 PCT 1/4IN WET SN PLOWED 100FT WID 6 IN BERMS...

Translation: Runway 16 is the landing runway, has a RwyCC of “3” in all thirds, and has been plowed 100 feet wide leaving 100% coverage of 1/4 inch wet snow on the plowed portion of the runway. In addition, 6 inch berms are observed along the edges of the plowed area.

Runway Third: Touchdown Midpoint Rollout

Remainder: 6 Inch Snow Berms

RwyCC:

16

3 3 3

34

Contaminant: 100% 1/4 Inch Wet Snow

100% 1/4 Inch Wet Snow

100% 1/4 Inch Wet Snow

Remainder: 6 Inch Snow Berms

Use the term PLOWED in a NOTAM if a portion of the surface has been plowed.

If the whole surface has been plowed, PLOWED is not used although reporting the surface contaminant conditions will still be appropriate.

Use PLOWED/SWEPT when indicating that a portion of a surface is plowed or swept and has depth, coverage, and conditions different than the surrounding area. When known, specify and list the surrounding area as “Remainder” after the plowed information.

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.10 Slippery When Wet Runway Procedures.

Omit PLOWED /SWEPT when the entire runway, taxiway, ramp, or apron has been plowed. When just portions are PLOWED/SWEPT, report the portions that are PLOWED/SWEPT in terms of the number of feet impacted and report the remainder for the depth and contaminants type.

Miscellaneous FICON (Mud, Ash).

!LGA LGA RWY 01R FICON 50 PCT 2IN MUD, DRY, DRY. OBS AT YYMMDD0230. YYMMDD0300-YYMMDD0400.

Translation: LaGuardia airport Runway 01R is the landing runway and the touchdown portion of the runway is 50% covered with 2 inches of mud. The remaining midpoint and rollout portions of the runway are contaminant free.

Note: When mud or ash is listed as a contaminant, no RwyCC will be generated.

…RWY 01L FICON 100 PCT ASH...

Translation: Runway 01L is the landing runway and is 100% covered with ash.

Slippery When Wet Runway Procedures. For runways where a friction survey (conducted for pavement maintenance) failed to meet the minimum friction level classification specified in AC 150/5320-12, Measurement, Construction, and Maintenance of Skid Resistant Airport Pavement Surfaces, the airport operator must report, via the NOTAM system, a RwyCC of “3” for the entire runway (by thirds: 3/3/3), and follow it with the term “SLIPPERY WHEN WET” when the runway is Wet. A “Wet” runway should not be reported when a “SLIPPERY WHEN WET” NOTAM is in effect. This may cause confusion by unnecessarily advertising two sets of condition codes. “Slippery When Wet” is only reported when a pavement maintenance evaluation indicates the averaged Mu value on the wet pavement surface is below the Minimum Friction Level classification specified in AC 150/5320-12. Some contributing factors that can create this condition include rubber buildup, groove failures/wear, and pavement macro/micro textures.

Note: If airport operator judgment deems a downgrade is necessary, the downgrade must be made, such that all three runway thirds match (e.g., 3/3/3, 2/2/2, and 1/1/1). An airport may discontinue the use of this NOTAM when the runway minimum friction level classification has been met or exceeded. This is the only contaminant that is reported using both runway designators.

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.11 Braking Action (Taxiways, Aprons, and Holding Bays).

…RWY 01/19 FICON 3/3/3 SLIPPERY WHEN WET…

Translation: The touchdown portion of Runway 01/19 is covered by rubber. Although the rubber is only observed at the approach end of Runway 01, when rubber is on a runway surface, the entire surface is reported as slippery when wet.

…RWY 01/19 FICON 2/2/2 SLIPPERY WHEN WET…

Translation: The same runway has more than 1/8 inch of water present on the surface as a result of a heavy rate of rainfall and/or standing water.

Braking Action (Taxiways, Aprons, and Holding Bays). Airport operators may report vehicle braking action on taxiway(s), apron(s), and holding bay(s) as Good to Medium, Medium, Medium to Poor, and Poor. Braking action, when reported by the airport operator, refers to vehicle braking and can be applied as a report for surfaces other than the runway. Report the worst braking action encountered on a given taxiway, apron/ramp, or holding bay. When reporting braking actions, the type of vehicle making the report should not be provided to avoid any bias in reporting.

Note: Airport operators are advised not to correlate friction readings (Mu numbers) to Good, Good to Medium, Medium, Medium to Poor, Poor, or Nil runway surface conditions, since no consistent, usable correlation between Mu values and these terms has been shown to exist to the FAA’s satisfaction. It is important to note that while manufacturers of the approved friction measuring equipment may provide a table that correlates braking action to Mu values, these correlations are not supported by the FAA.

Taxiway FICON.

!DEN DEN TWY AA FICON BA MEDIUM OBS AT YYMMDD0230. YYMMDD0253-YYMMDD0400

Translation: Denver Taxiway AA vehicle braking action is Medium with an observed at time.

…TWY B FICON BA POOR…

Translation: Taxiway Bravo FICON vehicle braking action is reported as Poor.

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.13 “Conditions (COND) Not Monitored (MNT)” NOTAMs.

Apron FICON.

…APRON MAIN APN FICON BA POOR...

Translation: The main apron FICON has vehicle braking action of Poor.

Pilot Reported Braking Action (PIREP).

A PIREP can be an aircraft braking report and will typically provide other pilots with a degree/quality of observed braking. The braking action observed is dependent on the type of aircraft, aircraft weight, touchdown point, and other factors. Pilots will use the terms Good, Good to Medium, Medium, Medium to Poor, Poor, and Nil. A braking action report from a landing aircraft should be processed as a PIREP. However, when receiving a PIREP, the recipient should consider that PIREPs rarely apply to the full length of the runway and are limited to the specific sections of the runway surface in which wheel braking was applied. There is no correlation between PIREPs from different aircraft types. The airport operator may combine airport surface condition reports with PIREP information to assist in determining FICON.

Airport operators are encouraged to input any PIREP information received within 15 minutes of the assessment currently being reported in NOTAM Manager or E- NOTAM II. This information should be entered under the pilot reported braking action information menu. The pilot reported braking action can be selected from the dropdown menu and the type of aircraft from which the PIREP originated is typed into the text box. For example, the PIREP received by the airport operator was “Good to Medium by a Boeing-737 aircraft”. This information will not be reported via the NOTAM system and is simply being recorded in the NOTAM system to provide data for analysis to determine any necessary modification to the RCAM as it relates to contaminants and airplane performance.

The RCAM upgrade criteria does not apply to pilot reported braking action reports of Nil.

Note: A Nil pilot reported braking action, or Nil braking action assessment by the airport operator, indicates a potentially unsafe condition. An acceptable action is for the airport operator to promptly close the particular surface prior to the next flight operation (and NOTAM that closure) until the airport is satisfied that the Nil condition no longer exists. This is a requirement at certificated and federally-obligated airports.

“Conditions (COND) Not Monitored (MNT)” NOTAMs.

Airport operators should use “conditions not monitored” NOTAMs as a way to provide information to pilots related to the conditions not being monitored at the airport, perhaps due to operations hours or staffing. COND NOT MNT is appended to the last FICON NOTAM an airport would issue prior to ending snow and ice control operations.

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.14 “Surface (SFC) Conditions (COND) Not Reported (REP)” NOTAMs.

Airport operators should avoid using “airport unattended” NOTAMs as a substitute for “conditions not monitored” because this type of NOTAM sends the incorrect message that other services provided by the airport, e.g., ATC, ARFF, fuel, are not available or accessible when the conditions are not being monitored.

The “Conditions not monitored” NOTAM is the preferred airport condition reporting for airport operators to use to address movement areas or airfield surfaces. When the field conditions will not be monitored, follow the most recent observation with the words “COND NOT MNT” (date/time) (date/time).” The time parameters specified must fall within the effective expiration times. FICON NOTAMs are considered temporary, therefore the expiration time for FICON NOTAMs must not exceed 24 hours from the effective time, except when the reported contaminant is Ash, Mud, Oil, Rubber, or Sand.

Airport operators should issue the “conditions not monitored” NOTAM accompanied with the most recent observation.

Example: !LGA LGA RWY 13 FICON 1/1/1 100 PCT ICE OBS AT YYMMDD0230. COND NOT MNT YYMMDD0300-YYMMDD1045.

Translation: LaGuardia Runway 13 is the landing runway and is 100% covered by ice. The RwyCC is 1/1/1. The field conditions are not monitored during a specified timeframe.

The airport operator can submit for publication a note stating conditions are not monitored between the hours of “X” and “Y” in the Chart Supplement or their Airport Master Records and Reports (5010).

“Surface (SFC) Conditions (COND) Not Reported (REP)” NOTAMs. When it is determined that no surface condition reports will be taken for longer than a 24-hour period, issue a single NOTAM for the entire time-period. Use the phrase “SFC COND NOT REP”, as this differs from Conditions Not Monitored. The difference between SFC Conditions Not Reported and Conditions Not Monitored is that SFC Conditions Not Reported is an aerodrome (AD) NOTAM and is for an extended period of time. Conditions Not Monitored is a FICON NOTAM that is accompanied with the most recent observation. This is used to report brief periods of time when conditions will not be monitored. If the airport has published a set schedule when conditions are not monitored in the Airport Master Record, a “SFC Conditions Not Monitored” NOTAM is not necessary to reflect these same hours.

Example: !CWA CWA AD AP SFC COND NOT REP YYMMDD2200- YYMMDD0500

Translation: Central Wisconsin airport surface conditions are not being reported during a specified timeframe.

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.15 Runway Light Obscuration or Outages.

Runway Light Obscuration or Outages. The diagram below illustrates the elements for a NOTAM to address runway light obscuration or outages. The paragraphs below provide some examples and plain text translations. Not all NOTAMs will contain all of the NOTAM elements.

Figure 3-1. NOTAM Elements to Address Runway Light Obscuration or Outages

Runway Light Obscuration. When reporting runway light obscuration due to snow and ice, report just the lights that are completely obscured.

1. Do not report lights that are partially obscured.

2. Be specific about which lights are affected, such as Runway 09/27 W 2000 feet.

3. Do not report the reason for the obscuration.

!BTV BTV RWY 15/33 REDL OBSC YYMMDD1300-YYMMDD1400

Translation: Burlington airport Runway 15/33 has edge lights obscured with a self-cancelling expiration time.

Runway and Affiliated Light Outages.

Runway Centerline Lights (RCLL).

!ATL ATL RWY 08R/26L RCLL U/S YYMMDD2300- YYMMDD1200

Translation: Atlanta airport Runway 08R/26L center line lights are out of service with a self-cancelling expiration time.

Touchdown Zone Lights (RTZL).

Figure 3-1: picture of page 48Figure 3-1 · page 48
Picture of the page from the copy saved here

!ATL ATL RWY 08R RTZL U/S YYMMDD2300-YYMMDD1200

Translation: Atlanta Runway 08R touchdown zone lights are out of service with a self-cancelling expiration time.

Keyword

Feature, Service,

Facility, or

System

Descriptive comments about Feature, Facility,

Service, or System

Geographical relationship

of surface to relevant

intersection

Condition Other Comments

Runway Edge Lights (REDL).

!ATL ATL RWY 08R/26L REDL U/S YYMMDD2300- YYMMDD0400

Translation: Atlanta airport Runway 08R/26L edge lights are out of service with a self-cancelling expiration time.

Note: When commissioning runway edge light systems, indicate the exact type of system; for example, Low Intensity Runway Lights (LIRL), Medium Intensity Runway Lights (MIRL), High Intensity Runway Lights (HIRL), etc. Once commissioned and published, runway edge lights are then shown as EDGE LGT.

Runway Lead-In Lighting System (RLLS) formerly LDIN.

!DCA DCA RWY 19 RLLS U/S YYMMDD2300-YYMMDD1200

Translation: Washington Reagan airport Runway 19 runway lead-in lighting system is out of service with a self-cancelling expiration time.

Runway End Light (RENL) co-located with Threshold Lights

!IAD IAD RWY 01R RENL U/S YYMMDD2000-YYMMDD2130

Translation: Washington Dulles airport Runway 01R runway end light is out of service with a self-cancelling expiration time.

Aerodrome Total Power Failure.

!SPA SPA AD AP LGT U/S YYMMDD2300-YYMMDD1200

Translation: Spartanburg airport all aerodrome lights are out of service with a self-cancelling expiration time.

Note: See the use of the keyword “AD” for any total aerodrome light outage situation.

Pilot Controlled Lighting (PCL). These examples discuss controlling runway or approach lights.

!SBY SBY SVC PCL ALL U/S YYMMDD2300-YYMMDD1200

Translation: Salisbury airport pilot control lights are out of service with a self-cancelling expiration time.

…SVC PCL FREQ CHANGED TO 122.8 YYMMDD2300-PERM

Translation: Pilot control lights frequency has changed to 122.8 with an effective date that makes it a permanent change.

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.16 Other Reportable Conditions.

…SVC PCL RWY 18 VASI U/S YYMMDD2300-YYMMDD1200

Translation: Runway 18 pilot control Visual Approach Slope Indicator (VASI) is out of service with a self-cancelling expiration time.

Other Reportable Conditions.

The airport operator ensures that a NOTAM is submitted for conditions considered hazardous or potentially hazardous to the aircraft operator. Permanent changes in surface conditions should be coordinated for publication.

Some examples of other reportable conditions are as follows:

!TSG TSG RWY 12/30 NUMEROUS 3IN CRACKS YYMMDD0100- YYMMDD1700

Translation: Tanacross airport Runway 12/30 has numerous 3 inch cracks with a reported discovery date and a self-cancelling expiration time.

… AIRSPACE CONTROLLED BURN WI AN AREA DEFINED AS .5NM RADIUS OF FXE360001 SFC-1500FT YYMMDD2300-YYMMDD0100

Translation: Airport is executing a controlled burn on the airport causing dense smoke for a given time period.

Note: Some airport operators may not be authorized to submit airspace NOTAMs for controlled burns. Direct contact with FSS may be required to issue this type of NOTAM.

Signage.

!IAD IAD TWY U7 HLDG PSN SIGN FOR RWY 01L/19R NOT STD YYMMDD2300-YYMMDD1200

Translation: Dulles airport holding position sign on taxiway U7 for runway 01L/19R is not lighted for a date and period indicated and with a self-cancelling expiration time.

…SFC PAINTED HLDG PSN SIGN NOT STD YYMMDD1200- YYMMDD2300

Translation: Surface painted holding position signs are not standard for a specific date with a self-cancelling expiration time.

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.17 Runway Thresholds and Declared Distances.

Taxiway Lights.

!SHL SHL TWY K, L EDGE LGT U/S YYMMDD2300- YYMMDD1200

Translation: Sheldon airport taxiway(s) K & L edge lights are out of service beginning at a certain period with a self-cancelling expiration time.

…TWY C STOP BAR LGT FOR RWY 16R/34L U/S YYMMDD2300-YYMMDD1200

Translation: Taxiway C stop bar lights for Runway 16R/34L are out of service for a date and period indicated with a selfcancelling expiration time.

Runway Thresholds and Declared Distances. The diagram below illustrates the elements for a NOTAM to address runway thresholds and declared distances. The paragraphs below provide some examples and plain text translations illustrating the structure of these NOTAMs. Not all NOTAMs will contain all of the elements.

Figure 3-2. NOTAM Elements to Address Runway Thresholds and Declared

Distances

Figure 3-2: picture of page 51Figure 3-2 · page 51
Picture of the page from the copy saved here

A displaced threshold affects runway length available for aircraft landing over the displacement. Report threshold displacement as closure of a portion of the runway until the actual physical appearance is altered so the closed runway segment no longer looks like a landing area. Consult with the responsible FAA Flight Procedures office when displacing a threshold because the resulting displacement may result in IFPs to the runway being impacted.

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

“RWY” Designator “THR DISPLACED” Other Comments

“TORA_FT” “TODA_FT” “ASDA_FT” “LDA_FT”

”RWY” Designator “TORA_FT” “TODA_FT” “ASDA_FT” “LDA_FT”

“FT” Distance Displaced

second NOTAM is originated for the reciprocal runway with all declared distances if any value has changed. Coordinate with the appropriate FAA Airports Regional or District Office to have declared distances information published. See AC 150/5300-13, Airport Design, for guidance on the use of declared distances.

Permanent changes to the TORA, TODA, ASDA, and LDA should be issued as a PERM NOTAM and should not last for more than 90 days. When the change will be permanent, submit the new information to the appropriate Regional Offices (Safety and Standards Branch) through the ADIP. Maintain the PERM NOTAM until the new information is processed and published in the appropriate FAA publication or Chart Supplement. Once published, cancel the PERM NOTAM.

Note: Any temporary change to declared distance information should not be issued as a PERM NOTAM.

!MKC MKC RWY 19 THR DISPLACED 300FT MARKING NOT STD. DECLARED DIST: TORA 6827FT TODA 6827FT ASDA 6827FT LDA 6527FT. YYMMDD1500–YYMMDD1600

!MKC MKC RWY 01 DECLARED DIST: TORA 6827FT TODA 6827FT ASDA 6527FT LDA 6527FT YYMMDD1500 -YYMMDD1600

Translation: Kansas City airport Runway 19 threshold is displaced 300 feet, therefore the Runway 19 landing LDA is reduced by 300 feet. The LDA and ASDA for Runway 01 are also reduced by 300 feet. An established selfcancelling expiration time has been established.

… RWY 28R THR DISPLACED 1500FT. DECLARED DIST: TORA 13001FT TODA 13001FT ASDA 13001FT LDA 11501FT. YYMMDD0300– YYMMDD0600

… RWY 10L DECLARED DIST: TORA 13001FT TODA 13001FT ASDA 11501FT LDA 11501FT YYMMDD0300–YYMMDD0600

Translation: A temporary structure becomes a controlling obstacle to the approach of Runway 28R and departure of Runway 10L resulting in the Runway 28 threshold being displaced 1500 feet resulting in changes to declared distances for Runways 10L and 28R. An established self-cancelling expiration time has been established for each runway.

… RWY 05/23 NE 500FT CLSD. DECLARED DIST: RWY 05 TORA 7002FT TODA 7002FT ASDA 7002 FT LDA 7002 FT RWY 23 TORA 7002FT TODA 7002FT ASDA 7002 FT LDA 7002FT YYMMDD0300–YYMMDD2100

Translation: Construction on Runway 05 requires 500 feet to be closed to protect a construction area thus changing declared distances to Runways 05 and 23. An established self-cancelling expiration time has been established.

… RWY 09/27 W 500FT CLSD FOR TKOF. DECLARED DIST: RWY 09 TORA 8446FT TODA 8446FT ASDA 8446FT LDA 8446FT. RWY 27 TORA 8946FT TODA 8946FT ASDA 8246FT LDA 8246FT. YYMMDD0300–YYMMDD2100

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.18 On or Off Airport Obstructions and Obstruction Lights.

Translation: The west 500 feet of Runway 09 is closed. Aircraft will enter the runway and depart Runway 09 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 are to be included in the NOTAM. An established self-cancelling expiration time has been established.

In the event the published TORA, TODA, ASDA, and LDA need to be reported without referencing 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 correct any erroneous declared distances currently published.

!CLT CLT RWY 05/23 DECLARED DISTANCES: RWY 05 TORA 7502FT TODA 7502FT ASDA 7202FT LDA 7202FT. RWY 23 TORA 7502FT TODA 7502FT ASDA 7202FT LDA 7202FT. YYMMDD0300–PERM

Translation: Charlotte airport Runway 05 and Runway 23 have permanent changes to their runway distances.

… RWY 08/26 DECLARED DISTANCES: RWY 08 TORA 10000FT TODA 10500FT ASDA 10000FT LDA 10000FT. RWY 26 TORA 10000FT TODA 10000FT ASDA 10400FT LDA 11000FT. YYMMDD0300–PERM

Translation: A temporary or permanent situation at an airport with nonstandard Runway Safety Areas (RSAs) or Object Free Area (OFA) leads to defining declared distances.

… RWY 08/26 NOW 10000FT X 150FT DECLARED DIST: RWY 08 TORA 9000FT TODA 9500FT ASDA 9000FT LDA 9000FT. RWY 26 TORA 9000FT TODA 9000FT ASDA 9400FT LDA 10000FT. YYMMDD0300–PERM

Translation: A NOTAM is required to correct an error in the Chart Supplement until the next publication date.

On or Off Airport Obstructions and Obstruction Lights. The diagram below illustrates the elements for an obstruction NOTAM. The elements “OBST; Type of Obstruction; Antenna Structure Registration (ASR) Number/Aeronautical Study Number (ASN); Coordinates; and HEIGHT (MSL) are mandatory elements; all other elements are included as needed. The paragraphs below provide some examples and plain text translations illustrating the structure of certain NOTAMs. Not all NOTAMs will contain all of the elements.

Figure 3-3. NOTAM Elements for an Obstruction

Obstructions such as towers, cranes, stacks, wind turbines, non-FCC towers, and power lines should have ASN numbers. Any failure or malfunction which affects a top light or flashing obstruction light regardless of its position is a condition for a NOTAM.

Figure 3-3: picture of page 54Figure 3-3 · page 54
Picture of the page from the copy saved here

Specify the altitude MSL with the unit of measurement (FT), if known. Otherwise, state UNKNOWN. In parentheses, specify the height with the unit of measurement (FT) and reference datum (AGL). Height is identified as MSL (when known) and may be accompanied with an AGL height listed in parenthesis.

Cranes that are marked by a flag or when the boom is lowered during night hours, periods of low visibility, do not exceed any obstruction standards contained in Part 77, and removed beyond the runway or taxiway safety areas may not require a NOTAM. At Part 139 airports, cranes not in use and located beyond the Runway OFA should not be NOTAMed; provided they meet all the same criteria as cited above. Comply with the Airspace Determination requirements for NOTAMS for on-airport cranes and construction activity.

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

When reporting an obstruction or obstruction light(s) failure located within the airport boundaries, identify the outage per the following:

1. Height, MSL, and AGL if known.

2. Distance from the ARP (nautical miles (NM)).

3. Direction from the Airport Reference Point (ARP) (16-point compass: N; NNE; NE; ENE; E; ESE; SE; SSE; S; SSW; SW; WSW; W; WNW; NW; NNW).

4. Tower registration number or ASR number (if applicable). The tower registration number can be found at wireless2.fcc.gov/UlsApp/AsrSearch/asrRegistrationSearch.jsp.

A NOTAM should be issued for all obstruction light outages within a 5 statute miles (SM) (4.3 nautical miles) radius of an airport, or obstruction light outages outside a 5SM radius that exceed 200 feet AGL. When able, report outages to the limits of the Part 77 surfaces of the airport.

Type of Obstruction

Obstruction

Identifier Coordinates

Alternate

Location Description

Condition Other Comments Height “AGL” Altitude

“OBST”

!GSP GSP OBST TOWER LGT (ASR 1234567) 345313.12N0815744.34W (3NM SSW SPA) 1528FT (564FT AGL) U/S YYMMDD1200-YYMMDD1200

Translation: Greer airport is reporting a tower obstruction light at a specific lat/long and 3NM SSW of Spartanburg is out of service with a specific date and time for return to service.

… OBST TOWER LGT (ASR 1234567) 420651.07N0817546.27W (12NM N PWK) 1049FT (330FT AGL) U/S YYMMDD1600-YYMMDD1600

Translation: Airport reports an obstruction tower light at a specific lat/long and within 12NM of north of Chicago Executive with identified above ground level height is out of service for an established date and time.

When the obstacle is within 500 feet either side of the centerline of a charted helicopter route, describe the plain language location by using the bearing, distance, and aerodrome designator of the nearest public-use airport. When able, report outages to the limits of the Part 77 surfaces of the airport. An Aeronautical Study Number (ASN), if known, should be included in parentheses in the NOTAM. If the ASN is not known, use parentheses to indicate (ASN UNKNOWN) in the NOTAM. See examples below:

!RDU RDU OBST CRANE (ASN 1234567) 345140N0804506W (1.44NM SW RDU) 580FT (195FT AGL) NOT LGTD YYMMDD2300-YYMMDD2300

Translation: Raleigh/Durham airport reports a crane at identified lat/long with cardinal direction from the lat/long that delineates the height and the crane being unlighted for a given time period.

… OBST WIND TURBINE (ASN UNKNOWN) 452315N0701346W (18.4NM SW BGR) 2820FT (410FT AGL) NOT LGTD YYMMDD2330-YYMMDD2359

Translation: Airport reports a wind turbine within an identified lat/long with a given height above ground level and not lighted for a set time period. A selfcancelling expiration time has been established.

The ASR number should be obtained from the tower owner when the outage is called in and will be put in the text of the NOTAM. The ASR number may also be obtained from the FCC website at wireless2.fcc.gov/UlsApp/AsrSearch/asrRegistrationSearch.jsp.

Note: See AC 70/7460-1, Obstruction Lighting and Marking, for additional guidance about obstruction light failure notification requirements.

Persons or organizations with obstruction ownership responsibilities should report the improper functioning of any obstruction light or lights immediately by telephone to the nearest local FSS. Callers should be prepared to provide the tower registration number (ASR number) and the name of the nearest airport. Reporting the operating status of

Chapter 3. Airport Condition NOTAMs and Reporting Process › 3.19 Birds and Other Wildlife.

obstruction lights on communication towers is the responsibility of the communication tower operator (47 CFR § 17.48).

If there is a report of an obstruction light outage on a tower outside the airport, airport operators with the responsibility of initiating NOTAMs should:

First check for any existing Flight Safety NOTAMs via the FSS or at http://notams.aim.faa.gov/notamSearch/.

If NOTAMs are not found, contact and advise the tower operator about the outage.

If the tower operator is not known, look up the information on the Federal Communications Commission (FCC) website at wireless2.fcc.gov/UlsApp/AsrSearch/asrRegistrationSearch.jsp.

Birds and Other Wildlife. Birds and other wildlife activity NOTAMs should focus on chronic or persistent problems that are relatively short-lived or seasonal in nature. NOTAMs of this type are effective at providing timely alerts when migration (e.g., birds, caribou), and other seasonal nesting, breeding, or movement activity is contrary to or beyond the scope of published airport data in the Chart Supplement or 5010 Airport Master Records.

Information that should be published in the Chart Supplement or 5010 Airport Master Record includes locations and conditions for seasonal movements or migrations associated with specific geographic locations, altitudes, or predictable behaviors. For example, waterfowl, raptors, gulls, or caribou that migrate on or near an airport during a short period each spring and fall in a predictable pattern. Movement activity of some hazardous species significantly increases during the breeding season (e.g., deer in the fall and alligators in spring to early summer) which may escalate wildlife/aircraft strike risk on airports during those seasons. Similarly, nest locations of hazardous species (e.g., bald and golden eagles, heron rookeries) located on or near an airport should be identified in the publications cited above.

When the airport operator observes any unusual or abnormal activity different from what is already published in Chart Supplement or 5010 Airport Master Record, a NOTAM can be issued citing the change in wildlife activities or conditions. Additionally, NOTAMs can be issued to provide information concerning the presence of threatened or endangered species.

NOTAM language should be as specific as possible to describe the activity that is occurring. NOTAM information should be updated and or cancelled as soon as possible once the condition dissipates and should not duplicate any published information or be published for the duration of seasonal events. Some example NOTAMs language are as follows:

….AD AP INCREASED BIRD ACT NW SIDE YYMMDD1000 – YYMMDD1700

Translation: Bird activity has increased on the northwest side of the airport according to a self-cancelling expiration time.

….AD AP BIRD MIGRATION INPR YYMMDD0800 – YYMMDD2000DLY

Translation: Bird migration in progress daily according to specific times.

….AD AP WILDLIFE ACT INCREASED NORTH SIDE YYMMDD1200 – YYMMDD2359DLY

Translation: Wildlife activity increased daily on the north side of the airport according to specific times.

Issue a PERM NOTAM for bird/wildlife activities or conditions only when it is a new condition being established as a permanent activity for the airport. Wildlife NOTAMs are not issued as PERM, unless the publication process has been initiated. See paragraph 2.3.13 for the PERM NOTAM process.

Page Intentionally Blank

Chapter 4. Select NOTAM Requirements Criteria › 4.1 Work In Progress (WIP).

Chapter 4. Select NOTAM Requirements Criteria

Work In Progress (WIP). Use the WIP criteria for routine maintenance events such as mowing, snow removal operations, and various types of short-term infrastructure maintenance and repairs. A particular surface should be closed as defined in each airport’s Airport Certification Manual for work that goes beyond routine maintenance. The diagram below illustrates the elements for a WIP NOTAM. The paragraphs below include some examples and plain text translations that illustrate certain WIP NOTAMs. Not all NOTAMs will contain all of the elements. Note that WIP is only used when the work is occurring.

Figure 4-1. Work-in-Progress NOTAM Elements

Content of NOTAMs for WIP.

Any NOTAM associated with WIP on or adjacent to a runway, taxiway, or apron are to begin with one of the following keywords: RWY, TWY, APRON, or AD. Additionally, if the work is proceeding in a particular direction, that should be specified.

Figure 4-1: picture of page 59Figure 4-1 · page 59
Picture of the page from the copy saved here

The NOTAM text would include the surface name/designator, the specified name/designator of the surface on which the work is being conducted, and the surface segment description specified in feet or from a specific point to point.

Snow/Ice Removal. Any NOTAM associated with snow/ice removal operations on multiple runways are to be described as “WIP (reason);” for example, SNOW (SN) REMOVAL, ICE REMOVAL. (See paragraph 4.1.) Airport operators are to ensure this NOTAM remains active when actual snow and ice removal operations are taking place. An individual NOTAM for each runway impacted is issued as the WIP moves from one runway to the next. In order to ensure the safety and efficiency of this snow removal operation, all of the following conditions should be met before proceeding:

The ATCT is in operation during the valid period of each NOTAM. For non-towered airports, communication via a secondary control center or use

Keyword

Feature, Service,

Facility, or

System

Descriptive comments about Feature, Facility,

Service, or System

Condition Other Comments

of Common Traffic Advisory Frequency or other local communication means may be used during the valid period of each NOTAM.

Closure times for each runway have been agreed upon by the airport operator, overlying air traffic facility/ATCT or other local airport control centers during the valid period of each NOTAM.

Operations are based on the process described in the Airport Certification Manual, Snow and Ice Control Plan, or other agreement between the airport operator, FSS, overlying air traffic facility, ATCT, or other local airport control centers as applicable. Some examples of WIP NOTAMs are as follows:

…AD AP ALL SFC WIP SN REMOVAL YYMMDD0700- YYMMDD1500

Translation: All aerodrome surfaces have snow removal work in progress for time given.

Note: A NOTAM associated with snow/ice removal can be described as “Work in Progress (reason),” (for example, Snow Removal, Ice Removal). Airport operators must ensure this NOTAM remains active when actual snow and ice removal operations are taking place.

…RWY 01L/19R WIP RESURFACING YYMMDD0700- YYMMDD1500

Continue reading ↓ 120 of 135 passages shown