Marine Guru, Mumbai (2026)

26/09/2026

25.09.2026: FIRE AT SEA : BLUE CARRIER 2 EVACUATED NORTH OF MYKONOS

A major maritime emergency unfolded north of after a fire broke out aboard the Ro/Ro vessel CARRIER 2 while underway from (Syros, Greece) to (Greek Island in Aegean Sea)

⏱️ 25/05:57 Z — FIRE REPORTED
The reportedly broke out in the vessel’s vehicle deck/garage while the ship was carrying:
🚛 166 trucks
🚗 29 cars
👨‍✈️ 28 crew members
👷 1 truck driver

The vessel’s onboard firefighting procedures were immediately activated, with the crew attempting to tackle the fire 🔥 using the ship’s own resources. However, the situation could not be brought under control even with the 🧯fixed FFE.

🛟 EVACUATION
With the fire rapidly progressing, all 29 persons on board the vessel and into the lifeboats. Nearby vessels subsequently recovered them & transported them safely towards .

✅ All 29 people were reported safe & in good health.

🔥 A MASSIVE EMERGENCY RESPONSE
Greek authorities mobilised substantial firefighting, rescue & pollution-response resources, including:
• Hellenic Coast Guard vessels & patrol craft
• Firefighting boats Syros and Lavrio
• Firefighting resources from
• Multiple tugboats
• Nearby commercial vessels
• Fire Service helicopters
• Underwater Operations Unit personnel
• Anti-pollution vessels & equipment

🚢 The firefighting & salvage vessel PELAGOS was also dispatched from Piraeus to assist with firefighting and salvage operations.

📍 Reported position:
37°36′N 025°22′E

At the reported position, BLUE CARRIER 2 was emitting a large column of smoke, with flames reportedly spreading along a substantial portion of the vessel.

This incident once again highlights the importance of:
🔹 Early fire detection
🔹 Rapid mobilisation of fixed & portable firefighting systems
🔹 Effective crew emergency response
🔹 Clear evacuation procedures
🔹 Lifeboat readiness
🔹 Close coordination with shore-based emergency services
🔹 Timely deployment of firefighting tugs & salvage assets

Most importantly, 29 lives were brought to safety. The firefighting & salvage operation remains focused on containing the blaze & preventing further escalation.

Ship's particulars:
LOA : 162.49 meters
B: 25.64 meters
Type: RO/RO Cargo Ship
Garage Capacity: 2,066 LM
Nominal Capacity: 300 TEU
Service Speed: 17 knots
Cabins / Crew: 12 single-berth cabins and capacity for 12 drivers

Marineguru

26/09/2026

25.09.2026: RIVER COLLISION AT KINDERDIJK — Musketier Vs Bayern 2

A busy inland waterway junction in the Netherlands became the scene of a significant collision yesterday, 24 September 2026.

At approximately 15:30 LT, the tanker & inland cargo vessel 2 collided at the junction of the and rivers near .

⚠️ WHAT HAPPENED?
🔹 Bayern 2 was reportedly navigating from the Lek towards the Noord when it collided with the approaching Musketier.
🔹 The impact caused substantial damage to the side of Bayern 2.
🔹 Musketier sustained damage around her bow & side.
🔹 At the time of the collision, the tanker was reportedly carrying gasoline, while Bayern 2 was carrying animal feed.

🛟 RAPID EMERGENCY RESPONSE
Police, firefighters, ambulance crews & Rijkswaterstaat responded to the incident.

A police helicopter was also deployed to monitor the situation from the air.
✅ NIL injuries reported
✅ NIL pollution reported
✅ NIL hazardous-substance release reported

Following the , the vessels were moved away from the immediate area. The damaged Bayern 2 was assisted towards the IHC shipyard at Kinderdijk for further assessment, while Musketier continued towards the Lek side near Krimpen aan de Lek.

🔎 INVESTIGATION UNDERWAY
Authorities are now expected to examine the vessels’ tracks, manoeuvres, bridge-team actions, visibility, traffic situation & navigational decisions to establish how the collision occurred.

