Tehachapi — Zoning

Last reviewed: July 2, 2026

Overview

This page summarizes what the City of Tehachapi's adopted Zoning Code (the Form‑Based Zoning Code) actually requires about zoning districts, the official zoning map, and the district‑level rules you must use when planning a project. The Code organizes districts into Transect zones (T2 → T5 and the SD2.1 special district) and Non‑Transect zones (for example E, R‑1, C‑2, A, PD), with land‑use tables and district‑specific development standards that control allowed uses, height, setbacks, and frontage/building form. Confirm the property’s official designation on the Official Regulating Plan before design work; that requirement and the zone descriptions are in the ordinance (see § 3.10.020 ). This summary focuses only on zoning/district rules in the Code — for parking, building code, ADUs or design review see the linked pages in context below.

First‑use links (internal resources):

• Tehachapi zoning & planning overview (/us/california/tehachapi)
• parking (/us/california/tehachapi/parking)
• development standards (/us/california/tehachapi/development-standards)
• design review (/us/california/tehachapi/design-review)
• overlay districts (/us/california/tehachapi/overlay-districts)
• ADUs (/us/california/tehachapi/adu)
• California Building Standards Code (/us/california/building-codes)

Article 3 of the Zoning Code groups the City’s zones; where I cite a zone below I give the Code section that creates that zone and the file preview that shows it. If you need a parcel‑specific answer, verify with the City (see "Risks & Ambiguities" below).

District-by-district breakdown

Notes on how the Code is organized: land uses allowed in each district are listed in the district’s Land Use Standards table (e.g., "Table 3.30.100" for C‑2). Where a zone’s text refers to development standards or frontage/building form it points you to Article 4 and Article 5 or to a zone’s C (Development Standards) subsection; follow those cross‑references. See Article 3 for the list and individual zone sections. All below items are grounded in the Code: the cited § is the district header or the Code chapter that contains the rules.

Transect zones (main downtown / walkable‑urban framework)

Transect zones prioritize form (block/building/frontage types) and translate that form into allowed uses and height/placement rules. See Chapter 3.20 for the transect regulations and the summary table that lists form types and typical max stories/feet. § 3.20.010–090 .

• T2 — Rural Edge
  Purpose: transition to rural edges; low‑intensity, larger lot house forms. See § 3.20.030 . Typical permitted uses: low‑density residential and very limited neighborhood uses per the zone’s land‑use table (see the zone’s Table). Dimensional/form standards: rural frontages and larger setbacks; transect allocation rules apply for master plans (see § 2.10.030) .

• T2.5 — Rural General
  Purpose: slightly denser rural/suburban edge than T2; see § 3.20.040 . Uses and development standards are listed in the zone’s table and cross‑refer to Article 5 frontage types (shopfront, porch, front yard, etc.) .

• T3 — Neighborhood Edge
  Purpose: neighborhood form with house‑form buildings, modest density; see § 3.20.050 . Typical allowed uses: neighborhood‑serving retail in small‑scale buildings plus residential. Heights and building forms are limited in the transect summary tables (see Chapter 3.20) .

• T4 — Neighborhood General
  Purpose: neighborhood general with mixed small‑scale commercial/residential frontages; see § 3.20.060 . Typical height: mid‑block house and block forms; the transect summary shows typical maxima around 2.5 stories / ~26 ft for many house‑forms and 3 stories / 35 ft for lined/block forms in the higher transects — verify the exact frontage and building‑type limits in Table 3.20 and Article 5 (Building Standards) .

• T4.5 — Neighborhood Center
  Purpose: intensified neighborhood center; see § 3.20.070 . Allows larger frontage types (galleries, shopfronts) and up to 3 stories / 35 ft on appropriate block/building types (see the transect summary table) .

• T5 — Downtown
  Purpose: downtown core; mixed uses, pedestrian‑oriented block forms. The transect table shows Lined / Large Flex / Rowhouse block forms and max 3 stories / 35 ft in many block forms (see § 3.20.080 and the table summary) . Land uses and parking demand are set by the district table.

• SD2.1 — Tehachapi Boulevard West (special district)
  Purpose: a special district along Tehachapi Boulevard intended for regional/community retail, lodging, and conference uses; block form buildings shape the street, with building heights and frontage types specifically tailored to Tehachapi Boulevard. See § 3.20.090 for intent, allowed character and that up to 3 stories is contemplated for SD2.1 (and reference to specific development standards in the zone) .

