Regulatory briefing
BVLOS is not a spray-drone shortcut yet. It is a waiver and risk-management problem.
As of May 17, 2026, routine beyond-visual-line-of-sight operations are still not a normal default for most U.S. agriculture drone operators. Plan around Part 107 visual-line-of-sight rules unless you have a specific approval path.
Last checked: May 17, 2026
BVLOS means the remote pilot cannot see the aircraft well enough with unaided vision to know its position, attitude, altitude, and direction of flight. For agriculture, that sounds attractive: larger farms, remote fields, linear scouting, and fewer repositioning stops. The regulatory reality is slower.
BVLOS status board · Last checked May 17, 2026
Routine VLOS
Normal Part 107 planning lane for most farm jobs.
Waiver path
Specific safety case; approval should not be assumed.
Enterprise operations
Possible in controlled programs with heavier documentation.
Rulemaking
Part 108 direction of travel, not blanket permission.
What operators should assume today
| Decision | Best fit | Watch point |
|---|---|---|
| Standard Part 107 job | Visual-line-of-sight missions with certificated remote pilot control. | The operator still needs airspace, Remote ID, and operating-rule compliance. |
| BVLOS waiver | Specific operation with a documented safety case and mitigation plan. | Approval is not automatic and should not be assumed in a sales plan. |
| Future routine BVLOS | Strategic planning for fleet operations and remote acreage. | Do not build a launch business model on rules that are not yet routine. |
Part 108 status: proposed, not a shortcut
The FAA released a proposed rule in August 2025 to normalize certain beyond-visual-line-of-sight drone operations. The FAA describes the proposal as covering operations, aircraft manufacturing, separation from other aircraft, operational authorizations, responsibility, security, reporting, and recordkeeping. That matters, but it is not the same as every farm operator being free to launch routine BVLOS work tomorrow.
For planning purposes, treat Part 108 as the direction of travel, not current permission for a specific spray or scouting job. A serious operator should understand the proposal, follow the final-rule process, and avoid selling BVLOS capacity until the legal pathway is real for that aircraft, crew, geography, and operation.
Why BVLOS is hard in farm country
Agriculture fields may look empty, but the airspace is not empty. Low-altitude crewed aircraft, helicopters, ag aircraft, utility work, rural airports, roads, and people near field edges all matter. A BVLOS safety case has to explain how the operator detects and avoids other aircraft and manages lost link, command, airspace, and emergency procedures.
Operational question
How will the crew detect and avoid low-altitude traffic, handle lost link, maintain command, define the operating area, and keep people and roads outside the risk picture?
Business question
Does the job still work financially if visual observers, reposition stops, waiver preparation, documentation, or a narrower operating area are required?
Remote ID is not BVLOS permission
Remote ID helps identify drones in flight; it does not by itself grant authority to fly beyond visual line of sight. Operators should treat Remote ID as a baseline compliance layer, not as a waiver substitute.
The same caution applies to obstacle avoidance sensors and autonomous flight software. Those features may support a safety case, but they do not replace the legal authority to conduct the operation.
Where BVLOS may matter first
Agriculture BVLOS may become most useful for linear inspections, scouting large contiguous acreage, remote pasture checks, irrigation infrastructure, and fleet operations where the operator can define the area and mitigations tightly. Spray work adds more complexity because the operation is not merely flight; it is also chemical application, label compliance, drift management, and often low-altitude work near field boundaries.
That does not make BVLOS irrelevant. It makes it a planning layer: useful for long-term fleet strategy, weak as a near-term promise unless the operator already has the approval path and safety case.
What to do before promising BVLOS service
- Define the exact operating area, altitude, aircraft, and crew roles.
- Map nearby airspace, roads, airports, and crewed low-altitude activity.
- Document detect-and-avoid, lost-link, and emergency procedures.
- Confirm Remote ID, pilot certification, and aircraft requirements.
- Use FAA primary sources and current waiver guidance before quoting the job.
This page is operational research, not legal advice. FAA rules and waiver expectations can change, and pesticide work adds a separate compliance layer outside the BVLOS question.