SPO.OP.100 Use of aerodromes and operating sites

Regulation (EU) No 379/2014

The operator shall only use aerodromes and operating sites that are adequate for the type of aircraft and operation concerned.

USE OF OPERATING SITES MOTOR-POWERED AIRCRAFT

(a) When defining adequate operating sites for use for the type(s) of aircraft and operation(s) concerned, the operator should take account of the following:

(1) An adequate site is a site that the operator considers to be satisfactory, taking account of the applicable performance requirements and site characteristics.

(2) The operator should have in place a procedure for the survey of operating sites by a competent person. Such a procedure should take account for possible changes to the operating site characteristics that may have taken place since last surveyed.

(b) Operating sites that are pre-surveyed should be specifically specified in the operations manual. The operations manual should contain diagrams or ground and aerial photographs, depiction (pictorial) and description of:

(1) the overall dimensions of the operating site;

(2) location and height of relevant obstacles to approach and take-off profiles and in the manoeuvring area;

(3) approach and take-off flight paths;

(4) surface condition (blowing dust/snow/sand);

(5) provision of control of third parties on the ground, if applicable;

(6) lighting, if applicable;

(7) procedure for activating the operating site in accordance with national regulations, if applicable;

(8) other useful information, for example details of the appropriate ATS agency and frequency; and

(9) site suitability with reference to available aircraft performance.

(c) Where the operator specifically permits operation from sites that are not pre-surveyed, the pilot-in-command should make, from the air a judgement on the suitability of a site. At least (b)(1) to (b)(6) inclusive and (b)(9) should be considered. Operations to non-pre-surveyed operating sites by night should not be conducted.

SPO.OP.101 Altimeter check and settings

Regulation (EU) 2021/2237

(a) The operator shall establish procedures for altimeter checking before each departure.

(b) The operator shall establish procedures for altimeter settings for all phases of flight, which shall take into account the procedures established by the State of the aerodrome or the State of the airspace, if applicable.

ALTIMETER SETTING PROCEDURES

The following paragraphs of ICAO Doc 8168 (PANS-OPS), Volume III provide recommended guidance on how to develop the altimeter setting procedure:

(a) 3.2 ‘Pre-flight operational test’;

(b) 3.3 ‘Take-off and climb’;

(c) 3.5 ‘Approach and landing’.

SPO.OP.105 Specification of isolated aerodromes – aeroplanes

Regulation (EU) 2021/1296

For the selection of alternate aerodromes and the fuel/energy planning and in-flight re-planning policy, the operator shall not consider an aerodrome as an isolated aerodrome unless the flying time to the nearest weather-permissible destination alternate aerodrome is more than:

(a) for aeroplanes with reciprocating engines, 60 minutes; or

(b) for turbine-engined aeroplanes, 90 minutes.

USE OF AN AERODROME AS AN ISOLATED AERODROME

The concept of an isolated aerodrome allows the operator to use aerodromes that would otherwise be impossible or impractical to use with sufficient fuel to fly to the destination aerodrome and then to a destination alternate aerodrome, provided that operational criteria are used to ensure a safe‑landing option, for example by specifying a point of no return (PNR). If alternate fuel is carried, the operator is not required to consider the aerodrome as isolated and use the aforementioned operational criteria.

SPO.OP.110 Aerodrome operating minima – aeroplanes and helicopters

Regulation (EU) 2021/2237

(a) The operator shall establish aerodrome operating minima for each departure, destination or alternate aerodrome that is planned to be used in order to ensure separation of the aircraft from terrain and obstacles and to mitigate the risk of loss of visual references during the visual flight segment of instrument approach operations.

(b) The method used to establish aerodrome operating minima shall take all the following elements into account:

(1) the type, performance, and handling characteristics of the aircraft;

(2) the equipment available on the aircraft for the purpose of navigation, acquisition of visual references, and/or control of the flight path during take-off, approach, landing, and missed approach;

(3) any conditions or limitations stated in the aircraft flight manual (AFM);

(4) the dimensions and characteristics of the runways/final approach and take-off areas (FATOs) that may be selected for use;

(5) the adequacy and performance of the available visual and non-visual aids and infrastructure;

(6) the obstacle clearance altitude/height (OCA/H) for the instrument approach procedures (IAPs);

(7) the obstacles in the climb-out areas and the necessary clearance margins;

(8) any non-standard characteristics of the aerodrome, the IAP or the local environment;

(9) the composition of the flight crew, their competence and experience;

(10) the IAP;

(11) the aerodrome characteristics and the available air navigation services (ANS);

(12) any minima that may be promulgated by the State of the aerodrome;

(13) the conditions prescribed in any specific approvals for low-visibility operations (LVOs) or operations with operational credits; and

(14) the relevant operational experience of the operator.

(c) The operator shall specify a method of determining aerodrome operating minima in the operations manual.

AMC1 SPO.OP.110 Aerodrome operating minima – aeroplanes and helicopters

ED Decision 2014/018/R

COMMERCIALLY AVAILABLE INFORMATION

An acceptable method of specifying aerodrome operating minima is through the use of commercially available information.

AMC2 SPO.OP.110 Aerodrome operating minima — aeroplanes and helicopters

ED Decision 2022/012/R

GENERAL

(a) The aerodrome operating minima should not be lower than those specified in AMC5 SPO.OP.110 or AMC4 SPO.OP.110(c).

(b) Whenever practical, approaches should be flown as stabilised approaches (SAps). Different procedures may be used for a particular approach to a particular runway.

(c) Whenever practical, non-precision approaches should be flown using the continuous descent final approach (CDFA) technique. Different procedures may be used for a particular approach to a particular runway.

(d) For approaches not flown using the CDFA technique: when calculating the minima in accordance with AMC5 SPO.OP.110, the applicable minimum runway visual range (RVR) should be increased by 200 m for Category A and B aeroplanes and by 400 m for Category C and D aeroplanes, provided that the resulting RVR/converted meteorological visibility (CMV) value does not exceed 5 000 m. SAp or CDFA should be used as soon as facilities are improved to allow these techniques.

AMC3 SPO.OP.110 Aerodrome operating minima — aeroplanes and helicopters

ED Decision 2022/014/R

TAKE-OFF OPERATIONS

(a) General

(1) Take-off minima should be expressed as VIS or RVR limits, taking into account all relevant factors for each aerodrome planned to be used and aircraft characteristics and equipment. Where there is a specific need to see and avoid obstacles on departure and/or for a forced landing, additional conditions, e.g. ceiling, should be specified.

(2) The pilot-in-command should not commence take-off unless the weather conditions at the aerodrome of departure are equal to or better than the applicable minima for landing at that aerodrome, unless a weather-permissible take-off alternate aerodrome is available.

(3) When the reported VIS is below that required for take-off and the RVR is not reported, a take-off should only be commenced if the pilot-in-command can determine that the visibility along the take-off runway/area is equal to or better than the required minimum.

(4) When no reported VIS or RVR is available, a take-off should only be commenced if the pilot-in-command can determine that the visibility along the take-off runway/area is equal to or better than the required minimum.

(b) Visual reference

(1) The take-off minima should be selected to ensure sufficient guidance to control the aircraft in the event of both a rejected take-off in adverse circumstances and a continued take-off after failure of the critical engine.

(2) For night operations, the prescribed runway lights should be in operation to mark the runway and any obstacles.

TAKE-OFF OPERATIONS WITH HELICOPTERS AND COMPLEX MOTOR-POWERED AEROPLANES

(c) Required RVR or VIS

(1) Complex motor-powered aeroplanes

(i) For multi-engined aeroplanes with such performance that in the event of a critical engine failure at any point during take-off the aeroplane can either stop or continue the take-off to a height of 1 500 ft above the aerodrome while clearing obstacles by the required margins, the take-off minima specified by the operator should be expressed as RVR or VIS values not lower than those specified in Table 1.

(ii) Multi-engined aeroplanes without the performance to comply with the conditions in (c)(1)(i) in the event of a critical engine failure may need to reland immediately and to see and avoid obstacles in the take-off area. Such aeroplanes may be operated to the following take-off minima provided that they are able to comply with the applicable obstacle clearance criteria, assuming engine failure at the specified height:

(A) The take-off minima specified by the operator should be based upon the height from which the one-engine-inoperative (OEI) net take-off flight path can be constructed.

(B) The RVR minima used should not be lower than either of the values specified in Table 1 or Table 2.

(iii) For single-engined complex aeroplane operations, the take-off minima specified by the operator should be expressed as RVR/CMV values not lower than those specified in Table 1 below.

Unless the operator makes use of a risk period, whenever the surface in front of the runway does not allow for a safe forced landing, the RVR/CMV values should not be lower than 800 m. In this case, the proportion of the flight to be considered starts at the lift-off position and ends when the aeroplane is able to turn back and land on the runway in the opposite direction or glide to the next landing site in case of power loss.

(iv) When the RVR or the VIS is not available, the pilot-in-command should not commence take-off unless he or she can determine that the actual conditions satisfy the applicable take-off minima.

Table 1

Take-off — aeroplanes (without LVTO approval)

RVR or VIS

Facilities

RVR or VIS (m)*

Day only: Nil**

500

Day: at least runway edge lights or runway centre line markings

Night: at least runway edge lights or runway centre line lights and runway end lights

400

* The reported RVR or VIS value representative of the initial part of the take-off run can be replaced by pilot assessment.

** The pilot is able to continuously identify the take-off surface and maintain directional control.

Table 2

Take-off — aeroplanes (without an LVTO approval)

Assumed engine failure height above the take-off runway versus RVR or VIS

Assumed engine failure height
above the take-off runway (ft)

RVR or VIS (m)*

<50

400

51–100

400

101–150

400

151–200

500

201–300

1 000

>300 or if no positive take-off flight path can be constructed

1 500

* The reported RVR or VIS value representative of the initial part of the take-off run can be replaced by pilot assessment.

(2) Helicopters

(i) For helicopters having a mass where it is possible to reject the take-off and land on the FATO in case of the critical engine failure being recognised at or before the take-off decision point (TDP), the operator should specify an RVR or VIS as take-off minima in accordance with Table 3.

(ii) For all other cases, the pilot-in-command should operate to take-off minima of 800 m RVR or VIS and remain clear of cloud during the take-off manoeuvre until reaching the performance capabilities of (c)(2)(i).

(iii) For point-in-space (PinS) departures to an initial departure fix (IDF), the take-off minima should be selected to ensure sufficient guidance to see and avoid obstacles and return to the heliport if the flight cannot continue visually to the IDF.

Table 3

Take-off — helicopters (without LVTO approval)

RVR or VIS

Onshore aerodromes or operating sites with instrument flight rules (IFR) departure procedures

RVR or VIS (m)**

No light and no markings (day only)

400 or the rejected take-off distance, whichever is the greater

No markings (night)

800

Runway edge/FATO light and centre line marking

400

Runway edge/FATO light, centre line marking and relevant RVR information

400

Offshore helideck*

 

Two-pilot operations

400

Single-pilot operations

500

* The take-off flight path to be free of obstacles.

** On PinS departures to IDF, VIS should not be less than 800 m and ceiling should not be less than 250 ft.

DETERMINATION OF THE DH/MDH FOR INSTRUMENT APPROACH OPERATIONS — AEROPLANES

(a) The decision height (DH) to be used for a 3D approach operation or a 2D approach operation flown using the continuous descent final approach (CDFA) technique should not be lower than the highest of:

(1) the obstacle clearance height (OCH) for the category of aircraft;

(2) the published approach procedure DH or minimum descent height (MDH) where applicable;

(3) the system minima specified in Table 4;

(4) the minimum DH permitted for the runway specified in Table 5; or

(5) the minimum DH specified in the AFM or equivalent document, if stated.

(b) The MDH for a 2D approach operation flown not using CDFA technique should not be lower than the highest of:

(1) the OCH for the category of aircraft;

(2) the published approach procedure MDH where applicable;

(3) the system minimum specified in Table 4;

(4) the lowest MDH permitted for the runway specified in Table 5; or

(5) the lowest MDH specified in the AFM, if stated.

DETERMINATION OF THE DH/MDH FOR INSTRUMENT APPROACH OPERATIONS — HELICOPTERS

(c) The DH or MDH should not be lower than the highest of:

(1) the OCH for the category of aircraft;

(2) the published approach procedure DH or MDH where applicable;

(3) the system minima specified in Table 4;

(4) the lowest DH or MDH permitted for the runway/FATO specified in Table 6 if applicable; or

(5) the lowest DH or MDH specified in the AFM, if stated.

Table 4

System minima — all aircraft

Facility

Lowest DH/MDH (ft)

ILS/MLS/GLS

200

GNSS/SBAS (LPV)

200*

Precision approach radar (PAR)

200

GNSS/SBAS (LP)

250

GNSS (LNAV)

250

GNSS/Baro VNAV (LNAV/VNAV)

250

Helicopter PinS approach

250**

LOC with or without DME

250

SRA (terminating at ½ NM)

250

SRA (terminating at 1 NM)

300

SRA (terminating at 2 NM or more)

350

VOR

300

VOR/DME

250

NDB

350

NDB/DME

300

VDF

350

* For localiser performance with vertical guidance (LPV), a DH of 200 ft may be used only if the published final approach segment (FAS) datablock sets a vertical alert limit not exceeding 35 m. Otherwise, the DH should not be lower than 250 ft.

** For PinS approaches with instructions to ‘proceed VFR’ to an undefined or virtual destination, the DH or MDH should be with reference to the ground below the missed approach point (MAPt).

Table 5

Runway type minima — aeroplanes

Runway type

Lowest DH/MDH (ft)

Precision approach (PA) runway, category I

200

NPA runway

250

Non-instrument runway

Circling minima as shown in Table 1 in SPO.OP.112

Table 6

Type of runway/FATO versus lowest DH/MDH — helicopters

Type of runway/FATO

Lowest DH/MDH (ft)

PA runway, category I

NPA runway

Non-instrument runway

200

Instrument FATO

FATO

200

250

Table 6 does not apply to helicopter PinS approaches with instructions to ‘proceed VFR’.

DETERMINATION OF RVR OR VIS FOR INSTRUMENT APPROACH OPERATIONS — AEROPLANES

(a) The RVR or VIS for straight-in instrument approach operations should not be less than the greatest of the following:

(1) the minimum RVR or VIS for the type of runway used according to Table 7;

(2) the minimum RVR determined according to the MDH or DH and class of lighting facility according to Table 8; or

(3) the minimum RVR according to the visual and non-visual aids and on-board equipment used according to Table 9.

If the value determined in (1) is a VIS, then the result is a minimum VIS. In all other cases, the result is a minimum RVR.

(b) For Category A and B aeroplanes, if the RVR or VIS determined in accordance with (a) is greater than 1 500 m, then 1 500 m should be used.

(c) If the approach is flown with a level flight segment at or above the MDA/H, then 200 m should be added to the RVR calculated in accordance with (a) and (b) for Category A and B aeroplanes and 400 m for Category C and D aeroplanes.

(d) The visual aids should comprise standard runway day markings, runway edge lights, threshold lights, runway end lights and approach lights as defined in Table 8.

Table 7

Type of runway versus minimum RVR or VIS — aeroplanes

Type of runway

Minimum RVR or VIS (m)

PA runway, category I

RVR 550

NPA runway

RVR 750

Non-instrument runway

VIS according to Table 1 in SPO.OP.112 (Circling minima)

Table 8

RVR versus DH/MDH

DH or MDH (ft)

Class of lighting facility

FALS

IALS

BALS

NALS

RVR (m)

200

210

550

750

1 000

1 200

211

240

550

800

1 000

1 200

241

250

550

800

1 000

1 300

251

260

600

800

1 100

1 300

261

280

600

900

1 100

1 300

281

300

650

900

1 200

1 400

301

320

700

1 000

1 200

1 400

321

340

800

1 100

1 300

1 500

341

360

900

1 200

1 400

1 600

361

380

1 000

1 300

1 500

1 700

381

400

1 100

1 400

1 600

1 800

401

420

1 200

1 500

1 700

1 900

421

440

1 300

1 600

1 800

2 000

441

460

1 400

1 700

1 900

2 100

461

480

1 500

1 800

2 000

2 200

481

500

1 500

1 800

2 100

2 300

501

520

1 600

1 900

2 100

2 400

521

540

1 700

2 000

2 200

2 400

541

560

1 800

2 100

2 300

2 400

561

580

1 900

2 200

2 400

2 400

581

600

2 000

2 300

2 400

2 400

601

620

2 100

2 400

2 400

2 400

621

640

2 200

2 400

2 400

2 400

641

660

2 300

2 400

2 400

2 400

661

and above

2 400

2 400

2 400

2 400

Table 9

Visual and non-visual aids and/or on-board equipment versus minimum RVR — aeroplanes

Type of approach

Facilities

Lowest RVR

Multi-pilot operations

Single-pilot operations

3D operations

Final approach track offset 15o for category A and B aeroplanes or 5o for Category C and D aeroplanes

runway touchdown zone lights (RTZL) and runway centre line lights (RCLL)

No limitation

without RTZL and RCLL but using HUDLS or equivalent system; autopilot or flight director to the DH

No limitation

600 m

No RTZL and RCLL, not using HUDLS or equivalent system or autopilot to the DH

750 m

800 m

3D operations

runway touchdown zone lights (RTZL) and runway centre line lights (RCLL)

and

Final approach track offset  15o for Category A and B aeroplanes or Final approach track offset 5o for Category C and D aeroplanes

800 m

1 000 m

without RTZL and RCLL but using HUDLS or equivalent system; autopilot or flight director to the DH

and

Final approach track offset  15o for Category A and B aeroplanes or Final approach track offset 5o for Category C and D aeroplanes

800 m

1 000 m

2D operations

Final approach track offset 15o for category A and B aeroplanes or 5o for Category C and D aeroplanes

750 m

2D operations

Final approach track offset  15o for Category A and B aeroplanes

1 000 m

1 000 m

Final approach track offset 5o for Category C and D aeroplanes

1 200 m

1 200 m

Table 10

Approach lighting systems — aeroplanes

Class of lighting facility

Length, configuration and intensity of approach lights

FALS

CAT I lighting system (HIALS ≥ 720 m) distance coded centre line, barrette centre line

IALS

Simple approach lighting system (HIALS 420–719 m) single source, barrette

BALS

Any other approach lighting system (HIALS, MALS or ALS 210–419 m)

NALS

Any other approach lighting system (HIALS, MALS or ALS < 210 m) or no approach lights

(e) For night operations or for any operation where credit for visual aids is required, the lights should be on and serviceable except as provided for in Table 15.

(f) Where any visual or non-visual aid specified for the approach and assumed to be available in the determination of operating minima is unavailable, revised operating minima will need to be determined.

DETERMINATION OF RVR OR VIS FOR TYPE A INSTRUMENT APPROACH AND TYPE B CAT I INSTRUMENT APPROACH OPERATIONS — HELICOPTERS

(a) For IFR operations, the RVR or VIS should not be less than the greatest of:

(1) the minimum RVR or VIS for the type of runway/FATO used according to Table 11;

(2) the minimum RVR determined according to the MDH or DH and class of lighting facility according to Table 12; or

(3) for PinS operations with instructions to ‘proceed visually’, the distance between the MAPt of the PinS and the FATO or its approach light system.

If the value determined in (1) is a VIS, then the result is a minimum VIS. In all other cases, the result is a minimum RVR.

(b) For PinS operations with instructions to ‘proceed VFR’, the VIS should be compatible with visual flight rules.

(c) For Type A instrument approaches where the MAPt is within ½ NM of the landing threshold, the approach minima specified for FALS may be used regardless of the length of approach lights available. However, FATO/runway edge lights, threshold lights, end lights and FATO/runway markings are still required.

(d) An RVR of less than 800 m should not be used except when using a suitable autopilot coupled to an ILS, MLS, GLS or LPV, in which case normal minima apply.

(e) For night operations, ground lights should be available to illuminate the FATO/runway and any obstacles.

(f) The visual aids should comprise standard runway day markings, runway edge lights, threshold lights and runway end lights and approach lights as specified in Table 13.

(g) For night operations or for any operation where credit for runway and approach lights as defined in Table 13 is required, the lights should be on and serviceable except as provided for in Table 15.

Table 11

Type of runway/FATO versus minimum RVR — helicopters

Type of runway/FATO

Minimum RVR or VIS (m)

PA runway, category I

NPA runway

Non-instrument runway

RVR 550

Instrument FATO

FATO

RVR 550

RVR or VIS 800

Table 12

Onshore helicopter instrument approach minima

DH/MDH (ft)

Facilities versus RVR (m)

FALS

IALS

BALS

NALS

200

550

600

700

1 000

201–249

550

650

750

1 000

250–299

600*

700*

800

1 000

300 and above

750*

800

900

1 000

* Minima on 2D approach operations should be no lower than 800 m.

Table 13

Approach lighting systems — helicopters

Class of lighting facility

Length, configuration and intensity of approach lights

FALS

CAT I lighting system (HIALS ≥ 720 m) distance coded centre line, barrette centre line

IALS

Simple approach lighting system (HIALS 420–719 m) single source, barrette

BALS

Any other approach lighting system (HIALS, MALS or ALS 210–419 m)

NALS

Any other approach lighting system (HIALS, MALS or ALS < 210 m) or no approach lights

AMC7 SPO.OP.110 Aerodrome operating minima — aeroplanes and helicopters

ED Decision 2022/012/R

VISUAL APPROACH OPERATIONS

For a visual approach operation, the runway visual range (RVR) should not be less than 800 m.

AMC8 SPO.OP.110 Aerodrome operating minima — aeroplanes and helicopters

ED Decision 2022/012/R

CONVERSION OF VISIBILITY TO CMV — AEROPLANES

The following conditions apply to the use of CMV instead of RVR:

(a) If the reported RVR is not available, a CMV may be substituted for the RVR, except:

(1) to satisfy take-off minima; or

(2) for the purpose of continuation of an approach in LVO.

(b) If the minimum RVR for an approach is more than the maximum value assessed by the aerodrome operator, then CMV should be used.

(c) In order to determine CMV from visibility:

(1) for flight planning purposes, a factor of 1.0 should be used;

(2) for purposes other than flight planning, the conversion factors specified in Table 14 should be used.

Table 14

Conversion of reported VIS to RVR/CMV

Light elements in operation

RVR/CMV = reported VIS x

Day

Night

HI approach and runway lights

1.5

2.0

Any type of light installation other than above

1.0

1.5

No lights

1.0

not applicable

EFFECT ON LANDING MINIMA OF TEMPORARILY FAILED OR DOWNGRADED GROUND EQUIPMENT — COMPLEX MOTOR-POWERED AIRCRAFT

(a) General

These instructions are intended for both pre-flight and in-flight use. It is, however, not expected that the pilot-in-command would consult such instructions after passing 1 000 ft above the aerodrome. If failures of ground aids are announced at such a late stage, the approach could be continued at the pilot-in-command’s discretion. If failures are announced before such a late stage in the approach, their effect on the approach should be considered as described in Table 15 and, if considered necessary, the approach should be abandoned.

(b) Conditions applicable to Table 15:

(1) multiple failures of runway/FATO lights other than those indicated in Table 15 should not be acceptable;

(2) failures of approach and runway/FATO lights are acceptable at the same time, and the most demanding consequence should be applied; and

(3) failures other than ILS or MLS affect the RVR only and not the DH.

Table 15

Failed or downgraded equipment — effect on landing minima

Failed or downgraded equipment

Effect on landing minima

Type B

Type A

Navaid standby transmitter

No effect

Outer marker (ILS only)

No effect if the required height or glide path can be checked using other means,

e.g. DME fix

APV — not applicable

NPA with FAF: no effect unless used as FAF

If the FAF cannot be identified (e.g. no method available for timing of descent), NPA operations cannot be conducted

Middle marker (ILS only)

No effect

No effect unless used as MAPt

RVR Assessment Systems

No effect

Approach lights

Minima as for NALS

Approach lights except the last 210 m

Minima as for BALS

Approach lights except the last 420 m

Minima as for IALS

Standby power for approach lights

No effect

Edge lights, threshold lights and runway end lights

