BVLOS drone regulations should be read at their actual stage, while a purchase separates the operator's present authority from equipment capability and future rulemaking. Commit to the operating concept first, then release hardware and expansion spending against defined milestones. A proposal for broader operations is useful planning context, but it is not an authorization for a specific route.
Table of Contents
Read the rulemaking signal at its actual stage
On January 28, 2026, the FAA reopened comments on its BVLOS proposal, specifically seeking further input on electronic conspicuity and right-of-way issues. That document is a proposed-rule action. It should not be cited as an operating certificate or as proof that every proposed requirement is already effective.
The FAA’s Part 107 waiver guidance describes the operation, hazards, mitigations, aircraft and personnel information required for the waiver pathway. A procurement team should identify the pathway applicable to its actual operation and inspect the resulting authorization and conditions.
This is a US procurement framework. Other jurisdictions use different approvals and terminology. The useful discipline is the same: keep the source’s legal stage, the operator’s permission and the supplier’s technical claims in separate fields.
Define the operation before the aircraft shortlist
“Inspect a pipeline” is too broad for a configuration baseline. A useful concept states the route, terrain, population exposure, airspace, launch and recovery locations, crew roles, communications and intended inspection output.
Changing one of these inputs can alter both the technical solution and the approval work. A remote launch site may reduce travel while increasing maintenance and recovery difficulty. A longer route may need different communications arrangements even if the airframe has enough energy.
The industrial drone procurement overview covers the wider purchasing process. The specific task is deciding which expenditure can proceed before the BVLOS program’s dependencies are resolved.
Use staged commitments
A staged purchase makes the dependencies visible without pretending that every project follows an identical approval timeline.
| Milestone | Concrete deliverable | Spending decision |
|---|---|---|
| Concept defined | Route, output, operating roles and intended pathway | Fund feasibility and configuration work |
| Technical baseline agreed | Aircraft, payload, control links and contingency behavior | Order a bounded pilot configuration |
| Applicable authority in place | Approved scope and conditions mapped to the baseline | Release operations within that scope |
| Representative output accepted | Route result, data quality and recovery demonstration | Expand the fleet or geographic scope |
| Configuration changes | Impact assessment against operation and approval | Release affected changes after resolution |
The milestones are a project contracting structure, not FAA-required payment stages. A buyer can adapt them to its procurement process. The important feature is that each payment or expansion has an observable dependency.
Put the dependency in the RFI
An RFI can ask each supplier to state the aircraft and control-link configuration it will support, the documents it will provide for the operator’s approval case, and the changes that would require a new or amended authorization. Ask for the response per milestone, not as one general compliance statement. A supplier that cannot separate those items is unlikely to support a staged purchase well.
Allocate the approval-related work
The operator owns the operational case. The manufacturer supplies configuration and capability information within its scope. The integrator resolves interfaces and produces the records needed to connect the equipment to the intended mission. A contract should identify who updates each item after a payload, firmware or communications change.
Specify evidence for command-link behavior and usable mission energy separately. A good radio link does not resolve every airspace risk, and long endurance does not establish detect-and-avoid capability.
For a critical infrastructure program, keep a permitted pilot task that is valuable even if broader authorization takes longer. A demonstration without an operational customer is not a useful fallback.
The industrial UAV configuration and its approval dependencies belong in the project resource package, with the trigger for each revision. Change the baseline when a final rule, effective date, transition requirement or operating authorization changes the project—not when a headline says BVLOS is becoming easier.
FAQs
Does buying a BVLOS-capable aircraft authorize the flight?
No. The aircraft's technical capabilities and the operator's authorization are different. The applicable approval must cover the operation, location, configuration and conditions.
Should a supplier promise approval by a fixed date?
A supplier can commit to defined technical documents and support tasks. An authority controls its own approval decision, so contract milestones should distinguish deliverable dates from regulatory outcomes.
Can equipment be purchased before the full operating area is approved?
A bounded pilot purchase can be reasonable when its permitted uses and financial exposure are clear. Expansion should depend on the intended authorization and demonstrated output, rather than an assumed approval date.
Can a staged purchase still use a single supplier?
Yes, if the contract separates technical deliverables from regulatory outcomes and names the owner of each update. A single supplier can support multiple milestones, but the buyer should retain acceptance and expansion decisions.
