Home » Updates » The FCC Is Looking Past the Hardware Now.

The FCC Is Looking Past the Hardware Now.

The FCC’s latest move in the DA 26-758 proceeding extends the question past which drones are on the market to what’s running inside them. The newest development in this saga signals that scrutiny may reach into drone software and supply chains, not just the airframe and its country of origin, but the code, updates, and vendor relationships underneath.

That’s a different compliance conversation than the one most contractors have been having. A hardware ban has a clear line: is the aircraft on the list or not. A software and supply-chain question doesn’t have a clean line yet. It’s asking who wrote the flight controller firmware, who maintains the cloud pipeline the data lands in, and how many hands are between capture and deliverable.

Our clients don’t buy a drone. They buy a deliverable. An orthomosaic, a progress report, a closeout package that has to hold up months or years later. If software provenance becomes part of that compliance picture, every contractor with a reality-capture line item in a contract needs an answer to “what’s actually running our data pipeline” before it becomes a question from an owner’s counsel instead of a curiosity.

We’ve already mapped our stack – flight software, processing pipeline, storage – against exactly this question, because a service provider that can’t answer it isn’t ready for enterprise work regardless of what the FCC ultimately decides. Whatever the final rule looks like, the contractors asking this question now are the ones who won’t be scrambling for an answer in Q4.

Source: https://dronelife.com/2026/08/20/fcc-drone-software-rules/