Montague — Variances and Exceptions

Last reviewed: July 6, 2026

Overview

Montague processes zoning variances under Title 17, primarily through the citywide procedures in the chapter labeled “Use Permits and Variances” and, within the airport overlay, through the “Montague‑Yreka Airport Hazard Zoning Ordinance.” Variances hinge on special property circumstances and are limited by express findings; some “exceptions” are built into the code (e.g., fences and substandard-lot setbacks) and do not require a formal variance. See the citywide variance standards in § 17.36.040 and the airport‑overlay variance standards in § 17.24.080.

The single most important rule: Montague variances require special property circumstances and cannot be used to legalize a nonconforming use; they also expire if unused within one year (§ 17.36.040; § 17.36.050; § 17.36.120).

Linking context:

• For how variances fit into the bigger picture, see the Montague zoning & planning overview and Montague Zoning.
• If a project also triggers plan/design checks, see Montague Design Review.
• Standards you may be varying—like setbacks or height—live in Montague Development Standards.
• For overlay rules (including the airport overlay), see Montague Overlay Districts.
• If a proposal touches legacy situations, compare with Montague Nonconforming Uses.
• Some exceptions intersect with frontage or vehicle standards; confirm any downstream parking effects under Montague Parking.

How Montague variances work (citywide)

• Decision body and findings. The Planning Commission may grant a variance only if both are true: (1) conditions ensure it is not a special privilege versus nearby similarly zoned properties; and (2) special circumstances (size, shape, topography, location, or surroundings) mean strict application would deprive the property of privileges enjoyed by others (§ 17.36.040).
• No “use variances.” A variance cannot authorize a use that is not allowed in the zone (§ 17.36.050).
• Application contents. File on the Planning Commission’s form with fee, a detailed plan of the variance, and evidence that granting it is consistent with Title 17 and public safety, and that strict application would impose practical difficulties and unnecessary hardship (§ 17.36.060).
• Hearing practice. No public hearing is required by default, but the Commission may hold hearings with legally required notice (§ 17.36.080).
• Appeals and timing. Variances are not issued until five days pass; if appealed, issuance waits for the City Council decision (§ 17.36.090). Any person, including the applicant, can appeal to the Council within five days (§ 17.36.110).
• Acceptance, expiration, and revocation. A variance is effective only after the permittee acknowledges and accepts any conditions (§ 17.36.100); it becomes null and void if not used within one year unless a shorter time is set (§ 17.36.120); and it can be revoked if continued relief would be contrary to public interest, safety, health, and welfare (§ 17.36.130–.140).

Airport overlay variances (Montague‑Yreka Airport Hazard Zoning)

• Where and what applies. The overlay creates Approach, Transitional, Horizontal, and Conical zones tied to FAA Part 77 airspace surfaces; the map titled “Airport Zoning Map for Montague Airport” controls (§ 17.24.040; § 17.24.020). Apply through the Building Inspector, who forwards applications to the Planning Commission (§ 17.24.030).
• Variance standard in the overlay. Relief may be granted where literal application would cause practical difficulty or unnecessary hardship, provided the variance serves the public interest, does substantial justice, and accords with the chapter’s spirit (§ 17.24.080).
• Conditions unique to aviation safety. Any permit or variance may be conditioned to allow the City, at its expense, to install and operate markers/lights to warn pilots (§ 17.24.090).
• Appeals and conflicts. Airport variance decisions may be appealed using the same procedures as Chapter 17.36 (§ 17.24.100). If this chapter conflicts with other rules, the stricter rule prevails (§ 17.24.110).

Built‑in exceptions (no variance required)

