Federal Aviation Administration Announces Major Drone Rule Changes

For years, commercial drone operators have faced a strange mismatch: the aircraft can navigate miles of pipeline, map enormous farms, or carry medicine across town, but the person responsible for the flight has generally needed to keep the drone in sight. It is a little like owning a racehorse and being told it may only trot around the mailbox.

The Federal Aviation Administration is now trying to replace that case-by-case system with a national framework for routine beyond visual line of sight, or BVLOS, operations. The proposed rules would create a new Part 108 for operators and aircraft, plus a Part 146 for automated data services that help organize low-altitude traffic. The goal is not to turn the sky into an airborne freeway overnight. It is to make advanced drone operations predictable, scalable, and safer than a patchwork of individual waivers.

What the FAA’s Drone Rule Changes Actually Do

Routine BVLOS Flights Would Get a Defined Approval Path

The biggest change is simple to describe and complicated to regulate: approved drones could fly beyond the operator’s direct view without obtaining the same kind of one-off waiver used today. Under the proposal, BVLOS flights would generally take place at or below 400 feet above ground level and begin from predesignated, access-controlled locations.

Operators would still need FAA approval for the geographic area, expected daily activity, launch and landing points, communications coverage, and procedures for a lost control link. In other words, “beyond sight” would not mean “beyond planning.”

The proposal is designed for package delivery, precision agriculture, infrastructure inspection, aerial surveying, public-safety missions, training, testing, demonstrations, and certain recreational operations. Those use cases matter because their economics often collapse when companies must place a visual observer every few hundred yards. A pipeline inspection is less impressive when the crew following the drone needs more vehicles than a small parade.

Operators Would Use Permits or Operating Certificates

The FAA proposes two approval tracks. A lower-risk, limited-scale operation could receive an operating permit. A larger, faster, heavier, denser, or otherwise higher-risk operation would need an operating certificate.

Certified operators would face deeper FAA review and oversight and would need a safety management system and formal training program. This risk-based structure is meant to avoid treating a small rural mapping mission exactly like a high-volume delivery network over a populated suburb.

The permit route could be especially important for smaller companies, utilities, local governments, universities, and public-safety agencies. However, “streamlined” does not mean casual. Applicants would still need operating manuals, documented procedures, trained personnel, approved aircraft, recordkeeping systems, and credible answers to every regulator’s favorite question: “What happens when something fails?”

Some Drones Could Be Much Heavier Than Part 107 Aircraft

Part 107 generally covers drones weighing less than 55 pounds. The proposed Part 108 framework could accept certain unmanned aircraft weighing as much as 1,320 pounds, including payload, although lower weight limits would apply to many permit categories.

That headline number does not mean a half-ton drone could immediately buzz through a neighborhood with a patio set dangling underneath. Aircraft size, speed, mission type, population density, and operational risk would determine which approval path and limitations apply.

Instead of requiring every Part 108 aircraft to obtain a traditional airworthiness certificate, the FAA proposes an “airworthiness acceptance” process based largely on FAA-accepted industry consensus standards. Manufacturers would test designs, establish operating limitations, publish maintenance information, and preserve compliance data.

This approach is intended to move faster than conventional aircraft certification while still giving the agency a formal safety gate.

Safety Technology Moves to Center Stage

Detect-and-Avoid Systems Become Essential

A human pilot can look outside and avoid traffic. A BVLOS drone cannot rely on eyeballs, sunglasses, or optimistic vibes. The proposal therefore places heavy emphasis on detect-and-avoid technology, strategic separation, conformance monitoring, reliable command-and-control links, and right-of-way rules.

Part 108 drones would have to yield to crewed aircraft in specified circumstances and avoid interfering with traffic around airports, heliports, seaplane bases, launch facilities, and eVTOL sites. Some operations would need systems capable of detecting both cooperative aircraft that broadcast their position and non-cooperative aircraft that do not.

This safety question has already produced an industry argument. Amazon’s Prime Air has supported robust detect-and-avoid requirements and said its system prevented potential conflicts during real operations. Other industry voices have pushed for a more flexible, performance-based approach and broader electronic visibility requirements for low-flying crewed aircraft.

