Skip to content

A gradual release of Avioverse begins in October 2026. Request early access →

CAT.POL.H.310 Take-off

ANNEX IV (Part-CAT) · Regulation (EU) No 965/2012 · EAR revision 27 Mar 2026

IRImplementing rule

CAT.POL.H.310Take-off

(a)The take-off mass shall not exceed the maximum mass specified for a rate of climb of 150 ft/min at 300 m (1 000 ft) above the level of the aerodrome or operating site with the critical engine inoperative and the remaining engine(s) operating at an appropriate power rating.

(b)For operations other than those specified in CAT.POL.H.305, the take-off shall be conducted such that a safe forced landing can be executed until the point where safe continuation of the flight is possible.

(c)For operations in accordance with CAT.POL.H.305, in addition to the requirements of (a):

(1)the take-off mass shall not exceed the maximum mass specified in the AFM for an all engines operative out of ground effect (AEO OGE) hover in still air with all engines operating at an appropriate power rating; or

(2)for operations from a helideck:

(i)with a helicopter that has an MOPSC of more than 19; or

(ii)any helicopter operated from a helideck located in a hostile environment, the take-off mass shall take into account: the procedure; deck-edge miss and drop down appropriate to the height of the helideck with the critical engine(s) inoperative and the remaining engines operating at an appropriate power rating.

(d)When showing compliance with (a) to (c), account shall be taken of the appropriate parameters of CAT.POL.H.105(c) at the point of departure.

(e)That part of the take-off before the requirement of CAT.POL.H.315 is met shall be conducted in sight of the surface.

IR · CAT.POL.H.310 — Regulation (EU) No 965/2012 · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

GMGuidance material

GM1 CAT.POL.H.310(c)& CAT.POL.H.325(c) Take-off and landing

Show the text

PROCEDURE FOR CONTINUED OPERATIONS TO HELIDECKS

(a)Factors to be considered when taking off from or landing on a helideck

(1)In order to take account of the considerable number of variables associated with the helideck environment, each take-off and landing may require a slightly different profile. Factors such as helicopter mass and centre of gravity, wind velocity, turbulence, deck size, deck elevation and orientation, obstructions, power margins, platform gas turbine exhaust plumes etc., will influence both the take-off and landing. In particular, for the landing, additional considerations such as the need for a clear go-around flight path, visibility and cloud base, etc. will affect the commander’s decision on the choice of landing profile. Profiles may be modified, taking account of the relevant factors noted above and the characteristics of individual helicopter types.

(b)Performance

(1)To perform the following take-off and landing profiles, adequate all engines operating (AEO) hover performance at the helideck is required. In order to provide a minimum level of performance, data (derived from the AFM AEO out of ground effect (OGE)) should be used to provide the maximum take-off or landing mass. Where a helideck is affected by downdrafts or turbulence or hot gases, or where the take-off or landing profile is obstructed, or the approach or take-off cannot be made into wind, it may be necessary to decrease this take-off or landing mass by using a suitable calculation method. The helicopter mass should not exceed that required by CAT.POL.H.310(a) or CAT.POL.H.325(a). (For helicopter types no longer supported by the manufacturer, data may be established by the operator, provided it is acceptable to the competent authority.)

(c)Take-off profile

(1)The take-off should be performed in a dynamic manner ensuring that the helicopter continuously moves vertically from the hover to the rotation point (RP) and thence into forward flight. If the manoeuvre is too dynamic, then there is an increased risk of losing spatial awareness (through loss of visual cues) in the event of a rejected take-off, particularly at night.

(2)If the transition to forward flight is too slow, the helicopter is exposed to an increased risk of contacting the deck edge in the event of an engine failure at or just after the point of cyclic input (RP).

(3)It has been found that the climb to RP is best made between 110 % and 120 % of the power required in the hover. This power offers a rate of climb that assists with deck-edge clearance following engine failure at RP, whilst minimising ballooning following a failure before RP. Individual types will require selection of different values within this range.