• Fences in front/side yards and easements. The code allows exceptions to standard fence placement with an encroachment permit under Chapter 12.02, subject to conditions (e.g., max 4 ft height along any side street and in front yards near sidewalks; visibility safeguards; indemnification) (§ 17.32.110(B)–(C)).
• Taller security fencing in commercial/industrial areas. In C‑2 and M zones, fences over 6 ft (plus up to 2 ft of barbed wire) may enclose the rear half of a lot if a use permit is approved, among other conditions (§ 17.32.110(D)).
• Substandard-lot side yards. For qualifying substandard residential lots, side yards may be reduced to the greater of 10% of lot width or 4 ft (§ 17.32.190; cross‑referenced to § 17.32.180 for eligibility).

Decision‑relevant standards (quick table)

District‑by‑district implications for variances and exceptions

R (Residential) districts

• Purpose/where: City’s residential zones (“R districts”) regulate homes and related uses across built neighborhoods (§ 17.32.200 references “any R district”).
• Typical permitted uses: Not found in retrieved materials.
• Key dimensional standards: The code provides targeted relief for substandard residential parcels—side yards may be reduced to 10% of lot width, minimum 4 ft, when the lot qualifies under § 17.32.180 (§ 17.32.190). Variances here must still meet § 17.36.040.
• Variance/exception notes: Consider the built‑in side‑yard exception first; if ineligible, a variance must satisfy the citywide findings. Verify whether any design review applies in nearby C or M edges (§ 17.32.220).

C‑2 (Commercial) district

• Purpose/where: City’s general commercial corridors (designation appears in the fence standards).
• Typical permitted uses: Not found in retrieved materials.
• Key dimensional standards: Not found in retrieved materials.
• Variance/exception notes: Tall rear security fencing (>6 ft plus up to 2 ft barbed wire) is allowed by use permit when enclosing the rear half of a lot and meeting stated conditions (§ 17.32.110(D)). Variances for other standards must meet § 17.36.040.

M (Industrial) district

• Purpose/where: Industrial employment areas (designation appears throughout fence and design‑review provisions).
• Typical permitted uses: Not found in retrieved materials.
• Key dimensional standards: Not found in retrieved materials.
• Variance/exception notes: As in C‑2, tall rear security fences may be approved with a use permit under conditions (§ 17.32.110(D)); architectural review applies in M (§ 17.32.220), which may run in parallel to a variance.

Approach Zone (Airport Overlay)

• Purpose/where: Protect takeoff/landing surfaces extending from runway ends (§ 17.24.020; § 17.24.040).
• Typical permitted uses: Governed by airport hazard restrictions; specific use list not found in retrieved materials (§ 17.24.060 referenced generally). Not found in retrieved materials.
• Key dimensional standards: Height limits tied to FAA Part 77 surfaces (§ 17.24.050). Not found in retrieved materials.
• Variance/exception notes: Airport‑specific variance standard in § 17.24.080, plus possible marking/lighting conditions in § 17.24.090.

Transitional Zone (Airport Overlay)

• Purpose/where: Flanks sides of approach surfaces (§ 17.24.020; § 17.24.040).
• Typical permitted uses: Not found in retrieved materials.
• Key dimensional standards: Not found in retrieved materials.
• Variance/exception notes: Same airport variance and condition framework (§ 17.24.080–.090).

Horizontal Zone (Airport Overlay)

• Purpose/where: Plateaus of controlled airspace above the airport (§ 17.24.020; § 17.24.040).
• Typical permitted uses: Not found in retrieved materials.
• Key dimensional standards: Not found in retrieved materials.
• Variance/exception notes: Same as above (§ 17.24.080–.090).

Conical Zone (Airport Overlay)

• Purpose/where: Outermost, sloped airspace band (§ 17.24.020; § 17.24.040).
• Typical permitted uses: Not found in retrieved materials.
• Key dimensional standards: Not found in retrieved materials.
• Variance/exception notes: Same as above (§ 17.24.080–.090).

Checklist

