People's Counsel v. Elm Street Development, Inc.

917 A.2d 166, 172 Md. App. 690, 2007 Md. App. LEXIS 21
CourtCourt of Special Appeals of Maryland
DecidedMarch 2, 2007
Docket9 September Term, 2006
StatusPublished
Cited by1 cases

This text of 917 A.2d 166 (People's Counsel v. Elm Street Development, Inc.) is published on Counsel Stack Legal Research, covering Court of Special Appeals of Maryland primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
People's Counsel v. Elm Street Development, Inc., 917 A.2d 166, 172 Md. App. 690, 2007 Md. App. LEXIS 21 (Md. Ct. App. 2007).

Opinion

*694 KRAUSER, Judge.

Appellants are People’s Counsel for Baltimore County; Maryland Line Area Association; Richard McQuaid; and Marion V. Runkles, III. 1 Appellees are Elm Street Development, Inc. (“Elm Street”) and Baltimore County. The Baltimore County Board of Appeals approved Elm Street’s development plan for a parcel of land known as the “Miller-Tipper property,” based in part on two County agencies’ recommendations that the plan complied with the relevant zoning regulations. When the Circuit Court for Baltimore County affirmed the decision, appellants noted this appeal, arguing that the Board erred in not requiring the County agencies to lay out the “facts and reasons” behind their recommendations. Appellants also noted an appeal regarding a related development plan from Elm Street.

To fully understand the questions raised on appeal, a brief review of the Baltimore County plan approval process is required before we proceed with our analysis.

PLAN APPROVAL PROCESS

In Baltimore County, the process of obtaining approval for a development plan begins with the filing of a concept plan which, among other things, “[generally complies] with county regulations and standards” and which will be reviewed at a Concept Plan Conference involving the developer and the relevant County agencies. Baltimore County Code (2003) §§ 32-4-211 — 32-4-216. After that review, the Department of Permits and Development Management (“PDM”) holds a Community Input Meeting to allow “Resolution of community concerns and developer constraints within the context of ... county regulations and policies.” Code § 32-4-217. Participants may include “representatives of the county, the [developer], owners of adjacent property, and representatives of local community associations or umbrella groups.” Code *695 § 32-4-101(l). Any relevant comments raised or conditions proposed that are not resolved at the Community Input Meeting must be “[a]ddress[ed]” by the appropriate agency and submitted to the hearing officer. Code § 32-4-217(e)(3). Only after participating in the Community Input Meeting can the developer file a development plan. Code § 32-4-221.

The development plan must not be “inconsistent” with the concept plan unless the inconsistencies are “related to the outcome of the [CJommunity [IJnput [MJeeting.” Code § 32-4-225. Otherwise, another Community Input Meeting must be held on the plan. Id.

The development plan, too, must undergo a process of review. As part of that review, County representatives must visit the property involved. Code § 32-4-226(a). And County agencies, such as PDM, the Office of Planning, and the Department of Environmental Protection and Resource Management (“DEPRM”), must review the plan for compliance with County regulations. Code § 32-4-226(b). After that has occurred, the developer and the relevant County agencies attend a Development Plan Conference, which the Community Input Meeting participants may also attend. Code § 32-4-226(c)(1). The Development Plan Conference provides the parties with an opportunity to resolve “any conflict between agency comments” and “any comments raised or conditions proposed at the [CJommunity [IJnput [MJeeting.” Code § 32-4-226(c)(2). These comments and conditions are available to the public upon request. Code § 32-4-227(c)(3).

Finally, after the Development Plan Conference is held, the plan goes before a hearing officer for a “public quasi-judicial hearing.” Code § 32-4-227(a). Before the hearing, the County agencies must submit, among other things, any agency comments on the development plan as well as agency responses to any “unresolved comments raised or conditions proposed or requested” at the Community Input Meeting. Code § 32-4-226(d). During the hearing, the hearing officer is required to “consider any comments and conditions submitted by a county agency,” Code § 32-4-227(e)(1), and to “take testimony *696 and receive evidence regarding any unresolved comment or condition,” Code § 32-4-228(a)(1). But, “[i]f no comments or conditions are received by the [h]earing [ojfficer,” the development plan “shall be considered to be in compliance with county regulations.” Code § 32-4-227(e)(2).

The hearing officer then issues a “final decision” on the development plan. Code § 32-4-229(a)(1). The hearing officer “shall grant approval” of a development plan which “complies with these development regulations and applicable policies, rule and regulations.” Code § 32-4-229(b)(1). The hearing officer’s final decision may be appealed to the Board. Code § 32-4-227(b)(2). The Board’s decision, in turn, may be reviewed by the circuit court. Maryland Rule 7-202.

ELM STREET’S REVISED RED-LINED DEVELOPMENT PLAN

Elm Street sought to develop the approximately 72.47 acre Miller-Tipper property into a residential subdivision of 14 single-family dwellings. Because the property was zoned RC-4 under the Baltimore County Zoning Regulations (1998) (“BCZR”), the development plan for the property had to designate a “minimum of 70%” of the property as a “conservancy area.” BCZR § 1A03.5. The conservancy area was to include certain “features,” such as wetlands and steep slopes, to be developed “as determined by the standards contained in the Comprehensive Manual of Development Policies;” the Director of the Office of Planning and the Director of DEPRM were to determine whether these requirements were met. BCZR § 1A03.5(A). Under the BCZR, the property was also required to be “held in unified ownership and control.” BCZR § 1A03.5(C). Before work could commence on the property, Elm Street had to obtain the County’s approval of its development plan.

In accordance with the County’s procedures, Elm Street filed a concept plan for the property. After it was reviewed at the Concept Plan Conference, a Community Input Meeting was held which allowed residents of the locality to review and *697 comment on the proposal. Elm Street then submitted a development plan to PDM, which was reviewed by the County agencies and discussed at the Development Plan Conference. Finally, the plan was submitted to the hearing officer — the County Zoning Commissioner — for a decision. During the ensuing three-day hearing before the hearing officer, County agencies and members of the community had the opportunity to comment on the plan and suggest conditions to be imposed upon it.

At that time, PDM, the Office of Planning, and DEPRM expressed concern that the property had two conservancy areas with two different owners, which they claimed was prohibited in an RC-4 zoned property. The hearing officer agreed and determined, among other things, that the “two conservancy areas proposed in this case, under different ownership, are simply not permitted,” absent “compelling factors,” under § 1A03.5(C). He therefore denied approval of the development plan as well as Elm Street’s subsequent request that he reconsider that decision.

Elm Street appealed the hearing officer’s decision to the Board.

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

Related

Neal v. CRIMINAL INJURIES COMPENSATION BOARD
993 A.2d 175 (Court of Special Appeals of Maryland, 2010)

Cite This Page — Counsel Stack

Bluebook (online)
917 A.2d 166, 172 Md. App. 690, 2007 Md. App. LEXIS 21, Counsel Stack Legal Research, https://law.counselstack.com/opinion/peoples-counsel-v-elm-street-development-inc-mdctspecapp-2007.