Legal to fly, hard to replace: the FCC drone listing and public-safety fleets

The week

On December 22, 2025, the Federal Communications Commission added uncrewed aircraft systems, the formal term for drones and the controllers and software that go with them, and their critical components produced in foreign countries to its Covered List. The FCC is the federal agency that regulates the airwaves, and because drones talk to their controllers by radio, they fall under its rules. The Covered List is the FCC’s register of communications equipment judged to pose an unacceptable risk to national security.

The step followed a national security determination by an Executive Branch interagency body, a group of federal agencies that assessed the risk. The FCC also cited Section 1709 of the Fiscal Year 2025 National Defense Authorization Act, the annual defense law, which had singled out two manufacturers, DJI and Autel Robotics, for review.

Take a county fire chief the morning after the news broke. Her department’s drones have found lost hikers, mapped wildfire edges at night and spotted hot spots inside burning buildings. Almost all of them were made abroad. Her inbox fills with the same question from the county manager, the sheriff and a local reporter: “Are we still allowed to fly them?”

Being on the list blocks new FCC equipment authorizations. An equipment authorization is a kind of federal permission slip: most products that send or receive radio signals, from phones to baby monitors to drones, need one before they can be marketed or imported in the United States. No authorization, no new models on American shelves.

The listing did not, by itself, prohibit the continued use of models the FCC had already authorized. The drones already sitting in fire stations and police evidence rooms could keep flying.

That distinction mattered enormously, because many state and local police, fire, emergency management and public works agencies had built their drone programs on foreign-made aircraft, much of it from DJI. So the honest answer to the fire chief’s question was “yes, for now.” How long the fleet would last, and what would replace it, were matters only just opening up.

Public-safety drone programs grew quickly over the past decade, many on inexpensive, capable foreign-made aircraft. As the aircraft became cheaper and easier to fly, the uses multiplied: search and rescue, accident scene mapping, fire overwatch, bridge and roof inspections, flood assessment.

The December action was easy to misread as a ban. It was narrower than that, and for budget holders more awkward. Existing aircraft stayed legal to fly, but the pipeline of new models closed. A ban would at least have forced an immediate, funded decision. A closing pipeline lets the problem arrive slowly, aircraft by aircraft, until a program discovers it has fewer drones than missions.

Unlike most communications equipment, drones have short service lives, consumable parts and a continuous dependence on software. The exposure splits four ways, each with its own owner and timeline: the airframes in service, the spares that keep them flying, the software and data services behind them, and the replacement fleet.

Seven parts of a public-safety drone program

A public-safety drone is more than a flying camera. A working program is a small system with several parts:

• The airframe: the aircraft itself, with its motors, propellers and frame.
• The payload: usually a camera, sometimes a thermal camera that sees heat, mounted on a gimbal, a motorized cradle that keeps the picture steady while the aircraft moves.
• Batteries: the single biggest consumable. A drone may fly for well under an hour on one, and each battery wears out after a limited number of charges, much like an old phone that no longer lasts the day.
• The controller and app: a handheld unit, often paired with an agency phone or tablet running the maker’s flight app.
• Firmware: the software built into the aircraft and controller that governs how it flies. Makers update it to fix bugs, close security holes and comply with airspace rules.
• Cloud and data services: online services for mapping, storing video, managing fleets and logging flights.
• People and paperwork: trained pilots, maintenance records, policies on when drones may be used, and rules for handling the footage.

Seen this way, the FCC’s action touched almost every layer. It did not stop the aircraft flying today, but it raised questions about whether parts, firmware and services would keep flowing, and about what the agency would buy next.

The airframes in service

Aircraft already authorized could keep operating. That bought time, though not much. Public-safety drones crash, get lost over water and wear out from heavy use. A program that flew a dozen aircraft at the end of 2025 would not fly the same dozen in 2028.

The practical issue is attrition rather than legality. Attrition is the rate at which a fleet shrinks through loss and wear. A program manager needs to know, for each airframe, its age, flight hours, mission and expected remaining life. From that comes a simple forecast: how many aircraft the program will have in each of the next three years if nothing new is bought.

Many agencies found their drone records sat with individual units or pilots rather than in a fleet system. One aircraft’s logbook lived in a patrol sergeant’s spreadsheet; another’s lived only in the maker’s app. That made the forecast slow, and it made it harder to show a budget office the shape of the decline.

The forecast also forces a mission decision. Not every use needs the same aircraft. Search and rescue, fire overwatch and crash reconstruction may justify keeping the best remaining airframes in reserve for them. Routine inspection and training flights can shift to older aircraft, or to replacements first. Ranking missions this way lets a program protect the capability that matters most while the fleet shrinks.

One page for the county board

