Navigate / EASA
GM2 CAT.GEN.MPA.205 Aircraft tracking system — Aeroplanes

ED Decision 2017/023/R

DETERMINING WHETHER A FLIGHT NEEDS TO BE TRACKED

Table 1 provides a summary of the cases applicable to an aeroplane which is within the scope of CAT.GEN.MPA.205(a).


Table 1: Cases applicable to the flight of an aeroplane subject to the aircraft tracking requirement

Condition 1:

The planned route and the planned diversion routes are included in airspace blocks where ATS surveillance service is normally provided.

Condition 2:

The ATS surveillance service provided in all airspace blocks determined by Condition 1 is supported by ATC surveillance systems locating the aircraft at time intervals with adequate duration.

Condition 3:

The operator has provided all air navigation service providers competent for the airspace blocks determined by Condition 1 with the necessary contact information.

Case considered:

Aeroplane that is within the scope of CAT.GEN.MPA.205(a).


Conditions 1, 2 and 3 are met altogether.

The flight does not need to be tracked (refer to CAT.GEN.MPA.205(b)).

Note:

The operator should check at regular time intervals that Conditions 1, 2 and 3 are still met (refer to AMC2 CAT.GEN.MPA.205).

Either Condition 1, Condition 2 or Condition 3 is not met.

The flight shall be tracked (refer to CAT.GEN.MPA.205(b)).

Note:

Lack of aircraft tracking data due to a temporary or unexpected issue may be acceptable (refer to AMC1 CAT.GEN.MPA.205). Examples of issues (list is indicative and not exhaustive): airborne equipment found inoperative, transmission link disturbed by environmental factors; issue with the ground-based infrastructure or the space-based infrastructure.