Browsed by
Tag: Bulk carrier

Brandweer Extinguishes Fire on Bulk Carrier Trade

Brandweer Extinguishes Fire on Bulk Carrier Trade

Trade
Photo: at4.nl

On the afternoon of May 15, the 190 meter long, 58096 dwt bulk carrier Trade (IMO: 9425942) caught fire while berthed at Amsterdam, Netherlands. The Trade was moored at the scrap terminal when a cargo of scrap caught fire in cargo hold #4. The local fire brigade was called out with multiple fire engines and fire boats responding. The burning scrap was hauled out of the cargo hold onto the quay where fire fighters would extinguish it while fireboats attempted to keep the bulk carrier’s hull cool.

Unfortunately, the time to extinguished the blaze was a slow and laborious process.  The fire could not be contained before it had spread into cargo hold #3.  Due to the high temperature, the #3 cargo hold hatches failed and eventually collapsed into the hold itself.  This prevented fire fighters to remove the scrap using a crane from that hold.

Reports state the fire spewed out large quantities of smoke that drifted over the center of the city. Authorities sent out an advisory to the surrounding area to bring in pets, turn off ventilation and close any open windows.  Due to the quantity of soot, authorities suggested that no one eat products from vegetable gardens that could be contaminated.

After 27 hours of fire fighting, the fire on board the Trade was finally was extinguished. A full log of events can be read on the Brandweer website. The extent of damage caused by the fire has not yet been disclosed. Authorities have launched an investigation into the incident.  This is the second scrap metal fire to occur in the port. On April 24, the Federal Tweed also suffered a cargo hold fire containing scrap metal. Fire fighters used the same strategy by unloading the burning scrap to the quay where it would be extinguished. An investigation may provide insight if this strategy can be improved when dealing with scrap metal fires on board bulk carriers.

Long Tau River Collision

Long Tau River Collision

Glengyle
Photo: tuoitre.vn

On the night of April 25, the 200 meter long, 34152 dwt container ship KMTC Surabaya (IMO: 9821081) collided with the 181 meter long, 37679 dwt bulk carrier Glengyle (IMO: 9727285) on the Long Tau River at An Thoi Dong, Ho chi Minh, Vietnam. The KMTC Surabaya bow struck the Glengyle just forward the superstructure along its port hull nearly breaking the vessel in two. With part of the hull ripped open, the Glengyle sustained uncontrolled water ingress in one of the holds and engine room causing the vessel to partially sink by the stern. The KMTC Surabaya sustained bow damage, but was able to contain the water ingress and was in no danger of sinking. There were no reports of injuries on either vessel.

Vietnamese Authorities responded to the incident and found the Glengyle had released oil pollution resulting in an oil sheen around both vessels. Containment booms were placed to contain the pollution.

Reports state the vessels were still locked together as both vessels drifted towards the shoreline. Salvage plans state the vessels will be pulled away from each other. Authorities state that maritime traffic in the area was not impacted by the incident. Authorities have launched an investigation into the incident.

Federal Tweed

Federal Tweed

Federal Tweed
Photo: nhnieuws.nl

On the morning of April 24, the 190 meter long, 55317 dwt bulk carrier Federal Tweed (IMO: 9658898) caught fire while berthed in Amsterdam, Netherlands. The blaze started in the hold containing a cargo of scrap releasing large quantities of smoke. The local fire brigade was alerted and dispatched fire fighters to the site while asking local residents in the area to close their windows and doors to keep the smoke out. Fire fighters used a crane to remove the scrap from the Federal Tweed‘s holds to the quay where it could be extinguished.  No reports of injuries.

Reports stated that fire fighters were engaged for an extended period in suppression efforts to ensure the fire did not flare up again. The extent of damage caused by the blaze was not disclosed.