NOTAM Field D: The Daily Schedule Within the Validity Window

In the reading framework used here, field D is the schedule of activity within a NOTAM’s B-to-C validity window. Field B identifies the beginning of that window, and field C identifies its end. Field D answers a different question: when, within that larger interval, the described activity is scheduled to occur.

This distinction is useful for students learning to separate dates, times, location, and altitude information in a structured aeronautical notice. A NOTAM can cover several days without describing an activity that runs continuously throughout those days. Conversely, a reader should not infer a recurring schedule merely because the validity window spans multiple dates.

The discussion below treats field D as a data-reading exercise, not as operational guidance. The permitted sources provide aviation-weather and data-access context, but they do not establish NOTAM field-D semantics. The field distinction is therefore the premise of this exercise, not a claim attributed to those sources. For operational use, consult an authoritative NOTAM-specific source and the applicable instructions.

Separating the Schedule From Other NOTAM Fields

B and C: The Outer Time Window

Fields B and C define the overall period to examine. In the simplified model used here:

The start and end of the overall window are not automatically the start and end of each daily activity period. If a notice spans three days, its B and C values establish the outer date-and-time bounds; a separate schedule may describe shorter intervals inside those bounds.

Students should keep two questions distinct: “During what overall period is this notice framed?” and “When is the described activity scheduled inside that period?” Reading B or C as though either were the daily schedule collapses those questions into one.

D: The Schedule to Interpret

Field D is the part of this exercise that describes scheduled activity. A schedule may require the reader to consider dates, days, time ranges, or other stated conditions. Its practical meaning depends on the actual text and the applicable conventions; the letter D alone does not supply every detail.

A careful reading also distinguishes a scheduled interval from proof that an activity occurred. A schedule describes what the notice says about timing. It is not, by itself, an observation, a weather report, or a record of actual activity.

F and G: Vertical Limits, Not Hours

Fields F and G concern vertical limits where those fields are used. They are not a substitute for field D. Values expressed as a surface reference or an altitude should therefore be interpreted as vertical information, not as clock times.

The same discipline works in reverse: a time range in D does not establish an activity’s altitude. Time and vertical extent are separate dimensions, even when they describe the same activity.

The Q-Line: Classification and Context

The Q-line is also separate from the field-D schedule. It provides coded information used to classify or contextualize a notice; it should not be read as the daily activity hours.

A reader can use a Q-line to understand what kind of notice is being encountered, while still looking to the schedule and descriptive text for the relevant temporal information. The code and the schedule are not interchangeable.

A Student Workflow for Reading Field D

Step 1: Record the Overall Window

First, identify B and C and write down their dates and times without converting them into a daily schedule. Note any qualification attached to the end of the period rather than silently treating it as a confirmed activity time.

For this exercise, make the assumed time standard explicit. Aviation Weather Center guidance identifies UTC as the report-time standard in its PIREP information, but that is an aviation-weather example—not evidence that every notation in a NOTAM should be interpreted without checking the governing NOTAM conventions. [1]

Step 2: Extract D Separately

Copy the field-D expression on its own. Ask what the text actually states:

Do not fill gaps by assuming that every calendar day in the B-to-C window has the same activity hours. An apparent recurrence must be supported by the schedule as written and by the conventions applicable to it.

Step 3: Compare the Schedule With B and C

The next task is to compare the schedule against the overall window. In a simplified exercise, the relevant scheduled interval is the overlap between the stated schedule and the B-to-C window.

Consider this synthetic example, with all dates and times assumed to be UTC and with D explicitly stipulated to apply on each date:

B) June 1, 2026, 1000
C) June 3, 2026, 1100
D) Daily 0900–1200

Under those stated assumptions, the overlapping portions are:

Date Scheduled range Portion inside the B-to-C window
June 1 0900–1200 1000–1200
June 2 0900–1200 0900–1200
June 3 0900–1200 0900–1100

The example illustrates why the outer bounds and the schedule must be read together. B begins after the first scheduled period has started, and C ends before the final scheduled period is complete. These are arithmetic assumptions for the example, not a substitute for interpreting an actual notice.

Step 4: Read the Description and Limits

A schedule is not a complete account of a NOTAM. Read the descriptive text to determine what the stated times concern, and keep any location and vertical limits attached to that same activity. A time range without its subject can be misleading: it might describe a restriction, an availability condition, or another stated circumstance.

If the schedule crosses midnight, contains an unfamiliar abbreviation, or leaves the applicable dates unclear, preserve that uncertainty. Do not silently assign an overnight interval to a particular day or extend it beyond C. Check a NOTAM-specific authority before using the interpretation operationally.

Contrasting Reading Methods and Data Sources

Field-by-Field Reading Versus Whole-Notice Reading

A field-by-field method is useful for initial extraction: B and C establish the outer window, D supplies the schedule, and other fields provide separate kinds of context. Its weakness is that isolated fields can be misread if the descriptive text qualifies them.

Whole-notice reading addresses that weakness by reconnecting each extracted element to the activity described. Its weakness is the opposite: a reader may absorb the notice as prose and overlook that the overall validity window and daily schedule are different temporal objects. A disciplined approach uses both methods—separate the fields first, then reconcile them.

NOTAM Schedules Versus Aviation-Weather Products

Aviation-weather resources are valuable for learning data terminology and access methods, but their product documentation should not be treated as a substitute for a NOTAM decoding guide. The Aviation Weather Center’s general help material concerns aviation-weather products and terminology. [2] Its data API documentation and WIFS user guide describe access to aviation-weather and advisory information; they do not, on the evidence provided here, establish how to decode field D. [3][4]

VectorWX, an aviation-weather information services participant, is an example of the industry context in which readers may encounter aviation data alongside other products. The permitted sources do not substantiate a claim about how it presents or interprets NOTAM schedules.

The methodological point is source fit: a weather-data page can support a claim about the weather product it documents, but it cannot automatically support a rule about a different data format.

Long-Term Implications for Data Literacy

The distinction between a validity window and an activity schedule matters beyond a single exercise. Digital interfaces often place dates, times, codes, and limits close together. If those elements are flattened into one summary, a reader may lose the relationship between the outer period and the intervals inside it.

For students, the durable skill is to retain both structure and uncertainty. Record which field supplied each value, distinguish an observed time from a scheduled time, and identify assumptions made during conversion. If a schedule cannot be resolved from the notice and the applicable conventions, mark it unresolved rather than inventing a daily interval.

The same standard applies to automated interpretation: a computed interval is only as reliable as the schedule text, the date and time conventions, and any assumptions used to parse it. Field D should be read with B and C—not replaced by them—and interpreted alongside the rest of the notice.

References

  1. https://aviationweather.gov/help/data/
  2. https://aviationweather.gov/help/
  3. https://aviationweather.gov/data/api/
  4. https://aviationweather.gov/wifs/users_guide/