How to find a drone's Remote ID serial number

The drone remote id serial number is the string that identifies your aircraft in every Remote ID broadcast and on its registration, and it is not always the number printed largest on the box. For an aircraft that broadcasts natively, it is the serial the producer assigned to the airframe and listed on a declaration of compliance accepted by the FAA. For an older aircraft fitted with a broadcast module, the number that belongs on the registration is the module's serial, not the airframe's. Filing the wrong one is a paperwork error with a compliance shape.

This article covers where the number physically lives, how to confirm you have the right one rather than a support or warranty reference, what the registration rule expects you to file, and how to check a serial against the FAA's own records. It closes with the fleet problem underneath all of it, which is keeping the number stamped on an airframe and the number filed with the government pointing at each other as aircraft move through a program.

Where the number lives on the aircraft

Start with the airframe. Producers of standard Remote ID aircraft must affix a label showing that the aircraft meets the requirements, in English, legible, prominent, and permanent, and the serial is usually printed on or beside it. On most airframes that label sits inside the battery bay, under a removable arm cover, or on the underside of the fuselage. It survives handling by design, which is the point: the label has to be readable years later on an aircraft that has been in and out of cases and trucks.

The second place is software. The manufacturer's flight application generally exposes the serial in a device information or about screen alongside firmware versions, and that screen is often easier to photograph than a label buried under a battery. Third is the original packaging and the purchase paperwork, which is the least reliable source because boxes get separated from aircraft. Whichever route you take, capture the serial once, into your own records, rather than rediscovering it every time a form asks.

Which serial the rules expect you to file

Format matters more than it looks. Under 14 CFR 89.505, a producer may not build a standard Remote ID aircraft or a broadcast module without assigning it a serial number that complies with ANSI/CTA-2063-A, the small unmanned aerial systems serial number standard incorporated into the rule. That standard gives serials a defined structure rather than leaving each manufacturer to invent one, which is what makes a broadcast serial meaningful to a receiver that has never seen your aircraft before. A support reference or an internal asset tag will not satisfy it.

The registration side is where operators most often go wrong. For a standard Remote ID aircraft, the Certificate of Aircraft Registration must carry the serial number of the aircraft. For an aircraft flying on a broadcast module, the registration must carry the serial number of the module. Programs that retrofit older airframes sometimes file the airframe serial out of habit, leaving the registration describing an aircraft that broadcasts a number the FAA has not been told about. A serial also cannot sit on more than one registration at a time, which matters when aircraft change hands.

Checking a serial against the FAA's records

A serial is only useful if it appears where the rule expects it. A standard Remote ID aircraft may be flown only if its serial is listed on a declaration of compliance the FAA has accepted, or if the aircraft is covered by a design or production approval. Producers submit those declarations with the make and model, the serial number or the range of serial numbers being declared, the radio equipment identifier, and the means of compliance used. The FAA publishes the accepted declarations in its UAS Declaration of Compliance list, which is searchable by make and model.

Checking takes a minute and is worth doing at acquisition rather than at an audit. Look up the model, confirm the declaration is accepted and current, and confirm your serial falls inside the declared range. Aircraft bought secondhand, imported, or acquired with a fleet during an acquisition are the ones worth checking hardest, because a model can appear compliant while a particular unit predates the declaration or came from a channel the producer never declared. Record the result of that check with the airframe, along with the date you made it.

Keeping the numbers aligned as a fleet moves

One aircraft with one serial is a five minute problem. Thirty aircraft across four sites, some broadcasting natively and some carrying modules, with airframes retired, replaced under warranty, and reassigned between projects, is a different exercise. Warranty replacements are the quiet troublemaker: the aircraft that comes back from service is often a different unit with a different serial, and the registration that was correct on the day it shipped now describes an airframe that is sitting in a manufacturer's workshop somewhere.

The habit that holds this together is filing the serial as an attribute of the airframe rather than as a line on a form. Each aircraft record carries its Remote ID serial, the module serial if one is fitted, the registration number the serial sits on, the expiration date of that registration, and the date somebody last confirmed the declaration of compliance. When an airframe is swapped, the record changes and the registration follows. When an inspector reads a number off the side of an aircraft, the answer is one lookup away and it matches.

Common mistakes in Remote ID serial numbers

Filing the airframe serial on a module equipped aircraft. When compliance runs through a broadcast module, the module's serial is the one the registration must carry. The airframe serial belongs in your own equipment record.

Using a support or asset reference. Only a serial meeting the ANSI/CTA-2063-A standard does the job. Internal asset tags and customer service reference numbers look official and satisfy nothing.

Skipping the declaration of compliance check. A model being listed is not the same as your unit falling inside a declared serial range. Secondhand and imported aircraft deserve the check most.

Leaving a serial on an old registration. A serial cannot sit on two registrations at once, so an aircraft sold or transferred without cancelling the original entry blocks the new owner from registering it properly.

Not updating after a warranty replacement. A replacement airframe carries a new serial. The registration that covered the original aircraft does not follow the box back from the service center.

FAQ

Is the Remote ID serial the same as the serial on the box?

Often, but not always. The number that counts is the one meeting the ANSI/CTA-2063-A standard and appearing on the accepted declaration of compliance, which may differ from a shorter support reference printed on packaging or paperwork.

What serial do I file if I fitted a broadcast module?

The module's serial number. The registration for an aircraft complying through a broadcast module must carry the module serial, and the airframe serial stays in your own equipment records rather than on the certificate.

Can two aircraft share one Remote ID serial?

No. Serials are assigned per aircraft or per module by the producer, and a given serial cannot appear on more than one registration at a time, which is why transfers need the old registration cancelled first.

Where can I check that my model has an accepted declaration?

The FAA publishes accepted declarations of compliance in its UAS Declaration of Compliance list, searchable by make and model. Confirm both that the declaration exists and that your serial falls within the declared range.

Closing thought

Finding the serial is easy. Keeping it correct across a fleet, through retrofits, transfers, and warranty swaps, is the part that quietly decays, and it decays in a place nobody looks until a registration renewal or a ramp check forces the comparison. The number on the aircraft and the number on file should be the same number, and somebody should be able to prove that without opening a battery bay.

If you are reconciling what is filed with the FAA against what is stamped on the airframe, FlybyOps was built for the operational record problem at the center of regulated drone work. An equipment registry holding per airframe history, a document vault with expiration tracking, role based access so the right people maintain those entries, and an append-only audit log are all part of how the platform keeps the number an inspector reads off an aircraft and the number on file pointing at each other.