வணிகம் · Containership fireSouth Atlantic ship explosion reported: Espirito Santo Express salvors engagedஎழுத்து வடிவம் 21 அக்டோபர், 2026 அன்று 10:32 AM UTCபாருங்கள்உரைப்பதிவு0:07Fire interrupted the Espirito Santo Express's voyage to Brazil.0:11C-SPAN says every crew member is safe and accounted for.0:14Professional salvers have been engaged, while the extent of damage to the ship and0:17its cargo remains unclear.0:19Whether those salvers have secured the vessel and brought the fire under control0:22still isn't clear.0:23The container ship was sailing from Singapore to Santos.0:26Built in 2020 by Yangzijiang Shipbuilding Group, it has a reported gross tonnage of0:31113,828.0:34That's a measure of the vessel's size rather than the weight of cargo it was0:38carrying.0:39C-SPAN owns the ship, and Hapag-Lloyd charters it.0:42C-SPAN notified the charterer about the fire.0:45The clearest later development is the appointment of SMIT, a professional salvage0:49firm, to respond to the casualty.0:51The reported incident window is October 15th to 16, 2026.0:55Hapag-Lloyd acknowledged the fire on October 16th.0:58By October 19th, SMIT had been engaged under a salvage contract known as LOF.1:03The precise outbreak time is still unclear.1:05The fire was already public several days before October 21.1:09The salvage appointment adds a concrete response, but an appointment alone doesn't1:12tell us whether a salvage team has reached the vessel.1:15At the time of the casualty, the ship was reportedly adrift about 975 nautical miles1:20northwest of Tristan da Cunha.1:22That puts the incident in the remote South Atlantic well away from its intended1:25destination at Santos.1:27That distance is an approximate historical position.1:29It shouldn't be read as a live location for the ship.1:32The voyage began in Singapore, but the fire interrupted the journey before the1:35vessel reached Brazil.1:37An explosion reportedly preceded the fire.1:39Nearby vessels were asked to help, and all crew were understood to have abandoned1:43ship safely.1:44What ignited and where aboard the ship the fire began haven't been explained.1:49The evacuation account can coexist with C-SPAN's assurance that everyone was safe.1:53A crew can leave a burning vessel and still be fully accounted for.1:56Hapag-Lloyd's statement never said the crew stayed aboard.1:59Hapag-Lloyd passed on C-SPAN's assurance on October 16th.2:03It remains the clearest statement about the people aboard.2:05Nobody has provided an injury assessment, and the sequence of any evacuation hasn't2:08been clarified.2:09The ship's carrying capacity also needs care.2:12Shipping companies measure container space in TEU short for 20-foot equivalent2:16units.2:17One unit represents a standard 20-foot container.2:19The published vessel capacity and a separate cargo listing give different figures.2:23One vessel listing gives capacity as 11,800 TEU.2:28A separate cargo listing says up to 11,923 TEU.2:32Those figures haven't been reconciled.2:34The amount actually loaded aboard the ship hasn't been confirmed.2:37The cargo listing includes temperature-sensitive goods.2:40Hapag-Lloyd said it was assessing the incident's extent and possible effects on2:44cargo and vessel operations.2:46Cargo owners still don't have a confirmed damage total or a timetable for delivery.2:51Hapag-Lloyd said measures were being taken to bring the situation under control.2:55Smit has since been engaged.2:56As of October 21st, nobody has confirmed that the fire is out or towing has started.3:01The ship's current position remains unclear.கட்டுரையைப் படிக்கவும்செய்தியின் காலவரிசைHeyDexகுறுங்காணொளி ↗
