Tributary – Zoning Map Amendment from R-2 to MU-A
2026-20 A PUBLIC HEARING AND INTRODUCTION OF AN ORDINANCE OF THE CITY COUNCIL OF THE CITY OF AURORA, COLORADO, FOR A ZONING MAP AMENDMENT TO REZONE APPROXIMATELY 104 ACRES OF LAND TO MIXED-USE AIRPORT (MU-A), LOCATED EAST OF FUTURE HARVEST ROAD, WEST OF POWHATON ROAD AND NORTH OF FUTURE 12TH AVENUE (MU-A TRIBUTARY REZONE)
Official status: Pass
Prime sponsors
Sponsor information is on the official bill page (linked below).
Progress (from the official record)
Official summary
Official text — shown in English exactly as published by the official source. The official text controls.
The official page for this measure does not publish a summary. Its full text is linked below.
Status timeline
| Date | Location | Action |
|---|---|---|
| 06/08/2026 | City Council | Listed on the City Council agenda — Public Hearings |
| 06/22/2026 | City Council | Listed on the City Council agenda — Consent Calendar — Finalizing of Ordinances |
Recorded votes
- 06/08/2026 — City Council: “Does the City Council wish to support the approval of the ordinance to amend the City of Aurora Zoning Map to MU-A?” — the motion Pass on a vote of 10–0.
Full text
Official record
City of Aurora — City Council meeting agendas and voting results (auroragov.org)
Source: City of Aurora — City Council meeting agendas and voting results (auroragov.org) · Data as of
Verify this record
This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.
SHA-256 fingerprint
2282d68adf143e39644c3a45b42a3a7135101ebd710c2257de5a8d4078824bcc
What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.
The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.
If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.