Hatley v. Umatilla County

Annotate this Case

Download PDF

FILED: April 03, 2013 IN THE COURT OF APPEALS OF THE STATE OF OREGON JIM HATLEY, Petitioner, v. UMATILLA COUNTY, Respondent, and BLUE MOUNTAIN ALLIANCE, DAVE PRICE, and RICHARD JOLLY, Intervenors-Respondents below. Land Use Board of Appeals 2012017, 2012018, 2012030 A152777 Argued and submitted on January 03, 2013. Bruce W. White argued the cause and filed the brief for petitioner. Michael C. Robinson argued the cause for respondent. With him on the brief were Corinne S. Celko and Perkins Coie LLP. Before Armstrong, Presiding Judge, and Nakamoto, Judge, and Egan, Judge. NAKAMOTO, J. Affirmed in part, reversed in part, and remanded. 1 1 1 NAKAMOTO, J., 2 Petitioner seeks judicial review of a final order of the Land Use Board of 3 Appeals (LUBA), in which LUBA affirmed Umatilla County's (the county) enactment of 4 two ordinances, Ordinances 2012-04 and 2012-05.1 Those ordinances, which affect 5 conditional uses of petitioner's property, were adopted in response to LUBA's remand in 6 Cosner v. Umatilla County, ___ Or LUBA ___ (LUBA Nos 2011-070, 2011-071, 2011- 7 072, Jan 12, 2012), an earlier case in which petitioner participated. On appeal, petitioner 8 advances two assignments of error. First, petitioner argues that LUBA erred in 9 determining that, in Ordinance 2012-05, the county's protections of threatened and 10 endangered fish and its restrictions on development of Wind Power Generation Facilities 11 (WPGFs) on highly erodible soils did not require the application of Goal 5, a statewide 12 land use planning goal. Second, petitioner contends that LUBA erred in determining that 13 his challenge to the two-mile setback requirement for WPGFs in Ordinance 2012-04 was 14 foreclosed on the basis of invited error or, in the alternative, waiver. For the reasons 15 stated below, we affirm in part and reverse in part. 16 Petitioner owns 1,926 acres of undeveloped property in an exclusive farm 17 use (EFU) zone in the Walla Walla River Sub-basin of Umatilla County. His property is 18 subject to a lease for development of WPGFs. His property has flat ridge tops that are 19 surrounded by slopes and drained by tributaries in the Walla Walla River Sub-basin. The 1 Intervenors in the LUBA proceedings--Blue Mountain Alliance, Dave Price, and Richard Jolly--did not participate in this appeal. 2 1 sloped areas are likely to fall within the county's classification of "highly erodible soils." 2 To provide context for one of the issues on review, we begin by giving a 3 brief overview of the requirements of Goal 5 and Goal 5's applicability to a post- 4 acknowledgment plan amendment (PAPA).2 Goal 5 is a statewide land use planning goal 5 to protect natural resources and conserve scenic, historic, and open space resources. 6 OAR 660-015-0000(5). Pursuant to OAR chapter 660, division 16, local governments 7 must conduct three tasks to comply with Goal 5. First, local governments must inventory 8 key resource sites. OAR 660-016-0000. Then, local governments must identify 9 conflicting uses with the inventoried Goal 5 resource sites and determine the "economic, 10 social, environmental and energy" (ESEE) consequences of allowing those conflicting 11 uses for those resource sites. OAR 660-016-0005(1). Last, based on its determination of 12 the ESEE consequences, the local government must develop a "program to achieve the 13 Goal." OAR 660-016-0010. 14 Local governments are not required to comply with Goal 5 when 15 considering a PAPA unless the PAPA "affects a Goal 5 resource." According to OAR 16 660-023-0250(3), there are three ways a PAPA can affect a Goal 5 resource: 17 18 19 "(a) The PAPA creates or amends a resource list or a portion of an acknowledged plan or land use regulation adopted in order to protect a significant Goal 5 resource or to address specific requirements of Goal 5; 20 21 "(b) The PAPA allows new uses that could be conflicting uses with a particular Goal 5 resource site on an acknowledged resource list; or 2 A PAPA includes "amendments to an acknowledged comprehensive plan or land use regulation and the adoption of any new plan or land use regulation" in accordance with ORS 197.610 to 197.625. OAR 660-023-0010(5). 3 1 2 3 4 "(c) The PAPA amends an acknowledged [Urban Growth Boundary] and factual information is submitted demonstrating that a resource site, or the impact areas of such a site, is included in the amended [Urban Growth Boundary] area." 5 In this case, petitioner's dispute with the county began in 2011, when the 6 county adopted an ordinance that, in petitioner's view, was a PAPA that the county had 7 adopted without complying with Goal 5, as required by OAR 660-023-0250(3). In 2011, 8 the county adopted Ordinances 2011-05 to 2011-07, which amended the county's 9 conditional use standards and added new restrictions to WPGFs in EFU zones. In 10 Cosner, petitioner intervened in an appeal to LUBA, challenging all three of the county's 11 2011 ordinances. Petitioner contended that one of them, Ordinance 2011-07, was a 12 PAPA because the county added section 11 to Umatilla County Development Code 13 (UCDC) 152.616(HHH) to provide additional standards for WPGFs in the Walla Walla 14 watershed. Ordinance 2011-07 provided, in part: 15 "(11) Walla Walla Watershed. 16 17 18 19 20 21 22 "Lands located within the Walla Walla Sub-basin East of Highway 11 shall be subject to additional standards. The purpose of these criteria is to prevent impacts to the following: inventoried Goal 5 resources, highly erodible soils (as defined by the Oregon Department of Agriculture), federally listed threatened and endangered species, and the Critical Winter Range. The standards are also designed to protect sensitive streams and to be consistent with the Clean Water Act. 23 24 25 26 "(A) There shall be no construction of project components, including wind turbines, transmission lines and access roads on soils identified as highly erodible. The highly erodible soils are those soils identified by the Oregon Department of Agriculture as highly erodible. 27 28 "(B) The application shall demonstrate that the [WPGF] and its components, wind turbines, transmission lines, and roads, will not conflict 4 1 2 with existing significant Goal 5 Resources within the Walla Walla Subbasin. 3 4 5 6 "(C) The application shall demonstrate that the [WPGF] and its components will be setback a minimum of two miles from streams and tributaries that contain Federally listed threatened and endangered species, and, that the project will generate no runoff or siltation into the streams. 7 8 "(D) The application shall demonstrate that the [WPGF] and its components will not be located within the Critical Winter Range." 9 (Underscoring omitted.) Petitioner contended that, because Ordinance 2011-07 amended 10 the county's land use regulations for WPGFs on EFU zones and affected Goal 5 11 inventoried resources, the county was required to comply with Goal 5's inventory and 12 conflicting use ESEE analysis requirements. 13 The two other ordinances petitioner challenged, Ordinances 2011-05 and 14 2011-06, did not affect Goal 5 inventoried resources and instead concerned setbacks for 15 WPGFs. Petitioner's challenge to those ordinances focused on their constitutionality. 16 The county's previous conditional use standard in section 6 of UCDC 152.616(HHH) 17 required WPGFs to be set back a minimum of 3,520 feet from property zoned for 18 residential use. In Ordinance 2011-05, the county significantly changed the setback 19 requirement by imposing a two-mile setback from any urban growth boundary, with the 20 possibility of a waiver if the city council of the affected city authorized a lesser setback. 21 Similarly, Ordinance 2011-06 imposed a two-mile setback from any rural residence, but 22 allowed a waiver if the affected land owner recorded a written waiver allowing a lesser 23 setback. Petitioner contended in Cosner that, by allowing city councils or private 24 landowners to "waive" the setbacks requirements, those two ordinances were an unlawful 5 1 delegation of legislative authority. 2 Petitioner's challenges were successful. In Cosner, LUBA remanded the 3 2011 ordinances that amended sections 6 and 11 of UCDC 152.616(HHH) for the county 4 to address three problems. First, LUBA remanded Ordinances 2011-05 and 2011-06 5 because the two-mile setback waiver provisions in each ordinance violated the delegation 6 clause of Article I, section 21, of the Oregon Constitution. Second, LUBA concluded 7 that, under Ordinance 2011-07, the county had amended the program to achieve Goal 5 8 by adopting additional measures to protect Goal 5 inventory resources without complying 9 with Goal 5, as required by OAR 660-023-0250(3). LUBA remanded Ordinance 2011-07 10 for the county to address the requirements of Goal 5, i.e., to conduct the inventory and 11 ESEE analysis described in OAR 660-023-0040(2) to (5) and to adopt the appropriate 12 findings. Lastly, LUBA remanded for the county to address whether all three ordinances 13 were consistent with several county comprehensive plan policies regarding energy. 14 On remand, the county addressed the problems identified in Cosner by 15 passing two new ordinances in 2012 that are relevant to the issues on review. In 16 Ordinance 2012-04, the county imposed an absolute two-mile setback from urban growth 17 boundaries on rural residences, deleting the two waiver provisions that LUBA had found 18 were unconstitutional in Cosner.3 3 Ordinance 2012-04 provides, in part: "(6) Standards/Criteria of Approval. The following requirements and restrictions apply to the siting of a [WPGF]: 6 1 In Ordinance 2012-05, the county sought to avoid the applicability of Goal 2 5 by deleting any express references to Goal 5 resources from section 11 of UCDC 3 152.616(HHH).4 In the county's findings for Ordinance 2012-05, the county stated that "Setbacks. The minimum setback shall be a distance of not less than the following: "(1) From a turbine tower to a city urban growth boundary (UGB) shall be two miles, unless a city council action authorizes a lesser setback. The measurement of the setback is from the centerline of a turbine tower to the edge of the UGB that was adopted by the city as of the date the application was deemed complete. "(2) From turbine tower to land zoned Unincorporated Community (UC) shall be 1 mile, unless the landowner of the land zoned UC authorizes by written waiver a lesser setback and the waiver is recorded with the county deed records. "(3) From a turbine tower to a rural residence shall be 2 miles, unless the landowner of the rural residence authorizes by written waiver of a lesser setback and the waiver is recorded with the county deed records. For purposes of this section, a 'rural residence' is defined as a legal, conforming dwelling existing on the parcel at the time an application is deemed complete. The measurement of the setback is from the centerline of the turbine tower to the centerpoint of the residence." (Emphasis and strikethrough in original.) 4 Ordinance 2012-05 provides, in part: "(11) Walla Walla Watershed. "Lands located within the Walla Walla Sub-basin East of Highway 11 shall be subject to additional standards. The purpose of these criteria is to prevent impacts to the following: inventoried Goal 5 resources, highly erodible soils (as defined by the Oregon Department of Agriculture), and federally listed threatened and endangered species, and the Critical Winter Range. The standards are also designed to protect sensitive streams and to be consistent with the Clean Water Act. 7 1 "it does not wish to amend its Goal 5 program and will adopt Section 11 on remand by 2 striking subsections (B) and (D) in their entirety." Subsections (B) and (D) required that 3 an applicant demonstrate that the WPGF would not conflict with "existing Goal 5 4 Resources" and would not "be located within the Critical Winter Range," a specific 5 inventoried Goal 5 resource in the county's comprehensive plan (the plan). At the same 6 time, the county also deleted parts of section 11 that identified the purpose of the 7 regulation as preventing "impacts" to "inventoried Goal 5 resources" and "the Critical 8 Winter Range." The county did not alter remaining subsections of section 11 related to 9 the impacts of WPGFs on highly erodible soils and federally listed threatened and 10 11 endangered species. Petitioner appealed the county's decision adopting the 2012 ordinances to "(A) There shall be no construction of project components, including wind turbines, transmission lines and access roads on soils identified as highly erodible. The highly erodible soils are those soils identified by the Oregon Department of Agriculture as highly erodible. "(B) The application shall demonstrate that the Wind Power Generation Facility and its components, wind turbines, transmission lines, and roads, will not conflict with existing significant Goal 5 Resources within the Walla Walla Sub-basin. "(C) The application shall demonstrate that the [WPGF] and its components will be setback a minimum of two miles from streams and tributaries that contain Federally listed threatened and endangered species, and, that the project will generate no runoff or siltation into the streams. "(D) The application shall demonstrate that the Wind Power Generation Facility and its components will not be located within the Critical Winter Range." (Strikethrough, emphasis, and underscoring in original.) 8 1 LUBA, challenging the amendments to section 6 and section 11 of UCDC 2 152.616(HHH). Petitioner argued, among other things, that Ordinance 2012-05 was 3 adopted to protect Goal 5 resources but the county had failed to address the Goal 5 4 requirements. Petitioner also argued that the two-mile setback and other restrictions on 5 WPGFs in Ordinance 2012-04 were preempted by state laws that encourage and govern 6 renewable energy, an argument petitioner had not raised in his challenge to the two 2011 7 ordinances concerning setbacks for WPGFs. 8 9 In its final order, LUBA affirmed the county's action. LUBA ruled that "the county did not err in failing to apply the Goal 5 rule to the remaining restrictions on 10 developing highly erodible soils and within two miles of streams with federally listed 11 species." In making its determination, LUBA reasoned: 12 13 14 15 16 17 "There is no dispute that highly erodible soils and streams with federally listed species are not inventoried Goal 5 resources in the county. Petitioner argues however that the restrictions on developing on highly erodible soils or within two miles of streams with federally listed species will have the secondary effect of protecting at least some riparian and fish habitat areas that are inventoried Goal 5 resources. 18 19 20 21 22 23 24 25 26 27 28 29 "* * * The county clearly did not intend to protect a significant Goal 5 resource. As the findings supporting Ordinance No. 2012-05 reflect, the county clearly did not intend to adopt any restriction 'in order to protect' any inventoried Goal 5 resource, or as an amendment to the county's program to protect any Goal 5 resource. The county's intent, presumably, was to protect highly erodible soils and federally listed species. The fact that such protections may have the unintended effect of providing additional protection to some of the riparian and fish habitat areas listed in the county's Goal 5 inventory is not sufficient, in our view, to constitute an amendment to 'a portion of an acknowledged plan or land use regulation adopted in order to protect a significant Goal 5 resource,' for purposes of OAR 660-023-0250(3)(a)." 30 In addition, LUBA rejected petitioner's challenge regarding the two-mile 9 1 setback and other restrictions on WPGFs for two reasons. First, LUBA concluded that 2 petitioner's argument was "akin to invited error" because petitioner, in Cosner, had 3 argued that those two waiver provisions to the two-mile setback requirements in 4 Ordinances 2011-05 and 2011-06 were unconstitutional and must be stricken, and the 5 county on remand consequently deleted those waiver provisions because LUBA had 6 found them to be unconstitutional. LUBA concluded that "[p]etitioner cannot argue that 7 the setback reduction provisions are unconstitutional and then, when those provisions are 8 deleted on remand, turn around and argue that the deletion creates conflicts between state 9 statutes and other provisions that were unchallenged in the first appeal." 10 Second, LUBA determined that, even if petitioner's argument was 11 permissible, his argument could have been raised in Cosner, but was not, and therefore 12 was waived under Beck v. City of Tillamook, 313 Or 148, 831 P2d 678 (1992) (holding 13 that, when a record is reopened on remand, the "parties may not raise old, resolved issues 14 again[,]" meaning issues that "LUBA affirmed or reversed on their merits"). In response 15 to petitioner's argument that the waiver doctrine does not apply to legislative land use 16 decisions, LUBA concluded that it had applied that waiver doctrine to legislative 17 decisions, citing DLCD v. Douglas County, 27 Or LUBA 129, 143 (1999), for support. 18 Petitioner seeks judicial review of LUBA's final order regarding 19 Ordinances 2012-04 and 2012-05. We review LUBA's order to determine whether the 20 order is "unlawful in substance or procedure[.]" ORS 197.850(9). Under ORS 21 197.835(7)(a), LUBA is required to reverse or remand an amendment to a land use 10 1 regulation or the adoption of a new land use regulation if "[t]he regulation is not in 2 compliance with the comprehensive plan[.]" 3 Petitioner assigns error to LUBA's determination that the county's 4 protection of federally listed threatened and endangered fish and restrictions on 5 development of WPGFs on highly erodible soils did not require compliance with Goal 5. 6 In petitioner's view, Ordinance 2012-05 adds protections to inventoried Goal 5 resources 7 in the Walla Walla River Sub-basin and therefore, under OAR 660-023-0250(3)(a), the 8 county was required to comply with Goal 5. Petitioner also assigns error to LUBA's 9 determination that he was precluded from challenging the two-mile setback requirement 10 in Ordinance 2012-04. According to petitioner, his argument was neither "invited error" 11 nor waived under the "law of the case" waiver doctrine. We address petitioner's 12 assignments related to each ordinance in turn. 13 14 I. ORDINANCE 2012-05 As previously noted, OAR 660-023-0250(3) sets out three ways in which a 15 PAPA can affect a Goal 5 resource. At issue in this case is OAR 660-023-0250(3)(a), 16 which states that a county is required to comply with Goal 5 if the PAPA amends a "land 17 use regulation adopted in order to protect a significant Goal 5 resource." Petitioner 18 contends that the county adopted Ordinance 2012-05 to protect a significant Goal 5 19 resource and therefore was required to comply with Goal 5. 20 21 In Rest-Haven Memorial Park v. City of Eugene, 175 Or App 419, 424, 28 P3d 1229 (2001), we determined whether an amendment to a land use regulation was 11 1 adopted to protect a city's Goal 5 resource. In that case, the city adopted an ordinance 2 that prohibited pipes or fill material in all of the city's open waterways that provided 3 various storm water benefits, such as water drainage. Id. at 421. The petitioner argued 4 that the city's ordinance was a PAPA that protected a Goal 5 resource because the city's 5 open waterways included drainageways that the city had inventoried as significant Goal 5 6 resources. Id. at 423. We agreed with LUBA that the city's protection of open 7 waterways had significant overlap with the protection of the drainageways. Id. We noted 8 that one of the purposes of the ordinance was to provide interim protection to open 9 waterways, including the drainageways, until the city completed its Goal 5 process. Id. 10 We ultimately concluded that, "[s]o long as one of the purposes of the ordinance was to 11 protect Goal 5 resources and no other provision of the law permits the city's action 12 without compliance with OAR 660-023-0250(3), the [Goal 5] rule is applicable." Id. at 13 424. Thus, to determine whether an amendment to a land use regulation is adopted to 14 protect a Goal 5 resource, we must look to the purpose of the ordinance as guidance. 15 Relying on Rest-Haven, petitioner argues that at least one purpose of the 16 ordinance is to protect Goal 5 resources. In petitioner's view, the county is trying to 17 protect Goal 5 resources by (1) requiring a two-mile setback from "streams and 18 tributaries that contain [f]ederally listed threatened and endangered species"; (2) 19 prohibiting WGPFs to be located on "highly erodible soils"; and (3) protecting "sensitive 20 streams." Petitioner does not argue that "federally listed species" and "highly erodible 21 soils" are themselves inventoried Goal 5 resources, but argues that the restrictions on 12 1 those resources will have a significant effect on fish habitat and vegetative riparian 2 habitat, both of which are Goal 5 resources. We address petitioner's arguments regarding 3 federally listed species and highly erodible soils in turn. 4 A. 5 Federally listed threatened and endangered fish There is no dispute that the county's plan lists fish habitat and riparian 6 vegetation corridors as inventoried Goal 5 resources and that Ordinance 2012-05's 7 express purpose is to prevent impacts to federally listed fish species. However, petitioner 8 contends that Ordinance 2012-05's protection of federally listed species can occur only 9 through the protection of fish habitat, namely, sensitive streams, and so Ordinance 2012- 10 11 05 was adopted to protect Goal 5 resources. To support his argument, petitioner relies on statements in the plan and in 12 the county's Technical Report, which is incorporated in the plan, coupled with references 13 to streams in the ordinance. The Technical Report designates certain fish and wildlife 14 habitats as "sensitive habitat," meaning "a land or water area where sustaining the natural 15 resource characteristics is important or essential to the production and maintenance of 16 fish or wildlife." The plan notes that the Oregon Department of Fish and Wildlife 17 generally considers all riparian vegetation located within 50 feet of a stream bank as 18 "important habitat." In addition, the plan identifies "sensitive areas" for fish production 19 as significant inventoried Goal 5 resources. The Technical Report identifies "sensitive 20 areas" as the "rivers and streams," "lakes, reservoirs and ponds[,]" and "[h]eadwater 21 areas" listed in Table D-XIII of the report. 13 1 Petitioner notes that the introductory paragraph of Ordinance 2012-05 2 states that its standards are designed to protect "sensitive streams," echoing the references 3 to "sensitive" habitat and areas of fish production in the Technical Report and the plan. 4 Petitioner also points to subsection (B) of Ordinance 2012-05, which prohibits runoff to 5 streams and tributaries that contain federally listed fish to support his assertion that the 6 county intended to protect federally listed fish species through protecting stream 7 segments, not through protecting the fish species themselves. 8 Petitioner further contends that there is a substantial overlap between the 9 county's protection of the inventoried fish habitats (sensitive areas) under Goal 5 and the 10 stream segments that contain federally listed fish species under Ordinance 2012-05. To 11 support his argument, petitioner relies on the county's findings for Ordinance 2011-07, 12 remanded by LUBA in Cosner, where the county indicated that the "Walla Walla 13 Watershed contains two species listed under the Endangered Species Act--Bull Trout and 14 Steelhead." According to petitioner, those two federally listed species inhabit segments 15 of the Walla Walla River and Couse Creek, which are inventoried Goal 5 resources. 16 Petitioner argues that Ordinance 2012-05 amended section 11 to protect a significant 17 Goal 5 resource because the ordinance protects a subset of the county's inventoried Goal 18 5 stream segments. 19 In response, the county argues that Ordinance 2012-05 did not amend a 20 land use regulation adopted to protect a significant inventoried Goal 5 resource or to 21 address specific requirements of Goal 5. The county argues that it amended Section 11 of 14 1 152.616(HHH) on remand to delete any reference to inventoried Goal 5 resources and, in 2 its findings, expressly stated that "it does not wish to amend its Goal 5 program." The 3 county contends that, although Ordinance 2012-05 may have an unintended effect of 4 furthering the objectives of Goal 5 by protecting habitat of federally listed species in the 5 Walla Walla Sub-basin, the county did not intend to protect fish habitat resources in their 6 entirety. The county argues that, unlike the ordinance in Rest-Haven that protected open 7 waterways, including all inventoried Goal 5 drainageways, Ordinance 2012-05 does not 8 specifically protect all inventoried Goal 5 fish habitats. Because only a few streams in 9 the Walla Walla Sub-basin contain federally listed fish species, the county asserts that 10 any overlap between protections in the ordinance for federally listed fish species and 11 inventoried Goal 5 fish habitat is de minimis. 12 As noted, whether the county must address Goal 5 pursuant to OAR 660- 13 023-0250(3)(a) when it adopted Ordinance 2012-05 depends on whether the county 14 created or amended a land use regulation in order to protect a Goal 5 resource. We agree 15 with petitioner that the county intended to protect "federally listed threatened and 16 endangered species" by requiring additional standards to protect habitat of federally 17 protected fish species in the Walla Walla Sub-basin. Ordinance 2012-05 specifically 18 states that the additional standards are designed to "protect sensitive streams and to be 19 consistent with the Clean Water Act." However, for a number of reasons, we disagree 20 with petitioner that the ordinance's express reference to sensitive streams triggers the 21 application of Goal 5. 15 1 First, the county specifically stated that its purpose in adopting the 2012 2 ordinance as it was worded was to avoid changes to its Goal 5 program. In its findings 3 on remand for Ordinance 2012-05, the county states that it is "not required to readopt 4 Section 11 in its entirety on remand" and now finds that "it does not wish to amend its 5 Goal 5 program." 6 Second, the county's stated intent is reflected in the changes it made to 7 section 11. The county adopted Ordinance 2012-05 by deleting portions of section 11 8 that listed purposes referring to Goal 5 inventoried resources generally and Critical 9 Winter Range in particular. The county also deleted subsections (B) and (D) of section 10 11 that provided additional standards to prevent impacts to Goal 5 resources and Critical 11 Winter Range. The remaining provisions in section 11 relate only to "federally listed 12 threatened and endangered species" and "highly erodible soils," neither of which are Goal 13 5 resources. As a result, the ordinance amending section 11 does not "create or amend" a 14 land use regulation that directly protects Goal 5 resources 15 Third, Ordinance 2012-05 does not indirectly protect a Goal 5 resource. 16 According to its plain language, the purpose of Ordinance 2012-05 is limited to 17 protecting sensitive streams that contain federally listed fish species and not all sensitive 18 areas in the Walla Walla Sub-basin. The Technical Report, incorporated in the plan, 19 designates sensitive areas for fish protection as inventoried Goal 5 resources, only some 20 of which are "rivers and streams." Within those listed as sensitive streams, only some are 21 within the Walla Walla Sub-basin and contain federally listed fish species. There is no 16 1 indication in the Technical Report that a substantial overlap exists between sensitive 2 streams containing federally listed fish species and the sensitive areas in the Walla Walla 3 Sub-basin. 4 This case is distinguishable from Rest-Haven. In Rest-Haven, we 5 concluded that the city intended to protect a significant Goal 5 resource because the 6 ordinance was specifically designed to protect open waterways that provided various 7 storm water benefits, such as storm drainage, as stated in the city code, and the open 8 waterways included the drainageways that the city had inventoried and identified as 9 significant Goal 5 resources. Id. at 423. Because one of the purposes of the ordinance 10 was to protect significant Goal 5 resources, the city was required to comply with the 11 requirements of Goal 5. Id. at 424. In this case, however, Ordinance 2012-05 does not 12 protect all inventoried fish habitats in the Walla Walla Sub-basin, but rather protects a 13 small subset of that Goal 5 resource. Neither the language of OAR 660-023-0250(3) nor 14 case law supports petitioner's assertion that a county must comply with Goal 5 if an 15 ordinance creates or amends a land use regulation that indirectly affects a small subset of 16 a Goal 5 resource. Unlike in Rest-Haven, the subject of the disputed ordinance in this 17 case does not "'overlap significantly'" with the inventoried Goal 5 resources. See Rest- 18 Haven, 175 Or App at 422 (quoting LUBA's observations as to the relationship between 19 the open waterways protected in the ordinance and the inventoried drainageways). As a 20 result, we conclude that Ordinance 2012-05's protection of federally listed threatened and 21 endangered fish species was not adopted to protect inventoried fish habitat or riparian 17 1 vegetation resources in the county's Goal 5 program. 2 B. 3 Highly erodible soils Petitioner next makes a similar argument that Ordinance 2012-05's 4 protection of highly erodible soils was adopted to protect sensitive streams. According to 5 petitioner, subsection (B)'s requirement of a two-mile setback of WPGFs from streams 6 and tributaries that contain federally listed species and prohibition of runoff and siltation 7 into those steams shows that the ordinance protects sensitive stream segments by 8 preventing erosion from highly erodible soils. Petitioner contends that the Technical 9 Report and the plan suggest that protection of sensitive fish habitat and riparian 10 vegetative habitat occurs partly through prohibiting runoff and siltation into streams. In 11 response, the county argues that because highly erodible soils are not listed as inventoried 12 Goal 5 resources and because Ordinance 2012-05 was not adopted to protect fish habitat 13 resources in their entirety, the ordinance does not protect a Goal 5 resource. 14 We disagree with petitioner's contention that the prohibition on 15 construction of WPGFs on highly erodible soils was adopted to protect fish habitat or 16 riparian vegetation habitat for two reasons. First, under subsection (A) of section 11, the 17 county's absolute prohibition on construction of WPGFs on highly erodible soils applies 18 irrespective of whether those soils are located near streams that contain federally listed 19 fish species. Although subsection (B) of section 11 prohibits runoff and siltation, those 20 restrictions are separate from the restrictions for highly erodible soils. Second, 21 petitioner's contention relies on a series of inferences: highly erodible soils cause erosion 18 1 in streams, federally listed fish reside in some of those streams, streams are fish habitat, 2 and fish habitat is an inventoried Goal 5 resource. Even if the county's protection of 3 highly erodible soils was adopted to protect the habitats of federally listed fish species, it 4 was not adopted to protect even a significant number of inventoried fish habitats. As we 5 previously concluded, Ordinance 2012-05's protection of a small subset of fish habitat is 6 insufficient to establish that the county enacted the ordinance to protect a Goal 5 7 resource. ___ Or App at ___ (slip op at 16-17). Accordingly, we conclude that 8 Ordinance 2012-05 was not adopted to protect a Goal 5 resource and the county was not 9 required to comply with Goal 5. 10 II. ORDINANCE 2012-04 11 Petitioner next assigns error to LUBA's determination that he had waived 12 his argument that the two-mile setback provision in Ordinance 2012-04 was preempted 13 by state statutes regarding renewable energy. To recap, in Cosner, petitioner had argued 14 that the two 2011 ordinances concerning setbacks for WPGFs, which allowed a city 15 council or neighboring landowner to waive the two-mile setback, were unconstitutional, 16 but he did not contend that the setbacks were preempted. Only after the county on 17 remand deleted those waiver provisions from UCDC 152.616(HHH) through adoption of 18 Ordinance 2012-04 did petitioner raise the issue of preemption. Based on petitioner's 19 arguments in Cosner, LUBA concluded that petitioner's preemption argument was either 20 "akin to invited error" or that petitioner waived his preemption argument under the "law 21 of the case" waiver doctrine articulated in Beck. 19 1 We first address waiver and the parties' arguments concerning whether the 2 "law of the case" waiver doctrine applies to the county's legislative land use enactments 3 in this case. Petitioner contends that the "law of the case" waiver doctrine applies to 4 quasi-judicial decisions, not legislative action. In Beck, the Supreme Court determined 5 the scope of judicial review of LUBA's land use decision when the petitioners, in an 6 earlier proceeding, had appealed a local land use decision to LUBA, prevailed in part and 7 received a remand back to the local government, and later appealed the local 8 government's new decision on remand to LUBA. 313 Or at 150. In deciding the scope of 9 judicial review, the Supreme Court initially determined whether the petitioners' second 10 appeal was part of the same case as the earlier proceeding. Id. at 151. The court held 11 that, in a quasi-judicial proceeding, when (1) a local government decision is appealed to 12 LUBA, (2) LUBA issues an order remanding that decision, (3) the local government 13 conducts a further proceeding and issues a new order, and (4) the new decision is 14 appealed to LUBA, then the two LUBA appeals are "two phases of the same case." Id. 15 The Supreme Court then addressed whether appellate courts can review issues that 16 LUBA decided in the same case but that were not challenged in the first appeal to LUBA. 17 The Supreme Court held that, when LUBA remands a case for further proceedings, the 18 parties are limited to "new, unresolved issues" relating to those remand instructions and 19 cannot raise any "issues that LUBA affirmed or reversed on their merits, which are old, 20 resolved issues." Id. 21 In support of its holding, the Supreme Court relied on four statutes. First, 20 1 the Supreme Court stated that the effect of former ORS 197.835(9) (1992), renumbered 2 as ORS 197.835(11) (1995) ("[T]he board shall decide all issues presented to it when 3 reversing or remanding a land use decision."), was that the local government's authority 4 on remand was limited to addressing issues that require further exploration. 313 Or at 5 151-52. Second, the court relied on ORS 197.850(1) ("Any party to a proceeding before 6 [LUBA] * * * may seek judicial review of a final order issued in those proceedings.") for 7 the proposition that a party may seek judicial review of all of LUBA's final orders, 8 including orders remanding land use decisions. Id. at 152-53. Third, the Supreme Court 9 determined that the effect of ORS 197.763(7) ("When a local governing body * * * 10 reopens a record to admit new evidence or testimony, any person may raise new issues 11 which relate to the new evidence[.]"), a statute governing quasi-judicial hearings, was 12 that when a record is reopened on remand, a party may raise "new, unresolved issues" 13 that relate to new evidence. Id. at 153. Lastly, the Supreme Court concluded that the 14 effect of former ORS 197.830(10) (1992) ("Issues [before LUBA] shall be limited to 15 those raised by any participant before the local hearings body" as provided in ORS 16 197.763.)5 was that, if a record is reopened on remand, then a subsequent appeal to 17 LUBA is limited to "new, unresolved issues" raised on remand, not issues that LUBA 18 "affirmed or reversed" in the earlier appeal. Id. at 153-54. Under Beck, a petitioner in a 5 In 1995, the legislature removed that language from ORS 197.830(10) (1992), amended by Or Laws 1995, ch 595, § 3. However, in 1995, the relevant language in ORS 197.830(10) (1992) could also be found in ORS 197.835(3) ("Issues shall be limited to those raised by any participate before the local hearings body as provided by ORS 197.915 or 197.763."). 21 1 quasi-judicial proceeding is required to appeal issues to LUBA in the first instance, 2 without waiting to raise them in a subsequent appeal of the local government's decision 3 on remand. 4 Petitioner argues that, because the underlying proceeding in this case was 5 legislative and not quasi-judicial, LUBA is not precluded from reviewing his preemption 6 argument on the merits. Petitioner does not attempt to distinguish the Supreme Court's 7 holding in Beck. Instead, petitioner makes a statutory argument. Petitioner cites ORS 8 197.835(11)(a) for the proposition that LUBA is required to "decide all issues presented 9 to it." Petitioner also cites ORS 197.835(3) ("Issues [before LUBA] shall be limited to 10 those raised by any participant before the local hearings body as provided by ORS 11 197.195 [(limited land use decisions)] or 197.763 [(local quasi-judicial land use 12 hearings)], whichever is applicable.").6 In petitioner's view, that statute's limitation of 6 The statute cited by petitioner, ORS 197.835(3), contains the same statutory language the Supreme Court relied on in Beck. However, ORS 197.835(3) and, by incorporation, ORS 197.763, together establish a modified "raise it or waive it" doctrine, another waiver doctrine created by statute. The "raise it or waive it" rule requires parties to preserve issues in local proceedings. Pliska v. Umatilla County, 240 Or App 238, 244, 246 P3d 1146 (2010), rev den, 350 Or 408 (2011). LUBA has recognized that the rule "represents a quid pro quo" whereby local governments must, among other things, give "broader and more detailed notice of [quasi-judicial land use] hearing[s] * * * and making evidence * * * and staff reports available" and, in exchange, participants are required to raise issues during the local proceedings to be able to raise those issues in an appeal before LUBA. 1000 Friends of Oregon v. Benton County, 20 Or LUBA 7, 10 (1990); see also Morsman v. City of Madras, 196 Or App 67, 76, 100 P3d 761 (2004) (holding that a petitioner who had not received notice as required by ORS 197.763(1) was relieved of the requirement under the "raise it or waive it" doctrine to raise constitutional issues before the city). LUBA also has recognized that the "raise it or waive it" waiver doctrine in ORS 197.835(3) and ORS 197.763 applies only to local government quasi-judicial proceedings and not to legislative land use proceedings, see 22 1 LUBA's scope of review to issues that the parties raised to the local government 2 expressly and solely applies to quasi-judicial proceedings and limited land use decisions. 3 In response, the county argues that the Supreme Court's holding in Beck is broad enough 4 to apply to both legislative land use decisions and quasi-judicial proceedings and that 5 petitioner's distinction is untenable. 6 In its order, LUBA stated that it has applied Beck or the "law of the case" 7 waiver doctrine to legislative decisions, citing DLCD v. Douglas County, 37 Or LUBA 8 129, 143 (1999) (noting that the petitioner's failure to challenge the county's population 9 projection in the first appeal precluded a challenge to that issue on a subsequent appeal of 10 the county's decision on remand). We note, however, that the county has not cited, nor 11 have we found, any other LUBA opinions that have applied the "law of the case" waiver 12 doctrine to legislative decisions. Instead, LUBA has applied that waiver doctrine 13 numerous times to appeals in quasi-judicial cases. It appears that, except for this case, 14 LUBA's decision in Douglas County is unique. And neither this court nor the Oregon 15 Supreme Court has applied Beck or the "law of the case" waiver doctrine to legislative DLCD v. Columbia County, 24 Or LUBA 32, 36 (1992) (stating that the "raise it or waive it" principle does not apply to legislative proceedings); Parmenter v. Wallow County, 21 Or LUBA 490, 492 (1991), aff'd, 114 Or App 362, 835 P2d 152, rev den, 314 Or 574 (1992) (same); Roads End Sanitary District v. City of Lincoln City, 48 Or LUBA 126, 129 (2004) (same), a distinction that we conclude also applies to the "law of the case" waiver doctrine at issue in this case, as we later discuss in more detail. We also note that the "raise it or waive it" doctrine is inapplicable in this case, either because there was no requirement to raise the preemption issue before the county to preserve the issue for appeal to LUBA or because petitioner actually raised the preemption issue before the county on remand from LUBA. 23 1 2 land use decisions; thus, we decide a case of first impression in Oregon. We conclude that there are three problems with LUBA's application of the 3 "law of the case" waiver doctrine in this case. As previously noted, in Beck, the Supreme 4 Court concluded that the two successive appeals of two quasi-judicial land use decisions 5 in that case were "two phases of the same case." 313 Or at 151 (emphasis added). But 6 this appeal is not in the same case as the appeal in Cosner. After LUBA remanded 7 Ordinances 2011-05 and 2011-06 to the county in Cosner, the county adopted Ordinance 8 2012-04. Like Ordinances 2011-05 and 2011-06, Ordinance 2012-04 amends section 6 9 of UCDC 152.616(HHH) by establishing a two-mile setback for WPGFs from any urban 10 growth boundary or rural residences. However, Ordinance 2012-04 is different; it does 11 not include the two waiver provisions that LUBA determined to be unconstitutional in 12 Cosner. And, Ordinance 2012-04 is a new piece of legislation that the county adopted 13 instead of amending and readopting Ordinances 2011-05 and 2011-06. Petitioner's 14 appeal of the new ordinance to LUBA is a different and separate challenge from 15 petitioner's earlier appeal of Ordinances 2011-05 and 2011-06 in Cosner. 16 Second, the statutory framework that the Supreme Court relied on in Beck 17 does not apply to legislative land use decisions. In a quasi-judicial or limited land use 18 proceeding, by virtue of LUBA's scope of review in ORS 197.835(11), after the local 19 government reopens the hearing on remand from LUBA, the parties may only raise new, 20 unresolved issues that relate to the basis of LUBA's remand. See Beck, 313 Or at 152 21 ("The effect of ORS 197.835(9) [renumbered as ORS 197.835(11)(1995)] is to allow 24 1 LUBA to narrow the scope of remand to those issues that require further exploration."). 2 For legislative proceedings, there is no equivalent statute that requires a local government 3 to have hearings for legislative decisions or to follow certain procedures for legislative 4 hearings after LUBA has remanded a legislative land use decision.7 Thus, after LUBA 5 remands a legislative decision, the local government can choose to amend its ordinance to 6 address LUBA's remanded issues, can choose to adopt a completely new ordinance, or 7 can choose not to adopt any ordinance. 8 9 Third, the Supreme Court's rationale that supported its holding in Beck does not necessarily apply to a legislative decision. In Beck, the court determined that the 10 effect of allowing LUBA to narrow the scope of remand was to "avoid redundant 11 proceedings" and to facilitate the legislative policy that "'time is of the essence in 12 reaching final decisions.'" 313 Or at 152 (quoting ORS 197.805). Therefore, to ensure 13 that land use decisions would reach finality quickly, by not having them decided 14 piecemeal, the court required a petitioner to raise issues before LUBA in the first instance 15 instead of raising those issues after LUBA remands a land use decision. 16 However, there is an important distinction between the legislative decision- 17 making process and quasi-judicial proceedings. Generally, in quasi-judicial proceedings, 18 the local government must address issues presented by an applicant regarding the 19 applicant's property. Unlike a quasi-judicial decision, a legislative decision is not 7 However, in this case, the county's development code does provide public hearings for amendments to its development code. See UCDC 152.771. 25 1 initiated by an applicant and instead is, generally, initiated by the local governmental 2 body. Thus, in the legislative process, the local government is not necessarily required to 3 make a particular decision or to adopt a particular ordinance, whereas, in a quasi-judicial 4 proceeding, the local government is required to make a final decision on all issues 5 presented by the applicant. The practical implication of that distinction relevant to this 6 case is the difference in the scope of a local government's authority on remand depending 7 on whether the matter is a quasi-judicial proceeding or a legislative decision. 8 After LUBA's remand of a quasi-judicial decision, when the local 9 government reopens the hearing, the issues narrow. Beck, 313 Or at 152. In the 10 legislative process, in contrast, the local government has a broad scope of authority on 11 remand. The local government's decision can apply to a large number of properties and 12 people, and on remand, the local government may take any number of actions and may 13 apply legislative priorities or considerations different than those used in developing the 14 initial legislation. In some situations, the local government may decide not to adopt any 15 ordinance. Thus, the principle of finality that the law of the case doctrine promotes does 16 not apply in the way that it does to quasi-judicial proceedings. We therefore conclude 17 that the "law of the case" waiver doctrine does not apply to legislative land use decisions. 18 We now turn to whether petitioner's preemption argument is precluded by 19 the "invited error" doctrine. Under that doctrine, "a party who was actively instrumental 20 in bringing about an alleged error cannot be heard to complain, and the case ought not to 21 be reversed because of it." State v. Kammeyer, 226 Or App 210, 214, 203 P3d 274, rev 26 1 den, 346 Or 590 (2009) (internal quotation marks omitted). Petitioner first argues that he 2 is not precluded by the "invited error" doctrine because that doctrine applies to actions in 3 trial courts, not to administrative proceedings, an argument we reject. See Teamsters 4 Local Union #223 v. Lake County, 208 Or App 271, 278-79, 145 P3d 187 (2006) 5 (applying the doctrine to the petitioner's conduct before the administrative law judge). 6 However, we agree with petitioner that, if the doctrine applies, he did not invite any error 7 through his conduct in Cosner. 8 9 In Cosner, petitioner argued that the 2011 ordinances allowing city councils or private landowners to waive the two-mile setback requirement were an 10 unconstitutional delegation of legislative authority. In other words, petitioner sought to 11 invalidate the two provisions, not force the county to adopt an absolute two-mile setback 12 requirement. After LUBA remanded the 2011 ordinances, the county chose to adopt a 13 new ordinance, Ordinance 2012-04, which imposed an absolute two-mile setback, but the 14 county was not required to do so. In fact, the county had the authority to adopt an 15 entirely new setback requirement or to delegate the waiver to another agency. See 16 Cosner, ___ Or LUBA at ____ (slip op at 7) ("[I]t is possible that modest changes in the 17 terms of Ordinance 2011-05 and 2011-06 could avoid any impermissible delegation. For 18 example, the legislature can delegate, at least to another agency of government[.]"). For 19 that reason, we conclude that petitioner's challenge in Cosner did not invite the error that 20 petitioner now challenges in this case. Accordingly, petitioner is not precluded from 21 raising his preemption challenge to the new setback requirement in UCDC 27 1 152.616(HHH), and we remand to LUBA to allow it to decide the issue in the first 2 instance. 3 Affirmed in part, reversed in part, and remanded. 28

Some case metadata and case summaries were written with the help of AI, which can produce inaccuracies. You should read the full case before relying on it for legal research purposes.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.