Practical guidance for transects: transect zones control both allowed uses and the required frontage/building form. Always check the transect’s Table and Article 5 Building Standards for the exact façade, frontage type, and maximum height that applies to your building type and frontage (see § 3.20.020 and Article 5) .

Non‑Transect zones (traditional zoning categories)

These zones use the more conventional allowed‑use and dimensional tables. See Chapter 3.30 and the specific zone headings (each zone has a "B. Land Use Standards" and "C. Development Standards"). § 3.30.010–160 .

• E — Estate
  Purpose: rural/larger residential lots with rural character. Primary rules and land‑use table are in § 3.30.030; the E zone's Development Standards and parking rules are in that section and cross‑references to Article 4/Chapter 4.50 (parking) are explicit .

• R‑1 — Single‑Family Residential
  Purpose and requirements: see § 3.30.040, which contains the R‑1 land use table and site standards (setbacks/lot coverage) and cross‑references to Article 4 building/siting standards; permitted uses are summarized in Table 3.30.040 .

• R‑2 / R‑3 — Medium & High‑Density Residential
  Purpose: R‑2 for low‑density multi‑family (minimum lot guidance appears in the zone text) and R‑3 for higher density multifamily. Notable detail: R‑3 establishes neighborhood design on lots not less than 7,500 sq ft (see § 3.30.060 for this explicit minimum) . Each zone lists allowed uses in its Table (e.g., Table 3.30.060 for R‑3) and parking rules are cross‑referenced in each zone section.

• MHP — Mobile Home Park; RP — Residential Professional
  See § 3.30.070 and § 3.30.080 for intent, permitted uses and special siting/park‑design standards in their tables .

• C‑1 / C‑2 / C‑3 / C‑4 — Commercial zones
  Each commercial zone has a descriptive intent, land‑use table, and parking rules. Example: C‑2 (Central Commercial) is intended for a broad mix of retail and services oriented to the whole community (see § 3.30.100 and its Table 3.30.100 for the permitted use matrix and parking ratios such as 1 space per 400 sq ft referenced in the table keys) .

• M‑1 / M‑2 — Light & Medium Industrial
  Industrial uses are handled in § 3.30.130–140 with permitted use tables and development/parking standards in those sections .

• A — Agriculture
  The A zone contains explicit buildable area and setback prescriptions that are illustrated in the Code. Example numeric standards shown in the Agriculture development standards include front setbacks measured from centerline (e.g., 55 ft from local street centerline; 70 ft from a secondary street; 80 ft from a major street; side and rear 25 ft; minimum lot size 10 acres) — see § 3.30.150 for these development requirements and diagrams .

• PD — Planned Development
  The PD zone provides a flexible, master‑planned approach; mapping and application rules include that a PD boundary must be indicated on the official zoning map and that PD applications follow preliminary/master plan procedures (including owner‑consent and fee requirements) — see § 3.30.160 (mapping and application rules) .

How the tables work: every zone’s B (Land Use Standards) subsection lists permitted (P), minor use permit (MUP), conditional (CUP) and prohibited uses with cross‑references to Article 6 (Specific Uses) and to Tables such as Table 3.30.100. The table keys include parking ratios (e.g., 1/400 = one parking space per 400 sq ft) — see the land use table keys in Chapter 3.30 and the example tables. § 3.30.100 and adjacent subsections show these tables and keys in practice .

Cross‑references and controlling rules

• When a conflict exists between zone‑specific standards and Article 4 or Article 6, the Code sets a hierarchy: provisions of Article 3 (Specific to Zones) control over Article 4 and 5; Article 6 (Specific Uses) controls over Articles 3, 4 and 5 in case of conflict. See § 3.20.020 and § 3.30.020 for the applicability rules and conflict hierarchy .
• The Code administration and permit processing responsibilities (who reviews what) are in the Administration chapters; the City Planner/Community Development Department administers the Code and certain discretion rules are listed in the administrative chapter (see § 1.20.020 and § 1.10.030) .

Quick reference table (selected decision‑relevant excerpts)

(These table entries summarize the zoning text and tables; always read the full zone subsection and its table before designing a project.)

Checklist

An applicant should, at minimum, do the following (each item maps to an ordinance provision you must check):