Day — no effect
Night — not allowed

Centre line lights

Aeroplanes: No effect if flight director (F/D), HUDLS or auto-land;
otherwise RVR 750 m

Helicopters: No effect on CAT I and SA CAT I approach operations.

No effect

Centre line lights spacing increased to 30 m

No effect

TDZ lights

Aeroplanes: No effect if F/D, HUDLS or auto-land;
otherwise RVR 750 m

 

Helicopters: No effect.

No effect

Taxiway lighting system

No effect

EFFECT ON LANDING MINIMA OF TEMPORARILY FAILED OR DOWNGRADED GROUND EQUIPMENT — OTHER-THAN COMPLEX MOTOR-POWERED AIRCRAFT

(a) Non-precision approaches requiring a final approach fix (FAF) and/or MAPt should not be conducted where a method of identifying the appropriate fix is not available.

(b) Where approach lighting is partly unavailable, minima should take account of the serviceable length of approach lighting.

AIRCRAFT CATEGORIES

(a) Aircraft categories should be based on the indicated airspeed at threshold (VAT), which is equal to the stalling speed (VSO) multiplied by 1.3 or where published 1-g (gravity) stall speed (VS1g) multiplied by 1.23 in the landing configuration at the maximum certified landing mass. If both VSO and VS1g are available, the higher resulting VAT should be used.

(b) The aircraft categories specified in Table 16 should be used.

Table 16

Aircraft categories corresponding to VAT values

Aircraft category

VAT

A

Less than 91 kt

B

from 91 to 120 kt

C

from 121 to 140 kt

D

from 141 to 165 kt

E

from 166 to 210 kt

CONTINUOUS DESCENT FINAL APPROACH (CDFA) — AEROPLANES

(a) Introduction

(1) Controlled flight into terrain (CFIT) is a major hazard in aviation. Most CFIT accidents occur in the final approach segment of non-precision approaches; the use of stabilised-approach criteria on a continuous descent with a constant, predetermined vertical path is seen as a major improvement in safety during the conduct of such approaches. Operators should ensure that the following techniques are adopted as widely as possible, for all approaches.

(2) The elimination of level flight segments at MDA close to the ground during approaches, and the avoidance of major changes in attitude and power/thrust close to the runway that can destabilise approaches, are seen as ways to reduce operational risks significantly.

(3) The term CDFA has been selected to cover a flight technique for any type of NPA operation.

(4) The advantages of CDFA are as follows:

(i) the technique enhances safe approach operations by the utilisation of standard operating practices;

(ii) the technique is similar to that used when flying an ILS approach, including when executing the missed approach and the associated missed approach procedure manoeuvre;

(iii) the aeroplane attitude may enable better acquisition of visual cues;

(iv) the technique may reduce pilot workload;

(v) the approach profile is fuel efficient;

(vi) the approach profile affords reduced noise levels; and

(vii) the technique affords procedural integration with APV operations.

(b) CDFA

(1) Continuous descent final approach is defined in Annex I to the Regulation on Air operations.

(2) An approach is only suitable for application of a CDFA technique when it is flown along a nominal vertical profile; a nominal vertical profile is not forming part of the approach procedure design, but can be flown as a continuous descent. The nominal vertical profile information may be published or displayed on the approach chart to the pilot by depicting the nominal slope or range/distance vs height. Approaches with a nominal vertical profile are considered to be:

(i) NDB, NDB/DME;

(ii) VOR, VOR/DME;

(iii) LOC, LOC/DME;

(iv) VDF, SRA; and

(v) GNSS/LNAV.

(3) Stabilised approach (SAp) is defined in Annex I to the Regulation on Air Operations.

(i) The control of the descent path is not the only consideration when using the CDFA technique. Control of the aeroplane’s configuration and energy is also vital to the safe conduct of an approach.

(ii) The control of the flight path, described above as one of the requirements for conducting an SAp, should not be confused with the path requirements for using the CDFA technique.

(iii) The predetermined approach slope requirements for applying the CDFA technique are established by the following:

(A) the published ‘nominal’ slope information when the approach has a nominal vertical profile; and

(B) the designated final-approach segment minimum of 3 NM, and maximum, when using timing techniques, of 8 NM.

(iv) An SAp will never have any level segment of flight at DA/H or MDA/H, as applicable. This enhances safety by mandating a prompt missed approach procedure manoeuvre at DA/H or MDA/H.

(v) An approach using the CDFA technique will always be flown as an SAp, since this is a requirement for applying CDFA. However, an SAp does not have to be flown using the CDFA technique, for example a visual approach.

ONSHORE AERODROME DEPARTURE PROCEDURES — OPERATIONS WITH NON-COMPLEX HELICOPTERS

The cloud base and visibility should be such as to allow the helicopter to be clear of cloud at the take-off decision point (TDP), and for the pilot flying to remain in sight of the surface until reaching the minimum speed for flight in instrument meteorological conditions, as given in the AFM.

TAKE-OFF MINIMA — OPERATIONS WITH COMPLEX HELICOPTERS

(a) To ensure sufficient control of the helicopter in IMC, the speed, before entering in IMC, should be above the minimum authorised speed in IMC, Vmini. This is a limitation in the AFM. Therefore, the lowest speed before entering in IMC is the highest of Vtoss (velocity take-off safety speed) and Vmini.

(b) As example, Vtoss is 45 kt and Vmini 60 kt. In that case, the take–off minima have to include the distance to accelerate to 60 kt. The take-off distance should be increased accordingly.

APPROACH LIGHTING SYSTEMS — ICAO, FAA

The following table provides a comparison of the ICAO and FAA specifications.

Table 17

Approach lighting systems — ICAO and FAA specifications

Class of lighting facility

Length, configuration and intensity of approach lights

FALS

ICAO: CAT I lighting system (HIALS ≥ 720 m) distance coded centre line, barrette centre line

FAA: ALSF1, ALSF2, SSALR, MALSR, high- or medium-intensity and/or flashing lights, 720 m or more

IALS

ICAO: simple approach lighting system (HIALS 420–719 m) single source, barrette

FAA: MALSF, MALS, SALS/SALSF, SSALF, SSALS, high- or medium-intensity and/or flashing lights, 420–719 m

BALS

Any other approach lighting system (e.g. HIALS, MALS or ALS 210–419 m)

FAA: ODALS, high- or medium-intensity or flashing lights 210–419 m

NALS

Any other approach lighting system (e.g. HIALS, MALS or ALS <210 m) or no approach lights

IAPs — SBAS OPERATIONS

(a) SBAS LPV operations with a DH of 200 ft depend on an SBAS approved for operations down to a DH of 200 ft.

(b) The following systems are in operational use or in a planning phase:

(1) European geostationary navigation overlay service (EGNOS), operational in Europe;

(2) wide area augmentation system (WAAS), operational in the USA;

(3) multi-functional satellite augmentation system (MSAS), operational in Japan;

(4) system of differential correction and monitoring (SDCM), planned by Russia;

(5) GPS-aided geo-augmented navigation (GAGAN) system, planned by India; and

(6) satellite navigation augmentation system (SNAS), planned by China.

MEANS TO DETERMINE THE REQUIRED RVR BASED ON DH AND LIGHTING FACILITIES

The values in Table 8 are derived from the formula below:

RVR (m) = [(DH/MDH (ft) × 0.3048)/tanα] – length of approach lights (m),

where α is the calculation angle, being a default value of 3.00° increasing in steps of 0.10° for each line in Table 8 up to 3.77° and then remaining constant. An upper RVR limit of 2 400 m has been applied to the table.

USE OF DH FOR NPAs FLOWN USING THE CONTINUOUS DESCENT FINAL APPROACH (CDFA) TECHNIQUE

The safety of using the MDH as DH in CDFA operations has been verified by at least two independent analyses concluding that a CDFA using MDH as DH without any add-on is safer than the traditional step-down and level flight NPA operation. A comparison was made between the safety level of using MDH as DH without an add-on with the well-established safety level resulting from the ILS collision risk model (CRM). The NPA used was the most demanding, i.e. most tightly designed NPA, which offers the least additional margins. It should be noted that the design limits of the ILS approach design, e.g. the maximum glide path (GP) angle of 3.5 degrees, must be observed for the CDFA in order to keep the validity of the comparison.

There is a wealth of operational experience in Europe confirming the above-mentioned analytical assessments. It cannot be expected that each operator is able to conduct similar safety assessments, and this is not necessary. The safety assessments already performed take into account the most demanding circumstances at hand, like the most tightly designed NPA procedures and other ‘worst-case scenarios’. The assessments naturally focus on cases where the controlling obstacle is located in the missed approach area.

However, it is necessary for operators to assess whether their cockpit procedures and training are adequate to ensure minimal height loss in case of a go-around manoeuvre. Suitable topics for the safety assessment required by each operator may include:

             understanding of the CDFA concept including use of the MDA/H as DA/H;

             cockpit procedures that ensure flight on speed, on path, and with proper configuration and energy management;

             cockpit procedures that ensure gradual decision-making; and

             identification of cases where an increase of the DA/H may be necessary because of non-standard circumstances, etc.

INCREMENTS SPECIFIED BY THE COMPETENT AUTHORITY

Additional increments to the published minima may be specified by the competent authority in order to take into account certain operations, such as downwind approaches, single-pilot operations, or approaches flown not using the CDFA technique.

USE OF COMMERCIALLY AVAILABLE INFORMATION

When an operator uses commercially available information to establish aerodrome operating minima, the operator remains responsible for ensuring that the information used is accurate and suitable for its operation, and that the aerodrome operating minima are calculated in accordance with the method specified in Part C of its operations manual.

The operator should apply the procedures in ORO.GEN.205 ‘Contracted activities’.

VISUAL AND NON-VISUAL AIDS AND INFRASTRUCTURE

‘Visual and non-visual aids and infrastructure’ refers to all equipment and facilities required for the procedure to be used for the intended instrument approach operation. This includes but is not limited to lights, markings, ground- or space-based radio aids, etc.

SPO.OP.112 Aerodrome operating minima — circling operations with aeroplanes

Regulation (EU) 2021/2237

(a) The minimum descent height (MDH) for a circling approach operation with aeroplanes shall not be lower than the highest of:

(1) the published circling OCH for the aeroplane category;

(2) the minimum circling height derived from Table 1; or

(3) the decision height (DH)/MDH of the preceding IAP.

(b) The minimum visibility for a circling approach operation with aeroplanes shall be the highest of:

(1) the circling visibility for the aeroplane category, if published; or

(2) the minimum visibility derived from Table 1.

Table 1

MDH and minimum visibility for circling per aeroplane category

 

Aeroplane category

A

B

C

D

MDH (ft)

400

500

600

700

Minimum VIS (m)

1 500

1 600

2 400

3 600

SUPPLEMENTAL INFORMATION

(a) The purpose of this guidance material is to provide operators with supplemental information regarding the application of aerodrome operating minima in relation to circling approaches.

(b) Conduct of flight — general:

(1) the MDH and OCH included in the procedure are referenced to aerodrome elevation;

(2) the MDA is referenced to mean sea level;

(3) for these procedures, the applicable visibility is the VIS; and

(4) operators should provide tabular guidance of the relationship between height above threshold and the in-flight visibility required to obtain and sustain visual contact during the circling manoeuvre.

(c) Instrument approach followed by visual manoeuvring (circling) without prescribed tracks:

(1) When the aeroplane is on the initial instrument approach, before visual reference is stabilised, but not below MDA/H, the aeroplane should follow the corresponding instrument approach procedure (IAP) until the appropriate instrument MAPt is reached.

(2) At the beginning of the level flight phase at or above the MDA/H, the instrument approach track should be maintained until the pilot:

(i) estimates that, in all probability, visual contact with the runway of intended landing or the runway environment will be maintained during the entire circling procedure;

(ii) estimates that the aeroplane is within the circling area before commencing circling; and

(iii) is able to determine the aeroplane’s position in relation to the runway of intended landing with the aid of the appropriate visual references.

(3) If the pilot cannot comply with the conditions in (c)(2) at the MAPt, then a missed approach should be executed in accordance with the IAP.

(4) After the aeroplane has left the track of the initial instrument approach, the flight phase outbound from the runway should be limited to an appropriate distance, which is required to align the aeroplane onto the final approach. Such manoeuvres should be conducted to enable the aeroplane to:

(i) attain a controlled and stable descent path to the intended landing runway; and

(ii) remain within the circling area and in such a way that visual contact with the runway of intended landing or runway environment is maintained at all times.

(5) Flight manoeuvres should be carried out at an altitude/height that is not less than the circling MDA/H.

(6) Descent below the MDA/H should not be initiated until the threshold of the runway to be used has been appropriately identified. The aeroplane should be in a position to continue with a normal rate of descent and land within the touchdown zone (TDZ).

(d) Instrument approach followed by a visual manoeuvring (circling) with prescribed track.

(1) The aeroplane should remain on the initial IAP until one of the following is reached:

(i) the prescribed divergence point to commence circling on the prescribed track; or

(ii) the MAPt.

(2) The aeroplane should be established on the instrument approach track in level flight at or above the MDA/H at or by the circling manoeuvre divergence point.

(3) If the divergence point is reached before the required visual reference is acquired, a missed approach should be initiated not later than the MAPt and completed in accordance with the initial instrument approach procedure.

(4) When commencing the prescribed circling manoeuvre at the published divergence point, the subsequent manoeuvres should be conducted to comply with the published routing and published heights/altitudes.

(5) Unless otherwise specified, once the aeroplane is established on the prescribed track(s), the published visual reference does not need to be maintained unless:

(i) required by the State of the aerodrome; or

(ii) the circling MAPt (if published) is reached.

(6) If the prescribed circling manoeuvre has a published MAPt and the required visual reference has not been obtained by that point, a missed approach should be executed in accordance with (e)(2) and (e)(3).

(7) Subsequent further descent below MDA/H should only commence when the required visual reference has been obtained.

(8) Unless otherwise specified in the procedure, final descent should not be commenced from the MDA/H until the threshold of the intended landing runway has been identified and the aeroplane is in a position to continue with a normal rate of descent to land within the TDZ.

(e) Missed approach

(1) Missed approach during the instrument procedure prior to circling:

(i) if the missed approach procedure is required to be flown when the aeroplane is positioned on the instrument approach track, and before commencing the circling manoeuvre, the published missed approach for the instrument approach should be followed; or

(ii) if the IAP is carried out with the aid of an ILS, an MLS or a SAp, the MAPt associated with an ILS or an MLS procedure without glide path (GP-out procedure) or the SAp, where applicable, should be used.

(2) If a prescribed missed approach is published for the circling manoeuvre, this overrides the manoeuvres prescribed below.

(3) If visual reference is lost while circling to land after the aeroplane has departed from the initial instrument approach track, the missed approach specified for that particular instrument approach should be followed. It is expected that the pilot will make an initial climbing turn toward the intended landing runway to a position overhead of the aerodrome where the pilot will establish the aeroplane in a climb on the instrument missed approach segment.

(4) The aeroplane should not leave the visual manoeuvring (circling) area, which is obstacle protected, unless:

(i) established on the appropriate missed approach procedure; or

(ii) at minimum sector altitude (MSA).

(5) All turns should be made in the same direction and the aeroplane should remain within the circling protected area while climbing to either:

(i) the altitude assigned to any published circling missed approach manoeuvre if applicable;

(ii) the altitude assigned to the missed approach of the initial instrument approach;

(iii) the MSA;

(iv) the minimum holding altitude (MHA) applicable for transition to a holding facility or fix, or continue to climb to an MSA; or

(v) as directed by ATS.

When the missed approach procedure is commenced on the ‘downwind’ leg of the circling manoeuvre, an ‘S’ turn may be undertaken to align the aeroplane on the initial instrument approach missed approach path, provided the aeroplane remains within the protected circling area.

The pilot-in-command should be responsible for ensuring adequate terrain clearance during the above-stipulated manoeuvres, particularly during the execution of a missed approach initiated by ATS.

(6) Because the circling manoeuvre may be accomplished in more than one direction, different patterns will be required to establish the aeroplane on the prescribed missed approach course depending on its position at the time visual reference is lost. In particular, all turns are to be in the prescribed direction if this is restricted, e.g. to the west/east (left or right hand) to remain within the protected circling area.

(7) If a missed approach procedure is published for a particular runway onto which the aeroplane is conducting a circling approach and the aeroplane has commenced a manoeuvre to align with the runway, the missed approach for this direction may be accomplished. The ATS unit should be informed of the intention to fly the published missed approach procedure for that particular runway.

(8) The pilot-in-command should advise ATS when any missed approach procedure has been commenced, the height/altitude the aeroplane is climbing to and the position the aeroplane is proceeding towards and/or heading the aeroplane is established on.

SPO.OP.113 Aerodrome operating minima – onshore circling operations with helicopters

Regulation (EU) No 379/2014

The MDH for an onshore circling operation with helicopters shall not be lower than 250 ft and the meteorological visibility not less than 800 m.

SPO.OP.115 Departure and approach procedures – aeroplanes and helicopters

Regulation (EU) No 379/2014

(a) The pilot-in-command shall use the departure and approach procedures established by the State of the aerodrome, if such procedures have been published for the runway or FATO to be used.

(b) The pilot-in-command may deviate from a published departure route, arrival route or approach procedure:

(1) provided obstacle clearance criteria can be observed, full account is taken of the operating conditions and any ATC clearance is adhered to; or

(2) when being radar-vectored by an ATC unit.

(c) In the case of operations with complex motor-powered aircraft, the final approach segment shall be flown visually or in accordance with the published approach procedures.

APPROACH FLIGHT TECHNIQUE — AEROPLANES

(a) All approach operations should be flown as SAp operations.

(b) The CDFA technique should be used for NPA procedures.

SPO.OP.116 Performance-based navigation – aeroplanes and helicopters

Regulation (EU) 2016/1199

The operator shall ensure that, when PBN is required for the route or procedure to be flown:

(a) the relevant PBN specification is stated in the AFM or other document that has been approved by the certifying authority as part of an airworthiness assessment or is based on such approval; and

(b) the aircraft is operated in conformance with the relevant navigation specification and limitations in the AFM or other document mentioned above.

PBN OPERATIONS

For operations where a navigation specification for performance-based navigation (PBN) has been prescribed and no specific approval is required in accordance with SPA.PBN.100, the operator should:

(a) establish operating procedures specifying:

(1) normal, abnormal and contingency procedures;

(2) electronic navigation database management; and

(3) relevant entries in the minimum equipment list (MEL);

(b) specify the flight crew qualification and proficiency constraints and ensure that the training programme for relevant personnel is consistent with the intended operation; and

(c) ensure continued airworthiness of the area navigation system.

MONITORING AND VERIFICATION

(a) Preflight and general considerations

(1) At navigation system initialisation, the flight crew should confirm that the navigation database is current and verify that the aircraft position has been entered correctly, if required.

(2) The active flight plan, if applicable, should be checked by comparing the charts or other applicable documents with navigation equipment and displays. This includes confirmation of the departing runway and the waypoint sequence, reasonableness of track angles and distances, any altitude or speed constraints, and, where possible, which waypoints are fly-by and which are fly-over. Where relevant, the RF leg arc radii should be confirmed.

(3) The flight crew should check that the navigation aids critical to the operation of the intended PBN procedure are available.

(4) The flight crew should confirm the navigation aids that should be excluded from the operation, if any.

(5) An arrival, approach or departure procedure should not be used if the validity of the procedure in the navigation database has expired.

(6) The flight crew should verify that the navigation systems required for the intended operation are operational.

(b) Departure

(1) Prior to commencing a take-off on a PBN procedure, the flight crew should check that the indicated aircraft position is consistent with the actual aircraft position at the start of the take-off roll (aeroplanes) or lift-off (helicopters).

(2) Where GNSS is used, the signal should be acquired before the take-off roll (aeroplanes) or lift-off (helicopters) commences.

(3) Unless automatic updating of the actual departure point is provided, the flight crew should ensure initialisation on the runway or FATO by means of a manual runway threshold or intersection update, as applicable. This is to preclude any inappropriate or inadvertent position shift after take-off.

(c) Arrival and approach

(1) The flight crew should verify that the navigation system is operating correctly and the correct arrival procedure and runway (including any applicable transition) are entered and properly depicted.

(2) Any published altitude and speed constraints should be observed.

(3) The flight crew should check approach procedures (including alternate aerodromes if needed) as extracted by the system (e.g. CDU flight plan page) or presented graphically on the moving map, in order to confirm the correct loading and the reasonableness of the procedure content.

(4) Prior to commencing the approach operation (before the IAF), the flight crew should verify the correctness of the loaded procedure by comparison with the appropriate approach charts. This check should include:

(i) the waypoint sequence;

(ii) reasonableness of the tracks and distances of the approach legs and the accuracy of the inbound course; and

(iii) the vertical path angle, if applicable.

(d) Altimetry settings for RNP APCH operations using Baro VNAV

(1) Barometric settings

(i) The flight crew should set and confirm the correct altimeter setting and check that the two altimeters provide altitude values that do not differ more than 100 ft at the most at or before the FAF.

(ii) The flight crew should fly the procedure with:

(A) a current local altimeter setting source available — a remote or regional altimeter setting source should not be used; and

(B) the QNH/QFE, as appropriate, set on the aircraft’s altimeters.

(2) Temperature compensation

(i) For RNP APCH operations to LNAV/VNAV minima using Baro VNAV:

(A) the flight crew should not commence the approach when the aerodrome temperature is outside the promulgated aerodrome temperature limits for the procedure unless the area navigation system is equipped with approved temperature compensation for the final approach;

(B) when the temperature is within promulgated limits, the flight crew should not make compensation to the altitude at the FAF; and

(C) since only the final approach segment is protected by the promulgated aerodrome temperature limits, the flight crew should consider the effect of temperature on terrain and obstacle clearance in other phases of flight.

(ii) For RNP APCH operations to LNAV minima, the flight crew should consider the effect of temperature on terrain and obstacle clearance in all phases of flight, in particular on any step-down fix.

(e) Sensor and lateral navigation accuracy selection

(1) For multi-sensor systems, the flight crew should verify, prior to approach, that the GNSS sensor is used for position computation.

(2) Flight crew of aircraft with RNP input selection capability should confirm that the indicated RNP value is appropriate for the PBN operation.

MANAGAMENT OF THE NAVIGATION DATABASE

(a) For RNAV 1, RNAV 2, RNP 1, RNP 2, and RNP APCH, the flight crew should neither insert nor modify waypoints by manual entry into a procedure (departure, arrival or approach) that has been retrieved from the database. User-defined data may be entered and used for waypoint altitude/speed constraints on a procedure where said constraints are not included in the navigation database coding.

(b) For RNP 4 operations, the flight crew should not modify waypoints that have been retrieved from the database. User-defined data (e.g. for flex-track routes) may be entered and used.

(c) The lateral and vertical definition of the flight path between the FAF and the missed approach point (MAPt) retrieved from the database should not be revised by the flight crew.

DISPLAYS AND AUTOMATION

(a) For RNAV 1, RNP 1, and RNP APCH operations, the flight crew should use a lateral deviation indicator, and where available, flight director and/or autopilot in lateral navigation mode.

(b) The appropriate displays should be selected so that the following information can be monitored:

(1) the computed desired path;

(2) aircraft position relative to the lateral path (cross-track deviation) for FTE monitoring; and

(3) aircraft position relative to the vertical path (for a 3D operation).

(c) The flight crew of an aircraft with a lateral deviation indicator (e.g. CDI) should ensure that lateral deviation indicator scaling (full-scale deflection) is suitable for the navigation accuracy associated with the various segments of the procedure.

(d) The flight crew should maintain procedure centrelines unless authorised to deviate by ATC or demanded by emergency conditions.

(e) Cross-track error/deviation (the difference between the area-navigation-system-computed path and the aircraft-computed position) should normally be limited to ± ½ time the RNAV/RNP value associated with the procedure. Brief deviations from this standard (e.g. overshoots or undershoots during and immediately after turns) up to a maximum of 1 time the RNAV/RNP value should be allowable.

(f) For a 3D approach operation, the flight crew should use a vertical deviation indicator and, where required by AFM limitations, a flight director or autopilot in vertical navigation mode.