Say a county emergency management agency runs a mixed fleet. Its coordinator builds a one-page table: each aircraft, its hours, its role, and a best guess at when it will be retired or lost. The table shows that the county will have enough aircraft for every mission through next year, but only enough for search and rescue the year after. The coordinator also notes which aircraft hold evidence footage in the maker’s cloud and which controllers run on phones connected to the county network. That single page turns a vague worry into a concrete choice for the county board: fund replacements in the coming budget, or accept that bridge inspections will go back to ladders and lift trucks. It gives elected officials a concrete account of what would be lost if replacement funding slipped, which is more persuasive than a general warning.

Spares, batteries and repairs

Consumables decide how long the airframes last. Batteries degrade with charge cycles, propellers and gimbals break, and cameras fail. An aircraft with a healthy frame but no working batteries stays on the ground.

Whether a replacement part counted as a covered critical component, and whether new versions could be authorized, depended on details the FCC continued to work through after December. That uncertainty is itself a planning fact: a program could not assume that a battery or camera it bought last year would be available on the same terms next year.

Agencies that used the manufacturer’s repair service also had to ask whether it would continue at the same price and speed in the United States. A two-week repair turnaround that became two months would take aircraft out of service without anyone deciding to.

Stockpiling is the obvious response, but batteries have limited shelf lives and stockpiles tie up money. A sensible middle course is a defined reserve of the highest-failure parts for the aircraft expected to stay in service longest, bought once and tracked. Spending on spares for aircraft that will be retired soon is money better saved for replacements.

Cannibalizing grounded airframes for parts, taking working components from a retired aircraft to keep others flying, is a legitimate plan if it is deliberate and recorded. Done informally, it leaves an agency unsure which aircraft contain which parts, which matters both for safety and for audit.

Software, firmware and data services

Modern drones depend on firmware updates, flight apps, mapping tools and cloud services, many supplied by the aircraft maker. If a supplier’s U.S. business shrinks, update frequency and support quality can fall while the aircraft remain legal. Being allowed to fly a drone differs from being able to fly it safely and securely.

That has security consequences. Unpatched flight software, meaning software that no longer receives fixes for known flaws, and controller apps on agency phones are risks in their own right. A phone running an unsupported app, connected to the agency network, is a potential door into other systems. Some states had already restricted foreign-made drones in state agencies for that reason. A practical safeguard is to isolate controller devices whose software is no longer maintained: dedicated phones or tablets, kept off the main network.

It also has data consequences. Agencies should know where flight logs, video and imagery are stored, who can reach them and how they would be exported if the vendor changed. “The cloud” here means the vendor’s servers, located wherever the vendor chooses. Many programs run in local data mode, where footage stays on the device and agency systems, or on agency-managed platforms for this reason.

For footage used as evidence, chain of custody requirements do not change because the vendor did. Chain of custody is the documented record of who handled a piece of evidence and when, which courts rely on to trust that it was not altered. If drone video sits in a vendor cloud that is winding down, the agency needs a way to get it out with that record intact. The records retention schedule, the formal list of how long each kind of public record must be kept, should cover drone footage explicitly, including footage held in a vendor cloud.

The replacement fleet

The fourth exposure is the one that needs money. U.S.-made and allied alternatives existed, and federal programs such as the Defense Department’s Blue UAS list, a roster of drones the department has vetted for security, had already steered some buyers toward vetted models. They generally cost more per aircraft and sometimes offered different capabilities, such as shorter flight times or different sensors. Pilots used to one system would need retraining on another.

That is a budget-cycle problem. Most state and local agencies set capital budgets a year or more ahead, and grant programs carry their own rules on eligible equipment. An agency that started replacement planning in January 2026 could fund aircraft in a later fiscal year. One that waited for its fleet to fail would face an unfunded gap, often at the moment a high-profile search or fire needed air support.

Cooperative purchasing helps. Statewide contracts and multi-agency buys can lower unit costs, standardize training and spares, and give smaller jurisdictions access to terms they could not negotiate alone. A small town buying two aircraft on its own has little bargaining power; buying through a statewide contract alongside dozens of other agencies changes that conversation.

Procurement teams should also price the whole program, beyond the aircraft: pilot retraining, docking stations, software subscriptions, data storage and the cost of running two fleets in parallel during a transition. The sticker price of a drone can be the smallest part of the bill.

Running two fleets in parallel deserves particular attention. During a transition, pilots may need to stay current on both the old and new systems, spare parts for both must be kept, and footage may flow into two different storage platforms with different export tools. Planning a clear cut-over date for each mission, rather than letting the two fleets overlap indefinitely, keeps that cost contained. It also gives the training team a schedule it can actually meet, and gives the records team a single date after which new footage lands in one place.