Busy river junctions demand early risk assessment, effective communication & continuous situational awareness — particularly where commercial traffic converges from different waterways.

⚓ One moment. Two vessels. A chain of navigational decisions.
The investigation will determine where that chain broke.

Marine Guru

26/09/2026

24.09.2026: 36-YEAR-OLD SEAFARER RESCUED AFTER SERIOUS ONBOARD FALL

A challenging maritime medical evacuation unfolded off Diglipur, Andaman & Nicobar Islands, on the night of 20 September 2026.

A 36-year-old Bangladeshi crew member aboard the Amris suffered severe head and spinal injuries after falling onboard.

With his condition requiring urgent medical attention, the Indian Coast Guard responded despite rough sea conditions.

🛟 THE RESCUE

⚓ Indian Coast Guard Ship Rajdoot was deployed to the scene.

🌊 Battling challenging sea conditions, the crew of Rajdoot successfully embarked the injured seafarer and transported him safely to Diglipur.

🚁 From there, the evacuation continued by air.

✈️ An Indian Navy aircraft airlifted the injured seafarer to Sri Vijaya Puram, where he was transferred to GB Pant Hospital for urgent medical treatment.

⚓ ONE INCIDENT — MULTIPLE TEAMS — ONE PRIORITY

From the shipboard emergency to the offshore rescue, sea transfer and subsequent air evacuation, the operation demonstrated the importance of rapid coordination between merchant vessels, the Indian Coast Guard, Indian Navy and shore-based medical facilities.

For an injured seafarer at sea, every minute matters.

👏 Respect to everyone involved in bringing him safely ashore and into medical care.

Seafarer safety doesn’t stop at the ship’s rail. It extends all the way to the hospital.

26/09/2026

24.09.2026: ONE SEAFARER KILLED WHEN CAPE DAO STRUCK IN THE STRAIT OF HORMUZ

23 September 2026 | 0630 UTC | Off Musandam, Oman

The Capesize bulk carrier CAPE DAO was struck while transiting the SOH, triggering a fire in the E/R & leaving the vessel adrift.

⚠️ WHAT HAPPENED?
🕡 ~0630 UTC — Cape Dao was struck by an unidentified projectile while transiting near Oman’s Musandam Peninsula.

🔥 The impact caused a fire in the E/R & the vessel was left without effective propulsion.

🛟 A Royal Navy of Oman vessel responded & evacuated 27 crew members, providing medical assistance.

🇮🇳 One Indian seafarer was killed. India’s Embassy in Muscat confirmed that 19 Indian nationals were among the crew.

The deceased seafarer has been identified as Suraj Yadav, Rank : Wiper from Uttar Pradesh.

🌊 ANOTHER DEADLY REMINDER
The Cape Dao incident follows attacks on other merchant vessels in the region.

🔴 LR Stephanie — struck by an unidentified projectile; two seafarers injured.

🔴 Al Maryah — LPG carrier damaged by debris from unidentified projectiles.

Responsibility for the Cape Dao attack has not been established.

📊 THE NUMBERS ARE MOUNTING

The IMO reported 80 verified attacks on merchant shipping in & around the Strait of Hormuz since the conflict began on 28 February 2026, with about 22 seafarers killed as of 16 September. The IMO’s incident tracker subsequently listed 84 confirmed incidents and 23 seafarer fatalities as of 23 September.

Marineguru

25/09/2026

🚨⚓ FLAG STATE vs PORT STATE — WHO REALLY CONTROLS THE SHIP?

OOW, Master or Engineer—you can have valid certificates onboard and still face detention at the next port.

🏴 FLAG STATE — THE PRIMARY JURISDICTION

→ Ship is registered under its flag
→ Flag State ensures statutory compliance
→ Certificates and surveys operate under its authority
→ ISM, SOLAS, MARPOL and STCW enforcement continues

