Helicopter Operations and Helideck Safety
Helicopter operations require dedicated firefighting personnel during refuelling, safety devices on the helideck and rigorous coordination with the flight crew: an area often neglected in general crew training.
Operational Explanation
Onboard helicopter operations (personnel transfer, medical evacuation, refuelling) require a dedicated area (helicopter landing area/helideck) compliant with specific construction and operational standards, distinct from the ship's normal safety requirements. Although mandatory only for specific ship categories (a landing area on ro-ro passenger ships ≥130 m under SOLAS III/28.2, a pick-up area on all ro-ro passenger ships under SOLAS III/28.1), helicopter operability potentially concerns any ship in medical emergency or evacuation situations.
The helideck's manoeuvring area must have a diameter not less than the helicopter's overall length (rotors turning included), and its construction, if it forms the roof of a superstructure, must be insulated to A-60 class with access for firefighting and rescue personnel positioned, where possible, on opposite sides of the helideck.
Regulatory Reference
SOLAS Regulation III/28.1 requires a helicopter pick-up area on all ro-ro passenger ships, with no length threshold; SOLAS Regulation III/28.2 requires a helicopter landing area on ro-ro passenger ships of 130 m in length and upwards constructed on or after 1 July 1999. Until 31 December 2001 the paragraph read “Passenger ships” and therefore covered cruise ships too; resolution MSC.91(72) of 26 May 2000, in force from 1 January 2002, replaced those words with “Ro-ro passenger ships”. In the meantime MSC/Circ.907 of 17 June 1999 had already stated that non ro-ro passenger ships “need not be fitted with helicopter landing areas”. A non ro-ro cruise ship, today, is not under that obligation. The standard the Regulation points to (“recommendations adopted by the Organization”) is MSC/Circ.895 of 4 February 1999, as amended by MSC.1/Circ.1524 (2016); for on-board facilities the standard remains resolution A.855(20) of 27 November 1997, Standards for on-board helicopter facilities. Regulation II-2/18 governs the helideck's firefighting systems.
Chapter 17 of the FSS Code, Helicopter Facility Foam Firefighting Appliances, is not under development: it has been in force since 1 January 2020. It was adopted by resolution MSC.403(96) of 19 May 2016, and on the same date resolution MSC.404(96) created its Convention hook, inserting SOLAS Regulation II-2/18.2.3: “Notwithstanding the requirements of paragraph 2.2 above, ships constructed on or after 1 January 2020, having a helicopter landing area, shall be provided with foam firefighting appliances which comply with the relevant provisions of chapter 17 of the Fire Safety Systems Code”. The same resolution inserted Regulation II-2/18.5.1.6, which for ships with a helideck constructed on or after 1 January 2020 prescribes foam appliances “in lieu of the requirements of paragraphs 5.1.3 through 5.1.5” and points to the FSS Code without naming chapter 17: the two Regulations are not symmetrical and operate on different premises.
Two points that change how this applies in practice. First, the obligation bears on ships constructed on or after 1 January 2020; it is not a retrofit requirement on existing ships. Second, helicopter landing area and helideck are two distinct defined terms in SOLAS II-2/3, and the two Regulations do not overlap — establish which one applies to your unit before assuming either.
Scope of Application
Distinguish certified helidecks/helicopter facilities from areas used for occasional or emergency landing or winching. The latter follows the ship's procedure, operator coordination and A.855(20) §5 without automatically importing helideck construction standards.
Procedure / How to Complete It
- Identify whether the operation uses a certified facility or an occasional/emergency area.
- For every planned operation make at least two trained rescue/fire-fighting persons and the equipment immediately available.
- During refuelling those persons must be present and not take part in refuelling.
- Coordinate risks, communications and limits with operator and ship procedure.
Practical Example
Example: before an emergency medical transfer, the Master designates the dedicated firefighting personnel for the helideck, verifies wind conditions and the availability of the manoeuvring area by radio with the pilot, and conducts a quick briefing with the crew involved on roles and escape routes in case of an emergency during the operation.
What Typically Goes Wrong
Common Mistakes Mistake Library
| Mistake | Consequence | How to avoid it |
|---|---|---|
| Helicopter operation conducted without dedicated firefighting personnel present during refuelling | Critical response time lost in the event of ignition during refuelling | Always designate and position dedicated firefighting personnel before refuelling begins |
| Coordination with the flight crew limited to informal last-minute communications | Misunderstandings over signage, reference points or operational conditions | Always conduct structured radio coordination before approach |
| Non-essential personnel not kept clear of the manoeuvring area during operations | Risk of injury from the rotor or flying objects during landing/take-off | Rigorously delimit and enforce the safety zone during every operation |
What the PSCO Checks
Operational Tips
- Don't treat helicopter operations as a rare event to be improvised: keep a written, up-to-date procedure even if the occasion is infrequent.
- Always verify the availability of dedicated firefighting personnel before authorising refuelling, with no exceptions for perceived urgency.
- Consult the Guide to Helicopter/Ship Operations (ICS) for detailed procedures, if the ship does not have a sufficiently developed internal procedure.
Preparation checklist
- Area and operation type identified
- Two trained persons and equipment available
- Refuelling fire team separate from refuelling task
- Ship/operator procedure checked
FAQ
Related Topics
Last substantive revision of this page: 20 August 2026 · page fingerprint d36f0c1ad789