Upload
dangminh
View
221
Download
3
Embed Size (px)
Citation preview
RPAS will generate the emergence of a new service sector
RPAS limited by flight authorisations not aligned one-another and limited to segregated airspace
Need to develop a seamless regulatory framework and enhance the coordination of various on-going R&D initiatives
A broad, safe and swift RPAS integration into the aviation system requires an enhanced coordination between the numerous actors and the different activities involved (regulatory, R&D and others)
RPAS insertion in airspace will be gradual and subsequently alleviated as soon as technology, regulation and societal acceptance progress
Rationale
3
4
Requirements & Challenges
Requirements for RPAS integration are linked to the European ATM Master Plan and the ICAO Global Plan/ASBU timeline
RPAS will have to fit into the ATM system (and not the reverse), with required adaptations to enable the safe integration of unmanned systems
RPAS will have to prove to be as safe as current manned vehicle operations and, their behaviour in operations, to be equivalent to manned aviation, in particular for air traffic control
Thus, RPAS insertion into the Aviation System shall comply with: - existing and consider future regulations and procedures developments
- the SESAR CONOPS(trajectory management)
- ATC rules/procedures
- capability requirements applicable to the airspace within which they operate
And not to:
- impact negatively the operations of the current system and its performance
- compromise existing aviation safety levels nor increase risk levels.
The way RPAS operations will be conducted, as regard to ATM operations has to be equivalent to manned aircraft
Demonstrating how to integrate RPAS into non-segregated airspace in a multi-aircraft
and manned flight environment
in order to explore the feasibility of integration with the wider aviation community by 2016
Providing concrete results, filling the operational and technical gaps identified for RPAS
integration into non-segregated airspace
Capitalising on the SESAR delivery approach by providing synergies, risk and
opportunities, with the overall SESAR programme
6
09 “RPAS Demonstration Projects”, which include integrated
pre-operational flight trials activities, have been selected:
Airports
RPAS Flight
Operator
Industry ANSP
SESAR RPAS Demonstration Projects
Timeline and deliverables
Phase 1
" Definition "
Phase 2
" Implementation "
Demonstration Plan
Including a Communication Strategy
Final Report
Max. 24 Months from KO
KO Meeting
45 to 90 days from KO meeting
Oct. / Nov. 2013 Jan. / March 2013
Oct. / Nov. 2015
Deliverable
D.02
Today
Deliverable
D.01
7
Refine the essential R&D activities for the integration in the EU Aviation System in the context of the SES initiative, as of 2016 and beyond
Identify globally interoperable and harmonised ATM requirements and enablers to meet the performance requirements
Produce a R&D and Validation programme - including planning, costs and priorities, as required by the different identified ATM requirements and enablers
Establish a high level implementation timeline, including costs and priorities
Provide material supporting the alignment of the legislative, financial and regulatory frameworks required for the deployment, including incentive mechanisms
Necessity of the RPAS Definition Phase
9
The following high-level operational requirements are to be considered:
Comply with existing and consider future regulations and procedures developments
Comply with the SESAR concept of operations and in particular trajectory management
Comply with air traffic control rules/procedures
Comply with the capability requirements applicable to the airspace within which they are intended to operate
Not impact negatively the operations of the current system and its performance in particular for the current users of the airspace
Not compromise existing aviation safety levels nor increase risk levels. The way RPAS operations will be conducted, as regard to ATM operations shall be equivalent to manned aircraft, as far as possible
Integration principles
10
The RPAS Definition Phase has to result in the following tree of activities:
Deliverable D.1: Regulatory and Business Framework
Deliverable D.2: Performance Requirements and Assessment
Deliverable D.3: Operational Changes in ATM
Deliverable D.4: Enabling Systems
Deliverable D.5: Validation Needs
Deliverable D.6: SESAR RPAS R&D Progr. requirements and outline
Deliverable D.7: Input to the EU ATM Master Plan
Evaluation in progress - Kick-off end of July - End in March 2015
Objective and Scope
11
The ATM System has to be trusted by the general public and by Governmental Authorities: sufficiently secure, resilient and trustworthy
As ATM System relies on SWIM: effective protection is essential to guarantee the effectiveness, efficiency and economy
Not only a technological change but also a cultural change due to its existing architecture, components and reliance on human operators
A systemic approach to cyber-security for SWIM, considering in particular best practices implemented in other sectors
An opportunity with regard to operational and cross-border interoperability (needs for international cooperation to ensure interoperability, standards definition...)
Need to understand the economic implications of any proposed investments in this area, for an accepted level of risk
Why a Cyber-Security Study?
13
Introduce a holistic approach to cyber-security which complement the SESAR ATM security approach
Provide a scalable approach and applicable across different stakeholders in different Member States at different levels of security maturity
Support the SESAR next developments, in particular SWIM
Be the grounds of a cyber-security strategy to participate to the effective deployment of the new ATM systems and to their interoperability
Consider the interoperability dimension, the definition of standards agreed at international level
Provide: Deliverable D.1: an ATM Cyber-Security Threat and Vulnerability Assessment
Deliverable D.2: a SESAR Target ATM Cyber-Security Framework
Deliverable D.3: a SESAR Cyber-Security Maturity Assessment
Deliverable D.4: a SESAR Cyber-Security Strategy
Study kick-off in May 2014 – foreseen end March 2015
Objective and Scope of the Study
14