Fairfield planners review proposed West Desert Airport zoning; debate residential limits, hangar oversight and crew-rest rules

Fairfield’s Planning and Zoning Commission on Aug. 6 reviewed a draft ordinance to regulate land use at the West Desert Airport (referred to in the draft as the airpark) and asked staff and legal counsel to refine definitions and implementation language before formal public hearings.

Commissioners and the mayor summarized the background: residents circulated a petition opposing some airport activities and asked the town to tighten land-use controls; the draft ordinance follows an airport land-use guide used previously in local decisions and was prepared with input from engineering and legal consultants, including a contractor identified as JUV Engineering.

Key topics during the discussion included the scope of the airport overlay (the draft follows the guide’s method of using runway length to set an overlay that extends beyond runway ends), whether residential uses should be prohibited inside the overlay (the draft would limit or bar residential development within about 3,200 feet of runway ends depending on runway length), and the legal and takings implications for property owners whose parcels currently allow residential use.

Legal counsel told commissioners that municipalities routinely change zoning and adopt overlay restrictions, but that prohibitions that substantially impair owner expectations can raise constitutional takings issues; counsel recommended careful drafting and consideration of grandfathering for existing lawful uses. Commissioners asked staff to identify parcel-level zoning and whether particular properties are already in light industrial or residential zones to understand practical effects.

FAA jurisdiction and operational controls were discussed at length. Commissioners noted the town cannot directly enforce aircraft flight patterns once airplanes are airborne; the FAA controls federal airspace and issues traffic-pattern approvals. However, planners and counsel said municipalities and airport sponsors can seek noise-mitigation measures, preferred-runway designations or traffic‑pattern requests through FAA processes, and that development agreements could include monitoring and reporting provisions for operations.

Commissioners also debated how to regulate hangars and tenant improvements. Several commissioners and staff said many hangars were built as “shells” and later modified without consistent tenant-improvement permits; the commission raised questions about ownership records, building permits on file with the county, fire inspections and whether hangar parcels and owner names should be recorded in county records to improve enforcement.

On use categories, the draft lists aviation‑related uses including airframe repair, fuel facilities, crew‑rest facilities and a small motel (up to 20 rooms) intended to serve transient pilots and crews. Commissioners questioned whether crew‑rest rooms would be enforceable (short-term versus permanent residence), whether a motel might be more straightforward for regulation and town revenue, and whether taverns or alcohol-serving uses should be allowed given safety concerns.

Other technical matters flagged for revision included: runway weight limits and whether town language should mirror FAA advisory circular definitions; whether to adopt specific FAA advisory circulars or reference them as of a fixed date; night‑time operations and lighting/visibility rules; and how the airport overlay would interact with existing parcels.

The commission did not adopt the ordinance at the meeting. Members asked staff to compile clearer parcel maps, verify which hangars/parcels are recorded with the county, confirm FAA advisory-circular references and identify options for development agreements and monitoring provisions. A follow-up planning meeting was scheduled to continue ordinance work prior to public hearing.