Legal Opinion

Friends of Keeseville, Inc. v. Federal Energy Regulatory Commission

Court of Appeals for the D.C. Circuit

Decided October 7, 1988No. 87-1691PublishedCited by 42 opinions

1Opinion of the Court

Opinion for the Court filed by Chief Judge WALD.

WALD, Chief Judge:

Petitioner, Friends of Keeseville (“Friends”), challenges certain orders of the Federal Energy Regulatory Commission (“FERC”). FERC contends that the orders were proper and that Friends is not currently aggrieved by the Commission’s actions. We have concluded that this case is partly moot and partly unripe, and that adjudication at this time is therefore inappropriate. The petition is accordingly dismissed,

Facts

This case involves the efforts of various parties to develop a hydroelectric power project on the Ausable River in…

2Cases cited22 opinions

  1. Chapman v. CaliforniaSupreme Court of the United States · 1967
  2. Kotteakos v. United StatesSupreme Court of the United States · 1946
  3. Abbott Laboratories v. GardnerSupreme Court of the United States · 1967
  4. Pierce v. UnderwoodSupreme Court of the United States · 1988
  5. Valley Forge Christian College v. Americans United for Separation of Church and State, Inc.Supreme Court of the United States · 1982

17 more not listed; retrieve them via the Exa API.

3Cited by42 opinions

  1. A.I. Trade Finance, Inc. v. Petra International Banking CorporationCourt of Appeals for the D.C. Circuit · 1995
  2. Crowley Caribbean Transport, Inc. Crowley Maritime Corporation v. Federico F. Pena, Secretary of Transportation Lykes Bros. Steamship Company, Inc.Court of Appeals for the D.C. Circuit · 1994
  3. Edison Electric Institute v. U.S. Environmental Protection AgencyCourt of Appeals for the D.C. Circuit · 1993
  4. American Bird Conservancy, Inc. v. Federal Communications CommissionCourt of Appeals for the D.C. Circuit · 2008
  5. Baystate Medical Center v. LeavittDistrict Court, District of Columbia · 2008

37 more not listed; retrieve them via the Exa API.

Showing a preview — retrieve the full document via the Exa API.

Powered by the Exa API