A generic term meaning: a) Ground: Air Traffic Control Unit, Flight Information Centre, or Air Traffic Control Service (area control services reporting office. ATSUI refers to both human operators (e.g. controllers) and automated systems (e.g. data processing systems) at an ATSU, unless specifically stated otherwise. b) Aircraft: a concept introduced on-board the Airbus aircraft family, which is in charge of managing the air/ground data link communication, which hosts all air traffic control and flight information applications, which manages the human machine interface and any required integration in air traffic control of flight information user systems on-board the aircraft.

Two aircraft are involved in an aircraft conflict if the distance between any probable position of one aircraft at a certain time, and any probable position of the other aircraft at that same time, will be less than the required separation criteria. (MTCD)

Airspace conflict refers to special use airspace penetration as defined in the EATM glossary of terms under Conflicts (MTCD).

Civil, including general aviation, and military users of controlled airspace.

That part of ATC that is concerned with en-route traffic coming from or going to adjacent centres or APP. It is a unit established to provide air traffic control service to controlled flights in control areas under its jurisdiction.

A volume of airspace as agreed between 2 ATS Units, extending into the adjacent/subjacent Areas of Responsibility, within which airspace structure and related activities may have an impact on air traffic co-ordination procedures. (SYSCO)

1. The airspace encompassing the AoR and a defined buffer zone within which airspace status and flight information are of operational interest to the system operators.

2. The Airspace volume for which the ACC requires information such as: entering flights, airspace status, etc. This area includes the AoR and its vicinity.

Either an aircraft conflict, or a special use airspace penetration, or a descent below lowest usable flight level, or a nominal routes overlap1. (MTCD)

An aircraft is in conflict with an object (other aircraft, protected airspace or the ground) when it is, or is predicted to be, within pre-defined separation criteria from that object. The separation criteria do not equate to ATC separation (SNET)

Consists of: conflict identification; conflict type, which is either aircraft conflict, or special use airspace penetration, or descent below lowest usable flight level, or nominal routes overlap; conflict severity; either aircraft conflict data, or special use airspace penetration data, or descent below lowest usable flight level data, or nominal routes overlap data. (MTCD)

Indication of the severity of a conflict (MTCD) on a scale from 1 to 10, based on values of predefined parameters (e.g., time to conflict, minimum distance between trajectories, and geometry of trajectories). (MTCD)

The Developers are those ANSPs who have conducted R&D and validation of elements of FASIT, over a number of years and who are now engaged in pre implementation activities.

In the context of this document the term ETMA (Extended terminal control area) is defined to be the En-route airspace surrounding a TMA which normally contains the en-route network from the top of descent to the initial approach fix. The ETMA sectors are normally under the ACC authority (AGC ODIAC S&M ORD v1.0).

The Newcomers are those ANSPs who are either:
i) considering the implementation of FASTI capability in the procurement of a new system or system upgrade
or
ii) have not yet considered implementing FASTI capability

The Pioneers are those ANSPs that have either:
i) implemented some elements of FASTI which are in operational daily use
or
ii) procured new ATM systems which have included some elements of FASTI but which are not being fully exploited operationally

The Planning Controller (PC), in the traditional controller team, is that controller responsible for non-radar related tasks.

The planning controller role refers to the responsibility defined for the PC for the purpose of the management of sector traffic entry and exit co-ordination and other tasks delegated by the TC.

The term SYSCO is used as a generic term to indicate the electronic system supported co-ordination process.

A defined airspace region for which an associated controller (or controllers) has ATC responsibility.

The use of the term strategic planning in this document is not intended to convey a context related to that of strategic planning by CFMU. Strategic planning (FASTI) refers to that activity whereby the PC, having availability of MTCD and other traffic information, can plan traffic management with a tactical approach/flair for a sector or a number of sectors without the same time critical context as that of tactical control.

Tactical ATC is a type of operational ATC situation. Tactical ATC situations involve time-critical communications, concerned with the tactical separation of aircraft for immediate safety reasons, or for other reasons of a time-critical and immediate nature.

The person having final responsibility in co-ordinating traffic in a sector. The radar controller (often simply called the controller) is assisted by a planner (advance planning) and assistant.
The Tactical Controller (TC) or Executive Controller (EXC), in the traditional controller team, is that controller responsible for the tasks associated with traffic co-ordination and management in a sector.

The tactical controller role refers to the responsibility defined for the TC for the purpose of co-ordinating and managing traffic in a sector.

A volume of airspace of defined dimensions usually established at the confluence of ATS routes in the vicinity of one or more aerodromes.

Trajectory edition is an activity whereby the controller can modify the system trajectory for the purpose of FPL/trajectory modification or to perform what-if probing (see what-if probing).

1. Computation of a 4D-trajectory based on an aircraft's planned route and altitudes.
2. The process of calculating a trajectory of an aircraft, based on a current or proposed plan, weather information, aircraft and flight characteristics data, and other variables.

What-if probing refers to the action by a controller whereby a trajectory is edited and prior to updating the system this edited trajectory is probed to ascertain if it is conflict free. The ‘probing’ process is a function of MTCD trajectory pair comparison to detect trajectory uncertainty overlap based on the offline predefined parameters set in the system.