Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Data Center Noise And Zoning topic
No spam. Unsubscribe anytime.
Prince William Board orders comprehensive zoning rewrite, moves forward on new noise rules after years of data‑center complaints
Summary
After months of resident complaints about low‑frequency noise from data centers, the Board of County Supervisors voted to initiate a comprehensive zoning‑ordinance update and discussed a proposed rewrite of the county noise ordinance that would add low‑frequency (octave‑band) limits, continuous‑noise standards and monitoring requirements.
Get email alerts on the Data Center Noise And Zoning topic
No spam. Unsubscribe anytime.
The Prince William County Board of Supervisors voted March 18 to begin a comprehensive overhaul of the county’s zoning ordinance and heard detailed recommendations for rewriting the county’s 30‑year‑old noise law in response to resident complaints about low‑frequency noise from data center operations.
The board formally initiated a zoning text amendment to update Chapter 32—revising definitions, overlay districts, buffer and setback standards, and modernizing development standards—after staff described a two‑year minimum timeline for the work. The motion to initiate the comprehensive update passed during the meeting.
Residents, neighborhood representatives and technical consultants told the board the county’s current A‑weighted noise standard does not capture the kinds of continuous, low‑frequency sounds that neighbors say have disrupted sleep and damaged quality of life in communities such as Great Oak and Wellington Glen.
David Nelson, an acoustical consultant hired by the county, told supervisors that A‑weighted measures, long used to assess roadway and aircraft noise, undercount low frequency energy. He and consultant JMT recommended adding C‑weighted measures and octave‑band analysis, and to classify noise enforcement into impulse, intermittent and continuous categories. Nelson said proposed continuous limits, expressed as octave‑band criteria, would produce a daytime environment roughly equivalent to 45 dBA and about 40 dBA at night — approximately 10–15 dB lower than existing county practice in some locations — and that meeting those levels would require different measurement and enforcement practices.
County staff summed up the technical proposals and enforcement needs: adoption of octave‑band and DBC/DBC‑style measurements, continuous monitoring at sites that meet low‑frequency criteria, expanded training for county personnel and likely budget requests for equipment and consultant support. The packet presented to the board included initial cost estimates: roughly $50,000 per “Level 1” meter (staff proposed buying 10), in‑house training courses (about $2,000), consultant support for technical reviews (roughly $3,000 or more per complex test) and multi‑day ambient studies (about $30,000 each), figures staff said would be refined in later budget discussions.
Public commenters and members of the Data Center Ordinance Advisory Group (DCOAG) urged several concurrent steps: stricter siting and setback rules to keep large clusters of data centers away from homes, requirements for pre‑development noise modeling for multi‑building campuses, and creation of a “noise budget” or campus‑level plan to prevent cumulative sound from ratcheting up as separate buildings come online. Residents described weeks‑ and months‑long sleep disruption and reported ongoing measurement campaigns capturing low‑frequency signatures they say correspond with data‑center operations.
Staff and consultants acknowledged limitations. Nelson warned that strict new limits could generate “false positives” in parts of the county where high background levels (traffic, HVAC, commercial activity) are normal; he said longer monitoring and professional analysis would be needed there. County staff and the county attorney noted Virginia’s Dillon Rule and other state limits could constrain some local options and that some enforcement and permitting changes may require legislative action or a zoning map amendment.
Supervisors generally expressed support for a rewrite of the noise ordinance and for moving the zoning rewrite forward, while asking staff to refine the technical thresholds, enforcement approach and estimated costs. The board directed staff to continue coordinating the data‑center and noise work with other parallel efforts—such as changes to overlay districts and to the Design and Construction Standards Manual—in order to produce an enforceable package.
The board’s initiation of the zoning ordinance rewrite is intended to align the county’s land‑use rules with the 2040 comprehensive plan; staff estimated a minimum two‑year timeline to complete consultant onboarding, community engagement, drafting and hearings. Staff said the DCOAG would be engaged as part of the process but that formal siting or campus boundary studies will proceed on their own parallel schedule and may include DCOAG input.
In closing, county leaders reiterated that while data center development has brought substantial tax revenue, residents’ complaints about continuous low‑frequency noise require a combination of: faster enforcement tools, new technical monitoring standards, and longer‑term land‑use solutions such as revised siting, setbacks and campus noise budgets.
