Remote ID for Part 107: The Rule Most Candidates Get Half Right

Ask a Part 107 candidate what Remote ID does and the most common wrong answer isn't a wild guess. It's a half-truth: "it's like a license plate for your drone." Close enough for a hallway conversation, wrong enough to miss exam questions, because a license plate identifies a vehicle once, at registration. Remote ID broadcasts live position data, continuously, for the entire flight. Those are different problems with different rules attached, and the exam is built around candidates conflating them.

Two compliance paths, not one rule

Since September 16, 2023, operating an unmanned aircraft in U.S. airspace requires one of two things: a Standard Remote ID aircraft, or a Remote ID broadcast module. There's no third option for most Part 107 flights, and the two paths aren't interchangeable footnotes of each other, they have genuinely different requirements.

A Standard Remote ID aircraft has the broadcast capability built in by the manufacturer. It transmits its own identity (serial number or a session ID), the control station's location, the aircraft's own location and altitude, its velocity, a synchronized time mark, and emergency status. All of that comes from the aircraft itself, continuously, from the moment it's airborne.

A broadcast module is what you add to an aircraft that doesn't have Standard Remote ID built in. It broadcasts a narrower set of data: its own serial number, the aircraft's location and altitude, velocity, the takeoff location, and a time mark. That last detail matters more than it sounds like it should: a module reports where the flight started, not a live control-station position. If the pilot walks somewhere else mid-flight, that doesn't change what the module is broadcasting, and it doesn't create a compliance problem by itself.

The module path also comes with a real operational constraint that a lot of candidates miss: when you're relying on a broadcast module, you have to be able to see the aircraft yourself throughout the flight. A visual observer doesn't substitute for that. Standard Remote ID doesn't carry that restriction.

FRIA is an exception, not a loophole

The third term that shows up on the exam is FRIA, an FAA-Recognized Identification Area. It's real, and it's genuinely useful for people flying aircraft that were never built with Remote ID and can't practically be retrofitted, like a lot of FPV and hobby platforms. Inside a FRIA, you can operate without Remote ID equipment at all.

What a FRIA is not: a blanket exemption from the rest of Part 107. Flying inside one doesn't waive airspace authorization, doesn't waive registration, and doesn't waive anything else in the regulation. It waives exactly one requirement, Remote ID equipage, and nothing else. Exam questions built around FRIA usually test exactly that boundary, by describing a pilot who assumes "I'm in a FRIA" answers more than it does.

What Remote ID deliberately isn't

Two comparisons are worth holding in your head at the same time, because the exam uses both to check whether you actually understand the rule or just memorized the term.

Remote ID is not registration. Registration puts an aircraft on record with the FAA once. Remote ID requires that record to connect to something broadcasting during flight, but they're separate compliance requirements that both have to be satisfied. Losing track of which one you're being tested on is the single most common way to miss an otherwise straightforward Remote ID question.

Remote ID is also not ADS-B Out, and small unmanned aircraft are specifically prohibited from transmitting it. ADS-B Out is how manned aircraft broadcast to air traffic control on dedicated aviation frequencies with genuinely limited bandwidth; if a meaningful fraction of consumer drones started transmitting on those same frequencies, it would degrade the system that manned aviation depends on. Remote ID solves the same underlying problem, "where is this aircraft," over Wi-Fi or Bluetooth instead, specifically so it doesn't compete for that bandwidth.

The pattern behind the trap questions

Every Remote ID exam trap follows roughly the same shape: describe a pilot doing something reasonable-sounding, then ask whether it satisfies Remote ID. Flying far from an airport doesn't satisfy it. Using a visual observer doesn't satisfy it. Registering the aircraft doesn't satisfy it. None of those are Remote ID compliance methods, they're separate good practices or separate rules entirely, and the question is really just checking whether you can tell the difference between "this is a good idea" and "this is what the regulation actually requires."

If there's one habit worth building before test day, it's this: whenever a Remote ID question describes a scenario, ask what specifically is being broadcast, by what equipment, and from where, before deciding whether the scenario is compliant. The rule is mechanical once you separate it from registration and from ADS-B in your head; it only feels hard while those three are still tangled together.

For the full regulatory citations and the practice questions built around each piece of this, the Remote ID section of the handbook walks through all seven ACS elements individually, with drills for each.