Fairfield planning commissioners send airpark overlay and air‑park mixed‑use zone to council after public concerns about scope and legal risk

The Fairfield Planning and Zoning Commission voted Wednesday to forward two revised airport zoning measures to the town council after an extended discussion and multiple public comments raising legal, technical and property‑impact questions.

Todd Sharon, planning staff, gave the commission an overview of revisions to the draft airport overlay and the new Air Park Mixed Use Zone, saying he “just wanted to give a, an update on some of the changes that were made from the previous draft.” The commission then heard public comments from landowners, an airport attorney and representatives of adjacent property interests before debating definitions, the required airport emergency plan, runway‑protection requirements and the overlay radius.

Commissioners said the measures aim to protect public safety and make development requirements clearer, but multiple speakers warned the draft goes beyond state definitions and could create legal risk or significant consequences for nearby landowners.

Dan McDonald, an attorney for Intermountain Regional Landfill (IRL), told the commission he was concerned the ordinance’s maps and text were inconsistent and overly broad. McDonald said the draft maps and GSBS drawings appeared to show a 10,000‑foot “control development” overlay while the text referenced a 5,000‑foot airport influence area. “Anything outside that 5,000 foot radius is potentially subject to legal challenge,” he said, urging the town to clarify the radius and consult airport operators and affected landowners.

Amy Walker, an attorney for West Desert Airpark, raised a separate legal objection about codifying FAA guidance. “I actually believe it's illegal,” she said, arguing that FAA rules and advisory circulars generally preempt municipal operational regulation and that some penalty language in the draft exceeded state allowable misdemeanor classifications for land‑use enforcement.

Representatives of other affected parties spoke as well. Aaron White, representing Property Reserve and the Church of Jesus Christ of Latter‑day Saints’ adjacent holdings, said he and colleagues were “listening” and working with counsel to understand potential impacts but were not prepared to comment on the ordinance’s merits. Sherry Anderson of Intermountain Regional Landfill asked whether fuel‑farm language and references to FAA recommendations could subject existing tanks or site features to new FAA or municipal enforcement.

Commission discussion focused on several recurring items: the overlay extent shown on consultant maps, the airport emergency plan requirement, pilot and tenant compliance language, runway protection/easements and a “preferred runway” statement. Commissioners and staff debated whether the overlay shown in the GSBS maps should be reduced from an effective 10,000‑foot dimension to the 5,000‑foot airport influence area described in Title 72 of the Utah Code. JUB Engineering and consultant remarks at the meeting reiterated that state guidance commonly uses a 5,000‑foot airport influence area and that the larger 10,000‑foot geometry shown on one map would extend protections and notification obligations much farther into town.

On emergency response, planning staff and some commissioners said the town needs to be apprised of the airport emergency plan to meet public‑safety obligations; staff recommended requiring an FAA‑compliant airport emergency plan be submitted and approved as part of development review while avoiding language that attempts to duplicate FAA approval authority. Commissioners also left in several runway‑protection and limited‑development provisions that staff said are supported by FAA circulars; the commission discussed but did not remove language calling for certain hazard notifications (for example, bird‑attracting uses near landfills) and runway protection easements.

Commissioners debated a “preferred runway” statement intended to encourage quieter operations when feasible; they agreed to retain language recommending Runway 17 as the preferred runway when conditions allow, while recognizing that wind and operational safety determine actual runway use.

After discussion, the commission approved two motions to forward the drafts to town council: one to send Exhibit A (Air Park Mixed Use Zone) to council with the working‑draft revisions and the suggestion that town council consider, at its discretion, allowing up to a 60‑day extension for stakeholders to negotiate; and a second to forward the Airport Overlay draft to council for approval or denial. The commission recorded the motions as approved by roll call.

The commission also directed staff and consultants to: correct and reissue the maps (including reconsidering the overlay geometry so it aligns with the statute’s 5,000‑foot airport influence area), confirm penalty language consistent with state law, and refine the emergency‑plan and pilot‑compliance sections so they require FAA‑compliant plans to be submitted for town review rather than attempt to substitute municipal approval for FAA regulatory functions.

Votes at a glance: the planning commission unanimously approved forwarding (1) Exhibit A, the Air Park Mixed Use Zone, to the town council with the working‑draft revisions and a recommendation that council decide whether to grant a stakeholder extension; and (2) the Airport Overlay draft to the town council for approval or denial. The roll call recorded commissioners voting yes: Kelton; Kyla/Kyle (record shows variations in spelling); David; Jamie; and Wayne.

The commission asked staff to post the revised working draft and respondent letters on the town website and recommended further collaborative review with airport operators, IRL, adjacent property owners and the town council before final action.

The commission meeting closed after scheduling the items to move to the town council agenda.