Registration puts your aircraft on paper; Remote ID puts it on the air. Under § 89.105, since September 16, 2023 no person may operate an unmanned aircraft in the airspace of the United States unless the operation meets § 89.110 or § 89.115 — the two ways of carrying Remote ID that the next sections lay out — apart from a narrow research-and-testing exception under § 89.120. For a Part 107 operator that makes Remote ID a condition of nearly every flight, not an accessory: no compliant Remote ID, no legal takeoff.

What the rule requires is a broadcast. A compliant aircraft transmits a standardized set of message elements — the identifying information the rule specifies — directly from the aircraft, and it must do so continuously, from takeoff to shutdown. This is not a one-time registration lookup or something an observer requests; it is a signal the drone sends the entire time it is flying, so that anyone with the right receiver can identify the aircraft in real time. The registration number from earlier in this chapter is the aircraft’s identity on the ground; Remote ID is how it announces itself while it is in the air.

Because Remote ID is a live broadcast, the rule attaches a duty for when it fails. Under § 89.110 and § 89.115, if the aircraft is no longer broadcasting the required message elements, the person manipulating the flight controls must land as soon as practicable. A Remote ID system is therefore not fit-and-forget equipment: losing the broadcast mid-flight is itself a reason to bring the aircraft down, not a paperwork issue to sort out later. How an aircraft actually produces that broadcast — built in, or through an added module — is the choice the next section sets out.