Decision

The ordinance says the City Council approved Specific Plan Amendments as depicted in Exhibit E, a Development Agreement as depicted in Exhibit F, and a Planned Development Permit as depicted in the project plan set attached as Exhibit G, subject to Conditions of Approval attached as Exhibit H.

The February 18, 2026 City Council minutes list Ordinance No. 2026-02 as a second-reading-and-adoption consent item. The minutes state that the ordinance had been approved on January 28, 2026 with a 4/1 vote, with Martinez voting no.

Project Context

The ordinance says a land-use development application was filed on April 1, 2024 on behalf of Kingsbarn Realty Inc. It describes the project as construction of 128 multi-family units on a 1.04 gross acre site at 137 W. Valley Parkway, APN 229-421-26-00, in the Specific Planning Area 9 General Plan land use designation and Specific Plan zone.

The ordinance describes requests for a Specific Plan Amendment, Development Agreement, Planned Development Permit, and Design Review Permit. This page does not publish map metadata, parcel boundaries, private-property access guidance, current construction conditions, current sales, or current occupancy.

Prior Review

The ordinance says the Planning Commission held a public hearing on November 18, 2025 and adopted Resolution No. 2025-10 recommending that the City Council approve the project's Specific Plan Amendment, Development Agreement, and Planned Development Permit.

This page does not summarize the Planning Commission record, Resolution No. 2025-10, the January 28, 2026 City Council staff report, City Council Resolution No. 2026-12, agreement terms, conditions of approval, or any later permitting record.

The February 18 minutes verify the recorded consent-item context for Ordinance No. 2026-02. They do not provide the full ordinance text, resolution text, agreement terms, condition text, current entitlement status, current construction status, sales, occupancy, parking availability, agreement recordation, condition compliance, or later project status.

Specific Plan Language

Exhibit E to the ordinance says the Specific Plan Amendments repeal and replace Downtown Specific Plan figures or tables to permit ground-floor residential uses subject to a Planned Development Permit on the subject property, establish a height overlay on the subject property, remove municipal parking Lot 1 as a municipal parking lot, and permit properties within the Height Overlay Area to build up to 65 feet and a maximum of five stories.

That statement is recorded here only as ordinance text. Check the current Downtown Specific Plan, municipal-code records, City Clerk records, later amendments, parking records, and project records before relying on current plan language, current parking-lot status, development rights, or legal interpretation.

Parking Finding

Exhibit D to the ordinance says the project includes redevelopment of a municipal parking lot that provides 118 public off-street parking spaces. It says a parking study found approximately 42 percent of the 2,339 off-street parking spaces in a 16-block study area were occupied during the peak hour, and that the City determined the property was not necessary for public parking use because demand could be accommodated nearby and other public parking lots remained available downtown.

That statement is recorded here only as an ordinance finding. This page does not state current parking availability, current lot status, construction staging, traffic or parking advice, or legal interpretation.

Environmental Review Statement

The ordinance says the City Council adopted a Fifth Addendum and revised Mitigation Monitoring and Reporting Program and instructed staff to file a Notice of Determination with the County Clerk.

That statement is recorded here only as ordinance text. This page does not provide CEQA analysis, legal interpretation, agreement interpretation, entitlement advice, appeal guidance, mitigation-compliance status, Notice of Determination status, or litigation status.

Reviewed pages that connect this item to nearby places, organizations, records, or topics.

Evidence and maintenanceReferences, source dates, and review trail

References, source snapshots, and audit notes are kept here for readers who want to verify the page or maintain it later.

Good to know

Use this page as a sourced starting point for understanding the reviewed civic record, key source dates, and related public-decision context.

  • Check a current source before relying on current project status, condition compliance, construction, sales, occupancy, public-parking availability, current plan/code effect, current law,...

Change and source dates

Latest page update
2026-06-12
Latest source check
2026-05-26
Source snapshot
2026-05-24T21:36:59-07:00

A newer source should be checked before changing current status, access, roles, schedules, or practical details.

References and audit trail

References

  1. Ordinance Number 2026-02
    City of Escondido · ordinance · retrieved 2026-05-24T21:36:59-07:00 · Origin
  2. Escondido City Council minutes for February 18, 2026
    City of Escondido · meeting-minutes · published 2026-02-18 · retrieved 2026-05-24T22:04:40-07:00 · Origin

Source Notes

The source for this page is the official Ordinance No. 2026-02 PDF linked from the City Council Adopted Ordinances page and retrieved on May 24, 2026. The source can support ordinance-stated decision context, but it should not be treated as a current project-status source, a current Specific Plan source, a parking-availability source, or a complete municipal-code record.

The February 18, 2026 City Council minutes add minutes-recorded consent-item context for Ordinance No. 2026-02. They should not be used as a substitute for Resolution No. 2025-10, City Council Resolution No. 2026-12, the staff report, agreement records, conditions of approval, or later project records.

Check approved minutes, Resolution No. 2025-10, City Council Resolution No. 2026-12, the January 28, 2026 staff report, planning records, permit records, building records, Downtown Specific Plan records, parking records, recorded agreement records, municipal-code records, and later official updates before relying on current status, conditions, construction, sales, occupancy, current parking availability, current plan/code effect, codification status, agreement meaning, or legal interpretation.