By Wesley Alexander • June 5, 2026 • 8 min read

While most of the BVLOS conversation is consumed by the Part 108 NPRM comment fight, a quieter story dropped this week that arguably tells operators more about what scalable beyond visual line of sight actually looks like in 2026. Northern Plains UAS Test Site, the FAA-designated test site administering North Dakota's statewide Vantis network, onboarded Frontier Precision as its second champion operator on May 28 and announced a new FAA BVLOS waiver that is fully aircraft-agnostic for any NDAA-compliant platform under 55 pounds across more than 5,000 square miles of managed airspace.

The headline number from NPUASTS Operations Manager Hunter Hegel is the one operators should sit with: approval timelines inside the Vantis volumes dropped from years to 23 business days. That is the BVLOS approval velocity Part 108 has been promising in the future, delivered in the present, in one state, for operators who plug into an existing surveillance and coordination backbone.

The lesson is not that everyone should move to North Dakota. It is that the architecture of BVLOS approval is shifting underneath the rule, and operators outside the Vantis footprint should be thinking now about how their own procurement, equipage, and compliance posture lines up with the model that is already winning approvals.

What the Vantis Waiver Actually Authorizes

Several things in this waiver are worth separating because the press coverage is blending them.

First, the waiver is aircraft-agnostic. That is the meaningful structural change. Traditional BVLOS waivers have been tied to a single make and model with a safety case built around that aircraft's specific failure modes, lost-link behavior, and flight envelope. Frontier Precision can now operate any NDAA-compliant system under 55 pounds within the four Vantis service volumes without going back to the FAA for a separate authorization tied to each new platform. That is a procurement-strategy change as much as a regulatory one.

Second, the waiver is scoped, not unlimited. The 5,000-plus square miles are the four established Vantis service volumes inside North Dakota, supported by ground-based radar, the FAA Federal Radar Enclave that NPUASTS activated earlier this year, and a Mission and Network Operations Center in Grand Forks running on Collins Aerospace, L3Harris, and Thales infrastructure. The 23-business-day approval timeline applies inside that footprint, where the surveillance, deconfliction, and coordination layer already exists. Outside the volumes, operators are back in the Part 107 waiver universe everyone is already familiar with.

Third, the waiver is for systems under 55 pounds today, with stated plans to onboard Group 3 VTOL aircraft up to 1,320 pounds and autonomous swarm operations for agriculture. The under-55-pound limit aligns with the existing Part 107 weight envelope, which is exactly the segment where most commercial operators already live and where the procurement decisions get made.

Why This Beats the Standard Single-Aircraft Waiver Path

For a multi-platform commercial operator, single-aircraft waivers are a slow tax. Every new airframe in the fleet, every sensor swap that changes the airworthiness picture, every supplier diversification move triggers a new safety case and a new submission. That tax compounds for operators who want to diversify away from concentration risk on a single manufacturer or to spec different aircraft for different missions.

The aircraft-agnostic structure pushes the safety case onto the airspace and the infrastructure rather than the airframe. The Vantis network handles strategic deconfliction, conformance monitoring, and the surveillance picture. The operator brings any NDAA-compliant platform that meets the network's interface and performance requirements. The result is a procurement environment where the operator can spec the right aircraft for the right mission, including swapping aircraft mid-program, without restarting the regulatory clock each time.

That is the operating model Part 108's certificate path is conceptually pointed at. Vantis is showing what it looks like in practice, in advance of the final rule, with the test-site authority as the regulatory wrapper.

The Procurement Read for Operators

If your fleet leans heavily on a single manufacturer, the policy environment of the next 18 months is going to keep punishing that concentration. NDAA compliance is the gating filter for any operator working with federal customers, public-safety programs, or state procurement programs like the recently passed North Dakota Senate Bill 2018, which funds replacement of noncompliant UAS platforms with NDAA-compliant alternatives. We walked through the broader Chinese-component compliance posture in our Oregon FCC ban cost analysis, and the direction of travel has not changed.

The Vantis waiver makes the case sharper. The aircraft-agnostic approval is only useful if your candidate aircraft list contains multiple NDAA-compliant platforms you have already vetted, trained on, and integrated into your maintenance and training programs. Operators who have done that work can take advantage of the new approval velocity. Operators who have not are going to find themselves shopping for aircraft after the approval lands, which defeats the point.

The practical procurement move this quarter: build the NDAA-compliant candidate list, get at least two platforms type-trained in your program, document the maintenance and training records for each, and make sure your safety case template can substitute aircraft without rewriting the entire document.

What It Means for Operators Outside North Dakota

Vantis is the lead, not the only example. The Project ULTRA federal UAS service supplier framework we covered in our Project ULTRA analysis is the structural cousin: surveillance and coordination infrastructure provided by an approved service provider, with the operator slotting into a defined performance envelope. Part 108 contemplates a similar architecture at national scale through approved BVLOS service providers handling strategic deconfliction and conformance monitoring.

The operators who are going to move fastest under that structure are the ones who already speak the language: documented C2 link performance, Remote ID broadcast reception data, conformance with strategic deconfliction interfaces, surveillance integration, and a safety management system that survives an outside operations inspector's audit. That is also the documentation stack we walked through in our FAA inspection masterclass, and the substantive overlap with Part 108 readiness is not a coincidence.

If you operate outside North Dakota and want to be ready when an infrastructure-backed BVLOS approval becomes available in your region, start now: document your C2 link performance under representative operating conditions, build a Remote ID broadcast reception map of your typical operating area, draft an SMS sized to a Category 4 or Category 5 operation under the Part 108 framework we covered in our Part 108 stadium and event analysis, and identify the regional test site or service provider you would plug into.

The 23-Business-Day Number, Honestly Read

The 23-business-day timeline is real and worth respecting, but it is not transferable to the rest of the country tomorrow. It depends on infrastructure North Dakota has spent years building, on a test site authority that is not available in every state, and on a federal radar enclave activation that no other state currently has. The operators getting 23-day approvals are not getting them because the FAA changed its mind about BVLOS. They are getting them because the surveillance and coordination work has already been done at the airspace level, so the residual safety case for each individual operator is small and well-defined.

Replicating that elsewhere requires the same upfront investment in surveillance, coordination, and FAA partnership. States and regional partnerships that want their operators to share in that approval velocity should be studying the Vantis model now, not in 2027. Operators in those states should be the ones asking the question, in writing, of their state aviation authorities and economic development offices.

The Working Operator's Read

The Vantis waiver is the clearest live example of what scalable BVLOS actually looks like in the United States right now. Aircraft-agnostic approval, infrastructure-backed safety case, sub-month approval velocity, and a clear path to heavier platforms and more complex operations.

For working operators, three moves make sense regardless of geography. Build the NDAA-compliant candidate fleet now so a future aircraft-agnostic approval can actually be used. Document the C2 link, Remote ID, and conformance data that any infrastructure-backed waiver or future Part 108 certificate will demand. And start asking, locally and regionally, when your state is going to build the infrastructure that makes 23-day approvals possible where you actually fly.

Part 108 is the rule that may eventually generalize this model. Vantis is the proof that the model works today. The operators who treat this announcement as a procurement and compliance signal rather than a regional curiosity are the ones who will be ready when the architecture comes to their airspace.

Sources

Building an NDAA-compliant fleet strategy, drafting a BVLOS safety case, or preparing to plug into an infrastructure-backed BVLOS network as it expands? UAVHQ's consulting practice works with commercial operators and public-safety programs on Part 108 readiness and BVLOS waiver strategy. Reach out through the contact page.