The disagreement is important: it is not about whether safety matters, but about which equipment should carry the burden and how prescriptive the final rule should be.

Automated Data Service Providers Would Help Manage Traffic

The proposed Part 146 would regulate Automated Data Service Providers, or ADSPs. These services could help drones avoid one another, verify that flights remain inside approved areas, provide surveillance or weather information, and support UAS Traffic Management.

An operator could contract with an outside provider or, if qualified, provide the service internally. Think of it as a digital traffic-management layer for dronesair traffic coordination without a tiny control tower staffed by very small people drinking even smaller coffee.

Because a faulty data service could misroute many aircraft at once, the FAA wants oversight of providers, software revisions, testing records, and performance standards. This is one of the proposal’s most consequential features. Scalable drone operations depend not only on sturdy aircraft but also on trustworthy software and data networks.

Flights Over People Would Expand, but Not Everywhere

The FAA proposes five operating categories based on population density. As the number of people below a route increases, the required technical and operational protections would also increase.

Flights could be allowed over people under approved conditions, but not over large open-air gatherings such as concerts, sporting events, or crowded parks. That distinction reflects a basic risk principle: a brief route over scattered pedestrians is not the same as crossing a packed stadium during the seventh-inning stretch.

Each Part 108 drone would also need lighting and Remote ID. Remote ID acts somewhat like a digital license plate, broadcasting identifying and location information required for accountability. The proposal combines that visibility with route approval, operational records, incident reporting, and stronger oversight of aircraft and service providers.

Security, Cybersecurity, and Records Are Not Side Notes

The proposed rules treat a drone network as both an aviation system and a potential security target. Operators would need physical-security controls, cybersecurity policies, incident-response plans, and protections against unauthorized access or intentional electronic interference.

The Transportation Security Administration would conduct security threat assessments for certain operations supervisors, flight coordinators, and other covered personnel. Package-delivery operators would face additional TSA program requirements.

Operators would keep detailed flight, maintenance, inspection, training, and personnel records. They would report events such as loss of control or communications, unplanned landings, automated-service failures, flights into unauthorized areas, significant security breaches, and operations causing more than $500 in property damage.

Manufacturers and data-service providers would have their own testing, software, configuration, and continuing-safety records. The paperwork may not be glamorous, but aviation has never considered “we forgot to write it down” a premium safety strategy.

Who Stands to Benefit From Part 108?

Delivery and Medical Logistics

Routine BVLOS approval could let delivery networks serve more customers from fewer launch sites. The most persuasive examples may involve urgent items rather than novelty snacks: prescriptions, laboratory samples, blood products, or medical supplies for rural and tribal communities.

The FAA added new test sites in Oklahoma and Indiana in 2026 to support BVLOS, cargo delivery, multiple-drone operations, and increasingly autonomous systems.

Agriculture, Energy, and Infrastructure

Farmers could monitor crops, apply treatments, and survey large properties without repositioning a pilot every few minutes. Utilities could inspect transmission lines, pipelines, bridges, rail corridors, and storm damage more quickly while reducing the need to place workers near hazardous equipment.

These are not flashy “flying robot” fantasies. They are repetitive, expensive jobs where range and automation can produce measurable value.

Public Safety and News Gathering

Fire departments, emergency managers, and law-enforcement agencies could use approved BVLOS systems to search large areas, assess disasters, or maintain awareness when roads are blocked.

News organizations could also use the aerial-surveying pathway for photography and reporting, although they would still need FAA authorization and would face fleet, weight, route, and operational limits.

What the Proposal Does Not Mean

It does not give every recreational pilot permission to fly over the horizon. It does not eliminate airspace authorization, Remote ID, registration, local launch-and-landing restrictions, temporary flight restrictions, or the duty to avoid crewed aircraft.

It does not authorize flights over packed events. It also does not make Part 107 disappear; operators choosing to remain within Part 107 would continue to follow that framework. As of July 2026, the FAA’s own current Part 107 guidance still says pilots must keep drones within sight unless another approval applies.

The final version may also differ from the proposal. The public comment period closed in October 2025 after thousands of submissions, and debate continued into 2026 over detect-and-avoid requirements, low-altitude electronic conspicuity, cost, competition, and the treatment of smaller operators.

