scope:

SCOPE OF THE DOCUMENT

This document describes the DAA function necessary to support the Remote Pilot (RP) to operate the Remotely Piloted Aircraft (RPA) in airspace A-C under IFR enroute according to the OSED [Ref 1]. Note that the OSED defines a Traffic Awareness and Collision Avoidance System (TAACAS), which in this MASPS is denoted DAA [Traf], and the two should be considered as the same.

It is not intended that anything written here precludes the use of systems with more limited capability should such systems be approved by the appropriate regulators. The guidance in this document may apply to such systems provided it is interpreted appropriately in the light of their limitations. For example, a Collision Avoidance (CA) function with no ability to track non-cooperative traffic might prove acceptable in certain airspace environments (e.g., low density airspace or airspace where transponder equipage is mandatory).

Ground based DAA is not covered. Ground based sensing, as long as surveillance data is processed in the RPA, is not excluded, but specific requirements of the ground based sensors are not explicitly derived.

Remain Well Clear (RWC) will eventually be required in all airspaces, but ED-238 [Ref 1], upon which this document is based explicitly excludes it. The current understanding is that both CA and RWC are necessary capabilities in all airspace classes.