Figure 1 Take-off profile [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(d)Selection of a lateral visual cue

(1)In order to obtain the maximum performance in the event of an engine failure being recognised at or just after RP, the RP should be at its optimum value, consistent with maintaining the necessary visual cues. If an engine failure is recognised just before RP, the helicopter, if operating at a low mass, may ‘balloon’ a significant height before the reject action has any effect. It is, therefore, important that the pilot flying selects a lateral visual marker and maintains it until the RP is achieved, particularly on decks with few visual cues. In the event of a rejected take-off, the lateral marker will be a vital visual cue in assisting the pilot to carry out a successful landing.

(e)Selection of the rotation point

(1)The optimum RP should be selected to ensure that the take-off path will continue upwards and away from the deck with AEO, but minimising the possibility of hitting the deck edge due to the height loss in the event of an engine failure at or just after RP.

(2)The optimum RP may vary from type to type. Lowering the RP will result in a reduced deck edge clearance in the event of an engine failure being recognised at or just after RP. Raising the RP will result in possible loss of visual cues, or a hard landing in the event of an engine failure just prior to RP.

(f)Pilot reaction times

(1)Pilot reaction time is an important factor affecting deck edge clearance in the event of an engine failure prior to or at RP. Simulation has shown that a delay of 1 second can result in a loss of up to 15 ft in deck edge clearance.

(g)Variation of wind speed

(1)Relative wind is an important parameter in the achieved take-off path following an engine failure; wherever practicable, take-off should be made into wind. Simulation has shown that a 10-kt wind can give an extra 5-ft deck edge clearance compared to a zero wind condition.

(h)Position of the helicopter relative to the deck edge

(1)It is important to position the helicopter as close to the deck edge (including safety nets) as possible whilst maintaining sufficient visual cues, particularly a lateral marker.

(2)The ideal position is normally achieved when the rotor tips are positioned at the forward deck edge. This position minimises the risk of striking the deck edge following recognition of an engine failure at or just after RP. Any take-off heading which causes the helicopter to fly over obstructions below and beyond the deck edge should be avoided if possible. Therefore, the final take-off heading and position will be a compromise between the take-off path for least obstructions, relative wind, turbulence and lateral marker cue considerations.

(i)Actions in the event of an engine failure at or just after RP

(1)Once committed to the continued take-off, it is important, in the event of an engine failure, to rotate the aircraft to the optimum attitude in order to give the best chance of missing the deck edge. The optimum pitch rates and absolute pitch attitudes should be detailed in the profile for the specific type.

(j)Take-off from helidecks that have significant movement

(1)This technique should be used when the helideck movement and any other factors, e.g. insufficient visual cues, makes a successful rejected take-off unlikely. Weight should be reduced to permit an improved one-engine-inoperative capability, as necessary.

(2)The optimum take-off moment is when the helideck is level and at its highest point, e.g. horizontal on top of the swell. Collective pitch should be applied positively and sufficiently to make an immediate transition to climbing forward flight. Because of the lack of a hover, the take-off profile should be planned and briefed prior to lift off from the deck.

(k)Standard landing profile

(1)The approach should be commenced into wind to a point outboard of the helideck. Rotor tip clearance from the helideck edge should be maintained until the aircraft approaches this position at the requisite height (type dependent) with approximately 10 kt of ground-speed and a minimal rate of descent. The aircraft is then flown on a flight path to pass over the deck edge and into a hover over the safe landing area. Figure 2 Standard landing profile [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(l)Offset landing profile

(1)If the normal landing profile is impracticable due to obstructions and the prevailing wind velocity, the offset procedure may be used. This should involve flying to a hover position, approximately 90° offset from the landing point, at the appropriate height and maintaining rotor tip clearance from the deck edge. The helicopter should then be flown slowly but positively sideways and down to position in a low hover over the landing point. Normally, the committal point (CP) will be the point at which helicopter begins to transition over the helideck edge.

(m)Training

(1)These techniques should be covered in the training required by Annex III (Part-ORO).

GM · GM1 CAT.POL.H.310(c) — Regulation (EU) No 965/2012 · ED Decision 2014/015/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

GMGuidance material

GM1 CAT.POL.H.310& CAT.POL.H.325 Take-off and landing

Show the text

TAKE-OFF AND LANDING TECHNIQUES

(a)This GM describes three types of operation to/from helidecks and elevated FATOs by helicopters operating in performance class 2.

(b)In two cases of take-off and landing, exposure time is used. During the exposure time (which is only approved for use when complying with CAT.POL.H.305), the probability of an engine failure is regarded as extremely remote. If an engine failure occurs during the exposure time, a safe forced landing may not be possible.

(c)Take-off — non-hostile environment (without an approval to operate with an exposure time) CAT.POL.H.310(b).

(1)Figure 1 shows a typical take-off profile for performance class 2 operations from a helideck or an elevated FATO in a non-hostile environment.

(2)If an engine failure occurs during the climb to the rotation point, compliance with CAT.POL.H.310(b) will enable a safe landing or a safe forced landing on the deck.

(3)If an engine failure occurs between the rotation point and the DPATO, compliance with CAT.POL.H.310(b) will enable a safe forced landing on the surface, clearing the deck edge.

(4)At or after the DPATO, the OEI flight path should clear all obstacles by the margins specified in CAT.POL.H.315.

Figure 1 Typical take-off profile PC2 from a helideck/elevated FATO, non-hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(d)Take-off — non-hostile environment (with exposure time) CAT.POL.H.310(c)

(1)Figure 2 shows a typical take-off profile for performance class 2 operations from a helideck or an elevated FATO in a non-hostile environment (with exposure time).

(2)If an engine failure occurs after the exposure time and before DPATO, compliance with CAT.POL.H.310(c) will enable a safe forced landing on the surface.

(3)At or after the DPATO, the OEI flight path should clear all obstacles by the margins specified in CAT.POL.H.315.

Figure 2 Typical take-off profile PC2 from a helideck/elevated FATO with exposure time, non-hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(e)Take-off — non-congested hostile environment (with exposure time) CAT.POL.H.310(c)

(1)Figure 3 shows a typical take off profile for performance class 2 operations from a helideck or an elevated FATO in a non-congested hostile environment (with exposure time).

(2)If an engine failure occurs after the exposure time, the helicopter is capable of a safe forced landing or safe continuation of the flight.

(3)At or after the DPATO, the OEI flight path should clear all obstacles by the margins specified in CAT.POL.H.315.

Figure 3 Typical take-off profile PC2 from a helideck/elevated FATO, non-congested hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(f)Landing — non-hostile environment (without an approval to operate with an exposure time) CAT.POL.H.325(b)

(1)Figure 4 shows a typical landing profile for performance class 2 operations to a helideck or an elevated FATO in a non-hostile environment.

(2)The DPBL is defined as a ‘window’ in terms of airspeed, rate of descent, and height above the landing surface. If an engine failure occurs before the DPBL, the pilot may elect to land or to execute a balked landing.

(3)In the event of an engine failure being recognised after the DPBL and before the committal point, compliance with CAT.POL.H.325(b) will enable a safe forced landing on the surface.

(4)In the event of an engine failure at or after the committal point, compliance with CAT.POL.H.325(b) will enable a safe forced landing on the deck.

Figure 4 Typical landing profile PC2 to a helideck/elevated FATO, non-hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(g)Landing — non-hostile environment (with exposure time) CAT.POL.H.325(c)

(1)Figure 5 shows a typical landing profile for performance class 2 operations to a helideck or an elevated FATO in a non-hostile environment (with exposure time).

(2)The DPBL is defined as a ‘window’ in terms of airspeed, rate of descent, and height above the landing surface. If an engine failure occurs before the DPBL, the pilot may elect to land or to execute a balked landing.

(3)In the event of an engine failure being recognised before the exposure time, compliance with CAT.POL.H.325(c) will enable a safe forced landing on the surface.

(4)In the event of an engine failure after the exposure time, compliance with CAT.POL.H.325(c) will enable a safe forced landing on the deck.

Figure 5 Typical landing profile PC2 to a helideck/elevated FATO with exposure time, non-hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(h)Landing — non-congested hostile environment (with exposure time) CAT.POL.H.325(c)

(1)Figure 6 shows a typical landing profile for performance class 2 operations to a helideck or an elevated FATO in a non-congested hostile environment (with exposure time).

(2)In the event of an engine failure at any point during the approach and landing phase up to the start of exposure time, compliance with CAT.POL.H.325(b) will enable the helicopter, after clearing all obstacles under the flight path, to continue the flight.

(3)In the event of an engine failure after the exposure time (i.e. at or after the committal point), a safe forced landing should be possible on the deck.

Figure 6 Typical landing profile PC2 to a helideck/elevated FATO with exposure time, non-congested hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

GM · GM1 CAT.POL.H.310 — Regulation (EU) No 965/2012 · ED Decision 2014/015/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

AMCAcceptable means of compliance

AMC1 CAT.POL.H.310(c)(2)and CAT.POL.H.325(c)(2) Take-off and landing

Show the text

FACTORS

(a)To ensure that the necessary factors are taken into account, the operator should:

(1)use take-off and landing procedures that are appropriate to the circumstances, and that minimise the risks of collision with obstacles at the individual offshore location under the prevailing conditions; and

(2)use the aircraft flight manual (AFM) performance data or, where such data is not available, alternative data approved by the competent authority, which show take-off and landing masses that take into account drop-down and take-off deck-edge miss, under varying conditions of pressure altitude, temperature, and wind.

(b)Replanning of offshore location take-off or landing masses during the flight should only be performed in accordance with procedures established in the operations manual (OM). These procedures should be simple and safe to carry out, with no significant increase in the crew workload during critical phases of the flight.

AMC · AMC1 CAT.POL.H.310(c)(2) — Regulation (EU) No 965/2012 · ED Decision 2016/022/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

GMGuidance material

GM1 CAT.POL.H.310& CAT.POL.H.325 Take-off and landing

Show the text

TAKE-OFF AND LANDING TECHNIQUES

(a)This GM describes three types of operation to/from helidecks and elevated FATOs by helicopters operating in performance class 2.

(b)In two cases of take-off and landing, exposure time is used. During the exposure time (which is only approved for use when complying with CAT.POL.H.305), the probability of an engine failure is regarded as extremely remote. If an engine failure occurs during the exposure time, a safe forced landing may not be possible.

(c)Take-off — non-hostile environment (without an approval to operate with an exposure time) CAT.POL.H.310(b).

(1)Figure 1 shows a typical take-off profile for performance class 2 operations from a helideck or an elevated FATO in a non-hostile environment.

(2)If an engine failure occurs during the climb to the rotation point, compliance with CAT.POL.H.310(b) will enable a safe landing or a safe forced landing on the deck.

(3)If an engine failure occurs between the rotation point and the DPATO, compliance with CAT.POL.H.310(b) will enable a safe forced landing on the surface, clearing the deck edge.

(4)At or after the DPATO, the OEI flight path should clear all obstacles by the margins specified in CAT.POL.H.315.

Figure 1 Typical take-off profile PC2 from a helideck/elevated FATO, non-hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(d)Take-off — non-hostile environment (with exposure time) CAT.POL.H.310(c)

(1)Figure 2 shows a typical take-off profile for performance class 2 operations from a helideck or an elevated FATO in a non-hostile environment (with exposure time).

(2)If an engine failure occurs after the exposure time and before DPATO, compliance with CAT.POL.H.310(c) will enable a safe forced landing on the surface.

(3)At or after the DPATO, the OEI flight path should clear all obstacles by the margins specified in CAT.POL.H.315.

Figure 2 Typical take-off profile PC2 from a helideck/elevated FATO with exposure time, non-hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(e)Take-off — non-congested hostile environment (with exposure time) CAT.POL.H.310(c)

(1)Figure 3 shows a typical take off profile for performance class 2 operations from a helideck or an elevated FATO in a non-congested hostile environment (with exposure time).

(2)If an engine failure occurs after the exposure time, the helicopter is capable of a safe forced landing or safe continuation of the flight.

(3)At or after the DPATO, the OEI flight path should clear all obstacles by the margins specified in CAT.POL.H.315.

Figure 3 Typical take-off profile PC2 from a helideck/elevated FATO, non-congested hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(f)Landing — non-hostile environment (without an approval to operate with an exposure time) CAT.POL.H.325(b)

(1)Figure 4 shows a typical landing profile for performance class 2 operations to a helideck or an elevated FATO in a non-hostile environment.

(2)The DPBL is defined as a ‘window’ in terms of airspeed, rate of descent, and height above the landing surface. If an engine failure occurs before the DPBL, the pilot may elect to land or to execute a balked landing.

(3)In the event of an engine failure being recognised after the DPBL and before the committal point, compliance with CAT.POL.H.325(b) will enable a safe forced landing on the surface.

(4)In the event of an engine failure at or after the committal point, compliance with CAT.POL.H.325(b) will enable a safe forced landing on the deck.

Figure 4 Typical landing profile PC2 to a helideck/elevated FATO, non-hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(g)Landing — non-hostile environment (with exposure time) CAT.POL.H.325(c)

(1)Figure 5 shows a typical landing profile for performance class 2 operations to a helideck or an elevated FATO in a non-hostile environment (with exposure time).

(2)The DPBL is defined as a ‘window’ in terms of airspeed, rate of descent, and height above the landing surface. If an engine failure occurs before the DPBL, the pilot may elect to land or to execute a balked landing.

(3)In the event of an engine failure being recognised before the exposure time, compliance with CAT.POL.H.325(c) will enable a safe forced landing on the surface.

(4)In the event of an engine failure after the exposure time, compliance with CAT.POL.H.325(c) will enable a safe forced landing on the deck.

Figure 5 Typical landing profile PC2 to a helideck/elevated FATO with exposure time, non-hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

(h)Landing — non-congested hostile environment (with exposure time) CAT.POL.H.325(c)

(1)Figure 6 shows a typical landing profile for performance class 2 operations to a helideck or an elevated FATO in a non-congested hostile environment (with exposure time).

(2)In the event of an engine failure at any point during the approach and landing phase up to the start of exposure time, compliance with CAT.POL.H.325(b) will enable the helicopter, after clearing all obstacles under the flight path, to continue the flight.

(3)In the event of an engine failure after the exposure time (i.e. at or after the committal point), a safe forced landing should be possible on the deck.

Figure 6 Typical landing profile PC2 to a helideck/elevated FATO with exposure time, non-congested hostile environment [Figure or form omitted from this preview — available in the Avioverse workspace library.]

GM · GM1 CAT.POL.H.310 — Regulation (EU) No 965/2012 · ED Decision 2014/015/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

All rules in SUBPART C: AIRCRAFT PERFORMANCE AND OPERATING LIMITATIONS

Consolidated from the EASA Easy Access Rules (revision 27 Mar 2026, extracted 17 Aug 2026) for convenience. Not the official publication — verify against the Official Journal of the European Union and the EASA publications before operational use.

Ask Metis about CAT.POL.H.310 →

Metis opens with Avioverse in October 2026 · request early access.