Four ways the fleet reaches the county manager’s desk

A county manager or city council might leave the whole issue to the drone coordinator, but the consequences land on the leadership’s desk in four ways.

Money. A program that has to replace its fleet all at once, in an emergency, pays more and gets less. The same replacement spread over two or three planned budget cycles, bought through cooperative contracts, is far easier to absorb. The difference lies less in the price of the aircraft than in whether the purchase was planned.

Operational risk. Drones have become part of how many agencies do their work. When a child goes missing near a river or a wildfire jumps a ridge at night, the question is whether there is an aircraft in the air within minutes. A shrinking, poorly tracked fleet means that answer can slip from “yes” to “sometimes” without anyone noticing.

Security and legal exposure. Unsupported software on devices connected to agency networks is a cyber risk that auditors and insurers increasingly ask about. Drone footage used in prosecutions has to survive a defense lawyer’s questions about how it was stored and handled. A vendor change that breaks the chain of custody can weaken a case that has nothing to do with drones.

Public trust. Drone programs already attract scrutiny over privacy and surveillance. An agency that can explain plainly what it flies, why, where the footage goes and how long it is kept is in a much stronger position than one that discovers those answers during a public records request or a council hearing. The regulatory change is an opportunity to put that house in order.

Put together, these make the drone fleet a modest line item with outsized consequences, which is exactly the kind of issue that benefits from a short, early conversation at the leadership level.

Asset management instead of an emergency request

Elected officials and budget offices need a straightforward briefing. The program is not being shut down, but its cost base is changing. The decisions made in the next one or two budget cycles will determine whether coverage continues without a gap. Presented that way, replacement funding reads as asset management rather than an emergency request, and it competes on ordinary terms with roads, vehicles and buildings.

A well-run response tends to share a few traits. There is a single fleet register instead of a scattering of spreadsheets. There is a three-year attrition forecast tied to ranked missions. There is a tracked spares reserve aimed at the aircraft that will last longest. Controller devices running unsupported software are isolated. Drone footage is covered by the retention schedule and can be exported with chain of custody intact. And replacement is priced as a whole program and bought through cooperative contracts where possible.

Good programs also keep the conversation with elected officials regular rather than occasional. A short annual update on fleet size, missions flown, spares on hand and the replacement timeline costs little and means that, when the funding request comes, nobody is surprised by it.

The failures are equally recognizable: treating “still legal” as “no action needed,” buying spares for every aircraft rather than the ones worth keeping, forgetting that evidence footage lives in a vendor cloud until a court asks for it, and asking for replacement money only after a high-profile failure, when the request looks like an emergency and the budget is already set.

What the county board needs to hear about its drones

• If we buy nothing new, how many aircraft will we have in each of the next three years, and are the best of them reserved for the missions that matter most?
• Are the firmware and flight app for each model still being updated, and if not, are those controller devices kept off our network?
• Where is our drone footage stored, and could we export evidence from a vendor cloud tomorrow with chain of custody intact?
• Which budget cycle will fund replacements, and does the estimate include retraining, docks, software and storage?

An honest set of answers to these questions is, in effect, the briefing the county board needs. It turns a regulatory headline into an ordinary, manageable asset decision.

With hindsight

The FCC kept adjusting the action in the months that followed, and each adjustment showed how much detail sat beneath the original headline.

On January 7, 2026, after a further determination from the Defense Department, the FCC exempted drones and components on the Blue UAS Cleared List and those qualifying as domestic end products under the Buy American standard, both until January 1, 2027. For agencies already shopping for replacements, that was a meaningful signal about which aircraft would stay purchasable, at least for a time.

Its engineering office also granted limited waivers allowing certain permissive changes to previously authorized covered drone equipment, which the Commission said in September 2026 remained in effect through January 1, 2029. Some modifications to drones already on the market could still go ahead under defined conditions.

Then, in July 2026, FCC bureaus proposed prohibiting continued importation and marketing of previously authorized drones from several foreign producers, while stating that the proposal would not affect continued use of equipment already purchased. That proposal reached further back than the December action, to models already approved as well as new ones.

“Legal to fly” proved a narrower comfort than it first looked. Aircraft could stay in service while the routes to buying more of them kept closing.

For agencies, the effect was gradual rather than sudden, which is exactly why it was easy to underestimate. Programs that budgeted for replacement in 2026 are positioned for a funded transition. Those that counted on existing aircraft lasting face attrition with fewer choices and higher unit prices.

The lesson reaches beyond drones. When a regulator closes the pipeline for a product rather than banning it outright, the risk shifts from compliance to asset management. The organizations that cope best are the ones that know what they own, how long it will last, and which budget cycle will pay for its successor.