Wesley Alexander • May 21, 2026 • 8 min read

Tactical Summary

At AUVSI XPONENTIAL 2026 in Detroit, FAA and Department of War (DoW) officials publicly framed something most operators have been treating as separate problems as a single problem. Project ULTRA at Grand Forks and the DoW's Federal USS platform are not really counter-drone initiatives; they are airspace management initiatives where counter-UAS is one component alongside UTM, manned traffic, and on-airport UAS operations. The practical takeaway for commercial drone operators is that the next round of BVLOS, sensitive-site, and shielded-operations waivers will be evaluated against this new "system of systems" framing, not against the old isolated-approval model.

Situation Report

Two paired XPONENTIAL panel briefings, surfaced through Dronelife on May 14 and May 15, are the public artifact. Officials from the FAA UAS Integration Office, the Department of War, Grand Sky, the Northern Plains UAS Test Site, and Modern Technology Solutions described two converging programs:

The most quoted line, from Grand Sky's Christopher Hewlett, captures the shift: "We're not asking the drones to be different, we're asking them to be treated as aircraft." That sentence sounds like marketing. It is not. It is the regulatory thesis underneath the next wave of Part 108 implementation decisions, sensitive-site rulemaking, and counter-UAS authority expansion.

Why This Matters Beyond a Panel Discussion

The drone industry has been operating inside three roughly separate regulatory conversations:

  1. BVLOS rulemaking (Part 108, comment reopening, electronic conspicuity).
  2. Sensitive-site protection (Section 2209 NPRM, World Cup posture, critical infrastructure no-fly designations).
  3. Counter-UAS authority (DHS C-UAS purchasing tool, DETER, directed-energy field trials).

Project ULTRA and Federal USS are the merge commit. The FAA's Paul Strande explicitly framed the work as testing "how those systems impact other systems in the NAS," and the DoW's John Sawyer described the transition from manual coordination by email toward automated strategic deconfliction backed by operational intent sharing. That is the same vocabulary the FAA uses for UTM, which means counter-UAS detection and mitigation are being designed to live inside the same data plane as routine drone traffic management.

For operators, this convergence is not abstract. It changes how authorized flights become visible to ground-based detection systems, how friend-versus-foe classification works, and how quickly a legitimate BVLOS mission can prove it belongs in the airspace it is operating in.

Operational Analysis

The Friend-or-Foe Gap Is Now an Operator Problem

Trevor Woods of the Northern Plains UAS Test Site named the gap plainly: "There is a gap in knowing who's friendly and who isn't friendly." Counter-UAS detection has improved faster than operational intent sharing has. A modern radar or RF detection suite will see your aircraft. It will not necessarily know that your aircraft is authorized, scheduled, and routine.

The implication for any operator running BVLOS, shielded, or sensitive-site adjacent missions:

The "Double Integration Problem" Mirrors Civil Operators

Sawyer described military installations as facing a double integration problem: drones must integrate with manned aircraft, and the installation's airspace must integrate with surrounding civil airspace. Read that as an operator and the structure is familiar. Any commercial program flying near an airport, a refinery, a stadium, or a public-safety jurisdiction is running the same problem at a smaller scale.

The good news is that the architectural answer being developed for the DoW is the architectural answer civil operators will get to reuse. Centralized intent sharing, automated strategic deconfliction, and standardized UTM data exchange are not military-only constructs. The FAA's Jessica Brightman explicitly noted that military systems are using the same UTM standards being developed for civil operations. The bad news is that operators who have built their compliance posture around manual coordination, phone calls to airport managers, and PDF waivers are about to look obsolete to the procurement teams writing the next round of enterprise contracts.

Counter-UAS Authority Is Following the Architecture

DHS's recent C-UAS purchasing tool expansion ahead of the 2026 World Cup, covered in our DHS counter-drone procurement analysis, already pointed at a national posture where authorized detection and mitigation systems propagate across stadiums, ports, and federal sites. Federal USS is the connective tissue. Once that connective tissue exists, the policy fight over expanding 18 U.S.C. § 2510 authorities to state, local, and critical infrastructure operators gets a lot easier to win because the systems being authorized already exchange data with the FAA's NAS picture.

The operator-facing implication: assume detection coverage, assume intent-sharing requirements, and assume audit trails. The era where a Part 107 operator could fly a one-off mission near a sensitive site and quietly land without anyone noticing is over. Whether that becomes a compliance burden or a compliance moat depends on how early operators wire intent sharing and clean Remote ID into their standard operating procedures.

Regulatory Implications

Part 108 Reads Differently Through This Lens

Part 108's comment reopening put electronic conspicuity at the center of the debate. Project ULTRA and Federal USS explain why the FAA cares so much. Conspicuity is not just about aircraft seeing each other, it is about authorized aircraft being legible to a national counter-UAS and UTM data plane that did not exist when Part 107 was written. Operators planning Part 108 compliance roadmaps should treat electronic conspicuity, Remote ID hardening, and intent feed publishing as a single workstream, not three separate ones.

Waivers Will Be Scored Against Coordinated Operations

The FAA's Jim Reynolds noted that combining novel approvals at Project ULTRA "requires thinking about new pathways to get those approvals." Translation: the agency is building precedent for layered, multi-system approvals where the operator's autonomy stack, conspicuity posture, and integration with airspace partners all count toward the safety case. This is the same trajectory we flagged in the Sunflower Labs 1:6 waiver analysis. Petitioners who can show clean intent sharing, validated Remote ID, and documented coordination with surrounding stakeholders will see their waivers approved faster than operators with stronger flight records but weaker integration posture.

What To Do This Week

Bottom Line

Counter-UAS used to be a security conversation that happened in a different room from the BVLOS conversation. Project ULTRA and Federal USS just put them in the same room and started building shared infrastructure. Operators who treat Remote ID, intent sharing, and telemetry retention as core operating disciplines will benefit from that infrastructure. Operators who do not are going to find their waiver petitions, their procurement conversations, and their post-incident reviews getting harder for reasons they cannot quite locate.

The drones do not need to be different. The operators around them do.

Sources

Related Analysis