The notation "NA-operational" appearing on FAA instrument procedure plates — in this case the San Jose International (KSJC) Three Departure — carries a specific regulatory meaning that pilots operating under IFR must understand before filing or flying the procedure. "NA" universally stands for "Not Authorized," and when paired with the qualifier "operational," it signals that the procedure, or a specific segment or minimum thereof, is not authorized when a designated facility, service, or system is not in an operational state. The distinction matters: it is not a blanket prohibition on the procedure, but a conditional one that activates when a defined operational dependency fails or is unavailable.
In the context of departure procedures, "NA-operational" most commonly ties to the availability of a specific air traffic control facility, a NAVAID, or an ATC radar service that the procedure requires to be safely executed. For example, a SID may depend on radar vectors from TRACON, a functioning localizer, or a specific DME. If that supporting element goes offline — whether through a NOTAM, equipment outage, or facility closure — the procedure becomes not authorized for that operational period. Pilots who encounter this notation must cross-reference current NOTAMs and confirm the status of any referenced facility or service before accepting a clearance on that departure. Accepting a clearance without doing so creates a compliance gap and potentially a safety hazard, particularly in congested terminal airspace like the San Francisco Bay Area where KSJC operates.
The confusion this notation generates — evidenced by the Reddit thread — reflects a broader gap in pilot familiarity with the fine print embedded in Jeppesen and FAA/NACO chart legend systems. While most instrument-rated pilots learn generic "NA" annotations during initial training, the modifier forms such as "NA-operational," "NA at night," or "NA when control tower closed" are often encountered for the first time in the field. For Part 91 operators, the consequence is usually a missed detail during preflight planning. For Part 135 or 121 operators, it can constitute a regulatory violation if the operational condition exists and the procedure is flown anyway. Chief pilots and training departments at charter and corporate flight departments should ensure that procedure annotation literacy is explicitly covered in recurrent ground training, particularly as operators expand into unfamiliar airports.
The KSJC Three Departure example sits within a wider pattern of increasing complexity in FAA terminal procedure design, driven by airspace congestion, RNAV integration, and the transition away from ground-based NAVAID-dependent procedures. As more SIDs and STARs incorporate conditional language tied to ATC capability, radar availability, or RNAV equipment requirements, the operational annotation problem grows more acute. Operators flying across diverse airport environments — especially those using supplemental type certificates for RNAV approaches or conducting international operations with mixed chart sources — face an expanding surface area of conditional restrictions that demand more than a quick preflight glance at the plate header.