THE SHELL LEAKS FILES: 23 AUGUST 2026
SLF-2007-035
The Sakhalin Papers XXV: The QA/QC Warning — Rivers, Permits and the Pipeline Built Under Pressure
An anonymous insider alleged corners were being cut. Months later, the lenders’ own environmental consultant documented a substantial record of non-compliance.
Archive reference: SLF-2007-035
Collection: The Sakhalin Papers
Principal record: May 2007 Sakhalin II whistleblower material concerning quality assurance, quality control, river crossings, permits, erosion, geohazards and alleged suppression of non-conformance reports
Supporting record: Shell internal 11 May 2007 correspondence subsequently disclosed under the Data Protection Act; AEA Technology’s September 2007 Independent Environmental Due Diligence Report to prospective agency lenders; UK Parliamentary answers; Russian regulatory and prosecutorial reporting; Export Credits Guarantee Department v Friends of the Earth [2008] EWHC 638 (Admin)
Evidence standard: Where the whistleblower’s allegations overlap with findings by AEA, regulators or Parliamentary records, that overlap is identified precisely. Independent evidence of a non-compliance does not establish the source’s allegation that management deliberately cut corners, suppressed reports or acted dishonestly.
Introduction
The anonymous Sakhalin II source examined in the previous file made one allegation that was unusually testable.
The source said that proper adherence to quality assurance and quality control requirements would push pipeline construction into 2008.
That forecast proved substantially accurate.
But the source did not stop at the calendar.
In material supplied on 14 May 2007, the insider alleged that the schedule problem was being dealt with by compromising standards.
The source listed areas said to be affected:
erosion protection;
water-protection zones;
tree-felling permits;
river-crossing permits;
pipeline excavation, cover and backfill;
damage to roads;
pipeline cleaning and gauging;
engineering around seismic fault lines;
and what the source called suppression of reports of non-conforming work. (Shell News)
Those are serious accusations.
Some describe ordinary construction deficiencies.
Others imply deliberate management misconduct.
The crucial question is therefore not whether later evidence shows that Sakhalin II had environmental and engineering problems.
It plainly did.
The question is narrower and more difficult:
How much of the May 2007 QA/QC warning was independently borne out — and where does the evidence stop?
The answer is unusually revealing.
Because only a few months after the whistleblower wrote, the prospective lenders’ own independent environmental consultant produced a detailed report.
That report documented significant failures involving river crossings, erosion control, monitoring, permits, reinstatement and geotechnical work.
But it also documented corrective action.
And nowhere does it prove that Shell management deliberately ordered engineers to falsify standards or suppress inconvenient reports.
1. The Warning Was Made Before the Lenders’ Final Report
Chronology matters.
The whistleblower material was published in May 2007.
At that point, AEA Technology had already been monitoring Sakhalin II for years on behalf of prospective agency lenders, including the UK Export Credits Guarantee Department, the Japan Bank for International Cooperation and US Ex-Im.
AEA’s final due-diligence report was dated 28 September 2007.
AEA described itself as the Independent Environmental Consultant and said it had assessed Sakhalin Energy against Russian regulatory requirements, World Bank and IFC standards, lender requirements and the company’s own Health, Safety, Environment and Social Action Plan. (doczz.net)
This makes the AEA report particularly useful.
It was not written by the whistleblower.
It was not written by the Donovan website.
It was not a Russian prosecutor’s press release.
And it was not Shell public relations.
It was a technical assessment prepared for institutions considering financing the project.
2. The First Whistleblower Claim: Erosion Protection Was Inadequate
The May source alleged insufficient or absent erosion protection along rivers and embankments. (Shell News)
On this point, the subsequent AEA findings are striking.
AEA reported that implementation of temporary and permanent erosion controls since pipeline right-of-way construction began in 2004 had “fallen significantly short” of the commitments established for the project, particularly in relation to surface stabilisation. (doczz.net)
The consultant said significant deficiencies had been found in all aspects of erosion control during a May 2006 inspection and that several commitments had been materially breached.
AEA’s September 2007 summary identified:
lack of surface stabilisation;
inadequate drainage controls;
and failure to provide adequate erosion-control equipment and materials in time.
It described these shortcomings as prolonged and persistent breaches of Sakhalin Energy’s own requirements and considered their procedural and best-practice significance high. (doczz.net)
That does not prove that management deliberately ordered erosion controls to be omitted.
But the underlying technical concern is independently established.
3. The Problem Was Not Merely Historical
It would be misleading to imply that nothing improved.
AEA recorded that Sakhalin Energy introduced an enhanced erosion-control campaign in 2006.
Management structures involving Sakhalin Energy and Starstroi environmental teams were integrated.
Contractor incentive schemes were introduced.
Subsequent inspections showed progress. (doczz.net)
But AEA also said important non-compliances remained in 2007, particularly concerning surface stabilisation and final reinstatement.
It warned that the project would remain out of compliance with relevant commitments until final reinstatement was completed. (doczz.net)
So the correct finding is not:
Nothing was being done.
It is:
Serious erosion-control deficiencies had existed; remediation was under way; important shortcomings remained.
4. The River-Crossing Strategy Arrived After Construction Had Already Started
The insider’s concerns about quality control must also be viewed against the chronology of environmental planning.
AEA recorded that Sakhalin II’s final River Crossing Strategy was not completed until December 2005.
By then, 64 sensitive Group 2 and Group 3 rivers had already been crossed by at least one pipeline.
AEA also recorded that many crossings took place while earlier versions of the strategy lacked important features included in the final version. (doczz.net)
This does not establish illegality.
Draft strategies existed beforehand.
But it does establish something important about project governance.
A major part of construction preceded finalisation of the environmental framework intended to govern some of its most sensitive work.
5. Some Rivers Were Crossed Twice in Different Years
A central requirement of the revised River Crossing Strategy was to minimise the time between installing the oil pipeline and gas pipeline through the same sensitive river.
That reduced repeated disturbance.
AEA found that performance improved after the strategy was finalised.
But it also documented important exceptions.
At the end of the 2005–06 winter period, 16 sensitive Group 2 or Group 3 rivers had been crossed by only one pipeline, with the second crossing delayed until the following winter.
AEA said this contravened a specific project commitment.
It also recorded 27 sensitive rivers where more than two weeks separated the two pipeline installations. (doczz.net)
Again, the fact of non-compliance is independently documented.
The motive is not.
6. Crossings Also Took Place Outside the Preferred Period
AEA examined the timing of sensitive river crossings.
It recorded that 40 crossings in higher-sensitivity Group 3 rivers occurred outside the nominal optimum mid-winter period after the final strategy was issued.
AEA cautioned against exaggeration.
March conditions were often comparable to January or February.
Late-April crossings were of greater concern because spring flows could increase and the period began approaching sensitive salmon and taimen seasons. (doczz.net)
That distinction matters.
An archival article should not turn every crossing outside January or February into environmental damage.
But the lender consultant did confirm that the project did not always meet the intended timing framework.
7. The Monitoring System Itself Had Weaknesses
The whistleblower alleged that QA/QC procedures were being compromised.
AEA’s monitoring findings provide a substantial independent context.
During the winter 2005–06 crossing season, its observers recorded lack of adequate monitoring equipment at 83 crossings, representing 46 per cent of the crossings witnessed.
Turbidity meters had not arrived on the island until late January 2006.
Even after they arrived, AEA observed cases where too few readings were taken to satisfy project commitments, meaning peak sediment concentrations may not have been captured. (doczz.net)
AEA said the equipment problem was largely resolved by mid-February.
This is therefore a documented historical deficiency, not evidence that monitoring remained equally poor throughout the project.
But it is directly relevant to the source’s claim that the quality-control system was under strain.
8. The Consultant Recorded Multiple Types of River-Crossing Non-Compliance
AEA’s own summary of river-crossing problems reads remarkably like part of the whistleblower’s list.
The report identified examples involving:
inadequate monitoring;
insufficient sediment-control measures;
poor spoil management;
extended trenching operations;
poor excavator work;
rivers drying below crossing points;
crossings exceeding specified durations;
non-consecutive crossings;
poor bank shaping;
delayed restoration;
and poor gravel or riprap placement. (doczz.net)
Those are not anonymous allegations.
They are findings recorded by the lenders’ environmental consultant.
They do not prove deliberate misconduct.
But they demonstrate that a substantial body of non-conforming construction activity existed.
9. One Detail Is Especially Important: Non-Conformance Reports Really Existed
The whistleblower alleged suppression of reports about non-conforming work. (Shell News)
AEA independently confirms that Non-Conformance Reports — NCRs — were indeed part of the project control system.
During its May 2007 visit, AEA examined riverbank engineering using Reno mattresses.
It reported deficiencies in many of the installations inspected.
In one pipeline section, NCRs had been issued for all previously installed Reno mattresses, and AEA said those installations were to be replaced. (doczz.net)
This is an important piece of evidence.
It proves that non-conforming work was being formally identified.
But it actually complicates the whistleblower’s allegation of suppression.
At least in this example, the reports were not simply being buried.
NCRs were issued.
Corrective action was underway.
A specialist contractor had been engaged.
AEA described the quality of the replacement work it observed as encouraging. (doczz.net)
10. So Was the Source Wrong About Suppression?
Not necessarily.
But the allegation remains unproved.
The source did not merely claim that non-conformances existed.
The source alleged that reports of non-conforming work were being suppressed. (Shell News)
AEA confirms the first proposition.
It does not confirm the second.
To establish suppression would require evidence showing that NCRs were deliberately hidden, deleted, ignored, downgraded or prevented from reaching decision-makers.
No such evidence has been identified for this instalment.
Indeed, the Reno-mattress example demonstrates that at least some NCRs were being acted upon.
The strongest documentary conclusion is therefore:
A significant NCR system existed and identified defective work. Deliberate suppression of those reports is not established.
11. Permit Problems Were Real
The whistleblower alleged that river crossings were being undertaken without the required permits or authority in order to avoid delay. (Shell News)
The AEA report documents genuine permit-related problems.
During the 2005–06 season, Sakhalin Energy used flume crossing techniques at a number of rivers.
Russian authorities subsequently determined that the use of flumes fell outside the permit conditions and imposed fines.
After further discussions, agreement was reached allowing their use at specified rivers. (doczz.net)
AEA also identified a small number of temporary bridges whose centre supports or bank supports were contrary to permit conditions. (doczz.net)
Those findings are significant.
They establish actual permit non-compliance.
But they do not establish the whistleblower’s stronger allegation about motive.
AEA does not say those methods were used because management consciously decided to ignore permits to meet a schedule.
12. The Water Protection Zone Concern Also Had a Real Basis
The source specifically alleged disregard for Water Protection Zone requirements. (Shell News)
AEA’s report explains why this was technically complicated.
Under the Russian Water Code then in force, Water Protection Zones imposed restrictions on activities close to rivers, including certain storage, refuelling and maintenance activities.
AEA concluded that refuelling some horizontal-directional-drilling machinery inside Water Protection Zones had technically been prohibited under the older rules.
It also noted that handling antifreeze used for hydrotesting inside those zones created legal questions. (doczz.net)
However, the report adds crucial context.
AEA said approvals were obtained for use of glycol at the relevant crossings and that construction permits had been received.
It also reported that Water Protection Zones were generally respected during the later 2006–07 crossing campaign, although minor non-compliances were identified. (doczz.net)
So the source had identified a genuine area of compliance difficulty.
But the evidence does not support a sweeping conclusion that water-protection law was simply ignored.
13. Some Russian Authorities Went Further
Russian regulators and prosecutors used much harsher language.
In September and October 2006, authorities accused Sakhalin Energy and contractors of environmental violations involving rivers, erosion, logging and pipeline construction.
Russian reporting later said prosecutors had identified more than 100 breaches across environmental, migration and labour law and alleged serious damage to salmon-spawning rivers. (Sputnik Globe)
The Russian Audit Chamber also reported alleged environmental and technical violations, while Natural Resources Minister Yuri Trutnev referred publicly to possible illegal forest cutting. (Royal Dutch Shell Plc .com)
Those are official regulatory allegations.
They are not neutral judicial findings.
Their political context cannot be ignored.
At precisely the same time, the Russian state was exerting enormous pressure over the ownership and economics of Sakhalin II.
14. Shell Denied Breaking Russian Environmental Law
Shell and Sakhalin Energy did not accept the Russian authorities’ broad accusations.
Following the September 2006 environmental-permit confrontation, Sakhalin Energy said no applicable law had been violated and that environmental issues were being addressed with the authorities.
It also pointed out that the project approval had recently survived a Russian court challenge. (Offshore Magazine)
Contemporaneous reporting simultaneously recorded widespread suspicion that environmental enforcement was being used as leverage to force Gazprom into the project. (Royal Dutch Shell Group .com)
That geopolitical context remains essential.
But the AEA findings prevent the opposite simplification.
Evidence that Moscow had political motives does not mean every environmental problem was invented.
15. The Lenders’ Report Found Real Breaches Without Adopting Moscow’s Rhetoric
This is where the AEA report becomes especially valuable.
It did not echo the most dramatic Russian accusations.
Instead, it catalogued individual issues.
Some were resolved.
Some were improving.
Some remained outstanding.
Some were regarded as procedurally serious but environmentally moderate.
That analytical approach gives the report considerable evidential value.
AEA explicitly concluded that erosion-control measures had fallen short of project requirements and had caused sediment releases into rivers and wetlands.
It also said improvements had occurred after summer 2006. (doczz.net)
That is very different from either:
Everything was environmentally catastrophic.
or:
Nothing was wrong and the entire controversy was political.
The evidence supports neither extreme.
16. The Whistleblower’s Concern About Backfill and Excavation Also Finds Partial Support
The source alleged insufficient excavation depth, cover and backfill material. (Shell News)
AEA recorded instances during river crossings where pipe strings could not immediately be lowered because trenches were insufficiently deep and additional excavation was required.
It also documented backfill delays and construction difficulties where unexpected ground conditions were encountered. (doczz.net)
This establishes that trench-depth and backfill problems occurred.
It does not establish that the finished pipeline was systematically buried below legal or engineering requirements.
Nor does it prove that management knowingly accepted inadequate cover.
The source’s broad concern has partial technical corroboration.
The stronger allegation remains unproved.
17. The Seismic-Fault Concern Was Certainly Not Imaginary
The whistleblower also alleged inadequate engineering solutions where the pipeline crossed seismic fault zones. (Shell News)
Sakhalin is geologically difficult terrain.
AEA’s earlier reviews identified uncertainties about fault locations, deformation patterns and potential surface rupture along the pipeline route.
The consultant said early investigations were insufficient to characterise some fault-crossing hazards confidently and recommended additional geological and tectonic work. (doczz.net)
Landslides presented another major concern.
AEA described the potential consequences of static and earthquake-triggered ground movement for pipeline integrity and noted that early work was still being undertaken to characterise landslide hazards through the Makarov Mountains. (doczz.net)
This establishes the technical seriousness of the problem.
But once again, the later record also shows mitigation.
18. Additional Geohazard Work Was Done
AEA said Sakhalin Energy subsequently carried out further geological and geomorphological investigations.
The revised geohazard assessment was considered to provide a reasonable framework for understanding seismic and landslide risks and identifying mitigation.
The report also describes engineering approaches available at fault crossings, including changes in wall thickness, crossing angle, trench design and packing to allow controlled pipeline movement. (doczz.net)
Accordingly, the source’s suggestion that seismic fault crossings required serious attention is supported.
The source’s stronger implication that the engineering remained knowingly inadequate is not.
19. Russian Inspectors and AEA Sometimes Identified the Same Problems
AEA’s report is particularly significant where it compares its own findings with those of Russian inspectors.
The consultant said regulatory inspections in 2006 had identified concerns involving:
spoil-tip design;
pipeline design in landslide and mudslide areas;
culvert and bridge design;
riverbank protection;
and drainage controls.
AEA stated that those regulatory concerns were broadly consistent with findings made by its own continuous monitors. (doczz.net)
That overlap matters.
It demonstrates that at least part of the Russian environmental case rested on technical issues independently visible to the lenders’ consultant.
It does not establish that every Russian allegation was justified.
20. Road Damage Was Also a Genuine Community Issue
The May source alleged damage to federal roads through inadequate maintenance and heavy-vehicle operations. (Shell News)
AEA later recorded persistent community complaints about road conditions and road safety associated with project traffic, continuing into early 2007.
The consultant also said Sakhalin Energy had undertaken substantial road upgrades and that later evidence showed company liaison staff working to mitigate road impacts. (doczz.net)
So there is independent evidence that project traffic and road condition were real community concerns.
There is not enough evidence here to establish the whistleblower’s particular allegation about unlawful use of heavy vehicles during thaw periods.
21. Tree-Felling Allegations Are Harder to Resolve
The whistleblower specifically alleged tree felling without required permits. (Shell News)
Russian officials publicly alleged illegal forest cutting during the 2006 regulatory campaign.
The Russian Audit Chamber and environmental authorities treated forest damage as part of their case against the project. (Royal Dutch Shell Plc .com)
But this instalment has not located an independent lender finding establishing the precise whistleblower proposition:
that project personnel deliberately cut trees without required permits in order to save time.
Accordingly, this issue remains:
supported by related regulator allegations, but not independently established in the specific form alleged by the source.
22. Parliament Was Already Watching the Rivers
British Parliamentary records provide another independent checkpoint.
In June and July 2006, MPs asked detailed questions about Sakhalin II river crossings, salmon habitat and whether crossings were occurring within the designated winter construction period.
Government answers stated that the project’s river work was being monitored by potential lenders including ECGD and the EBRD, together with independent environmental consultants.
DEFRA also referred specifically to Sakhalin Energy’s River Crossing Strategy and monitoring information. (Hansard)
This does not prove non-compliance.
It establishes that river-crossing performance was already considered significant enough to generate formal Parliamentary scrutiny before the May 2007 whistleblower warning.
23. The Independent Lender Review Later Reached Parliament Too
In evidence subsequently published by the House of Commons Environmental Audit Committee, Sakhalin II was described as approximately 90 per cent complete by November 2007.
The submission cited AEA’s lender review and raised concerns about failures to implement mitigation measures at pipeline river crossings. (UK Parliament)
Again, this was evidence submitted to Parliament rather than a Parliamentary finding that every allegation was correct.
But the same technical issues had now moved through several documentary layers:
project monitoring;
lender due diligence;
NGO submissions;
and Parliamentary publication.
24. The QA/QC Warning Was Therefore Not Detached From Reality
By now the pattern is clear.
The May 2007 insider alleged that the project schedule was being pursued at the expense of proper quality and environmental controls.
The strongest form of that allegation — deliberate management corner-cutting — remains unproved.
But many of the individual technical problems named by the source were independently documented:
erosion deficiencies;
river-restoration problems;
inadequate monitoring;
permit conflicts;
crossing-timing failures;
non-conforming riverbank works;
trench and backfill difficulties;
Water Protection Zone issues;
road concerns;
and real uncertainty over geohazards. (doczz.net)
This is more than a coincidence of vocabulary.
It demonstrates that the whistleblower was describing genuine fault lines within the project.
25. But the AEA Report Also Shows Why the Insider Must Not Be Treated as Infallible
The same report that documents non-compliance also records extensive remedial work.
Monitoring equipment arrived.
River-crossing performance improved.
Specialist contractors were brought in.
NCRs were raised.
Defective Reno mattresses were scheduled for replacement.
Erosion campaigns were implemented.
Water Protection Zone approvals were obtained in relevant cases.
Additional geohazard investigations were carried out.
Road-impact mitigation improved. (doczz.net)
This is important because it contradicts any crude narrative that the entire project organisation simply ignored quality control.
The evidence shows a troubled system.
It also shows a functioning corrective system.
Both facts belong in the archive.
26. The Most Serious Allegation Remains the Least Proven
The whistleblower’s most serious proposition was not that defects existed.
Large construction projects generate defects.
The serious accusation was that management knew standards were being compromised and intentionally accepted that position because the proper construction schedule was unacceptable.
That allegation would require evidence of intent.
Internal instructions.
Suppressed reports.
Management orders overriding inspectors.
Documents linking the schedule explicitly to acceptance of known non-conforming work.
No such authenticated document has been located for this instalment.
AEA’s findings demonstrate non-compliance.
They do not establish a corporate policy of knowingly violating requirements.
27. The High Court Did Not Decide the Engineering Dispute
Sakhalin II later entered the English High Court record in Export Credits Guarantee Department v Friends of the Earth [2008] EWHC 638 (Admin).
Mr Justice Mitting recorded that approximately $650 million in UK export-credit support had been sought and that the project raised potentially significant environmental issues.
He also recorded that the application was ultimately withdrawn before a financing decision was made. (vLex)
The case concerned access to internal government environmental information.
The court did not determine:
whether Shell had breached Russian pipeline regulations;
whether particular river crossings were defective;
whether QA/QC reports were suppressed;
or whether the anonymous source’s allegations were correct.
The judgment belongs in the transparency record.
It is not an engineering verdict.
28. Prediction and Corroboration Must Still Be Kept Separate
One fact does strengthen the historical significance of the whistleblower material.
The source predicted that a properly completed pipeline programme extended into 2008.
That prediction proved substantially right.
As previous files have documented, pipeline completion and year-round oil production did not arrive until late 2008.
That gives weight to the proposition that the source had real knowledge of the project schedule.
But the logic must stop there.
Accurate scheduling knowledge does not prove deliberate misconduct.
Technical access does not prove every accusation.
A good documentary archive must resist both vindication-by-association and dismissal-by-association.
Claim Against Record
Whistleblower claim: erosion protection was inadequate.
Independent record: AEA documented material and persistent shortcomings in erosion control, including inadequate surface stabilisation, drainage and equipment. (doczz.net)
Assessment: Strongly supported as a technical concern. Deliberate omission to accelerate schedule not proved.
Whistleblower claim: Water Protection Zone requirements were being ignored.
Independent record: AEA identified activities that conflicted technically with earlier Water Protection Zone restrictions and recorded minor later non-compliances, while also documenting approvals and permits in relevant cases. (doczz.net)
Assessment: Partially supported. Blanket disregard not established.
Whistleblower claim: rivers were being crossed without required permits or authority.
Independent record: AEA recorded that Russian authorities found flume crossing techniques outside permit conditions and imposed fines; it also recorded some bridge configurations contrary to permit conditions. (doczz.net)
Assessment: Permit non-compliance established in specific cases. Deliberate permit avoidance to save time not proved.
Whistleblower claim: excavation, cover and backfill were inadequate.
Independent record: AEA recorded insufficient trench depth and backfill delays at some crossings. (doczz.net)
Assessment: Specific construction difficulties corroborated. Systematic acceptance of inadequate pipeline burial not established.
Whistleblower claim: riverbank engineering was deficient.
Independent record: AEA found deficiencies in Reno-mattress installations and recorded that NCRs had been issued for all such installations in one section, with replacement planned. (doczz.net)
Assessment: Strongly supported as a localised quality problem.
Whistleblower claim: reports of non-conforming work were suppressed.
Independent record: AEA confirms the existence of NCRs and documents corrective action on some of them.
Assessment: Not established. The available evidence proves non-conformance reporting existed, not that it was suppressed.
Whistleblower claim: seismic-fault engineering was inadequate.
Independent record: AEA recorded early uncertainty over fault crossings and landslide hazards and called for further investigation. It later considered the revised framework reasonable. (doczz.net)
Assessment: Underlying hazard and early uncertainty established; inadequate final engineering not established.
Whistleblower claim: road damage was occurring.
Independent record: AEA recorded persistent community complaints over project-related road conditions and later mitigation. (doczz.net)
Assessment: Broadly supported as a community-impact issue. Specific alleged causes remain unproved.
Whistleblower claim: tree felling occurred without permits to avoid delay.
Independent record: Russian authorities alleged illegal forest cutting during their enforcement campaign. (Royal Dutch Shell Plc .com)
Assessment: Related official allegations existed. The specific whistleblower claim and motive are not independently established here.
Documentary Findings
Established
The May 2007 source alleged specific QA/QC and regulatory deficiencies involving erosion, river crossings, permits, Water Protection Zones, pipeline burial, roads, seismic areas and non-conforming work. (Shell News)
Shell’s internal correspondence demonstrates that the company was aware of the developing allegations and sought a measured response from Sakhalin Energy. (Shell News)
AEA Technology acted as independent environmental consultant for prospective agency lenders and assessed Sakhalin II against Russian law, international standards, lender requirements and the project’s own HSES commitments. (doczz.net)
AEA found significant historical and continuing shortcomings in erosion control. (doczz.net)
AEA documented numerous river-crossing non-compliances involving monitoring, sediment control, timing, construction method and restoration. (doczz.net)
AEA recorded that 64 sensitive rivers had already been crossed before finalisation of the River Crossing Strategy. (doczz.net)
AEA documented specific permit conflicts and fines concerning river-crossing techniques. (doczz.net)
AEA confirmed the use of Non-Conformance Reports and documented replacement of defective riverbank engineering in one section. (doczz.net)
AEA identified early uncertainty concerning seismic fault crossings and landslide risks and later documented additional technical investigation. (doczz.net)
UK Parliament had already subjected the river-crossing programme to formal scrutiny in 2006. (Hansard)
Supported in substance but not in alleged motive
The source’s broad contention that the project faced serious QA/QC, environmental and regulatory problems is strongly supported by later independent technical evidence.
The source’s concern that permit and river-crossing compliance problems existed is supported in specific instances.
The source’s concern that some riverbank work was non-conforming is directly supported.
The source’s concern that erosion controls were inadequate is strongly supported.
The source’s concern that fault crossings and landslide areas required substantial engineering attention is supported.
What the independent evidence does not establish is that Shell or Sakhalin Energy deliberately created those deficiencies in order to meet a politically or commercially imposed schedule.
Not established
It is not established that Shell management ordered corners to be cut.
It is not established that QA/QC personnel were instructed to approve defective work.
It is not established that Non-Conformance Reports were systematically suppressed.
It is not established that pipeline cover and backfill were knowingly accepted below final engineering requirements.
It is not established that tree-felling permits were deliberately bypassed to accelerate construction.
It is not established that every river crossing lacking perfect compliance was unlawful.
It is not established that final engineering at seismic faults was inadequate.
It is not established that Russian regulators’ entire case was technically justified or politically neutral.
And no located court judgment establishes the whistleblower’s central allegation of deliberate management compromise.
Commentary
The May 2007 source now looks considerably more interesting than an anonymous critic throwing accusations at a troubled project.
Strip away the false Greer identity.
Strip away the rhetoric.
Strip away the allegations of motive.
What remains is a technical checklist.
Erosion.
River-crossing timing.
Monitoring.
Permits.
Water Protection Zones.
Backfill.
Non-conformance reports.
Geohazards.
Roads.
Months later, the lenders’ environmental consultant was discussing many of the same subjects — and documenting genuine shortcomings.
That matters.
It suggests the insider was operating inside a recognisable technical reality.
But the AEA report also prevents the source from being turned into an oracle.
The same report shows inspectors raising NCRs.
Defective work being replaced.
Specialists being added.
Permit issues being regularised.
Erosion campaigns being introduced.
Monitoring improving.
Geohazard investigations expanding.
This was not a project without quality control.
It was a project whose quality-control system was under extraordinary pressure and sometimes failed to meet its own commitments.
That is a different proposition.
And it is the proposition the documentary record supports most strongly.
There is also a broader lesson here.
The most powerful evidence against a megaproject is often not the most sensational allegation.
It is the spreadsheet of small failures.
One crossing too slow.
One bridge outside permit conditions.
One trench too shallow.
One erosion barrier missing.
One monitor absent.
One river disturbed twice.
One NCR requiring an installation to be replaced.
Individually, such matters can look mundane.
Collectively, they reveal the operational strain inside a project attempting to build hundreds of kilometres of pipeline across forests, wetlands, salmon rivers, mountains, fault zones and some of Russia’s most difficult terrain.
That strain is established.
Whether senior management deliberately converted it into a policy of cutting corners is not.
The distinction remains decisive.
Source Record
The principal whistleblower record is the May 2007 Sakhalin II material preserved in the Donovan archive and associated DPA files.
The 14 May source specifically alleged compromised erosion protection, permit compliance, Water Protection Zone practice, pipeline cover and backfill, road maintenance, geohazard engineering and suppression of non-conforming work reports. (Shell News)
Shell’s internal 11 May 2007 correspondence, subsequently supplied through Data Protection Act disclosure, records the company’s reaction to the developing Sakhalin article and its request for a measured response from Shell and Sakhalin Energy personnel. (Shell News)
The most important independent technical source is AEA Technology’s Independent Environmental Due Diligence Report, dated 28 September 2007.
AEA stated that it was acting as Independent Environmental Consultant for prospective agency lenders and assessed the project against Russian regulatory requirements, World Bank and IFC standards, lender requirements and the Sakhalin Energy HSES Action Plan. (doczz.net)
Its findings include material erosion-control breaches, extensive river-crossing compliance issues, deficiencies in monitoring, permit conflicts, NCRs concerning riverbank engineering, unfinished reinstatement and geotechnical concerns associated with fault and landslide areas. (doczz.net)
The UK Parliamentary record demonstrates that Sakhalin II river crossings and salmon habitat were already under formal scrutiny in 2006 and that prospective lenders and their environmental consultants were actively monitoring pipeline construction. (Hansard)
Russian regulatory and prosecutorial records are used only to establish the allegations those authorities made at the time. Their broader environmental case coincided with the geopolitical struggle over Gazprom’s entry into Sakhalin II and must therefore be treated separately from independent technical findings. (Royal Dutch Shell Group .com)
The English judicial record remains Export Credits Guarantee Department v Friends of the Earth [2008] EWHC 638 (Admin). It records the environmental sensitivity of Sakhalin II and the proposed UK export-credit involvement but does not adjudicate the individual QA/QC allegations examined here. (vLex)
Archive disclaimer: This instalment distinguishes independently documented construction and environmental non-compliances from allegations of intentional misconduct. Evidence that erosion, permit, river-crossing, monitoring or engineering problems existed does not establish that Shell or Sakhalin Energy deliberately ordered standards to be compromised or reports suppressed. No judicial finding establishing such deliberate conduct has been identified.
Site wide disclaimer also applies.
Next Archive File
SLF-2007-036 — The Sakhalin Papers XXVI: The NCR Trail — What the Non-Conformance Reports Actually Tell Us
The whistleblower used one phrase that deserves its own investigation:
“non-conforming work.”
AEA later confirmed that Sakhalin Energy had a formal Non-Conformance Report system.
And the lenders’ consultant gave at least one unusually concrete example.
In Pipeline Section 3, NCRs had been issued for every previously installed Reno mattress inspected in that category, with the defective riverbank protection scheduled for replacement. (doczz.net)
That raises a new set of documentary questions.
How did Sakhalin Energy define a non-conformance?
Who could raise an NCR?
How many were issued on the pipeline project?
Which concerned environmental requirements and which concerned engineering quality?
What happened after an NCR was raised?
Were defective works repaired?
Were NCRs ever closed without full remediation?
And most importantly, is there any documentary evidence supporting the whistleblower’s allegation that some non-conformance reports were ignored or suppressed?
SLF-2007-036 will follow the NCR paper trail — separating the existence of defective work from the much more serious allegation that the system designed to expose it was deliberately overridden.
*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.