(g) Deviations below the vertical path should not exceed 75 ft at any time, or half-scale deflection where angular deviation is indicated, and not more than 75 ft above the vertical profile, or half-scale deflection where angular deviation is indicated, at or below 1 000 ft above aerodrome level. The flight crew should execute a missed approach if the vertical deviation exceeds this criterion unless the flight crew has in sight the visual references required to continue the approach.

VECTORING AND POSITIONING

(a) ATC tactical interventions in the terminal area may include radar headings, ‘direct to’ clearances which bypass the initial legs of an approach procedure, interceptions of an initial or intermediate segments of an approach procedure or the insertion of additional waypoints loaded from the database.

(b) In complying with ATC instructions, the flight crew should be aware of the implications for the navigation system.

(c) ‘Direct to’ clearances may be accepted to the IF provided that it is clear to the flight crew that the aircraft will be established on the final approach track at least 2 NM before the FAF.

(d) ‘Direct to’ clearance to the FAF should not be acceptable. Modifying the procedure to intercept the final approach track prior to the FAF should be acceptable for radar-vectored arrivals or otherwise only with ATC approval.

(e) The final approach trajectory should be intercepted no later than the FAF in order for the aircraft to be correctly established on the final approach track before starting the descent (to ensure terrain and obstacle clearance).

(f) ‘Direct to’ clearances to a fix that immediately precede an RF leg should not be permitted.

(g) For parallel offset operations en route in RNP 4 and A-RNP, transitions to and from the offset track should maintain an intercept angle of no more than 45° unless specified otherwise by ATC.

ALERTING AND ABORT

(a) Unless the flight crew has sufficient visual reference to continue the approach operation to a safe landing, an RNP APCH operation should be discontinued if:

(1) navigation system failure is annunciated (e.g. warning flag);

(2) lateral or vertical deviations exceed the tolerances; and

(3) loss of the on-board monitoring and alerting system.

(b) Discontinuing the approach operation may not be necessary for a multi-sensor navigation system that includes demonstrated RNP capability without GNSS in accordance with the AFM.

(c) Where vertical guidance is lost while the aircraft is still above 1 000 ft AGL, the flight crew may decide to continue the approach to LNAV minima, when supported by the navigation system.

CONTINGENCY PROCEDURES

(a) The flight crew should make the necessary preparation to revert to a conventional arrival procedure where appropriate. The following conditions should be considered:

(1) failure of the navigation system components including navigation sensors, and a failure effecting flight technical error (e.g. failures of the flight director or autopilot);

(2) multiple system failures affecting aircraft performance;

(3) coasting on inertial sensors beyond a specified time limit; and

(4) RAIM (or equivalent) alert or loss of integrity function.

(b) In the event of loss of PBN capability, the flight crew should invoke contingency procedures and navigate using an alternative means of navigation.

(c) The flight crew should notify ATC of any problem with PBN capability.

(d) In the event of communication failure, the flight crew should continue with the operation in accordance with published lost communication procedures.

RNAV 10

(a) Operating procedures and routes should take account of the RNAV 10 time limit declared for the inertial system, if applicable, considering also the effect of weather conditions that could affect flight duration in RNAV 10 airspace.

(b) The operator may extend RNAV 10 inertial navigation time by position updating. The operator should calculate, using statistically-based typical wind scenarios for each planned route, points at which updates can be made, and the points at which further updates will not be possible.

DESCRIPTION

(a) For both, RNP X and RNAV X designations, the ‘X’ (where stated) refers to the lateral navigation accuracy (total system error) in NM, which is expected to be achieved at least 95 % of the flight time by the population of aircraft operating within the airspace, route or procedure. For RNP APCH and A-RNP, the lateral navigation accuracy depends on the segment.

(b) PBN may be required on notified routes, for notified procedures and in notified airspace.

RNAV 10

(c) For purposes of consistency with the PBN concept, this Regulation is using the designation ‘RNAV 10’ because this specification does not include on-board performance monitoring and alerting.

(d) However, it should be noted that many routes still use the designation ‘RNP 10’ instead of ‘RNAV 10’. ‘RNP 10’ was used as designation before the publication of the fourth edition of ICAO Doc 9613 in 2013. The terms ‘RNP 10’ and ‘RNAV 10’ should be considered equivalent.

SPO.OP.120 Noise abatement procedures

Regulation (EU) No 379/2014

The pilot-in-command shall take into account published noise abatement procedures to minimise the effect of aircraft noise while ensuring that safety has priority over noise abatement.

NADP DESIGN — OPERATIONS WITH COMPLEX MOTOR-POWERED AIRCRAFT

(a) For each aeroplane type two departure procedures should be defined, in accordance with ICAO Doc. 8168 (Procedures for Air Navigation Services, ‘PANS-OPS’), Volume I:

(1) noise abatement departure procedure one (NADP 1), designed to meet the close-in noise abatement objective; and

(2) noise abatement departure procedure two (NADP 2), designed to meet the distant noise abatement objective.

(b) For each type of NADP (1 and 2), a single climb profile should be specified for use at all aerodromes, which is associated with a single sequence of actions. The NADP 1 and NADP 2 profiles may be identical.

GM1 SPO.OP.120 Noise abatement procedures

ED Decision 2014/018/R

TERMINOLOGY — OPERATIONS WITH COMPLEX MOTOR-POWERED AEROPLANES

(a) ‘Climb profile’ means in this context the vertical path of the NADP as it results from the pilot’s actions (engine power reduction, acceleration, slats/flaps retraction).

(b) ‘Sequence of actions’ means the order in which these pilot’s actions are done and their timing.

GENERAL

(c) The rule addresses only the vertical profile of the departure procedure. Lateral track has to comply with the standard instrument departure (SID).

EXAMPLE

(d) For a given aeroplane type, when establishing the distant NADP, the operator should choose either to reduce power first and then accelerate, or to accelerate first and then wait until slats/flaps are retracted before reducing power. The two methods constitute two different sequences of actions.

(e) For an aeroplane type, each of the two departure climb profiles may be defined by one sequence of actions (one for close-in, one for distant) and two above aerodrome level (AAL) altitudes/heights. These are:

(1) the altitude of the first pilot’s action (generally power reduction with or without acceleration). This altitude should not be less than 800 ft AAL; or

(2) the altitude of the end of the noise abatement procedure. This altitude should usually not be more than 3 000 ft AAL.

(f) These two altitudes may be runway specific when the aeroplane flight management system (FMS) has the relevant function that permits the crew to change thrust reduction and/or acceleration altitude/height. If the aeroplane is not FMS equipped or the FMS is not fitted with the relevant function, two fixed heights should be defined and used for each of the two NADPs.

SPO.OP.125 Minimum obstacle clearance altitudes – IFR flights

Regulation (EU) No 379/2014

(a) The operator shall specify a method to establish minimum flight altitudes that provide the required terrain clearance for all route segments to be flown in IFR.

(b) The pilot-in-command shall establish minimum flight altitudes for each flight based on this method. The minimum flight altitudes shall not be lower than those published by the State overflown.

GENERAL

Commercially available information specifying minimum obstacle clearance altitudes may be used.

SPO.OP.130 Fuel/energy scheme – aeroplanes and helicopters

Regulation (EU) 2021/1296

(a) The operator shall establish, implement, and maintain a fuel/energy scheme that comprises:

(1) a fuel/energy planning and in-flight re-planning policy; and

(2) an in-flight fuel/energy management policy.

(b) The fuel/energy scheme shall:

(1) be appropriate for the type(s) of operation performed; and

(2) correspond to the capability of the operator to support its implementation.

SPO.OP.131 Fuel/energy scheme – fuel/energy planning and in flight re-planning policy – aeroplanes and helicopters

Regulation (EU) 2021/1296

(a) As part of the fuel/energy scheme, the operator shall establish a fuel/energy planning and in‑flight re-planning policy to ensure that the aircraft carries a sufficient amount of usable fuel/energy to safely complete the planned flight and to allow for deviations from the planned operation.

(b) The operator shall ensure that the fuel/energy planning of flights is based upon at least the following elements:

(1) procedures contained in the operations manual as well as:

(i) current aircraft-specific data derived from a fuel/energy consumption monitoring system or, if not available;

(ii) data provided by the aircraft manufacturer; and

(2) the operating conditions under which the flight is to be conducted including:

(i) aircraft fuel/energy consumption data;

(ii) anticipated masses;

(iii) anticipated meteorological conditions;

(iv) the effects of deferred maintenance items and/or configuration deviations; and

(v) anticipated delays.

(c) For aeroplanes, the operator shall ensure that the pre-flight calculation of the usable fuel/energy that is required for a flight includes:

(1) taxi fuel/energy that shall not be less than the amount expected to be used prior to take‑off;

(2) trip fuel/energy that shall be the amount of fuel/energy that is required to enable the aeroplane to fly from take-off, or from the point of in-flight re-planning, to landing at the destination aerodrome;

(3) contingency fuel/energy that shall be the amount of fuel/energy required to compensate for unforeseen factors;

(4) destination alternate fuel/energy

(i) when a flight is operated with at least one destination alternate aerodrome, it shall be the amount of fuel/energy required to fly from the destination aerodrome to the destination alternate aerodrome; or

(ii) when a flight is operated with no destination alternate aerodrome, it shall be the amount of fuel/energy required to hold at the destination aerodrome to compensate for the lack of a destination alternate aerodrome;

(5) final reserve fuel/energy that shall be protected to ensure a safe landing; the operator shall take into account all of the following, and in the following order of priority, to determine the quantity of the final reserve fuel/energy:

(i) the severity of the hazard to persons or property that may result from an emergency landing after fuel/energy starvation;

(ii) the likelihood of unexpected circumstances that the final reserve fuel/energy may no longer be protected;

(6) additional fuel/energy, if required by the type of operation; it shall be the amount of fuel/energy to enable the aeroplane to perform a safe landing at a fuel/energy en route alternate aerodrome (fuel/energy ERA aerodrome critical scenario) in the event of an engine failure or loss of pressurisation, whichever requires the greater amount of fuel/energy, based on the assumption that such a failure occurs at the most critical point along the route; this additional fuel/energy is required only if the minimum amount of fuel/energy that is calculated according to points (c)(2) to (c)(5) is not sufficient for such an event;

(7) extra fuel/energy to take into account anticipated delays or specific operational constraints; and

(8) discretionary fuel/energy, if required by the pilot-in-command.

(d) For helicopters, the operator shall ensure that the pre-flight calculation of the usable fuel/energy that is required for a flight includes all of the following:

(1) fuel/energy to fly to the aerodrome or operating site of intended landing;

(2) if a destination alternate is required, destination alternate fuel/energy, which shall be the amount of fuel/energy that is required to execute a missed approach at the aerodrome or operating site of intended landing, and thereafter, to fly to the specified destination alternate, approach and land; and

(3) final reserve fuel/energy, which shall be protected to ensure a safe landing; the operator shall take into account all of the following, and in the following order of priority, to determine the quantity of the final reserve fuel/energy:

(i) the severity of the hazard to persons or property that may result from an emergency landing after fuel/energy starvation; and

(ii) the likelihood of such unexpected circumstances that the final reserve fuel/energy may no longer be protected;

(4) extra fuel/energy to take into account anticipated delays or specific operational constraints; and

(5) discretionary fuel/energy, if required by the pilot-in-command.

(e) The operator shall ensure that, if a flight has to proceed to a destination aerodrome other than the one originally planned, in-flight re-planning procedures for calculating the required usable fuel/energy are available and comply with points (c)(2) to (c)(7) for aeroplanes, and point (d) for helicopters.

(f) The pilot in command shall only commence a flight or continue in the event of in-flight re‑planning, when satisfied that the aircraft carries at least the planned amount of usable fuel/energy and oil to safely complete the flight.

AEROPLANES

For the fuel planning policy, the amount of the required usable fuel for a flight should not be less than the sum of the following:

(a) taxi fuel that should take into account the local conditions at the departure aerodrome and the APU consumption;

(b) trip fuel that should include:

(1) fuel for take-off and climb from the aerodrome elevation to the initial cruising level/altitude, taking into account the expected departure routing;

(2) fuel from the top of climb to the top of descent, including any step climb/descent;

(3) fuel from the top of descent to the point where the approach procedure is initiated, taking into account the expected arrival routing; and

(4) fuel for making an approach and landing at the destination aerodrome;

(c) contingency fuel that should be:

(1) 5 % of the planned trip fuel or, in the event of in-flight re-planning, 5 % of the trip fuel for the remainder of the flight; or

(2) an amount to fly for 5 minutes at holding speed at 1 500 ft (450 m) above the destination aerodrome in standard conditions,

whichever is higher;

(d) destination alternate fuel that should be:

(1) when the aeroplane is operated with one destination alternate aerodrome:

(i) fuel for a missed approach from the applicable DA/H or MDA/H at the destination aerodrome to the missed-approach altitude, taking into account the complete missed-approach procedure;

(ii) fuel for climb from the missed-approach altitude to the cruising level/altitude, taking into account the expected departure routing;

(iii) fuel for cruising from the top of climb to the top of descent, taking into account the expected routing;

(iv) fuel for descent from the top of descent to the point where the approach is initiated, taking into account the expected arrival routing; and

(v) fuel for making an approach and landing at the destination alternate aerodrome;

(2) when the aeroplane is operated with no destination alternate aerodrome, the amount of fuel to hold for 15 minutes at 1 500 ft (450 m) in standard conditions above the destination aerodrome elevation;

(3) when the aerodrome of intended landing is an isolated aerodrome:

(i) for aeroplanes with reciprocating engines, the amount of fuel required to fly either for 45 minutes plus 15 % of the flight time planned for cruising, including the FRF, or for 2 hours, whichever is less; or

(ii) for turbine-engined aeroplanes, the amount of fuel required to fly for 2 hours with normal cruise consumption above the destination aerodrome, including the FRF.

(e) FRF that should not be less than the fuel required to fly:

(1) for 10 minutes at normal cruising altitude under VFR by day, taking off and landing at the same aerodrome/landing site, and always remaining within sight of that aerodrome/landing site;

(2) for 30 minutes at normal cruising altitude for other VFR flights by day; and

(3) for 45 minutes at normal cruising altitude under VFR by night, and under IFR for aeroplanes with reciprocating engines; and

(4) for 30 minutes at holding speed at 1 500 ft (450 m) above the aerodrome elevation in standard conditions, which is calculated according to the estimated mass on arrival under VFR by night and under IFR for turbine-engined aeroplanes,

Note: When the operator follows point (e)(1) for the FRF, the operator should specify in the standard operating procedures (SOPs):

the type of operation in which such reduced RFR may be used; and

the methods of reading and calculating the remaining fuel.

(f) additional fuel that should be the amount of fuel that allows the aeroplane to proceed, in the event of an engine failure or loss of pressurisation, from the most critical point along the route to a fuel en route alternate (fuel ERA) aerodrome in the relevant aircraft configuration, hold there for 15 minutes at 1 500 ft (450 m) above the aerodrome elevation in standard conditions, make an approach, and land;

(g) extra fuel if there are anticipated delays or specific operational constraints; and

(h) discretionary fuel, if required by the pilot-in-command.

HELICOPTERS

(i) The FRF should not be less than the fuel required to fly:

(1) for 10 minutes at best-range speed, provided that the helicopter remains within 25 NM of the aerodrome/operating site of departure, under VFR;

(2) for 20 minutes at best-range speed for flights other than the ones referred to in (i)(1) under VFR; and

(3) for 30 minutes at holding speed at 1 500 ft (450 m) above the destination or destination alternate under IFR.

(j) If point (i)(1) is used for the FRF, the operator should specify in the SOPs:

(1) the type of operation in which such reduced FRF may be used; and

(2) methods of reading and calculating the remaining fuel.

REDUCED RESERVE FUEL

(a) The operator should specify in the SOP:

(1) the type of activity where such reduced reserve fuel may be used; and

(2) methods of reading and calculating the remaining fuel.

(b) Refuelling facilities should be available at the aerodrome/operating site.

SPO.OP.135 Safety briefing

Regulation (EU) No 379/2014

(a) The operator shall ensure that, prior to take-off task specialists are given a briefing on:

(1) emergency equipment and procedures;

(2) operational procedures associated with the specialised task before each flight or series of flights

(b) The briefing referred to in (a)(2) may be replaced by an initial and recurrent training programme. In such case the operator shall also define recency requirements.

TASK SPECIALISTS — GENERAL

(a) The purpose of operational briefing is to ensure that task specialists are familiar with all aspects of the operation, including their responsibilities.

(b) Such briefing should include, as appropriate:

(1) behaviour on the ground and in-flight, including emergency procedures;

(2) procedures for boarding and disembarking;

(3) procedures for loading and unloading the aircraft;

(4) use of doors in normal and emergency operations;

(5) use of communication equipment and hand signals;

(6) precautions in case of a landing on sloping ground; and

(7) in addition to the items listed from (b)(1) to (b)(6) before take-off:

(i) location of emergency exits;

(ii) restrictions regarding smoking;

(iii) restrictions regarding the use of portable electronic equipment; and

(iv) stowage of tools and hand baggage.

(c) The briefing may be given as a verbal presentation or by issuing the appropriate procedures and instructions in written form. Before commencement of the flight, their understanding should be confirmed.

SPO.OP.140 Flight preparation

Regulation (EU) 2021/2237

(a) Before commencing a flight, the pilot-in-command shall ascertain by every reasonable means available that the space-based facilities, ground and/or water facilities, including communication facilities and navigation aids available and directly required on such flight, for the safe operation of the aircraft, are adequate for the type of operation under which the flight is to be conducted.

(b) Before commencing a flight, the pilot-in-command shall be familiar with all available meteorological information appropriate to the intended flight. Preparation for a flight away from the vicinity of the place of departure, and for every flight under IFR, shall include:

(1) a study of the available current meteorological reports and forecasts; and

(2) the planning of an alternative course of action to provide for the eventuality that the flight cannot be completed as planned, because of meteorological conditions.

AMC1 SPO.OP.140(a) Flight preparation

ED Decision 2023/004/R

ADEQUACY OF GROUND FACILITIES

When deciding on the adequacy of facilities and services available at an aerodrome of intended operation, the operator should:

  1.            consult the aeronautical information publication (AIP) for information on the availability of rescue and firefighting services (RFFS) at the aerodrome of intended operation; and
  2.            assess the level of safety risk that is associated with the aircraft type and nature of the operation in relation to the availability of RFFS.

GM1 SPO.OP.140(a) Flight preparation

ED Decision 2023/004/R

ADEQUACY OF GROUND FACILITIES — SAFETY RISK ASSESSMENT OF OPERATIONS WITHOUT RESCUE AND FIREFIGHTING SERVICES AT THE AERODROME OF INTENDED OPERATION

To operate at an aerodrome with downgraded or unavailable rescue and firefighting services (RFFS), the operator may consider including in its operations manual, for each aircraft type, certain criteria to be used when conducting a safety risk assessment of such operations. For aircraft in rescue and firefighting (RFF) category 3 and higher, the conditions under which the pilot-in-command may decide to conduct a flight may include, but not be limited to the following:

  1.            acceptable downgrades of RFFS for planning and in-flight purposes such as departure, destination, and alternate aerodromes;
  2.            aircraft characteristics related to mass, landing speed, fuel capacity;
  3.             possible limitation to daytime only or a certain time of the day (due to fatigue);
  4.            weather constraints;
  5.            aerodromes that are unacceptable with unavailable or downgraded RFFS.

SPO.OP.143 Destination alternate aerodromes planning minima — aeroplanes

Regulation (EU) 2021/2237

An aerodrome shall not be specified as a destination alternate aerodrome unless the available current meteorological information indicates, for the period from 1 hour before until 1 hour after the estimated time of arrival, or from the actual time of departure to 1 hour after the estimated time of arrival, whichever is the shorter period,

(a) for an alternate aerodrome with an available instrument approach operation with DH less than 250 ft,

(1) a ceiling of at least 200 ft above the DH or MDH associated with the instrument approach operation; and

(2) a visibility of at least the higher of 1 500 m and 800 m above the instrument approach operation RVR/VIS minima; or

(b) for an alternate aerodrome with an instrument approach operation with DH or MDH 250 ft or more,

(1) a ceiling of at least 400 ft above the DH or MDH associated with the instrument approach operation; and

(2) a visibility of at least 3 000 m; or

(c) for an alternate aerodrome without an instrument approach procedure,

(1) a ceiling of at least the higher of 2 000 ft and the minimum safe IFR height; and

(2) a visibility of at least 5 000 m.

SPO.OP.144 Destination alternate aerodrome planning minima — helicopters

Regulation (EU) 2021/2237

The operator shall only select an aerodrome as a destination alternate aerodrome if the available current meteorological information indicates, for the period from 1 hour before until 1 hour after the estimated time of arrival, or from the actual time of departure to 1 hour after the estimated time of arrival, whichever is the shorter period,

(a) for an alternate aerodrome with an IAP:

(1) a ceiling of at least 200 ft above the DH or MDH associated with the IAP; and

(2) a visibility of at least 1 500 m by day or 3 000 m by night; or

(b) for an alternate aerodrome without an IAP:

(1) a ceiling of at least 2 000 ft or the minimum safe IFR height, whichever is greater; and

(2) a visibility of at least 1 500 m by day or 3 000 m by night.

SPO.OP.145 Take-off alternate aerodromes — complex motor‑powered aeroplanes

Regulation (EU) 2021/2237

(a) For IFR flights, the pilot-in-command shall specify at least one weather-permissible take-off alternate aerodrome in the flight plan if the meteorological conditions at the aerodrome of departure are at or below the applicable aerodrome operating minima or if it would not be possible to return to the aerodrome of departure for other reasons.

(b) The take-off alternate aerodrome shall be located within the following distance from the aerodrome of departure:

(1) for aeroplanes having two engines, not more than a distance equivalent to a flight time of 1 hour at the single-engine cruise speed in still air standard conditions; and

(2) for aeroplanes having three or more engines, not more than a distance equivalent to a flight time of 2 hours at the one-engine-inoperative (OEI) cruise speed according to the AFM in still air standard conditions.

(c) For an aerodrome to be selected as a take-off alternate aerodrome the available information shall indicate that, at the estimated time of use, the conditions will be at or above the aerodrome operating minima for that operation.

SPO.OP.150 Destination alternate aerodromes – aeroplanes

Regulation (EU) 2021/1296

For IFR flights, the pilot-in-command shall specify at least one weather-permissible destination alternate aerodrome in the flight plan, unless:

(a) the available current meteorological information indicates that, for the period from 1 hour before until 1 hour after the estimated time of arrival, or from the actual time of departure to 1 hour after the estimated time of arrival, whichever is the shorter period, the approach and landing may be made under visual meteorological conditions (VMC); or

(b) the place of intended landing is designated as an isolated aerodrome and:

(1) an instrument approach procedure is prescribed for the aerodrome of intended landing; and

(2) available current meteorological information indicates that both following meteorological conditions will exist from 2 hours before to 2 hours after the estimated time of arrival, or from the actual time of departure to 2 hours after the estimated time of arrival whichever is the shorter period:

(i) a cloud base of at least 300 m (1 000 ft) above the minimum associated with the instrument approach procedure;

(ii) visibility of at least 5,5 km or of 4 km more than the minimum associated with the procedure.

SPO.OP.151 Destination alternate aerodromes – helicopters

Regulation (EU) 2016/1199

For IFR flights, the pilot-in-command shall specify at least one weather-permissible destination alternate aerodrome in the flight plan, unless:

(a) an instrument approach procedure is prescribed for the aerodrome of intended landing and the available current meteorological information indicates that the following meteorological conditions will exist from 2 hours before to 2 hours after the estimated time of arrival, or from the actual time of departure to 2 hours after the estimated time of arrival, whichever is the shorter period:

(1) a cloud base of at least 120 m (400 ft) above the minimum associated with the instrument approach procedure; and

(2) visibility of at least 1 500 m more than the minimum associated with the procedure; or

(b) the place of intended landing is isolated and:

(1) an instrument approach procedure is prescribed for the aerodrome of intended landing;

