Discover the W-sapphire: Ratings & Maritime News
IMO: 9605645
Bulk Carrier, Liberia
Photos
Vessel Details
MMSI
636023364
Callsign
D5AF7
Width
32.0 m
Length
229.0 m
Reviews (1)
Wayne
2025-03-28
Position: Third Officer
Advantages:
Looking for information about this vessel. Can someone share their experience on this vessel? Would you recommend it?
Disadvantages:
No personal experience yet, just gathering info.
Featured Review Articles
Incident Overview: W-sapphire Explosion and Recovery Efforts
On August 18, 2025, the bulk carrier <a href='/ships/w-sapphire-9605645'>W-sapphire</a> experienced a significant explosion while en route from Baltimore to Port Louis, just after loading a cargo of coal at CSX's Curtis Bay terminal. The explosion oc...
Read Full ReviewLatest News (7)
Recovery of 30-Ton Hatch Cover from 'W Sapphire' Clears Path for Shipping Traffic
On August 28, officials successfully retrieved the 30-ton hatch cover of the 'W Sapphire', which had become lost following a significant explosion on the vessel in the Patapsco River. This incident had led to a temporary safety zone enforced by the Coast Guard, resulting in intermittent restrictions for maritime traffic navigating the Fort McHenry Federal Channel. Following the hatch's recovery, the Coast Guard promptly reopened the channel, allowing vessels to resume their operations. In the aftermath, the U.S. Army Corps of Engineers deployed sonar technology to assess the riverbed and ensure there were no remaining obstructions that could hinder shipping activities.
Salvage Operation Closes Baltimore Channel Following W-Sapphire Hatch Incident
On August 27, maritime operations faced disruptions as the U.S. Coast Guard established an intermittent safety zone to facilitate the recovery of a hatch from the bulk carrier 'W-Sapphire'. The hatch was dislodged due to an explosion that occurred on August 18, occurring south of Fort Carroll. The designated safety zone encompassed all waters within a 500-yard radius of the hatch cover's last known position in the Baltimore channel. The Port of Baltimore announced that the channel would be officially closed from 8 a.m. to 5 p.m. for safety reasons. As of August 28, the 'W-Sapphire' was reported to be anchored off Sandy Point while investigations continued; no definitive cause for the explosion has been established. For further updates and visual coverage, visit: https://www.thebanner.com/community/transportation/channel-closed-w-sapphire-F7BDLUOH3NERFD2H6ZRRLFS3HI/
Salvage Operations Prompt Closure of Fort McHenry Federal Channel Following W-Sapphire Explosion
On August 27, the Fort McHenry Federal Channel was temporarily closed to establish a safety zone for salvage operations concerning a hatch cover that was ejected during a significant explosion aboard the bulk carrier 'W-Sapphire'. This unfortunate incident occurred on August 18 at 9:30 p.m. while the vessel was departing from Baltimore Harbor, carrying 23 crew members and two pilots. The channel's closure was scheduled from 8 a.m. to 5 p.m. to allow recovery efforts of the massive hatch cover, which was located earlier in the week. The Army Corps of Engineers utilized a sonar-equipped survey vessel at the explosion site to aid in this process. Following the incident, the Coast Guard established a 2,000-yard safety zone stretching from the Key Bridge to Brewerton Angle Channel Lighted Buoy “14”. Multiple crews from the Coast Guard, in conjunction with the Baltimore Fire Department and Maryland Natural Resources Police, were dispatched to manage the situation and ensure public safety. As of the morning of August 26, the Port of Baltimore confirmed that the Fort McHenry Federal Channel would remain closed while the Coast Guard assessed when it could safely reopen for regular vessel traffic, pausing all incoming and outgoing ship movements. Earlier, the Coast Guard had lifted a temporary safety zone on August 21, which had been activated the previous day, thereby allowing boats to navigate freely in the area until restrictions were reinstated for salvage work. Investigators from the Coast Guard, along with various other agencies, plan to board the W-Sapphire to determine the cause of the explosion. Post-investigation, the Coast Guard will focus on developing a plan to safely remove the bulk carrier from the port, which remained moored at positional coordinates 39° 01' N 076° 22' W as of August 27. For more details and visuals, visit: https://www.msn.com/en-us/news/us/coast-guard-to-salvage-30-ton-hatch-from-ship-explosion-in-baltimore/ar-AA1KXCGc?apiversion=v2&noservercache=1&domshim=1&renderwebcomponents=1&wcseo=1&batchservertelemetry=1&noservertelemetry=1.
Draft Restrictions Enforced on Patapsco River Amid W Sapphire Salvage Efforts
On August 20, personnel from Coast Guard Sector Maryland-National Capital Region, alongside various partner agencies, continued their salvage planning efforts to recover a hatch cover that became dislodged during an explosion on the 'W Sapphire' in Baltimore's port. As a safety precaution, a draft restriction is currently enforced, limiting the maximum navigational draft to 46.6 feet for vessels navigating within a 500-yard proximity to the hatch cover's location. Additionally, a temporary safety zone encompassing all navigable waters within this radius will be reactivated during upcoming dive and salvage operations. The Coast Guard Sector Maryland-National Capital Region will keep the public informed with updates on this safety zone. As of August 21, the 'W Sapphire' remains anchored north of the Chesapeake Bay Bridge, positioned at 39° 02' N 076° 22' W. The vessel is operating under its vessel response plan and is reported to be in stable condition. Following a joint boarding with various investigative entities, plans are being formulated to safely expedite the removal of the 'W Sapphire' from the port.
Fort McHenry Federal Channel in Baltimore Reopened Following Vessel Explosion
In a swift move to restore maritime operations, the U.S. Coast Guard has reopened the Fort McHenry Federal Channel, which serves as a vital access route to and from the Port of Baltimore. This reopening comes just one day after an explosion on board the 'W Sapphire' led to the channel's temporary closure. Collaborating seamlessly with tugs, pilots, and other port stakeholders, the Coast Guard implemented measures to facilitate a rapid return to normalcy. As of August 19, access to the Patapsco River was initially restricted for all vessels, specifically between coordinates 39°11.70’ N, 076°31.71’ W - near Swan Creek - and 39°12.6’ N, 076°29.74’ W - close to Sparrows Point, extending up to the area adjacent to the former location of the Francis Scott Key Bridge. A 500-yard safety zone has been established around the site of the explosion, where the 'W Sapphire' came to anchor at coordinates 39°01.4’ N, 076°22.10’ W, which is north of the Chesapeake Bay Bridge. Fortunately, no injuries have been reported, and the fire resulting from the explosion has now been extinguished, although the cause remains under investigation. The explosion resulted in a hatch being dislodged and sent into the surrounding waters. Efforts to locate and retrieve the hatch are underway, with its exact position and potential impact on navigational routes still being assessed. To assist in identifying any navigational hazards near the incident site, the U.S. Army Corps of Engineers deployed the sonar-equipped vessel 'Buck' around 7:30 a.m. This vessel commenced data collection aimed at elucidating any obstructive factors that could hinder safe navigation into and out of the Port of Baltimore via the Fort McHenry Federal Channel. The findings will help structure a comprehensive operational plan to ensure the channel's full reopening. The incident response has elicited a collaborative effort among multiple agencies, including Coast Guard Station Curtis Bay, a response crew from Coast Guard Station Annapolis, Sector Maryland – National Capital Region personnel, Baltimore Fire Department teams, and members of the Maryland Department of Natural Resources Police. Together, they are closely monitoring the situation and coordinating recovery efforts to maintain maritime safety in the area. In a recent update, the expansive 2,000-yard safety zone previously effective around the detached hatch has been rescinded, though an intermittent safety zone within a 500-yard radius of the hatch cover at coordinates 39.20865° N, 76.52017° W will be enacted during scheduled dive and salvage operations, tentatively set for August 20 at 6:00 a.m. Meanwhile, the 500-yard safety zone around the 'W Sapphire' at coordinates 39.02333° N, 76.36833° W remains in place, with mariners advised to steer clear of this area. Notably, drat restrictions for vessels navigating within a 500-yard boundary of the detached hatch have been imposed, limiting vessels to a maximum navigational draft of 46.6 feet due to a recorded depth of 49.7 feet at Mean Lower Low Water (MLLW). Crews continue to await confirmation of safe conditions for progressing with further Coast Guard investigations of the 'W Sapphire.' The Coast Guard and its partner agencies persist in their diligent monitoring of this maritime incident, ensuring a comprehensive response to safeguard operations around the Port of Baltimore.
W Sapphire Explosion on Patapsco River: Extensive Response Underway
An explosive incident occurred aboard the bulk carrier 'W Sapphire' on August 18, 2025, around 6:30 PM local time, while en route from Baltimore to Port Louis. The vessel, which had just taken on a coal shipment at CSX's Curtis Bay terminal in Baltimore, was navigating the Patapsco River in Chesapeake Bay, close to the collapsed Francis Scott Key Bridge, when the explosion took place south of Fort Carroll. Fortunately, all 23 crew members and two pilots operating the ship were unharmed. The Coast Guard Sector Maryland - National Capital Region quickly mobilized responders to the site. Fire containment efforts involved sealing the vessel’s hatches, effectively bringing the blaze under control, while fireboats maintained a presence in the area. The 'W Sapphire' was aided by tugs to a nearby mooring, where it anchored at coordinates 39° 02' N 076° 22' W. Additionally, a safety zone extending 2,000 yards around the explosion site has been established by the Coast Guard, covering the area from the Key Bridge to Brewerton Angle Channel LB “14.” Coordinated efforts by multiple agencies include: - Coast Guard Station Curtis Bay response boat crews - Coast Guard Station Annapolis response boat crew - Sector Maryland - National Capital Region responders - Baltimore Fire Department crews - Maryland Department of Natural Resources Police crews As plans for the affected vessel are being developed, watchstanders issued an Urgent Marine Information Broadcast (UMIB) and ensured coordination with local port partners to manage the ongoing response effectively. For video coverage of the incident, visit: https://twitter.com/i/status/1957590461075660940
Belo Horizonte Grounds on Paraná River, Navigation Resumes Quickly
On June 22, 2015, the vessel 'Belo Horizonte', en route from San Lorenzo, encountered trouble while navigating the Paraná River and ran aground at the entrance of the Emilio Mitre Channel. The incident prompted immediate attention, and operations to resume navigation were swiftly put in place. The Argentinian tug 'Ona Don Lorenzo' (IMO: 9328388) was dispatched and successfully towed the stranded 'Belo Horizonte' the following day, June 23, allowing the Emilio Mitre Channel to reopen for maritime traffic.
Frequently Asked Questions
🔥 Were there any fires on W-sapphire?
Based on available news reports, W-sapphire has been mentioned in connection with fire-related incidents. There have been 3 news reports mentioning fire incidents. For detailed information about specific incidents, please refer to the latest news section above.
🌊 Did W-sapphire sink or have any sinking incidents?
Based on available news reports, W-sapphire has been mentioned in connection with sinking-related incidents. There have been 3 news reports mentioning sinking incidents. For detailed information about specific incidents, please refer to the latest news section above.
🚫 Are there any sanctions against W-sapphire?
Based on available news reports, W-sapphire has been mentioned in connection with sanction-related incidents. There have been 1 news reports mentioning sanctions. For detailed information about specific incidents, please refer to the latest news section above.
🏴☠️ Was W-sapphire involved in any pirate attacks?
Based on available news reports, W-sapphire has been mentioned in connection with pirate-related incidents. There have been 1 news reports mentioning pirate attacks. For detailed information about specific incidents, please refer to the latest news section above.
⚙️ Did W-sapphire have any engine problems?
Based on available news reports, W-sapphire has been mentioned in connection with engine-related incidents. There have been 3 news reports mentioning engine problems. For detailed information about specific incidents, please refer to the latest news section above.
🚓 Was W-sapphire detained or arrested?
Based on available news reports, W-sapphire has been mentioned in connection with detention-related incidents. There have been 1 news reports mentioning detentions. For detailed information about specific incidents, please refer to the latest news section above.