Part 3: The Architectural Discipline Not Being Applied to the Harder Cases

Three structural failures in air traffic management architecture — surface conflict detection gaps, rotorcraft route-conformance monitoring deficits, and the absence of any coordination infrastructure for eVTOL operations — are being decided by regulatory default while public and political attention remains focused almost exclusively on the FAA's Strategic Management of Airspace Routing Trajectories procurement. Writing for Leeham News & Analysis, ATC correspondent Vincent E. Bianco III argues that each of the three neglected questions carries consequences more operationally significant than the SMART debate, and each already has a documented body count or near-miss record attached to it. The article closes what is framed as a multi-part series on AI in ATC by identifying the institutional pathology not as the SMART procurement itself, but as the treatment of that single procurement as the totality of the AI-and-ATC policy conversation.

The surface conflict detection argument centers on the March 2026 collision at LaGuardia Airport, in which an Air Canada CRJ and an airport fire department truck made contact on the movement area. Airport Surface Detection Equipment, Model X — deployed system-wide following the 1991 USAir 1493 runway collision at Los Angeles International — could not generate a conflict alert because the fire department vehicles involved were not equipped with transponders readable by the system. The regulatory fix is architecturally straightforward: mandate ASDE-X-compatible transponders on every vehicle authorized to operate in the movement area. That mandate has not been issued. For crews operating at high-density airports, particularly at night or in low-visibility conditions during ground operations, the implication is direct: the safety net that controllers and crews implicitly rely upon has a documented and unaddressed gap involving the class of vehicles most likely to be on a runway during an emergency — emergency vehicles themselves.

The rotorcraft conformance monitoring gap is the most operationally alarming finding for airline crews operating in dense terminal airspace. The NTSB's final report on the January 2025 DCA mid-air collision between an American Airlines CRJ on final to Runway 33 and a U.S. Army helicopter operating above its assigned altitude documented more than 15,000 near-miss events between rotorcraft and commercial aircraft along the DCA helicopter route system between 2021 and 2024, with at least one TCAS resolution advisory per month going back to 2011. The corridor in question provided seventy-five feet of vertical separation from the final approach path. The FAA had received and not acted on an NTSB recommendation to require ADS-B In equipage for rotorcraft operating in Class B airspace prior to the collision. The architecture for closing the gap — mandatory ADS-B In, automated route-conformance monitoring integrated into controller workstations — was known and available. It was not deployed. For Part 121 and Part 135 operators flying approach corridors near Washington, New York, Los Angeles, and other metro areas with active helicopter route structures, the regulatory inaction documented here represents an ongoing, unmitigated exposure rather than a resolved historical event.

The third structural question — coordination infrastructure for the eVTOL middle layer — is the most consequential in terms of scale and timeline. Joby, Archer, BETA, and Wisk are scheduled to begin commercial operations this summer in airspace for which no traffic management infrastructure currently exists. The regulatory framework that will govern that airspace sits fragmented across multiple FAA offices and rulemaking processes, including the Office of Advanced Aviation Technologies, the Part 108 BVLOS rulemaking, the Part 146 Automated Data Service Provider framework, and the eVTOL Integration Pilot Program. The companies that will provide coordination services have not been selected. The authority, failure modes, and interaction protocols for a future coordination layer remain architecturally unresolved. For Part 91K and Part 135 operators whose routes transit urban terminal airspace — particularly those operating business jets and turboprops into downtown-adjacent airports in cities targeted for early eVTOL deployment — this is not a distant abstraction. It is an operational environment that will materialize without agreed coordination standards in place.

The broader pattern Bianco identifies has direct bearing on how flight departments and aviation operators should read FAA regulatory signals over the coming legislative cycle. When a high-profile procurement dominates agency and congressional bandwidth, it is historically common for operationally critical but lower-visibility rulemaking to stall. The three gaps documented here — undetectable surface vehicles, unmonitored rotorcraft conformance, and an unpopulated eVTOL coordination layer — share the characteristic of being technically solvable, architecturally understood, and politically unattended. Operators who rely on regulatory infrastructure as a backstop to crew vigilance and procedural compliance are operating with a smaller backstop than the installed-equipment baseline implies. The analysis reinforces an older principle in aviation risk management: the absence of an accident since the last failure is not evidence that the system corrected the failure mode, only that the geometry of the next event has not yet presented itself.