From the Department of Redundant NOTAMs Department

A contradictory NOTAM restricting Runway 4/22 to aircraft with wingspans of fewer than 50 feet — while simultaneously carving out an exception for aircraft whose wingspans are also less than 49 feet — has drawn attention for its circular and self-defeating logic. The notice, as written, appears to prohibit operations for aircraft exceeding 50 feet of wingspan, then redundantly re-restricts an already-excluded subset of aircraft (those between 49 and 50 feet), while doing nothing meaningful to clarify the actual operational intent. Whether the originating facility intended a different threshold, a different exception, or simply produced a data-entry error, the resulting NOTAM is operationally incoherent on its face.

The post's tongue-in-cheek reference to the Grumman S-2 Tracker's wing-fold capability is more than just humor — it illustrates a genuine interpretive problem with poorly drafted aeronautical information. The S-2 carries a wingspan of approximately 72 feet in the extended position, well above the stated restriction, but folds to roughly 27 feet for carrier deck operations. Under a hyper-literal reading of the NOTAM's contradictory language, one could theoretically construct an argument that a folding-wing aircraft in its stowed configuration satisfies any sub-49-foot restriction. In practice, no competent pilot or operator would pursue that interpretation, but the joke underscores a real hazard: when NOTAMs are ambiguous or internally inconsistent, pilots are left to make judgment calls about regulatory intent under time pressure, often without access to the originating authority.

NOTAM quality has been a persistent concern in aviation safety culture for decades. The FAA's NOTAM Improvement Program, launched in the early 2020s, and the broader international push under ICAO toward digital NOTAM (D-NOTAM) and the eventual migration to the SWIM (System Wide Information Management) framework reflect institutional acknowledgment that the legacy NOTAM system produces precisely this kind of noise — redundant, contradictory, or impenetrable entries that erode pilot trust and increase cognitive load during preflight planning. Studies and ASRS reports have consistently documented pilot fatigue from NOTAM overload as a contributing factor in runway incursions and airspace busts.

For professional and corporate flight crews operating under Part 91, 91K, or 135, the practical takeaway from a NOTAM like this is straightforward: when a restriction appears logically inconsistent, the conservative interpretation governs, and the originating ARTCC, ATCT, or airport operations office must be contacted for clarification prior to the operation. No regulatory or operational benefit exists in attempting to exploit ambiguous language, and doing so could expose operators to enforcement action if the intended restriction — however poorly stated — was clearly more conservative than the loophole suggests. Dispatchers and flight planners reviewing NOTAM packages for turbine and business jet operations bear equal responsibility for flagging these discrepancies before the crew ever reaches the flight deck.

The broader implication is that human error in NOTAM authorship remains an underappreciated systemic risk. The humor of the S-2 Tracker scenario distracts only slightly from the underlying reality: a runway restriction that cannot be unambiguously interpreted is not merely an administrative annoyance but a latent safety hazard, particularly at unfamiliar fields where pilots have no local knowledge to fill in the gaps. The aviation community's continued push for plain-language, machine-readable, and logically validated aeronautical information cannot arrive soon enough.