(2) available current meteorological information indicates that the following meteorological conditions will exist from 2 hours before to 2 hours after the estimated time of arrival:

(i) the cloud base is at least 120 m (400 ft) above the minimum associated with the instrument approach procedure;

(ii) visibility is at least 1 500 m more than the minimum associated with the procedure.

SPO.OP.152 Destination aerodromes – instrument approach operations

Regulation (EU) 2016/1199

The pilot-in-command shall ensure that sufficient means are available to navigate and land at the destination aerodrome or at any destination alternate aerodrome in the case of loss of capability for the intended approach and landing operation.

PBN OPERATIONS

(a) When the operator intends to use PBN, the operator should either:

(1) demonstrate that the GNSS is robust against loss of capability; or

(2) select an aerodrome as a destination alternate aerodrome only if an IAP that does not rely on a GNSS is available either at that aerodrome or at the destination aerodrome.

GNSS ROBUSTNESS AGAINST LOSS OF CAPABILITY — HELICOPTERS

(b) The operator may demonstrate robustness against the loss of capability of the GNSS if all of the following criteria are met:

(1) At flight planning stage, SBAS or GBAS are expected to be available and used.

(2) The failure of a single receiver or system should not compromise the navigation capability required for the intended instrument approach.

(3) The temporary jamming of all GNSS frequencies should not compromise the navigation capability required for the intended route. The operator should provide a procedure to deal with such cases unless other sensors are available to continue on the intended route.

(4) The duration of a jamming event should be determined as follows:

(i) Considering the average speed and height of a helicopter flight, the duration of a jamming event may be considered to be less than 2 minutes.

(ii) The time needed for the GNSS system to re-start and provide the aircraft position and navigation guidance should also be considered.

(iii) Based on (i) and (ii) above, the operator should establish the duration of the loss of GNSS navigation data due to jamming. This duration should be no less than 3 minutes, and may be no longer than 4 minutes.

(5) The operator should ensure resilience to jamming for the duration determined in (4) above, as follows:

(i) If the altitude of obstacles on both sides of the flight path are higher than the planned altitude for a given segment of the flight, the operator should ensure no excessive drift on either side by relying on navigation sensors such as an inertial system with performance in accordance with the intended function.

(ii) If (i) does not apply and the operator cannot rely on sensors other than GNSS, the operator should develop a procedure to ensure that a drift from the intended route during the jamming event has no adverse consequences on the safety of the flight. This procedure may involve air traffic services.

(6) The operator should ensure that no space weather event is predicted to disrupt the GNSS reliability and integrity at both the destination and the alternate aerodromes.

(7) The operator should verify the availability of RAIM for all phases of flight based on GNSS, including navigation to the alternate aerodrome.

(8) The operator’s MEL should reflect the elements in points (b)(1) and (b)(2).

OPERATIONAL CREDITS

(c) To comply with point SPO.OP.153, when the operator intends to use ‘operational credits’ (e.g. EFVS, SA CAT I, etc.), the operator should select an aerodrome as destination alternate aerodrome only if an approach procedure that does not rely on the same ‘operational credit’ is available either at that aerodrome or at the destination aerodrome.

INTENT OF AMC1

(a) The limitation applies only to destination alternate aerodromes for flights when a destination alternate aerodrome is required. A take-off or en route alternate aerodrome with instrument approach procedures relying on GNSS may be planned without restrictions. A destination aerodrome with all instrument approach procedures relying solely on GNSS may be used without a destination alternate aerodrome if the conditions for a flight without a destination alternate aerodrome are met.

(b) The term ‘available’ means that the procedure can be used in the planning stage and complies with planning minima requirements.

GNSS ROBUSTNESS AGAINST LOSS OF CAPABILITY — HELICOPTERS

(a) Redundancy of on-board systems ensures that no single on-board equipment failure (e.g. antenna, GNSS receiver, FMS, or navigation display failure) results in the loss of the GNSS capability.

(b) Any shadowing of the GNSS signal or jamming of all GNSS frequencies from the ground is expected to be of a very short duration and affect a very small area. Additional sensors or functions such as inertial coasting may be used during jamming events. Jamming should be considered on all segments of the intended route, including the approach.

(c) The availability of GNSS signals can be compromised if space weather events cause ‘loss of lock’ conditions and more than one satellite signal may be lost on a given GNSS frequency. Until space weather forecasts are available, the operator may use ‘nowcasts’ as short-term predictions for helicopter flights of short durations.

(d) SBAS also contributes to mitigate space weather effects, both by providing integrity messages and by correcting ionosphere-induced errors.

(e) Even though SBAS should be available and used, RAIM should remain available autonomously. In case of loss of the SBAS, the route and the approach to the destination or alternate should still be flown with an available RAIM function.

(f) When available, GNSS based on more than one constellation and more than one frequency may provide better integrity and redundancy regarding failures in the space segment of the GNSS, jamming, and resilience to space weather events.

SPO.OP.155 Refuelling with persons embarking, on board or disembarking

Regulation (EU) 2021/1296

(a) The aircraft shall not be refuelled with aviation gasoline (AVGAS) or wide-cut type fuel or a mixture of these types of fuel, when persons are embarking, on board or disembarking.

(b) For all other types of fuel/energy, necessary precautions shall be taken and the aircraft shall be properly manned by qualified personnel ready to initiate and direct an evacuation of the aircraft by the most practical and expeditious means available.

OPERATIONAL PROCEDURES — AEROPLANES

(a) Operational procedures should specify that at least the following precautions are taken:

(1) One qualified person should remain at a specified location during fuelling operations with persons on board. This qualified person should be capable of handling emergency procedures concerning fire protection and firefighting, handling communications and initiating and directing an evacuation.

(2) Two-way communication should be established and should remain available by the aeroplane's inter-communication system or other suitable means between the ground crew supervising the refuelling and the qualified personnel on board the aeroplane; the involved personnel should remain within easy reach of the system of communication.

(3) Flight crew members and task specialists should be warned that refuelling will take place.

(4) ‘Fasten seat belts’ signs should be off.

(5) ‘No smoking’ signs should be on, together with interior lighting to enable emergency exits to be identified.

(6) Task specialists should be instructed to unfasten their seat belts and refrain from smoking.

(7) If the presence of fuel vapour is detected inside the aeroplane, or any other hazard arises during refuelling, fuelling should be stopped immediately.

(8) The ground area beneath the exits intended for emergency evacuation and slide deployment areas should be kept clear.

(9) Provision should be made for a safe and rapid evacuation.

OPERATIONAL PROCEDURES — helicopters

When the helicopter rotors are stopped, the efficiency and speed of task specialists disembarking from and re-embarking on board helicopters is such that disembarking before refuelling and re-embarking after refuelling is the general practice. However, if such operations are needed, the operator should refer to AMC1 SPO.OP.157 and AMC2 SPO.OP.157. Operational procedures to be described in the operations manual (OM) should specify that at least the relevant precautions of the aforementioned AMC are taken.

AIRCRAFT REFUELLING PROVISIONS AND GUIDANCE ON SAFE REFUELLING PRACTICES

Provisions concerning aircraft refuelling are contained in Volume I (Aerodrome Design and Operations) of ICAO Annex 14 (Aerodromes), and guidance on safe refuelling practices is contained in Parts 1 and 8 of the ICAO Airport Services Manual (Doc 9137).

SPO.OP.157 Refuelling with engine(s) and/or rotors turning – helicopters

Regulation (EU) 2021/1296

(a) Refuelling with engine(s) and/or rotors turning shall only be conducted:

(1) with no task specialists embarking or disembarking;

(2) if the operator of the aerodrome or operating site allows such operations;

(3) in accordance with any specific procedures and limitations in the aircraft flight manual (AFM);

(4) with JET A or JET A-1 fuel types; and

(5) in the presence of the appropriate rescue and firefighting (RFF) facilities or equipment.

(b) The operator shall assess the risks associated with refuelling with engine(s) and/or rotors turning.

(c) The operator shall establish appropriate procedures to be followed by all involved personnel, such as crew members, task specialists, and ground operations personnel.

(d) The operator shall ensure that its crew members, ground operations personnel, as well as any task specialist involved in the procedures, are appropriately trained.

(e) The operator shall ensure that the helicopter refuelling procedures with engine(s) and/or rotors turning are specified in the operations manual.

OPERATIONAL PROCEDURES — NO TASK SPECIALISTS ON BOARD

Operational procedures in the OM should specify that at least the following precautions are taken:

(a) all necessary information should be exchanged in advance with the aerodrome operator, operating-site operator, and refuelling operator;

(b) the procedures to be used by crew members should be defined;

(c) the procedures to be used by the operator’s ground operations personnel that may be in charge of refuelling or assisting in emergency evacuations should be described;

(d) the operator’s training programmes for crew members and for the operator’s ground operations personnel should be described;

(e) the minimum distance between the helicopter turning parts and the refuelling vehicle or installations should be defined when the refuelling takes place outside an aerodrome or at an aerodrome where there are no such limitations;

(f) besides any rescue and firefighting services (RFFSs) that are required to be available by aerodrome regulations, an additional handheld fire extinguisher with the equivalent of 5 kg of dry powder should be immediately available and ready for use;

(g) a means for a two-way communication between the crew and the person in charge of refuelling should be defined and established;

(h) if fuel vapour is detected inside the helicopter, or any other hazard arises, refuelling/defuelling should be stopped immediately;

(i) one pilot should stay at the controls, constantly monitor the refuelling, and be ready to shut off the engines and evacuate at all times; and

(j) any additional precautions should be taken, as determined by the risk assessment.

OPERATIONAL PROCEDURES — TASK SPECIALISTS ON BOARD

In addition to AMC1 SPO.OP.157, for refuelling with task specialists on board, operational procedures in the OM should specify that at least the following precautions are taken:

(a) the positioning of the helicopter and the corresponding helicopter evacuation strategy should be defined taking into account the wind as well as the refuelling facilities or vehicles;

(b) on a heliport, the ground area beneath the exits that are intended for emergency evacuation should be kept clear;

(c) an additional task specialist briefing as well as instructions should be defined, and the ‘No smoking’ signs should be on unless ‘No smoking’ placards are installed;

(d) interior lighting should be set to enable identification of emergency exits;

(e) the use of doors during refuelling should be defined: doors on the refuelling side should remain closed, while doors on the opposite side should remain unlocked or, weather permitting, open unless otherwise specified in the AFM; and

(f) at least one suitable person or appropriately trained task specialist capable of implementing emergency procedures for firefighting, communications, as well for initiating and directing an evacuation, should remain at a specified location; this person should not be the qualified pilot at the controls or the person performing the refuelling.

RISK ASSESSMENT

The risk assessment should explain why it is not practical to refuel with the engine(s) and rotors stopped, identify the additional hazards, and describe how the additional risks are controlled. Helicopter offshore operations (HOFO) are typical operations where the benefits should outweigh the risks if mitigation measures are taken.

Guidance on safe refuelling practices is contained in ICAO Doc 9137 Airport Services Manual, Parts 1 and 8.

The operator’s risk assessment may include, but not be limited to, the following risks, hazards and mitigation measures:

(a) risk related to refuelling with rotors turning;

(b) risk related to the shutting down of the engines, including the risk of failures during start-up;

(c) environmental conditions, such as wind limitations, displacement of exhaust gases, and blade sailing;

(d) risk related to human factors and fatigue management, especially for single-pilot operations for long periods of time;

(e) risk mitigation, such as the safety features of the fuel installation, rescue and firefighting (RFF) capability, number of personnel members available, ease of emergency evacuation of the helicopter, etc.;

(f) assessment of the use of radio transmitting equipment;

(g) determination of the use of seat belts; and

(h) review of the portable electronic device (PED) policy.

SPO.OP.160 Use of headset

Regulation (EU) 2018/394

Each flight crew member required to be on duty in the flight crew compartment shall wear a headset with boom microphone or equivalent and use it as the primary device to communicate with ATS, other crew members and task specialists.

SPO.OP.165 Smoking

Regulation (EU) No 379/2014

The pilot-in-command shall not allow smoking on board or during refuelling or defuelling of the aircraft.

SPO.OP.170 Meteorological conditions

Regulation (EU) 2021/2237

(a) The pilot-in-command shall only commence or continue a VFR flight if the latest available meteorological information indicates that the meteorological conditions along the route and at the intended destination at the estimated time of use will be at or above the applicable VFR operating minima.

(b) The pilot-in-command shall only commence or continue an IFR flight towards the planned destination aerodrome if the latest available meteorological information indicates that, at the estimated time of arrival, the meteorological conditions at the destination or at least one destination alternate aerodrome are at or above the applicable aerodrome operating minima.

(c) If a flight contains VFR and IFR segments, the meteorological information referred to in (a) and (b) shall be applicable as far as relevant.

EVALUATION OF METEOROLOGICAL CONDITIONS

Pilots should carefully evaluate the available meteorological information relevant to the proposed flight, such as applicable surface observations, winds and temperatures aloft, terminal and area forecasts, air meteorological information reports (AIRMETs), significant meteorological information (SIGMET) and pilot reports. The ultimate decision whether, when, and where to make the flight rests with the pilot-in-command. Pilots should continue to re-evaluate changing weather conditions.

APPLICATION OF AERODROME FORECASTS (TAF & TREND)

Where a terminal area forecast (TAF) or meteorological aerodrome or aeronautical report (METAR) with landing forecast (TREND) is used as forecast, the following criteria should be used:

(a) From the start of a TAF validity period up to the time of applicability of the first subsequent 'FM...' or 'BECMG' or, if no 'FM' or BECMG' is given, up to the end of the validity period of the TAF, the prevailing weather conditions forecast in the initial part of the TAF should be applied.

(b) From the time of observation of a METAR up to the time of applicability of the first subsequent 'FM...' or 'BECMG' or, if no 'FM' or BECMG' is given, up to the end of the validity period of the TREND, the prevailing weather conditions forecast in the METAR should be applied.

(c) Following FM (alone) or BECMG AT, any specified change should be applied from the time of the change.

(d) Following BECMG (alone), BECMG FM, BECMG TL, BECMG FM TL:

(1) in the case of deterioration, any specified change should be applied from the start of the change; and

(2) in the case of improvement, any specified change should be applied from the end of the change.

(e) In a period indicated by TEMPO (alone), TEMPO FM, TEMPO TL, TEMPO FM TL, PROB30/40 (alone):

(1) deteriorations associated with persistent conditions in connection with e.g. haze, mist, fog, dust/sandstorm, continuous precipitation should be applied;

(2) deteriorations associated with transient/showery conditions in connection with short-lived weather phenomena, e.g. thunderstorms, showers may be ignored; and

(3) improvements should in all cases be disregarded.

(f) In a period indicated by PROB30/40 TEMPO:

(1) deteriorations may be disregarded; and

(2) improvements should be disregarded.

Note:  Abbreviations used in the context of this AMC are as follows:

FM:    from

BECMG:  becoming

AT:    at

TL:    till

TEMPO:  temporarily

PROB:  probability

CONTINUATION OF A FLIGHT

In the case of in-flight re-planning, continuation of a flight refers to the point from which a revised flight plan applies.

SPO.OP.175 Ice and other contaminants – ground procedures

Regulation (EU) No 379/2014

(a) The pilot-in-command shall only commence take-off if the aircraft is clear of any deposit that might adversely affect the performance or controllability of the aircraft, except as permitted in the AFM.

(b) In the case of operations with complex motor-powered aircraft, the operator shall establish procedures to be followed when ground de-icing and anti-icing and related inspections of the aircraft are necessary to allow the safe operation of the aircraft.

TERMINOLOGY

Terms used in the context of de-icing/anti-icing have the meaning defined in the following subparagraphs.

(a) ‘Anti-icing’: the process of protecting the aircraft to prevent contamination due to existing or expected weather, typically by applying anti-icing fluids on uncontaminated aircraft surfaces.

(b) ‘Anti-icing fluid’ includes, but is not limited to, the following:

(1) Typically, Type II, III or IV fluid (neat or diluted), normally applied unheated (*);

(2) Type I fluid/water mixture heated to minimum 60°C at the nozzle.

  (*) When de-icing and anti-icing in a one-step process, Type II and Type IV fluids are typically applied diluted and heated.

(c) ‘Clear ice’: a coating of ice, generally clear and smooth, but with some air pockets. It forms on exposed objects, the temperatures of which are at, below or slightly above the freezing temperature, by the freezing of super-cooled drizzle, droplets or raindrops. Clear ice is very difficult to be detected visually.

(d) ‘Cold soaked surface frost (CSSF)’: frost developed on cold soaked aircraft surfaces by sublimation of air humidity. This effect can take place at ambient temperatures above 0 °C. Cold soaked aircraft surfaces are more common on aircraft that have recently landed. External surfaces of fuel tanks (e.g. wing skins) are typical areas of CSSF formation (known in this case as cold soaked fuel frost (CSFF)), due to the thermal inertia of very cold fuel that remains on the tanks after landing.

(e) ‘Conditions conducive to aircraft icing on the ground’: freezing fog, freezing precipitation, frost, rain or high humidity (on cold soaked wings), hail, ice pellets, snow or mixed rain and snow, etc.

(f) ‘Contamination’: all forms of frozen or semi-frozen deposits on an aircraft, such as frost, snow, slush or ice.

(g) ‘Contamination check’: a check of the aircraft for contamination to establish the need for de-icing.

(h) ‘De-icing’: the process of eliminating frozen contamination from aircraft surfaces, typically by applying de-icing fluids.

(i) ‘De-icing fluid’: such fluid includes, but is not limited to, the following:

(1) Heated water;

(2) Preferably, Type I fluid (neat or diluted (typically));

(3) Type II, III or IV fluid (neat or diluted).

The de-icing fluid is normally applied heated to ensure maximum efficiency and its freezing point should be at the outside air temperature (OAT) or below.

(j) ‘De-icing/anti-icing’: this is the combination of de-icing and anti-icing performed in either one or two steps.

(k) ‘Ground ice detection system (GIDS)’: a system used during aircraft ground operations to inform the personnel involved in the operation and/or the flight crew about the presence of frost, ice, snow or slush on the aircraft surfaces.

(l) ‘Holdover time (HOT)’: the period of time during which an anti-icing fluid provides protection against frozen contamination to the treated aircraft surfaces. It depends among other variables, on the type and intensity of the precipitation, OAT, wind, the particular fluid (or fluid Type) and aircraft design and aircraft configuration during the treatment.

(m) ‘Liquid water equivalent (LWE) system’: an automated weather measurement system that determines the LWE precipitation rate in conditions of frozen or freezing precipitation. The system provides flight crew with continuously updated information on the fluid protection capability under varying weather conditions.

(n) ‘Lowest operational use temperature (LOUT)’: the lowest temperature at which a fluid has been tested and certified as acceptable in accordance with the appropriate aerodynamic acceptance test whilst still maintaining a freezing point buffer of not less than:

(1) 10°C for a Type I fluid; or

(2) 7°C for Type II, III or IV fluids.

(o) ‘Post-treatment check’, ‘Post- de-icing check’ or ‘Post- de-icing/anti-icing check’: an external check of the aircraft after de-icing and/or anti-icing treatment accomplished by qualified staff and from suitably elevated observation points (e.g. from the de-icing/anti-icing equipment itself or other elevated equipment) to ensure that the aircraft is free from frost, ice, snow, or slush.

(p) ‘Pre-take-off check’: The flight crew should continuously monitor the weather conditions after the de-icing/anti-icing treatment to assess whether the applied holdover time is still appropriate. Within the aircraft’s HOT and prior to take-off, the flight crew should check the aircraft’s wings or representative aircraft surfaces for frozen contaminants.

(q) ‘Pre-take-off contamination check’: a check of the treated surfaces for contamination, performed when the HOT has been exceeded or if any doubt exists regarding the continued effectiveness of the applied anti-icing treatment. It is normally accomplished externally, just before commencement of the take-off run.

ANTI-ICING CODES

(r) Upon completion of the anti-icing treatment, a qualified staff provides the anti-icing code to the flight crew as follows: ‘the fluid Type/the fluid name (except for Type I)/concentration (except for Type I)/local time at start of anti-icing/date (optional)/the statement ‘post- de-icing/anti-icing check completed’ (if check completed). Example:

 ‘TYPE II / MANUFACTURER, BRAND X / 75% / 1335 / 15FEB20 / POST- DE-ICING/ANTI-ICING CHECK COMPLETED’.

(s) When a two-step de-icing/anti-icing operation has been carried out, the anti-icing code should be determined by the second step fluid.

DE-ICING/ANTI-ICING — PROCEDURES

(a) De-icing and/or anti-icing procedures should take into account manufacturer’s recommendations, including those that are type-specific, and should cover:

(1) contamination checks, including detection of clear ice and under-wing frost; limits on the thickness/area of contamination published in the AFM or other manufacturers’ documentation should be followed;

(2) procedures to be followed if de-icing and/or anti-icing procedures are interrupted or unsuccessful;

(3) post-treatment checks;

(4) pre-take-off checks;

(5) pre-take-off contamination checks;

(6) the recording of any incidents relating to de-icing and/or anti-icing; and

(7) the responsibilities of all personnel involved in de-icing and/or anti-icing.

(b) Operator’s procedures should ensure the following:

(1) When aircraft surfaces are contaminated by ice, frost, slush or snow, they are de-iced prior to take-off according to the prevailing conditions. Removal of contaminants may be performed with mechanical tools, fluids (including hot water), infrared heat or forced air, taking account of aircraft type-specific provisions.

(2) Account is taken of the wing skin temperature versus OAT, as this may affect:

(i) the need to carry out aircraft de-icing and/or anti-icing; and/or

(ii) the performance of the de-icing/anti-icing fluids.

(3) When freezing precipitation occurs or there is a risk of freezing precipitation occurring that would contaminate the surfaces at the time of take-off, aircraft surfaces should be anti-iced. Anti-icing fluids (neat or diluted) should not be applied at OAT below their LOUT. If both de-icing and anti-icing are required, the procedure may be performed in a one- or two-step process, depending upon weather conditions, available equipment, available fluids and the desired HOT. One-step de-icing/anti-icing means that de-icing and anti-icing are carried out at the same time, using a mixture of de-icing/anti-icing fluid and water. Two-step de-icing/anti-icing means that de-icing and anti-icing are carried out in two separate steps. The aircraft is first de-iced using heated water only or a heated mixture of de-icing/anti-icing fluid and water. After completion of the de-icing operation, a layer of a mixture of de-icing/anti-icing fluid and water, or of de-icing /anti-icing fluid only, is sprayed over the aircraft surfaces. The second step will be taken before the first step fluid freezes (typically within 3 minutes but severe conditions may shorten this) and, if necessary, area by area.

(4) When an aircraft is anti-iced and a longer HOT is needed/desired, the use of a less diluted thickened fluid may be considered.

(5) All restrictions relative to OAT and fluid application (including, but not necessarily limited to, temperature and pressure) published by the fluid manufacturer and/or aircraft manufacturer, are followed and procedures, limitations and recommendations to prevent the formation of fluid residues are followed.

(6) During conditions conducive to aircraft icing on the ground or after de-icing and/or anti-icing, an aircraft is not dispatched for departure unless it has been given a contamination check or a post-treatment check by a trained and qualified person. This check should cover all treated surfaces of the aircraft and be performed from points offering sufficient visibility to these parts. To ensure that there is no clear ice on suspect areas, it may also be necessary to make a physical check (e.g. tactile).

(7) The required entry is made in the technical log.

(8) The commander continually monitors the environmental situation after the performed treatment. Prior to take-off, he/she performs a pre-take-off check, which is an assessment of whether the applied HOT is still appropriate. This pre-take-off check includes, but is not limited to, factors such as precipitation, wind and OAT.

(9) If any doubt exists as to whether a deposit may adversely affect the aircraft’s performance and/or controllability characteristics, the commander should arrange for a re-treatment or a pre-take-off contamination check to be performed in order to verify that the aircraft’s surfaces are free of contamination. Special methods and/or equipment may be necessary to perform this check, especially at night time or in extremely adverse weather conditions. If this check cannot be performed just before take-off, re-treatment should be applied.

