RPAS integration, the future is now

EUROCONTROL

Edgar Reuber UAS ATM Integration manager (mil)

WAC Madrid May 04th and 05th 2014

RPAS integration, the future is now 2

Overview

What are RPAS Types of operations Perception of RPAS? Civil applications Basic principles for RPAS integration and challenges Future view

RPAS integration, the future is now 3

What are RPAS

Remotely Piloted Aircraft Systems (RPAS) Aircraft Ground station Data link

No pilot in cockpit. Remotely operated. Can be programmed. Capable of operating autonomously with pilot-in-the-loop. Normally recoverable but ultimately expendable

Subset of Unmanned Aircraft Systems (UAS)

They are NOT called drones!

RPAS integration, the future is now 4

Types of Operations (instead of weight, e.g. 150 kg, or size categories) Very low level Operations

VLOS E-VLOS B-VLOS

IFR/VFR RLOS

IFR/VFR BRLOS (SATCOM)

=> Distinguished according to IFR / VFR and ICAO airspace classification they fly in

RPAS integration, the future is now 5

RPAS what is your perception?

RPAS integration, the future is now 6

Public perception?

DRONES Big brother watching/listening Paparazzi Privacy PROBLEM Emotive:

Who’s flying this thing? His life isn’t in danger!

Interaction: Flying to same rules? Predictable response? Collision avoidance?

Visibility. Reaction times. Legality.

RPAS integration, the future is now 7

Or societal benefits?

RPAS integration, the future is now 8

Civil/Commercial UAS – Where/Why?

RPAS integration, the future is now 9

Civil/Commercial UAS – Where/Why?

RPAS integration, the future is now 10

Civil/Commercial UAS – Where/Why?

RPAS integration, the future is now 11

Civil/Commercial UAS – Where/Why?

RPAS integration, the future is now 12

BASIC PRINCIPLES FOR INTEGRATION:

AS SAFE AS MANNED AVIATION OR SAFER TRANSPARENT OPERATIONS TOWARDS ATC AND OTHER AIRSPACE USERS SHOULD NOT EXCLUDE OTHER AIRSPACE USERS AIRSPACE ACCESS RPAS WILL HAVE TO FIT INTO ATM SYSTEM

SEAMLESS INTEGRATION CHALLENGES

AIRWORTHINESS DETECT & AVOID DATA LINK HUMAN FACTORS SPECTRUM ACCEPTANCE

13

UAS integration in non-SA is a “manned aviation” issue

• Acceptability by manned aviation is a priority

– Aviation stakeholders need to be part of the process

– Pilots, ANSPs, CAAs, ATC controllers

• Standardisation is the most efficient way for acceptability

– Providing a common UAS view and understanding to all airspace users and actors

– Addressing interoperability, performance, safety

Management of UAS collision avoidance and separation is one of the most

challenging issues

The Challenges of RPAS Integration

RPAS integration, the future is now 14

See and Avoid

RPAS integration, the future is now 15

HOW RPAS INTEGRATION MIGHT EVOLVE

Evolutionary and incremental process. Usage to increase as confidence in UAS safety

and reliability grows. Near-term commercial requirement for small civil

UAS flying VLOS. Early RLOS flying under IFR in Classes A-C

airspace. Later RLOS in all classes of airspace under IFR

and VFR .

RPAS integration, the future is now 16

DATA LINK (not exhaustive)

C2 Definition of general performances Categories:

Robustness Availability Integrity QoS Continuity

Latency Spectrum Software Defined Radio techniques for secure and efficient use of allowable

bandwidth Modeling, prototyping and demonstration

RPAS integration, the future is now 17

HUMAN FACTORS (not exhaustive)

HF issues shall identify functional requirements for operations of RPAs in non-segregated airspace in order to support safety in the ATM system

They shall consider HSI implications of such functional requirements, i.e. implications for manpower personnel training Human Factors

GCS design Environmental conditions HMI design Use of automation

Occupational Health & Safety

RPAS integration, the future is now 18

SECURITY (not exhaustive)

RPAS IT hardware integrity Software integrity Secure IT maintenance Cyber intrusion detection Cyber intrusion protection Authentication and encryption of comms Resistance to GNSS jamming and spoofing, to C&C jamming and spoofing

Ground Station RPAS Equipment Software integrity Authentication and encryption of comms

19

How to organise the Integration? Policy

– Support to EC

• ATM

– Guidelines, integration, training, etc

• Regulation

– EASA

– JARUS

• R&D

– SJU, EDA, ESA etc (until SESAR2)

• Standardisation

– ICAO UASSG

– EUROCAE WG 73/93

– NATO

• Support to States

– ATM, REG, R&D

MAIN GOAL DRIVE HARMONISATION