ASTM F3586-22

Standard Practice for Remote ID Means of Compliance to Federal Aviation Administration Regulation 14 CFR Part 89<refdocr rid="r00001"/>

SIGNIFICANCE AND USE
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.
SCOPE
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:    
Title  
Section  
Scope  
1  
Referenced Documents  
2  
Significance and Use  
3  
Subset of Options in the F3411 Specification Considered  
4  
Requirements and Exceptions from the F3411 Specification  
5  
Alternative Applications of Specification F3411 to Meet Part 89
Requirements  
6  
MOC Requirements Not Covered by the Practice  
7  
Test Methods  
8  
Precision and Bias  
9  
Satisfaction of Rule Requirements  
10  
Keywords  
11  
ANNEX A1—Simulation Option for Accuracy Testing  
Annex A1  
APPENDIX X1—External Device for GCS Location Source Rationale  
Appendix X1  
APPENDIX X2—Power Level Rationale  
Appendix X2  
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.

General Information

• Status: Published
• Publication Date: 31-May-2022
• ICS: 03.220.50 - Air transport
• ICS: 49.020 - Aircraft and space vehicles in general
• Technical Committee: F38 - Unmanned Aircraft Systems
• Drafting Committee: F38.02 - Flight Operations

Overview

ASTM F3586-22 is a standard practice established by ASTM International, providing a Means of Compliance (MOC) for Remote Identification (Remote ID) systems required under the Federal Aviation Administration (FAA) regulation 14 CFR Part 89. This standard is designed to help Unmanned Aircraft Systems (UAS) and broadcast module manufacturers align with regulatory requirements for Remote ID, ensuring that their products meet all necessary FAA compliance for safe and legal operation in U.S. airspace.

ASTM F3586-22 serves as an overlay to the ASTM F3411 Specification for Remote ID and Tracking, identifying mandatory requirements, substituting values as required, and imposing additional criteria to guide manufacturers toward full Part 89 compliance. This practice covers both Standard Remote ID UAS and Remote ID Broadcast Modules, providing clarity on design, documentation, testing, and user instructions. The intent is to facilitate the process for submitting a Declaration of Compliance (DOC) and to clarify the expectations for aircraft operating under this MOC.

Key Topics

• Means of Compliance (MOC): Guidance for manufacturers to produce a compliant Remote ID System, including necessary documentation and testing.
• Broadcast Methods: Focus on Bluetooth Long Range (5) and Wi-Fi Beacon to meet the broadcast, error correction, and range requirements specified in Part 89.
• Overlay to ASTM F3411: Identifies and requires certain options from F3411, overrides others, and adds requirements for minimal testing and user instructions.
• Testing Procedures: Comprehensive test methods, including pre-flight self-testing, continuous monitoring, and field-testing of message elements, accuracy, and emergency indicators.
• Tamper Resistance and Interference: Requirements ensuring the Remote ID equipment cannot be easily tampered with, and does not interfere with or is not interfered by other on-board systems.
• User Documentation: Clear guidance on installation, operational limitations, and monitoring for Broadcast Module and Standard Remote ID UAS products.
• Data Synchronization and Error Correction: Alignment with FAA rules ensuring all required messages are accurately and consistently broadcast within mandated time intervals.
• Regulatory Alignment: Developed in accordance with international standardization principles and the World Trade Organization’s Technical Barriers to Trade (TBT) guidelines.

Applications

ASTM F3586-22 is applicable for:

• UAS Manufacturers: Assisting in the development of drones and broadcast modules that are compliant with FAA’s Remote ID requirements.
• Broadcast Module Suppliers: Ensuring stand-alone modules meet the technical and operational criteria to be legally used with non-compliant aircraft.
• FAA Compliance: Providing a clear, standardized path for submitting a Declaration of Compliance, easing regulatory approval processes.
• Integration with Flight Operations: Supporting UAS operators in understanding installation, maintenance, and operational requirements for Remote ID, including emergency status reporting and interference prevention.
• Testing and Certification Bodies: Offering structured test procedures for validating product compliance and performance against FAA and ASTM specifications.

Related Standards

