Council weighs options on Rocky Mountain Metropolitan Airport noise; staff to seek expert briefing

Lafayette councilors on July 2 discussed growing community concerns about noise from Rocky Mountain Metropolitan Airport (RMMA), focused primarily on flight‑training traffic and frequent touch‑and‑go operations. Staff outlined voluntary noise abatement options, the airport’s ongoing FAA‑funded Part 150 noise compatibility study, and recommended steps for coordination.

RMMA background and issues: RMMA is an FAA‑designated general aviation reliever airport near U.S. 36 that supports business aircraft, flight training, charters and wildland firefighting. Staff said the airport averages roughly 250,000–300,000 annual operations and that more than half of operations at RMMA are associated with flight training, including small piston‑engine aircraft that use leaded fuel, fly lower and are louder at ground level.

Part 150 study and limits: The airport is undertaking a Phase 1 Part 150 study — an FAA program that maps noise exposure and can support voluntary noise compatibility measures and limited mitigation programs (for example, insulation funds where noise contours meet FAA thresholds). City staff said Lafayette is unlikely to fall within the 65 DNL noise contour that typically triggers FAA mitigation funding, and that Part 150 outcomes are therefore unlikely to deliver direct mitigation dollars for Lafayette households; the study’s noise exposure mapping, however, will clarify regional footprints and voluntary measures.

Engagement options: Staff discussed several next steps: expanding partnerships with adjacent communities (Louisville, Superior, Westminster, Broomfield and Boulder County), continued engagement with Jefferson County and RMMA leadership (RMMA has offered airport tours and an advisory board seat), and retaining external aviation or legal consultants for technical analysis and advocacy. Staff said legal consultants the city consulted advised that litigation is unlikely to succeed for noise complaints and that dollars are more productively spent on targeted technical expertise and coalition advocacy to engage FAA and airport operators.

Council direction: Members requested a staged approach. They asked staff to (1) arrange an expert briefing for council on legal and operational landscape, (2) reach out to neighboring jurisdictions and regional partners to coordinate joint engagement, (3) seek the airport’s information on recent route changes and timing, and (4) explore a small consultant engagement (or shared engagement with neighboring jurisdictions) to help identify FAA contacts, explain Part 150 implications and advise on advocacy strategies. Council also suggested using national associations (for example, National League of Cities) and regional partners to amplify requests to the FAA.

What’s next: Staff will schedule an expert briefing (legal and operational) for Council and follow up with Jefferson County and RMMA on specific recent route changes and the Part 150 timeline. Staff said RMMA has an open seat on its advisory board and a council member or neighboring‑jurisdiction representative could apply to increase regional representation on airport advisory processes.

Limitations: Staff emphasized that RMMA and the FAA control different elements: RMMA manages ground operations and voluntary airport programs; the FAA controls airspace and flight routing rules. Because of this division, staff said a coalition of affected communities and technical expertise would be the most viable path for influencing flight routing and noise outcomes.