• Confirm the property’s official zone on the Official Regulating Plan / zoning map (§ 3.10.020) .
• Read the zone header (Article 3, the specific zone section such as § 3.20.030 for T2 or § 3.30.040 for R‑1) to determine allowed uses and required permits (P/MUP/CUP) .
• Check the zone’s Land Use Standards table and the Table keys (parking ratios, special notes) and cross‑reference Article 6 (Specific Uses) where required (see the table references in each zone) .
• Apply the applicable development standards in the zone’s C subsection plus Article 4 (General standards) and Article 5 (Building and Frontage standards) for façade, frontage and height requirements (Article 4/Article 5) .
• Calculate parking to the ratios and rules in Chapter 4.50 and the zone’s parking cross‑references, and plan landscaping/screening per Chapter 4.40 (Chapter 4.50 / Chapter 4.40) .
• Verify whether your project triggers design review or specific frontage standards (see Article 5 and local design review rules) and consult the City’s design review guidance early (/us/california/tehachapi/design-review) .
• For PD or master‑planned projects, follow the PD mapping and application requirements (owner consent, preliminary/master plan steps) in § 3.30.160 .
• If there is any doubt about allowed uses, nonconforming status, or conflicts among requirements, request a formal determination from the Community Development Director (administration and appeals procedures are in the administrative chapters) § 1.20.020 .

Risks & Ambiguities

Plain‑English Summary

Tehachapi’s Zoning Code uses a mix of transect (form‑based) zones for downtown/walkable areas and traditional zones for other areas. Each zone section lists allowed/conditional uses, required parking, frontage and building‑form rules, and development standards — always read the zone header (Article 3) + the land‑use table + the cross‑referenced development standards (Articles 4–5) to know what applies to a parcel (§ 3.10.020, § 3.20.020, § 3.30.020) .

Source References

• Official Regulating Plan / Zones: § 3.10.020
• Transect Zones summary and individual transect sections: § 3.20.010–090 (T2 → T5, SD2.1)
• Non‑Transect Zones and individual zone sections (E, R‑1, R‑2, R‑3, C‑2, A, PD, etc.): § 3.30.010–160 (see each zone header and its tables)
• Building and Frontage Standards (Article 5 / Chapter 5.10): Article 5 / § 5.10.010 et seq.
• Agriculture zone diagrams and numeric setbacks/lot size: § 3.30.150
• Central Commercial / land use table example: § 3.30.100 and Table 3.30.100 (parking keys such as 1/400 appear in table keys)
• Planned Development (PD) mapping & application rules: § 3.30.160
• Administration, applicability, and compliance statements: § 1.10.030 and § 1.20.020 (administration & delegated review)

Retrieved passages

• Tehachapi Zoning Code (Chapter 2.10) High relevance show source text
• Tehachapi Zoning Code (Chapter 3.20) High relevance show source text
• Tehachapi Zoning Code (Chapter 3.30) High relevance show source text
• Tehachapi Zoning Code (Chapter 3.30) High relevance show source text
• Tehachapi Zoning Code (Chapter 5.20) High relevance show source text
• Tehachapi Zoning Code (Section 1351) High relevance show source text
• Tehachapi Zoning Code (Article 5) High relevance show source text
• Tehachapi Zoning Code (Section 10.20) High relevance show source text

Cited sections

• Official Regulating Plan / Zones: **§ 3.10.020** (§ 3.10.020)
• Transect Zones summary and individual transect sections: **§ 3.20.010–090** (T2 → T5, SD2.1) fileciteturn0file1turn0file12 (§ 3.20.010)
• Non‑Transect Zones and individual zone sections (E, R‑1, R‑2, R‑3, C‑2, A, PD, etc.): **§ 3.30.010–160** (see each zone header and its tables) fileciteturn0file3turn0file11turn0file14 (§ 3.30.010)
• Building and Frontage Standards (Article 5 / Chapter 5.10): **Article 5 / § 5.10.010 et seq.** (Article 5)
• Agriculture zone diagrams and numeric setbacks/lot size: **§ 3.30.150** (§ 3.30.150)
• Central Commercial / land use table example: **§ 3.30.100** and Table **3.30.100** (parking keys such as 1/400 appear in table keys) fileciteturn0file9turn0file14 (§ 3.30.100)
• Planned Development (PD) mapping & application rules: **§ 3.30.160** (§ 3.30.160)
• Administration, applicability, and compliance statements: **§ 1.10.030** and **§ 1.20.020** (administration & delegated review) fileciteturn0file18turn0file19 (§ 1.10.030)
• Tehachapi_ZoningCode.md

• Official Tehachapi code library