U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION

Includes: Change 1 effective February 11, 2010
and Change 2 effective October 20, 2011

Section 3. NAVAID NOTAMs

5-3-1. GENERAL

a. Originate NOTAMs concerning NAVAIDs for which your facility has monitor responsibility.

b. NAVAID NOTAMs will be prefaced with the keyword NAV following the Location Identifier.

EXAMPLE-
!DCA LDN NAV VOR UNMONITORED

5-3-2. REPORTING NAVAID MALFUNCTIONS

The person in charge of the watch shall report any known or reported malfunctions of a NAVAID to technical operations or appropriate personnel and coordinate issuance of a NOTAM.

5-3-3. UNPROGRAMMED EXTENDED SHUTDOWNS

Unprogrammed extended facility shutdowns or other unanticipated outages that are expected to last more than 30 days shall be promptly reported to NFDC by administrative message or FAX. When possible, the expected duration of the shutdown is to be included in the message.

NOTE-
Except for emergency shutdowns, technical operations personnel are expected to give at least 1-hour notice to the FSS.

5-3-4. NAVAID MAINTENANCE SHUTDOWNS

Information concerning maintenance shutdown of NAVAIDs that are a part of the NAS shall be handled as follows:

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

b. Emergency shutdown. When possible, at least 1-hour advance notice should be obtained so that appropriate dissemination may be made prior to shutdown.

c. Extended maintenance shutdown. Notify the NFDC sufficiently in advance to permit publication of the information prior to the shutdown date. When this is not possible, disseminate a NOTAM not more than 3 days before the shutdown.

5-3-5. UNMONITORED NAVAIDs

a. All VOR, VORTAC, and ILS equipment in the NAS have automatic monitoring and shutdown features in the event of malfunction. Unmonitored, as used in this order, means that the personnel responsible for monitoring the facility have lost aural and visual monitoring capabilities and cannot observe the status of the facility. It does not refer to the automatic monitoring feature.

b. When a navigational aid's operational status cannot be monitored at the controlling or monitoring facility, but all indications or reports are the facility is operating normally, issue a NOTAM placing the aid in an unmonitored status.

c. When issuing a NOTAM describing a facility as unmonitored, do not use the category of monitor, only the contraction UNMON.

EXAMPLE-
DCA LDN NAV VOR UNMONITORED

d. If the NAVAID is reported as being out of service, the unmonitored NOTAM must be canceled.

5-3-6. CATEGORY 2 AND 3 INSTRUMENT LANDING SYSTEM STATUS

a. Category 2 and/or 3 approaches are automatically cancelled or not authorized when a NOTAM has been issued for any fundamental component needed for the approaches. Those components are the glide slope (GP), localizer (LLZ), approach lighting system (ALS), and the runway edge lights (RWY LGTS).

b. Category 2 and/or 3 approaches may not be authorized due to the failure of additional equipment, such as the outer marker (OM), inner marker (IM), locator at the outer marker (LO), distance measuring equipment (DME), sequence flashing lights/runway alignment indicator lights (SFL/RAIL), touchdown zone lights (TDZL), runway centerline lights (RCLL), RVR touchdown (RVRT), RVR midpoint (RVRM), and RVR rollout (RVRR). The determination of impact to higher category ILS operations will be made by the Tech Ops Control Center specialist in accordance with the guidance contained in FAA Order 6750.24, and a separate NOTAM request for loss of ILS category will be made if the equipment failures warrant this action.

EXAMPLES-
ATL ATL NAV ILS RWY 8L CAT 2 NA

!ATL ATL NAV ILS RWY 8L CAT 3 NA

!ATL ATL NAV ILS RWY 8L CAT 2/3 NA WEF 1111251600�11251900

5-3-7. NOTAM (D) NAVAID

a. The flight service specialist is responsible for formatting the information correctly.

NOTE-
The examples used in this order are representative of the format discussed in this paragraph.

b. For guidance on NOTAM D composition, see paragraph 4-2-1, NOTAM Composition.

c. Disseminate commissioning, decommissioning, outages, or unmonitored status of NAVAIDs (more than 1 hour or 30 minutes for radar) that are part of the NAS as NOTAMs. NAVAID outage NOTAMs will remain active until the NAVAID is returned to service or decommissioned.

d. Restrictions to NAVAIDs are normally published by segment; for example, 020�5 degree radials. Do not carry more than one NOTAM describing the restrictions of a NAVAID. To correct a given segment, issue a completely new NOTAM for that segment. Add 揚LUS SEE (publication)� when other restrictions to the NAVAID are published. The absence of this statement from the NOTAM indicates that all other restrictions have been canceled.

EXAMPLES-
!SAV SAV NAV VOR UNUSBL 010-030 BYD 35 BLW 10000

!PNC PER NAV VOR UNUSBL 045-060 BYD 20 BLW 2000
!FMN FMN NAV VOR UNUSBL 090-180/270-360 BYD 25 BLW 5000

e. Instrument Landing Systems (ILS). Distinguish components of an ILS from nonprecision approach NAVAIDs by preceding the component with 揑LS� followed by 揜WY� and the runway number (including single ILS airports).

EXAMPLES-
!SHV SHV NAV ILS RWY 32 110.3 CMSN

