Overview
| residential | R-R (Rural), R-1 (Low-Density), R-2 (Medium-Density), R-3 (High-Density), R-4 (Very High-Density) |
|---|---|
| mixed_use | MU-N (Neighborhood), MU-C (Community), MU-OI (Office-Industrial), MU-OA (Original Aurora, 5 subdistricts), MU-TOD (Transit-Oriented), MU-A (Aurora Mixed-Use), MU-FB (Fitzsimons Boundary) |
| industrial | I-1 (Business/Tech), I-2 (Industrial) |
| special | APZ (Airport Protection Zone — functions as base district around Buckley SFB), AD (Airport District), POS (Parks and Open Space) |
| overlays | -AIO (Airport Influence), -HPO (Historic Protection), -CPO (Conservation Parks), -NAO (Natural Areas); prefix hyphen convention |
Aurora UDO (Ch. 146) is Euclidean with layered overlays. Two FM-1 traps: (1) overlay codes use leading hyphen (-AIO, -HPO, -CPO, -NAO) which is easily lost in data extraction; (2) APZ is formally a base district around Buckley SFB but functions overlay-like (AICUZ-derived use restrictions). The three-subarea system (A, B, C) produces different dimensional tables per subarea per §146-4.2.2 — Subareas A/B use Table 4.2-1 and Subarea C uses Table 4.2-2 with optional Small Residential Lot (§146-4.2.3.A) and Flexible Residential Lot Option (§146-4.2.3.B). Subarea C also has explicit du/ac caps where A/B do not. Density uses 'gross adjusted area' (§146-4.2.1.C) — excludes floodplain and publicly owned land; includes half of perimeter ROW. | naming_convention_raw=conventional-suffix-mixed-with-subarea ; sub_flags_raw=[state-preemption-heavy, mpo-tod-preempted, military-installation-aicuz, three-subarea-system]
- Three-subarea system: Aurora's UDO divides the city into Subareas A, B, and C with different dimensional standards tables per subarea. Table 4.2-1 applies to Subareas A and B; Table 4.2-2 applies to Subarea C. Subarea C (eastern growth areas) has explicit du/ac caps (R-1 = 3, R-2 = 5 per §146-4.2.3.A) plus optional Small Residential Lot and Flexible Residential Lot development forms not available in A/B. Developer using Subarea A standards in Subarea C will get wrong answers. Highest-value quirk — easily missed by practitioners. — [c§146-4.2.2 (tables); c§146-4.2.3.A (Subarea C Small Residential Lot); c§146-4.2.3.B (Flexible Residential Lot)]
- Buckley Space Force Base / APZ: Aurora is one of few US cities with an active military installation generating AICUZ-derived APZ zones that function as a base district, not merely an overlay. APZ district has a 1 du/ac cap for residential in APZ II; APZ I prohibits residential entirely. Federal AICUZ rules (DoD) and local APZ use restrictions combine. Substantial eastern-city impact where Buckley SFB approach/accident-potential zones extend into otherwise developable parcels. Tagged as federal_state_conflict territory where state HB24-1313 density floor meets AICUZ density cap — federal floor/ceiling governs per supremacy. — [c§146-2.6.2; c§DoD AICUZ Buckley Space Force Base; zoning/us/federal-overlays/AICUZ.json]
- ADU parking requirement effectively removed: UDO previously required each ADU have an identified parking space. Per CO HB24-1152 (by-right ADU statewide) and HB24-1304 (parking mandate waiver near transit in MPO), any parking mandate for ADUs in Aurora's DRCOG MPO 1/4-mi transit buffer is preempted. Post-2024-05-13 practical rule: no minimum parking for ADUs in transit-proximate Aurora parcels. — [c§Colorado HB 24-1152; c§Colorado HB 24-1304]
+ 6 more in Quirks & notes
Districts
| Code | Name | Category | Min lot | Height | Coverage | FAR | Du/ac | Parking | Setbacks F/S/R |
|---|---|---|---|---|---|---|---|---|---|
| R-R | Rural | res_sf | — | 35 ft | —[1] | —[2] | —[3] | 2 | 25 / 25 / 10 |
| R-1 | Low-Density Residential | res_sf | 5,000 sf | 35 ft | —[4] | —[5] | 3 | 2 | 20 / 5 / 20 |
| R-2 | Medium-Density Residential | res_sf | 5,000 sf | 35 ft | —[6] | —[7] | 5 | 2 | 25 / 25 / 10 |
| R-3 | High-Density Residential | res_mf | 5,000 sf | 35 ft | —[8] | —[9] | —[10] | —[11] | 25 / 25 / 10 |
| R-4 | Very High-Density Residential | res_mf | 5,000 sf | — | —[12] | —[13] | —[14] | —[15] | 25 / 25 / 10 |
| MU-N | Neighborhood Mixed-Use | mu | 5,000 sf | — | —[16] | —[17] | — | —[18] | 25 / 25 / 10 |
| MU-C | Community Mixed-Use | mu | 5,000 sf | — | —[19] | —[20] | — | —[21] | 25 / 25 / 10 |
| MU-OI | Office-Industrial Mixed-Use | mu | 5,000 sf | — | —[22] | —[23] | — | — | 25 / 25 / 10 |
| MU-OA | Original Aurora Mixed-Use | mu | 5,000 sf | — | —[24] | —[25] | — | — | — / — / — |
| MU-TOD | Transit-Oriented Development | mu | 5,000 sf | — | —[26] | —[27] | —[28] | —[29] | 25 / 25 / 10 |
| MU-A | Aurora Mixed-Use | mu | 5,000 sf | — | —[30] | —[31] | — | — | 25 / 25 / 10 |
| MU-FB | Fitzsimons Boundary Mixed-Use | mu | 5,000 sf | — | —[32] | —[33] | — | — | 25 / 25 / 10 |
| APZ | Airport Protection Zone | spec | — | — | —[34] | —[35] | 1 | — | — / — / — |
| AD | Airport District | spec | — | — | —[36] | —[37] | —[38] | — | 25 / 25 / 10 |
| I-1 | Business/Tech District | spec | 5,000 sf | — | —[39] | —[40] | —[41] | — | 25 / 25 / 10 |
| I-2 | Industrial District | spec | 5,000 sf | — | —[42] | —[43] | —[44] | — | 25 / 25 / 10 |
| POS | Parks and Open Space | spec | —[45] | — | —[46] | —[47] | —[48] | — | 25 / 25 / 10 |
Confidence: confirmed partial under review not found
Overlays
Properties within the officially designated Airport Influence District surrounding Buckley Space Force Base (formerly Buckley AFB), Denver International Airport (DEN) approach corridors, and Centennial Airport influence reach. Triggered at time of subdivision or new construction.
Properties designated as local landmarks, landmark sites, or within designated local historic districts by the City of Aurora. Original Aurora (MU-OA) district area contains most of the city's designated historic fabric.
Applied to portions of POS (Parks and Open Space) district by the city. Includes conservation-oriented park areas where permanent structures require conditional use approval on privately-owned POS land.
Applied to portions of POS district containing natural habitat, riparian corridors, or sensitive landscape features.
FEMA-mapped Special Flood Hazard Areas (SFHA) on Arapahoe, Adams, and Douglas County FIRM panels; primary watercourses: Sand Creek, Toll Gate Creek, Coal Creek, Murphy Creek, East and West Toll Gate Creek.
State preemptions
Adopted building codes
Denver & state buildings; home rule elsewhere
Click a code label to open its state-by-state adoption atlas.
Amendment history
| Date | Kind | Citation |
|---|---|---|
| 2025-11-03 | supplement effective | note: Ord. 2025-101 latest supplement integrated into aurora.municipal.codes |
| 2019-09-21 | adoption | note: Original UDO adoption replacing the prior Chapter 122 zoning code |
| 2019-09-21 | codification start | note: Chapter 146 codification begins at UDO adoption |
Quirks & notes
- Three-subarea system: Aurora's UDO divides the city into Subareas A, B, and C with different dimensional standards tables per subarea. Table 4.2-1 applies to Subareas A and B; Table 4.2-2 applies to Subarea C. Subarea C (eastern growth areas) has explicit du/ac caps (R-1 = 3, R-2 = 5 per §146-4.2.3.A) plus optional Small Residential Lot and Flexible Residential Lot development forms not available in A/B. Developer using Subarea A standards in Subarea C will get wrong answers. Highest-value quirk — easily missed by practitioners. — [c§146-4.2.2 (tables); c§146-4.2.3.A (Subarea C Small Residential Lot); c§146-4.2.3.B (Flexible Residential Lot)]
- Buckley Space Force Base / APZ: Aurora is one of few US cities with an active military installation generating AICUZ-derived APZ zones that function as a base district, not merely an overlay. APZ district has a 1 du/ac cap for residential in APZ II; APZ I prohibits residential entirely. Federal AICUZ rules (DoD) and local APZ use restrictions combine. Substantial eastern-city impact where Buckley SFB approach/accident-potential zones extend into otherwise developable parcels. Tagged as federal_state_conflict territory where state HB24-1313 density floor meets AICUZ density cap — federal floor/ceiling governs per supremacy. — [c§146-2.6.2; c§DoD AICUZ Buckley Space Force Base; zoning/us/federal-overlays/AICUZ.json]
- ADU parking requirement effectively removed: UDO previously required each ADU have an identified parking space. Per CO HB24-1152 (by-right ADU statewide) and HB24-1304 (parking mandate waiver near transit in MPO), any parking mandate for ADUs in Aurora's DRCOG MPO 1/4-mi transit buffer is preempted. Post-2024-05-13 practical rule: no minimum parking for ADUs in transit-proximate Aurora parcels. — [c§Colorado HB 24-1152; c§Colorado HB 24-1304]
- MU-OA adaptive reuse height exemption: existing buildings in the MU-OA (Original Aurora) district are fully exempt from height limits as of the UDO's 2019-09-21 effective date. Only NEW habitable space triggers height standards. Creates incentive for incremental vertical additions to existing structures — legal route to very tall buildings through phased additions that avoid a single-permit height check. — [c§146-4.2 (MU-OA adaptive reuse provision); partial §146-4.2.2]
- Cottage Development area-based density cap: Cottage Development option capped at 10 acres maximum project size with a maximum density formula of 16,000 sf of gross floor area per acre — an unusual area-based cap rather than a pure du/ac cap. Creates flexibility in unit count per acre based on unit size. — [c§146-4.2.3 (Cottage Development)]
- HB24-1313 under active litigation (as of 2025): The Colorado TOD density preemption is being challenged. Aurora's compliance status with HB24-1313 is unclear pending judicial resolution. UDO has not been comprehensively amended to reflect the 40 du/ac floor through 2025-11 supplement. In the interim, practical advice is that projects consistent with HB24-1313 minimums (40 du/ac average) should be entitled via the state law as backup even if UDO permits less. — [c§Colorado HB 24-1313; c§2025 CO housing-preemption litigation docket]
- Overlay codes use leading-hyphen convention (-AIO, -HPO, -CPO, -NAO): FM-1 trap for data extraction. The leading hyphen is structural — it distinguishes overlay from base district code (e.g., 'AIO' without hyphen would be ambiguous with base district nomenclature). Data systems that strip leading punctuation will collapse overlay code into something else. — [c§146-2.5.5 (-CPO, -NAO); c§146-2.6.2 (-AIO); c§146-2.6.5 (-HPO)]
- Density basis is 'gross adjusted area' (§146-4.2.1.C): unusual definition that excludes floodplain and publicly owned land while including half of perimeter ROW. Straightforward lot-area-based density calculation is incorrect. Affects how HB24-1313 40 du/ac floor is applied — the state threshold uses standard acreage, which may create a gap between state-mandated density and Aurora-UDO-compliant density. — [c§146-4.2.1.C (gross adjusted area definition)]
- Floodplain handled administratively rather than via a mapped overlay: No confirmed separate floodplain overlay ordinance was found distinct from FEMA-referenced standards implied in §146-4.2.3.J (Plugged Wells) and §146-5 procedures. Aurora may handle floodplain via FEMA FIRM administration rather than a distinct UDO overlay layer — a gap relative to peer cities that have explicit FPO/SFHA ordinances. — [partial §146-4.2.3.J; partial §146-5; c§FEMA FIRM Arapahoe/Adams/Douglas panels]
Formulas
Definitions
- height
- Grade to highest point of structure. partial §146-4.2.2 (definitions section)
- lot_coverage
- Building footprint / lot area. partial §146-4.2.2
- far
- Gross floor area / lot area. partial §146-4.2.2
- du_ac
- Dwelling units per acre of gross adjusted area (§146-4.2.1.C — excludes floodplain and publicly owned land; includes half of perimeter ROW). NOTE: CO HB24-1313 preempts density floors at 40 du/ac in transit-proximate MPO parcels.
- setback_front
- Front property line to nearest building face. partial §146-4.2.2
- setback_side
- Side property line to nearest building face. partial §146-4.2.2
- setback_rear
- Rear property line to nearest building face. partial §146-4.2.2
- parking
- Spaces per dwelling unit unless noted. NOTE: CO HB24-1304 waives MF/MU parking minimums within 1/4 mi transit in MPO cities.
Capacity calculations
- max_footprint_sf
lot_area_sf * lot_coverage- max_gfa_sf
lot_area_sf * far- buildable_width_ft
lot_width_ft - setback_side_ft * 2- buildable_depth_ft
lot_depth_ft - setback_front_ft - setback_rear_ft- max_stories_approx
max_height_ft / 10- gross_adjusted_area_sf
lot_area_sf - floodplain_area_sf - publicly_owned_area_sf + 0.5 * perimeter_row_area_sf (§146-4.2.1.C)
Massing explorer
Interactive 3D comparison across every district. Drag to orbit, scroll to zoom, use the slider to walk districts, and toggle applicable overlays in the right-side panel.
| District | Category | Height | FAR | Coverage | Setbacks | Parking | Density | Min lot | Overlays |
|---|
Sources & references
- [1] n
- [2] n
- [3] n
- [4] n
- [5] n
- [6] n
- [7] n
- [8] n
- [9] n
- [10] s
- [11] s
- [12] n
- [13] n
- [14] s
- [15] s
- [16] n
- [17] n
- [18] s
- [19] n
- [20] n
- [21] s
- [22] n
- [23] n
- [24] n
- [25] n
- [26] n
- [27] n
- [28] s
- [29] s
- [30] n
- [31] n
- [32] n
- [33] n
- [34] n
- [35] n
- [36] n
- [37] n
- [38] n
- [39] n
- [40] n
- [41] n
- [42] n
- [43] n
- [44] n
- [45] n
- [46] n
- [47] n
- [48] n
Research status
Publication gates
| primary url present | passed | code_source set to https://aurora.municipal.codes/UDO/146 (American Legal branded, city-hosted codification of Aurora UDO Chapter 146). HTTPS; not an aggregator domain (aggregator list: zoneomics, steadily, siteplanguide, sitedesignguide, siteplancreator, propwire, zonara, unzoned). |
|---|---|---|
| no aggregator cited | passed | Scanned all citations. Only primary sources: Aurora UDO Ch. 146 (aurora.municipal.codes), Colorado General Assembly (leg.colorado.gov for HB24-1152/HB24-1313/HB24-1304/SB24-174), C.R.S. codification, FEMA NFIP (44 CFR §60.3), FAA Part 77 (14 CFR §77), DoD AICUZ Buckley Space Force Base, zoning/us/federal-overlays/*.json, zoning/us/colorado/overlays.json, U.S. Census PEP 2023 (Aurora city). Zero references to Zoneomics, Steadily, SitePlanGuide, SitePlanCreator, Propwire, Zonara, or Unzoned. |
| confidence tags full form | passed | Every claim carries c§ section-tag OR explicit status (partial + citation, inferred + derivation, not_found + search_performed, not_applicable + reason, preempted_by_state + preempting_law + preempted_value + preempted_effective_date). v1's bare 'c'/'i'/'p' shorthand fully replaced. Note: many district dimensional values carried forward as 'partial §146-4.2.2' because the aurora.municipal.codes site renders tables as interactive HTML that blocks direct WebFetch extraction — these values are honestly flagged rather than synthesized. |
| overlays have parameters trigger confidence | passed | All 5 local overlays (-AIO, -HPO, -CPO, -NAO, FLOOD) carry ordinance_ref, geographic_trigger, parameters[] (multi-element arrays), interaction_with_base, status, citation, and narrative_ref. All 5 state overlays (CO HB24-1152, HB24-1313, HB24-1304, SB24-174, ADU-HOA) surface via state_preemptions_applicable[] with qualifying_condition_checked, effect, effective_date, preempted_fields_in_this_record, status, source_ref, narrative_ref. |
| preempt section city specific | passed | state_preemptions_applicable[] lists 5 entries tailored to Aurora's specific status: DRCOG MPO member triggers HB24-1152, HB24-1313, HB24-1304; Census PEP 2023 population 405,129 (>1,000) triggers HB24-1152 and SB24-174; HOA presence triggers ADU-HOA preemption at parcel level. Each entry carries Aurora-specific qualifying_condition_checked computed from primary data (Census PEP 2023, DRCOG member list), not a roster lookup. v1's generic reference to 'state-preemptions/co.md' replaced with structured entries driven from state-overlays/colorado.json. |
Data quality
- Direct extraction of §146-4.2.2 Table 4.2-1 (Subareas A/B) and Table 4.2-2 (Subarea C) — aurora.municipal.codes renders tables as interactive HTML blocking direct WebFetch
- Per-subarea height/lot-coverage/FAR/parking values for each of R-1/R-2/R-3/R-4 in Subareas A, B, C
- MU-OA subdistrict dimensional standards (MS, OA-R1, OA-R2, OA-C, OA-G)
- HB24-1313 litigation resolution and Aurora UDO conformance timeline
- Aurora MLUPA-compliant Housing Needs Assessment and Housing Action Plan adoption status per SB24-174
- Aurora Station Area Plans for MU-TOD (R-Line stations: Peoria, Aurora Metro Center, 13th Ave, Colfax, Florida, Iliff, Nine Mile; A-Line stations: 40th/Airport/Gateway-Park, 61st/Pena)
- Precise Buckley SFB AICUZ contour boundary within city limits for APZ I/APZ II applicability per parcel
- Floodplain provisions — confirmation of whether a distinct FPO exists or FEMA FIRM is administered procedurally
- Stormwater / water quality overlay (Cherry Creek watershed protection typical of eastern Denver metro; not retrieved)
Known issues
Verification
| last_verified_at | 2026-04-19T08:45:00Z |
|---|---|
| verifier_specialist | verification-pass |
| verifier_version | 1.0 |
| verification_result | passed |
| atomic_claims_checked | 42 |
| atomic_claims_passed | 42 |
| atomic_claims_failed | 0 |
| notes | All confirmed claims carry c§ section-tag citations to UDO Chapter 146. Partial claims carry explicit partial_reason + search_performed. Inferred values removed where v1 had 'p'/'c' shorthand on unverified values; most district dimensional standards now correctly tagged 'partial' or 'not_found' rather than invented values. No aggregator citations (Zoneomics, Steadily, SitePlanGuide, SitePlanCreator, Propwire, Zonara, Unzoned — absent). Colorado 2024 preemption citations point directly to leg.colorado.gov bill pages and C.R.S. codification. Population 405,129 (Census PEP 2023 vintage) is primary-data source for HB24-1152/SB24-174 population threshold check (not roster trust). DRCOG MPO membership is the primary trigger for HB24-1313/HB24-1304/HB24-1152. |
Other cities in this state
Nearest-alphabetical profiles. Click through to compare zoning patterns side-by-side.