Full Report
Satellite images newly obtained by Bellingcat shed light on how a stranded barge at the centre of a major oil spill ended up aground and leaking oil off the Tobago coast. The post How a Leaking Barge Became an Oil Spill Disaster Off the Tobago Coast appeared first on bellingcat.
Analysis Summary
# Incident Report: Venezuelan Oil Barge Grounding and Major Oil Spill off Tobago Coast
## Executive Summary
A major oil spill occurred off the coast of Tobago following a stranded barge, identified as the *Gulfstream* (later *Sea Marlin*), grounding and capsizing. Investigations using satellite imagery and AIS data tracked the vessel's suspicious journey from Panama, including a critical, undocumented stop at a Venezuelan state-owned oil facility (Pozuelo's Bay), where it likely became laden. The leak began immediately after departing this location, suggesting operational failure or deliberate misconduct related to the vessel's cargo transfer or condition prior to arrival in Tobago. Accountability remains unresolved as authorities seek the responsible parties.
## Incident Details
- **Discovery Date:** Early February (Barge ran aground off Tobago coast earlier this month; oil slick extended by late last week).
- **Incident Date:** Oil began leaking as early as February 3 (after leaving Pozuelo’s Bay); barge appears to have capsized by the morning of February 6.
- **Affected Organization:** Trinidad and Tobago Authorities, Caribbean Sea regional environment.
- **Sector:** Maritime transport, Petrochemicals/Oil.
- **Geography:** Journey involved Panama, Venezuela (Pozuelo’s Bay), and Tobago.
## Timeline of Events
### Initial Access
- **Date/Time:** Prior to January 22, 2024 (Barge prepared for voyage from Panama).
- **Vector:** Preparation and clandestine movement of the vessel using a tugboat (*Solo Creed*).
- **Details:** The barge (*Gulfstream* / *Sea Marlin*), towed by the *Solo Creed*, departed an informal harbor in Colón, Panama, sometime after December 30, 2023.
### Covert Voyage & Loading
- **Date/Time:** January 22 – February 3.
- **Vector:** Turning off Automatic Identification System (AIS) to obscure route.
- **Details:** The tugboat *Solo Creed* disabled its AIS on January 22. The vessels traveled approximately 375 nautical miles (a journey typically taking three days) before the *Solo Creed* re-enabled AIS on February 4. During this dark period, the barge was located in Pozuelo’s Bay, Venezuela—a known site for Petróleos de Venezuela (PDVSA) ship-to-ship oil transfers—between January 26 and the morning of February 3.
### Data Exfiltration/Impact
- **Date/Time:** Beginning February 3 through February 6.
- **Vector:** Grounding and capsizing of the barge.
- **Details:** Imagery confirms the barge began leaking oil immediately after leaving Pozuelo’s Bay on February 3. It appeared to have capsized by the morning of February 6. The resulting oil slick extended some 90 miles into the Caribbean.
### Detection & Response
- **Date/Time:** Early February to Present.
- **Vector:** Public reporting and satellite/AIS tracking analysis (Bellingcat investigation).
- **Details:** The vessel ran aground off Tobago. Authorities launched an investigation and requested accountability from those responsible.
## Attack Methodology
This incident involves maritime misconduct rather than a traditional cyberattack. The methodologies relate to operational deception and mismanagement:
- **Initial Access (Operational):** Utilizing a tugboat (*Solo Creed*) to tow an unseaworthy or improperly loaded barge (*Gulfstream*/*Sea Marlin*).
- **Defense Evasion (Maritime Deception):** Deliberate disabling of AIS transmissions for 14 days (Jan 22 to Feb 4) to hide the origin and nature of the journey, particularly the stop in Venezuela.
- **Collection/Loading (Inferred):** Visit to Pozuelo’s Bay, a major PDVSA port, strongly suggesting the barge received oil cargo there during the AIS blackout period.
- **Impact:** Vessel grounding, capsizing, and massive subsequent oil spill.
## Impact Assessment
- **Financial:** Costs associated with cleanup and remediation (not explicitly quantified in the text).
- **Data Breach:** N/A (Environmental/Physical incident).
- **Operational:** Major maritime incident declared by Tobago authorities; prolonged cleanup effort required for an oil slick extending 90 miles.
- **Reputational:** Increased scrutiny on maritime tracking, accountability for vessel ownership, and international environmental impact.
## Indicators of Compromise
This section focuses on operational indicators related to the vessels involved:
- **Vessel Identification:** *Gulfstream* (formerly *Sea Marlin*), Tugboat *Solo Creed*.
- **Operational Anomalies:** Deliberate AIS disabling for 14 days (Jan 22 - Feb 4).
- **Geographic Anomaly:** Stop at Pozuelo’s Bay, Venezuela, a noted hub for illicit or clandestine oil transfers.
- **Visual Indicator:** Photograph of *Solo Creed* allegedly flying the Tanzanian flag upside down was noted in pre-voyage imagery.
## Response Actions
- **Containment/Mitigation:** Authorities working to manage the resulting 90-mile oil slick in the Caribbean.
- **Investigation:** Extensive tracking efforts utilizing satellite imagery and AIS data reconstruction to determine the vessel's journey and potential points of culpability.
- **Legal/Accountability:** Tobago authorities called on responsible parties to come forward to face accountability.
## Lessons Learned
- **Transparency in Maritime Operations:** The intentional disabling of AIS highlights a critical vulnerability in tracking suspect vessel movements, requiring enhanced monitoring of vessels operating near known transfer hubs.
- **Vessel Condition:** The barge *Gulfstream* had been laid up on a beach in Panama for months prior to being towed, suggesting potential pre-existing structural deficiencies before the voyage began.
- **Ownership Obscurity:** The identity and current owner of the vessel remain unanswered questions for Tobago authorities, complicating accountability efforts.
## Recommendations
- Implement stricter monitoring protocols for vessels departing known high-risk ports or engaging in long periods of AIS deactivation, especially if associated with older or previously laid-up vessels.
- Enhance multi-source verification (satellite, port records, AIS reconstruction) to identify potential misuse of vessel names or flags (e.g., visual verification of flag status).
- Establish clear liability frameworks and mandatory disclosure requirements for maritime service providers (e.g., tow companies, ship managers like Mahi Shipping) involved in the transfer of potentially unseaworthy assets.