A NAVAID Outage NOTAM Identifies a Facility and Its Unserviceable Period
What the notice tells you
A NAVAID-outage NOTAM is a facility-status record, not a weather text. Its purpose is to identify an affected navigation aid, state its operational condition, and define when that condition applies. It does not report atmospheric conditions or forecast changes. Domestic NOTAM samples show navigation-aid conditions on their own lines, including “VOR U/S” and “DME U/S,” rather than inside a weather report. [1]
That distinction shapes how to read the notice. A METAR or TAF describes weather observations or expected weather. A NAVAID-outage NOTAM describes the status of a navigation facility. The practical question is therefore not “What are the conditions?” but “Which aid is affected, what part is unavailable, and does the outage overlap the time I may rely on it?”
Identify the aid before assessing impact
Start by locating the facility identifier and reading the text that names or describes the aid. The Chart Supplement lists Armel as a VOR/DME with the identifier AML. [2] This example illustrates why an airport name or nearby location alone is not enough to establish which facility a NOTAM concerns. Match the identifier and facility description to the aid shown in your charting or navigation references.
A frequency can also help confirm that you are looking at the intended aid when it is included in the notice or appears in the reference material. Do not assume, however, that a frequency by itself explains the scope of the outage. Read the full facility description and any text identifying an affected component or limitation.
The central reading sequence is simple: identify the facility, establish its stated condition, and then evaluate the validity period. This prevents a notice from being misread as a general airport or weather condition.
How to Read the Identity, Status, and Time Fields
Facility identity is more than a nearby airport name
A NAVAID may be associated with an airport without being identified simply by that airport’s name. The NOTAM’s facility identifier and description are the primary clues to the specific aid being reported. In the FAA example, AML corresponds to the Armel VOR/DME. [2] Use that identity to cross-check the charted facility rather than inferring that every aid serving a particular airport shares its name or status.
Some facilities combine more than one navigation function. When a notice names a VOR/DME or another combined facility, read for wording that narrows the condition to a particular component. Domestic samples list “VOR U/S” and “DME U/S” as separate conditions. [1] The operational meaning depends on those details: a notice about one component should not automatically be read as a statement that every function at the site is unavailable.
“U/S” states a condition, not every consequence
On those sample lines, U/S marks the named aid unserviceable. [1] It is a status description, not a complete explanation of how the condition affects a route, airway, or procedure. The rest of the text may specify whether the entire facility is affected or identify a particular component, area, or altitude limitation.
For a pilot, the distinction is practical. If a facility or function is marked unserviceable, do not rely on it during the stated period. But do not infer additional restrictions that the notice does not state. Determine whether the aid is required for the navigation method or procedure you plan to use, and consult the applicable chart or procedure information to understand the operational effect. Use the charted identifier to see whether this notice is about the aid you are reading. [2]
Decode the validity period as UTC
In a validity range, the first time group marks the start of the condition and the second marks its stated end. Treat both times as UTC and convert them before deciding whether the outage overlaps the period you would use the aid.
An end time should be read as the stated end of the notice, not as a promise that service will be restored at that exact moment. A recurring daily window can restrict when the condition applies, so read that schedule together with the start and end.
A useful check is to compare the entire period of intended reliance—not just the planned departure time—with the outage window. If the aid is expected to be used later in a flight, its status at that later time matters too. Verify the latest status before departure, since the notice’s stated period is the information available at the time of briefing.
Manual Reading and Structured Processing
What a careful manual review does
A manual review can be organized around three questions:
- Which aid? Match the NOTAM’s identifier and name to the charted facility. Use a frequency as a cross-check when available.
- What is unavailable? Read the status and the complete text for a component, area, altitude, or other stated limitation.
- When does it apply? Decode the UTC start and end groups, account for any daily schedule, and compare them with the period when you plan to use the aid.
This sequence is more reliable than scanning for “U/S” alone. The status flag may be easy to spot, but it does not establish facility identity or describe every operational consequence. The full notice supplies that context. [1][2]
What structured processing can add
A digital system can represent a notice’s facility identity, status, and time period as separate data elements rather than leaving them embedded only in a text string. That separation can help a user compare the notice with a planned route or time window. It does not remove the need to confirm that the system has matched the correct facility or interpreted the notice’s scope accurately. The source record and current facility information remain important checks.
VectorWX, at https://vectorwx.app, is a student-learning display for reading these fields side by side. A digital interface may make status and timing easier to review, but the existence of an interface does not by itself establish that a particular NOTAM has been parsed correctly. Confirm the aid’s identity, read the complete condition, and check the UTC validity period against the time you would use the aid. [3]
Why Precise Identity and Timing Matter
Outage notices describe operational availability
A NAVAID notice matters when a pilot intends to use that facility for navigation or as part of a procedure. Treat the stated unserviceable aid or component as unavailable during the applicable period, then determine whether the planned operation depends on it. A nearby airport name, an assumed shared function, or a status symbol in an interface is not a substitute for reading the notice’s actual identity and scope.
The absence of a notice in the set you are reading is not proof that the aid is available. Check the current notice for that identifier before treating the charted facility as usable.
The durable reading rule
As aeronautical information becomes easier to search and display in digital tools, the core task remains the same: keep facility identity, service condition, and validity time distinct. A NAVAID-outage NOTAM is not a weather product and should not be interpreted as one. It is a record about a named navigation facility and its unserviceable period. Confirm the identifier and description, read what is specifically affected, interpret the time window in UTC, and verify the latest status before relying on the aid.