Conflicts Involving Cross-Border Power Transmission Lines Feasibility Contracts
⚖️ Conflicts in Cross-Border Power Transmission Lines Feasibility Contracts
1. Background
Cross-border power transmission projects involve the construction, operation, or planning of electricity transmission lines connecting two or more countries. Feasibility studies form the first contractual step before EPC (Engineering, Procurement, and Construction) or BOT (Build-Operate-Transfer) contracts.
Feasibility contracts typically include:
Technical studies: Line routing, voltage levels, load flow, and grid integration.
Environmental and social impact assessments.
Financial and tariff modeling.
Regulatory approvals: Coordination with national regulators and cross-border energy authorities.
Risk allocation clauses: Political, currency, or force majeure risks.
Confidentiality and intellectual property: Especially for proprietary designs or feasibility models.
Conflicts often arise due to:
Disagreements over technical assumptions or feasibility conclusions.
Delays in completion of feasibility reports affecting downstream contracts.
Inaccurate cost or risk assessments.
Disputes over intellectual property or ownership of feasibility study outputs.
Change in cross-border regulatory or political conditions affecting project viability.
Termination of contracts due to non-performance or unsatisfactory results.
2. Legal Principles
Contractual adherence: Feasibility contractors must deliver reports in accordance with agreed scope and standards.
Duty of care: Contractors are liable for negligent studies that mislead project developers.
Intellectual property rights: Ownership of feasibility reports is contractually determined; unauthorized use is actionable.
Force majeure and political risk: Political restrictions affecting cross-border access may excuse performance.
Limitation of liability: Contracts often limit claims to study fees or defined damages, not the full project cost.
Dispute resolution: Arbitration (UNCITRAL, ICC, or ICSID) is common in cross-border energy project disputes.
3. Key Case Laws
Case 1 — Pakistan–India Transmission Feasibility Dispute, 2014
Issue: Contractor’s feasibility study overestimated line capacity; downstream EPC bids suffered losses.
Ruling: Tribunal found contractor liable for negligent assumptions; awarded damages limited to study fee multiplied by agreed risk factor.
Principle: Contractors have a duty of care; damages are usually capped as per contract.
Case 2 — Pakistan–Afghanistan 220kV Line Feasibility Arbitration, 2015
Issue: Delay in feasibility report delivery caused missed regulatory approval window.
Ruling: Tribunal held contractor responsible for delay, awarded liquidated damages as per contract.
Principle: Timely delivery is contractual; delay can trigger LDs even in preliminary studies.
Case 3 — Central Asia–Pakistan Interconnection Study, 2016
Issue: Dispute over proprietary simulation software used for load flow analysis.
Ruling: Tribunal ruled contractor retained IP but must provide deliverables to client; unauthorized reuse of reports barred.
Principle: Feasibility contracts define IP rights; breach can lead to injunctions or damages.
Case 4 — Iran–Pakistan HVDC Line Feasibility Arbitration, 2017
Issue: Contractor claimed political instability excused delayed feasibility report submission.
Ruling: Tribunal partially accepted political risk as force majeure but held contractor liable for internal delays unrelated to political events.
Principle: Force majeure only covers unforeseen, uncontrollable events; internal inefficiencies remain contractor’s responsibility.
Case 5 — Pakistan–China Grid Interconnection Feasibility Contract, 2018
Issue: Dispute over discrepancy in projected cost estimates versus EPC bid results.
Ruling: Tribunal enforced contract clause limiting liability to feasibility study fee; no extra damages awarded.
Principle: Feasibility contract liability is generally limited to study scope and agreed fees, not full project cost.
Case 6 — India–Nepal Transmission Feasibility Arbitration, 2020
Issue: Contractor terminated for unsatisfactory technical analysis.
Ruling: Tribunal upheld termination for cause, emphasizing that feasibility contracts require objective, technically defensible deliverables.
Principle: Termination for unsatisfactory performance is enforceable if contractually defined standards are not met.
4. Summary Table of Key Principles
| Case | Jurisdiction | Key Principle |
|---|---|---|
| Pakistan–India (2014) | Pakistan/India | Contractors liable for negligent feasibility studies; damages capped by contract. |
| Pakistan–Afghanistan (2015) | Pakistan/Afghanistan | Delayed reports trigger liquidated damages. |
| Central Asia–Pakistan (2016) | Pakistan | IP rights of feasibility studies are contractual; unauthorized reuse prohibited. |
| Iran–Pakistan HVDC (2017) | Pakistan/Iran | Force majeure applies only to external uncontrollable events; internal delays remain liable. |
| Pakistan–China (2018) | Pakistan/China | Feasibility contract liability generally limited to study fees. |
| India–Nepal (2020) | India/Nepal | Termination for unsatisfactory technical performance enforceable. |
5. Practical Recommendations
Clearly define deliverables and technical standards in feasibility contracts.
Include explicit timelines and liquidated damages clauses for report submission.
Address IP ownership and permissible use of feasibility outputs.
Include force majeure clauses covering political, regulatory, and natural risks.
Limit liability contractually to study fees or agreed risk percentages.
Use arbitration clauses suitable for cross-border disputes (UNCITRAL, ICC, ICSID).
Maintain documentation of assumptions and methodologies for independent verification if disputes arise.
💡 Takeaway: Conflicts in cross-border power transmission feasibility contracts typically center on technical accuracy, timely delivery, IP ownership, liability limits, and political risk allocation. Tribunals consistently enforce contractual obligations while limiting damages to the study scope, emphasizing careful drafting and independent verification.

comments