WEEKEND SPECIAL   October 11, 2026

A restriction written when cellular phones were still a novelty has become an obstacle to connecting aircraft that inspect power lines, deliver packages and support emergency crews. This weekend, we're looking at the FCC's proposal to open the 800 MHz cellular band to drones: where the restriction came from, what removing it could accomplish, and what still stands between a rule change and a working service.

The story begins well before commercial drones. In 1981, the FCC established licensing rules for cellular service in the 800 MHz band. U.S. commercial cellular service arrived in Chicago on October 13, 1983. These were the early days of analog mobile phones, when making a call from a car was a considerable achievement.

Taking those phones into the air created a different problem. Cellular networks reuse frequencies across separate coverage areas. A transmitter high above the ground can reach many more cell sites, potentially interfering with customers across several areas at once. The FCC's concern was protecting the network serving people below.

The agency announced an airborne-use prohibition in 1984 and adopted a formal rule in December 1991. That broad restriction, now found in section 22.925, also caught drones in its scope.

Wireless technology kept moving. Analog systems gave way to successive digital generations, including LTE and 5G. The airborne restriction remained. The FCC's October draft argues that modern networks have tools to manage the interference that prompted the original ban, including identifying airborne devices, receiving height reports and managing their connections.

Read more

Further reading: AT&T's account of the 1983 commercial launch

Further reading: FCC draft order and technical background

The FCC's proposed order, released October 8, would exempt uncrewed aircraft and their associated systems from the airborne restriction and add an allocation allowing their mobile communications in the band.

The frequencies are 824–849 MHz and 869–894 MHz, totaling 50 MHz of existing licensed spectrum. The proposal would let cellular licensees support drone operations there. It would not turn those frequencies into an unlicensed band anyone could use freely.

The attraction is practical. In comments cited by the FCC, AT&T and Verizon describe the band's propagation characteristics as particularly useful for rural and suburban drone operations. The draft identifies agriculture, utility and pipeline inspection, search and rescue, wildfire monitoring, and delivery as potential beneficiaries.

For a utility trying to inspect a long corridor, another usable cellular band could mean more options for maintaining the aircraft's connection. For a delivery operator, it could give a network provider more flexibility to support control messages and payload data. Those are potential operating benefits; the order does not promise a particular flight range or uninterrupted coverage.

There is also a business case. The FCC says adding this band could lower deployment costs and improve service by allowing providers to supplement or substitute for spectrum already available to drones. That could help operators make better use of existing cellular infrastructure.

Some other cellular bands already support drone operations without this particular prohibition. The proposal therefore expands the available choices. It also expressly preserves the restriction on airline passengers operating their cellular phones while airborne.

Read more

FAA permission remains a separate requirement. The FCC proposal changes access to radio spectrum. It does not approve a delivery route or authorize flights beyond visual line of sight. For operators using Part 107, the FAA continues to identify operations beyond its visual-line-of-sight limits as requiring a waiver. The mission still needs the applicable aviation authority.

The carrier and aircraft have to be ready. The draft retains existing cellular service rules and licensed geographic limits. An operator should confirm that its provider supports airborne use, that the aircraft's radio and software support the service, and that the arrangement meets the mission's needs. A change in the rulebook alone does not establish those things.

The connection needs to prove itself where the aircraft flies. My practical test would be straightforward: check coverage along the route and at operating altitude, measure delays and interruptions, and verify what the aircraft does when the connection fails. The FCC's technical case for lifting a general prohibition is encouraging, but it is not a performance guarantee for an individual operation.

For customers, that means the path runs through carrier offerings, compatible aircraft and demonstrated operating reliability. Those steps will determine how quickly the regulatory opportunity becomes a useful service.

Read the FCC draft, including the continuing service conditions

The FCC's tentative agenda places the proposed order at its October 29, 2026 open meeting, scheduled to begin at 10:30 a.m. Eastern / 9:30 a.m. Central. As of this edition, the Commission has not adopted it, and the draft can still change.

If adopted as written, the order and rule amendments would take effect 30 days after publication in the Federal Register. The clock would run from publication, not from the meeting date. There is no fixed effective date yet.

This is a draft Report and Order following earlier public input. The FCC sought comment on airborne restrictions in 2023 and revisited the issue in April 2026; that later round had May 1 comment and May 18 reply deadlines. Those deadlines have passed.

The FCC has not supplied a date by which carriers must launch drone services in this band or the public will be able to buy them. For planning purposes, keep three milestones separate: adoption, legal effectiveness and commercial availability.

See the order here: FCC draft order, including the proposed effective date