{"id":942,"date":"2026-10-08T11:34:21","date_gmt":"2026-10-08T11:34:21","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/mscio-logs-shots-at-cul-klang-north-of-bab-el-mandeb\/"},"modified":"2026-10-08T11:34:21","modified_gmt":"2026-10-08T11:34:21","slug":"mscio-logs-shots-at-cul-klang-north-of-bab-el-mandeb","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/mscio-logs-shots-at-cul-klang-north-of-bab-el-mandeb\/","title":{"rendered":"MSCIO logs shots at CUL Klang north of Bab el-Mandeb"},"content":{"rendered":"

The EU-sponsored Maritime Security Centre Indian Ocean received reports of a small boat harassing a passing containership in the southern Red Sea, north of the Bab el-Mandeb, early on Wednesday, 7 October. The vessel said shots had been fired by a small craft. The small craft subsequently moved away. The containership continued its northbound passage. The crew was uninjured. The Maritime Executive, carried by World Ports on Thursday, 8 October, treated that MSCIO line as the working centre report. It did not name the hull.<\/p>\n

Maritime security consultancy Marisks, summarised by Kuehne+Nagel\u2019s myKN desk and by Lloyd\u2019s List on Wednesday, identified the ship as the Singapore-flag containership CUL Klang, IMO 9958535, operated by China\u2019s CU Lines. Marisks timed the incident at about 0615 UTC, around 15 nautical miles southwest of Mocha, and said multiple shots were fired towards the vessel\u2019s bridge before the attackers broke off. No injuries were reported. All crew were safe. That is the working named-hull matching. MSCIO did not print the IMO. UKMTO did not issue a numbered Warning or Advisory on the English primaries used. Do not upgrade a consultant naming into a UKMTO product, and do not treat an unclaimed small-craft firing as a confirmed Houthi hit.<\/p>\n

What the centres published, and what they did not<\/h2>\n

MSCIO\u2019s account is short: small boat, harassment, shots fired, southern Red Sea north of the Bab el-Mandeb, craft moved away, northbound passage continued, crew uninjured. The Maritime Executive said the details were unclear and that there were no claims of responsibility. That combination is a bridge-watch and citadel problem before it is an attribution exercise. A master who has taken small-arms fire at the bridge has to keep way on, keep the lookout, log the contact, and decide whether to alter, increase speed or call for an escort while the boat is still in the picture. MSCIO did not say the ship was hit. It did not report damage, a casualty, a pollution line or a request for assistance.<\/p>\n

Marisks supplies the geometry and the hull. About 0615 UTC on Wednesday, northbound, around 15 nautical miles southwest of Mocha, multiple shots towards the bridge, attackers broke off. Mocha sits on Yemen\u2019s Red Sea coast north of the Bab el-Mandeb. Fifteen nautical miles southwest of that port is still on the northbound coastal track through the southern Red Sea, not a Gulf of Aden file and not a 60-nautical-mile-south-of-Mokha tanker product. Stay with shots from a small craft. Do not invent a missile, a UAV or a waterborne improvised explosive device to fill the gap.<\/p>\n

Open particulars matching IMO 9958535: Singapore-flag, MMSI 563219200, call sign 9V8953, 2024 container ship, about 189 by 32 metres, about 26,749 gt \/ 35,281 dwt. The Maritime Executive used about 35,300 dwt and a container capacity of 2,433 teu; Kuehne+Nagel rounded the box count to 2,400 teu. Registered owner matching is SPDBFL Two Hundred & Eighteen; commercial manager CU Lines Ltd; ISM manager CUL Ship Management Pte Ltd; class Lloyd\u2019s Register. The ship had departed Port Klang, Malaysia, on 27 September. Voyage colour on open AIS services put Jeddah as a subsequent destination. Use that as a northbound Red Sea track, not as a cargo manifest. The AIS destination field was displaying \u201cChina owned&CHN crew.\u201d That is a self-broadcast, not a flag finding and not a UKMTO naming.<\/p>\n

Do not invent a crew count, a nationality list or a damage survey. CU Lines had not published a named casualty statement on the English primaries used. Stay with MSCIO\u2019s uninjured line and Marisks\u2019 all-crew-safe line.<\/p>\n

A Red Sea small-craft file, not a Mokha tanker reprint<\/h2>\n

Keep Wednesday off the dedicated 5 October 03:30 Warning 151-26 desk. That product was a CSO-sourced Attack warning on an unnamed tanker that sighted multiple explosions in close proximity about 60 nautical miles south of Mokha, crew safe, no environmental impact at warning time, UKMTO investigating. Wednesday\u2019s hull is a named Singapore-flag feeder, shots from a small craft, 15 nautical miles southwest of Mocha, north of the strait, continuing northbound. Do not collapse the two. The Maritime Executive\u2019s own recap of 151-26 is context for the corridor, not a finding that CUL Klang is the 4 October tanker.<\/p>\n

The last Red Sea kinetic file on this desk that was not a Gulf of Aden product remains the late-August tanker strike off Yanbu, already treated as shore-and-harbour context in earlier INTERTANKO recaps. Do not rewrite Yanbu as Wednesday\u2019s containership. September\u2019s Gulf of Aden skiff and citadel files, Honour 25 \/ Eureka \/ Sibu 1, and the still-held Asana, remain Indian Ocean piracy and hostage products. They are not a Mocha small-craft firing.<\/p>\n

Attribution is not settled. Kuehne+Nagel noted that an armed small craft off Yemen\u2019s western coast is consistent with tactics previously used by Houthi forces, and that attribution has not been independently confirmed. The Maritime Executive recorded a contrary operational colour: the Houthis have said they would only target ships linked to Saudi Arabia, which raises doubt they would fire on a Chinese-operated container vessel, and some small boats in the area have previously been fishing craft protecting nets. Hold both remarks as colour. No claim of responsibility was on the English primaries used. Do not brief CUL Klang as a confirmed Houthi attack, a fishing-net dispute, or a Saudi-linked tanker.<\/p>\n

Land fighting is colour, not a transit-rule instrument<\/h2>\n

Wednesday\u2019s firing sits inside a land war, not inside a new coastal-state circular. The Maritime Executive reported intensified fighting along the Yemeni coast as Saudi and government-aligned forces clashed with the Houthis. Yemen\u2019s Homeland Shield Forces announced a large-scale offensive around al-Waziya in the Taiz highlands. There was fighting south of Mocha and around Dhubab, near the Bab el-Mandeb. Saudi-backed forces had claimed on Tuesday to have retaken Mocha and key parts of the coastline and to control the strait; by Wednesday both sides were claiming the same ground. That is a contested-coast picture. It is not a UKMTO or JMIC transit-rule change, and it is not a reason to rewrite the unused Saudi-backed Bab el-Mandeb control claim as a completed clearance.<\/p>\n

Hours before the CUL Klang report, Houthi forces launched ballistic missiles and drones toward Aden. Kuehne+Nagel said the group claimed a Saudi military facility; Yemeni authorities said one missile struck the runway at Aden International Airport and forced a Cairo-bound commercial flight to divert. The Maritime Executive separately recorded confirmed strikes at or near the airports in Abha and Riyadh, with Associated Press reporting three people killed and at least 30 injured at those two airports. Those are land and aviation files. Use them only as the reason the southern Red Sea was not a quiet coastal transit on Wednesday morning. Do not treat an airport strike as a named-hull maritime attack.<\/p>\n

Marisks, via Kuehne+Nagel, called the combination of the CUL Klang firing and the Aden strikes a \u201cmaterial deterioration\u201d in the southern Red Sea security environment. That is a consultancy assessment. It is not a JMIC numbered update and not a new listed-area circular. Lloyd\u2019s List Intelligence counted at least 1,214 transits by cargo-carrying vessels above 10,000 gt through the Bab el-Mandeb in September, up 17 percent year on year. Container lines have kept planning returns. Diversions have been concentrated on Saudi-affiliated tankers. Hold that as traffic colour. Do not brief a 2,400 teu feeder taking small-arms fire as a Bab el-Mandeb closure, and do not fold it into the dedicated 4 October Premier Alliance FE1 Suez return. ONE Continuity\u2019s November canal crossing remains a liner pro forma. Wednesday\u2019s file is a named hull, shots at the bridge, crew uninjured, still northbound.<\/p>\n

Operational implications<\/h2>\n

A small-craft firing at the bridge on a northbound feeder is a different night order from an unnamed tanker watching explosions 60 nautical miles south of Mokha. Masters already in the Mocha\u2013Bab el-Mandeb corridor need a written small-boat watch on the Red Sea leg, not only a missile watch in the Gulf of Aden. Bridge wings, lookouts, searchlights, citadel, AIS hygiene and a prepared UKMTO\/MSCIO\/MDAT report are the standing orders. The ship continued. That is a snapshot, not a finding that the next boat will break off.<\/p>\n

The AIS text \u201cChina owned&CHN crew\u201d is now part of the voyage picture whether or not it deterred the boat. Other operators who have been broadcasting similar ownership-and-crew messages as a deconfliction tactic should treat Wednesday as evidence that the message is not a shield. It is also not a substitute for BMP, a security team decision, or an Aspides escort request. EUNAVFOR Aspides had posted that it \u201csupports the confidence of the shipping industry in continuing to use challenged maritime routes\u201d and continues to escort vessels. That is an existing mission line, not a report that CUL Klang was under escort, and not a rewrite of the 28 September Kallas no-new-hulls file.<\/p>\n

Managers who recognise IMO 9958535 as theirs should assume flag, class, P&I and the Singapore MPA will ask for the master\u2019s report, the VDR, the last position, whether the bridge was hit, and whether the ship diverted. Charterers still stemming Jeddah, Sokhna, Aqaba or Mediterranean discharge on a Port Klang\u2013Red Sea rotation should treat Wednesday as a kinetic morning on a corridor that box operators have been treating as recoverable. Do not brief the combination of September\u2019s +17 percent Bab el-Mandeb count and an uninjured crew as a reason to drop BMP or to assume Mocha is a quiet coastal transit behind the strait.<\/p>\n

Do not fold Wednesday into Yanbu loadings, the UAE MPCI container-filing mandate, Japan\u2019s 35-ship vessel-level permit, or Iran\u2019s Persian Gulf Strait Authority declaration channel. Those are crude-export, documentation, sanctions and Gulf coastal-state products. Wednesday\u2019s file is a Singapore-flag feeder, small-craft shots at the bridge, 15 nautical miles southwest of Mocha, crew uninjured, still northbound.<\/p>\n

What Operators Should Note<\/h2>\n