Remote ID was designed for cooperative airspace participants, but security teams are dealing with adversarial actors.
Every time a drone incident makes the news, whether it's contraband drops at a correctional facility or surveillance activity near a power plant, I see the same response from security teams: "We're covered. We have Remote ID."
Remote ID sounds like a detection capability. It is not. FAA Remote ID is a regulatory broadcast framework for compliant operators. RF detection is independent drone detection that does not depend on operator participation to detect drone activity. Confusing the two creates that gap between compliance and actual airspace awareness which is where the bad actors operate.
So...what is Remote ID?
Remote ID is a rule that requires drones over 250 grams to broadcast their location and operator information. Think of it as a digital license plate law. It's useful when everyone follows it. It falls apart the moment they don't.
And in the security context, "the moment they don't" is the only moment that matters.
Every drone is flown with a purpose, whether for recreation, commercial operations, photography, or criminal activity. However, Remote ID alone cannot reliably identify every drone in the airspace. Operators may use sub-250 gram drones that are exempt from certain Remote ID requirements, fly drones from manufacturers that have not fully complied with the standard, or simply disable the Remote ID broadcast...a process that can take as little as 30 seconds.
In 2024 testing, only one of seven major drone manufacturers demonstrated full Remote ID compliance. These realities highlight why organizations need detection capabilities that extend beyond Remote ID alone.
Remote ID assumes the person flying wants to be identified. Security teams are responsible for detecting both cooperative and non-cooperative activity.
SkySafe doesn't rely on a drone choosing to broadcast. Our sensors listen to the radio frequency communication between a drone and its controller. That signal exists whether the operator wants it to or not. Detection is there from the moment of liftoff, not once a drone crosses some geofence or triggers a camera. The drone doesn't have to cooperate. It just has to fly.
What that means practically: we see the drones that Remote ID-only systems miss entirely. Not occasionally. Consistently. We've sat alongside competitor systems at the same facility and watched them show minimal activity while our sensors were tracking multiple non-DJI drones the other system had no visibility into. The competitor system wasn't broken. It was doing exactly what it was built to do. The limitation of Remote ID is not the technology. It’s the assumption of compliance.
The other piece that gets overlooked is what happens after detection. Remote ID tells you a drone is there right now. It doesn't tell you that the same drone was at that location seventeen times in the past two months. It doesn't give you flight history, operator behavior patterns, or the kind of drone forensic data that becomes evidence in a prosecution. It's a snapshot. Security teams need a record.
SkySafe builds that record. Every flight, every operator location, every timestamp, stored and searchable. When a drone is recovered, our forensics team can extract and decrypt flight data directly off the device and produce court-admissible reports. No other drone detection platform in this market offers that.
The industry conversation around Remote ID has been dominated by compliance questions: do drones have it, are manufacturers implementing it, is enforcement catching up. Those are regulatory questions and they're worth asking. But they're not the same as asking whether your facility can detect a drone that doesn't want to be detected. That's a different question entirely, and it requires a different tool.
Remote ID is a license plate law. SkySafe is the license plate reader network, and it works even when the license plate is missing.
