07.01.2015 Views

-i- TO THE SUBROGATE PRESIDENT OF THE ... - Chevron

-i- TO THE SUBROGATE PRESIDENT OF THE ... - Chevron

-i- TO THE SUBROGATE PRESIDENT OF THE ... - Chevron

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

an entitlement to monetary damages for “a plan to regenerate aquatic life,” 784 an<br />

injunctive order for the “cleanup of rivers, streams, lakes, marshes and natural and<br />

manmade waterways” 785 is superfluous. Because plaintiffs have not even attempted to<br />

prove an action for individualized damages under the provisions Article 2214, the only<br />

legal basis for the claims asserted here is—as is expressly pled in Chapter VI(2)—the<br />

EMA.<br />

In any event, for any injunctive claim brought under these facts for contingent<br />

damages, Petroecuador is the only proper defendant. An action to prevent potential<br />

future harm must be brought against either the owner of the property or the party<br />

currently engaged in the activity that causes the threat or contingent harm, since they<br />

are the only ones who can prevent the challenged activity and the threatened harm.<br />

Such an action cannot logically be brought against a third party who has no control over<br />

the activity or the property. That is the case here with respect to <strong>Chevron</strong>. First,<br />

Petroecuador alone has operated the former Consortium fields for almost twenty years.<br />

It is thus responsible for any threatening condition that presently exists in the area—as<br />

the current owner and operator, it alone is “negligent” under Article 2236 of Civil Code in<br />

failing to remove any threat to unspecified persons. Second, the nature of the claim is<br />

injunctive, in that it requires the elimination of the threatening condition. The current<br />

operator and holder of rights over the area where the allegedly threatening condition<br />

exists (here, Petroecuador) is the only party that is capable of fulfilling the terms of the<br />

requested injunction. 786 Third, as discussed above, supra § 5.2.2, Petroecuador<br />

released TexPet and itself assumed all remaining responsibility for environmental<br />

impact in the former Consortium area. The structure of the settlement, under which<br />

TexPet performed remediation commensurate with its minority share of the Consortium,<br />

reflected the parties’ understanding that Petroecuador would have to answer for any<br />

continued environmental threats in the former concession area, where it continues to<br />

operate today. Because Petroecuador is the proper defendant, the plaintiffs have no<br />

cause of action against <strong>Chevron</strong> for the injunctive relief they seek.<br />

5.3.3 The Cause of Action Granted by the EMA Constitutes a Substantive<br />

Change in the Law and Thus Cannot Be Applied Retroactively<br />

Because no pre-existing provision of the law authorized an equivalent cause of<br />

action, Article 43 of the 1999 EMA substantively changed the law. As demonstrated<br />

above, such provisions cannot be applied retroactively to conduct that occurred prior to<br />

the change in the law, especially in the face of the settlement agreement releasing<br />

TexPet and its affiliates from any liability for environmental impacts in the area of the<br />

former Petroecuador-TexPet concession.<br />

784 Plaintiffs’ Complaint, filed May 7, 2003 at 11:30 a.m., Record at 73-80v, 80.<br />

785 Plaintiffs’ Complaint, filed May 7, 2003 at 11:30 a.m., Record at 73-80v, 79v.<br />

786 Article 1569 of the Civil Code is not applicable because the defendant is not currently in<br />

default. <strong>Chevron</strong> has not failed to perform any preexisting legal obligation; to the contrary, the<br />

Government of Ecuador certified that TexPet fulfilled all of its contractual remediation responsibilities.<br />

CERT. INTERMARK VER: JD<br />

- 175 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!