Compare and highlight differences

Compare / EASA/ Incorporated Amendments/ Compare & Highlight Differences

12.3. Appendix 3: List of operational hazards for AFIS

Available versions for ERULES-1963177438-16267

ED Decision 2019/004/R found in: GM Remote Aerodrome Air Traffic Services (Jan 2026)

Version

Show details Hide details

##### 12.3. Appendix 3: List of operational hazards for AFIS

*ED Decision 2019/004/R*

**Table 3** below lists the operational hazards as derived from
the results of the SESAR safety work (performed in the framework of
the SESAR JU programme) that may be considered by the ATS provider
for AFIS. They are valid in the context of both single mode of
operation as well as multiple mode of operation. However, it should
be noted that the list of operational hazards was developed for the
specific operational applications and context that was studied and
using the specific methodology as described in the SESAR safety
assessment reports [27] and [34]. The SESAR safety work focused on
the ATC service case, assuming that the most constraining results
specifying the concept of remote aerodrome ATS would be derived from
ATC services. Therefore, if using this list as an initial input, it
needs to be adapted as necessary taking into account the local
conditions and the operational application and context of the
particular implementation as well as the addition of potential system
hazards.

**Table 2: Initial list of
operational hazards (SESAR safety assessment — AFIS case)**

<table cellpadding="7" cellspacing="0">
<col/>
<col/>
<thead>
<tr>
<td bgcolor="#f3f3f3">
ID
</td>
<td bgcolor="#f3f3f3">
Description
</td>
</tr>
</thead>
<tbody>
<tr valign="top">
<td>
OH-AFIS-01
</td>
<td>
Remote
					AFIS fails to properly select runway-in-use.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-02
</td>
<td>
Remote
					AFIS fails to identify potential ‘conflicts’ in the vicinity
					of the aerodrome.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-03
</td>
<td>
Remote
					AFIS fails to provide appropriate traffic information (including
					local traffic) to relevant traffic:

					—	direction
					of flight or traffic concerned;

					—	type
					of wake-turbulence category;

					—	level
					of traffic and potential changes;

					—	relative
					bearing (12-h clock indication);

					—	other
					relevant information.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-04
</td>
<td>
Remote
					AFIS fails to provide appropriate information concerning the
					availability of the runway for departing/arriving traffic.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-05
</td>
<td>
Remote
					AFIS fails to provide appropriate traffic position information
					on the manoeuvring area.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-06
</td>
<td>
Remote
					AFIS fails to provide appropriate wake-turbulence- and
					jet-blast-related information.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-07
</td>
<td>
Remote
					AFIS fails to provide appropriate essential information on
					aerodrome conditions (surface conditions, maintenance works,
					obstacles, birds, lighting system failure, etc.) to departing
					and arriving traffic:

					—	conditions
					on the manoeuvring area;

					—	conditions
					on the parking area.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-08
</td>
<td>
Remote
					AFIS fails to provide appropriate start-up instructions to
					departing traffic.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-09
</td>
<td>
Remote
					AFIS fails to provide appropriate meteorological information to
					departing and arriving traffic.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-10
</td>
<td>
Remote
					AFIS fails to manoeuvre the visual signals to indicate to
					traffic that the aerodrome is not safe.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-11
</td>
<td>
Remote
					AFIS incorrectly coordinates with ATC for arriving traffic.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-12
</td>
<td>
Remote
					AFIS incorrectly coordinates with ATC for departing traffic.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-13
</td>
<td>
Remote
					AFIS fails to provide appropriate information on local traffic
					to assist taxiing operations.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-14
</td>
<td>
Remote
					AFIS incorrectly provides authorisation to persons/vehicles to
					enter into the manoeuvring area.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-15
</td>
<td>
Remote
					AFIS fails to provide light signals to vehicles and personnel on
					the manoeuvring area (when adequate or in case of radio
					communication failure).
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-16
</td>
<td>
Remote
					AFIS fails to provide appropriate relevant information on local
					traffic and aerodrome conditions to assist the flight crew in
					deciding when to take off.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-17
</td>
<td>
Remote
					AFIS fails to provide appropriate relevant information on local
					traffic and aerodrome conditions to assist the flight crew in
					deciding whether to land or go around.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-18
</td>
<td>
Remote
					AFIS fails to detect a runway incursion or the existence of any
					obstruction (including animals) on or in close proximity to the
					take-off/landing area.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-19
</td>
<td>
Remote
					AFIS fails to operate aeronautical ground lights:

					—	manoeuvring
					area lighting;

					—	taxiway
					area lighting.
</td>
</tr>
<tr valign="top">
<td>
OH-AFIS-20
</td>
<td>
Remote
					AFIS fails to monitor visual aids status.
</td>
</tr>
</tbody>
</table>