FAA BVLOS Rulemaking Has Moved Beyond The ARC: What Operators Should Track Now

There is an easy way to misread the BVLOS calendar. The FAA's UAS BVLOS Aviation Rulemaking Committee work still matters, but the public meeting around that final report was part of the 2022 process, not a new June 2026 event. The current issue for operators is what happened after that ARC work: the FAA and TSA's Part 108 proposal, the reopened comment record, and the operational details that could shape routine BVLOS approvals.

The FAA's own committee page lists the UAS BVLOS ARC Final Report as submitted on March 10, 2022. The official Federal Register public meeting notice for that report was also a 2022 notice. For a 2026 operator, the useful question is not whether to attend an old meeting. It is what the FAA has carried forward into the rulemaking record.

The ARC Report Is History, Not Today's Action Item

The ARC was important because it framed the operating cases that still dominate BVLOS policy: long-line infrastructure inspection, industrial aerial data gathering, small package delivery, and precision agriculture. Those categories map directly to commercial work that Aerosyne has covered before, including offshore wind inspection and precision agriculture spraying.

But operators should be careful with dates. Treating the ARC meeting as a current event would lead to the wrong action plan. The ARC report is now background material. The current operating question is how the proposed BVLOS framework would translate into aircraft eligibility, operator responsibilities, traffic deconfliction, and records that a commercial team can actually maintain.

The Center Of Gravity Is Part 108

On August 7, 2025, DOT published the FAA and TSA notice of proposed rulemaking, Normalizing Unmanned Aircraft Systems Beyond Visual Line of Sight Operations. The summary says the proposal would create performance-based rules for low-altitude BVLOS operations and for third-party services, including UAS Traffic Management.

That is why the ARC still matters, but only as the starting point. Aerosyne's earlier Part 108 overview covered the bigger shift from individual waivers toward a standardized BVLOS framework. The next layer for operators is more practical: what evidence, equipment assumptions, operating roles, and data records will be needed if the final rule follows the proposal's general direction.

Electronic Conspicuity And Right Of Way Are The Pressure Points

The reopened 2026 comment period shows where the FAA saw the most friction. In January, the agency reopened the BVLOS NPRM comment period for focused input on electronic conspicuity, ADS-B Out, right-of-way policy, and detect-and-avoid assumptions. The reopening notice says more than half of the roughly 3,100 NPRM comments discussed the right-of-way proposal in some capacity.

That should get every commercial operator's attention. BVLOS is not only a question of whether a drone can fly beyond visual range. It is a question of how the aircraft detects other traffic, how low-altitude right-of-way is assigned, when electronic conspicuity is enough, and what happens around aircraft that are not broadcasting a cooperative signal.

The FAA later denied an extension request and kept the reopened comment period closing on February 11, 2026. That does not create a new comment window now. It does show which issues are most likely to affect the final operational rule.

What Operators Should Do Before The Final Rule

The near-term work is preparation, not speculation. Operators should inventory aircraft by Remote ID status, detect-and-avoid capability, command-and-control architecture, maintenance record, and mission type. If a fleet is being positioned for infrastructure inspection, industrial mapping, agriculture, or delivery, the records should show which aircraft can support those missions under a performance-based framework.

Teams should also document the human side of BVLOS. Who supervises automated operations? Who monitors airspace and weather? How are exceptions escalated? What data gets stored after each flight? Those questions may sound administrative, but they are exactly where a waiver-based program can stumble when it tries to scale into routine operations.

Finally, operators should stop treating BVLOS as one market. Infrastructure corridors, industrial sites, crop spraying, and package delivery have different risk profiles. The FAA's proposed approach is broad enough to touch all of them, but the compliance evidence for each mission will not be identical.

The Practical Takeaway

The BVLOS ARC report is still worth reading because it explains how the industry framed the problem. It is not the current deadline. The live work is preparing for the Part 108 framework that followed, especially around electronic conspicuity, right-of-way, detect-and-avoid, UAS Traffic Management, and operational records. Operators who start organizing that evidence now will be in a stronger position when the FAA moves from proposal to final rule.