Light
Dark
System
Log In
Loading...
Compare / EASA/
Incorporated Amendments
/
Compare & Highlight Differences
AMC1 ATS.TR.155(e) ATS surveillance services
Available versions for ERULES-1963177438-17134
ED Decision 2020/008/R
found in: ATM/ANS Provision of Services (2017/373) (Feb 2023)
From
ATM/ANS Provision ... (Mar 2025)
ATM/ANS Provision ... (Feb 2023)
From section
To
ATM/ANS Provision ... (Mar 2025)
ATM/ANS Provision ... (Feb 2023)
To section
No visible text changes
0 removals
0 additions
View
Rich
Plain
Sync scrolling
Share
From
Show details
Hide details
To
Show details
Hide details
Version
Show side by side
AMC1 ATS.TR.155(e) ATS surveillance services ED Decision 2020/008/R INFORMATION REGARDING TRAFFIC ON A CONFLICTING PATH (a) Information regarding traffic on a conflicting path should be given, whenever practicable, in the following form: (1) relative bearing of the conflicting traffic in terms of the 12-hour clock; (2) distance from the conflicting traffic in kilometres or nautical miles; (3) direction in which the conflicting traffic appears to be proceeding; and (4) level and type of aircraft or, if unknown, relative speed of the conflicting traffic, e.g. slow or fast. (b) Pressure-altitude-derived level information, even when unverified, should be used in the provision of collision hazard information because such information, particularly if available from an otherwise unknown aircraft (e.g. a VFR flight) and given to the pilot of a known aircraft, could facilitate the location of a collision hazard. (c) If the level information has not been verified, the accuracy of the information should be considered uncertain and the pilot should be informed accordingly.
AMC1 ATS.TR.155(e) ATS surveillance services ED Decision 2020/008/R INFORMATION REGARDING TRAFFIC ON A CONFLICTING PATH (a) Information regarding traffic on a conflicting path should be given, whenever practicable, in the following form: (1) relative bearing of the conflicting traffic in terms of the 12-hour clock; (2) distance from the conflicting traffic in kilometres or nautical miles; (3) direction in which the conflicting traffic appears to be proceeding; and (4) level and type of aircraft or, if unknown, relative speed of the conflicting traffic, e.g. slow or fast. (b) Pressure-altitude-derived level information, even when unverified, should be used in the provision of collision hazard information because such information, particularly if available from an otherwise unknown aircraft (e.g. a VFR flight) and given to the pilot of a known aircraft, could facilitate the location of a collision hazard. (c) If the level information has not been verified, the accuracy of the information should be considered uncertain and the pilot should be informed accordingly.