• Confirm your project’s base zone and whether any overlay (airport) applies; consult the airport zoning map (§ 17.24.040).
• Determine if a built‑in exception solves the issue (e.g., fence encroachment with encroachment permit under § 17.32.110, or substandard‑lot side‑yard relief under § 17.32.190).
• If a variance is needed, prepare evidence of special circumstances and lack of special privilege; include a detailed plan set (§ 17.36.040; § 17.36.060).
• Verify the request is not a prohibited “use variance” (§ 17.36.050).
• File on the Planning Commission’s form with the prescribed fee (§ 17.36.060).
• Track timing: a variance is issued only after a 5‑day wait; appeals must be filed within 5 days (§ 17.36.090; § 17.36.110).
• On issuance, sign the acceptance acknowledging any conditions (§ 17.36.100).
• Use the variance within 1 year, or it lapses (§ 17.36.120).
• In the airport overlay, anticipate potential marking/lighting conditions (§ 17.24.090).
• If other approvals apply (e.g., design review in C or M), coordinate submittals (§ 17.32.220).

Risks & Ambiguities

Plain‑English Summary

In Montague, you can ask for a variance when your property has unique physical constraints that make strict zoning rules unfair—but you must prove those constraints and show you’re not getting a special break others don’t have. Some relief is already “baked in” (like limited fence encroachments or smaller side yards on small lots), and airport‑area projects face special safety rules. Most importantly, you can’t use a variance to permit a use the zone doesn’t allow, and any approved variance will expire if you don’t act on it within a year. See § 17.36.040, § 17.36.050, § 17.36.120, and § 17.32.110/§ 17.32.190.

Source References

• Title 17, Use Permits and Variances: § 17.36.040–.140 (findings, applications, hearings, appeals, expiration, revocation)
• Title 17, Airport Zoning (Montague‑Yreka Airport Hazard Zoning Ordinance): § 17.24.020–.040, .080–.110 (definitions, map, variance criteria, conditions, appeals/conflicts)
• Title 17, General Use Restrictions—Fences: § 17.32.110(B)–(D) (fence exceptions and taller security fences in C‑2/M)
• Title 17, General Use Restrictions—Substandard lots: § 17.32.190 (side‑yard reduction)
• Title 17, Architectural review in C/M: § 17.32.220 (coordination with design review)

Information Gaps

• Specific permitted uses and dimensional standards for C‑2 and M beyond fence/architectural items: Not found in retrieved materials.
• Exact airport‑zone height tables/angles in § 17.24.050–.060: Not found in retrieved materials.
• Eligibility criteria in § 17.32.180 (referenced by § 17.32.190): Not found in retrieved materials.
• Verify with the jurisdiction if parcel‑specific interpretations are needed.

Retrieved passages

• Montague Zoning Code (§ 6) High relevance show source text
• Montague Zoning Code (Chapter 12.02) High relevance show source text
• Montague Zoning Code (§ 7.3) High relevance show source text
• Montague Zoning Code (title or) High relevance show source text
• Montague Zoning Code (Title 17) High relevance show source text
• Montague Zoning Code (Title 17) Medium relevance show source text
• Montague Zoning Code (§ 7.9) Medium relevance show source text
• Montague Zoning Code (Chapter 12.02) Medium relevance show source text

Cited sections

• Title 17, Use Permits and Variances: § 17.36.040–.140 (findings, applications, hearings, appeals, expiration, revocation) (Title 17)
• Title 17, Airport Zoning (Montague‑Yreka Airport Hazard Zoning Ordinance): § 17.24.020–.040, .080–.110 (definitions, map, variance criteria, conditions, appeals/conflicts) (Title 17)
• Title 17, General Use Restrictions—Fences: § 17.32.110(B)–(D) (fence exceptions and taller security fences in C‑2/M) (Title 17)
• Title 17, General Use Restrictions—Substandard lots: § 17.32.190 (side‑yard reduction) (Title 17)
• Title 17, Architectural review in C/M: § 17.32.220 (coordination with design review) (Title 17)
• Montague_ZoningCode.md