By Wesley Alexander • June 3, 2026 • 9 min read
The interesting thing about the Part 108 NPRM is not that the crewed-aviation lobby pushed back. That was inevitable. The interesting thing is that AOPA, EAA, ALPA, and NBAA largely agree on the problem, and the problem is not whether scalable BVLOS happens. It is who absorbs the residual midair risk while detect-and-avoid technology, automation, and oversight catch up to the privileges the rule grants.
If you are an operator preparing a Part 108 application, building a BVLOS network, or briefing a commercial customer on what scalable BVLOS looks like, this is the alignment that will shape the final rule. Not the loudest comment letter. The convergence underneath them.
What the Four Organizations Actually Said
Commercial UAV News summarized the four-organization response this week, and the framing matters. AOPA, EAA, ALPA, and NBAA represent very different constituencies: general aviation pilots, recreational and experimental builders, airline crews, and business aviation operators. Their day jobs barely touch each other. But on Part 108 they converge on three points.
First, they accept that BVLOS and advanced air mobility are coming and that a scalable rule is better than an indefinite waiver regime. None of them are arguing for a moratorium. That is a significant shift from the tone of crewed-aviation pushback five years ago.
Second, they question the rule's heavy reliance on detect-and-avoid systems and high levels of automation that have not yet demonstrated mature, durable safety performance across the operational envelope the rule would unlock. The concern is not theoretical DAA. It is DAA at scale, in mixed traffic, against light aircraft that may not be electronically conspicuous, in weather and lighting conditions that stress sensors.
Third, and most pointed, all four organizations argue that the NPRM as drafted shifts residual risk onto crewed aircraft. The phrase that keeps surfacing is "silent risk transfer." Crewed aviation should never bear elevated collision risk because a new entrant scaled its operations before its technology fully closed the safety loop.
Their individual lenses differ in instructive ways. AOPA worries about the general aviation pilot in a Cessna 172 becoming the de facto absorber of risk in low-altitude airspace. EAA points out that experimental and light-sport aircraft fly lower and slower, often without the avionics that DAA systems assume. ALPA holds the most conservative line, arguing for airline-grade safety standards before normalization. NBAA, the most integration-forward of the four, supports Part 108 but conditions support on foundational infrastructure: robust DAA, electronic conspicuity, and information sharing that actually works in the field.
The Operator Translation
If you are reading this as a Part 108 applicant or a BVLOS service provider, the comment letters are not just political theater. They will shape what the FAA tightens in the final rule, and the things they will tighten are the things you need to be documenting now.
Three areas matter most.
DAA performance evidence. The NPRM is performance-based. That language sounds operator-friendly, but performance-based standards only work if the operator can demonstrate the performance. If your BVLOS concept of operations relies on detect-and-avoid against non-cooperative crewed traffic, you should be building a case file that goes beyond manufacturer specs. Sensor envelope, false-positive rate, geometry assumptions, latency through the C2 link, behavior in degraded conditions, and the human-in-the-loop or human-on-the-loop role when the system flags conflict. Reviewers will not accept a vendor data sheet as a safety case.
Electronic conspicuity assumptions. A meaningful share of the operations Part 108 would normalize assume that crewed traffic is broadcasting position. That is not a safe assumption in 2026. ADS-B Out is required in much of the airspace BVLOS will use, but compliance is not universal, and the lower the altitude, the messier the picture. If your operational design relies on cooperative detection, you should also document what happens when the conspicuity assumption fails. The crewed-aviation organizations are going to keep hammering this point until the rule reflects it. See our earlier analysis of the electronic conspicuity debate for the longer thread.
Tiered authorization fit. The two-tier permit-and-certificate structure is the FAA's primary tool for matching authorization to risk. Operators who try to slot complex, populated-area, or shared-airspace operations into the lower tier will draw heat from exactly the organizations writing these comment letters. Plan the application against where the operation actually sits on the risk curve, not where it is cheapest to live.
Why This Lands on Public Safety and Delivery First
Two operator segments are going to feel this debate before anyone else: public safety drone-as-first-responder programs and commercial delivery networks. Both push BVLOS at meaningful scale, both interact with low-altitude crewed traffic, and both are politically visible.
Public safety DFR programs have been one of the strongest demonstrations of the operator value of BVLOS, and they are also the operations crewed-aviation groups watch most closely. A medevac helicopter and a DFR drone responding to the same incident is not a hypothetical. Programs that document conspicuity, coordination, and DAA assumptions now will be in a better position when Part 108 lands. Programs that wave at "we will figure it out" will be the case studies the comment letters cite.
Delivery is the other one. Wing's Houston expansion and Amazon's UK launch are operating at densities that will eventually intersect the same airspace as general aviation training operations and aerial application work. We covered the regulatory shape of that integration in our Part 108 complete guide and the BVLOS normalization market analysis. The honest read is that the delivery business case depends on a final rule that does not silently transfer risk to the GA community, because if it does, the comment process will tighten it, and the tightening will land on operators.
What the Final Rule Will Probably Look Like
I am not in the room when the FAA writes the final rule, so this is judgment, not prediction. But the shape of the four-organization pushback suggests a few likely adjustments.
DAA documentation requirements will get more specific. Expect named performance metrics, named conditions, and named edge cases that applicants must address rather than a generic "demonstrate safe operation" standard. That is good for serious operators and painful for the marketing-led BVLOS pitch decks.
The certificate tier is likely to absorb more operations than the permit tier as drafted. The FAA will move complexity up, not down, in response to the crewed-aviation comments. Operators planning to live in the lighter tier should pressure-test that assumption.
Electronic conspicuity assumptions will be made explicit. If the rule depends on cooperative detection, the rule will probably say so, and operators will need a documented fallback for the non-cooperative case. NBAA's comments in particular point this direction.
Coordination obligations will sharpen. The vague "notify and coordinate with stakeholders" language in early BVLOS thinking has not survived contact with reality. Expect more defined coordination duties around airports, public safety operations, and special-use airspace.
Operator Bottom Line
Part 108 is not in trouble. The four organizations all accept its general direction. But the NPRM as drafted is going to get edited where the risk distribution is uncomfortable, and the operator community should be building application packages that survive those edits rather than packages that assume the lightest possible reading of the proposal.
If you are an operator working a BVLOS path right now, three things to do this month:
- Audit your DAA evidence. Move from vendor specs to documented operational performance in the conditions you will fly.
- Audit your conspicuity assumptions. Where you assume cooperative detection, write the non-cooperative fallback.
- Audit your tier fit. Be honest about whether your operation is a permit or a certificate operation, and build the package the harder tier will demand.
The crewed-aviation organizations are not blocking BVLOS. They are forcing the rule to be precise about who carries the residual risk. Operators who treat that as input, not opposition, will land Part 108 authorizations faster than the ones who treat the comment process as theater.
UAVHQ supports operators preparing Part 108 applications, BVLOS waiver packages, and DAA/conspicuity documentation. If your team is working the path now and wants a structured operator-side review before submission, that is the kind of work we do.