THE SHELL LEAKS FILES
SLF-2007-025
The Sakhalin Papers XV: A Thousand Rivers — Salmon, Pipeline Crossings and the Contractor Problem
Archive reference: SLF-2007-025
Collection: The Sakhalin Papers
Principal record: The Shell Sustainability Report 2005; Sakhalin Energy river-crossing documentation and monitoring records; UK Export Credits Guarantee Department evidence to Parliament
Supporting record: Russian regulatory actions, Reuters and other contemporaneous reporting, EBRD records and subsequent court proceedings concerning UK government scrutiny of Sakhalin II
Evidence standard: Shell and Sakhalin Energy admissions are distinguished from regulator allegations, NGO claims, journalistic reporting, subsequent governmental assessments and judicial findings.
Introduction
The previous archive file followed the Western gray whales offshore.
This one follows the pipeline inland.
Sakhalin II required twin oil and gas pipelines to run almost the entire length of Sakhalin Island. In doing so, the route crossed more than 1,000 rivers and streams. Shell itself identified approximately 180 of those watercourses as potentially environmentally sensitive. Many supported salmon spawning. (Shell)
That scale transformed what might ordinarily have been a routine pipeline-construction issue into a project-management test.
A single badly executed river crossing might be a contractor error.
Scores of crossings carried out under tight construction schedules raised a more difficult question:
How does a project operator ensure that environmental commitments made in corporate documents are actually followed by contractors working hundreds of kilometres away?
Shell’s own 2005 Sustainability Report supplies an unusually candid starting point.
It acknowledged that contractors did not always comply with Sakhalin Energy’s river-crossing strategy during the winter of 2004–05. (Shell)
That admission is central to this file.
The controversy did not begin with an environmental group accusing Shell of wrongdoing.
It begins with Shell saying, in its own published report, that the system had failed.
1. More Than 1,000 Crossings
Sakhalin Energy’s onshore pipeline system extended roughly 800 kilometres along the island and crossed approximately 1,000 freshwater bodies. Shell’s Sustainability Report said around 180 were regarded as potentially environmentally sensitive. (Shell)
The environmental concern was straightforward.
Pipeline construction can disturb riverbeds, banks and surrounding soil. Sediment entering a spawning river can affect aquatic habitat, while excavation, temporary dams, vehicle movements and erosion can change the physical condition of the channel.
Shell explicitly recognised that the onshore pipeline crossed salmon-spawning rivers and said construction therefore needed to be carefully managed. (Shell)
Sakhalin Energy says it conducted baseline studies and environmental monitoring of water bodies crossed by the pipelines and later developed long-term monitoring programmes covering water quality, sediments, riverbed morphology, benthic organisms, fish populations and potential salmon-spawning areas. (Sakhalin Energy)
That is the operator’s record.
But the question in 2004–06 was not whether procedures existed.
It was whether the procedures were being followed during construction.
2. The River-Crossing Strategy
Before construction, Sakhalin Energy developed a river-crossing strategy with external input.
According to Shell’s own description, each crossing was categorised according to potential impact. Contractors working on higher-risk rivers were required to employ lower-impact methods. These included carrying out work when sensitive rivers were frozen or at low flow and, where appropriate, using horizontal directional drilling to avoid excavating directly through the riverbed. (Shell)
On paper, this was recognisably a risk-management system.
Identify the sensitive river.
Select the least damaging practical method.
Restrict the construction window.
Control sediment.
Restore the bank and channel.
Monitor compliance.
The difficulty was execution.
3. Shell’s Admission: Contractors Did Not Always Comply
The crucial passage appears in The Shell Sustainability Report 2005.
Shell recorded that contractors had not always complied with the river-crossing strategy during the winter of 2004–05 and that Sakhalin Energy stopped the winter programme after becoming aware of the problem. (Shell)
This deserves careful treatment.
Shell did not say that every crossing was defective.
It did not say that salmon populations had been destroyed.
It did not admit systematic criminal violations.
What it admitted was operationally significant enough:
the environmental control system had not been consistently followed by contractors.
For a project spanning more than a thousand watercourses, that was not a trivial management problem.
4. What Sakhalin Energy Did Next
Shell’s report says the response was substantial.
For the following winter programme, the river-crossing strategy was revised. Monitoring was tightened. Individual action plans were prepared for remaining sensitive crossings. Contractors were retrained. Contracts were amended to include incentives and penalties linked to compliance. Independent, technically qualified external observers were also invited to monitor sensitive crossings, with reports and photographs made public. (Shell)
Those measures are evidence of corrective action.
They are also evidence of the seriousness with which the earlier failure was regarded.
Companies do not normally retrain contractors, rewrite contractual incentives, prepare individual crossing plans and introduce external observation unless the existing control mechanism has proved inadequate in some material respect.
That last sentence is commentary.
The underlying measures are Shell’s own documented record.
5. The External Observers Did Not Produce a Perfect Picture
The subsequent observer process generated further controversy.
A May 2006 presentation by Sakhalin Environment Watch, based in part on Sakhalin Energy’s own published external-observer records, highlighted individual crossings where non-compliances were recorded.
One example concerned the Chernaya River crossing in December 2005. The presentation reproduced an observer report describing six non-compliances involving monitoring, dam installation and erosion-control measures. Another example, at the Bolotnaya River, described an episode in which stream flow disappeared for several days across part of the channel following excavation work. (国際環境NGO FoE Japan)
These were environmental-group interpretations of project records and should be identified as such.
They do not establish, by themselves, that permanent ecological damage occurred.
But they matter for another reason.
The revised system did not reveal that every contractor had suddenly achieved perfect compliance.
It generated documented examples of continuing problems.
6. Salmon Made the Timing Important
Pacific salmon return to freshwater systems to reproduce, making river condition and construction timing particularly sensitive.
Shell’s own project reporting therefore treated salmon spawning as a biodiversity issue requiring mitigation. (Shell)
Critics argued that sedimentation, interrupted flows and poorly timed construction could damage spawning habitat or eggs already present in river gravels. Sakhalin Environment Watch accused the project of failing to observe some of its own mitigation commitments and argued that certain crossing methods placed salmon habitat at unnecessary risk. (国際環境NGO FoE Japan)
The later UK Parliamentary record went further.
Evidence submitted to the Environmental Audit Committee stated that Sakhalin Energy had failed to identify all sensitive rivers before construction, had not adequately surveyed habitat associated with the endangered Sakhalin taimen, and had failed to implement some mitigation measures, including simultaneous pipeline crossings and avoidance of spawning periods. The same parliamentary material attributed those criticisms to regulatory inspections, consultants and NGO monitoring. (UK Parliament)
Again, evidential categories matter.
That Parliamentary document records allegations and evidence placed before Parliament.
It is not itself a criminal conviction or a judicial finding that every allegation was proved.
7. The Lenders Were Watching the Rivers Too
As with the whale issue, environmental performance became inseparable from project finance.
The UK Export Credits Guarantee Department had been considering approximately US$650 million of support connected with Sakhalin II. It classified the project as potentially sensitive and high-impact and worked with other export-credit agencies and financial institutions to assess whether the project’s environmental documentation met international standards. (UK Parliament)
The Parliamentary record later stated that this group concluded the project did not fully meet some relevant World Bank Group guidelines and that further action by Sakhalin Energy would be required. (UK Parliament)
By late 2005, Sakhalin Energy had produced a much larger environmental and social documentation package, including more than 2,000 specific commitments. Independent consultants were engaged to monitor implementation for the prospective financial institutions. (UK Parliament)
The important point was no longer simply:
What had Sakhalin Energy promised?
It had become:
Were those promises being carried out in the field?
8. The Parliamentary Record Later Answered That Question Uneasily
The evidence supplied to the House of Commons Environmental Audit Committee is unusually significant.
It states that because construction had already begun, ECGD and other financial institutions had to monitor not only whether the project’s plans met international standards, but whether commitments made in 2003 and 2005 were actually being observed.
Then comes the important conclusion:
By 2006–07, according to the Parliamentary account, it was becoming clear that this was not always the case. Sakhalin Energy subsequently published a Remedial Action Plan in August 2007 specifying further actions concerning the onshore pipelines. (UK Parliament)
That finding substantially reinforces Shell’s earlier admission.
The contractor-compliance issue was not merely a short-lived winter-2004 problem that vanished once work resumed.
Questions about implementation persisted into later lender scrutiny.
9. September 2006: The Russian State Moves In
By September 2006, the dispute had escalated far beyond contractor management.
Russia’s Ministry of Natural Resources moved to withdraw or suspend the project’s environmental approval, citing inadequate environmental safeguards.
Contemporaneous reporting said construction could be halted until revised environmental measures were submitted and approved. Sakhalin Energy strongly rejected the legal basis for the move and maintained that the issues identified by regulators did not justify revoking the project’s environmental approval. (Oil & Gas Journal)
The regulator’s complaints included river damage.
Reuters reported that Russian Natural Resources Minister Yuri Trutnev alleged that work had been carried out without adequate protective structures and that soil had been dumped into riverbeds. Rosprirodnadzor also argued that deforestation, erosion and soil disturbance associated with pipeline construction increased mudslide risks. (Royal Dutch Shell Plc .com)
Another Reuters report quoted Russian environmental official Oleg Mitvol calling for action over every damaged river while Shell’s senior executive in Russia, Chris Finlayson, defended Sakhalin II as a world-class project and said the company had nothing to hide or be ashamed of. (Royal Dutch Shell Plc .com)
Both sides therefore went on the record.
Russian officials alleged serious environmental violations.
Shell denied that the problems justified the regulatory assault.
10. The Political Question Cannot Be Ignored
There is a danger in telling this episode as though environmental regulation operated in a political vacuum.
It did not.
Contemporaneous journalists, diplomats and analysts openly questioned whether Moscow’s sudden environmental zeal was connected with a broader effort to renegotiate the commercial position of foreign investors and strengthen Gazprom’s role in the project. Reuters recorded this suspicion directly, while Shell itself argued that the regulatory process was being used unfairly. (Royal Dutch Shell Plc .com)
Oil & Gas Journal similarly reported that observers suspected Russian pressure was intended to improve the prospects of a Russian company gaining a stake in Sakhalin II. (Oil & Gas Journal)
The later ownership outcome makes that suspicion historically important.
But political motive does not automatically erase environmental evidence.
Those are separate questions.
It is entirely possible for genuine environmental failures to exist while a government simultaneously exploits them for commercial or geopolitical leverage.
The documentary record does not require us to choose one explanation and discard the other.
11. The Court Story Was Complicated
The Russian regulatory battle itself moved in and out of court.
Sakhalin Energy pointed out in September 2006 that the project’s environmental approval had survived a Russian court challenge as recently as 29 August 2006. Contemporary reporting says Russian authorities later withdrew a separate Moscow action seeking revocation of the approval after the Natural Resources Ministry acted administratively instead. (Royal Dutch Shell Plc .com)
That procedural history matters.
There was no Russian court judgment in September 2006 establishing that Shell had committed every environmental violation alleged by Rosprirodnadzor.
Nor did the earlier court victory prove that the subsequent environmental allegations were false.
The legal and administrative processes were moving on different tracks.
12. The British Court Record Adds a Different Kind of Scrutiny
Sakhalin II later appeared before the English High Court for a different reason.
In Export Credits Guarantee Department v Friends of the Earth, the dispute concerned whether UK government communications about the environmentally sensitive project should be disclosed under the Environmental Information Regulations.
Mr Justice Mitting dismissed ECGD’s appeal, leaving in place the Information Tribunal’s order requiring disclosure of the requested government material. (CaseMine)
The High Court did not decide whether river crossings had damaged salmon.
It did not decide whether Sakhalin Energy had broken Russian environmental law.
It did not determine whether Russia’s 2006 intervention was politically motivated.
Its significance is narrower but still relevant.
The financing and environmental scrutiny surrounding Sakhalin II had become important enough to generate litigation over what the British Government should reveal about its own internal assessment of the project. (CaseMine)
13. What Shell’s Own Document Proves
Strip away the rhetoric from both sides and Shell’s Sustainability Report leaves us with several hard facts.
The pipeline crossed more than 1,000 rivers and streams.
Approximately 180 were regarded as potentially environmentally sensitive.
A specialist river-crossing strategy existed.
Contractors were required to follow particular low-impact methods.
Contractors did not always comply during the 2004–05 winter programme.
Sakhalin Energy stopped that programme after discovering the problem.
It revised the strategy, retrained contractors, strengthened monitoring, rewrote contractual incentives and introduced independent observation. (Shell)
None of those propositions depends upon an NGO accusation.
They come from Shell.
14. What the Wider Record Adds
The wider record shows why the issue did not end there.
External observers continued to document non-compliances at individual crossings.
Environmental organisations continued to allege damage to salmon-bearing rivers.
Russian regulators escalated those allegations dramatically in 2006.
Potential lenders continued examining whether environmental commitments were actually being implemented.
UK Parliamentary evidence later recorded that by 2006–07 it had become apparent that commitments were not always being observed, leading to a Remedial Action Plan addressing the onshore pipelines. (国際環境NGO FoE Japan)
At the same time, credible contemporary observers believed the Russian state was using environmental enforcement as leverage in a much larger struggle over ownership and economics. (Royal Dutch Shell Plc .com)
Both parts of that record belong in the archive.
Documentary Findings
Established by Shell’s own published record
Sakhalin II’s onshore pipelines crossed more than 1,000 rivers and streams.
Around 180 were identified as potentially environmentally sensitive.
Sakhalin Energy had a formal river-crossing strategy requiring special construction methods at higher-risk sites.
Contractors did not always comply with that strategy during the winter of 2004–05.
Sakhalin Energy stopped the winter programme after learning of the failures.
The company subsequently revised procedures, retrained contractors, changed contractual incentives, increased monitoring and introduced independent external observers. (Shell)
Established by subsequent UK government evidence
ECGD and other prospective financial institutions concluded that Sakhalin II initially did not fully meet some World Bank Group guidelines.
Sakhalin Energy subsequently produced a much larger environmental and social action framework containing thousands of commitments.
The financial institutions monitored whether those commitments were being implemented.
The Parliamentary record states that by 2006–07 it was becoming clear that implementation was not always occurring as promised and that an onshore-pipeline Remedial Action Plan followed in 2007. (UK Parliament)
Established by contemporaneous reporting
Russian regulators alleged damage to rivers, improper soil disposal, erosion and other environmental violations in 2006.
Shell and Sakhalin Energy disputed the allegations and challenged the legal basis for revoking environmental approval.
Contemporary analysts and diplomats also suspected the environmental campaign was being used to pressure the foreign consortium in negotiations involving Russian strategic control of the project. (Royal Dutch Shell Plc .com)
Established by the court record
A Russian court had upheld the project’s environmental approval shortly before the September 2006 regulatory escalation, according to contemporaneous reports.
A subsequent Russian action seeking revocation was withdrawn when the Ministry proceeded administratively.
The English High Court later upheld disclosure of UK government material concerning the environmental and financing scrutiny of Sakhalin II.
None of those judicial proceedings established that Shell had caused the specific ecological damage alleged by critics. (Oil & Gas Journal)
Not established
The surviving record does not establish that every Sakhalin II river crossing was defective.
It does not establish that contractor non-compliance caused island-wide destruction of salmon populations.
It does not establish that every allegation made by Rosprirodnadzor was correct.
It does not establish that Russia’s environmental intervention was purely environmental.
And it would be equally misleading to argue that evidence of Russian political pressure proves that the contractor failures acknowledged by Shell never happened.
Commentary
The most instructive sentence in this entire file may be one of the least dramatic:
Contractors did not always comply.
That is where corporate sustainability promises encounter physical reality.
Shell could produce a strategy.
Sakhalin Energy could classify the rivers.
Experts could design low-impact crossing techniques.
Lenders could require commitments.
But eventually somebody operating an excavator had to cross the river.
And that is the point at which a multinational company’s environmental policy becomes either real or merely documentary.
The response described by Shell — stopping work, rewriting procedures, retraining contractors, changing contractual incentives and introducing independent observers — demonstrates that Sakhalin Energy recognised the weakness and attempted to correct it. (Shell)
That deserves to be recorded.
So does what happened next.
The revised process continued to produce reports of non-compliance.
Financial institutions continued asking whether commitments were being implemented.
Russian regulators eventually arrived with accusations serious enough to threaten the entire project.
And behind the environmental dispute was an increasingly obvious geopolitical struggle over who would control Sakhalin II. (国際環境NGO FoE Japan)
The rivers therefore became more than waterways.
They became evidence.
Evidence for environmental campaigners.
Evidence for prospective lenders.
Evidence for Russian regulators.
Evidence for Shell that its contractor-management system needed strengthening.
And, eventually, evidence deployed in a confrontation capable of altering ownership of one of the world’s largest energy projects.
The crucial historical distinction is this:
Environmental shortcomings were real enough for Shell to acknowledge and remediate.
Whether those shortcomings subsequently justified the scale and timing of the Kremlin’s intervention is an entirely different question.
That is where the next archive file begins.
Source Record
The principal source for this instalment is The Shell Sustainability Report 2005, particularly its Sakhalin II river-crossing section. Supporting records include Sakhalin Energy material concerning river monitoring and restoration; UK Export Credits Guarantee Department evidence subsequently supplied to the House of Commons Environmental Audit Committee; EBRD documentation concerning Sakhalin II environmental and financing scrutiny; contemporaneous Reuters and Oil & Gas Journal reporting on the 2006 Russian regulatory intervention; environmental-monitoring material cited by Sakhalin Environment Watch; and Export Credits Guarantee Department v Friends of the Earth, the 2008 High Court disclosure case. (Shell)
Archive disclaimer: Shell’s acknowledgement of contractor non-compliance is not proof that every river crossing breached environmental law or caused ecological damage. Regulatory allegations are identified as allegations unless supported by a final competent finding. Parliamentary evidence records the material placed before Parliament and is not itself a criminal or civil judgment. Contemporary suspicions that Russian environmental enforcement was politically motivated are reported as contemporary assessments, not established fact.
Site wide disclaimer also applies.
Next Archive File
SLF-2007-026 — The Sakhalin Papers XVI: The Permit, the Prosecutors and Gazprom
In September 2006, the argument over rivers, forests and pipelines abruptly became a struggle over the future of the entire Sakhalin II project.
Russian environmental officials threatened suspension.
Prosecutors and regulators moved against permits.
Shell protested that the legal foundations of the project were being undermined.
Foreign governments complained.
Analysts questioned why environmental enforcement had suddenly become so ferocious.
And waiting in the wings was Gazprom.
Within months, Shell would cease to control Sakhalin Energy.
The next archive file will examine the documents and contemporary record surrounding one of the most consequential questions in the Sakhalin story:
Did Russia finally lose patience with Shell’s environmental performance — or were environmental violations the leverage through which the Kremlin forced a transfer of control?
The surviving evidence suggests the answer may not be one or the other.
It may be both.
*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, the Independent Shell Archive, 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 conjured up by internet wizz, Nick Gill.
