Apalategui v. Washington County

723 P.2d 1021, 80 Or. App. 508
CourtCourt of Appeals of Oregon
DecidedAugust 6, 1986
DocketLUBA 85-043, 85-044, & 85-045; CA A39012
StatusPublished
Cited by4 cases

This text of 723 P.2d 1021 (Apalategui v. Washington County) is published on Counsel Stack Legal Research, covering Court of Appeals of Oregon primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Apalategui v. Washington County, 723 P.2d 1021, 80 Or. App. 508 (Or. Ct. App. 1986).

Opinion

*510 WARDEN, P. J.

Petitioners in these consolidated cases seek review of an order of the Land Use Board of Appeals (LUBA) which rejected some of their challenges to three Washington County ordinances. The ordinances amended the county’s comprehensive plan, community development (zoning) code (CDC) and comprehensive plan maps. The county cross-petitions, seeking review of LUBA’s action in sustaining some of petitioners’ other challenges. We affirm on the petitions and reverse and remand in part on the cross-petition. 1

Many of the issues in this case arise from Washington County’s peculiar procedures for adopting and amending land use ordinances. Under the county charter, changes to the comprehensive plan, zoning code or specific zoning designations require individual notices to affected property owners and others in possession of the affected property. The notices must describe in detail the effect that the proposed changes will have on the recipient’s property. The requirements are cumbersome for plan or zoning changes which would affect more than individual parcels or small, specific areas within the county.

As an alternative, the charter permits the county to make land use changes by adoption of not more than three ordinances a year, sending only a more general notice to all affected owners. Each of these “annual ordinances” may *511 concern changes within only one of three categories: adoption or amendment of a comprehensive plan; re-zoning of property; or adoption or amendment of a zoning code. 2 An annual ordinance must be filed and available for public inspection no later than August 1 and must receive its first reading at a Board of County Commissioners’ meeting in November. In practice the general notice describing these ordinances is enclosed with the property tax statements mailed in October. The Board may amend the ordinances if the notice informed property owners affected by the amendment that the ordinance would affect their property. The mailing of proper notice is essential to the validity of the ordinances. Wash Co Charter, §§ 100(c),(d); 102; 103.

As one would expect, and as they were apparently intended to do, the charter requirements create difficulties for county planners and for the Board. They must consolidate significant plan and zoning changes into not more than three single-purpose ordinances. They must file the ordinances in July but cannot consider them until November. It is likely that what is proposed in July may or may not be exactly what is considered in November, and there is a substantial probability that changes in a proposal will be made before ultimate adoption of the ordinance. 3

The county knew in July, in a general way, what geographical areas it wished to consider for plan modifications and what changes it wished to make in the CDC. Work on those matters was not complete, however, and the three ordinances it filed on July 31, 1984, only outlined the intended changes. For instance, Ordinance 292, as filed, listed five geographical areas for which the county intended to revise the comprehensive plan; it also referred to other, undefined, necessary revisions. Ordinance 294 proposed modifications in the comprehensive plan maps to conform to the changes made by Ordinance 292; it necessarily had the same lack of definiteness as did Ordinance 292. Ordinance 293 proposed a *512 number of changes in the CDC. As ultimately adopted, Ordinances 292 and 294 applied to only four of the original five geographical areas and made changes in the plan in other areas not originally listed. Ordinance 293 made changes in the CDC which had not been included in the original proposal.

The “General Notice of Land Use Change” mailed to all property owners in October described the general subject matter of each ordinance and stated that it was impossible to give a complete description of the effects of the ordinances. The introductory portion of the notice gave the date on which the Board would first consider the ordinances and warned recipients that they would not receive additional mailed notices. It included the following statement:

“PLEASE NOTE: THE FOLLOWING DESCRIPTIONS ARE GENERAL AND ARE BASED ON CURRENT INTENT. PRIOR TO FINAL ADOPTION, THE BOARD WILL HEAR TESTIMONY. BASED ON THIS TESTIMONY, THE BOARD WILL LIKELY CONSIDER SUBSTANTIAL AMENDMENTS TO THESE ORDINANCES WHICH MAY AFFECT YOUR PROPERTY. THEREFORE, EVEN IF YOUR PROPERTY IS NOT AFFECTED BY THESE ORDINANCES AS INTRODUCED, SUBSEQUENT AMENDMENTS MAY AFFECT YOU.”

As the county’s charter requires, the Property Rights Commission approved the notice.

Before considering the parties’ contentions concerning various procedural requirements, we first consider the county’s challenge to petitioners’ standing. ORS 197.830(3) establishes the requirements which must be met by a person who wishes to appeal a quasi-judicial land use decision to LUBA. 4 The crucial question is whether petitioners were *513 “aggrieved” by the county’s decision. In Jefferson Landfill Comm. v. Marion Co., 297 Or 280, 284, 686 P2d 310 (1984), the Supreme Court established a three-part test for determining when someone is aggrieved: whether the local body has recognized the person’s interest in the decision, whether the person has asserted a position on the merits and whether the local body’s decision was contrary to the position which the person asserted. 5

Petitioners were clearly aggrieved under that test. Indeed, the county does not seriously contest their standing on some issues. Rather, it asserts that petitioners may not assign as error matters which they did not raise during the county’s consideration of the ordinances. In this argument the county misunderstands the nature of the standing requirement. Standing concerns whether a party may bring a case to court — or, in this context, before an administrative appeals board — at all. Standing does not turn on whether the party has preserved particular issues. Petitioners have standing. If the county’s real point is that petitioners may seek LUBA review only of issues which they raised in the local proceedings, we rejected an identical contention in Lane County v. City of Eugene, 54 Or App 26, 32-3, 633 P2d 1306 (1981), construing the predecessor of ORS 197.830(3), see n 5, supra, in the context of former Oregon Laws 1979, ch 772. We concluded that “it is not necessary for the party seeking LUBA review to have raised below the issues on which review is sought.” (Footnote omitted.) We reject the county’s assignment on the standing question.

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

Related

Trautman v. City of Eugene
383 P.3d 420 (Court of Appeals of Oregon, 2016)
Hausam v. City of Salem
37 P.3d 1039 (Court of Appeals of Oregon, 2001)
1000 Friends of Oregon v. Lane County
793 P.2d 885 (Court of Appeals of Oregon, 1990)
Newcomer v. Clackamas County
758 P.2d 369 (Court of Appeals of Oregon, 1988)

Cite This Page — Counsel Stack

Bluebook (online)
723 P.2d 1021, 80 Or. App. 508, Counsel Stack Legal Research, https://law.counselstack.com/opinion/apalategui-v-washington-county-orctapp-1986.