(10) When re-treatment is necessary, any residue of the previous treatment should be removed, and a completely new de-icing/anti-icing treatment should be applied.

(11) When a ground ice detection system (GIDS) is used to perform an aircraft surfaces check prior to and/or after a treatment, the use of GIDS by suitably trained personnel should be part of the procedure.

(c) Special operational considerations

(1) When using thickened de-icing/anti-icing fluids, the operator should consider a two-step deicing/anti-icing procedure, the first step preferably with hot water and/or un-thickened fluids.

(2) The use of de-icing/anti-icing fluids should be in accordance with the aircraft manufacturer’s documentation. This is particularly important for thickened fluids to assure sufficient flow-off during take-off. Avoid applying excessive thickened fluid on the horizontal tail of aircraft with unpowered elevator controls.

(3) The operator should comply with any type-specific operational provision(s), such as an aircraft mass decrease and/or a take-off speed increase associated with a fluid application.

(4) The operator should take into account any flight handling procedures (stick force, rotation speed and rate, take-off speed, aircraft attitude etc.) laid down by the aircraft manufacturer when associated with a fluid application.

(5) The limitations or handling procedures resulting from (c)(3) and/or (c)(4) above should be part of the flight crew pre take-off briefing.

(d) Communications

(1) Before aircraft treatment. When the aircraft is to be treated with the flight crew on board, the flight and personnel involved in the operation should confirm the fluid to be used, the extent of treatment required and any aircraft type-specific procedure(s) to be used. Any other information needed to apply the HOT tables should be exchanged.

(2) Anti-icing code. The operator’s procedures should include an anti-icing code, which indicates the treatment the aircraft has received. This code provides the flight crew with the minimum details necessary to estimate a HOT and confirms that the aircraft is free of contamination.

(3) After treatment. Before reconfiguring or moving the aircraft, the flight crew should receive a confirmation from the qualified personnel involved in the operation that all de-icing and/or anti-icing operations are complete and that all personnel and equipment are clear of the aircraft.

(e) Holdover protection & LWE systems

The operator should publish in the operations manual (OM), when required, the HOTs in the form of a table or a diagram, to account for the various types of ground icing conditions and the different types and concentrations of fluids used. However, the times of protection shown in these tables are to be used as guidelines only and are normally used in conjunction with the pre-take-off check.

An operator may choose to operate using LWE systems instead of HOT tables whenever the required means for using these systems are in place.

(f) Training

The operator’s initial and recurrent de-icing training programmes (including communication training) for flight crew and for other personnel involved in de-icing operations should include additional training if any of the following is introduced:

(1) a new method, procedure and/or technique;

(2) a new type of fluid and/or equipment; or

(3) a new type of aircraft.

(g) Contracting

When the operator contracts de-icing/anti-icing functions, the operator should ensure that the contractor complies with the operator’s training/qualification procedures, together with any specific procedures in respect of:

(1) roles and responsibilities;

(2) de-icing and/or anti-icing methods and procedures;

(3) fluids to be used, including precautions for storage, preparation for use and chemical incompatibilities;

(4) specific aircraft provisions (e.g. no-spray areas, propeller/engine de-icing, APU operation etc.);

(5) different checks to be conducted; and

(6) procedures for communications with flight crew and any other third party involved.

(h) Special maintenance considerations

(1) General

The operator should take proper account of the possible side-effects of fluid use. Such effects may include, but are not necessarily limited to, dried and/or re-hydrated residues, corrosion and the removal of lubricants.

(2) Special considerations regarding residues of dried fluids

The operator should establish procedures to prevent or detect and remove residues of dried fluid. If necessary, the operator should establish appropriate inspection intervals based on the recommendations of the airframe manufacturers and/or the operator’s own experience:

(i) Dried fluid residues

Dried fluid residues could occur when surfaces have been treated and the aircraft has not subsequently been flown and has not been subject to precipitation. The fluid may then have dried on the surfaces.

(ii) Re-hydrated fluid residues

Repetitive application of thickened de-icing/anti-icing fluids may lead to the subsequent formation/build-up of a dried residue in aerodynamically quiet areas, such as cavities and gaps. This residue may re-hydrate if exposed to high humidity conditions, precipitation, washing, etc., and increase to many times its original size/volume. This residue will freeze if exposed to conditions at or below 0 °C. This may cause moving parts, such as elevators, ailerons, and flap actuating mechanisms to stiffen or jam in-flight. Re-hydrated residues may also form on exterior surfaces, which can reduce lift, increase drag and stall speed. Re-hydrated residues may also collect inside control surface structures and cause clogging of drain holes or imbalances to flight controls. Residues may also collect in hidden areas, such as around flight control hinges, pulleys, grommets, on cables and in gaps.

(iii) Operators are strongly recommended to obtain information about the fluid dry-out and re-hydration characteristics from the fluid manufacturers and to select products with optimised characteristics.

(iv) Additional information should be obtained from fluid manufacturers for handling, storage, application and testing of their products.

DE-ICING/ANTI-ICING — BACKGROUND INFORMATION

Further guidance material on this issue is given in the ICAO Manual of Aircraft Ground De-icing/Anti-icing Operations (Doc 9640).

(a) General

(1) Any deposit of frost, ice, snow or slush on the external surfaces of an aircraft may drastically affect its flying qualities because of reduced aerodynamic lift, increased drag, modified stability and control characteristics. Furthermore, freezing deposits may cause moving parts, such as elevators, ailerons, flap actuating mechanism, etc., to jam and create a potentially hazardous condition. Propeller/engine/APU/systems performance may deteriorate due to the presence of frozen contaminants on blades, intakes and components. Also, engine operation may be seriously affected by the ingestion of snow or ice, thereby causing engine stall or compressor damage. In addition, ice/frost may form on certain external surfaces (e.g. wing upper and lower surfaces, etc.) due to the effects of cold fuel/structures, even in ambient temperatures well above 0°C.

(2) Procedures established by the operator for de-icing and/or anti-icing are intended to ensure that the aircraft is clear of contamination so that degradation of aerodynamic characteristics or mechanical interference will not occur and, following anti-icing, to maintain the airframe in that condition during the appropriate HOT.

(3) Under certain meteorological conditions, de-icing and/or anti-icing procedures may be ineffective in providing sufficient protection for continued operations. Examples of these conditions are freezing rain, ice pellets and hail snow exceeding certain intensities, high wind velocity, and fast-dropping OAT. No HOT guidelines exist for these conditions.

(4) Material for establishing operational procedures can be found, for example, in:

(i) ICAO Annex 3 ‘Meteorological Service for International Air Navigation’;

(ii) ICAO ‘Manual of Aircraft Ground De-icing/Anti-icing Operations’;

(iii) SAE AS6285 ‘Aircraft Ground Deicing/Anti-Icing Processes’;

(iv) SAE AS6286 ‘Aircraft Ground Deicing/Anti-Icing Training and Qualification Program’;

(v) SAE AS6332 ‘Aircraft Ground Deicing/Anti-icing Quality Management’;

(vi) SAE ARP6257 ‘Aircraft Ground De/Anti-Icing Communication Phraseology for Flight and Ground Crews’;

(vii) FAA Holdover Time Guidelines

(viii) FAA 8900.xxx series Notice ‘Revised FAA-Approved Deicing Program Updates, Winter 20xx-20yy’.

(b) Fluids

(1) Type I fluid: Due to its properties, Type I fluid forms a thin, liquid-wetting film on surfaces to which it is applied which, under certain weather conditions, gives a very limited HOT. For anti-icing purposes the fluid/water mixture should have a freezing point of at least 10 °C below OAT; increasing the concentration of fluid in the fluid/water mix does not provide any extension in HOT.

(2) Type II and Type IV fluids contain thickeners which enable the fluid to form a thicker liquid-wetting film on surfaces to which it is applied. Generally, this fluid provides a longer HOT than Type I fluids in similar conditions.

(3) Type III fluid is a thickened fluid especially intended for use on aircraft with low rotation speeds.

(4) Fluids used for de-icing and/or anti-icing should be acceptable to the operator and the aircraft manufacturer. These fluids normally conform to specifications such as SAE AMS1424 (Type I) or SAE AMS1428 (Types II, III and IV). Use of non-conforming fluids is not recommended due to their characteristics being unknown. The anti-icing and aerodynamic properties of thickened fluids may be seriously degraded by, for example, inappropriate storage, treatment, application, application equipment, age and in case they are applied on top of non-chemically compatible de-icing fluids.

(c) Holdover protection

(1) Holdover protection is achieved by a layer of anti-icing fluid remaining on and protecting aircraft surfaces for a period of time. With a one-step de-icing/anti-icing procedure, the HOT begins at the commencement of de-icing/anti-icing. With a two-step procedure, the HOT begins at the commencement of the second (anti-icing) step. The holdover protection runs out:

(i) at the commencement of the take-off roll (due to aerodynamic shedding of fluid); or

(ii) when frozen deposits start to form or accumulate on treated aircraft surfaces, thereby indicating the loss of effectiveness of the fluid.

(2) The duration of holdover protection may vary depending on the influence of factors other than those specified in the HOT tables. Guidance should be provided by the operator to take account of such factors, which may include:

(i) atmospheric conditions, e.g. exact type and rate of precipitation, wind direction and velocity, relative humidity and solar radiation; and

(ii) the aircraft and its surroundings, such as aircraft component inclination angle, contour and surface roughness, surface temperature, operation in close proximity to other aircraft (jet or propeller blast) and ground equipment and structures.

(3) HOTs are not meant to imply that flight is safe in the prevailing conditions if the specified HOT has not been exceeded. Certain meteorological conditions, such as freezing drizzle or freezing rain, may be beyond the certification envelope of the aircraft.

SPO.OP.176 Ice and other contaminants – flight procedures

Regulation (EU) No 379/2014

(a) The pilot-in-command shall only commence a flight or intentionally fly into expected or actual icing conditions if the aircraft is certified and equipped to cope with such conditions as referred to in 2.a.5 of Annex IV to Regulation (EC) No 216/2008.

(b) If icing exceeds the intensity of icing for which the aircraft is certified or if an aircraft not certified for flight in known icing conditions encounters icing, the pilot-in-command shall exit the icing conditions without delay, by a change of level and/or route, and if necessary by declaring an emergency to ATC.

(c) In the case of operations with complex motor-powered aircraft, the operator shall establish procedures for flights in expected or actual icing conditions.

FLIGHT IN EXPECTED OR ACTUAL ICING CONDITIONS

(a) The procedures to be established by the operator should take account of the design, the equipment, the configuration of the aircraft and the necessary training. For these reasons, different aircraft types operated by the same company may require the development of different procedures. In every case, the relevant limitations are those that are defined in the AFM and other documents produced by the manufacturer.

(b) The operator should ensure that the procedures take account of the following:

(1) the equipment and instruments that should be serviceable for flight in icing conditions;

(2) the limitations on flight in icing conditions for each phase of flight. These limitations may be imposed by the aircraft’s de-icing or anti-icing equipment or the necessary performance corrections that have to be made;

(3) the criteria the flight crew should use to assess the effect of icing on the performance and/or controllability of the aircraft;

(4) the means by which the flight crew detects, by visual cues or the use of the aircraft’s ice detection system, that the flight is entering icing conditions; and

(5) the action to be taken by the flight crew in a deteriorating situation (which may develop rapidly) resulting in an adverse effect on the performance and/or controllability of the aircraft, due to:

(i) the failure of the aircraft’s anti-icing or de-icing equipment to control a build-up of ice; and/or

(ii) ice build-up on unprotected areas.

(c) Training for dispatch and flight in expected or actual icing conditions. The content of the operations manual should reflect the training, both conversion and recurrent, that flight crew and all other relevant operational personnel require in order to comply with the procedures for dispatch and flight in icing conditions:

(1) instruction on how to recognise, from weather reports or forecasts that are available before flight commences or during flight, the risks of encountering icing conditions along the planned route and on how to modify, as necessary, the departure and in-flight routes or profiles;

(2) instruction on the operational and performance limitations or margins;

(3) the use of in-flight ice detection, anti-icing and de-icing systems in both normal and abnormal operation; and

(4) instruction on the differing intensities and forms of ice accretion and the consequent action which should be taken.

SPO.OP.180 Take-off conditions — aeroplanes and helicopters

Regulation (EU) 2021/2237

Before commencing take-off, the pilot-in-command shall be satisfied that:

(a) the meteorological conditions at the aerodrome or the operating site and the condition of the runway/FATO intended to be used will not prevent a safe take-off and departure; and

(b) the selected aerodrome operating minima are consistent with all of the following:

(1) the operative ground equipment;

(2) the operative aircraft systems;

(3) the aircraft performance;

(4) flight crew qualifications.

SPO.OP.185 Simulated situations in flight

Regulation (EU) No 379/2014

Unless a task specialist is on-board the aircraft for training, the pilot-in-command shall, when carrying task specialists, not simulate:

(a) situations that require the application of abnormal or emergency procedures; or

(b) flight in instrument meteorological conditions (IMC).

SPO.OP.190 Fuel/energy scheme – in-flight fuel/energy management policy

Regulation (EU) 2021/1296

(a) The operator of complex motor-powered aircraft shall establish procedures to ensure that in‑flight fuel/energy checks and fuel/energy management are performed.

(b) The pilot-in-command shall monitor the amount of usable fuel/energy remaining on board to ensure that it is protected and not less than the fuel/energy that is required to proceed to an aerodrome or operating site where a safe landing can be made.

(c) The pilot-in-command shall advise air traffic control (ATC) of a ‘minimum fuel/energy’ state by declaring ‘MINIMUM FUEL’ when the pilot-in-command has:

(1) committed to land at a specific aerodrome or operating site; and

(2) calculated that any change to the existing clearance to that aerodrome or operating site, or other air traffic delays, may result in landing with less than the planned final reserve fuel/energy.

(d) The pilot-in-command shall declare a situation of ‘fuel/energy emergency’ by broadcasting ‘MAYDAY MAYDAY MAYDAY FUEL’ when the usable fuel/energy estimated to be available upon landing at the nearest aerodrome or operating site where a safe landing can be made is less than the planned final reserve fuel/energy.

FINAL RESERVE FUEL PROTECTION

To ensure a safe landing, the pilot needs to protect the final reserve fuel (FRF) in accordance with point SPO.OP.131. The objective of the FRF protection is to ensure that a safe landing is made at any aerodrome or operating site when unforeseen circumstances may not allow to safely complete the flight, as originally planned.

When the FRF can no longer be protected, then a fuel emergency needs to be declared, as per point SPO.OP.190(d), and any landing option explored (e.g. for aeroplanes, aerodromes not assessed by the operator, military aerodromes, closed runways), including deviating from rules, operational procedures, and methods in the interest of safety (as per point CAT.GEN.MPA.105(b)).

ICAO Doc 9976 Flight Planning and Fuel Management (FPFM) Manual and the EASA Fuel Manual contain further detailed guidance on the development of a comprehensive in-flight fuel management policy and related procedures.

‘MINIMUM FUEL’ DECLARATION

The ‘MINIMUM FUEL’ declaration informs the ATC that all planned landing options have been reduced to a specific aerodrome or operating site of intended landing, and for helicopters, that no other landing site is available. It also informs the ATC that any change to the existing clearance may result in landing with less than the planned FRF/energy. This is not an emergency situation but an indication that an emergency situation is possible, should any additional delay occur.

The pilot should not expect any form of priority handling as a result of a ‘MINIMUM FUEL’ declaration. However, the ATC should advise the flight crew of any additional expected delays, as well as coordinate with other ATC units when transferring the control of the aircraft, to ensure that the other ATC units are aware of the flight’s fuel/energy state.

ICAO Doc 9976 Flight Planning and Fuel Management (FPFM) Manual (1st Edition, 2015) and the EASA Fuel Manual contain guidance on declaring ‘MINIMUM FUEL’.

SPO.OP.195 Use of supplemental oxygen

Regulation (EU) No 379/2014

(a) The operator shall ensure that task specialists and crew members use supplemental oxygen continuously whenever the cabin altitude exceeds 10 000 ft for a period of more than 30 minutes and whenever the cabin altitude exceeds 13 000 ft, unless otherwise approved by the competent authority and in accordance with SOPs.

(b) Notwithstanding (a) and except for parachute operations, short excursions of a specified duration above 13 000 ft without using supplemental oxygen on other-than complex aeroplanes and helicopters may be undertaken with a prior approval of the competent authority based on the consideration of the following:

(1) the duration of the excursion above 13 000 ft is not more than 10 minutes or, if needed for a longer period, the time strictly necessary to the accomplishment of the specialised task;

(2) the flight is not conducted above 16 000 ft;

(3) the safety briefing in accordance with SPO.OP.135 includes adequate information to crew members and tasks specialists on the effects of hypoxia;

(4) SOPs for the concerned operation reflecting (1), (2) and (3);

(5) the previous experience of the operator in conducting operations above 13 000 ft without using supplemental oxygen;

(6) the individual experience of crew members and task specialists and their physiological adaptation to high altitudes; and

(7) the altitude of the base where the operator is established or the operations are conducted from.

SPO.OP.200 Ground proximity detection

Regulation (EU) No 379/2014

(a) When undue proximity to the ground is detected by a flight crew member or by a ground proximity warning system, the pilot flying shall take corrective action immediately in order to establish safe flight conditions.

(b) The ground proximity warning system may be disabled during those specialised tasks, which by their nature require the aircraft to be operated within a distance from the ground below that which would trigger the ground proximity warning system.

GM1 SPO.OP.200 Ground proximity detection

ED Decision 2014/018/R

GUIDANCE MATERIAL FOR TERRAIN AWARENESS WARNING SYSTEM (TAWS) FLIGHT CREW TRAINING PROGRAMMES

(a) Introduction

(1) This GM contains performance-based training objectives for TAWS flight crew training.

(2) The training objectives cover five areas: theory of operation; pre-flight operations; general in-flight operations; response to TAWS cautions; response to TAWS warnings.

(3) The term ‘TAWS’ in this GM means a ground proximity warning system (GPWS) enhanced by a forward-looking terrain avoidance function. Alerts include both cautions and warnings.

(4) The content of this GM is intended to assist operators who are producing training programmes. The information it contains has not been tailored to any specific aircraft or TAWS equipment, but highlights features that are typically available where such systems are installed. It is the responsibility of the individual operator to determine the applicability of the content of this Guidance Material to each aircraft and TAWS equipment installed and their operation. Operators should refer to the AFM and/or aircraft/flight crew operating manual (A/FCOM), or similar documents, for information applicable to specific configurations. If there should be any conflict between the content of this Guidance Material and that published in the other documents described above, then the information contained in the AFM or A/FCOM will take precedence.

(b) Scope

(1) The scope of this GM is designed to identify training objectives in the areas of: academic training; manoeuvre training; initial evaluation; recurrent qualification. Under each of these four areas, the training material has been separated into those items that are considered essential training items and those that are considered to be desirable. In each area, objectives and acceptable performance criteria are defined.

(2) No attempt is made to define how the training programme should be implemented. Instead, objectives are established to define the knowledge that a pilot operating a TAWS is expected to possess and the performance expected from a pilot who has completed TAWS training. However, the guidelines do indicate those areas in which the pilot receiving the training should demonstrate his/her understanding, or performance, using a real-time, interactive training device, i.e. a flight simulator. Where appropriate, notes are included within the performance criteria that amplify or clarify the material addressed by the training objective.

(c) Performance-based training objectives

(1) TAWS academic training

(i) This training is typically conducted in a classroom environment. The knowledge demonstrations specified in this section may be completed through the successful completion of written tests or by providing correct responses to non-real-time computer-based training (CBT) questions.

(ii) Theory of operation. The pilot should demonstrate an understanding of TAWS operation and the criteria used for issuing cautions and warnings. This training should address system operation. Objective: to demonstrate knowledge of how a TAWS functions. Criteria: the pilot should demonstrate an understanding of the following functions:

(A) Surveillance

(a) The GPWS computer processes data supplied from an air data computer, a radio altimeter, an instrument landing system (ILS)/microwave landing system (MLS)/multi-mode (MM) receiver, a roll attitude sensor, and actual position of the surfaces and of the landing gear.

(b) The forward-looking terrain avoidance function utilises an accurate source of known aircraft position, such as that which may be provided by a flight management system (FMS) or global positioning system (GPS), or an electronic terrain database. The source and scope of the terrain, obstacle and airport data, and features such as the terrain clearance floor, the runway picker, and geometric altitude (where provided), should all be described.

(c) Displays required to deliver TAWS outputs include a loudspeaker for voice announcements, visual alerts (typically amber and red lights) and a terrain awareness display (that may be combined with other displays). In addition, means should be provided for indicating the status of the TAWS and any partial or total failures that may occur.

(B) Terrain avoidance. Outputs from the TAWS computer provide visual and audio synthetic voice cautions and warnings to alert the flight crew about potential conflicts with terrain and obstacles.

(C) Alert thresholds. Objective: to demonstrate knowledge of the criteria for issuing cautions and warnings. Criteria: the pilot should be able to demonstrate an understanding of the methodology used by a TAWS to issue cautions and alerts and the general criteria for the issuance of these alerts, including:

(a) basic GPWS alerting modes specified in the ICAO standard:

             Mode 1: excessive sink rate;

             Mode 2: excessive terrain closure rate;

             Mode 3: descent after take-off or missed approach;

             Mode 4: unsafe proximity to terrain; and

             Mode 5: descent below ILS glide slope (caution only);

(b) an additional, optional alert mode:

 Mode 6: radio altitude call-out (information only); and

(c) TAWS cautions and warnings that alert the flight crew to obstacles and terrain ahead of the aircraft in line with or adjacent to its projected flight path (forward-looking terrain avoidance (FLTA) and premature descent alert (PDA) functions).

(D) TAWS limitations. Objective: to verify that the pilot is aware of the limitations of TAWS. Criteria: the pilot should demonstrate knowledge and an understanding of TAWS limitations identified by the manufacturer for the equipment model installed, such as:

(a) navigation should not be predicated on the use of the terrain display;

(b) unless geometric altitude data is provided, use of predictive TAWS functions is prohibited when altimeter subscale settings display ‘QFE’ (atmospheric pressure at aerodrome elevation/runway threshold);

(c) nuisance alerts can be issued if the aerodrome of intended landing is not included in the TAWS airport database;

(d) in cold weather operations, corrective procedures should be implemented by the pilot unless the TAWS has in-built compensation, such as geometric altitude data;

(e) loss of input data to the TAWS computer could result in partial or total loss of functionality. Where means exist to inform the flight crew that functionality has been degraded, this should be known and the consequences understood;

(f) radio signals not associated with the intended flight profile (e.g. ILS glide path transmissions from an adjacent runway) may cause false alerts;

(g) inaccurate or low accuracy aircraft position data could lead to false or non-annunciation of terrain or obstacles ahead of the aircraft; and

(h) minimum equipment list (MEL) restrictions should be applied in the event of the TAWS becoming partially or completely unserviceable. (It should be noted that basic GPWS has no forward-looking capability.)

(E) TAWS inhibits. Objective: to verify that the pilot is aware of the conditions under which certain functions of a TAWS are inhibited. Criteria: the pilot should demonstrate knowledge and an understanding of the various TAWS inhibits, including the following means of:

(a) silencing voice alerts;

(b) inhibiting ILS glide path signals (as may be required when executing an ILS back beam approach);

(c) inhibiting flap position sensors (as may be required when executing an approach with the flaps not in a normal position for landing);

(d) inhibiting the FLTA and PDA functions; and

(e) selecting or deselecting the display of terrain information, together with appropriate annunciation of the status of each selection.

(2) Operating procedures. The pilot should demonstrate the knowledge required to operate TAWS avionics and to interpret the information presented by a TAWS. This training should address the following topics:

(i) Use of controls. Objective: to verify that the pilot can properly operate all TAWS controls and inhibits. Criteria: the pilot should demonstrate the proper use of controls, including the following means by which:

(A) before flight, any equipment self-test functions can be initiated;

(B) TAWS information can be selected for display; and

(C) all TAWS inhibits can be operated and what the consequent annunciations mean with regard to loss of functionality.