⚓ PORT STATE — THE SECOND LINE OF CONTROL

→ Foreign ships can be inspected in port
→ PSCO checks actual condition, not paperwork alone
→ Clear grounds can trigger expanded inspection
→ Serious deficiencies can prevent departure

🔧 REAL PSC SCENARIO

→ 180,000 DWT bulk carrier arrives in Australia
→ Emergency fire pump fails during testing
→ Valid certificates do not make the defect disappear
→ Vessel can be detained until deficiency is rectified

📋 THE OFFICER’S LESSON

→ Flag approval is not immunity from PSC
→ Keep equipment operational, certificates current
→ Crew must demonstrate actual competence
→ PSC sees the ship you actually operate

💥 Flag State sets continuing responsibility; Port State can enforce locally.

🧑‍✈️ OOWs: What PSC deficiency have you personally seen cause detention—and why?

25/09/2026

🚢⚓ YOUR FIRST SHIPPING COMPANY — LOOK BEYOND THE SALARY

Cadet or newly joined 3/O? That first contract can shape your next CoC, vessel type, and promotion path.

💰 OFFER A — THE HIGHER PAY

→ $3,200/month on a 2,400 GT feeder
→ Near-coastal trading
→ Limited exposure to larger vessels
→ Higher salary looks attractive initially

🌊 OFFER B — THE LOWER PAY

→ $2,400/month on a large ocean-going tanker
→ Structured onboard training
→ More relevant vessel experience
→ Potential tanker-specialization pathway

📋 BEFORE SIGNING, CHECK

→ Is the crewing agency properly licensed?
→ Who verifies your sea service?
→ What vessels will you actually sail?
→ Is your TRB properly supported onboard?
→ How does promotion work after contract?

⚠️ NEVER PAY FOR A BERTH

→ Recruitment and placement fees are prohibited under MLC
→ Verify the agency before handing over documents
→ Ask exactly how your sea service is recorded

💥 Your first company is not just your first salary—it builds your sea-time story.

🧑‍✈️ JUNIOR OFFICERS: Higher salary or better vessel exposure—what would you choose, and why?

25/09/2026

🚨⚓ SEWOL — 4 STABILITY MYTHS THAT CAN KILL

Ask any Chief Officer: a vessel can be within her marks and still be dangerously unstable.

⚖️ MYTH 1: “LOAD LINE = SAFE TO SAIL”

→ Freeboard does not guarantee adequate intact stability
→ KG, GM and loading distribution still matter
→ Draft marks cannot replace stability calculations

🛢️ MYTH 2: “BALLAST IS JUST FOR TRIM”

→ Ballast can keep KG lower
→ Deballasting can seriously reduce stability margin
→ Cargo weight and vertical position must be assessed together

📦 MYTH 3: “LASHINGS ONLY MATTER IN HEAVY WEATHER”

→ Cargo shift creates a dangerous heeling moment
→ Shifted cargo can further reduce effective stability
→ Ro-Ro cargo securing is a critical safety barrier

📐 SEWOL — THE SCALE OF THE PROBLEM

→ Approved cargo capacity: about 987 tonnes
→ Reported cargo carried: over 2,000 tonnes
→ Ballast condition was also critically reduced
→ Alterations had increased the vessel’s stability challenges

💥 The casualty shows how loading decisions can become a capsize chain: poor stability → heel → cargo shift → flooding.

🧑‍✈️ CHIEF OFFICERS: Would you reject excess cargo—or refuse departure? Why?

25/09/2026

🚨⚓ EXXON VALDEZ — THE GROUNDING THAT CHANGED OIL SHIPPING

Every OOW knows the danger: miss one alteration in confined waters, and the ship keeps going.

🧭 WHAT HAPPENED?

→ 24 March 1989, Bligh Reef, Alaska
→ Third Mate was OOW during grounding
→ Master was not on the bridge
→ 11 of 18 cargo tanks were ruptured
→ About 11 million gallons of crude spilled

⚠️ THE BRIDGE LESSON

