Helideck InfoShare

Poor communication with HLO on vessel

Reference 2022-009 Priority Routine

Event Date 12 Dec 2021 Event Time 01:35

Region Europe Event Category Communication

Aircraft Model S-92A

Type of Facility -

Manned Facility -

Design Standard

Dimensions (mxm) Size (D-val in m)

Height a.s.l. (ft) Max Mass (t)

Surface Mat. - Landing Net?

Limitations

Pitch/Roll/Heave Last Inspected

Wind Dir. (deg) Wind Speed (kts)

Pressure (hPa) Temperature (C)

Cloud Base (ft) Visibility (SM)

Light Conditions - Sea State (WMO) -

Synopsis

Helicopter was scrambled to a patient located onboard a vessel positioned only a few minutes flight time away.
The vessel has a helipad on the front, and after getting readouts for the vessel’s movement the pilots decided
to land.

From the helipad to the vessel’s "sky lobby" there is a flight of stairs down. The patient was brought up to the
sky lobby, and a crew member began to brief the personnel who would help carry the patient to the helicopter.
At that time, the SAR nurse decided to go on to the helicopter and wait for the patient there.

Meanwhile the movement of the vessel had increased, and the pilots notified the Helicopter Landing Officer
(HLO) that no one should come near the helicopter as they were using the flight controls to keep the helicopter
steady. The same message was relayed to the rescue swimmer on Polycom. At the same time, the SAR nurse
were almost at the top of the stairs on her way to the helicopter, and the vessel’s HLO was not in place to stop
the SAR nurse.

Cause

The vessel’s HLO was not in place to stop the SAR nurse, and it is not certain whether the message was
copied by the HLO as his response on radio had been scrambled and unreadable.

HeliOffshore has been established to promote safety and the development of best practices. InfoShare reports are intended for
the development of safety standards, lessons learned and the collection of industry statistical data.
This document may only be shared in accordance with the HeliOffshore InfoShare code of conduct and may not
be distributed outside of the HeliOffshore community.
Page 1 of 2
The rescue swimmer instantly ran up the stairs, caught up with and managed to stop the SAR nurse just as
she entered the helipad.

Actions taken

The helideck operator was reminded to ensure the helideck is staffed in accordance with local procedures.

The helideck operator was requested to ensure they have fully functioning communication equipment, so they
can communicate with the helicopter even when it has landed on the helipad.

The Helicopter operator issued a “Lessons Learned” notification to all installations and vessels in their area of
operation.

HeliOffshore has been established to promote safety and the development of best practices. InfoShare reports are intended for
the development of safety standards, lessons learned and the collection of industry statistical data.
This document may only be shared in accordance with the HeliOffshore InfoShare code of conduct and may not
be distributed outside of the HeliOffshore community.
Page 2 of 2