July-August 2002

  • 1
  • 2

Stormwater Regulations in California Vineyards

A complex legal battle around one local industry could affect the future of stormwater regulations–and costs–nationwide.

Article Tools

Create a Link to this Article

By Stephen Ferry

Comments

The environmental impacts of one of the largest and most visible agricultural activities in the state of California are under scrutiny. At issue are the industry's categorical exemptions from the state's environmental review process, permitting and enforcement issues, and erosion and sediment control (ESC) ordinances specifically designed for hillside vineyards.

The California wine industry is huge; in terms of retail sales, wine is the state's top finished agricultural product. California produces approximately 450 million gal. of wine per year, and total revenue from the wine industry and its associated support functions–from trucking to equipment to wine labels–runs to more than $28 billion a year. Napa Valley alone has more than 300 wineries of various sizes.

Other industries are watching closely to see how local governments finally cope with the industry–on a project-by-project basis or under a general classification–and how government and industry divide the financial burden of determining compliance.

Federal and State Regulations

In 1987, Section 319 was added to the federal Clean Water Act (CWA), requiring each state to assess nonpoint-source (NPS) pollution problems, identify sources of pollution, and implement management programs to control NPS pollution. All states by now have begun the process of assessing watersheds, identifying beneficial uses of the water bodies in each, identifying stressors (pollutants) that are negatively impacting those beneficial uses, and inducing stakeholders within each impaired watershed to reduce discharges of the known stressors. A water body identified as having impaired beneficial uses is placed on the federal 303(d) list, and the state is then charged with establishing numerical limits (total maximum daily loads, or TMDLs) on the stressor at appropriate locations within the water body and reducing total discharges of the target stressor to levels that do not impair beneficial uses.

One of the most common stressors identified in 303(d)-listed waters is sediment or siltation. Stormwater runoff is probably the most common mode of transport for sediment. Many activities not previously covered by an existing National Pollutant Discharge Elimination System (NPDES) general stormwater permit clearly have the potential to contribute sediment to local water bodies.

State and local governments with oversight responsibilities in 303(d)-listed watersheds are coming under increasing pressure to ensure that the cumulative effect of all activities within a watershed will not lead to a persistent violation of the inevitable TMDL target discharge levels. In California, the California Environmental Quality Act (CEQA) provides the legal framework for the manner in which local governments implement the TMDL process.

The CEQA Process and Its Exemptions

The CEQA process is defined in Division 13 of the California Public Resources Code, Articles 21000-21178, and is further clarified in Title 14, Sections 15000-15387 of the California Code of Regulations (the CEQA guidelines). CEQA provides that public decision-makers and the public are informed about the potential, significant environmental impacts of a proposed project.

PRC§§21065 and CCR14§15378 define the scope of projects subject to review under CEQA. A proposed enterprise is a "project" under CEQA if it "has a potential for resulting in either a direct physical change in the environment, or a reasonably foreseeable indirect physical change in the environment," if the project is undertaken, subsidized, or permitted by a public agency (CCR14§15378).

Complying with CEQA is typically approached in the same manner as establishing compliance with most regulations seeking to govern the conduct of commerce: by exploring possible avenues to exemption from the regulation.

Statutory Exemption (Stat Ex) from the CEQA process is allowed for a number of classifications of projects, most of which are ministerial under the lead public agency's statutes and ordinances (PRC§§21080). Ministerial projects are defined under the CEQA guidelines as "involving little or no personal judgment by the public official as to the wisdom or manner of carrying out the project. The public official merely applies the law to the facts as presented but uses no special discretion or judgment in reaching a decision. A ministerial decision involves only the use of fixed standards or objective measurements, and the public official cannot use personal, subjective judgment in deciding whether or how the project should be carried out. Common examples of ministerial permits include automobile registrations, dog licenses, and marriage licenses. A building permit is ministerial if the ordinance requiring the permit limits the public official to determining whether zoning allows the structure to be built in the requested location, the structure would meet the strength requirements in the Uniform Building Code, and the applicant has paid his fee." (14CCR§15369).

