County of Rockland v. Federal Aviation Administration

335 F. App'x 52
Court of Appeals for the D.C. Circuit·Decided June 10, 2009·No. Nos. 07-1363, 07-1437, 07-1493 to 07-1499, 08-1105 to 08-1107·Published

Opinion

[53]*53 JUDGMENT

These petitions for review were considered on the record from the Federal Aviation Administration and on the briefs and arguments of the parties. It is

ORDERED AND ADJUDGED that the petitions for review be dismissed insofar as the petitioners forfeited some of their challenges and otherwise denied for the reasons given in the attached memorandum opinion.

Pursuant to D.C. Circuit Rule 36, this disposition will not be published. The Clerk is directed to withhold issuance of the mandate herein until seven days after resolution of any timely petition for rehearing or petition for rehearing en banc. See Fed. RApp. P. 41(b); D.C.Cir. Rule 41.

MEMORANDUM OPINION

In a corrected Record of Decision (ROD) issued September 28, 2007 the Federal Aviation Administration adopted a multi-phase plan to modernize the New York/New Jersey/Philadelphia Metropolitan Area airspace. The redesign shifts flight paths, reallocates management of particular sectors of airspace amongst air traffic control facilities, and adopts new flight procedures. The changes will, the FAA determined, reduce delay and increase operational efficiency, without imposing significant noise effects upon, or increasing air pollution in, the states below the NY/NJ/PHL airspace. The petitioners object to the FAA’s analysis of environmental impacts as procedurally invalid and substantively unreasonable, in violation of the National Environmental Policy Act (NEPA), the Department of Transportation Act (DOT Act), and the Clean Air Act (CAA). We dismiss the petitions for review insofar as the petitioners forfeited some of their challenges and deny the rest of the petitions because the FAA’s environmental impact analysis was procedurally sound and substantively reasonable.

I. NEPA

NEPA directs a federal agency to “include in every ... report on proposals for ... major Federal actions significantly affecting the quality of the human environment, a detailed statement ... on ... the environmental impact of the proposed action,” 42 U.S.C. § 4332(2)(C)(i), known as an environmental impact statement (EIS). We review the FAA’s compliance with NEPA for the most part under the arbitrary and capricious standard of the Administrative Procedure Act, asking whether the agency provided “the necessary process” and took a “ ‘hard look’ at environmental consequences.” Robertson v. Methow Valley Citizens Council, 490 U.S. 332, 350, 109 S.Ct. 1835, 104 L.Ed.2d 351 (1989); see Nevada v. Dep’t of Energy, 457 F.3d 78, 93 (D.C.Cir.2006). We address only a few of the petitioners’ many objections to the EIS. None of the petitioners’ objections amounts to a significant procedural deficiency and none indicates that the FAA failed to take a “hard look” at the environmental impacts of its action. See Cmtys. Against Runway Expansion, Inc. v. FAA, 355 F.3d 678, 685 (D.C.Cir.2004).

The petitioners first attack the FAA’s forecast of future traffic. The agency’s forecast is entitled to “even more deference” than this court gives “under the highly deferential arbitrary and capricious standard.” St. John’s United Church of Christ v. FAA, 550 F.3d 1168, 1172 (D.C.Cir.2008). The petitioners argue the FAA failed to consider reasonably foreseeable indirect effects of the redesign, as required by 42 U.S.C. § 4332(2)(C)(ii) and 40 C.F.R. § 1508.8(b), because the agency refused to adjust its forecast for the growth-inducing effect of reductions in [54]*54flight delay. In the FAA’s experience, however, airspace redesign, which increases throughput but not airport capacity, does not induce significant enough additional demand to warrant modeling. We have deferred to similar reasoning before, and we do so again here. See City of Olmsted Falls v. FAA, 292 F.3d 261, 272 (D.C.Cir.2002). The petitioners insist the FAA’s reliance upon its experience ran counter to the evidence before it, but they point to statements of the agency that show nothing more than the possibility of another reasonable view; that is not enough to discharge their burden to show the FAA was arbitrary, see City of Los Angeles v. FAA, 138 F.3d 806, 808 (9th Cir.1998).

Next, the petitioners change course, contending that once the FAA recognized it had overestimated future traffic, particularly at Newark International Airport, it should have adjusted the baseline for its environmental analysis. The FAA, however, took the requisite hard look by “creating its models with the best information available when it began its analysis and then checking the assumptions of those models as new information became available.” Village of Bensenville v. FAA, 457 F.3d 52, 71 (D.C.Cir.2006). Although the agency found a 14% gap between its forecast of 2006 traffic on the average annual day at Newark and actual traffic there on the average day in 2005, it also found the overall forecast was well within the 10% margin of acceptable error the agency employs when deciding whether a forecast is useful for decision making. The FAA concluded the forecast, although not perfect, still “capture[d] the general flow and magnitude of the traffic in a way that can show differences among the proposed alternatives.”

The petitioners’ chief complaint is that the FAA’s explanation is unreasonable because whether the redesign will reduce delay turns upon the forecast at Newark. As the FAA explains, however, although Newark will experience the greatest reduction in “block time” — which the petitioners erroneously treat as a reduction in delay — all the major airports in the region will experience reductions in delay. The petitioners’ focus upon one data point for Newark is therefore based upon their having misunderstood the record before the agency. Given the substantial deference we owe the agency, see St. John’s, 550 F.3d at 1172, we cannot say its reassessment of the forecast was arbitrary and capricious.

In their final challenge to the FAA’s traffic forecast, the petitioners argue the FAA should have forecast the impact of future traffic in 2012 and in 2017 because the agency “usually” forecasts such impacts for the “year of anticipated project implementation and [for] 5 to 10 years after implementation.” FAA Order 1050.1E, Environmental Impacts: Policies and Procedures app.A § 14.4g(2) (Mar. 20, 2006). The FAA, however, need only select an “appropriate” timeframe for a forecast, id., and the petitioners have not given us a reason to think the FAA, when it began the analysis in 2001, selected an inappropriate timeframe; nor have they shown that, once the FAA pushed back the date of implementation, it was arbitrary not to restart the analysis.

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

County of Rockland v. Federal Aviation Administration, 335 F. App'x 52 (D.C. Cir. 2009).

335 F. App'x 52 (County of Rockland v. Federal Aviation Administration) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related