FAA Declaration of Compliance: what operators must check

An FAA Declaration of Compliance is a manufacturer's formal statement to the FAA that a drone or broadcast module meets the performance requirements of a rule, filed for Remote ID under Part 89 and for operations over people categories under Part 107. Operators never file one. They rely on them, usually without noticing, every time a purchased aircraft's Remote ID counts as compliant or a category label makes certain flights over people legal. The declaration is the invisible paperwork underneath the spec sheet, and the FAA keeps a public list of every accepted one.

This article explains why the declaration belongs to the manufacturer and not the operator, what a DOC covers and where the system lives, and how a buying or flying operation should use the public list. The closing sections take up the operator's half of the bargain: knowing, and being able to show, which declaration each aircraft in the fleet is standing on.

A manufacturer's filing, not an operator's

The regulatory design splits the work cleanly. The producer of a standard Remote ID aircraft or a broadcast module declares to the FAA that the product was designed and built to an FAA accepted means of compliance, a technical standard describing how the performance requirements are met. The same declaration mechanism serves manufacturers labeling aircraft as Category 2 or Category 3 for operations over people. Acceptance by the FAA puts the product on the public list, and with it come ongoing duties. Every declaring manufacturer must tell the FAA and the public about a defect that breaks compliance. Remote ID producers must do it within 15 calendar days of learning of it, and must also arrange recurring independent audits.

Operators sit entirely on the consuming side, and the FAA is explicit that individual owners should not submit declarations. Your obligations are to fly aircraft whose compliance claims are real: a Remote ID serial number that appears on an accepted declaration, a category label backed by one when flying over people under those provisions. The division matters most when it fails, because an aircraft whose declaration is rescinded loses the compliance its operations were built on, through no action of the operator at all.

Which categories require a Declaration of Compliance

Four things need one, and each sits under its own rule:

• Standard Remote ID aircraft (14 CFR 89.530). A standard Remote ID drone may be flown only if its serial number is listed on an FAA accepted declaration, unless a part 21 design or production approval covers it instead (89.110).
• Remote ID broadcast modules (89.530). An aircraft flying with a module complies only if the module's serial number is on an accepted declaration (89.115).
• Category 2 operations over people (107.160). The manufacturer declares the aircraft won't cause an injury as severe as an 11 foot-pound impact from a rigid object, has no exposed rotating parts that would lacerate skin, and has no safety defects (107.120).
• Category 3 operations over people (107.160). The same test at 25 foot-pounds (107.130).

Two categories need no declaration. Category 1 is limited to aircraft of 0.55 pounds or less, including everything on board, with no exposed rotating parts that would lacerate skin (107.110). Category 4 needs an airworthiness certificate issued under part 21 instead (107.140). Remote ID and operations over people need separate declarations, so an aircraft listed for one isn't necessarily listed for the other. The FAA's own search page points this out.

When the FAA accepts a declaration

The rules don't say a declaration is issued. The manufacturer submits it, and the FAA accepts it once it determines the applicant has demonstrated compliance, then notifies the applicant (107.160(b) for operations over people, 89.535(b) for Remote ID). For Category 2 and 3, the submission names the make and model, the serial number or range of serial numbers it covers, and whether it's an initial or amended declaration. It also names the accepted means of compliance used, which must consist of test, analysis or inspection (107.155, 107.160(a)).

What the declaration covers and where it lives

The system of record is the FAA's UAS Declaration of Compliance site, which serves two audiences from one address: manufacturers file and manage declarations there, and everyone else uses the public list to look up accepted ones. A listing ties a manufacturer and model, and for Remote ID the serial number scheme, to the rule and the accepted means of compliance it was declared against. For Remote ID that covers standard aircraft and broadcast modules; for operations over people it covers the category eligibility a label asserts.

Reading a listing well means knowing what it is and is not saying. It says the FAA accepted the manufacturer's declaration that the product meets the requirements; it does not grade the aircraft, and it does not follow the airframe through firmware changes and repairs. It also is not permanent: the FAA can rescind a declaration, and products fall off the accepted list. The list is a snapshot of standing, which is why the check belongs at specific moments, before purchase, before a category dependent operation, and periodically across a fleet, rather than once forever.

How operators should use the public list

Before buying, the list is a procurement filter. A drone marketed as Remote ID ready either appears on an accepted declaration under the serial number scheme it ships with or it does not, and a Category 2 or 3 claim either traces to a listing or is a brochure sentence. Checking takes minutes and belongs in the purchase file with the quote, because the aircraft's compliance basis is part of what the money bought. Registration then depends on getting the details right, since a standard Remote ID aircraft registers with its Remote ID serial number.

In service, the check becomes an occasional fleet hygiene task. Match each airframe's model and serial scheme to its declaration, note the declaration identifier in the aircraft's record, and recheck when the FAA's list changes or a manufacturer issues a compliance notice. Category dependent work deserves the strictest version: an operation flying over people under a category label should be able to point from the job to the aircraft to the label to the accepted declaration in one motion, because that chain is exactly what a ramp inspection or an incident review will walk.

To check one aircraft on the FAA's Declaration of Compliance list:

1. On the DOC Search tab, filter by type: OOP for operations over people, RID for Remote ID.
2. Search the make and model, or use the Serial Number Lookup tab with the aircraft's or module's serial.
3. Confirm the status reads Accepted and your unit's serial falls inside the declared range.
4. Copy the tracking number into the aircraft's record with the date you checked.

What the rules ask of the operator

The declaration is the manufacturer's filing, but three duties built on it fall on whoever flies the aircraft:

• Fly only listed aircraft. A standard Remote ID drone needs its serial number on an accepted declaration (89.110), and a Category 2 or 3 operation over people needs the aircraft listed and labeled for that category (107.115, 107.125).
• Stop when a declaration is rescinded. For operations over people, no person may operate an aircraft identified on a rescinded declaration while it stays rescinded (107.160(d)(1)). If a safety issue goes unresolved, the FAA can issue a notice proposing rescission, which gives the holder 30 calendar days to respond, but in an emergency it can rescind by order without that process (107.160(d)(3) and (d)(4)). For Remote ID, a rescinded declaration means the serial is no longer on an accepted one, so the aircraft no longer meets 89.110.
• Replace a lost label. If a Category 2 or 3 label is damaged, destroyed or missing, the remote pilot in command must relabel the aircraft in English, legibly and so it stays on for the flight, before flying over people (107.135).

Compliance you can look up beats compliance you assume

Most operators inherit their compliance posture from the checkout page: the drone was expensive and current, so surely the paperwork underneath it is fine. That works until the day it has to be shown. A client's aviation counsel asks how the fleet meets Remote ID; an inspector asks why this aircraft may fly over that crowd; an insurer asks after an incident whether the category claim was ever verified. The honest answers are lookups, and the operation that has already done them answers from its own records in a sentence.

The record is small and cheap to keep. Each aircraft's file carries its model, serial number, registration, and the declaration it stands on, with the date someone last confirmed the listing. When a declaration is rescinded or a defect notice lands, the fleet impact is a filter on that record instead of a scramble through boxes. Keeping this record isn't legally demanded of operators, which is precisely the point: the FAA obligated the manufacturers, and the operators who mirror that diligence into their own files are the ones who never have to explain an assumption.

Common mistakes in checking Declarations of Compliance

Filing one as an operator. The FAA is direct about this: owners and operators do not submit declarations, manufacturers do. If your aircraft is not on an accepted listing, the remedies are a broadcast module, a different aircraft, or the manufacturer, never a homemade filing.

Trusting the box over the list. Remote ID ready and Category 2 are marketing phrases until they trace to an accepted declaration. The public list is the arbiter, the check is free, and the result belongs in the purchase record.

Ignoring rescission risk. Acceptance is not permanent. A rescinded declaration or a defect notice can strip the compliance basis from aircraft already in service, so fleet files should note which declaration each airframe depends on and get rechecked occasionally.

Registering the wrong serial number. Standard Remote ID aircraft register with the Remote ID serial number the declaration's scheme covers. Mismatched serials quietly break the chain between the registration, the aircraft, and the declaration behind it.

Assuming the module inherits the aircraft's status. Broadcast modules carry their own declarations, separate from any aircraft listing. A retrofit fleet needs the module's listing verified and recorded per unit, exactly as it would for a standard Remote ID airframe.

FAQ

Who files an FAA Declaration of Compliance?

The manufacturer or producer of a standard Remote ID aircraft, a Remote ID broadcast module, or an aircraft labeled for operations over people categories. Operators and individual owners do not file declarations and are told not to submit them.

What does a DOC attest to?

That the product was designed and produced to meet the rule's performance requirements using an FAA accepted means of compliance, a recognized technical standard. FAA acceptance places the product on the public list operators can search.

Where do you check whether a drone is on an accepted DOC?

On the FAA's UAS Declaration of Compliance site, which hosts the public list. Search by manufacturer and model, confirm the serial number scheme matches your aircraft or module, and record the listing in the aircraft's file.

Can a Declaration of Compliance be revoked?

Yes. The FAA can rescind an accepted declaration, and Remote ID manufacturers must report defects that break compliance within 15 days of learning of them. No one may fly over people on a rescinded declaration while it stays rescinded, and a rescinded Remote ID declaration no longer meets 89.110, so operators relying on that listing need a plan.

Which categories require a declaration of compliance?

Category 2 and Category 3 operations over people, plus standard Remote ID aircraft and Remote ID broadcast modules. Category 1 needs none, and Category 4 needs an airworthiness certificate instead.

When is a declaration of compliance accepted?

When the FAA determines the manufacturer has demonstrated compliance with the rule's requirements. The FAA then notifies the manufacturer, and accepted declarations show as Accepted in the FAA's public search.

Closing thought

The Declaration of Compliance is the manufacturer's paperwork, but whether an aircraft may fly rests on it, which is why diligent operators keep their own record of it. A five minute lookup at purchase and a line in each aircraft's record convert an assumption into evidence, and evidence is what every later question, from inspectors, clients, and insurers, is really asking for.

If you are buying or fielding aircraft that must meet Remote ID and category rules, FlybyOps was built for the operational record problem at the center of regulated drone work. An equipment registry with per-airframe history, document storage with version history, and an append-only audit log are all part of how the platform keeps each aircraft's compliance basis filed beside the registration and jobs that depend on it.