A separate FAA proposal announced in May 2026 would allow certain critical-infrastructure operators to petition for site-specific drone restrictions, showing that federal policy is expanding legitimate use while tightening protection around sensitive locations.

Practical Experience: What Operating Under the New Framework Could Feel Like

Experience 1: The Mission Begins Long Before Takeoff

Imagine a small utility preparing to inspect 40 miles of distribution line after a windstorm. Under ordinary visual-line-of-sight operations, the crew might leapfrog vehicles along the route, stop repeatedly, reposition observers, and spend more time coordinating people than collecting images.

Under a future Part 108 permit, the company could design an approved operating area, define launch and recovery sites, confirm communications coverage, load current airspace restrictions, and file the day’s mission into its operating system.

The practical lesson is that BVLOS does not remove work; it moves work upstream. The crew trades constant physical repositioning for detailed planning, reliable software, equipment checks, and documented contingencies.

Before launch, the flight coordinator verifies weather, NOTAMs, aircraft status, Remote ID, lighting, battery reserves, detect-and-avoid health, and the lost-link response. The drone may be automated, but the checklist will not become shy.

Experience 2: A Lost Link Becomes a Designed Event, Not a Surprise

During the inspection, cellular coverage drops near a wooded ridge. In an amateur setup, that moment might produce frantic tapping and language unsuitable for an operations manual. In a compliant BVLOS program, the response has already been tested.

The aircraft follows a predefined contingency: hold, climb or descend within approved limits, divert to a safe landing point, or return along a validated route. The data service flags the deviation, the flight coordinator monitors the response, and the operator records the event for review.

That experience captures the FAA’s philosophy. Safety is not based on promising that failures will never occur. It is based on proving that foreseeable failures have controlled outcomes.

Mature operators will practice lost communications, navigation faults, weather deterioration, unexpected crewed traffic, and emergency landings until the response becomes routine rather than theatrical.

Experience 3: Communities Notice More Than the Technology

Now picture a suburban delivery trial. Residents may appreciate receiving medicine quickly, yet still ask reasonable questions: How loud are repeated flights? Are cameras recording yards? Who answers complaints? Can drones cross school property? What happens when a route changes?

An operator that arrives with only a glossy demonstration and a cheerful “trust the robot” message will probably discover that public acceptance has its own form of gravity.

The strongest programs will publish plain-language route information, explain privacy practices, offer a complaint channel, track noise, and show how emergency procedures work. They will also avoid pretending every concern is anti-technology.

Community engagement is operational risk management. A technically safe system can still fail commercially if people below it feel ignored.

Experience 4: Smaller Operators Face Both Opportunity and Pressure

A local surveying company may finally gain access to missions once reserved for firms with the resources to pursue complex waivers. That is the opportunity.

The pressure comes from aircraft acceptance, software subscriptions, cybersecurity procedures, staff training, manuals, maintenance records, and insurance. The business case will depend on whether the permit process is genuinely accessible and whether shared data services reduce costs rather than creating a new tollbooth in the sky.

For operators preparing now, the smartest experience-building steps are unglamorous: improve recordkeeping, standardize maintenance, document risk assessments, test emergency procedures, train staff to recognize airspace hazards, and evaluate communications and detect-and-avoid systems.

Companies that already run disciplined Part 107 programs will have a head start. Companies whose safety system consists of “Dave is usually careful” may find the transition more educational.

Conclusion: A Bigger Sky With More Rules, Not Fewer

The FAA’s proposed drone rule changes represent the largest potential shift in U.S. commercial drone operations since Part 107. Part 108 could replace many individual BVLOS waivers with scalable permits and certificates, support larger and more automated aircraft, establish regulated traffic-data services, and open practical routes for delivery, farming, inspection, public safety, and aerial surveying.

Yet the proposal is not deregulation wearing propellers. It adds airworthiness acceptance, operational approvals, detect-and-avoid expectations, security screening, cybersecurity, reporting, maintenance, and oversight.

The bargain is straightforward: operators may gain more range and flexibility, but only by demonstrating more system-level responsibility. The future of drones may be autonomous, but it will still have forms to fill out.