Document Center is acquired by Nimonik

1.1 This practice provides a Means of Compliance (MOC) that gives sufficient clarity to the Unmanned Aircraft System (UAS) or Broadcast Module manufacturers to produce a compliant Remote ID (RID) System (RIDS) such that submitting a Declaration of Compliance2 (DOC) to this MOC will satisfy the requirements of the Federal Aviation Administration (FAA) 14 CFR Part 89 (Part 89) rule.3 This practice also explains what to expect from aircraft operating in compliance to this MOC.

1.2 The FAA provided three options to comply with the Remote ID regulations: Standard Remote ID UAS, Remote ID Broadcast Modules, and FAA-recognized identification areas (FRIAs). The scope of this MOC is to cover both Standard RID and RID Broadcast Modules.

1.3 The FRIA portion of the rule is out of scope since it provides a means to avoid the technical RID requirements by operating within administrative boundaries.

1.4 Both SI and non-SI units are used in this document. Since this is an aviation standard and it addresses FAA rules, some units are used in preference of being consistent with industry and regulatory norms.

1.5 Table of Contents:

1.6 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.

1.7 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

3.1 The general approach to this practice is to serve as an “overlay” of requirements to the ASTM F3411-22a Standard Specification for Remote ID and Tracking by identifying mandatory portions, substituting values as needed, overriding items that may be optional, and providing additional requirements that are beyond the scope of Specification F3411, yet are necessary to provide proper guidance to meet the requirements set forth in Part 89.

3.2 Furthermore, this practice provides additional details on minimal testing requirements for those submitting a DOC based on this MOC.