CEQA provides that neither a public review period nor a public notice of exemption (NOE) from CEQA is required when the project is statutorily exempt from CEQA, and the basis for exemption is that the agency's project review process is completely ministerial.

For projects sufficiently complex as to require discretionary judgment on the part of the public agency in evaluating the potential for environmental impacts, Stat Ex from CEQA is not an option. Where the public agency, in its judgment, considers the impacts to be less than significant, a Categorical Exemption (Cat Ex) from CEQA may be issued.

CEQA does not require a public review period for Cat Ex projects. Although not required under CEQA, public agencies generally file NOEs, but only after the agency has determined to carry out the project. In the interest of keeping the public informed, Subsection 15061(d) allows the NOE to be completed during the preliminary review and to be kept with the project file during the processing of the project application. By including the notice in the file, the agency would show any people reviewing the file that CEQA had been considered, that the agency regarded the project as exempt, and that the agency would be ready to file the notice as soon as the decision was made on the project.

Cat Ex determinations generally withstand legal scrutiny. But when a large number of essentially identical projects are proposed to be conducted in close geographical proximity to each other, the cumulative impact of all of the projects considered together becomes a consideration. CEQA denies Cat Ex status to a project when "the cumulative impact of successive projects of the same type in the same place, over time is significant" (CCR14§15300.2[b]).

Where the Cat Ex is not an option, CEQA requires either a Negative Declaration (ND), a Mitigated Negative Declaration (MND), or a full-blown environmental impact review (EIR). In all cases, an initial study is the first step in the process. This study may support the preparation of an ND or an MND, or it may serve as the basis for an eventual EIR.

CEQA requires public review periods of three to six weeks as part of the approval process for any projects not statutorily or categorically exempt. In addition, public noticing is required before all public review periods and after all decisions have been reached.

A project that cannot achieve Stat Ex or Cat Ex status and goes instead to the initial study level turns into a costly and lengthy process. Regulatory approval time frequently increases from months to years. Costs can increase from tens of thousands to millions of dollars.

Vineyard Development Regulation in Napa and Sonoma Counties

A topographical map of the Napa Valley illustrates the runoff potential of the surrounding hillsides.

In the wine country of northern California, a critical battle is being played behind the scenes as local governments grapple with the dilemma of how to shepherd their constituent base through the expanding CEQA maze. This battle could set precedents for how future stormwater regulations are enforced and administered in many industries and localities–and who pays for it.

In 1987, a vineyard development operation was found to be the cause of a significant movement of soil into Bell Canyon Municipal Reservoir, an important drinking-water source for the Napa Valley. Napa County was stimulated to generate California's first hillside vineyard ESC ordinance. In 1991, Napa County adopted the state's first county ordinance specifically regulating vineyard development. The planting of new vineyards on slopes greater than 50% was prohibited, and vineyard development activities on slopes greater than 30% were restricted.

In response to public comment regarding the application and enforcement of the new Napa vineyard ESC ordinance over the first seven years of its existence, the Napa River Watershed Task Force (NWTF) was formed in December 1998 to develop recommendations for possible improvements to the ordinance. The task force was originally funded with $100,000 of county money and anticipated producing, in less than a year, a set of recommendations for conservation strategies to protect natural resources. Seventeen local citizens representing a cross-section of stakeholder interests served on the task force.

Advertisement

In September 1999, the Sierra Club sued Napa County, the county planning director personally, and a private winery/vineyard developer, claiming that the county's administration of the original Napa vineyard ESC ordinance failed to provide for adequate environmental review of proposed vineyard development projects and so did not provide effective protection of water quality and wildlife habitat.

The lawsuit challenged the county's tendency to judge the projects as categorically exempt from CEQA and therefore not subject to public review before approval. The lawsuit also charged that the cumulative impacts of all the projects were not being adequately considered. Next Page >

  • 1
  • 2

What Do You Think?

Post a Comment

Be the first to tell us what you think!

Post a Comment

Not a subscriber? Sign Up
 
 
*  
 




 

Get Stormwater E-mail Updates!

Get weekly news and updates through our Stormwater e-mail newsletter!