Washington Toxics Coalition v. U.S. Environmental Protection Agency

357 F. Supp. 2d 1266, 2004 U.S. Dist. LEXIS 27625
CourtDistrict Court, W.D. Washington
DecidedAugust 12, 2004
DocketC04-0113C
StatusPublished
Cited by2 cases

This text of 357 F. Supp. 2d 1266 (Washington Toxics Coalition v. U.S. Environmental Protection Agency) is published on Counsel Stack Legal Research, covering District Court, W.D. Washington primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Washington Toxics Coalition v. U.S. Environmental Protection Agency, 357 F. Supp. 2d 1266, 2004 U.S. Dist. LEXIS 27625 (W.D. Wash. 2004).

Opinion

ORDER

COUGHENOUR, Chief Judge.

I. INTRODUCTION

This matter comes before the Court on Defendant U.S. Environmental Protection Agency’s (“EPA”) motion to dismiss, or, in the alternative, for summary judgment (Dkt. No. 8). The Court has considered the' papers submitted by the parties and determined that oral argument is not necessary. For the following reasons, the Court DENIES Defendant’s motion to dismiss and GRANTS Defendant’s alternative motion for summary judgment.

II. BACKGROUND

A. EPA and the Federal Insecticide, Fungicide, and Rodenticide Act 1 (“FIFRA”)

FIFRA, enacted in 1947 and revised in 1972, regulates the use of pesticides by prohibiting the distribution or sale of any pesticide not registered with the EPA. 7 U.S.C. § 186a. The Office of Pesticide Programs (“OPP”), part of EPA, administers FIFRA. A pesticide may only be registered if, based on data conforming to EPA-established guidelines, OPP determines that the pesticide “will perform its intended function without unreasonable adverse effects on the environment.” Id. § 136a(c)(5). This evaluation depends, in part, on whether the pesticide violates the Endangered Species Act 2 (“ESA”), because of its potential to “jeopardize the continued existence of any endangered species or threatened species or result in the destruction or adverse modification of habitat of such species.” 16 U.S.C. § 1536(a)(2). OPP frequently directs registrants of pesticides to submit data, called “species proximity data,” to determine whether this is the case. (Def.’s Mot. to Dismiss at 4,) Species proximity data indicates “where threatened and endangered species could be found in relation to the use sites for which the pesticides were registered.” (Id.) After notifying EPA, pesticide registrants may form a joint data development arrangement (“JDDA”), an agreement to jointly develop or share the cost of developing data that meets EPA requirements for registering pesticides under FIFRA. 7 U.S.C. § 136a(e)(2)(B)(ii). JDDAs help interested pesticide registrants defray the cost of collecting and compiling data to show that a pesticide satisfies FIFRA’s requirements.

B. The FIFRA Endangered Species Task Force (“FESTF”)

In 1994, the National Agricultural Chemical Association (“NACA”), a national trade association for developers, manufacturers, formulators, and distributors of agricultural pesticides in the United States, began using a steering committee to seek support for the formation of a JDDA to collect and compile species proximity data as required by OPP. In 1995, NACA suc *1269 ceeded in prompting development of FESTF, which was originally composed of eleven private companies. As a JDDA, FESTF’s purpose was to develop data to meet OPP requirements for registering pesticides and disperse the related costs among its members, while “protecting the proprietary interests of the members of FESTF.” (Def.’s Mot. to Dismiss at 5.) Before establishing FESTF, the NACA steering committee met with OPP in 1994 to determine whether the proposed methodology for gathering and compiling data through FESTF would meet OPP requirements under FIFRA and ESA. OPP confirmed that the proposed methodology would likely be acceptable, and FESTF began operating as an unincorporated association in March 1995.

FESTF first developed detailed possible procedures for obtaining species proximity data, then submitted these proposals to several organizations, including OPP and The Nature Conservancy, for comment. Based on the comments, FESTF decided that the proposed methods would not produce the appropriate data. By 1997, however, FESTF had developed another proposal for obtaining data to satisfy OPP requirements with the help of Nature-Serve, a nonprofit conservation organization. FESTF hired Battelle Pacific Northwest Laboratories to develop an Information Management System to compile data obtained from NatureServe about the location of endangered and threatened species. Throughout this process, FESTF maintained a relationship with OPP, frequently requesting feedback on its developing methodology for meeting OPP data requirements. EPA representatives attended some FESTF meetings, and OPP and FESTF corresponded ' regularly. EPA did not, however, play a role in the formation of FESTF, nor is any EPA representative a member of FESTF. EPA does not provide FESTF with financial support, and FESTF has not received public funds from any other source.

FESTF reorganized as a limited liability company under Delaware law in 1997. FESTF continued to develop software and methodology for gathering and compiling data in the following years, consulting OPP regularly about “how FESTF intend[ed] to meet the species proximity data requirements.” (Id. at 10.) The parties dispute whether, throughout their years of contact, FESTF also communicated its position on pesticide “policy” matters to EPA. On April 17, 2000, OPP publicly announced the existence and purpose of FESTF and its complete proposal for meeting OPP’s species proximity data requirements. The notice advised all pesticide registrants and applicants that they would be required to submit similar data, and could satisfy this requirement by joining FESTF, citing to its work and sharing its costs, or submitting their own data (also subject to OPP standards).

Plaintiffs brought this action alleging that EPA violated the Federal Advisory Committee Act (“FACA”), 5 U.S.C.App. § 2, by establishing and obtaining advice from FESTF without classifying and treating it as a federal advisory committee (see discussion infra). Plaintiffs allege that EPA’s role during FESTF’s formation and development indicates that EPA “established” or “utilized” FESTF, because “EPA was intimately involved in establishing FESTF ... and has repeatedly shaped and approved its evolving priorities ever since.”- (Pl.’s Opp’n to Mot. to Dismiss at 17.) Plaintiffs provide examples to illustrate their allegations, including a letter from FESTF to EPA in 1994 that stated that FESTF would “[djevelop priorities in partnership with [EPA],” and-that the two groups would work in “close cooperation.” (Shaw Decl. 6 at 1-2.) EPA filed a motion to dismiss, or, in the alternative, a motion *1270 for summary judgment (Dkt. No. 8), arguing that Plaintiffs do not have standing to bring this action and that FESTF is not a federal advisory committee under FACA. In their opposition to the motion to dismiss, Plaintiffs request that the Court continue consideration of the motion, arguing that they are entitled to conduct discovery on the issue of whether FESTF “was established or utilized by a federal agency because it was permeated by, organized by, or closely tied to the federal government,” in order to oppose EPA’s motion to dismiss. (Pl.’s Opp’n to Mot. to Dismiss at 15-16.)

III. ANALYSIS

A. Motion to Dismiss

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Judicial Watch, Inc. v. United States Department of Commerce
736 F. Supp. 2d 24 (District of Columbia, 2010)

Cite This Page — Counsel Stack

Bluebook (online)
357 F. Supp. 2d 1266, 2004 U.S. Dist. LEXIS 27625, Counsel Stack Legal Research, https://law.counselstack.com/opinion/washington-toxics-coalition-v-us-environmental-protection-agency-wawd-2004.