How we label compliance

A part gets an NDAA Compliant badge when its maker or a store selling it says so publicly. Parts without a statement simply carry no badge.

Compliant

The manufacturer or a store selling the part publicly states it is compliant under that framework (for example "NDAA compliant"), and the statement is linked as its source. A statement counts only for the framework it names: an NDAA statement is not a Blue UAS listing. A covered company (on the FCC Covered List, or domiciled in a covered country) fails regardless of any statement.

No compliance statement found

Neither the manufacturer nor a store we list states compliance. Never counted as a pass.

Build evidence

A build reads "every regulated part stated compliant" only when every part in a regulated category has a compliance statement under NDAA Section 848. Blue UAS Framework is shown as eligibility, never as a pass for a whole aircraft.

Community notes

Descriptions, comments and suggestions are written by community members. They are labelled as community notes and never change a part's evidence. A suggestion changes the catalog only after staff check its source.

Estimates

Weight, thrust-to-weight and hover time are calculated from published part specs and labelled as estimates. Nothing on a build page is a flight test.