What Is Remote ID and Why It Exists

The plain-English version: a digital license plate for drones

Remote Identification (Remote ID) is a requirement that an unmanned aircraft broadcast certain identifying information, in real time, over radio frequency, while it is flying. Nearby personal wireless devices — a smartphone or tablet running the right app — can pick up that broadcast directly, without needing an internet connection or any special receiving equipment, and see basic facts about the aircraft in the sky above them. The FAA's own framing for this, and a genuinely useful mental model for the knowledge test, is that Remote ID functions like a license plate on a car: it does not stop anyone from driving, and it does not by itself tell a passerby who owns the vehicle, but it gives authorities a reliable way to identify that vehicle and, if needed, trace it back to a registered owner. Remote ID does the same thing for an unmanned aircraft in flight.

Why the FAA built this requirement: safety and security

Two distinct goals drove Remote ID, and both show up in ACS Task I.F. The first is safety and airspace integration. As the number of small UAS operating in the national airspace system has grown, the FAA, air traffic control, and other aircraft need a reliable way to know what is flying and roughly where, especially as the agency works toward more advanced future operations like routine beyond visual line of sight (BVLOS) flights. Remote ID is a foundational building block for that future airspace, functioning conceptually similar to how ADS-B Out gives manned aircraft mutual awareness of each other, even though the two systems are technically different and serve different aircraft populations.

The second goal is security. Remote ID gives the FAA, law enforcement, and other federal security partners a way to identify a UAS in flight and quickly assess whether it represents a properly authorized operation or a potential safety or security concern — for example, an unauthorized flight near a stadium during an event, close to critical infrastructure, or inside a temporary flight restriction. Before Remote ID, identifying an unknown drone in flight generally required physically locating and interacting with whoever was on the controls. Remote ID makes that identification possible without ever needing to find the pilot first.

A separate regulation from Part 107 — but one Part 107 cross-references

A common point of confusion is assuming Remote ID rules live inside 14 CFR Part 107 itself, the way the 400-foot altitude limit or the daylight-operations rule do. They do not. Remote ID is governed by its own, entirely separate regulation: 14 CFR Part 89, Remote Identification of Unmanned Aircraft. Part 89 applies broadly across essentially all categories of civil unmanned aircraft operations in the United States — not just Part 107 commercial flights, but recreational flights and others as well — which is exactly why it needed its own Part rather than being folded into Part 107's operating rules.

That said, Part 107 does reference Part 89 directly in places where the two rules interact. For example, 14 CFR 107.145, governing sustained flight over open-air assemblies of people, requires that the operation meet the requirements of either § 89.110 or § 89.115(a) — the two Remote ID compliance methods covered in Lessons B and C of this module. Treat Part 89 as the authoritative source for every Remote ID knowledge/risk-management element tested under I.F, and expect test questions to cite it by its own section numbers, not by a 107.xx number.

Who Remote ID applies to: it is about registration, not size

Section 89.105 states that the Remote ID requirement applies to any unmanned aircraft that is "registered or required to be registered" under 14 CFR Part 47 or Part 48. That single phrase is the entire key to understanding applicability, and it is worth re-teaching the registration rule fully here because it determines whether a given aircraft needs Remote ID at all.

14 CFR Part 48 governs registration of small unmanned aircraft. There are two very different registration pathways depending on how the aircraft is actually flown:

• Genuinely recreational flying under 49 U.S.C. § 44809 (the Exception for Limited Recreational Operations of Unmanned Aircraft): a recreational flyer meeting every condition of that exception — flying purely for recreation, following community-based safety guidelines, staying within visual line of sight, yielding right-of-way to manned aircraft, and the other conditions taught in Module 1 — is not required to individually register an aircraft that weighs less than 0.55 lb (250 g) at takeoff, including everything on board. This is narrow: it is a recreational-only exception, not a general "small drones don't need to register" rule.
• Part 107 operations: there is no weight-based registration exception under Part 107. Every aircraft flown under Part 107 — commercial or otherwise non-recreational — must be registered under Part 48 regardless of how small or light it is. A 3-ounce micro drone used for a paid real estate photography job still must be registered if it is flown under Part 107, exactly the same as a 20-pound mapping platform.

Because 89.105's applicability trigger is registration status rather than weight, and because virtually every Part 107 aircraft is required to be registered no matter how small it is, Remote ID applies to virtually all Part 107 operations. Being small and light does not exempt an aircraft flown under Part 107 from Remote ID the way it might for a genuinely recreational flyer under § 44809.

Scenario: a 0.4 lb (180 g) drone used for a paid rooftop inspection

You are hired to fly a compact 0.4 lb (180 g) quadcopter to photograph a rooftop solar installation for a commercial client. Because this is a paid, non-recreational operation, it must be conducted under Part 107. Working through the applicability chain: the flight is under Part 107, so the aircraft must be registered under 14 CFR Part 48 regardless of its weight — the 0.55 lb (250 g) recreational-only exception under 49 U.S.C. § 44809 does not apply, because this is not a recreational flight. Since the aircraft is registered (or required to be registered), § 89.105 applies, and Remote ID is required. The only way to fly this aircraft without Remote ID equipment would be operating entirely within an FAA-Recognized Identification Area, which is very unlikely to include a client's rooftop (Lesson D covers this fully). In practice, this aircraft needs either Standard Remote ID or a broadcast module before this job can be flown legally.