+ All Categories
Home > Documents > Mission Trajectory Step 1 From planning to deployment.

Mission Trajectory Step 1 From planning to deployment.

Date post: 01-Apr-2015
Category:
Upload: stone-tatlock
View: 218 times
Download: 1 times
Share this document with a friend
Popular Tags:
10
Mission Trajectory Step 1 From planning to deployment
Transcript
Page 1: Mission Trajectory Step 1 From planning to deployment.

Mission Trajectory Step 1

From planning to deployment

Page 2: Mission Trajectory Step 1 From planning to deployment.

Deployment Baseline (formerly: IP1)

Step 1Time-based Operations

Step 2Trajectory-based Operations

Step 3Performance-based Operations

SESAR Steps are capability-based(not fixed in time)

The SESAR concept

Page 3: Mission Trajectory Step 1 From planning to deployment.

4D Business Trajectories data linked and negotiated between

AOC-NM-aircraft-ATC

4DT4DT

4DT

4DT

4DT

4DT

Trajectory negotiation

4D Mission Trajectory same principles as Business Trajectory but enables complex military

operations:• Airspace reservations part of trajectory definition• Synchronisation of multiple trajectories for complex missions• Formation flights with trajectory split/join up • Confidentiality & security requirements of exchanges between WOC-NM-aircraft-ATC

SESAR : Business/Mission Trajectory

Page 4: Mission Trajectory Step 1 From planning to deployment.

Business/Mission Trajectory

Not a new way to fulfill missions

- A new way to share information, negotiate trajectories and allocate airspace during planning cycles and execution phase,

- A new way for flights description, richer than today’s Flight Plan

- A new way to provide Air Navigation Services

- A new challenge for civil/military coordination

Mission Trajectory

Page 5: Mission Trajectory Step 1 From planning to deployment.

Network Shortcomings

• Lack of Airspace management flexibility (inability to exploit capacity opportunities)

• Lack of integration of Network, ATC and AOC/WOC operations (limited reliability of available information by different actors) implies:

Limited predictabilityoverprotection in term of capacity,Local actions with negative impact on Network

• 2 hours gap between ATFM and ATC (limited flexibility and reactivity)

• Civil military airspace management systems to distribute planned airspace usage & airspace status and to allow more modular airspace structures.• Harmonised military flight planning & aeronautical information systems to support improved “Operational Air Traffic”

• Secure gateways to interconnect military systems to the ATM network

• Uplink & downlink of trajectory data through data link (Transport type only for time based operations)• Enhanced airborne navigation and surveillance systems (Transport type only for time based operations)

Technical Enablers

Mission Trajectory requirements

• Unrestricted access to airspace for high priority missions

• Operational Air Traffic Transit Service across Europe

• Sufficient airspace for training• Confidentiality & security• Compatibility with FABs & NM

Main Step 1 system changesin support of Mission Trajectory & Network performance

Page 6: Mission Trajectory Step 1 From planning to deployment.

STEP 1

Mission trajectory development

ATFCM

BaselineProjects

7.5.213.2.1

Projects 7.5.2

13.2.1

ASM local simulation/negotiation

ASM local simulation/negotiation

ASM simulation/negotiationBased on Mission requests

ASM simulation/negotiationBased on Mission requests

ASM simulation/negotiationBased on flight intents

ASM simulation/negotiationBased on flight intents

Project 7.5.27.6.213.2.1

15.2.10

Project 7.5.27.6.213.2.1

15.2.10

Project 7.6.2

11.1.1

Project 7.6.2

11.1.1

WOC

ATC

ATC

ATC

ATFCM

A/C

AircraftMeteo

Page 7: Mission Trajectory Step 1 From planning to deployment.

Common Projects

(Business view)

7

Main challenges

Master Plan

Network Strategy Plan

ESSIP

Performances& MaturityAnalysis,Business

casesImplementation

Projects

CFT

Level 1 Level 3

• Monitoring execution• Ensuring Consistency• Trigger and support

corrective actionsLevel 2

Page 8: Mission Trajectory Step 1 From planning to deployment.

ATM Master Plan 2012--Operational changes for Military-

STEP 1 “full scope”ANSP Aeronautical Information Data sharing

Airspace Management Systems

Datalink systems and services

Enhanced local ATFCM tools for NOP & trajectories

Enhanced Flight data processing

Ground communication and information infrastructure

WOC Aeronautical Information Data sharing

Airspace Management Systems

Enhanced WOC systems

Flight planning and demand data

Ground communication and information infrastructure

TRANSPORTAIRCRAFT

ABAS capability

ASAS spacing capability

Datalink systems and services

FMS capability to support i4d operations

FMS upgrade for Lateral/Vertical NAV approach

Onboard D-Taxi management

Onboard situation awareness & alerts on ground

AIRPORT Aeronautical Information Data sharing

Airport lighting system

Datalink systems and services

Ground communication and information infrastructure

Surface movement systems

Surveillance infrastructure

Planning exercise/No CBAPrioritisation based on:• Mission trajectory needs•Network performance• synchronisation

Page 9: Mission Trajectory Step 1 From planning to deployment.

Interim DeploymentProgramme 2012-2014

Reference

WP 2 Airspace management tools interoperable with the network

AOM 19; FUA regulation

WP 2 Migration to European Aeronautical Service EAD

AOM 13.1; LSSIP report; regulation 73/2010; ITY ADQ

WP 4 VDL 2 for Transport Aircraft ITY AGDL; link 2000+

WP 5 Ground systems upgrade for Flight Data Exchange

ITY COTR; FMTP

WP 6* Avionics and procedures for RNP 1 performance

NAV 03; PBN mandate

WP 7* Avionics and procedures for APV baro/SBAS

NAV 10; ICAO spec; PBN mandate

Military priorities• deployment decision taken• no need for Cost Benefit analysis

* maturity linked to PBN mandate

Page 10: Mission Trajectory Step 1 From planning to deployment.

Pilot “common project”2015-2017

& Deployment Programme

2015-2030

Reference

WP 1 Enhanced ASM/ATFCM/ATC ?

WP 2 Enhanced OAT FPL?

WP 3 AMHS?

WP 4 Secure gateways with IP networks?

WP ..

Deployment based on European ATM Master Plan• Refined Performance needs•Refined Cost Benefit Analysis• Updated with R&D results and maturity checks• With updated OIs/enablers/lines of action


Recommended