Remote ID for Part 107: What Most Candidates Miss

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.

What are the two Remote ID compliance paths?

Under 14 CFR §89.105, after September 16, 2023, no one may operate an unmanned aircraft in U.S. airspace unless the operation meets §89.110 (a Standard Remote ID aircraft) or §89.115 (a broadcast module, or flying inside an FAA-recognized identification area). The rule applies to anyone flying an unmanned aircraft that is registered or required to be registered. For an ordinary Part 107 job, that means one of the two equipment paths, and they have genuinely different requirements. Practice material written before that date may still call Remote ID optional; the outdated question bank post lists that and five other warning signs.

A Standard Remote ID aircraft has the broadcast capability built in by the manufacturer. Under §89.305 it transmits its identity (serial number or a session ID), the latitude, longitude and altitude of the control station, the latitude, longitude and altitude of the aircraft, its velocity, a UTC time mark, and emergency status. It must broadcast from takeoff to shutdown, and if the broadcast stops, the person manipulating the controls must land as soon as practicable.

A broadcast module is what you add to an aircraft that doesn't have Standard Remote ID built in. Under §89.315 it broadcasts a narrower set of data: its own serial number, the aircraft's latitude, longitude and altitude, velocity, the takeoff location and altitude, and a time mark. The module's serial number must be on the aircraft's Certificate of Aircraft Registration, the pilot must confirm before takeoff that it's working, and a lost broadcast in flight again means landing as soon as practicable. 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 broadcast location comparison puts the two message lists side by side.

The module path also comes with a real operational constraint that a lot of candidates miss: under §89.115(a)(2)(ii), the person manipulating the flight controls must be able to see the aircraft at all times. A visual observer doesn't satisfy that on the pilot's behalf, even though under Part 107's own visual line of sight rule an observer normally can. Standard Remote ID carries no such extra condition in Part 89.

What is a FRIA and when does it apply?

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. Under §89.115(b), you can fly without Remote ID equipment only while both the aircraft and the person manipulating the controls stay inside the FRIA's boundaries for the whole flight, and that person can see the aircraft at all times.

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 14 CFR §107.53 prohibits operating a small UAS under Part 107 with ADS-B Out in transmit mode, unless the FAA authorizes it (§107.52 does the same for transponders). 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," on unlicensed spectrum compatible with personal wireless devices, in practice Wi-Fi or Bluetooth, 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.

Remote ID is separate from registration, which is covered in registration, reporting, and preflight. It also interacts with operations over people, and equipment restrictions are a different topic, covered in Is DJI banned?.