Understanding FAA Remote ID requirements for buyers importing into the US
Remote ID is frequently confused with registration and with the broadcast module rules. They are three separate obligations, and conflating them produces avoidable costs at the point of import.
There are three distinct obligations and buyers routinely bundle them together. The first is aircraft registration, which falls on the operator rather than the owner and is completed before first flight in the FAADroneZone system. The second is the Remote ID requirement itself, which applies to most aircraft operated in United States airspace and requires the aircraft to broadcast identification, position and operator information. The third is the operational rule for how that broadcast must be achieved.
On that third point, the rule permits three routes. The aircraft may have Remote ID built in, in which case the aircraft is identified on the FCC grant as Remote ID compliant and the buyer should see that noted on the product documentation. Or a separate module may be attached to the aircraft, which then must itself be registered and must broadcast the host aircraft’s information rather than its own. Or a broadcast module may be flown alongside the aircraft in the same operation and in the same visual line of sight, broadcasting the host aircraft’s information, with the module itself registered to the remote pilot rather than the aircraft owner.
The practical commercial consequence is worth stating plainly. An aircraft sold for the US market with built-in Remote ID and an FCC grant that reflects it can be imported and operated without further hardware work. An aircraft sold without Remote ID capability, into a market where the operator intends to fly commercially, means the buyer faces either a retrofit cost or a restriction to operations where a visual line of sight to the operator is maintained and no other aircraft is in the airspace — which in practice excludes a great deal of useful commercial work.
For suppliers, this creates a documentation obligation. Because the FCC grant is what establishes the compliance claim, and because the grant must match the specific model, a supplier who simply asserts "Remote ID ready" without identifying the grant, the module route, or the certification basis has given the buyer nothing usable. The verifiable evidence is specific: the FCC ID, the grant document showing the Remote ID certification, and for a separate-module configuration, the module’s own FCC ID and its broadcast behaviour with respect to the host aircraft.
There is also a timing consideration worth planning for. The requirement has been enforced through a phased schedule with enforcement discretion applied over time, so a platform that complies today will remain compliant, but a platform sold on the basis that compliance is optional creates a future problem for the operator, and in some jurisdictions creates a problem for the importer as well. Where a buyer is unsure whether a platform is compliant, the correct answer is to ask for the grant document rather than to accept a summary statement.
