Military activities planned for the long term by military Authorities will be shared with the ATM network. These activities will be further detailed to the level of individual flights for the medium-short term planning phase. An improved and harmonised OAT flight plan will represent the first description of the Mission Trajectory (MT) and will be integrated into the ATM network systems for processing and distribution. Mission Trajectory in Step1 will be the specific representation of the military flights which vary from the requirements for Business Trajectory or when their needs exceed these requirements. Demand for airspace reservation/restriction (ARES) will become an integral part of MT. ASM support tools in conjunction with congruent protocols and procedures will facilitate the automation of the data sharing and Collaborative Decision Making process (CDM) triggered either by Airspace Users or by NM. The negotiation process may result in agreed configuration of the airspace volume along with associated target times over the entry/exit points into ARES (TTO) to improve the Network performance.
For the Mission Trajectories which will use airspace reservations/restrictions (ARES), this specific information will be reflected in the dedicated improved OAT flight plan fields. Description of MT will thus include the unique identification of the airspace volume and associated estimates, e.g. elapsed time in ARES or TTOs agreed upon CDM process. Improved OAT flight plans will be integrated at European network level in the short term planning phase. Typically they will be delivered at the day of operations. Input, validation, acceptance and distribution of the OAT flight plans will be performed through network level services. Once validated in NM system, Shared MT will be published in Network Operations Plan (NOP) and will become the initial Reference Mission Trajectory (iRMT).
Code | Dates |
---|---|
2015
15
2016
16
2017
17
2018
18
2019
19
2020
20
2021
21
2022
22
2023
23
2024
24
2025
25
2026
26
2027
27
2028
28
2029
29
2030
30
2031
31
2032
32
2033
33
2034
34
2035
35
2036
36
2037
37
2038
38
2039
39
2040
40
|
|
|
|
AOM-0304-A | |
AIMS-06 |
|
AIMS-19b |
V4
V5
IOC - FOC
|
AOC-ATM-14 |
V4
V5
IOC - FOC
|
CTE-C06d |
V4
V5
IOC - FOC
|
ER APP ATC 143 |
V4
V5
IOC - FOC
|
ER APP ATC 168 |
V4
V5
IOC - FOC
|
MIL-0502 |
V4
V5
IOC - FOC
|
MIL-STD-03 | |
NIMS-35 |
V4
V5
IOC - FOC
|
PRO-014 |
V5
IOC - FOC
|
PRO-015 |
IOC - FOC
|
SWIM-APS-01a |
V4
V5
IOC - FOC
|
SWIM-APS-02a |
V4
V5
IOC - FOC
|
SWIM-APS-03a |
V4
V5
IOC - FOC
|
SWIM-APS-04a |
V4
V5
IOC - FOC
|
SWIM-INFR-05a |
V4
V5
IOC - FOC
|
SWIM-NET-01a |
V4
V5
IOC - FOC
|
AOC-ATM-15 |
V4
V5
IOC - FOC
|
MIL-0501 | |
SWIM-SUPT-01a |
|
SWIM-SUPT-03a |
IOC - FOC
|
SWIM-SUPT-05a |
V4
V5
IOC - FOC
|
Relationship | Code | Title | Related Elements |
---|---|---|---|
10
Has predecessor
|
AOM-0301 | Harmonised EUROCONTROL ECAC Area Rules for OAT-IFR and GAT Interface | |
10
Has successor
|
AOM-0304-B | Integrated management of Mission Trajectory in trajectory based operations environment |
Code | Title | Program | Related Elements | Analysis |
---|---|---|---|---|
PJ.07-03 | Mission Trajectory Driven Processes | SESAR 2020 Wave 1 | Analysis |