• ASTM F3411 – Standard Specification for Remote ID and Tracking
• ANSI/CTA-2063-A – Small Unmanned Aerial Systems Serial Numbers
• 47 CFR Part 15 – FCC requirements for Radio Frequency Devices
• FAA Advisory Circular AC 89-2 – Guidance on Declaration of Compliance for Remote Identification
• TSO-C199 – Technical Standard Order for Traffic Awareness Beacon System (TABS)
• WGS-84 – World Geodetic System standard for geographic data

Summary

By adhering to ASTM F3586-22, manufacturers and suppliers of UAS and Remote ID Broadcast Modules can demonstrate clear compliance with FAA’s 14 CFR Part 89 Remote ID regulations. This standard offers practical, tested guidance on the implementation, testing, and documentation of compliant systems, thereby supporting safer skies, streamlined regulatory approvals, and trusted integration of unmanned aircraft into the national airspace.

Keywords: ASTM F3586-22, Remote ID compliance, FAA 14 CFR Part 89, UAS, drone regulations, ASTM F3411, broadcast module, Declaration of Compliance, drone identification standard, aviation safety, drone manufacturer compliance.

Standards Content (Sample)

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.
Designation: F3586 − 22
Standard Practice for
Remote ID Means of Compliance to Federal Aviation
Administration Regulation 14 CFR Part 89
This standard is issued under the fixed designation F3586; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
1. Scope
Precision and Bias 9
Satisfaction of Rule Requirements 10
1.1 This practice provides a Means of Compliance (MOC)
Keywords 11
that gives sufficient clarity to the Unmanned Aircraft System ANNEX A1—Simulation Option for Accuracy Testing Annex A1
APPENDIX X1—External Device for GCS Location Source Ra- Appendix X1
(UAS) or Broadcast Module manufacturers to produce a
tionale
compliant Remote ID (RID) System (RIDS) such that submit-
APPENDIX X2—Power Level Rationale Appendix X2
ting a Declaration of Compliance (DOC) to this MOC will
1.6 This standard does not purport to address all of the
satisfy the requirements of the FederalAviationAdministration
safety concerns, if any, associated with its use. It is the
(FAA) 14 CFR Part 89 (Part 89) rule. This practice also
responsibility of the user of this standard to establish appro-
explains what to expect from aircraft operating in compliance
priate safety, health, and environmental practices and deter-
to this MOC.
mine the applicability of regulatory limitations prior to use.
1.2 The FAA provided three options to comply with the
1.7 This international standard was developed in accor-
Remote ID regulations: Standard Remote ID UAS, Remote ID
dance with internationally recognized principles on standard-
Broadcast Modules, and FAA-recognized identification areas
ization established in the Decision on Principles for the
(FRIAs).ThescopeofthisMOCistocoverbothStandardRID
Development of International Standards, Guides and Recom-
and RID Broadcast Modules.
mendations issued by the World Trade Organization Technical
1.3 The FRIA portion of the rule is out of scope since it
Barriers to Trade (TBT) Committee.
provides a means to avoid the technical RID requirements by
operating within administrative boundaries.
2. Referenced Documents
1.4 Both SI and non-SI units are used in this document.
2.1 ASTM Standard:
Since this is an aviation standard and it addresses FAA rules,
F3411 Specification for Remote ID and Tracking
some units are used in preference of being consistent with
2.2 Other Documents:
industry and regulatory norms.
14 CFR Part 89 Remote Identification of Unmanned Air-
1.5 Table of Contents:
craft
Title Section
47 CFR Part 15 Radio Frequency Devices
Scope 1
Referenced Documents 2 Advisory CircularAC 89-2 Declaration of Compliance Pro-
Significance and Use 3
cess for Remote Identification of Unmanned Aircraft
Subset of Options in the F3411 Specification Considered 4
ANSI/CTA-2063-A Small Unmanned Aerial Systems Serial
Requirements and Exceptions from the F3411 Specification 5
Alternative Applications of Specification F3411 to Meet Part 89 6
Numbers
Requirements
TechnicalStandardOrderTSO-C199 TrafficAwarenessBea-
MOC Requirements Not Covered by the Practice 7
con System (TABS)
Test Methods 8
1 4
This practice is under the jurisdiction ofASTM Committee F38 on Unmanned For referenced ASTM standards, visit the ASTM website, www.astm.org, or
Aircraft Systems and is the direct responsibility of Subcommittee F38.02 on Flight contact ASTM Customer Service at [e-mail]. For Annual Book of ASTM
Operations. Standards volume information, refer to the standard’s Document Summary page on
Current edition approved June 1, 2022. Published July 2022. DOI: 10.1520/ the ASTM website.
F3586-22. Available from https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/
See FAA Advisory Circular 89-2, https://www.faa.gov/documentLibrary/ part-15.
media/Advisory_Circular/AC_89-2.pdf. Available from Consumer Technology Association, 1919 S. Eads Street,
Available from https://www.federalregister.gov/documents/2021/01/15/2020- Arlington, VA 22202, https://www.cta.tech/.
28948/remote-identification-of-unmanned-aircraft. Portions of Part 89 are repro- Available from https://rgl.faa.gov/Regulatory_and_Guidance_Library/
duced (in italics) in Section 7 and Appendix X1. rgTSO.nsf/0/1600df588a6f53ae86257d710070d105/$FILE/TSO-C199.pdf.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
F3586 − 22
WGS-84 World Geodetic System 5.1.2 Either (or both) of the following:
5.1.2.1 If Implementing Bluetooth, all of Subsection 5.4.6
3. Significance and Use
and all of Subsection 5.4.7 (includes both Bluetooth 5 and
3.1 The general approach to this practice is to serve as an Bluetooth 4).
“overlay” of requirements to the ASTM F3411-22a Standard
5.1.2.2 If Implementing Wi-Fi Beacon, all of Subsection
Specification for Remote ID and Tracking by identifying
5.4.9.
mandatory portions, substituting values as needed, overriding
5.1.3 The following FAA requirements take precedence
items that may be optional, and providing additional require-
over certain requirements, options, and values in the F3411
mentsthatarebeyondthescopeofSpecificationF3411,yetare
Specification.
necessary to provide proper guidance to meet the requirements
5.1.3.1 Specification F3411, Subsection 5.4.3, only Wave
set forth in Part 89.
Law “Type 1” in Tables A3.2 and A3.3 shall apply.
3.2 Furthermore, this practice provides additional details on
5.1.3.2 Specification F3411, Subsection 5.4.5.6, for Stan-
minimal testing requirements for those submitting a DOC
dard RID, the Basic ID message shall include either:
based on this MOC.
(1) The Unmanned Aircraft (UA) serial number in the
format required by the F3411 Specification (in the format of
4. Subset of Options in the F3411 Specification Consid-
ANSI/CTA-2063-A); or
ered
(2) A unique Session ID (UTM Assigned universally
4.1 The F3411 Specification provides four broadcast meth-
unique identifier (UUID) or Specific Session ID) as described
ods and one network method to implement RID:
in Specification F3411, Table 1 and Subsection 5.4.5.6, which
4.1.1 Bluetooth Legacy Advertising (also known as the
canberesolvedtothecorrespondingserialnumber,withaccess
“Bluetooth 4” method): Specification F3411, Subsection 5.4.6.
limited to authorized parties only, through a system and
4.1.2 Bluetooth5LongRange+ExtendedAdvertising(also
process accepted by the FAA.
known as the “Bluetooth 5” method), Specification F3411,
For Broadcast Modules, the Basic ID message shall be the
Subsection 5.4.7: this includes the requirement to implement
broadcast module’s serial number in the format required by the
Bluetooth Legacy, Specification F3411, Subsection 5.4.6.
F3411 Specification (which requires the format ofANSI/CTA-
4.1.3 Wi-Fi Neighbor Awareness Networking (NAN):
2063-A).
Specification F3411, Subsection 5.4.8.
5.1.3.3 Specification F3411, Subsection 5.4.5.18, The Sys-
4.1.4 Wi-Fi Beacon: Specification F3411, Subsection 5.4.9.
tem Message is required.
4.1.5 Network RID with Service Suppliers, Display
5.1.3.4 In the System Message, the following fields are
Providers, and Discovery and Synchronization Service (DSS):
required (the remaining fields in the System Message can be
Specification F3411, Subsection 5.5.
filled with default values when not used):
4.2 To meet the “broadcast,” “error correction,” and “maxi-
(1) Operator Location/Altitude Type
mumrange”requirementsofPart89,andtoconvergeonbetter
(2) Operator Latitude
interoperability, this MOC requires broadcasting using meth-
(3) Operator Longitude
ods 4.1.2 or 4.1.4.
(4) Operator Altitude
(5) Timestamp
5. Requirements and Exceptions from the F3411 Specifi-
5.1.3.5 For Standard Remote ID, the Operational Status
cation
field (Specification F3411, Subsection 5.4.5.7) in the Location/
5.1 The requirements in this MOC are design requirements
Vector Message is required.
of UAS Remote ID. They are not operational requirements.
5.1.3.6 For Standard Remote ID, the Operator Location/
Although a UAS may be designed to these requirements, there
Altitude Type (Specification F3411, Subsections
may be times when, operationally, certain information cannot
5.4.5.18–5.4.5.19) in the System Message shall be either “1.
perform to the intended requirements. For example, Global
Dynamic” and use a system that accurately (as described in
Navigation Satellite Systems (GNSS) may have limited recep-
MOC 7.1) reports the location of the ground control station
tion in certain environments (such as indoors). These require-
(GCS); or “2. Fixed” where the location is automatically
ments do not seek to remedy those conditions. Both Standard
programmed into the UAS based on the actual location of the
RID and Broadcast Modules shall implement all mandatory
GCS within the accuracy requirements of Part 89 (as described
requirements in the following sections of the F3411 Specifica-
in MOC 7.1). The GCS location must correspond with the
tion:
location of the operator.
5.1.1 Subsections 5.1 through 5.4.5.
NOTE 1—UAS designers and producers may determine which part or
element of the control station represents the location to be incorporated
Available from International CivilAviation Organization (ICAO), 999 Robert-
into “System Message” if it corresponds to the actual operator’s location.
Bourassa Boulevard, Montréal, Quebec, Canada H3C 5H7, https://www.icao.int/
5.1.3.7 For Broadcast Modules, the Operator Location/
safety/pbn/Documentation/EUROCONTROL/
Eurocontrol%20WGS%2084%20Implementation%20Manual.pdf.
Altitude Type (F3411, Subsection 5.4.5.18) in the System
Used throughout the practice, Bluetooth is a registered trademark of Bluetooth
Message shall be “0. Take Off.” The source of the “operator
SIG, Inc., 5209 Lake Washington Blvd. NE, Suite 350, Kirkland, WA 98033.
location” shall be based on the location of take off within the
Used throughout the practice, Wi-Fi is a registered trademark of Wi-Fi
Alliance, 10900-B Stonelake Boulevard, Suite 126, Austin, TX 78759. accuracy requirements of Part 89 (as described in 7.1).
F3586 − 22
5.1.3.8 The following value in Specification F3411, Table (1) Aircraft—The aircraft is designed with an integrated
A3.1, shall be overridden to the following: GNSS system that, at a minimum, uses Global Positioning
BcMinStaticRefreshRate = 1 Second. This shall be the mini- System (GPS) with Satellite-based Augmentation System
mum period within which all required data elements are (SBAS) (WideAreaAugmentation System (WAAS)) augmen-
regularly broadcast. tation as its location source.
5.1.3.9 Although the term “Geometric Altitude” is used in (2) GCS—The GCS is designed with an integrated GNSS
the rule, the F3411 Specification uses the term “Geodetic system that, at a minimum, uses GPS with SBAS (WAAS)
Altitude” based on the WGS 84 Height Above Ellipsoid augmentation as its location source.
standard, which is a form of Geometric Altitude and thus
7.1.1.2 Design specification (GCS Only)—GCS uses an
satisfies the requirement of this term within Part 89.
external device with either of the following characteristics as
5.1.4 For physical add-on Remote ID Modules, the user
its location source:
instructions shall include the following: (1) External device uses GPS with SBAS (WAAS), or
5.1.4.1 Instructions on how to install the module on an
(2) Federal Communications Commission (FCC)-certified
aircraft in a way that ensures the location source hardware can external personal wireless device with integrated GNSS (See
acquire the aircraft location and ground-based receivers are
AppendixX1forjustification).TheUASuserinstructionsshall
able to receive the RID broadcasts at an optimal range in any
minimally include the following text:
direction.
“The [device description] connected to the ground con-
5.1.4.2 Limitations that may prevent the module from:
trol station must minimally be one of the following:
(1) Determining the aircraft location.
1) FCC Certified personal wireless device that uses GPS
(2) Transmitting in an omni-directional manner.
with SBAS (WAAS) for location services; or
2) FCC Certified personal wireless device with integrated
6. Alternative Applications of Specification F3411 to
GNSS.
Meet Part 89 Requirements
Also, the [device description] must be operated in a way
that does not interfere with the location reported and its
6.1 Message Synchronization:
correlation to the operator location.”
6.1.1 The rule also requires the following:
89.310(b) Time mark. The time mark message element must
NOTE 2—Example “device description”: “Cell Phone or Tablet”.
be synchronized with all other remote identification message
7.1.1.3 Test demonstration (aircraft or GCS):
elements.
(1) Aircraft—If the aircraft does not satisfy method 7.1.1.1
6.1.2 The F3411 Specification presents the required data
requirements, then the test demonstration method outlined in
elements spread across three messages (1. Basic ID, 2.
8.9.3 or 8.9.4 shall be used to satisfy the location accuracy
Location/Vector, 3. System). The Timestamp shall be incorpo-
requirements.
rated into the System message as described in Specification
(2) GCS—If the GCS does not satisfy method 7.1.1.1 or
F3411, Table 11.
7.1.1.2 requirements, then the test demonstration method
6.1.3 When the receiver receives position updates, that data
outlined in 8.9.3 or 8.9.4 shall be used to satisfy the location
is merged with the most recently received static data to present
accuracy requirements. If the GCS relies on a separate device
a synchronized data element record with the time mark being
as its location source, a representative device shall be used in
setbythemostrecentaircraftpositionupdate.Additionally,the
the testing.
requirement in MOC 5.1.3.8, following Part 89, effectively
7.1.2 Broadcast Modules:
mandates that all three required messages are transmitted
7.1.2.1 Broadcast modules shall use the take-off location to
within 1 second, with this method resulting in the system
represent the location (horizontally and vertically) of the
timestamp being associated with all required data elements is
operator.
never older than 1 second. Therefore, this MOC submits that
7.1.2.2 The same requirements in 7.1.1, methods 7.1.1.1 or
the Specification F3411 implementation ofTimestamp satisfies
7.1.1.3(1), shall be used to satisfy the aircraft and take-off
the intent of Part 89.305(b).
location accuracy requirements.
6.2 Error Correction:
6.2.1 By requiring either the Bluetooth 5 Long Range or 7.2 Pre-flight Self-Test (PFST):
Wi-Fi in MOC 5.1.2, forward error correction (FEC) is 7.2.1 Part 89 requires:
inherently required as it is built into both transport protocols.
89.310(c)(1) [standard] Prior to take off, the unmanned
Therefore, this MOC satisfies the “error correction” require-
aircraft must automatically test the remote identification func-
ment of Part 89.
tionality and notify the person manipulating the flight controls
of the unmanned aircraft system of the result of the test.
7. MOC Requirements Not Covered by the Practice
89.320(c)(1) [broadcast modules] Prior to take off, the
remote identification broadcast module must automatically test
7.1 Location Accuracy Requirements of Broadcasted Loca-
the remote identification functionality and notify the person
tion Information:
manipulating the flight controls of the unmanned aircraft
7.1.1 Standard Remote ID—Standard Remote ID products
system of the result of the test.
(both aircraft and GCS) shall meet the Part 89 accuracy
requirements through either of the following three methods: 7.2.2 To meet this requirement, the RID system, whether
7.1.1.1 Design specification (aircraft or GCS): integrated into the UAS or as a separate broadcast module,
F3586 − 22
shall automatically initiate a PFST, and the user instructions of 7.4.1 Part 89 Requires:
the product shall document the PFST usage and limitations. It 89.310(c)(2): The unmanned aircraft must not be able to
is not necessary for the UAS to perform the PFST again prior
take off if the remote identification equipment is not functional.
to power off. 7.4.2 For standard RID systems, after power on, until the
7.2.3 The RID system or UAS shall have a documented PFSTpasses, and all required RID message elements are being
unique indicator, either visual (light emissive), audible, or transmitted, taking flight shall be prevented by the control
using some other user interface that informs the operator of the system of the UAS.
result of the PFST. The documentation shall include how to
NOTE 6—As stated in Note 3, the PFST does not require establishing a
interpret a pass or fail of the PFST. The components and
locationfixorspecificaccuracytopass.Undercertainconditions(indoors,
functions tested shall include the following:
or GNSS “canyon”), this may not be possible.
7.2.3.1 Locationsourcehardwareandsoftwarearefunction-
7.5 Tamper Resistance:
ing properly, and the required parameter values are set.
7.5.1 Part 89 Requires:
7.2.3.2 Transmitter radio hardware and software are func-
89.310(d) [standard]: The unmanned aircraft must be de-
tioning properly, transmitting and the required parameter
signed and produced in a way that reduces the ability of a
values are set.
person to tamper with the remote identification functionality.
89.320(d) [broadcast modules]: The remote identification
NOTE 3—Although the aircraft and GCS must be designed to meet
certain accuracy requirements, the PFST of these specific hardware/ broadcastmodulemustbedesignedandproducedinawaythat
software functions does not require establishing a location fix or specific
reduces the ability of a person to tamper with the remote
accuracy.
identification functionality.
7.3 Monitoring:
7.5.2 The Remote ID system shall protect Part 89 required
7.3.1 Part 89 Requires:
broadcasted message elements from being altered through the
89.310(c)(3) [standard]: The unmanned aircraft must con-
end-user interface(s) of the system by masking the items from
tinuously monitor the remote identification functionality from
userinput.Thefollowingmessageelementsareanexceptionto
take off to shutdown and must provide notification of malfunc-
this requirement:
tion or failure to the person manipulating the flight controls of
7.5.2.1 Emergency Status Indicator.
the unmanned aircraft system.
7.5.2.2 ID mode selection of Serial Number or Session ID.
89.310(c)(3) [broadcast modules]: The remote identification
NOTE 7—End-user interfaces include the following: External Buttons,
broadcast module must continuously monitor the remote iden-
screens, add-on devices (such as cell phones/apps), external wiring
tification functionality from take off to shutdown and must
interfaces + supporting software.
provide notification of malfunction or failure to the person
7.5.3 For Standard RID, as required in 7.2.2, the RID
manipulating the flight controls of the unmanned aircraft
system must perform a PFST. If the aircraft RID location
system.
source hardware and software or RID transmit hardware and
7.3.2 To meet this requirement, the RID system, whether
software are detected not functional as described in 7.2.3, due
integratedintotheUASorimplementedasaseparatebroadcast
to tampering or other failure, then taking flight shall be
module, shall have a documented indicator that communicates
prevented by the control system. This take-off prevention
a malfunction or failure of the RID system to the operator.The
feature shall be protected from being altered through the
functions monitored shall include the following:
end-user interface(s) of the system.
7.3.2.1 RID-required data source hardware and software are
7.6 Interference Considerations:
functioning properly.
7.6.1 Part 89 Requires:
7.3.2.2 Transmitter radio hardware and software are func-
89.310(f) Interference considerations. The remote identifica-
tioning properly.
tion equipment must not interfere with other systems or
NOTE 4—Monitoring these hardware/software functions does not re-
equipment installed on the unmanned aircraft, and other
quire establishing a location fix or specific accuracy, nor does it (neces-
systems or equipment installed on the unmanned aircraft must
sarily) require a “closed-loop” RID receiver function.
not interfere with the remote identification equipment.
7.3.3 The indicator could be displayed in the GCS, an RID
7.6.2 The RID system shall not degrade the flight-critical
receiver, mobile application, or other means with software
radio communications to the extent where the aircraft cannot
logic to detect a failure and inform the operator.
be safely controlled.
7.3.4 The monitoring system shall start prior to take off and
7.6.3 The RID system shall not degrade the other Radio
continue to run at least until shutdown.
Frequency (RF) sensitive systems, for example: GNSS such
that the data elements transmitted are unable to meet the
NOTE 5—Shutdown does not necessarily imply power down. Shutdown
will be aircraft and operator specific, but generally corresponds to a
performance and periodicity requirements of this MOC.
situation where the UAS is not available for flight.
7.6.4 Other radio systems on the aircraft shall not interfere
with the Remote ID equipment in a way that prevents Remote
7.3.5 Documentation of the functionality, possible software
installation, and usage instructions for this monitoring system, ID from functioning as intended.
shall be provided together with the RID system.
7.7 Emergency Status Indicator:
7.4 Take-off Prevention When Not Broadcasting RID (Stan- 7.7.1 ForstandardRID,theemergencystatusindicatorshall
dard RID Only): be satisfied using either (or both) of the following methods:
F3586 − 22
TABLE 1 System Properties
7.7.1.1 The system shall provide a mechanism for the
operatortomanuallyasserttheemergencystatusanddocument Item Value Notes
Product Make
this function in the user instructions. If a manual assert
Product Model #
mechanism is used, it shall be available to use at the operator’s
Product RID Serial #
discretion. Software Stack Version
Hardware Version
7.7.1.2 The system shall automatically assert the emergency
Broadcast Method(s) “Bluetooth” or
status at least under the two following conditions:
“Wi-Fi,” or both
Broadcast Rate x Hz How often are packets
(1) UAS unable to recover from an uncontrolled descent.
sent
(2) UAS unable to recover from loss of control of the flight
Msg Update Rate x Hz How often are messages
trajectory.
updated
RID Monitor Indication GCS indicator, App
7.7.2 In the event of an emergency status assertion, the RID
Method (Name), Other (describe)
system shall transmit the Operational Status of “Emergency”
Implemented Optional Y/N
Emergency Status
(3) as described in Specification F3411,Tables 1, 2, and 6.The
Description
RID system may optionally fill in the “Self ID” message
(Specification F3411, Subsections 5.4.5.16–5.4.5.17) with a
short description of the emergency condition. When imple-
menting the Self ID message for this purpose, it shall set the
8. Test Methods
Description Type to “Emergency Description” (1).
8.1 Scope—This section includes testing that shall be per-
7.8 Designed to Maximize Range—The rule requirement,
formed to declare a product design compliant to this MOC. It
Part89.310(g)(2),“…designedtomaximizetherangeatwhich
is not intended to be comprehensive of all testing that may be
the broadcast can be received…” is met in the F3411 Specifi-
required for a product.
cation by balancing the general available electronics that can
8.2 Significance and Use—Thistestseriesservesasadesign
be used for this purpose and prescribing the minimum power,
validation of a compliant make and model. In addition to
periodicity, radiation pattern, and technique.
meeting all requirements in Sections 5, 6, and 7 of this MOC,
7.8.1 Power:
all items in this section shall achieve a result of “PASS” for a
7.8.1.1 The solution (whether standard RID or broadcast
Standard RID UAS or RID Broadcast Module (as appropriate)
module) shall conform to the requirements specified in Speci-
to be compliant to this MOC. (Portions sourced from ASD-
fication F3411, Subsection 5.4.3 (which specifies power and
STAN. )
radiation pattern), and the associated values in Tables A3.1,
8.3 Hazards:
A3.2,A3.3 (Wave LawType 1). See rationale in Appendix X2.
8.3.1 Ensure that UAS are configured as to not cause harm
7.8.1.2 This requirement reflects the capabilities of com-
to individual(s) conducting the test or third parties.
monly available commodity radio parts.
8.3.2 UAS that are powered or operational can present
7.8.1.3 Although the Bluetooth power level requirements
hazards. Ensure that propellers are removed or caged during
are lower than Wi-Fi, to implement the Bluetooth solution,
laboratory testing.
both Long Range and Legacy advertising modes shall be
8.3.3 Field testing of UAS can present hazards. Take appro-
implemented. The Long Range mode transmits at a much
priate safety precautions when field testing UAS.
lower rate (than Legacy advertising mode—125 kbps rather
8.3.4 When testing UAS with power plants or lithium
than 1 Mbps) and uses FEC, which both will serve to extend
batteries, or both, an appropriate fire extinguisher for each
the range. Requiring Legacy mode enhances compatibility
application should be within reach. Participants should be
across nearly all handheld devices.
made aware of the hazards of lithium batteries or flammable
7.8.2 Periodicity—The rule requires all required data ele-
fuels, or both, and which fire extinguishers are appropriate for
ments to be transmitted at least once per second. Therefore,
lithium or flammable fuel-based fires, or both.
when sending the data across multiple messages, all messages
8.4 Procedure—A unit representative of the make and
containing the Part 89 required data elements (Basic ID,
model that will be submitted in the DOC shall be used in all
Location/Vector, System messages) shall be sent at least every
applicable tests in this section. When performing all the tests
1 second.
required in Section 8 and assessing that all requirements stated
7.8.3 Radiation Pattern—The F3411 Specification, Subsec-
in this MOC are met, Table 3 shall be filled in and recorded as
tion 5.4.3, requires the minimum average EIRP power and a
a checklist and shall be archived as a part of the “supporting
maximum “peak to average” around the horizontal plane. The
data” to show compliance to this MOC.
most common implementation of this requirement will likely
8.5 Required System Documentation for Performing the
result in a horizontal toroid (donut) shape radiation pattern that
Test—Table 1 shall be filled and maintained in compliance
optimizes for horizontal range.
records in support of the testing process.
7.8.4 Technique—Asspecifiedin5.1ofthisMOC,requiring
either Wi-Fi or Bluetooth Long Range (+ Bluetooth Legacy),
given the constraints of handheld device compatibilities, al-
Copyright CEN, reproduced with permission;ASD-STAN prEN 4709-002 P1,
lowing only this subset contributes toward “designing for
Aerospace series - Unmanned Aircraft Systems - Part 002: Direct Remote
maximum range.” Identification, http://asd-stan.org/downloads/asd-stan-pren-4709-002-p1/.
F3586 − 22
TABLE 2 Received Data Elements
8.6 Broadcast Protocol, Message Elements, and Periodicity
Testing: Field Received/
Correct
8.6.1 General Test Setup—The test requires a computer,
1. Properly assigned serial number or session ID, or
laptop, or other device with packet capturing software installed
if broadcast module, the properly assigned serial
and a wireless network device with a “sniffing” function number of the broadcast module
2. Latitude and longitude of the GCS, or if broadcast
capable of capturing and logging the underlying raw data and
module, the take-off position of the UA
timing information (at least to 10 ms accuracy) transmitted by
3. Geometric altitude of the GCS, or if broadcast
module, the take-off altitude of the UA
the UA or broadcast module. See Fig. 1.
4. Latitude and longitude of the UA
8.6.2 Measurement Procedure:
5. Geometric altitude of the UA
8.6.2.1 Step 1—Set the UA or Broadcast Module to power
6. Velocity of the UA expressed as:
a. Track direction
on, and to the point where the RID System (RIDS) is in its
b. (Horizontal) speed
nominal state of periodically broadcasting data.
c. Vertical speed
8.6.2.2 Step 2—Start the packet capturing software to cap-
7. Coordinated Universal Time (UTC) time of
applicability of the position data
ture at least 10 seconds of broadcast data.
8. Operational (or emergency) status of the UA
8.6.2.3 Step 3—Use the packet capture software to filter out
(standard RID only)
the required data, check whether the captured packets contain
periodic RID-required data (Sections 5.1.3.2 – 5.1.3.9)as
appropriate for Standard Remote ID or broadcast modules.
(1) (Broadcast Modules only) Follow the user instructions
Calculate the interval between multiple frames by taking the
to install the module on the UA and turn on the module.
difference of the received timestamps logged in the sniffing
(2) Follow the UAS user instructions on the power-on
software.Byanalyzingthemessagetypescarriedintheframes,
procedure and wait the required amount of time or the
the transmitting intervals of the messages can be calculated.
indication of when the system is ready to take flig
...