(ii) Display interpretation. Objective: to verify that the pilot understands the meaning of all information that can be annunciated or displayed by a TAWS. Criteria: the pilot should demonstrate the ability to properly interpret information annunciated or displayed by a TAWS, including the following:

(A) knowledge of all visual and aural indications that may be seen or heard;

(B) response required on receipt of a caution;

(C) response required on receipt of a warning; and

(D) response required on receipt of a notification that partial or total failure of the TAWS has occurred (including annunciation that the present aircraft position is of low accuracy).

(iii) Use of basic GPWS or use of the FLTA function only. Objective: to verify that the pilot understands what functionality will remain following loss of the GPWS or of the FLTA function. Criteria: the pilot should demonstrate knowledge of how to recognise the following:

(A) un-commanded loss of the GPWS function, or how to isolate this function and how to recognise the level of the remaining controlled flight into terrain (CFIT) protection (essentially, this is the FLTA function); and

(B) un-commanded loss of the FLTA function, or how to isolate this function and how to recognise the level of the remaining CFIT protection (essentially, this is the basic GPWS).

(iv) Crew coordination. Objective: to verify that the pilot adequately briefs other flight crew members on how TAWS alerts will be handled. Criteria: the pilot should demonstrate that the pre-flight briefing addresses procedures that will be used in preparation for responding to TAWS cautions and warnings, including the following:

(A) the action to be taken, and by whom, in the event that a TAWS caution and/or warning is issued; and

(B) how multi-function displays will be used to depict TAWS information at take-off, in the cruise and for the descent, approach, landing (and any missed approach). This will be in accordance with procedures specified by the operator, who will recognise that it may be more desirable that other data is displayed at certain phases of flight and that the terrain display has an automatic 'pop-up' mode in the event that an alert is issued.

(v) Reporting rules. Objective: to verify that the pilot is aware of the rules for reporting alerts to the controller and other authorities. Criteria: the pilot should demonstrate knowledge of the following:

(A) when, following recovery from a TAWS alert or caution, a transmission of information should be made to the appropriate ATC unit; and

(B) the type of written report that is required, how it is to be compiled and whether any cross-reference should be made in the aircraft technical log and/or voyage report (in accordance with procedures specified by the operator), following a flight in which the aircraft flight path has been modified in response to a TAWS alert, or if any part of the equipment appears not to have functioned correctly.

(vi) Alert thresholds. Objective: to demonstrate knowledge of the criteria for issuing cautions and warnings. Criteria: the pilot should be able to demonstrate an understanding of the methodology used by a TAWS to issue cautions and warnings and the general criteria for the issuance of these alerts, including awareness of the following:

(A) modes associated with basic GPWS, including the input data associated with each; and

(B) visual and aural annunciations that can be issued by TAWS and how to identify which are cautions and which are warnings.

(3) TAWS manoeuvre training. The pilot should demonstrate the knowledge required to respond correctly to TAWS cautions and warnings. This training should address the following topics:

(i) Response to cautions:

(A) Objective: to verify that the pilot properly interprets and responds to cautions. Criteria: the pilot should demonstrate an understanding of the need, without delay:

(a) to initiate action required to correct the condition that has caused the TAWS to issue the caution and to be prepared to respond to a warning, if this should follow; and

(b) if a warning does not follow the caution, to notify the controller of the new position, heading and/or altitude/flight level of the aircraft, and what the pilot-in-command intends to do next.

(B) The correct response to a caution might require the pilot to:

(a) reduce a rate of descent and/or to initiate a climb;

(b) regain an ILS glide path from below, or to inhibit a glide path signal if an ILS is not being flown;

(c) select more flap, or to inhibit a flap sensor if the landing is being conducted with the intent that the normal flap setting will not be used;

(d) select gear down; and/or

(e) initiate a turn away from the terrain or obstacle ahead and towards an area free of such obstructions if a forward-looking terrain display indicates that this would be a good solution and the entire manoeuvre can be carried out in clear visual conditions.

(ii) Response to warnings. Objective: to verify that the pilot properly interprets and responds to warnings. Criteria: the pilot should demonstrate an understanding of the following:

(A) The need, without delay, to initiate a climb in the manner specified by the operator.

(B) The need, without delay, to maintain the climb until visual verification can be made that the aircraft will clear the terrain or obstacle ahead or until above the appropriate sector safe altitude (if certain about the location of the aircraft with respect to terrain) even if the TAWS warning stops. If, subsequently, the aircraft climbs up through the sector safe altitude, but the visibility does not allow the flight crew to confirm that the terrain hazard has ended, checks should be made to verify the location of the aircraft and to confirm that the altimeter subscale settings are correct.

(C) When workload permits that, the flight crew should notify the air traffic controller of the new position and altitude/flight level and what the pilot-in-command intends to do next.

(D) That the manner in which the climb is made should reflect the type of aircraft and the method specified by the aircraft manufacturer (which should be reflected in the operations manual) for performing the escape manoeuvre. Essential aspects will include the need for an increase in pitch attitude, selection of maximum thrust, confirmation that external sources of drag (e.g. spoilers/speed brakes) are retracted and respect of the stick shaker or other indication of eroded stall margin.

(E) That TAWS warnings should never be ignored. However, the pilot’s response may be limited to that which is appropriate for a caution, only if:

(a) the aircraft is being operated by day in clear, visual conditions; and

(b) it is immediately clear to the pilot that the aircraft is in no danger in respect of its configuration, proximity to terrain or current flight path.

(4) TAWS initial evaluation:

(i) The flight crew member’s understanding of the academic training items should be assessed by means of a written test.

(ii) The flight crew member’s understanding of the manoeuvre training items should be assessed in a flight simulation training device (FSTD) equipped with TAWS visual and aural displays and inhibit selectors similar in appearance and operation to those in the aircraft that the pilot will fly. The results should be assessed by a flight simulation training instructor, synthetic flight examiner, type rating instructor or type rating examiner.

(iii) The range of scenarios should be designed to give confidence that proper and timely responses to TAWS cautions and warnings will result in the aircraft avoiding a CFIT accident. To achieve this objective, the pilot should demonstrate taking the correct action to prevent a caution developing into a warning and, separately, the escape manoeuvre needed in response to a warning. These demonstrations should take place when the external visibility is zero, though there is much to be learnt if, initially, the training is given in 'mountainous' or 'hilly' terrain with clear visibility. This training should comprise a sequence of scenarios, rather than be included in line orientated flight training (LOFT).

(iv) A record should be made, after the pilot has demonstrated competence, of the scenarios that were practised.

(5) TAWS recurrent training:

(i) TAWS recurrent training ensures that pilots maintain the appropriate TAWS knowledge and skills. In particular, it reminds pilots of the need to act promptly in response to cautions and warnings and of the unusual attitude associated with flying the escape manoeuvre.

(ii) An essential item of recurrent training is the discussion of any significant issues and operational concerns that have been identified by the operator. Recurrent training should also address changes to TAWS logic, parameters or procedures and to any unique TAWS characteristics of which pilots should be aware.

(6) Reporting procedures:

(i) Verbal reports. Verbal reports should be made promptly to the appropriate ATC unit:

(A) whenever any manoeuvre has caused the aircraft to deviate from an air traffic clearance;

(B) when, following a manoeuvre that has caused the aircraft to deviate from an air traffic clearance, the aircraft has returned to a flight path that complies with the clearance; and/or

(C) when an air traffic control unit issues instructions that, if followed, would cause the pilot to manoeuvre the aircraft towards terrain or obstacle or it would appear from the display that a potential CFIT occurrence is likely to result.

(ii) Written reports. Written reports should be submitted in accordance with the operator's occurrence reporting scheme and they should also be recorded in the aircraft technical log:

(A) whenever the aircraft flight path has been modified in response to a TAWS alert (false, nuisance or genuine);

(B) whenever a TAWS alert has been issued and is believed to have been false; and/or

(C) if it is believed that a TAWS alert should have been issued, but was not.

(iii) Within this GM, and with regard to reports:

(A) the term 'false' means that the TAWS issued an alert that could not possibly be justified by the position of the aircraft in respect to terrain and it is probable that a fault or failure in the system (equipment and/or input data) was the cause;

(B) the term 'nuisance' means that the TAWS issued an alert that was appropriate, but was not needed because the flight crew could determine by independent means that the flight path was, at that time, safe;

(C) the term 'genuine' means that the TAWS issued an alert that was both appropriate and necessary;

(D) the report terms described above are only meant to be assessed after the occurrence is over, to facilitate subsequent analysis, the adequacy of the equipment and the programmes it contains. The intention is not for the flight crew to attempt to classify an alert into any of these three categories when visual and/or aural cautions or warnings are annunciated.

SPO.OP.205 Airborne collision avoidance system (ACAS)

Regulation (EU) 2016/1199

(a) The operator shall establish operational procedures and training programmes when ACAS is installed and serviceable so that the flight crew is appropriately trained in the avoidance of collisions and competent in the use of ACAS II equipment.

(b) The ACAS II may be disabled during those specialised tasks, which by their nature require the aircraft to be operated within a distance from each other below that which would trigger the ACAS.

GENERAL

(a) The ACAS operational procedures and training programmes established by the operator should take into account this Guidance Material. It incorporates advice contained in:

(1) ICAO Annex 10, Volume IV;

(2) ICAO Doc 8168 (PANS-OPS), Volume III; and

(3) ICAO PANS-ATM.

(b) Additional guidance material on ACAS may be referred to, including information available from such sources as EUROCONTROL.

ACAS FLIGHT CREW TRAINING

(c) During the implementation of ACAS, several operational issues were identified that had been attributed to deficiencies in flight crew training programmes. As a result, the issue of flight crew training has been discussed within the ICAO, which has developed guidelines for operators to use when designing training programmes.

(d) This Guidance Material contains performance-based training objectives for ACAS II flight crew training. Information contained here related to traffic advisories (TAs) is also applicable to ACAS I and ACAS II users. The training objectives cover five areas: theory of operation; pre-flight operations; general in-flight operations; response to TAs; and response to resolution advisories (RAs).

(e) The information provided is valid for version 7 and 7.1 (ACAS II). Where differences arise, these are identified.

(f) The performance-based training objectives are further divided into the areas of: academic training; manoeuvre training; initial evaluation and recurrent qualification. Under each of these four areas, the training material has been separated into those items which are considered essential training items and those which are considered desirable. In each area, objectives and acceptable performance criteria are defined.

(g) ACAS academic training

(1) This training is typically conducted in a classroom environment. The knowledge demonstrations specified in this section may be completed through the successful completion of written tests or through providing correct responses to non-real-time computer-based training (CBT) questions.

(2) Essential items

(i) Theory of operation. The flight crew member should demonstrate an understanding of ACAS II operation and the criteria used for issuing TAs and RAs. This training should address the following topics:

(A) System operation

Objective: to demonstrate knowledge of how ACAS functions.

Criteria: the flight crew member should demonstrate an understanding of the following functions:

(a) Surveillance

(1) ACAS interrogates other transponder-equipped aircraft within a nominal range of 14 NM.

(2) ACAS surveillance range can be reduced in geographic areas with a large number of ground interrogators and/or ACAS II-equipped aircraft.

(3) If the operator's ACAS implementation provides for the use of the Mode S extended squitter, the normal surveillance range may be increased beyond the nominal 14 NM. However, this information is not used for collision avoidance purposes.

(b) Collision avoidance

(1) TAs can be issued against any transponder-equipped aircraft that responds to the ICAO Mode C interrogations, even if the aircraft does not have altitude reporting capability.

(2) RAs can be issued only against aircraft that are reporting altitude and in the vertical plane only.

(3) RAs issued against an ACAS-equipped intruder are co-ordinated to ensure complementary RAs are issued.

(4) Failure to respond to an RA deprives own aircraft of the collision protection provided by own ACAS.

(5) Additionally, in ACAS-ACAS encounters, failure to respond to an RA also restricts the choices available to the other aircraft's ACAS and thus renders the other aircraft's ACAS less effective than if own aircraft were not ACAS equipped.

(B) Advisory thresholds

Objective: to demonstrate knowledge of the criteria for issuing TAs and RAs.

Criteria: the flight crew member should demonstrate an understanding of the methodology used by ACAS to issue TAs and RAs and the general criteria for the issuance of these advisories, including the following:

(a) ACAS advisories are based on time to closest point of approach (CPA) rather than distance. The time should be short and vertical separation should be small, or projected to be small, before an advisory can be issued. The separation standards provided by ATS are different from the miss distances against which ACAS issues alerts.

(b) Thresholds for issuing a TA or an RA vary with altitude. The thresholds are larger at higher altitudes.

(c) A TA occurs from 15 to 48 seconds and an RA from 15 to 35 seconds before the projected CPA.

(d) RAs are chosen to provide the desired vertical miss distance at CPA. As a result, RAs can instruct a climb or descent through the intruder aircraft's altitude.

(C) ACAS limitations

Objective: to verify that the flight crew member is aware of the limitations of ACAS.

Criteria: the flight crew member should demonstrate knowledge and understanding of ACAS limitations, including the following:

(a) ACAS will neither track nor display non-transponder-equipped aircraft, nor aircraft not responding to ACAS Mode C interrogations.

(b) ACAS will automatically fail if the input from the aircraft’s barometric altimeter, radio altimeter or transponder is lost.

(1) In some installations, the loss of information from other on-board systems such as an inertial reference system (IRS) or attitude heading reference system (AHRS) may result in an ACAS failure. Individual operators should ensure that their flight crews are aware of the types of failure which will result in an ACAS failure.

(2) ACAS may react in an improper manner when false altitude information is provided to own ACAS or transmitted by another aircraft. Individual operators should ensure that their flight crew are aware of the types of unsafe conditions which can arise. Flight crew members should ensure that when they are advised, if their own aircraft is transmitting false altitude reports, an alternative altitude reporting source is selected, or altitude reporting is switched off.

(c) Some aeroplanes within 380 ft above ground level (AGL) (nominal value) are deemed to be ‘on ground’ and will not be displayed. If ACAS is able to determine an aircraft below this altitude is airborne, it will be displayed.

(d) ACAS may not display all proximate transponder-equipped aircraft in areas of high density traffic.

(e) The bearing displayed by ACAS is not sufficiently accurate to support the initiation of horizontal manoeuvres based solely on the traffic display.

(f) ACAS will neither track nor display intruders with a vertical speed in excess of 10 000 ft/min. In addition, the design implementation may result in some short-term errors in the tracked vertical speed of an intruder during periods of high vertical acceleration by the intruder.

(g) Ground proximity warning systems/ground collision avoidance systems (GPWSs/GCASs) warnings and wind shear warnings take precedence over ACAS advisories. When either a GPWS/GCAS or wind shear warning is active, ACAS aural annunciations will be inhibited and ACAS will automatically switch to the 'TA only' mode of operation.

(D) ACAS inhibits

Objective: to verify that the flight crew member is aware of the conditions under which certain functions of ACAS are inhibited.

Criteria: the flight crew member should demonstrate knowledge and understanding of the various ACAS inhibits, including the following:

(a) ‘Increase Descent’ RAs are inhibited below 1 450 ft AGL.

(b) ‘Descend’ RAs are inhibited below 1 100 ft AGL.

(c) All RAs are inhibited below 1 000 ft AGL.

(d) All TA aural annunciations are inhibited below 500 ft AGL.

(e) Altitude and configuration under which ‘Climb’ and ‘Increase Climb’ RAs are inhibited. ACAS can still issue ‘Climb’ and ‘Increase Climb’ RAs when operating at the aeroplane's certified ceiling. (In some aircraft types, ‘Climb’ or ‘Increase Climb’ RAs are never inhibited.)

(ii) Operating procedures

The flight crew member should demonstrate the knowledge required to operate the ACAS avionics and interpret the information presented by ACAS. This training should address the following:

(A) Use of controls

Objective: to verify that the pilot can properly operate all ACAS and display controls.

Criteria: demonstrate the proper use of controls, including the following:

(a) Aircraft configuration required to initiate a self-test.

(b) Steps required to initiate a self-test.

(c) Recognising when the self-test was successful and when it was unsuccessful. When the self-test is unsuccessful, recognising the reason for the failure and, if possible, correcting the problem.

(d) Recommended usage of range selection. Low ranges are used in the terminal area and the higher display ranges are used in the en-route environment and in the transition between the terminal and en-route environment.

(e) Recognising that the configuration of the display does not affect the ACAS surveillance volume.

(f) Selection of lower ranges when an advisory is issued, to increase display resolution.

(g) Proper configuration to display the appropriate ACAS information without eliminating the display of other needed information.

(h) If available, recommended usage of the above/below mode selector. The above mode should be used during climb and the below mode should be used during descent.

(i) If available, proper selection of the display of absolute or relative altitude and the limitations of using this display if a barometric correction is not provided to ACAS.

(B) Display interpretation

Objective: to verify that the flight crew member understands the meaning of all information that can be displayed by ACAS. The wide variety of display implementations require the tailoring of some criteria. When the training programme is developed, these criteria should be expanded to cover details for the operator's specific display implementation.

Criteria: the flight crew member should demonstrate the ability to properly interpret information displayed by ACAS, including the following:

(a) Other traffic, i.e. traffic within the selected display range that is not proximate traffic, or causing a TA or RA to be issued.

(b) Proximate traffic, i.e. traffic that is within 6 NM and ± 1 200 ft.

(c) Non-altitude reporting traffic.

(d) No bearing TAs and RAs.

(e) Off-scale TAs and RAs: the selected range should be changed to ensure that all available information on the intruder is displayed.

(f) TAs: the minimum available display range that allows the traffic to be displayed should be selected, to provide the maximum display resolution.

(g) RAs (traffic display): the minimum available display range of the traffic display that allows the traffic to be displayed should be selected, to provide the maximum display resolution.

(h) RAs (RA display): flight crew members should demonstrate knowledge of the meaning of the red and green areas or the meaning of pitch or flight path angle cues displayed on the RA display. Flight crew members should also demonstrate an understanding of the RA display limitations, i.e. if a vertical speed tape is used and the range of the tape is less than 2 500 ft/min, an increase rate RA cannot be properly displayed.

(i) If appropriate, awareness that navigation displays oriented on ‘Track-Up’ may require a flight crew member to make a mental adjustment for drift angle when assessing the bearing of proximate traffic.

(C) Use of the TA only mode

Objective: to verify that a flight crew member understands the appropriate times to select the TA only mode of operation and the limitations associated with using this mode.

Criteria: the flight crew member should demonstrate the following:

(a) Knowledge of the operator's guidance for the use of TA only.

(b) Reasons for using this mode. If TA only is not selected when an airport is conducting simultaneous operations from parallel runways separated by less than 1 200 ft, and to some intersecting runways, RAs can be expected. If, for any reason, TA only is not selected and an RA is received in these situations, the response should comply with the operator's approved procedures.

(c) All TA aural annunciations are inhibited below 500 ft AGL. As a result, TAs issued below 500 ft AGL may not be noticed unless the TA display is included in the routine instrument scan.

(D) Crew coordination

Objective: to verify that the flight crew member understands how ACAS advisories will be handled.

Criteria: the flight crew member should demonstrate knowledge of the crew procedures that should be used when responding to TAs and RAs, including the following:

(a) task sharing between the pilot flying and the pilot monitoring;

(b) expected call-outs; and

(c) communications with ATC.

(E) Phraseology rules

Objective: to verify that the flight crew member is aware of the rules for reporting RAs to the controller.

Criteria: the flight crew member should demonstrate the following:

(a) the use of the phraseology contained in ICAO PANS-OPS;

(b) an understanding of the procedures contained in ICAO PANS-ATM and ICAO Annex 2; and

(c) the understanding that verbal reports should be made promptly to the appropriate ATC unit:

(1) whenever any manoeuvre has caused the aeroplane to deviate from an air traffic clearance;

(2) when, subsequent to a manoeuvre that has caused the aeroplane to deviate from an air traffic clearance, the aeroplane has returned to a flight path that complies with the clearance; and/or

(3) when air traffic issue instructions that, if followed, would cause the crew to manoeuvre the aircraft contrary to an RA with which they are complying.

(F) Reporting rules

Objective: to verify that the flight crew member is aware of the rules for reporting RAs to the operator.

Criteria: the flight crew member should demonstrate knowledge of where information can be obtained regarding the need for making written reports to various States when an RA is issued. Various States have different reporting rules and the material available to the flight crew member should be tailored to the operator’s operating environment. This responsibility is satisfied by the flight crew member reporting to the operator according to the applicable reporting rules.

(3) Non-essential items: advisory thresholds

Objective: to demonstrate knowledge of the criteria for issuing TAs and RAs.

Criteria: the flight crew member should demonstrate an understanding of the methodology used by ACAS to issue TAs and RAs and the general criteria for the issuance of these advisories, including the following:

(i) The minimum and maximum altitudes below/above which TAs will not be issued.

(ii) When the vertical separation at CPA is projected to be less than the ACAS-desired separation, a corrective RA that requires a change to the existing vertical speed will be issued. This separation varies from 300 ft at low altitude to a maximum of 700 ft at high altitude.

(iii) When the vertical separation at CPA is projected to be just outside the ACAS-desired separation, a preventive RA that does not require a change to the existing vertical speed will be issued. This separation varies from 600 to 800 ft.

(iv) RA fixed range thresholds vary between 0.2 and 1.1 NM.

(h) ACAS manoeuvre training

(1) Demonstration of the flight crew member’s ability to use ACAS displayed information to properly respond to TAs and RAs should be carried out in a full flight simulator equipped with an ACAS display and controls similar in appearance and operation to those in the aircraft. If a full flight simulator is utilised, crew resource management (CRM) should be practised during this training.

(2) Alternatively, the required demonstrations can be carried out by means of an interactive CBT with an ACAS display and controls similar in appearance and operation to those in the aircraft. This interactive CBT should depict scenarios in which real-time responses should be made. The flight crew member should be informed whether or not the responses made were correct. If the response was incorrect or inappropriate, the CBT should show what the correct response should be.

(3) The scenarios included in the manoeuvre training should include: corrective RAs; initial preventive RAs; maintain rate RAs; altitude crossing RAs; increase rate RAs; RA reversals; weakening RAs; and multi-aircraft encounters. The consequences of failure to respond correctly should be demonstrated by reference to actual incidents such as those publicised in EUROCONTROL ACAS II Bulletins (available on the EUROCONTROL website).

(i) TA responses

Objective: to verify that the pilot properly interprets and responds to TAs.

Criteria: the pilot should demonstrate the following:

(A) Proper division of responsibilities between the pilot flying and the pilot monitoring. The pilot flying should fly the aircraft using any type-specific procedures and be prepared to respond to any RA that might follow. For aircraft without an RA pitch display, the pilot flying should consider the likely magnitude of an appropriate pitch change. The pilot monitoring should provide updates on the traffic location shown on the ACAS display, using this information to help visually acquire the intruder.

(B) Proper interpretation of the displayed information. Flight crew members should confirm that the aircraft they have visually acquired is that which has caused the TA to be issued. Use should be made of all information shown on the display, note being taken of the bearing and range of the intruder (amber circle), whether it is above or below (data tag), and its vertical speed direction (trend arrow).

(C) Other available information should be used to assist in visual acquisition, including ATC ‘party-line’ information, traffic flow in use, etc.

(D) Because of the limitations described, the pilot flying should not manoeuvre the aircraft based solely on the information shown on the ACAS display. No attempt should be made to adjust the current flight path in anticipation of what an RA would advise, except that if own aircraft is approaching its cleared level at a high vertical rate with a TA present, vertical rate should be reduced to less than 1 500 ft/min.

(E) When visual acquisition is attained, and as long as no RA is received, normal right of way rules should be used to maintain or attain safe separation. No unnecessary manoeuvres should be initiated. The limitations of making manoeuvres based solely on visual acquisition, especially at high altitude or at night, or without a definite horizon should be demonstrated as being understood.

(ii) RA responses

Objective: to verify that the pilot properly interprets and responds to RAs.

Criteria: the pilot should demonstrate the following:

(A) Proper response to the RA, even if it is in conflict with an ATC instruction and even if the pilot believes that there is no threat present.

