Professional Documents
Culture Documents
Lesson Learnt - Rev-New2022
Lesson Learnt - Rev-New2022
2
Lesson Learnt
The experience itself is the
best way to learn.
How many times do we have to
repeat the same mistake to
recognize it as a mistake and to
learn a lesson
Lesson Learnt Circulars
Injury During Dismantling of Piston
Crown – 10 Jan 2020
Preventive
actions?
Lesson Learnt Circulars
Burn injury due to hot water scalding –
1st Jan 2020.
Lesson Learnt Circulars
Burn injury due to hot water scalding – Jan 2020.
What contributed to this Accident?
Lesson Learnt Circulars
Serious injury during greasing of mooring winch
– 18 February 2020
Lesson Learnt Circulars
Serious injury during greasing of mooring winch –
18 February 2020
Lesson Learnt Circulars
Bosun Crushed
Index Finger
Fall Injury
Lesson Learnt….
Arm Injury Case
Trap Injury
Trap Injury
Preventive
actions?
Crew Injury during tank cleaning operation
Lesson Learnt with Hoses
SAFETY ALERT 001/2021
05 Jan 2021
Left Arm Injury due to Slipped Down
Three Point Contact principle in ladders:
32
Job Safety Analysis Risk Assessment
JSA RA
Identify specific dangers A systematic process of
related to specific tasks in evaluating a potential risk
the workplace. that may be involved in a
projected activity or
undertaking.
33
Lesson Learnt….
34
Collision with outbound Vessel
near approach Channel
MT ESTEEM HOUSTON while approaching buoyed
channel towards Breakwater at Callao, Peru collided with
the outbound vessel OCEAN PHOENIX TREE in location
12-02.52 S / 077-11.23 W. The incident occurred on 11
Dec 2021 at 1835 LT with Pilot on board. Other vessel was
bulk carrier exiting breakwater. Vessel sustained damages
at the port side quarter hull area iwo frame 23, between
longitudinal 38 and 39 with in E/Room.
No pollution due to the collision. No crew injury due to the
incident.
ECDIS and RADAR Screenshots
36
Collision with outbound Vessel
near approach Channel
The consequences
Hull rupture iwo Frame 23 between longitudinals 38 and 39.
As per preliminary inspection it was found the Shell plate with a
rupture behind the ECR on 2nd Deck, the opening is appx. 70cm
long & Height 130 cm In way of Longitudinal 38 & 39 - Frame 23.
Delays in discharging of Cargo destined for this Port.
Collision with outbound Vessel
near approach Channel
Causal factors, Immediate Causes, Direct Causes:
Immediate cause is attributed to communication between the
two Pilots and agreeing to pass Red to Red but outbound Vessel
Pilot disembarked with in the buoyed channel before the critical
maneuver was completed. Also Pilot on outbound vessel failed
to ensure that outbound vessel Master understood and will
follow the correct maneuver as agreed with Pilot of own Vessel.
Lack of proper watchkeeping and situational awareness of
outbound vessel and her failure to respond to all VHF warning
Calls and sound signals by own vessel and port control.
Possible miscommunication between Chinese Master and local
Pilot of outbound Vessel while communicating in English.
Collision with outbound Vessel
near approach Channel
Preventive/Corrective Actions:
Master to ensure to discuss with Pilot movement of any vessels
in and out of the Port when own vessel is likely to proceed.
As far as possible, Master to agree with Pilot to wait for any
outbound vessel to clear the channel before proceeding
inbound.
Master to ensure to check with the Pilot on intentions of
outbound vessel and agree on the maneuver before proceeding.
In case of any doubt, maneuver to be aborted till outbound
vessel is past and clear.
Lesson Learnt….
40
Incident 1
Loss of Port anchor and cable
Situation:
Type of Vessel: Bulk Carrier (DWT: 80,000)
Draft: Forward 4.74m, Aft 7.25m
Charted depth: About 53 meters
Weather: Gentle breeze, daytime.
Wind: Easterly – 8 to 9 knots.
Current: ESE about 1.5 knots, high tide
Visibility: Good visibility
Vessel under pilotage.
Tanjong Bara anchorage, Indonesia.
THE CONSEQUENCES
Stuck chain link between gypsy Damage to the Main shaft support
wheel and shaft cover stud
What went wrong/ the root causes
Excessive stress on the cable causing physical
damage to the hydraulic motor
Gear was engaged before easing off weight on cable
Cable was heaved up even when there was weight
and even when the windlass operator reported that
there was difficulty in heaving up anchor.
Vessel pivoted with high momentum (Yellow circle)
around the cable with gear engaged causing severe
stress on windlass motor.
Lessons learnt
Anchoring team forward:
Forward station should report cable direction, weight and
advise bridge to ease weight on the cable before engaging
gear.
Forward station should engage gear only when the weight
on anchor cable is eased off and is up and down.
Officer in charge of anchor station shall not ignore windlass
operator’s feedback
Bridge should be informed immediately regarding the
heavy load on windlass.
Officer in charge should cross checked engine and helm
movements with bridge.
Lessons learnt
On Bridge:
Conduct BTM to discuss anchor heaving procedure, familiarize
with contents of BDP and sections containing anchoring, anchor
watch and heaving up anchor with anchoring team and bridge
team before anchoring operation.
Bridge should verify and confirm cable direction, weight and ease
off weight on cable using engine before ordering forward to
engage gear.
Bridge should order forward station to engage gear only once
anchor cable is up and down.
Bridge shall keep forward station closely updated with engine
and helm movements.
If after giving engine movement and helm for a prolonged
period, forward station does not report change in cable direction
or weight, always suspect and cross check.
Incident 3
Intentional Release of Anchor
Scenario / Vessel
Description Opponent
Own Vessel – Anchored @ Pajaritos Vessel
“C” Anchorage.
Drops Anchor at 9th Jan / 1018LT
Draft: 6.6m / 8.6m
Port Anchor 7 Shackles on Deck
Depth – 34m // UKC – 25m
Wind: NE x BF3
Sea: Low
Current: SE x 1.0 Kts
Distance from Other vsl: 2.3 nm Own
Vessel
Other Vessel
Chemical Tanker
Draft: 8.4 m
Damages due to backlash from the
anchor chain
57
Root Cause Analysis
RCA
Above the surface
you see the
SYMPTOMS
of the problem