Connect with us

Incident

MPA: Singapore-registered ship in Baltimore bridge crash passed previous foreign port state inspections

MPA confirmed vessel’s required classification society and statutory certificates covering structural integrity of vessel and functionality of vessel’s equipment were valid at time of the incident.

Admin

Published

on

MPA: Singapore-registered ship in Baltimore bridge crash passed previous foreign port state inspections

The Singapore-registered container vessel Dali that crashed into the Francis Scott Key bridge in Baltimore, Maryland, USA, underwent and passed previous foreign port state inspections, the Maritime and Port Authority of Singapore confirmed on Wednesday (27 March). 

The vessel struck the Francis Scott Key bridge in Baltimore, Maryland, USA, on 26 March at about 1.30pm (Singapore Time), causing the bridge to collapse. 

MPA said Dali was flagged with Singapore from October 2016 and is classed by classification society ClassNK. 

Classification societies are generally authorised by a flag administration to monitor compliance to technical standards and the applicable regulations by vessels registered under its flag.

Based on records, MPA confirmed that the vessel’s required classification society and statutory certificates covering the structural integrity of the vessel and functionality of the vessel’s equipment, were valid at the time of the incident.

“The vessel also underwent and passed two separate foreign port state inspections in June and September 2023,” MPA said in its latest statement on the incident.

“In the June 2023 inspection, a faulty monitor gauge for fuel pressure was rectified before the vessel departed the port.”

Dali‘s next classification and statutory surveys are due in June 2024.

MPA: Singapore-registered ship in Baltimore bridge crash passed previous foreign port state inspections

Part of the collapsed bridge on top of “Dali”

In another statement, MPA said Dali is a 95,000 GT container vessel operating with 22 crew onboard at the time of the incident.

MPA said it was in contact with the US Coast Guard and the ship management company to provide the necessary assistance.

“As the flag state, MPA will provide full cooperation to the US Coast Guard in its investigations. MPA will also be investigating the incident,” it said in a statement. 

MPA also confirmed that it has contacted the United States Coast Guard (USGC) Headquarters and the Office of Marine Safety, National Transportation Safety Board, and offered MPA’s assistance as the flag administration to support the investigations.

“Investigators from the Transport Safety Investigation Bureau and MPA are making their way to Baltimore, Maryland,” it added. 

“The ship management company, Synergy Marine Pte Ltd, reported to MPA that just prior to the incident, the vessel had experienced momentary loss of propulsion. As a result, she was unable to maintain the desired heading and collided with the Francis Scott Key bridge.”

The vessel was reported to have dropped its anchors as part of the vessel’s emergency procedures prior to its impact with the bridge. The vessel was under pilotage at the time of the incident.

The vessel is currently holding onto its position at the site of the collision and is in a stable condition. All 22 crew members are safe and accounted for.

MPA added search and rescue efforts led by US authorities are ongoing.

The US Coast Guard said there were reports of persons in the water following the collapse of the bridge. 

“Response boat crews from Coast Guard Stations Curtis Bay and Annapolis have crews deployed to the incident for active search and rescue,” it said in a statement. 

FBI Evidence Response Team members work at the site of the Francis Scott Key Bridge collapse in Baltimore on March 26

FBI Evidence Response Team members work at the site of the Francis Scott Key Bridge collapse in Baltimore on March 26

A Coast Guard Air Station Atlantic City MH-65 Dolphin helicopter crew, Coast Guard investigators and pollution responders also responded to the incident. 

Marty Durbin, senior vice president of policy at the U.S. Chamber of Commerce, issued the following statement in response to the collapse of the Francis Scott Key Bridge in Maryland.

“We are deeply saddened by the tragic collapse of the Francis Scott Key Bridge early this morning.”

“While search and rescue operations for the victims of this terrible incident are the priority, we are working closely with the Maryland State Chamber of Commerce, the Baltimore Chamber of Commerce, as well as other industry and government partners to assess its impact and provide assistance.”

“As a critical thoroughfare for Maryland and the East Coast, this bridge has kept people, businesses, and communities connected.”

“Unfortunately, its prolonged closure will likely disrupt commercial activities and supply chains that rely on the bridge and Port of Baltimore each day. We will support the many individuals, businesses, and communities affected by this incident and help to both identify and implement solutions during this challenging time.”

 

Photo credit: Baltimore County Fire Department / FBI Baltimore
Published: 27 March 2024

Continue Reading

Vessel Arrest

Malaysia: MMEA detains tanker for anchoring without permission near Port Klang

Tanker was anchored 5.9 nautical miles west of Pulau Pintu Gedong; Second Deck Officer and Second Engineer were taken to the Pulau Indah marine police jetty for further action.

Admin

Published

on

By

Malaysia: MMEA detains tanker for anchoring without permission near Port Klang

The Malaysian Maritime Enforcement Agency (MMEA) on Wednesday (23 April) said it detained a tanker for anchoring without permission at 5.9 nautical miles west of Pulau Pintu Gedong at about 3.15pm on 22 April. 

The ship was operated by a 36-year-old Thai captain with 16 crew members aged between 20 and 55 years, consisting of 13 Thais including two women, two Myanmar nationals and an Indonesian national.