→ Position monitoring failed when it mattered
→ Passage-plan cross-checking broke down
→ Distraction delayed the required alteration
→ Fatigue and watchkeeping became critical factors
→ Modern BRM demands active cross-checking

🛢️ WHY TANKERS CHANGED

→ Exxon Valdez accelerated pressure for double hulls
→ OPA 90 drove major US tanker requirements
→ MARPOL later established global double-hull requirements
→ Double hulls reduce spill risk after certain casualties
→ But double hulls cannot prevent every major spill

📐 OFFICER EXAMPLE

→ Modern Suezmax: 150,000 DWT
→ Narrow passage: autopilot requires careful control
→ One missed alteration can erase miles of clearance
→ ECDIS, radar and visual fixes must agree

💥 The reef was physical. The failure chain started on the bridge.

🧑‍✈️ OOWs: Would you call the Master early—or try correcting alone? Why?

25/09/2026

🚨⚓ CARGO CLAIMS — 4 MYTHS THAT COST MONEY

Chief Officer, cargo damage is rarely “just bad luck.” The claim often starts with something missed before sailing.

📦 MYTH 1: “HEAVY WEATHER CAUSED IT”

→ Weather alone doesn’t automatically remove liability
→ Hatch condition and seaworthiness still matter
→ Preserve inspection and maintenance evidence
→ Record significant weather and cargo events

🌊 MYTH 2: “ANY WET CARGO MEANS HATCH LEAK”

→ Identify seawater versus condensation first
→ Check hatch packing and drainage channels
→ Review ventilation records and cargo temperatures
→ Preserve samples and survey evidence

🧾 MYTH 3: “CLEAN B/L MEANS NO PROBLEM”

→ Never ignore visible cargo defects
→ Record appropriate reservations when justified
→ LOIs don’t magically remove cargo risks
→ Follow company and P&I instructions

📐 REAL SHIP SCENARIO

→ 57,000 DWT Supramax
→ 50,000 MT grain cargo
→ Water staining found under Hold 2
→ Hatch records become critical evidence

💥 One missing inspection record can become a very expensive conversation.

🧑‍✈️ CHIEF OFFICERS: Which claim have you actually faced—water ingress, shortage, contamination, or cargo sweat? What caused it?

25/09/2026

🚨⚓ CARGO HOLD VENTILATION — VENTILATE OR KEEP CLOSED?

Chief Mate on a bulk carrier checks the hygrometer. Cargo is cold, destination is tropical. Someone says, “Open the vents—fresh air will dry it.” Would you?

🌡️ CASE STUDY: THE CARGO

→ Steel coils loaded at 5°C
→ Outside air: 30°C
→ Outside RH: 85%
→ Outside dew point: approximately 27°C
→ Cargo is far colder than incoming air

💧 WHAT HAPPENS IF YOU VENTILATE?

→ Warm humid air enters the cold hold
→ Moisture can condense on colder cargo
→ Cargo sweat can promote corrosion
→ “Fresh air” does not automatically mean dry air

🧭 CHIEF OFFICER’S CHECK

→ Compare ambient dew point with cargo temperature
→ Follow the cargo-specific ventilation guidance
→ Record temperature and ventilation decisions
→ IMSBC requirements can override sweat prevention

⚠️ TWO SWEATS — DON’T MIX THEM

→ Cargo sweat forms directly on cargo
→ Ship sweat forms on cold steel
→ Voyage conditions determine the condensation risk

💥 One wrong ventilation decision can become a cargo claim.

🧑‍✈️ CHIEF OFFICERS: Would you ventilate this 5°C steel cargo? Give your decision—and the dew-point reasoning behind it.

Marine Guru

26/09/2026

26/09/2026

26/09/2026

26/09/2026

25/09/2026

25/09/2026

25/09/2026

25/09/2026

25/09/2026

25/09/2026

Address

Website

Alerts

Contact The School

Shortcuts

Share

Category

Listing takedown request