The scenario which is intended to be used as basis for the definition of the scenarios to be addressed within RAID project is derived from the ICONUS study (Initial CON OPS for UAS in SESAR – the study on the integration of UAS in non-segregated airspace [3]). Specifically the project refers to the ICONUS scenario that foresees the short term integration of RPAS in the SESAR context.

This scenario is adapted to the requirements and assumptions of the RAID project considering the specific characteristics of the RPAS under consideration, type of mission envisaged under relevant operational conditions.

  • RPAS characteristics:
    • Vehicle category Remotely Piloted Turboprop aircraft
    • Working Altitude: Medium altitude: max 3000ft (~1000m)
    • RPAS category: Medium altitude 1000m; Short range ~ 10km
    • Weight category: >250kg
    • Altitude and endurance: medium altitude, medium endurance
  • Type of mission:

The Remote Piloted Aircraft will perform patrolling activities in the area of predefined dimensions. The trajectory of the flight will be a point to point route between take-off and the mission area. Within the mission area the RPA will follow a systematic target seeking pattern until the target is identified. The RPA follows the target for the period of time that is previously defined after which it will proceed to a predefined return flight route towards the landing airport.

  • Operational conditions:

In particular, the reference scenario considers an RPAS flying at medium level altitude, under IFR conditions, with 5nm separation minima, departing and landing on standard civil airport or local area for VTOL where no other civil air traffic will be present during the live trials. Operations will be conducted in RLOS (both in the VLOS and BVLOS).

Communication between RP and ATC will be performed by telephone, while communication between OP and ATC will be based on RT.

The Flight Test Area (FTA, in Fig.1) is located close to the CIRA premises, aside the Capua Airport (LIAU). For the execution of the RAID flight tests the area, normally open to leisure and commercial air transport operations, will be covered by NOTAM released by the GRAZZANISE Airport Authority. 

The FTA has a polygonal structure, which extends for about 10NM in the EST-WEST direction and for about 6 NM in the NORTH-SOUTH direction, and with a PTF allowing operations from 500 ft to 5000 ft AGL. The FTA has been designed in order to support all the conflict conditions that are expected to be tested in the RAID flight test plan, allowing both vertical and lateral conflict resolutions manoeuvres (3NM is the larger lateral minima to be maintained during the tests and 1000 ft is the vertical separation). The only vehicles under test admitted to fly into FTA are the Flare OPV and collaborative vehicles equipped with ADS-B Out. TSA2 is managed by the ATC as a class A airspace with mandatory ADS-B out equipment.

FTA fig.1

Fig. 1 – The RAID Flight Test Area located near between the Grazzanise and Capua Airports

Inside the FTA, a simulated “reserved” area has been identified, the OMA – Operational Manoeuvring Area (Fig.2) -, which has been introduced to test procedures for the operational use of typical RPAS missions areas (i.e., the use of areas for Search and Rescue operations, or Surveillance and Tracking operations, and so on). The OMA is a polygonal area of about 7×3 NM, procedures foreseeing that the RPAS is required to be cleared to enter or leave the area while operating in unsegregated airspace. The OMA will be activated on a tactical basis (simulating a Dynamical Segregated Area) for an agreed duration depending on the type of exercise/scenario. 

FTA & OMA fig.2

Fig. 2 – The RAID FTA and OMA areas of operations

Based on these preconditions, following 7th scenarios are defined to be addressed through the demonstration activities:

  1. SCN-RPAS.03-001: En-Route Operations of the RPAS, entering and leaving a Temporary Segregated Area from/to an unrestricted managed airspace.
  2. SCN-RPAS.03-002: En-Route Operations of the RPAS in presence of potentially conflicting manned traffic
  3. SCN-RPAS.03-003: Detect and Avoid (Collision Avoidance Function)
  4. SCN-RPAS.03-004: Detect and Avoid testing (Traffic Avoidance) – One manned vehicle involved
  5. SCN-RPAS.03-005: Detect and Avoid testing (Traffic Avoidance) – Multiple manned vehicles involved
  6. SCN-RPAS.03-006: Detect and Avoid testing (Traffic Avoidance) – Unmanned vehicle involved
  7. SCN-RPAS.03-007: En-Route Operations of the RPAS, under C3L security threats (spoofing, jamming)