!SUS SUS NAV SNOOP NDB/ILS RWY 8R LO OTS

!SHV SHV NAV ILS RWY 5 DCMSN

!DCA DCA NAV ILS RWY 18 LLZ OTS

!DTW DTW NAV ILS RWY 30 LLZ RTS

!CDR CDR NAV ILS RWY 2 FAN MKR OTS

!ANB EUF NAV ILS RWY 18 GP UNUSBL BLW 768

!ANB EUF NAV ILS RWY 36 GP UNUSBL CPD APCH BLW 1240

!TOL TOL NAV ILS RWY 25 CAT 1 UNUSBL DA TO TDZ

NOTE-
At airports that have LLZ approaches only, precede the outage with 揑LS.� Fan markers are NOTAM material as long as they are associated with an ILS approach.

f. Simplified directional facility (SDF).

EXAMPLE-
!BKW 107 NAV SDF RWY 4 OTS

g. Localizer type directional aid (LDA).

EXAMPLE-
!DCA DCA NAV LDA RWY 18 OTS

h. VOR/DME.

EXAMPLES-
!OJC OJC NAV VOR/DME 113.0/CH 77 CMSN

!OJC OJC NAV VOR/DME DCMSN

!OJC OJC NAV VOR OTS

!OJC OJC NAV DME OTS

i. VORTAC.

1. VORTAC (all components, VOR/DME/TACAN).

EXAMPLES-
!GSO GSO NAV VORTAC 116.2/CH 109 CMSN

!GSO GSO NAV VORTAC DCMSN

!OJC OJC NAV VORTAC OTS

2. VOR out of service (DME/TACAN operational).

EXAMPLE-
!GSO GSO NAV VOR OTS

3. DME out of service (VOR operational/TACAN out).

EXAMPLE-
!GSO GSO NAV TACAN OTS

NOTE-
When the DME portion of a VORTAC fails or is removed from service for maintenance, the TACAN automatically becomes inoperative.

4. TACAN azimuth out of service (VOR/DME operational).

EXAMPLE-
!GSO GSO NAV TACAN AZM OTS

5. VOT � out of service

EXAMPLE-
!SBY SBY NAV VOT OTS 1110242000�10250300

j. TVOR.

1. TVORs serving one airport, and not associated with airway structure, must have NOTAMs issued using the associated airport identifier as the affected facility.

EXAMPLE-
!ILN ILN NAV MXQ VOR OTS

2. TVORs serving more than one airport, or associated with airway structure, must have NOTAMs issued using the TVOR identifier as the affected facility.

EXAMPLE-
!DAY XUB NAV VOR OTS

k. NDB or NDB/LO as follows:

1. Terminal NDBs. Those NDBs located on or serving only that airport must have NOTAMs issued using the associated airport as the affected facility.

EXAMPLE-
!DCA DCA NAV GTN NDB OTS

2. If an NDB serves more than one airport, issue a NOTAM using the identifier of the NDB as the affected facility.

EXAMPLE-
!MIV PNJ NAV NDB OTS

NOTE-
1. PNJ serves TEB and CDW.

2. Except in Alaska, collocated NDB/LOs are assigned five-letter names. All other NDBs are assigned three-letter identifiers.

3. NDB/LO outages.

(a) NDB/LO serving one airport must be issued with the three-letter identifier of the airport as the affected location.

EXAMPLES-
!SBY SBY NAV COLBE NDB/ILS RWY 32 LO OTS WEF 1109241430�09241700

!SUS SUS NAV SNOOP NDB/ILS RWY 8R LO OTS

(b) NDB/LO serving more than one airport must be issued under the three-letter identifier of each airport that it serves. This procedure may require coordination with other facilities.

EXAMPLES-
!MCI MCI NAV HUGGY NDB/ILS RWY 9 LO OTS WEF 11010241300�10241700

!FLV FLV NAV HUGGY NDB OTS WEF 1111241300�11241700

NOTE-
In the above examples, Huggy NDB serves as a LO to runway 9 at Kansas City Intl (MCI) and issued by Columbia (COU), Missouri AFSS. It also serves Fort Leavenworth/Sherman AAF (FLV), Kansas, as an NDB and issued by Wichita (ICT), Kansas.

l. NAVAID identification change.

EXAMPLE-
!IND IND NAV VORTAC ID NOW VHP

NOTE-
When the NOTAM is cancelled, the FSS must notify the USNOF to have the old identifier deleted from the NOTAM tables.

m. Global Positioning System (GPS).

1. All GPS navigational aid outages will be reported directly to the USNOF by Air Force Space Command (AFSPACECOM) monitoring facility. The USNOF will issue NOTAMs under the accountability 揋PS� with an affected location of 揋PS.�

EXAMPLE-
!GPS GPS NAV PRN 16 OTS

NOTE-
Global position system pseudorandom noise (PRN) number 16 is out of service until further notice.

EXAMPLE-
!GPS GPS NAV PRN 16 OTS WEF 1109231600-1109242300

NOTE-
1. Global position system pseudorandom noise (PRN) number 16 is out of service from September twenty-third two thousand eleven at sixteen hundred until September twenty-fourth two thousand eleven at twenty-three hundred.

2. GPS outages will be issued internationally under the affected location of 揔NMH.�/i>