Alberta Regulator Rejects Gas Plant for Canada's Largest AI Data Centre in Olds, Citing Major Deficiencies

AUC nixed Synapse's 1.4-GW gas plant for an Olds data centre, citing errors, gaps, and hidden diesel units. Residents exhaled; for builders, do the homework or expect delays.

Published on: Mar 07, 2026
Alberta Regulator Rejects Gas Plant for Canada's Largest AI Data Centre in Olds, Citing Major Deficiencies

AUC rejects gas-fired generation facility for proposed Olds AI data centre: practical takeaways for builders and developers

Alberta's utilities regulator has turned down Synapse Real Estate Corp.'s application to build a 1.4-gigawatt natural gas generation facility in Olds. The plant was intended to feed a data centre campus the company billed as Canada's largest.

The commission cited "significant deficiencies" in the filing, including errors, missing information, and contradictions across documents. Synapse can reapply, but only with a submission that meets legislative and regulatory requirements.

The site spans 121 hectares at Highway 2A and Highway 27, close to existing homes. Some residents expressed relief at the pause, pointing to noise, water use, and transparency concerns.

What the AUC flagged

  • Public engagement: Consultation with more than 700 residences within 800 metres started just 14 days before filing. The participant involvement package lacked required detail.
  • Undisclosed equipment: A proposed set of roughly 600 diesel backup units (about 2.6 MW each) was not discussed in the January 27, 2026 information package provided to residents.
  • Environmental work: The environmental evaluation was a draft with incomplete citations, missing figures, and mark-ups. Wildlife and wetland conclusions relied on limited winter field studies.
  • Noise: The noise impact assessment did not model worst-case scenarios, among other issues.

Voices from Olds

Rachel Sorenson said she was "elated" by the decision. "I feel like I'll be able to sleep again… without two years of construction and knowing that for now, we can rest easy."

Bek MacIntosh called it a pause, not a finish line. "There was a momentary sigh of collective relief… but an almost dawning awareness that this is so far down the road and such a large scale."

Why this matters for real estate and construction teams

Large data centres are hungry for reliable electricity and standby generation. That scale magnifies scrutiny on siting, acoustics, emissions, water, and community impact-especially when projects sit next to established neighbourhoods.

The Olds decision is a reminder: incomplete studies, late outreach, or missing equipment disclosures can stall a schedule more than any design iteration. Permitting is a deliverable, just like steel, switchgear, and cooling gear.

Regulatory reference points (Alberta)

Practical checklist to avoid the same outcome

  • Engagement start line: Begin outreach 60-90 days before filing. Map at least an 800 m radius, log all contacts, and document responses.
  • Disclose everything that makes noise, heat, light, or emissions: Count, rating, and duty cycle of every turbine, diesel unit, chiller, cooling tower, and emergency system. Include fuel storage and refuelling plans.
  • Noise modelling: Run worst-case scenarios per Rule 012, including cumulative effects and low-frequency content. Provide mitigations (enclosures, barriers, orientation) with performance specs.
  • Environmental baseline: Conduct multi-season fieldwork for wildlife and wetlands. Provide complete figures, citations, QA/QC, and geospatial files. Avoid draft or placeholder content.
  • Water and wastewater: Quantify peak and average demand, source reliability, treatment approach, blowdown, and discharge permits. Align with municipal capacity and capital plans.
  • Air emissions: Model criteria pollutants for all combustion sources (prime and standby). Include start/stop transients and maintenance runs. Confirm permitting thresholds and monitoring.
  • Construction impacts: Publish a two-year construction phasing plan with traffic routing, working hours, dust, lighting, and complaint response protocols.
  • Land use and setbacks: Show conformance with zoning, noise receptors, and sensitive areas. Add buffers, berms, and architectural screening next to homes.
  • Electrical strategy: Document grid interconnection status, contingency plans, and how onsite generation and storage interact with the grid under normal and emergency conditions.
  • Reliability without surprises: If standby diesel is required, justify unit count and runtime, and assess alternatives (gas-fired standby, battery-based ride-through, demand management) to shrink diesel footprint.
  • Third-party reviews: Commission independent peer reviews of acoustics, environmental, and electrical studies before filing.
  • Plain language: Publish a resident-friendly summary (10 pages or less) that mirrors the technical application-no gaps between what's filed and what's shared locally.

Site selection and design notes for data-centre campuses

  • Proximity trade-offs: Highway access is good for logistics, but adjacent housing tightens noise and visual limits. Budget early for enclosures and façade treatments.
  • Scale in phases: Submit a phased plan with cumulative impact modelling and triggers for additional mitigations as capacity rises.
  • Cooling strategy: Compare water use, plume, and noise across air-cooled, evaporative, and hybrid systems; size make-up water and blowdown accordingly.
  • Resilience mix: Pair onsite generation with storage to cut diesel starts, flatten peaks, and meet acoustic limits at night.

Community expectations have shifted

Residents want early notice, real numbers, and clear maps. Anything short of that reads as a red flag, especially near established neighbourhoods.

Synapse says the project is intended as a 100-year fixture in Olds and has committed to a longer-term dialogue with regulators and neighbours. That commitment will need to show up in the next filing as complete studies, earlier outreach, and tighter design controls.

If you're preparing a similar filing

  • Run an internal "AUC audit" against Rule 007 and Rule 012 before submission.
  • Publish the same figures and equipment lists to residents that you submit to the regulator.
  • Anticipate worst-case noise, winter field constraints, and construction fatigue. Design mitigations into the base scope, not as add-ons.
  • Track every condition you're willing to accept and convert them into enforceable commitments.

Further learning


Get Daily AI News

Your membership also unlocks:

700+ AI Courses
700+ Certifications
Personalized AI Learning Plan
6500+ AI Tools (no Ads)
Daily AI News by job industry (no Ads)