RTCA規格 DO-398, Revision A, 2023: Operational Services and Environment Definition (OSED) for Unmanned Aircraft Systems Detect and Avoid Systems (DAA)

Description

INTRODUCTION
This document provides the Operational Services and Environment Description (OSED) for the RTCA Special Committee 228 (SC-228) Uncrewed Aircraft System (UAS) Detect and Avoid (DAA) Minimum Operational Performance Standards (MOPS). The purpose of this OSED is to provide a basis for assessing and establishing operational, safety, performance, and interoperability requirements for DAA systems.

Because there is no human pilot onboard an Uncrewed Aircraft (UA) looking out the window of a cockpit, a DAA system is being standardized in order to establish an acceptable alternative means of compliance with applicable standards. These include Title 14 (Aeronautics and Space) of the United States (US) Code of Federal Regulations (14 CFR), 91.111, 91.113, and 91.181, and Section 3.2 of the International Civil Aviation Organization (ICAO) Annex 2 to the Convention on International Civil Aviation. The DAA system is used to avoid nearby aircraft (hereafter referred to as “intruders”). This OSED for DAA uses the term “remote pilot” throughout to describe the person acting as the remote pilot of the UA and manipulating the flight controls. This OSED does not attempt to allocate responsibility for specific DAA tasks to individual members of the flight crew; instead, the OSED assumes a single remote pilot. Remote pilot and crew training for a specific DAA system may allocate responsibilities differently.

It is further recognized that, though designed to support remotely piloted operations, DAA systems may find use in vehicles with an onboard pilot. Use of the term “remote pilot” in this OSED should not be interpreted as excluding onboard pilot operations. It is assumed that any requirements on or expectations of a remote pilot are also applicable to an onboard pilot. This OSED does include some examples of an onboard pilot’s use of a DAA system but is not comprehensive.

This OSED describes using a MOPS-compliant DAA systems with sensors onboard and/or offboard a UA operating under Instrument Flight Rules (IFR) while transiting through Class B, Class C, Class D, Class E up to Flight Level (FL) 180, or while transitioning through Class G airspace or while conducting extended operations in Class D, E, and G airspace. DAA equipment also enables operations in the Terminal Area during approach and departure in Class C, D, E, and G airspace and off-airport locations. DAA functionality as specified in this OSED is not expected to be required for operations within Class A, Class E above FL180, or Special Use Airspace (SUA), although DAA equipment may remain on and Resolution Advisories (RAs) will be followed. This includes Traffic Alert and Collision Avoidance Version(TCAS) or Airborne Collision Avoidance System X for Uncrewed aircraft (ACAS X).

Optional DAA equipment classes enable lower Size, Weight and Power (SWaP) onboard non-cooperative sensors, Terminal Area alerting and guidance, and Ground Based (GB) surveillance equipment.

With the above mentioned introduction of DAA equipment classes and their applicability to various UAS sizes and concepts of operations (ConOps) applied, this OSED describes DAA system functions and capabilities generically without reference to specific implementations or equipment classes that are defined in the system MOPS.

Figure 1-1 depicts the document hierachy as it pertains to the items not referenced in this document. Documents following the hierachy of DO-398 can, and will, reference the contents found within this document.

This OSED for DAA does not directly apply to UAS operations under 14 CFR Part 101 or 107. UA performance is covered by RTCA DO-365.

The guiding RTCA Special Committee 228 (SC-228) Terms of Reference (TORs),¹ and this OSED focus on both airborne DAA systems with sensors onboard the UA and GB surveillance equipment.

The scenarios in this OSED expand upon the Federal Aviation Administration (FAA) Integration of Civil Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) Roadmap, 3rd Edition 2020 and provide additional operational detail necessary for DAA MOPS development.

In developing the services and environment description, the OSED for DAA identifies numbered Operational Assumptions (ASSUMP-OSED.##) and Operational Requirements (OR.##), which are necessary to bound the scope of the document. Operational Assumptions, while important, do not establish a requirement upon the system or other actors in the environment. Operational Assumptions establish the environment under which this document and the associated requirements are valid. While Operational Requirements do establish requirements, the object of the requirement will always be an actor “external to the DAA system” (e.g., requirements on training or responsibilities for remote pilots or Air Traffic Control (ATC) personnel). Operational Requirements contain the word “shall” and the requirement text and surrounding paragraphs will identify the external actor or system which is expected to meet the intent of that requirement. DAA System Requirements are developed in the DAA MOPS; Surveillance System Requirements are developed separately in their respective MOPS (e.g. airborne radar requirements are developed in the Air-to-Air radar MOPS).

The OSED describes a DAA system built and integrated with other ground and avionic systems as proposed in Operational Views depicted in Section 2 using DAA architectures developed in Section 3. The OSED for DAA references MOPS, MASPS, and other standards where specific functionallity is required to achieve the envisioned operational capability. The referenced standards contain the system, subsystem, and interface requirements which achieve the capabilities developed in this OSED for DAA.

¹ Terms of Reference for RTCA Special Committee 228 Minimum Performance Standards for Uncrewed Aircraft Systems Rev 10, 11 June 2020