Why Do States Adopt Renewable Portfolio Standards? An Empirical Investigation

24 Pages Posted: 31 Oct 2007

See all articles by Thomas P. Lyon

Thomas P. Lyon

University of Michigan, Stephen M. Ross School of Business

Haitao Yin

Erb Institute for Global Sustainable Enterprise

Multiple version iconThere are 2 versions of this paper

Date Written: May 2007

Abstract

We present the first empirical analysis of the factors that drive state governments to adopt a Renewable Portfolio Standard (RPS), and the factors that lead to the inclusion of in-state requirements given the adoption of an RPS. We find that states with poor air quality, strong democratic presence in the state legislature and organized renewable developers are more likely to adopt an RPS. Economic benefits do not seem to be an important driver for RPS adoption although they have been widely touted in the legislative process. In-state requirements are more likely in states with poor air quality, rich renewable energy resources, and low amounts of existing renewable electricity generation. In-state requirements are also positively correlated with the percentage of congressional seats occupied by Democrats and negatively correlated with the presence of a Republican governor.

Keywords: Renewable Portfolio Standards, Renewable Energy, Regulation

JEL Classification: Q58

Suggested Citation

Lyon, Thomas P. and Yin, Haitao, Why Do States Adopt Renewable Portfolio Standards? An Empirical Investigation (May 2007). Available at SSRN: https://ssrn.com/abstract=1025513 or http://dx.doi.org/10.2139/ssrn.1025513

Thomas P. Lyon (Contact Author)

University of Michigan, Stephen M. Ross School of Business ( email )

701 Tappan Street
Ann Arbor, MI MI 48109
United States
734-615-1639 (Phone)

Haitao Yin

Erb Institute for Global Sustainable Enterprise ( email )

Dana Building
440 Church Street
Ann Arbor, MI, MI 48109-1041
United States

Do you have negative results from your research you’d like to share?

Paper statistics

Downloads
543
Abstract Views
3,318
Rank
55,239
PlumX Metrics