(B) Proper task sharing between the pilot flying and the pilot monitoring. The pilot flying should respond to a corrective RA with appropriate control inputs. The pilot monitoring should monitor the response to the RA and should provide updates on the traffic location by checking the traffic display. Proper CRM should be used.

(C) Proper interpretation of the displayed information. The pilot should recognise the intruder causing the RA to be issued (red square on display). The pilot should respond appropriately.

(D) For corrective RAs, the response should be initiated in the proper direction within 5 seconds of the RA being displayed. The change in vertical speed should be accomplished with an acceleration of approximately ¼ g (gravitational acceleration of 9.81 m/sec²).

(E) Recognition of the initially displayed RA being modified. Response to the modified RA should be properly accomplished, as follows:

(a) For increase rate RAs, the vertical speed change should be started within 2½ seconds of the RA being displayed. The change in vertical speed should be accomplished with an acceleration of approximately ⅓ g.

(b) For RA reversals, the vertical speed reversal should be started within 2½ seconds of the RA being displayed. The change in vertical speed should be accomplished with an acceleration of approximately ⅓ g.

(c) For RA weakenings, the vertical speed should be modified to initiate a return towards the original clearance.

(d) An acceleration of approximately ¼ g will be achieved if the change in pitch attitude corresponding to a change in vertical speed of 1 500 ft/min is accomplished in approximately 5 seconds, and of ⅓ g if the change is accomplished in approximately 3 seconds. The change in pitch attitude required to establish a rate of climb or descent of 1 500 ft/min from level flight will be approximately 6 when the true airspeed (TAS) is 150 kt, 4 at 250 kt, and 2 at 500 kt. (These angles are derived from the formula: 1 000 divided by TAS.)

(F) Recognition of altitude crossing encounters and the proper response to these RAs.

(G) For preventive RAs, the vertical speed needle or pitch attitude indication should remain outside the red area on the RA display.

(H) For maintain rate RAs, the vertical speed should not be reduced. Pilots should recognise that a maintain rate RA may result in crossing through the intruder's altitude.

(I) When the RA weakens, or when the green 'fly to' indicator changes position, the pilot should initiate a return towards the original clearance, and when ‘clear of conflict’ is annunciated, the pilot should complete the return to the original clearance.

(J) The controller should be informed of the RA as soon as time and workload permit, using the standard phraseology.

