scope:

Overview and Scope

Anything involved with spectrum use by UAS of any type for any non-payload purpose is within the scope of this Guidance. Use of spectrum for payload is out of the scope of this Guidance.

UAS require access to spectrum for: functions to manage the flight of the UA (aviate, navigate, telecommand, telemetry, management, etc. - so-called Control and Non- Payload Communications (CNPC)); to support navigation and surveillance; and communications related to Air Traffic Management (ATM) services.

The need for spectrum access depends on the type of the UAS and the type of operation that it is doing. This is accordingly the first main part (CHAPTER 2), outlined in sub-section 1.4.2.

Safety, security and compliance with performance requirements are the most important considerations once the spectrum requirements have been identified. These are addressed in CHAPTER 3 and outlined in 1.4.3.

The remaining Chapters provide guidance on more detailed technical considerations starting with the regulatory aspects of spectrum management (CHAPTER 4, outlined in 1.4.4), and ending with the potential impact of Information and Communication Technology (ICT) system implementation (CHAPTER 6, summarised in 1.4.6).

Note: this document does not anticipate, or speculate about, the use of spectrum by services related to UAS C2 that will be introduced in the future. For example, remote identification or geo-awareness have become topical in the context of UAS Traffic Management (UTM) but their technical specification is not yet mature enough to be able to identify the spectrum that they will require.