THE SHELL LEAKS FILES: 24 SEPTEMBER 2026
SLF-2007-067
The Sakhalin Papers LVII: The Spill Before the Whale Fight — Cristoforo Colombo, Kholmsk and Shell’s Emergency System Put to a Real-World Test
On 8 September 2004, Typhoon Songda drove the dredger Cristoforo Colombo aground only metres from the shore at Kholmsk. The vessel was working within the Sakhalin II construction chain. Fuel tanks ruptured, oil reached the sea and shoreline, Russian prosecutors opened a criminal investigation, and environmental organisations demanded that Shell halt marine work. Sakhalin Energy insisted that the vessel was neither owned nor directly contracted by the company and that its emergency organisation responded rapidly. A later company presentation provides something unusually valuable: an hour-by-hour response chronology. It also revises the amount of oil said to have escaped dramatically downward from the roughly 190–200 tonnes reported at the time to a final company estimate of 28 tonnes.
Archive reference: SLF-2007-067
Collection: The Sakhalin Papers
Principal authenticated records: Sakhalin Energy 2004 Annual Review; Sakhalin Energy presentation, Cristoforo Colombo Incident — 8th September 2004
Contemporaneous reporting: Energy Intelligence, Kommersant and contemporary Russian reporting
Legal record: Sakhalin environmental prosecutor’s criminal investigation under Article 252(2) of the Russian Criminal Code; subsequent civil claim against European Dredging Company
Related archive evidence: Rick Steiner’s 1999 Sakhalin oil-spill recommendations and the 2004–2005 environmental controversy
Evidence standard: Initial spill-volume estimates are distinguished from Sakhalin Energy’s later estimate. Statements by environmental organisations are attributed to them. Company response claims are tested where possible against Sakhalin Energy’s own detailed incident chronology.
Introduction
Yesterday’s file examined warnings.
Today’s examines what happened when Sakhalin II encountered an actual marine accident.
Not the catastrophic tanker loss Rick Steiner had feared.
Not an Exxon Valdez-scale crude-oil disaster.
But a genuine accident involving:
a project-related vessel;
severe weather;
engine failure;
ruptured fuel tanks;
shoreline contamination;
and an emergency response that immediately became the subject of dispute.
The vessel was the Belgian trailing-suction hopper dredger:
Cristoforo Colombo.
The date was:
8 September 2004.
And what happened over the following hours provides an unusually good test of competing descriptions of Sakhalin II’s preparedness.
1. The vessel was part of the Sakhalin II construction chain
The ownership and contractual relationships need to be stated precisely.
Cristoforo Colombo was owned by European Dredging Company and chartered by the Italian contractor Saipem.
Saipem was performing seabed-pipeline work for Sakhalin Energy.
At the time of the accident, the vessel was anchored near Kholmsk awaiting remobilisation to the Lunskoye area for further offshore pipeline work. Contemporary Energy Intelligence reporting described precisely that contractual chain. (Energy Intelligence)
Sakhalin Energy later emphasised an important distinction: the dredger was not owned or directly contracted by Sakhalin Energy. (Sakhalin Energy)
Both statements can be true.
The vessel was not a Sakhalin Energy-owned ship.
But it was working within the contractor chain of the Shell-led Sakhalin II project.
That distinction would become central to the argument over responsibility.
2. Typhoon Songda reaches Kholmsk
Sakhalin Energy’s later incident presentation reconstructs the final minutes before the grounding.
The weather deteriorated sharply.
The captain called for the main engines.
At 20:53, according to the company chronology, a low-fuel-oil-pressure alarm was followed by the first loss of engine power.
The vessel began drifting shoreward.
Both engines subsequently shut down automatically.
Anchors were lowered.
A Mayday was transmitted.
The company timeline places the vessel aground at approximately 21:30. (Japan Petroleum Association)
A separate summary slide in the same company presentation gives 21:50 as the incident time, so even the surviving corporate record contains a minor timing discrepancy.
The broader sequence is not in doubt.
Engine power was lost during extreme weather.
The anchors could not hold the vessel.
Cristoforo Colombo was driven onto the shoreline.
3. Fifty metres from land
Sakhalin Energy’s incident presentation describes the vessel as grounding approximately 50 metres offshore, between Kholmsk Commercial Port and the Fishing Port.
There were 29 crew members aboard.
No injuries were reported. (Japan Petroleum Association)
A later salvage account gives a similar description: severe winds associated with Typhoon Songda drove the dredger onto a stony shoal close to shore while it awaited remobilisation for Sakhalin II offshore-pipeline work. (Dredgepoint)
Three fuel tanks were damaged.
Oil entered the sea.
Then the numbers began to diverge.
4. How much oil actually escaped?
This is one of the most important documentary issues in the incident.
Contemporaneous reporting repeatedly cited figures close to 190–200 tonnes.
Energy Intelligence reported on 12 September 2004 that approximately 190 tonnes of fuel oil and diesel had been lost. (Energy Intelligence)
Kommersant reported several days later that around 200 tonnes of diesel and fuel oil had escaped after the vessel’s tanks were damaged. (Коммерсантъ)
Those were the figures entering the contemporary public record.
But Sakhalin Energy’s later technical presentation says something substantially different.
5. Sakhalin Energy later said the final estimate was 28 tonnes
The company presentation records the initial damage assessment as:
two heavy-fuel-oil tanks ruptured, with a possible loss of 120 tonnes;
one diesel tank ruptured, with a possible loss of 70 tonnes.
That explains the early figure of approximately 190 tonnes.
But the same presentation then states:
“Final estimates are 28 tonnes of oil lost in total.”
The vessel had been carrying substantially more fuel — 161 tonnes of heavy fuel oil and 160.5 tonnes of marine diesel in its tanks — but Sakhalin Energy’s later calculation was that only 28 tonnes actually escaped. (Japan Petroleum Association)
This is a significant documentary correction.
The historical archive should therefore not state simply that “190 tonnes were spilled” as though that figure were uncontested.
The proper formulation is:
early public estimates were approximately 190–200 tonnes; Sakhalin Energy subsequently gave a final estimate of 28 tonnes.
No independent judicial determination of the precise spill quantity has been located for this instalment.
6. The first hour: Sakhalin Energy mobilises
Sakhalin Energy’s 2004 Annual Review says the company:
“reacted immediately”
and was asked to manage the continuing response under a Unified Command arrangement.
It says Sakhalin Energy established its emergency-response team and mobilised its oil-spill contractor’s command group and response team:
“within one hour.”
The company’s more detailed incident timeline broadly supports the first part of that account.
It records the Mayday at approximately 21:30.
By 22:30, Sakhalin Energy’s emergency control team had been manned. (Japan Petroleum Association)
But mobilisation is not the same thing as arrival at the shoreline.
That distinction became the centre of the subsequent criticism.
7. The company’s own timeline shows the on-site delay
Environmental organisations later said it took about nine hours for Sakhalin Energy’s response contractor to reach the site.
The company’s own chronology provides useful context.
It records the emergency control team departing for Kholmsk at:
04:45 on 9 September.
It records arrival at the site at:
06:35.
Measured from the approximately 21:30 grounding, that is roughly nine hours.
Thus two apparently competing claims can be reconciled.
Sakhalin Energy says its organisation was mobilised within an hour.
The detailed company record shows personnel reaching the site many hours later.
Those statements describe different stages of the response.
8. Equipment was not instantly deployable
The company chronology records oil-spill response and personal-protective equipment being prepared for transport at 05:25.
At 10:29, boom was on its way to the beach.
But the entry contains a crucial qualification:
“Too rough to deploy.”
Additional response equipment travelled from Yuzhno-Sakhalinsk and the LNG construction site later that morning.
The trucks reached Kholmsk at approximately:
16:00 on 9 September.
A boom was laid out in the commercial harbour ready for deployment at approximately 19:19. (Japan Petroleum Association)
The company timeline therefore demonstrates the practical problem Rick Steiner had repeatedly emphasised:
having an emergency plan and equipment somewhere within the regional system is not the same thing as being able to put that equipment into the water immediately during severe weather.
9. What about the claim of a 48-hour delay?
Environmental organisations subsequently alleged that although Sakhalin Energy’s contractor arrived after roughly nine hours, it took more than 48 hours to bring necessary equipment to the incident.
That claim appeared in later environmental submissions concerning Sakhalin II. (WWF EU)
The primary company chronology does not support a blanket proposition that no response equipment reached Kholmsk for 48 hours.
It records equipment trucks arriving during the afternoon of 9 September and boom being readied that evening. (Japan Petroleum Association)
It is possible that the environmental groups were referring to particular categories or quantities of equipment rather than all equipment.
The documents examined here do not resolve that point.
Accordingly, the 48-hour allegation should remain attributed rather than converted into an established fact.
10. The sea itself limited the response
The incident demonstrates another problem.
Boom is useful only when it can be safely and effectively deployed.
The company record expressly states that conditions were too rough for deployment during part of 9 September. (Japan Petroleum Association)
This is significant because one of the central arguments in the earlier Steiner material concerned Sakhalin’s physical environment.
Remote location, extreme weather, ice, waves and wind could turn apparently adequate paper resources into resources that could not be used when most needed.
The Cristoforo Colombo accident did not prove what would happen during a catastrophic offshore tanker spill.
But it provided a real-world example of weather constraining marine response.
11. Oil nevertheless reached the shoreline
Contemporary reporting records visible contamination.
Energy Intelligence reported a sheen approximately 7.5 kilometres long, although thin, moving northward before dissipating.
It also reported oil reaching Kholmsk’s public beach. (Energy Intelligence)
Russian reporting described roughly five kilometres of shoreline as affected, including the city waterfront. (Коммерсантъ)
Sakhalin Energy’s own later presentation records shoreline surveys extending five kilometres north and south of the vessel.
The survey programme recorded oil within parts of the commercial-port area and an oiled bird found on 11 September that subsequently died. (Japan Petroleum Association)
Those company records independently establish that the environmental consequence was not confined to oil remaining aboard the damaged dredger.
12. Sakhalin Energy says the principal cleanup was completed quickly
The company’s 2004 Annual Review says cleanup of affected areas was essentially completed by:
12 September 2004.
It says portions of Primorsky Boulevard reopened that day.
According to Sakhalin Energy, the entire cleanup was completed within approximately:
two weeks.
Those are the company’s statements.
They establish what Sakhalin Energy reported about completion of the response.
They do not independently resolve questions about residual contamination, environmental effects or whether critics regarded the cleanup standard as adequate.
13. The critics saw a different emergency
Environmental organisations reacted aggressively.
They characterised the accident as evidence that Sakhalin II’s spill-prevention and response arrangements were inadequate and demanded a temporary moratorium on marine operations until a comprehensive response plan covering project contractors and subcontractors was in place. (VFF S)
Their central argument concerned contractor boundaries.
From their perspective, Sakhalin Energy could not claim internationally high project standards while excluding a vessel working through its construction chain from the relevant preparedness system.
That was an advocacy position.
Sakhalin Energy rejected the premise.
14. Sakhalin Energy said Kholmsk was not a project production facility
The company’s formal answer is set out clearly in the 2004 Annual Review.
Sakhalin Energy said it had:
no production operations at Kholmsk.
The company and its contractors used the port in the same way other industries used it for ordinary shipping activities.
According to Sakhalin Energy, any ferry, fishing boat or merchant vessel could have suffered a similar accident during the extreme weather.
The company therefore said there was no requirement for Sakhalin Energy to maintain an oil-spill contingency plan or response equipment specifically for Kholmsk. (Sakhalin Energy)
That is the company’s legal and operational position as published at the time.
15. Yet Sakhalin Energy took command of the response
This produces an interesting documentary tension.
Sakhalin Energy said the accident fell outside circumstances requiring it to maintain dedicated spill capability at the port.
Nevertheless, the company says it:
mobilised its emergency organisation;
mobilised its response contractor;
and was asked to manage the response through the Unified Command structure. (Sakhalin Energy)
That does not make the company legally responsible for causing the accident.
But it demonstrates that, once the spill occurred, Sakhalin Energy possessed both the resources and the organisational role to become deeply involved in managing the consequences.
16. The Russian environmental prosecutor opened a criminal case
The event moved rapidly from environmental controversy into formal legal proceedings.
On 16 September 2004, Kommersant reported that the Sakhalin inter-district environmental prosecutor had opened a criminal case under:
Article 252, Part 2 of the Russian Criminal Code
concerning pollution of the marine environment.
The report said approximately 200 tonnes of diesel and fuel oil were then believed to have leaked and that a five-kilometre stretch of coastline had been contaminated. (Коммерсантъ)
The opening of an investigation establishes neither guilt nor the accuracy of the contemporary quantity estimate.
No final criminal judgment resolving those questions has been located for this instalment.
17. A civil damages claim followed
The legal aftermath continued into 2005.
On 31 March 2005, Kommersant reported that Sakhalin environmental prosecutor Sergei Mochalov had brought a civil claim in Yuzhno-Sakhalinsk seeking:
8.5 million roubles
from European Dredging Company S.A., the Belgian owner of Cristoforo Colombo, on behalf of the Kholmsk district.
The amount was said to correspond to environmental damage arising from the September accident. (Коммерсантъ)
Significantly, the reported defendant was the ship owner — not Shell and not Sakhalin Energy.
That is consistent with the legal distinction Sakhalin Energy had emphasised.
The final disposition of that civil action has not been located in the public sources examined for this file.
18. The vessel itself never returned to service
Attempts to salvage Cristoforo Colombo failed.
By February 2005, Russian reporting said a decision had been made to dismantle the dredger where it lay.
Two salvage efforts had failed, while winter storms further enlarged damage to the hull. (Коммерсантъ)
Independent vessel records likewise identify the dredger as having become a constructive total loss after the Kholmsk grounding and subsequently being broken up in situ. (Ship Photos)
The accident was therefore not merely a temporary grounding.
The ship was lost.
19. Sakhalin Energy changed something afterwards
One passage in the company’s Annual Review deserves particular attention.
Following the grounding, Sakhalin Energy announced a series of what it called goodwill projects for Kholmsk.
They included improvements to Primorsky Boulevard, health facilities and other community measures.
But the first measure listed was particularly relevant:
deployment of oil-spill response equipment for use in the town.
That does not amount to an admission that the pre-accident arrangements were legally deficient.
The company explicitly denied that it had been required to maintain such equipment at Kholmsk.
But it does establish that after the accident, additional local spill-response capability formed part of Sakhalin Energy’s response.
20. That is where the 1999 warnings become relevant again
Five years earlier, Rick Steiner and his colleagues had argued that effective Sakhalin spill preparedness required more than written plans.
They emphasised:
equipment positioning;
rapid access to affected coastlines;
trained personnel;
tugs and vessels;
independent oversight;
contractor standards;
and planning for severe weather before an accident occurred.
The Cristoforo Colombo incident cannot be used to prove that all of those earlier recommendations had been disregarded.
Nor can it demonstrate that implementation of any single recommendation would necessarily have prevented this grounding.
But the accident involved exactly the categories the earlier work had treated as important:
a contractor-chain vessel,
severe weather,
mechanical failure,
oil entering coastal waters,
equipment that could not immediately be deployed,
and disagreement over where project responsibility began and ended.
That continuity is documentary fact.
Whether it amounts to vindication of the critics is commentary.
21. A particularly useful primary record
The later Sakhalin Energy presentation is especially valuable because it cuts through part of the rhetoric surrounding the accident.
It shows that both sides could make statements that sounded contradictory while referring to different facts.
Sakhalin Energy could truthfully say:
the emergency organisation was mobilised within one hour.
Critics could also point out:
the company’s own timeline places the emergency team at Kholmsk roughly nine hours after grounding.
Similarly:
contemporaneous sources could report a possible 190–200 tonne release based on ruptured tanks;
while Sakhalin Energy could later calculate a final actual loss of 28 tonnes.
A documentary archive should preserve those distinctions rather than choosing whichever number best supports a preferred narrative.
Documentary Findings
Established
On 8 September 2004, the Belgian dredger Cristoforo Colombo grounded near Kholmsk during Typhoon Songda after engine-power problems and failure to maintain position. (Japan Petroleum Association)
The vessel was owned by European Dredging Company and chartered by Saipem for work connected with Sakhalin II offshore-pipeline construction. (Energy Intelligence)
The vessel was neither owned nor directly contracted by Sakhalin Energy. (Sakhalin Energy)
Fuel tanks were damaged and oil entered the marine environment.
Contemporaneous reporting estimated the release at roughly 190–200 tonnes. (Energy Intelligence)
Sakhalin Energy’s later technical presentation revised the final estimated quantity to 28 tonnes. (Japan Petroleum Association)
Sakhalin Energy’s emergency control team was manned approximately one hour after the grounding, while its own detailed chronology shows the emergency team reaching Kholmsk the following morning. (Japan Petroleum Association)
The company chronology records that weather conditions were initially too rough for boom deployment. (Japan Petroleum Association)
Oil reached the shoreline and commercial-port area, and Sakhalin Energy’s later survey record identifies an oiled bird that subsequently died. (Japan Petroleum Association)
Sakhalin Energy said affected areas were essentially cleaned by 12 September and the full cleanup was completed in approximately two weeks. (Sakhalin Energy)
Russian environmental prosecutors opened a criminal investigation into marine pollution. (Коммерсантъ)
A subsequent civil claim sought 8.5 million roubles from European Dredging Company for environmental damage. (Коммерсантъ)
The dredger was ultimately declared unsalvageable and dismantled in place. (Коммерсантъ)
Sakhalin Energy’s stated position
The company maintained that Cristoforo Colombo was neither owned nor directly contracted by Sakhalin Energy and that Kholmsk was not a Sakhalin Energy production facility.
It said there was therefore no requirement for it to maintain dedicated oil-spill contingency equipment at the port.
Nevertheless, it said it responded immediately, mobilised its emergency organisation and response contractor, and took a leading role in the Unified Command response. (Sakhalin Energy)
Sakhalin Energy subsequently gave the final spill estimate as 28 tonnes and said the cleanup was completed within approximately two weeks. (Japan Petroleum Association)
The critics’ stated position
Environmental organisations argued that the contractor distinction was too narrow for a development of Sakhalin II’s scale.
They said the accident demonstrated weaknesses in project-wide spill preparedness and called for a moratorium on marine work until an internationally acceptable spill-prevention and response regime covering contractors and subcontractors was established. (VFF S)
They also alleged delays in the arrival and deployment of response resources.
Those remain attributed allegations rather than independent findings.
Not established
It is not established that 190–200 tonnes actually entered the environment; that was the early estimate, while Sakhalin Energy subsequently estimated 28 tonnes.
It is not established by the records examined here that Sakhalin Energy caused the grounding.
It is not established that Sakhalin Energy was legally required to maintain spill-response equipment at Kholmsk before the accident.
It is not established that every item of necessary response equipment took more than 48 hours to reach the scene.
It is not established that the grounding resulted from failure to implement a specific recommendation made by Rick Steiner or the authors of Sakhalin’s Oil: Doing It Right.
It is not established that the criminal investigation resulted in a conviction.
It is not established from the sources located here how the 8.5-million-rouble civil claim was finally resolved.
And the accident does not establish how Sakhalin Energy would have performed during a catastrophic crude-oil tanker release offshore.
Commentary
Cristoforo Colombo matters because it converts theoretical risk into observable behaviour.
Before 8 September 2004, arguments over Sakhalin oil-spill preparedness could remain hypothetical.
Afterwards, there was a clock.
When was the alarm raised?
When was Sakhalin Energy’s emergency centre staffed?
When did responders leave?
When did they reach Kholmsk?
When did equipment arrive?
When could boom actually be deployed?
Those questions can now be answered at least partly from Sakhalin Energy’s own records.
And the answer is more nuanced than either side’s slogan.
The company did mobilise quickly.
But rapid mobilisation did not mean immediate physical response.
Severe weather mattered.
Distance mattered.
Equipment location mattered.
Contractual boundaries mattered.
Exactly the subjects that had featured in the earlier warnings.
The more important lesson may concern contractors
Large energy projects do not consist only of the operating company.
They depend on chains of:
engineering companies;
construction companies;
ship owners;
charterers;
subcontractors;
ports;
transport companies;
and specialist response organisations.
An accident can therefore occur several contractual steps away from the corporate entity whose name the public associates with the project.
That is what happened at Kholmsk.
Sakhalin Energy’s legal distinction was real.
So was the project connection.
Both belong in the record.
And there is one revealing postscript
Sakhalin Energy said before and after the accident that it was not required to maintain dedicated spill-response capability at Kholmsk.
Yet after the grounding it arranged:
new oil-spill response equipment for Kholmsk.
That does not prove an earlier violation.
But it does show that the accident changed the practical arrangements.
Sometimes the clearest evidence that an incident mattered is not found in what a company says about blame.
It is found in what the company does next.
Source Record
Sakhalin Energy’s authenticated 2004 Annual Review gives the company’s formal account of the grounding, its contractual position, its emergency response, cleanup timetable and subsequent Kholmsk initiatives. It also records the deployment of additional oil-spill response equipment in Kholmsk following the incident. (Sakhalin Energy)
Sakhalin Energy — 2004 Annual Review
A later Sakhalin Energy incident presentation, Cristoforo Colombo Incident — 8th September 2004, supplies the detailed chronology used in this instalment. It records the engine-power failure, grounding sequence, emergency-response timings, equipment movements, shoreline surveys and the company’s final spill estimate of 28 tonnes. (Japan Petroleum Association)
Cristoforo Colombo Incident — Sakhalin Energy presentation
Energy Intelligence’s contemporaneous report of 12 September 2004 recorded an initial estimate of approximately 190 tonnes, the contractual relationship between European Dredging Company, Saipem and Sakhalin Energy, the cleanup operation and the reported 7.5-kilometre surface sheen. (Energy Intelligence)
Energy Intelligence — Oil Spill off Sakhalin Sparks Renewed Green Pressure, 12 September 2004
Kommersant reported on 16 September 2004 that the Sakhalin environmental prosecutor had opened criminal proceedings concerning marine pollution and described approximately five kilometres of affected shoreline. (Коммерсантъ)
Kommersant — Prosecutor investigates Cristoforo Colombo spill, 16 September 2004
Kommersant subsequently reported on 31 March 2005 that the environmental prosecutor had filed an 8.5-million-rouble civil claim against European Dredging Company on behalf of Kholmsk district. (Коммерсантъ)
Kommersant — Civil damages claim arising from Cristoforo Colombo grounding, 31 March 2005
A further Kommersant report of 25 February 2005 records the failed salvage attempts and the decision to dismantle the vessel in place. (Коммерсантъ)
Kommersant — Cristoforo Colombo to be dismantled at Kholmsk, 25 February 2005
Archive disclaimer: Contemporary accounts differed significantly over the amount of fuel released. This file therefore preserves both the initial approximately 190–200-tonne estimate and Sakhalin Energy’s later 28-tonne final estimate rather than selecting one without qualification. Allegations concerning response delays and regulatory shortcomings made by environmental organisations remain attributed to those organisations unless independently corroborated. The existence of a criminal investigation or civil claim is not evidence of criminal or civil liability by Shell or Sakhalin Energy.
Site-wide disclaimer applies.
Next instalment
The Sakhalin Papers LVIII: The Audit After the Spill — When Independent Inspectors Tested Sakhalin II’s Safety System
Cristoforo Colombo was cleaned up.
The wreck remained.
But another paper trail was beginning.
Prospective lenders to Sakhalin II were commissioning independent health, safety and environmental scrutiny of the project.
A 2005 Lenders Tier III HSE Audit subsequently entered the public debate.
Environmental organisations later said the auditors had identified poor management of oil-spill response equipment — including materials used during the Cristoforo Colombo response that had not been replaced. A 2006 German parliamentary document also cited the same Phase I lenders’ audit while questioning Sakhalin II’s environmental performance. (WWF EU)
Those are secondary descriptions of the audit.
The next instalment will go back to the audit trail itself wherever the surviving records permit and ask:
After the Kholmsk accident exposed Sakhalin II’s emergency system to a real spill, what did the independent inspectors find — and what did prospective lenders know before deciding whether to put their money behind Shell’s $20-billion project?
*This website and sisters royaldutchshellgroup.com, shellnazihistory.com, royaldutchshell.website, johndonovan.website, shellnews.net, and shellwikipedia.com, are owned by John Donovan - more information here. There is also a Wikipedia segment, the Shell DPA Files, "Shell and the Spies", the Shell Leaks files, as well as books written and published by John Donovan - Kindle eBooks. Timeline of the Donovan Shell Feud. Toxic History of Royal Dutch Shell Group. Shell and the Donovans: The Full Media Record — 550+ Articles, 110 Books, 40 Years. *All created and supported by internet wizz, Nick Gill.
