Commission examines airport overlay draft, runway protection zone and uses; seeks technical aviation review

The Fairfield Planning & Zoning Commission reviewed a draft airport overlay and land‑use table on Sept. 3 that would update how the town regulates uses near the municipal airpark. Discussion covered the overlay boundary, runway protection surfaces, permissible and conditional uses (restaurants, hangar residences, crew rest areas) and whether the town should adopt specific FAA or state land‑use guide thresholds into local code.

Todd, the town attorney/staff advisor, walked the commission through the draft and noted that much of the language derives from the Utah Airport Land Use Guide (2018) and from FAA circulars. He warned commissioners that Part 77 imaginary surfaces (the federal overflight/obstruction standard codified in CFR/FAA guidance) do not always align with the land‑use guide’s “limited development” and “no development” zones; the draft needs to make clear which standard applies when the two conflict. Brian Carver — an aviation commenter whose markups are in the draft — flagged that the draft contains different radius/zone options (a 5,000‑foot ring around the runway versus a broader 10,000‑foot controlled development area) and asked the town to choose a consistent mapping approach.

Commissioners debated permitted uses and enforcement. The draft currently lists a range of aviation‑related and mixed uses; commissioners agreed to remove a separate “café” line and instead treat eating‑and‑drinking establishments as restaurants subject to conditional‑use review, so hours, traffic circulation and noise conditions can be imposed case by case. The commission also discussed so‑called crew rest areas inside hangars: the draft limits such areas in time and scope (a non‑residential rest area, limited hours and separation between periods), but some members questioned how the town could enforce those limits and whether the aviation community should be expected to police hangar uses.

Runway protection zones and approach surfaces generated particular attention. Commissioners asked staff to produce an overlay map showing the draft boundaries, to check whether the airport’s existing pavement and proposed road align with the recommended protection zones, and to consult the FAA and aviation experts on whether a public road that crosses a runway protection area would create a regulatory or safety problem. Todd said the draft will be revised and flagged that the town may need to clarify whether FAA Part 77 or the Utah Airport Land Use Guide provides the controlling standard for different overlay elements.

The commission asked staff to obtain technical review from aviation professionals and to coordinate with the airport operator and Utah Aviation contacts. Commissioners left the draft overlay in progress and asked staff to return with consolidated maps and recommended language that resolves the 5,000‑foot vs. 10,000‑foot boundary question, clarifies how Part 77 surfaces apply and proposes enforceable special‑use criteria for restaurants, hangar operations and crew rest areas.

The commission did not adopt the overlay on Sept. 3 and requested additional aviation review.