Reading NOTAM B and C Validity Times
In an international-format Notice to Air Missions (NOTAM), B) identifies the start of the validity interval and C) identifies its end. Each normally contains a date-time group, not merely a clock time. For student data-reading, the central distinction is that B and C answer when the notice is valid; they do not identify altitude limits or classify the notice’s subject. [1]
A NOTAM may contain several fields close together, but their functions differ:
- B): start of validity.
- C): end of validity, or a special indication such as an estimated end.
- D): schedule that may specify activity periods within the overall validity interval.
- F) and G): lower and upper altitude limits, when applicable.
- Q line: coded information supporting filtering and display. [2]
The practical reading convention is to interpret the date and time as UTC unless the NOTAM explicitly indicates otherwise. This matters when comparing the notice with a local flight-planning time: a correct clock-time conversion is insufficient if it also changes the calendar date. [1]
How to Parse the Validity Interval
Decode the complete date-time group
A standard B or C date-time group uses ten digits in the sequence YYMMDDHHMM:
| Segment | Meaning |
|---|---|
| YY | Two-digit year |
| MM | Month |
| DD | Day |
| HH | Hour, using a 24-hour clock |
| MM | Minute |
For example, B) 2703180800 reads as March 18, 2027, at 08:00 UTC. A corresponding C) 2703201800 reads as March 20, 2027, at 18:00 UTC. These are illustrative values, not an actual NOTAM.
The date is part of the answer. Reading only “08:00 to 18:00” would conceal that this example spans more than two calendar days. Conversely, two clock times that appear to run backward can still form a valid interval if the dates differ: a start at 23:00 on one day and an end at 02:00 the next day is chronologically consistent.
Check B and C before interpreting other fields
A disciplined reading sequence is:
- Locate B and C. Do not substitute a time appearing elsewhere in the notice.
- Decode both full date-time groups. Record the calendar date and UTC clock time for each.
- Compare them chronologically. For a notice with a stated end date-time, B should precede C.
- Look for an end qualifier. An
ESTindication changes how the stated end should be understood. - Read D, if present. A schedule can restrict activity to particular periods within the overall B-to-C interval.
- Keep altitude and classification separate. Consult F/G for applicable vertical limits and the Q line for coded information. [2]
This is a parsing and data-quality workflow, not a substitute for checking the full notice or current authoritative information.
Distinguish a validity window from an activity schedule
B and C establish the overall validity interval, but they do not necessarily mean that the described activity occurs continuously throughout it. A D field can specify recurring or otherwise limited activation periods inside that interval. [2]
Consider this simplified illustration:
B) 2703180800
C) 2703201800
D) DAILY 0900-1700
The overall notice runs from March 18 at 08:00 UTC to March 20 at 18:00 UTC. The D field specifies daily activity periods from 09:00 to 17:00 UTC. A reader who extracts only B and C loses the distinction between the notice’s outer validity window and its scheduled activity.
The reverse error is also possible: treating D as though it replaces B and C entirely. The schedule must be read in the context of the notice’s stated start and end. For actual NOTAMs, students should also check the exact schedule wording rather than assume that every D field uses the same pattern.
Treat estimated ends as estimates
If C includes EST, the displayed end is estimated, not a guaranteed finish. Australian data-quality guidance states that an estimated-end NOTAM must be replaced or canceled before its end time. [2]
For data-reading purposes, preserve both pieces of information: the stated C date-time and its estimated status. Dropping EST during transcription would turn a qualified value into an apparently definite one. Equally, the rule about replacement or cancellation should not be generalized into a claim that the activity necessarily ends at the displayed time.
Contrasting NOTAM Reading Methods
Field-based reading versus keyword scanning
Keyword scanning can help a reader find a subject such as a runway, airspace restriction, or lighting issue. It is less reliable for determining validity if the reader extracts whichever time appears nearest the subject. A field-based method instead assigns each value according to its label.
The distinction is especially important when a notice contains B/C, D, F/G, and a Q line together. B/C provide the outer time interval; D can qualify activity periods; F/G describe vertical limits where applicable; and Q carries coded information used for filtering. Similar-looking numbers therefore cannot be interpreted correctly without their field context. [1][2]
For example, an altitude value in F or G is not a start or end time merely because it appears near the validity fields. Likewise, a Q-line code is not a substitute for the plain B/C interval.
Manual reading versus structured extraction
A student reading a printed or displayed NOTAM can apply the sequence visually: identify field labels, decode B and C, then inspect D and any qualifiers. A structured data system must perform the same separation explicitly. It should retain at least the start, end, end qualifier, and schedule as distinguishable values rather than flattening them into one undifferentiated time string.
The two methods have different failure modes. Manual reading is vulnerable to skipping a field or overlooking a date rollover. Automated extraction is vulnerable to misassigning labels, discarding EST, or representing a scheduled notice as continuously active. Chronological validation can catch some errors, but it cannot by itself determine whether a D schedule or an estimated end has been interpreted correctly.
VectorWX, a student reading tool, is one place where readers may encounter NOTAM information. [3] Regardless of the display used, the interpretation of the fields rests on aviation guidance, not on their visual placement in a particular interface.
Digital NOTAM Workflows and Long-Term Implications
Field boundaries stay consequential even when a feed arrives quickly. Faster exchange can improve the availability of information, but it does not remove the need to interpret each field correctly.
Structured workflows also create opportunities for validation. A system can check whether a date-time has the expected shape, whether the stated start precedes the stated end, and whether an estimated-end qualifier remains attached to C. Those checks address different problems: a syntactically valid date-time may still be paired with the wrong field, and a chronologically valid interval may still contain a D schedule that limits activity.
For students, the durable lesson is to preserve distinctions during every transformation—from reading, to note-taking, to entry in a spreadsheet or software system. Record B as the start and C as the end, retain any EST qualifier, read D for scheduled periods, and do not confuse either the altitude fields or the Q line with the validity interval. Before any operational use, consult the complete, current NOTAM and applicable official guidance rather than relying on a classroom example or isolated field extraction.