The inspection found that the ship had committed an offence under the Merchant Shipping Ordinance 1952 by not obtaining permission from the Director-General of the Malaysian Maritime Department and for failing to fly the Malaysian flag. 

The tanker’s Second Deck Officer and Second Engineer were taken to the Pulau Indah marine police jetty for further action.

 

Photo credit: Malaysian Maritime Enforcement Agency
Published: 24 April, 2025

Continue Reading

Incident

Debris in lube oil caused engine room fire onboard passenger vessel in 2023, says NTSB

NTSB investigators found that debris in an engine’s lube oil system led to a diesel engine failure and an engine room fire aboard “Ocean Navigator” docked in Portland, Maine.

Admin

Published

on

By

Debris in lube oil caused engine room fire onboard passenger vessel, says NTSB

Debris in an engine’s lube oil system led to a diesel engine failure and an engine room fire aboard a passenger vessel docked in Portland, Maine, the National Transportation Safety Board (NTSB) said Tuesday (22 April).

The passenger vessel Ocean Navigator was moored at the Ocean Gateway Terminal on 18 October 2023, when the no. 2 auxiliary diesel generator engine suffered a catastrophic mechanical failure that seriously injured one crew member and resulted in an engine-room fire. Crewm embers secured ventilation to the engine room, and the fire self-extinguished. None of the 128 passengers onboard were injured, and no pollution was reported. Damage to the vessel was estimated at USD 2.4 million. 

After the fire, third-party technicians disassembled all components from the no. 2 auxiliary engine and found the crankshaft, several main bearings, connecting rod bearings and the no. 14 fuel injector were damaged. An additional inspection found abnormal wear on the connecting rod bearings and main bearings, which showed signs of cavitation erosion bearing damage, as well as damage from debris, which had been introduced at some point into the lube oil system.

NTSB investigators found the engine failure was caused by debris in the engine’s lube oil system—possibly due to the crew exceeding manufacturer-recommended intervals for changing the lube oil and oil filter elements—which caused catastrophic mechanical damage to the engine and a subsequent fire from the ignition of atomise lube oil released through the engine’s ruptured crankcase.

The crew had last changed the entire quantity of lube oil for the no. 2 auxiliary engine in September 2022—about 13 months before the engine failure—but the engine had operated more than 5,000 hours with this lube oil in the engine, five times longer than the manufacturer’s recommendation. Additionally, since the last change of the lube oil filter elements in May 2023, the engine had run over 3,000 hours. 

The engine manufacturer’s recommendation is to replace filter elements at every oil change or after the filter elements had been used for 1,000 hours.

“Manufacturers provide maintenance recommendations and intervals (schedules) to ensure equipment operates safely, optimally, and reliably throughout its service life,” the report said. 

“By regularly reviewing equipment manufacturer manuals and guidance, operators can ensure conformance with recommended maintenance plans and mitigate the risk of equipment malfunction or failure.” 

NTSB also found the crew’s quick action to secure engine room ventilation and engine fuel sources prevented the fire from spreading.

“Engine rooms contain multiple fuel sources as well as mechanical ventilation, making the spaces especially vulnerable to rapidly spreading fires,” the report said. 

“After an engine room fire ignites, it is imperative to remove the sources of available fuel and ventilation to the fire to prevent it from spreading. Vessel crews should familiarise themselves and train frequently on machinery, fuel oil, lube oil, and ventilation shutoff systems to quickly act to contain and suppress engine room fires before they can spread to other spaces.”

Note: Marine Investigation Report 25-13​ is available online.​

 

Photo credit: National Transportation Safety Board
Published: 24 April, 2025

Continue Reading

Incident

Armed group boards Marshall Islands-bulk carrier transiting in Singapore Strait

Bulker was boarded by four individuals armed with knives while transiting eastbound through Philip Channel, 9.5 nautical miles northeast of Great Karimun, Indonesia, according to Ambrey Analytics.

Admin

Published

on

By

396

A Marshall Islands-flagged bulk carrier was boarded by four individuals while transiting eastbound through the Philip Channel in the Singapore Strait, 9.5 nautical miles northeast of Great Karimun, Indonesia on Wednesday (23 April).

The individuals were reportedly armed with knives, according to Ambrey Analytics, the digital intelligence arm of the Ambrey risk management group. 

At the time of the incident, the vessel was underway at 10.6 knots with an estimated freeboard of 6.7 metres. The carrier was observed continuing on its original planned route.

Ambrey Analytics said crews transiting the Singapore Strait with freeboards lower than 10m are advised they are at heightened risk. 

“Crews should lock down access to the accommodation block and ship’s stores. It is recommended to carry out partnered deck patrols. Do not confront criminals,” it added.

Just two days before, a Panama-flagged crude oil tanker was boarded by an armed gang while transiting eastbound in the Philip Channel, 4.5 nautical miles northwest of Pulau Terung, Indonesia. 

The three individuals were reportedly armed with knives. At the time of the incident, the vessel was underway at 10.3 knots with an estimated freeboard of 6.3 metres. 

Related: Panama-flagged tanker heading to Johor boarded by armed gang off Indonesia

 

Photo credit: Ambrey Analytics
Published: 23 April, 2025

Continue Reading
Advertisement

OUR INDUSTRY PARTNERS



Trending