Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Airport Land Use topic
No spam. Unsubscribe anytime.
Fairfield planning commission debates airpark ordinance, runway protections and residential overlay
Summary
Planning commissioners reviewed a draft airpark ordinance and airport-overlay maps, debated flight limits, hangar uses and crew-rest rules, and flagged potential legal and property-value implications before scheduling a public hearing.
Get email alerts on the Airport Land Use topic
No spam. Unsubscribe anytime.
Fairfield Town Planning and Zoning Commissioners spent more than two hours on a draft airpark ordinance and an airport-overlay map that would change how land near the town airport can be used.
Commissioners and town counsel focused on operations limits, clarifications about FAA authority, runway and aircraft-size thresholds, and how large an overlay the town should adopt. Commissioners and staff also debated whether certain hangar uses — notably crew rest facilities, on-site motels and fuel dispensing — should be permitted by right, by condition, or prohibited.
The draft ordinance would add a new airport zone with several technical limits and a companion “airpark overlay” that applies height and land-use restrictions on parcels near the runway. Todd, the town attorney, told the commission that many of the ordinance’s technical details must be refined to avoid duplicating definitions and accidentally inserting enforceable regulations into the definitions section. He recommended keeping land-use definitions in the town’s broader code and concentrating regulatory language in the ordinance sections where it belongs.
Why this matters: The overlay map covers parcels used for residences, commercial properties and the LDS church site near the north runway, and commissioners repeatedly flagged the risk that strict limits could reduce property values or lead to legal “takings” claims if residential uses are effectively prohibited in impacted zones.
Major points and clarifications
90-day notice for status changes — Commissioners agreed to add a written notice requirement for changes in an airport’s public/private status. Several commissioners supported adding a 90-day written-notice requirement for any change from private to public use (or vice versa) so the town has time to review permitting and compliance obligations.
Flight counts and enforcement — The draft ties some limits to numbers of annual operations (the ordinance draft referenced “less than 10,000 annual operations” for certain runway categories). Commissioners and counsel said enforcement would depend on recordkeeping at the airport and town code-enforcement capacity; counsel observed that requiring logs is possible but that not all operators reliably use them.
Aircraft weight / single-wheel-load debate — The draft currently references FAA thresholds and a “single-wheel gear load” value (12,500 pounds was mentioned repeatedly). Several commissioners said 12,500 pounds describes many general-aviation aircraft and is too high; they discussed lowering thresholds (5,000–12,500 pounds was discussed) or simply regulating by gross weight rather than wheel-load calculations. An aviation engineer consulted by staff recommended using the aircraft’s gross weight in many ordinance places rather than technical single-wheel formulas; the commission asked staff to remove duplicative single-wheel references and standardize on a single plain-weight figure pending legal review.
Runway length, approach limits and visual approaches — Commissioners asked staff to confirm runway length thresholds cited in the draft (5,000 feet, 5,200 feet and a 6,200-foot figure were all referenced in documents), and to verify which runway/approach rules actually apply. The draft restricts some operations to “visual approaches only” and includes a runway-protection-zone and approach-surface diagram; commissioners asked staff to reconcile the table in the ordinance with FAA circulars and to document the source of each numeric limit.
Crew rest facilities, hangar accessory uses and enforcement
The commission reviewed a proposed definition: a “crew rest facility” as a short-term area inside a hangar for flight crew rest that “shall not be used or approved as a permanent residence” and that must be accessory to the hangar’s aviation use. Commissioners asked staff to add a clear time limit or “short-term” definition (several suggested 12–24 hours) and to require tenant-improvement and building-permit review before a rest area could be used for sleep.
Commissioners were split on permitting approach: many said crew rest areas should be allowed as a conditional use so reviewers can impose conditions (fire-safety, septic and building-code compliance) and address problems if a particular rest facility becomes a de-facto residence. Commissioners also asked staff to ensure the fire marshal reviews any fuel- or rest-facility permit and to confirm what building and plumbing approvals are required for occupant safety.
Other uses discussed
- Small motels and full-service crew rest hotels: Commissioners agreed to remove “small motel” from the permitted-uses list and to treat larger or overnight-stay uses as conditional or special uses. Several commissioners said allowing both small motels and individual hangar rest facilities would increase overnight stays and likely increase flight activity. - Aircraft museum / special events: Commissioners suggested moving an aircraft museum and similar public attractions to a conditional-use category so each proposal can be evaluated for traffic, noise and safety impacts. - Fuel farms: Commissioners asked staff to require fire-marshal review and any standard state or county fuel-dispensing permitting. Some said fuel-dispensing that is operationally equivalent to a commercial aviation fuel farm should be handled as a conditional use so proper safety and water/response planning can be required.
Overlay map and limited development zone
Staff presented an overlay map with runway-protection zones, approach surfaces (the red approach bands) and a “no development” or “limited development” band (dark gray and lighter gray on the map). Commissioners and residents noted that the overlay, as drawn, would cover many existing parcels and that prohibiting residential development in the limited-development band could substantially reduce affected owners’ development rights.
Town counsel warned that a broad prohibition on residential uses in an area presently zoned residential could raise constitutional takings claims; counsel recommended the code rely on disclosure requirements and incentives rather than an outright prohibition where possible. Commissioners asked staff to: (1) identify which parcels would be affected, (2) confirm current underlying zoning on those parcels, and (3) prepare alternatives (for example, notice to purchasers and use restrictions rather than a wholesale residential ban).
Enforcement and community concerns
Residents and some commissioners described a recent increase in low-altitude or frequent flights over town and asked what the town can do about frequency, noise and short-circuit “lap” flights. Counsel and staff repeatedly explained that flight altitudes and patterns are governed by the Federal Aviation Administration and that the town’s primary lever is land-use regulation on the ground (for example, restricting sensitive uses in approach/protection zones, or imposing disclosure requirements). Counsel said some ordinance provisions can take effect only when future changes to airport operations occur; others would apply prospectively.
Next steps and commission direction
Commissioners asked staff and counsel to: remove duplicative definitions, replace single-wheel engineering thresholds with a simpler gross-weight standard where appropriate, draft a 90‑day written-notice clause for airport-status changes, add a time-limited definition for “short-term” crew rest, and mark museum/fuel/crew-rest items as conditional uses pending fire-marshal and building-code review. Commissioners also directed staff to prepare parcel-level overlays and to evaluate the takings/legal risk associated with strict residential prohibitions.
The planning commission voted to schedule a public hearing on Sept. 3 for the airpark ordinance and the airpark overlay along with the water ordinance. The commission set the meeting start time for 6 p.m. and told staff to circulate updated language prior to public noticing.
Ending
Commissioners said they intend to craft ordinance language that addresses safety and compatibility while avoiding unnecessary legal exposure; staff and counsel will return revised text and maps for a public hearing and additional review.
