Reno council denies Mount Rose Junction zoning change after neighbors, planners cite missing details

Reno City Council on Sept. 24 voted unanimously to deny a request to reclassify a 0.99-acre parcel on the west side of Plumas Street near Mount Rose from multifamily residential (MF-14) to a Specific Plan District (SPD) that would increase height and density and allow up to 39 units.

The council action upheld the Planning Commission’s earlier technical denial and followed months of neighborhood opposition and repeated staff requests for a more specific plan. Planning Manager Mike Raley told the council that the SPD handbook submitted by the applicant included only a conceptual site plan and did not lock in the details—setbacks, circulation, parking and building placement—that staff and the commission say are required to satisfy the heightened scrutiny an SPD demands.

“That site plan is a concept only,” Raley said. “There is nothing to require that to be developed. The planning commission was not comfortable because of that lack of specificity.”

Brook Oswald, representing Park Real Estate Partners, the project applicant, told the council the site is one of the rare vacant infill acres inside McCarran and argued the project would add housing and support nearby businesses. Oswald said the developer was willing to work with staff on a revised SPD handbook and that the proposed design included increased setbacks along the south property line, landscaping, sustainability elements and parking at the code-required minimum.

But residents and the ward Neighborhood Advisory Board expressed consistent objections during public comment and at Planning Commission hearings. Neighbors told the council the 3-story height and proposed density were out of scale with the Plumas Neighborhood Overlay, which generally limits building height to 25 feet and favors lower-density forms. Speakers described narrow neighborhood streets, limited parking, aging sidewalks and a lack of pedestrian facilities around the site and said the developer had not provided a neighborhood meeting or sufficient, fixed project details for review.

“Three-story structures are completely incompatible with the character of the neighborhood,” said resident Lynn Devine. “We have a lot of children and a lot of dogs. This is a safety concern.”

The Planning Commission’s staff report recommended denial, citing lack of a specific plan to evaluate impacts and an SPD that could be interpreted as a workaround of the Plumas overlay. At the council meeting, Councilwoman Doer moved to uphold the commission’s recommendation; the motion passed with all members present voting yes.

What the council approved (by denying the SPD request) was not a prohibition on development at the site. Under the code the property still can be developed consistent with its existing MF-14 zoning, which allows multifamily at 14 units per acre and has its own development standards. Several speakers and council members said the neighborhood could reasonably expect an increase in units under the existing zoning, but that a larger rezoning to SPD required more concrete commitments from the applicant before approval.

Council discussion repeatedly returned to the same point: the SPD process is intended to allow flexibility in exchange for binding, site-specific public benefits and development standards. Raley and multiple council members said the application lacked sufficient binding detail and a process for community input tied to the standards. Councilwoman Durer, who moved the denial, said the applicant could return with a substantially revised SPD that included a required project plan, modified development standards and a plan amendment process before the Planning Commission and council.

The council’s votes on Sept. 24 included three related ballot items that together would have implemented the rezoning: a master plan amendment, an SPD handbook adoption and a zoning map amendment. All three actions failed to gain approval because the council adopted the Planning Commission recommendation to deny the request.

Looking ahead, staff told the council how the applicant could proceed: submit a detailed project plan, include a binding site-specific SPD handbook (with the required site plan, setbacks, circulation, parking and architectural requirements), and re-notice the project for planning and public review. If the applicant does so and addresses the outstanding concerns, the matter can return to the Planning Commission for a fresh recommendation to council.

Neighbors who opposed the application said they welcomed further engagement in a reworked proposal. Several council members urged both sides to meet and seek a solution that allowed new housing while protecting neighborhood character, pedestrian safety and parking.

The denial leaves the property governed by the current MF-14 zoning and Plumas Neighborhood Overlay. The applicant may submit a substantially different application in the near term or wait 12 months to propose a substantially similar SPD application, per code requirements on resubmittal after denial.

Ending: The council’s unanimous denial underscored a recurring theme at this hearing: when applicants ask for departures from overlay or base zoning rules via an SPD, the council and staff expect a clear, enforceable plan that crystallizes exactly what will be built and what neighborhood benefits will be delivered. The applicant and neighborhood now have a clearer path — but it will require more detailed, binding commitments to win the council’s approval.