(K) When possible, an ATC clearance should be complied with while responding to an RA. For example, if the aircraft can level at the assigned altitude while responding to RA (an ‘adjust vertical speed’ RA (version 7) or ‘level off’ (version 7.1), it should be done; the horizontal (turn) element of an ATC instruction should be followed.

(L) Knowledge of the ACAS multi-aircraft logic and its limitations, and that ACAS can optimise separations from two aircraft by climbing or descending towards one of them. For example, ACAS only considers intruders that it considers to be a threat when selecting an RA. As such, it is possible for ACAS to issue an RA against one intruder that results in a manoeuvre towards another intruder that is not classified as a threat. If the second intruder becomes a threat, the RA will be modified to provide separation from that intruder.

(i) ACAS initial evaluation

(1) The flight crew member’s understanding of the academic training items should be assessed by means of a written test or interactive CBT that records correct and incorrect responses to phrased questions.

(2) The flight crew member’s understanding of the manoeuvre training items should be assessed in a full flight simulator equipped with an ACAS display and controls similar in appearance and operation to those in the aircraft the flight crew member will fly, and the results assessed by a qualified instructor, inspector, or check airman. The range of scenarios should include: corrective RAs; initial preventive RAs; maintain rate RAs; altitude crossing RAs; increase rate RAs; RA reversals; weakening RAs; and multi-threat encounters. The scenarios should also include demonstrations of the consequences of not responding to RAs, slow or late responses, and manoeuvring opposite to the direction called for by the displayed RA.

(3) Alternatively, exposure to these scenarios can be conducted by means of an interactive CBT with an ACAS display and controls similar in appearance and operation to those in the aircraft the pilot will fly. This interactive CBT should depict scenarios in which real-time responses should be made and a record made of whether or not each response was correct.

(j) ACAS recurrent training

(1) ACAS recurrent training ensures that flight crew members maintain the appropriate ACAS knowledge and skills. ACAS recurrent training should be integrated into and/or conducted in conjunction with other established recurrent training programmes. An essential item of recurrent training is the discussion of any significant issues and operational concerns that have been identified by the operator. Recurrent training should also address changes to ACAS logic, parameters or procedures and to any unique ACAS characteristics which flight crew members should be made aware of.

(2) It is recommended that the operator's recurrent training programmes using full flight simulators include encounters with conflicting traffic when these simulators are equipped with ACAS. The full range of likely scenarios may be spread over a 2 year period. If a full flight simulator, as described above, is not available, use should be made of an interactive CBT that is capable of presenting scenarios to which pilot responses should be made in real-time.

SPO.OP.210 Approach and landing conditions — aeroplanes and helicopters

Regulation (EU) 2021/2237

Before commencing an approach operation, the pilot-in-command shall be satisfied that:

(a) the meteorological conditions at the aerodrome or the operating site and the condition of the runway/FATO intended to be used will not prevent a safe approach, landing or go-around, considering the performance information contained in the operations manual; and

(b) the selected aerodrome operating minima are consistent with all of the following:

(1) the operative ground equipment;

(2) the operative aircraft systems;

(3) the aircraft performance;

(4) flight crew qualifications.

LANDING DISTANCE ASSESSMENT— COMPLEX AEROPLANES

(a) The in-flight landing distance assessment should be based on the latest available weather report and runway condition report (RCR) or equivalent information based on the RCR.

(b) The assessment should be initially carried out when the weather report and the RCR are obtained, usually around top of descent. If the planned duration of the flight does not allow the flight crew to carry out the assessment in non-critical phases of flight, the assessment should be carried out before departure.

(c) When meteorological conditions may lead to a degradation of the runway surface condition, the assessment should include consideration of how much deterioration in runway surface friction characteristics may be tolerated, so that a quick decision can be made prior to landing.

(d) The flight crew should monitor the evolution of the actual conditions during the approach, to ensure that they do not degrade below the condition that was previously determined to be the minimum acceptable.

(e) The in-flight determination of the landing distance should be done is such a way that either:

(1) the landing distance available (LDA) on the intended runway is at least 115 % of the landing distance at the estimated time of landing, determined in accordance with the performance information for the assessment of the landing distance at time of arrival (LDTA); or

(2) if performance information for the assessment of the LDTA is not available, the LDA on the intended runway at the estimated time of landing is at least the landing distance determined at the time of dispatch.

(f) If performance information for the assessment of the LDTA is available, it should be based on approved data contained in the AFM, or on other data that is either determined in accordance with the applicable certification standards for aeroplanes or determined by EASA.

(g) Whenever the runway braking action encountered during the landing roll is not as good as reported by the aerodrome operator in the RCR, the pilot-in-command should notify the air traffic services (ATS) by means of a special air-report (AIREP) as soon as practicable.

LANDING DISTANCE ASSESSMENT— OTHER-THAN-COMPLEX AEROPLANES

(a) The in-flight landing distance assessment should be based on the latest available weather report and, if available, RCR.

(b) The assessment should be initially carried out when weather report and RCR are obtained, usually around top of descent. If the planned duration of the flight does not allow the flight crew to carry out the assessment in non-critical phases of flight, the assessment should be carried out before departure.

(c) When meteorological conditions may lead to a degradation of the runway surface condition, the assessment should include consideration of how much deterioration in runway surface friction characteristics may be tolerated, so that a quick decision can be made prior to landing.

(d) Whenever the runway braking action encountered during the landing roll is not as good as reported by the aerodrome operator in the RCR, the pilot-in-command should notify ATS by means of an AIREP as soon as practicable.

LANDING DISTANCE — COMPLEX AEROPLANES

The assessment of the landing distance begins with the acquisition of the latest available weather information and the RCR. The information provided in the RCR is divided in two sections:

(a) The ‘aircraft performance’ section which contains information that is directly relevant in a performance computation.

(b) The ‘situational awareness’ section which contains information that the flight crew should be aware of for a safe operation, but which does not have a direct impact on the performance assessment.

The ‘aircraft performance’ section of the RCR includes an RWYCC, the contaminant type, depth and coverage for each third of the runway.

The determination of the RWYCC is based on the use of the runway condition assessment matrix (RCAM); however, the presentation of the information in the RCAM is appropriate for use by aerodrome personnel trained and competent in assessing the runway condition in a way that is relevant to aircraft performance. While full implementation of the RCAM standard will eventually no longer require the flight crew to derive from various information available to them the appropriate runway condition to be used for the landing performance assessment at the time of arrival, it is desirable that pilots maintain an understanding of the performance effect of various components considered in the assessment.

It is the task of the aerodrome personnel to report the appropriate RWYCC in order to allow the flight crew to assess the landing performance characteristics of the runway in use. When no RWYCC is available in winter conditions, the RCAM provides the flight crew with a combination of the relevant information (runway surface conditions: state and/or contaminant or AIREP in order to determine the RWYCC.

Table 1 below is an excerpt of the RCAM and permits to carry out the primary assessment based on the reported contaminant type and depth, as well as on the OAT.

Table 1: Association between the runway surface condition and the RWYCC based on the reported contaminant type and depth and on the OAT

Runway surface condition

Surface condition descriptor

Depth

Notes

RWYCC

Dry

 

n/a

 

6

Wet

Damp

(any visible dampness)

3 mm or less

Including wet or contaminated runways below 25 % coverage in each runway third

5

 

Wet

Slippery wet

 

 

 

3

Contaminated

Compacted snow

Any

At or below OAT – 15 °C 3

4

Above OAT – 15 °C 3

3

Dry snow

3 mm or less

 

5

More than 3 mm up to 100 mm

Including when any depth occurs on top of compacted snow

3

Any

On top of ice

02

Frost1

Any

 

5

Ice

Any

In cold and dry conditions

1

Slush

3 mm or less

 

5

More than 3 mm up to 15 mm

 

2

Standing water

3 mm or less

 

5

More than 3 mm up to 15 mm

 

2

Any

On top of ice

02

Wet ice

Any

 

02

Wet snow

3 mm or less

 

5

More than 3 mm up to 30 mm

Including when any depth occurs on top of compacted snow

3

Any

On top of ice

02

Note 1: Under certain conditions, frost may cause the surface to become very slippery.

Note 2: Operations in conditions where less-than-poor braking action prevails are prohibited.

Note 3: The runway surface temperature should preferably be used where available.

A primary assessment may have to be downgraded by the aerodrome operator based on an AIREP of lower braking action than the one typically associated with the type and depth of contaminant on the runway or any other observation.

Upgrading a RWYCC 5, 4, 3 or 2 determined by the aerodrome operator from the observed contaminant type is not allowed.

A RWYCC 1 or 0 maybe be upgraded by the aerodrome operator to a maximum of RWYCC 3. The reason for the upgrade will be specified in the ‘situational awareness’ section of the RCR.

When the aerodrome operator is approved for operations on specially prepared winter runways, in accordance with Annex V (Part-ADR.OPS) to Regulation (EU) No 139/2014, the RWYCC of a runway that is contaminated with compacted snow or ice, may be upgraded to RWYCC 4 depending upon a specific treatment of the runway. In such cases, the reason for the upgrade will be specified in the ‘situational awareness’ section of the RCR.

RCR, RWYCC and RCAM — COMPLEX AEROPLANES

A detailed description of the RCR format and content, the RWYCC and the RCAM may be found in Annex V (Part-ADR.OPS) to Regulation (EU) No 139/2014. Further guidance may be found in the following documents:

(a) ICAO Doc 9981 ‘PANS Aerodromes’;

(b) ICAO Doc 4444 ‘PANS ATM’;

(c) ICAO Doc 10064 ‘Aeroplane Performance Manual’; and

(d) ICAO Circular 355 ‘Assessment, Measurement and Reporting of Runway Surface Conditions’.

RUNWAY CONDITION REPORT (RCR) — OTHER-THAN-COMPLEX AEROPLANES

When the aerodrome reports the runway conditions by means of an RCR, the information thereby contained, includes a RWYCC. The determination of the RWYCC is based on the use of the RCAM. The RCAM correlates the RWYCC with the contaminant present on the runway and the braking action.

A detailed description of the RCR format and content, the RWYCC and the RCAM may be found in Annex V (Part-ADR.OPS) to Regulation (EU) No 139/2014. Further guidance may be found in the following documents:

(a) ICAO Doc 9981 ‘PANS Aerodromes’;

(b) ICAO Doc 4444 ‘PANS ATM’;

(c) ICAO Doc 10064 ‘Aeroplane Performance Manual’; and

(d) ICAO Circular 355 ‘Assessment, Measurement and Reporting of Runway Surface Conditions’.

COMPLEX MOTO-POWERED AEROPLANES — PERFORMANCE INFORMATION FOR THE ASSESSMENT OF LDTA

Guidance on performance information for the assessment of the LDTA may be found in:

(a) AMC1 CAT.OP.MPA.303(e) of the AMC & GM to Annex IV (Part CAT) to Regulation (EU) No 965/2012; and

(b) ICAO Doc 10064 ‘Aeroplane Performance Manual’.

REPORTING ON RUNWAY BRAKING ACTION — COMPLEX AEROPLANES

The role of the flight crew in the runway surface condition reporting process does not end once a safe landing has been achieved. While the aerodrome operator is responsible for generating the RCR, flight crew are responsible for providing accurate braking action reports.

The flight crew braking action reports provide feedback to the aerodrome operator regarding the accuracy of the RCR resulting from the observed runway surface conditions.

ATC passes these braking action reports to the aerodrome operator, which in turn uses them in conjunction with the RCAM to determine if it is necessary to downgrade or upgrade the RWYCC.

During busy times, runway inspections and maintenance may be less frequent and need to be sequenced with arrivals. Therefore, aerodrome operators may depend on braking action reports to confirm that the runway surface condition is not deteriorating below the assigned RCR.

Since both the ATC and the aerodrome operator rely on accurate braking action reports, flight crew should use standardised terminology in accordance with ICAO Doc 4444 — ‘PANS ATM’.

The following Table 1 shows the correlation between the terminology to be used in the AIREP to report the braking action and the RWYCC.

Table 1: Association between AIREP and RWYCC

AIREP

(braking action)

Description

RWYCC

N/A

 

6

GOOD

Braking deceleration is normal for the wheel braking effort applied AND directional control is normal.

5

GOOD TO MEDIUM

Braking deceleration OR directional control is between good and medium.

4

MEDIUM

Braking deceleration is noticeably reduced for the wheel braking effort applied OR directional control is noticeably reduced.

3

MEDIUM TO POOR

Braking deceleration OR directional control is between medium and poor.

2

POOR

Braking deceleration is significantly reduced for the wheel braking effort applied OR directional control is significantly reduced.

1

LESS THAN POOR

Braking deceleration is minimal to non-existent for the wheel braking effort applied OR directional control is uncertain.

0

An AIREP should be transmitted to the ATC, in accordance with one of the following specifications, as applicable:

(a) Good braking action is reported as ‘BRAKING ACTION GOOD’.

(b) Good to medium braking action is reported as ‘BRAKING ACTION GOOD TO MEDIUM’.

(c) Medium braking action is reported as ‘BRAKING ACTION MEDIUM’.

(d) Medium to poor braking action is reported as ‘BRAKING ACTION MEDIUM TO POOR’.

(e) Poor braking action is reported as ‘BRAKING ACTION POOR’.

(f) Less than poor braking action is reported as ‘BRAKING ACTION LESS THAN POOR’.

In some cases, the differences between two consecutive levels of the six braking action categories between ‘Good’ and ‘Less than Poor’ may be too subtle for the flight crew to detect. It is therefore acceptable for the flight crew to report on a more coarse scale of ‘Good’, ‘Medium’ and ‘Poor’.

Whenever requested by ATC, or if the braking action encountered during the landing roll is not as previously reported by the aerodrome operator in the RCR, pilots should provide a braking action report. This is especially important and safety relevant where the experienced braking action is worse than the braking action associated with any RWYCC code currently in effect for that portion of the runway concerned.

When the experienced braking action is better than that reported by the aerodrome operator, it is important to report this information, which may trigger further actions for the aerodrome operator in order to upgrade the RCR.

If an aircraft-generated braking action report is available, it should be transmitted, identifying its origin accordingly. If the flight crew have reason to modify the aircraft-generated braking action report based on their judgement, the commander should be able to amend such report.

A braking action AIREP of ‘Less than Poor’ leads to a runway closure until the aerodrome operator can improve the runway condition.

An air safety report should be submitted whenever flight safety has been endangered due to low braking action.

FLIGHT CREW TRAINING

Flight crew should be trained on the use of the RCR, on the use of performance data for the assessment of the LDTA, if available, and on reporting braking action using the AIREP format.

Guidance to develop the content of the training may be found in:

(a) AMC1 CAT.OP.MPA.303 & CAT.OP.MPA.311 of the AMC & GM to Annex IV (Part CAT) to Regulation (EU) No 965/2012, as applicable to the intended operations;

(b) ICAO Doc 10064 ‘Aeroplane Performance Manual’; and

(c) ICAO Circular 355 ‘Assessment, Measurement and Reporting of Runway Surface Conditions’.

FLIGHT CREW TRAINING — OTHER-THAN-COMPLEX AEROPLANES

When the aerodrome reports the runway conditions by means of a RCR, flight crew should be trained on the use of the RCR for the assessment of the landing distance, and on reporting braking action using the AIREP format. Guidance to develop the content of the training may be found in:

(a) ICAO Doc 10064 ‘Aeroplane Performance Manual’; and

(b) ICAO Circular 355 ‘Assessment, Measurement and Reporting of Runway Surface Conditions’.

SPO.OP.211 Approach and landing conditions – helicopters

Regulation (EU) 2019/1387

Before commencing an approach to land, the pilot-in-command shall be satisfied that, according to the information available, the weather at the aerodrome or the operating site and the condition of the final approach and take-off area (FATO) intended to be used would not prevent a safe approach, landing or missed approach.

FATO SUITABILITY

The in-flight determination of the FATO suitability should be based on the latest available meteorological report.

SPO.OP.215 Commencement and continuation of approach

Regulation (EU) 2021/2237

(a) For aeroplanes, if the reported visibility (VIS) or controlling RVR for the runway to be used for landing is less than the applicable minimum, then an instrument approach operation shall not be continued:

(1) past a point at which the aeroplane is 1 000 ft above the aerodrome elevation; or

(2) into the final approach segment (FAS) if the DH or MDH is higher than 1 000 ft.

(b) For helicopters, if the reported RVR is less than 550 m and the controlling RVR for the runway to be used for landing is less than the applicable minimum, then an instrument approach operation shall not be continued:

(1) past a point at which the helicopter is 1 000 ft above the aerodrome elevation; or

(2) into the FAS if the DH or MDH is higher than 1 000 ft.

(c) If the required visual reference is not established, a missed approach shall be executed at or before the DA/H or the MDA/H.

(d) If the required visual reference is not maintained after DA/H or MDA/H, a go-around shall be executed promptly.

(e) Notwithstanding point (a), in the case where no RVR is reported, and the reported VIS is lower, but the converted meteorological visibility (CMV) is greater than the applicable minimum, then the instrument approach can be continued to the DA/H or MDA/H.

(f) Notwithstanding points (a) and (b), if there is no intention to land, the instrument approach may be continued to the DA/H or the MDA/H. A missed approach shall be executed at or before the DA/H or the MDA/H.

APPLICATION OF RVR OR VIS REPORTS — AEROPLANES

(a) There is no prohibition on the commencement of an approach based on the reported RVR or VIS. The restriction in SPO.OP.215 applies only if the RVR or VIS is reported and applies to the continuation of the approach past a point where the aircraft is 1 000 ft above the aerodrome elevation or in the FAS, as applicable.

APPLICATION OF RVR OR VIS REPORTS — HELICOPTERS

(b) There is no prohibition on the commencement of an approach based on the reported RVR. The restriction in SPO.OP.215 applies to the continuation of the approach past a point where the aircraft is 1 000 ft above the aerodrome elevation or into the FAS, as applicable.

The prohibition to continue the approach applies only if the RVR is reported and is below 550 m and is below the operating minima. There is no prohibition based on VIS.

(c) If the reported RVR is 550 m or greater, but it is less than the RVR calculated in accordance with AMC5 CAT.OP.MPA.110, a go-around is likely to be necessary since visual reference may not be established at the DH or MDH. Similarly, in the absence of an RVR report, the reported visibility or a digital image may indicate that a go-around is likely. The pilot-in-command should consider available options, based on a thorough assessment of risk, such as diverting to an alternate, before commencing the approach.

APPLICATION OF RVR OR VIS REPORTS — ALL AIRCRAFT

(d) If a deterioration in the RVR or VIS is reported once the aircraft is below 1 000 ft or in the FAS, as applicable, then there is no requirement for the approach to be discontinued. In this situation, the normal visual reference requirements would apply at the DA/H.

(e) Where additional RVR information is provided (e.g. midpoint and stop end), this is advisory; such information may be useful to the pilot in order to determine whether there will be sufficient visual reference to control the aircraft during roll-out and taxi. For operations where the aircraft will be controlled manually during roll-out, Table 1 in AMC1 SPA.LVO.100(a) provides an indication of the RVR that may be required to allow manual lateral control of the aircraft on the runway.

MINIMUM RVR FOR CONTINUATION OF APPROACH — AEROPLANES

(a) The controlling RVR should be the touchdown RVR.

(b) If the touchdown RVR is not reported, then the midpoint RVR should be the controlling RVR.

(c) Where the RVR is not available, CMV should be used, except for the purpose of continuation of an approach in LVO in accordance with AMC8 SPO.OP.110.

MINIMUM RVR FOR CONTINUATION OF APPROACH — HELICOPTERS

(a) The controlling RVR should be the touchdown RVR.

(b) If the touchdown RVR is not reported, then the midpoint RVR should be the controlling RVR.

VISUAL REFERENCES FOR INSTRUMENT APPROACH OPERATIONS

For instrument approach operations Type A and CAT I instrument approach operations Type B, at least one of the visual references specified below should be distinctly visible and identifiable to the pilot at the MDA/H or the DA/H:

(a) elements of the approach lighting system;

(b) the threshold;

(c) the threshold markings;

(d) the threshold lights;

(e) the threshold identification lights;

(f) the visual glide path indicator;

(g) the TDZ or TDZ markings;

(h) the TDZ lights;

(i) FATO/runway edge lights;

(j) for helicopter PinS approaches, the identification beacon light and visual ground reference;

(k) for helicopter PinS approaches, the identifiable elements of the environment defined on the instrument chart;

(l) for helicopter PinS approaches with instructions to ‘proceed VFR’, sufficient visual cues to determine that VFR criteria are met; or

(m) other visual references specified in the operations manual.

APPROACHES WITH NO INTENTION TO LAND

The approach may be continued to the DA/H or the MDA/H regardless of the reported RVR or VIS. Such operations should be coordinated with the air traffic services (ATS).

SPO.OP.230 Standard operating procedures

Regulation (EU) No 379/2014

(a) Before commencing a specialised operation, the operator shall conduct a risk assessment, assessing the complexity of the activity to determine the hazards and associated risks inherent in the operation and establish mitigating measures.

(b) Based on the risk assessment, the operator shall establish standard operating procedures (SOP) appropriate to the specialised activity and aircraft used taking account of the requirements of subpart E. The SOP shall be part of the operations manual or a separate document. SOP shall be regularly reviewed and updated, as appropriate.

(c) The operator shall ensure that specialised operations are performed in accordance with SOP.

DEVELOPMENT OF STANDARD OPERATING PROCEDURES

(a) SOPs should be developed to a standard format in accordance with AMC2 SPO.OP.230 (SOP template) and taking into account the results of the risk assessment process.

(b) SOPs should be based on a systematic risk assessment to ensure that the risks associated with the task are acceptable. The risk assessment should describe the activity in detail, identify the relevant hazards, analyse the causes and consequences of accidental events and establish methods to treat the associated risk.

TEMPLATE

(a) Nature and complexity of the activity:

(1) The nature of the activity and exposure. The nature of the flight and the risk exposure (e.g. low height) should be described.

(2) The complexity of the activity. Detail should be provided on how demanding the activity is with regard to the required piloting skills, the crew composition, the necessary level of experience, the ground support, safety and individual protective equipment that should be provided for persons involved.

(3) The operational environment and geographical area. The operational environment and geographical area over which the operation takes place should be described:

(i) congested hostile environment: aircraft performance standard, compliance with rules of the air, mitigation of third party risk;

(ii) mountain areas: altitude, performance, the use/non-use of oxygen with mitigating procedures;

(iii) sea areas: sea state and temperature, risk of ditching, availability of search and rescue, survivability, carriage of safety equipment;

(iv) desert areas: carriage of safety equipment, reporting procedures, search and rescue information; and

(v) other areas.

(4) The application of risk assessment and evaluation. The method of application of (a)(1) to (a)(3) to the particular operation so as to minimise risk should be described. The description should reference the risk assessment and the evaluation on which the procedure is based. The SOPs should:

(i) contain elements relevant to the operational risk management performed during flight;

(ii) contain limitations, where required, such as weather, altitudes, speeds, power margins, masses, landing site size; and

(iii) list functions required to monitor the operation. Special monitoring requirements in addition to the normal functions should be described in the SOPs.

(b) Aircraft and equipment:

(1) The aircraft. The category of aircraft to be used for the activity should be indicated (e.g. helicopter/aeroplane, single/multi-engined, other-than complex motor‑powered/complex motor-powered, classic tail rotor/Fenestron/no tail rotor (NOTAR) equipped). In particular, for helicopters, the necessary level of performance certification (Category A/B) should be specified.

(2) Equipment. All equipment required for the activity should be listed. This includes installed equipment certified in accordance with Part-21 as well as equipment approved in accordance with other officially recognised standards. A large number of activities require, in addition to the standard radio communication equipment, additional air‑to‑ground communication equipment. This should be listed and the operational procedure should be defined.

(c) Crew members:

(1) The crew composition, including the following, should be specified:

(i) minimum flight crew (according to the appropriate manual); and

(ii) additional flight crew.

(2) In addition, for flight crew members, the following should be specified:

(i) selection criteria (initial qualification, flight experience, experience of the activity);

(ii) initial training (volume and content of the training); and

(iii) recent experience requirement and/or recurrent training (volume and content of the training).

(3) If the operator specifies a crew composition of more than one pilot, the following should apply:

(i) the SOPs should ensure that the pilot flying and pilot monitoring functions are possible from either pilot’s seat throughout the flight; and

(ii) the operator should adapt the SOPs to the specified crew composition.

The criteria listed in (c)(2)(i) to (c)(2)(iii) should take into account the operational environment and the complexity of the activity and should be detailed in the training programmes.

(d) Task specialists:

(1) Whenever a task specialist is required, his/her function on board should be clearly defined. In addition, the following should be specified:

(i) selection criteria (initial background, experience of the activity);

(ii) initial training (volume and content of the training); and

(iii) recent experience requirement and/or recurrent training (volume and content of the training).

The criteria listed in (d)(1) should take into account the specialisation of the task specialist and should be detailed in the training programmes.

(2) There is a large number of activities for which task specialists are required. This chapter should detail the following for such personnel:

(i) specialisation;

(ii) previous experience; and

(iii) training or briefing.

Briefing or specific training for task specialists referred to in (d)(2) should be detailed in the training programmes.

(e) Performance:

This chapter should detail the specific performance requirements to be applied, in order to ensure an adequate power margin.

(f) Normal procedures:

(1) Operating procedures. The operating procedures to be applied by the flight crew, including the coordination with task specialists.

(2) Ground procedures. The procedures to be applied by the task specialists should be described, e.g. loading/unloading, cargo hook operation.

(g) Emergency procedures:

(1) Operating procedures. The emergency procedures to be applied by the flight crew, the coordination with the task specialist and coordination between the flight crew and task specialists should be described.

(2) Ground procedures. The emergency procedures to be applied by the task specialists (e.g. in the case of a forced landing) should be specified.

(h) Ground equipment:

This chapter should detail the nature, number and location of ground equipment required for the activity, such as:

(1) refuelling facilities, dispenser and storage;

(2) firefighting equipment;

(3) size of the operating site (landing surface, loading/unloading area); and

(4) ground markings.

(i) Records:

It should be determined which records specific to the flight(s) are to be kept, such as task details, aircraft registration, pilot-in-command, flight times, weather and any remarks, including a record of occurrences affecting flight safety or the safety of persons or property on the ground.

TEMPLATE FORMS

Figure 1 — Development of a SOP based on a risk assessment

Template Form A — Risk assessment (RA)

Date:  RA of  Responsible: 

Purpose:

Type of operation and brief description:

Participants, working group:

Preconditions, assumptions and simplifications:

Data used:

Description of the analysis method:

External context:

 Regulatory requirements

 Approvals

 Environmental conditions (visibility, wind, turbulence, contrast, light, elevation, etc. unless evident from the SOPs)

 Stakeholders and their potential interest

Internal context:

 Type(s) of aircraft

 Personnel and qualifications

 Combination/similarity with other operations/SOPs

 Other RA used/considered/plugged in

Existing barriers and emergency preparedness:

Monitoring and follow up:

Description of the risk:

Risk evaluation:

Conclusions:

Template Form B — Hazard identification (HI)

Date: ………………………………..HI of …………………………… Responsible: ………………………………………………

Phase of operation

Hazard ref

Hazard

Causes

Existing controls

Controls ref

Comments

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Note:

Haz ref: A unique number for hazards, e.g. for use in a database

Controls ref: A unique number for the existing controls

Template Form C — Mitigating measures

Date: ………………..................... RA of ……………………… Responsible: ………………………………………………

Phase of operation

Haz ref

Consequence

Existing mitigation actions

Mitigation

ref

L

S

Further mitigation required

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Note:

Haz ref: A unique number for hazards, e.g. for use in a database

Mitigation ref: A unique number for the mitigation actions

L:  Likelihood

S: Severity

Template register A — risk register

Ref

Operation/ Procedure

Ref

Hazard

Ref

Consequences

Mitigation actions

L

S

Monitoring

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Note:

L:  Likelihood

S:  Severity

SPO.OP.235 EFVS 200 operations

Regulation (EU) 2021/2237

(a) An operator that intends to conduct EFVS 200 operations with operational credits and without a specific approval shall ensure that:

(1) the aircraft is certified for the intended operations;

(2) only runways, FATOs and IAPs suitable for EFVS operations are used;

(3) the flight crew are competent to conduct the intended operation and a training and checking programme for the flight crew members and relevant personnel involved in the flight preparation is established;

(4) operating procedures are established;

(5) any relevant information is documented in the minimum equipment list (MEL);

(6) any relevant information is documented in the maintenance programme;

(7) safety assessments are carried out and performance indicators are established to monitor the level of safety of the operation; and

(8) the aerodrome operating minima take into account the capability of the system used.

(b) The operator shall not conduct EFVS 200 operations when conducting LVOs.

(c) Notwithstanding point (a)(1), the operator may use EVSs meeting the minimum criteria to conduct EFVS 200 operations, provided that this is approved by the competent authority.

GM1 SPO.OP.235 EFVS 200 operations

ED Decision 2022/012/R

GENERAL

(a) EFVS operations exploit the improved visibility provided by the EFVS to extend the visual segment of an instrument approach. EFVSs cannot be used to extend the instrument segment of an approach and thus the DH for EFVS 200 operations is always the same as for the same approach conducted without EFVS.

(b) Equipment for EFVS 200 operations

(1) In order to conduct EFVS 200 operations, a certified EFVS is used (EFVS-A or EFVS-L). An EFVS is an enhanced vision system (EVS) that also incorporates a flight guidance system and displays the image on a HUD or equivalent display. The flight guidance system will incorporate aircraft flight information and flight symbology.

(2) In multi-pilot operations, a suitable display of EFVS sensory imagery is provided to the pilot monitoring.

(c) Suitable approach procedures

(1) Types of approach operation are specified in AMC1 SPO.OP.235(a)(2).

EFVS 200 operations are used for 3D approach operations. This may include operations based on NPA procedures, approach procedures with vertical guidance and PA procedures including approach operations requiring specific approvals, provided that the operator holds the necessary approvals.

(2) Offset approaches

Refer to AMC1 SPO.OP.235(a)(2).

(3) Circling approaches

EFVSs incorporate a HUD or an equivalent system so that the EFVS image of the scene ahead of the aircraft is visible in the pilot’s forward external FOV. Circling operations require the pilot to maintain visual references that may not be directly ahead of the aircraft and may not be aligned with the current flight path. EFVSs cannot therefore be used in place of natural visual reference for circling approaches.

(d) Aerodrome operating minima for EFVS 200 operations are determined in accordance with AMC1 SPO.OP.235(a)(8).

The performance of EFVSs depends on the technology used and weather conditions encountered. Table 1 ‘Operations utilising EFVS: RVR reduction’ has been developed after an operational evaluation of two different EVSs, both using infrared sensors, along with data and support provided by the FAA. Approaches were flown in a variety of conditions including fog, rain and snow showers, as well as at night to aerodromes located in mountainous terrain. Table 1 contains conservative figures to cater for the expected performance of infrared sensors in the variety of conditions that might be encountered. Some systems may have better capability than those used for the evaluation, but credit cannot be taken for such performance in EFVS 200 operations.

(e) The conditions for commencement and continuation of the approach are in accordance with SPO.OP.215.

Pilots conducting EFVS 200 operations may commence an approach and continue that approach below 1 000 ft above the aerodrome or into the FAS if the reported RVR or CMV is equal to or greater than the lowest RVR minima determined in accordance with AMC1 SPO.OP.235(a)(8) and if all the conditions for the conduct of EFVS 200 operations are met.

Should any equipment required for EFVS 200 operations be unserviceable or unavailable, the conditions to conduct EFVS 200 operations would not be satisfied, and the approach should not be commenced. In the event of failure of the equipment required for EFVS 200 operations after the aircraft descends below 1 000 ft above the aerodrome or into the FAS, the conditions of SPO.OP.230 would no longer be satisfied unless the RVR reported prior to commencement of the approach was sufficient for the approach to be flown without the use of EFVS in lieu of natural vision.

(f) EFVS image requirements at the DA/H are specified in AMC1 SPO.OP.235(a)(4).

The requirements for features to be identifiable on the EFVS image in order to continue approach below the DH are more stringent than the visual reference requirements for the same approach flown without EFVS. The more stringent standard is needed because the EFVS might not display the colour of lights used to identify specific portions of the runway and might not consistently display the runway markings. Any visual approach path indicator using colour‑coded lights may be unusable.

(g) Obstacle clearance in the visual segment

The ‘visual segment’ is the portion of the approach between the DH or the MAPt and the runway threshold. In the case of EFVS 200 operations, this part of the approach may be flown using the EFVS image as the primary reference and obstacles may not always be identifiable on an EFVS image. The operational assessment specified in AMC1 SPO.OP.235(a)(2) is therefore required to ensure obstacle clearance during the visual segment.

(h) Visual reference requirements at 200 ft above the threshold

For EFVS 200 operations, natural visual reference is required by a height of 200 ft above the runway threshold. The objective of this requirement is to ensure that the pilot will have sufficient visual reference to land. The visual reference should be the same as that required for the same approach flown without the use of EFVS.

Some EFVSs may have additional requirements that have to be fulfilled at this height to allow the approach to continue, such as a requirement to check that elements of the EFVS display remain correctly aligned and scaled to the external view. Any such requirements will be detailed in the AFM and included in the operator’s procedures.

(i) Specific approval for EFVS

In order to use EFVS without natural visual reference below 200 ft above the threshold, the operator needs to hold a specific approval in accordance with Part-SPA.

(j) Go-around

A go-around will be promptly executed if the required visual references are not maintained on the EFVS image at any time after the aircraft has descended below the DA/H or if the required visual references are not distinctly visible and identifiable using natural vision after the aircraft is below 200 ft. It is considered more likely that an EFVS 200 operation could result in the initiation of a go-around below the DA/H than the equivalent approach flown without EFVS and thus the operational assessment required by AMC1 SPO.OP.235(a)(2) takes into account the possibility of a balked landing.

An obstacle free zone (OFZ) may also be provided for CAT I PA procedures. Where an OFZ is not provided for a CAT I precision approach, this will be indicated on the approach chart. NPA procedures and approach procedures with vertical guidance provide obstacle clearance for the missed approach based on the assumption that a go-around is executed at the MAPt and not below the MDH.

EQUIPMENT CERTIFICATION

For EFVS 200 operations, the aircraft should be equipped with an approach system using EFVS-A or a landing system using EFVS-L.

AERODROMES AND INSTRUMENT PROCEDURES SUITABLE FOR EFVS 200 OPERATIONS

(a) For EFVS 200 operations, the operator should verify the suitability of a runway before authorising EFVS operations to that runway through an operational assessment taking into account the following elements:

(1) the obstacle situation;

(2) the type of aerodrome lighting;

(3) the available IAPs;

(4) the aerodrome operating minima; and

(5) any non-standard conditions that may affect the operations.

(b) EFVS 200 operations should only be conducted as 3D operations, using an IAP in which the final approach track is offset by a maximum of 3 degrees from the extended centre line of the runway.

(c) The IAP should be designed in accordance with PANS-OPS, Volume I (ICAO Doc 8168) or equivalent criteria.

VERIFICATION OF THE SUITABILITY OF RUNWAYS FOR EFVS 200 OPERATIONS

The operational assessment before authorising the use of a runway for EFVS 200 operations may be conducted as follows:

(a) Check whether the runway has been promulgated as suitable for EFVS 200 operations or is certified as a PA category II or III runway by the State of the aerodrome. If this is so, then check whether and where the approach and runway lights installed (notably incandescent or LED lights) are adequate for the EFVS equipment used by the operator.

(b) If the check in point (a) above comes out negative (the runway is not promulgated as EFVS suitable or is not category II or III), then proceed as follows:

(1) For straight-in IAPs, US Standard for Terminal Instrument Procedures (TERPS) may be considered to be acceptable as an equivalent to PANS-OPS. If other design criteria than PANS‑OPS or US TERPS are used, the operations should not be conducted.

(2) If an OFZ is established, this will ensure adequate obstacle protection from 960 m before the threshold. If an OFZ is not established or if the DH for the approach is above 250 ft, then check whether there is a visual segment surface (VSS).

(3) VSSs are required for procedures published after 15 March 2007, but the existence of the VSS has to be verified through an aeronautical information publication (AIP), operations manual Part C, or direct contact with the aerodrome. Where the VSS is established, it may not be penetrated by obstacles. If the VSS is not established or is penetrated by obstacles and an OFZ is not established, then the operations should not be conducted. Note: obstacles of a height of less than 50 ft above the threshold may be disregarded when assessing the VSS.

(4) Runways with obstacles that require visual identification and avoidance should not be accepted.

(5) For the obstacle protection of a balked landing where an OFZ is not established, the operator may specify that pilots follow a departure procedure in the event of a balked landing, in which case it is necessary to verify that the aircraft will be able to comply with the climb gradients published for the instrument departure procedures for the expected landing conditions.

(6) Perform an assessment of the suitability of the runway which should include whether the approach and runway lights installed (notably incandescent or LED lights) are adequate for the EFVS equipment used by the operator.

(c) If the AFM stipulates specific requirements for approach procedures, then the operational assessment should verify that these requirements can be met.

INITIAL TRAINING FOR EFVS 200 OPERATIONS

Operators should ensure that flight crew members complete the following conversion training before being authorised to conduct EFVS operations unless credits related to training and checking for previous experience on similar aircraft types are defined in the operational suitability data established in accordance with Regulation (EU) No 748/2012:

(a) A course of ground training including at least the following:

(1) characteristics and limitations of head-up displays (HUDs) or equivalent display systems including information presentation and symbology;

(2) EFVS sensor performance in different weather conditions, sensor limitations, scene interpretation, visual anomalies and other visual effects;

(3) EFVS display, control, modes, features, symbology, annunciations and associated systems and components;

(4) the interpretation of EFVS imagery;

(5) the interpretation of approach and runway lighting systems and display characteristics when using EFVS;

(6) pre-flight planning and selection of suitable aerodromes and approach procedures;

(7) principles of obstacle clearance requirements;

(8) the use and limitations of RVR assessment systems;

(9) normal, abnormal and emergency procedures for EFVS 200 operations;

(10) the effect of specific aircraft/system malfunctions;

(11) human factors aspects of EFVS 200 operations; and

(12) qualification requirements for pilots to obtain and retain approval for EFVS 200 operations.

(b) A course of FSTD training and/or flight training in two phases as follows:

(1) Phase one (EFVS 200 operations with aircraft and all equipment serviceable) — objectives:

(i) understand the operation of equipment required for EFVS 200 operations;

(ii) understand operating limitations of the installed EFVS;

(iii) practise the use of HUD or equivalent display systems;

(iv) practise the set-up and adjustment of EFVS equipment in different conditions (e.g. day and night);

(v) practise the monitoring of automatic flight control systems, EFVS information and status annunciators;

(vi) practise the interpretation of EFVS imagery;

(vii) become familiar with the features needed on the EFVS image to continue approach below the DH;

(viii) practise the identification of visual references using natural vision while using EFVS equipment;

(ix) master the manual aircraft handling relevant to EFVS 200 operations including, where appropriate, the use of the flare cue and guidance for landing;

(x) practise coordination with other crew members; and

(xi) become proficient at procedures for EFVS 200 operations.

(2) Phase one of the training should include the following exercises:

(i) the required checks for satisfactory functioning of equipment, both on the ground and in flight;

(ii) the use of HUD or equivalent display systems during all phases of flight;

(iii) approach using the EFVSs installed on the aircraft to the appropriate DH and transition to visual flight and landing;

(iv) approach with all engines operating using the EFVS, down to the appropriate DH followed by a missed approach, all without external visual reference, as appropriate.

(3) Phase two (EFVS 200 operations with aircraft and equipment failures and degradations) — objectives:

(i) understand the effect of known aircraft unserviceabilities including use of the MEL;

(ii) understand the effect of failed or downgraded equipment on aerodrome operating minima;

(iii) understand the actions required in response to failures and changes in the status of the EFVS including HUD or equivalent display systems;

(iv) understand the actions required in response to failures above and below the DH;

(v) practise abnormal operations and incapacitation procedures; and

(vi) become proficient at dealing with failures and abnormal situations during EFVS 200 operations.

(4) Phase two of the training should include the following exercises:

(i) approaches with engine failures at various stages of the approach;

(ii) approaches with failures of the EFVS at various stages of the approach, including failures between the DH and the height below which an approach should not be continued if natural visual reference is not acquired, require either:

(A) reversion to head down displays to control missed approach; or

(B) reversion to flight with downgraded or no guidance to control missed approaches from the DH or below, including those which may result in a touchdown on the runway;

(iii) incapacitation procedures appropriate to EFVS 200 operations;

(iv) failures and procedures applicable to the specific EFVS installation and aircraft type; and

(v) FSTD training, which should include minimum eight approaches.

RECURRENT TRAINING AND CHECKING FOR EFVS 200 OPERATIONS

(a) The operator should ensure that the pilots are competent to perform EFVS 200 operations. To do so, pilots should be trained every 6 months by performing at least two approaches on each type of aircraft operated.

(b) The operator should ensure that the pilots’ competence to perform EFVS 200 operations is checked at each required operator proficiency check by performing at least two approaches on each type of aircraft operated, of which one should be flown without natural vision to 200 ft.

RECENT EXPERIENCE REQUIREMENTS FOR EFVS 200 OPERATIONS

Pilots should complete a minimum of four approaches using the operator’s procedures for EFVS 200 operations during the validity period of the periodic operator proficiency check unless credits related to currency are defined in the operational suitability data established in accordance with Regulation (EU) No 748/2012.

DIFFERENCES TRAINING FOR EFVS 200 OPERATIONS

(a) The operator should ensure that the flight crew members authorised to conduct EFVS 200 operations are provided with differences training or familiarisation whenever there is a change to any of the following:

(1) the technology used in the flight guidance and flight control system;

(2) the HUD or equivalent display systems;

(3) the operating procedures.

(b) The differences training should:

(1) meet the objectives of the appropriate initial training course;

(2) take into account the flight crew members’ previous experience; and

(3) take into account the operational suitability data established in accordance with Regulation (EU) No 748/2012.

TRAINING FOR EFVS 200 OPERATIONS

If a flight crew member is to be authorised to operate as pilot flying and pilot monitoring during EFVS 200 operations, then the flight crew member should complete the required FSTD training for each operating capacity.

RECURRENT CHECKING FOR EFVS 200 OPERATIONS

In order to provide the opportunity to practise decision-making in the event of system failures and failure to acquire natural visual reference, the recurrent training and checking for EFVS 200 operations is recommended to periodically include different combinations of equipment failures, go-around due to loss of visual reference, and landings.

OPERATING PROCEDURES FOR EFVS 200 OPERATIONS

(a) For EFVS 200 operations, the following should apply:

(1) the pilot flying should use the EFVS throughout the approach;

(2) in multi-pilot operations, a suitable display of EFVS sensory imagery should be provided to the pilot monitoring;

(3) the approach between the FAF and the DA/H should be flown using vertical flight path guidance;

(4) the approach may be continued below the DA/H provided that the pilot can identify on the EFVS image either:

(i) the approach light system; or

(ii) both of the following:

(A) the runway threshold identified by the beginning of the runway landing surface, the threshold lights or the runway end identifier lights; and

(B) the TDZ identified by the TDZ lights, the TDZ runway markings or the runway lights;

(5) a missed approach should be executed promptly if the required visual reference is not distinctly visible and identifiable to the pilot without reliance on the EFVS by 200 ft above the threshold.

(b) Operating procedures for EFVS 200 operations should:

(1) be consistent with the AFM;

(2) be appropriate to the technology and equipment to be used;

(3) specify the duties and responsibilities of each flight crew member in each relevant phase of flight;

(4) ensure that flight crew workload is managed to facilitate effective decision-making and monitoring of the aircraft; and

(5) deviate to the minimum extent practicable from normal procedures used for routine operations.

(c) Operating procedures should include:

(1) the required checks for the satisfactory functioning of the aircraft equipment, both before departure and in flight;

(2) the correct seating and eye position;

(3) determination of aerodrome operating minima;

(4) the required visual references at the DH;

(5) the action to be taken if natural visual reference is not acquired by 200 ft;

(6) the action to be taken in the event of loss of the required visual reference; and

(7) procedures for balked landing.

(d) Operating procedures for EFVS 200 operations should be included in the operations manual.

AERODROME OPERATING MINIMA — EFVS 200 OPERATIONS

When conducting EFVS 200 operations:

(a) the DA/H used should be the same as for operations without EFVS;

(b) the lowest RVR minima to be used should be determined by reducing the RVR presented in:

(1) Table 8 in AMC5 SPO.OP.110 in accordance with Table 1 below for aeroplanes;

(2) Table 12 of AMC6 SPO.OP.110 in accordance with Table 1 below for helicopters;

(c) in case of failed or downgraded equipment, Table 15 in AMC9 SPO.OP.110 should apply.

Table 1

Operations utilising EFVS: RVR reduction

RVR (m) presented in Table 8 in AMC5 SPO.OP.110 or in Table 12 of AMC6 SPO.OP.110

RVR (m)
for EFVS 200 operations

550

550

600

550

650

550

700

550

750

550

800

550

900

600

1 000

650

1 100

750

1 200

800

1 300

900

1 400

900

1 500

1 000

1 600

1 100

1 700

1 100

1 800

1 200

1 900

1 300

2 000

1 300

2 100

1 400

2 200

1 500

2 300

1 500

2 400

1 600

EVFS 200 WITH LEGACY SYSTEMS UNDER AN APPROVAL

The EVS should be certified before 1 January 2022 as ‘EVS with an operational credit’.

GM1 SPO.OP.235(c) EFVS 200 operations

ED Decision 2022/012/R

The competent authority referred to in SPO.OP.235 point (c) is the competent authority for the oversight of the operator, as established in ORO.GEN.105.