You’re out of free articles.
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
Sign In or Create an Account.
By continuing, you agree to the Terms of Service and acknowledge our Privacy Policy
Welcome to Heatmap
Thank you for registering with Heatmap. Climate change is one of the greatest challenges of our lives, a force reshaping our economy, our politics, and our culture. We hope to be your trusted, friendly, and insightful guide to that transformation. Please enjoy your free articles. You can check your profile here .
subscribe to get Unlimited access
Offer for a Heatmap News Unlimited Access subscription; please note that your subscription will renew automatically unless you cancel prior to renewal. Cancellation takes effect at the end of your current billing period. We will let you know in advance of any price changes. Taxes may apply. Offer terms are subject to change.
Subscribe to get unlimited Access
Hey, you are out of free articles but you are only a few clicks away from full access. Subscribe below and take advantage of our introductory offer.
subscribe to get Unlimited access
Offer for a Heatmap News Unlimited Access subscription; please note that your subscription will renew automatically unless you cancel prior to renewal. Cancellation takes effect at the end of your current billing period. We will let you know in advance of any price changes. Taxes may apply. Offer terms are subject to change.
Create Your Account
Please Enter Your Password
Forgot your password?
Please enter the email address you use for your account so we can send you a link to reset your password:
The administration argued in the name of national defense — but Orsted had receipts.

When the Trump administration ordered work on Orsted’s Revolution Wind offshore wind project to shut down in late August, it cited national security concerns as the reason for the delay.
Within weeks, a federal judge had lifted the stop work order, allowing construction to proceed.
What happened in between matters. In its rush to stop a wind project, the Trump administration exposed the first cracks in its anti-wind policy agenda — a loss that may embolden companies targeted by the crackdown on renewable energy development to fight back.
Orsted, the Danish wind giant, was more than halfway done building Revolution Wind by August 22, the day the Bureau of Ocean Energy Management ordered an immediate stop to construction. In a one-page letter explaining the order, the agency dedicated a single paragraph to the rationale behind its decision: “BOEM is seeking to address concerns related to the protection of national security interests of the United States and prevention of interference with reasonable uses of the exclusive economic zone, the high seas, and the territorial seas,” it said.
Orsted filed a lawsuit against the U.S. government within days and asked for a preliminary injunction against the stop-work order. The Trump administration had acted arbitrarily when it halted construction on Revolution Wind, the company argued, a violation of the Administrative Procedures Act, which forces the government to have at least some sensible reason for its decision-making.
There were urgent financial stakes to the court’s decision, the company said. On top of strict timelines for completing the project that were laid out in power purchase agreements, the cable installation company working on Revolution Wind has just a brief window before it is booked for other projects through mid-2028. Unless the judge acted quickly, according to Orsted, Revolution Wind could face “project cancellation and termination of the enterprise,” at an estimated cost of more than $1 billion.
After Orsted filed its suit, the attorneys general of Connecticut and Rhode Island — two of the three states designated to receive electricity from Revolution Wind — soon followed course. The Trump administration responded by doubling down on its claims related to national defense. Revolution Wind, officials argued, would negatively impact radar detection and result in dangerous electromagnetic emissions. They also asserted that Defense Department officials were overruled or ignored when they raised concerns about this matter in the review process for the project, which received its final permits in 2023. (It’s worth noting the Trump administration’s legal filings refer to the military as the Department of War, or DOW.)
The Department of the Interior’s acting assistant secretary for land and minerals management, Adam Suess, told the court on September 12 in a sworn declaration that Revolution Wind had not fully addressed a host of concerns. Suess elaborated on the stop work order, asserting that it concerned the project’s “continued inability to reach certain mitigation agreements” with the military and the National Oceanic and Atmospheric Administration. Suess stated Revolution Wind was not in full compliance with the terms of its construction and operations plan, which are subject to government approval. He also said there were outstanding issues with Revolution Wind’s coordination with military operators at sea, and that there was still “risk from distributed optical fiber sensing and acoustic monitoring equipment.
“The Department has been in touch with NOAA and the DOW to gather more information,” the filing said, somewhat cryptically.
Suess also acknowledged that the Trump administration is reconsidering its prior green lights for Revolution Wind, including its approval of the construction and operations plan, linking this to a broader all-of-government review of the offshore wind industry Trump ordered on Day One via executive order.
In response, Orsted called the government’s bluff. The company submitted sworn declarations from top company officials who had worked on Revolution Wind, attesting to the fact that before Trump came into office, the military and NOAA were saying everything looked A-OK.
“Mr. Suess’ declaration makes new allegations against Revolution Wind that were not mentioned in the stop work order,” Orsted’s attorneys wrote in their reply. “These new allegations are factually inaccurate and controverted by Revolution Wind’s compliance with project requirements.”
One of Orsted’s declarations was from Melanie Gearon, the company’s head of northeast permitting. Suess had claimed that Revolution Wind was far from reaching a critical agreement with NOAA’s Fisheries division, known as the National Marine Fisheries Service, to mitigate the effects of sea surveys on fishing vessels. But Gearon painted a completely different picture, detailing years of negotiations with NOAA and BOEM about how to handle the surveys.
These talks had apparently continued months into the Trump administration. Orsted submitted an email from BOEM to the company dated July 9, in which an official explicitly says that agency staff were discussing scenarios where Orsted could just “state that they are continuing to work with [the National Marine Fisheries Service] on a Survey Mitigation agreement, which could still be submitted at a later date.” Gearon said the company had received “updated cost modeling” from the agency as recently as September 9, days before Suess’ comments were submitted in court.
Then came the comments from Orsted’s head of marine affairs, Edward LeBlanc, who served in the military for decades and worked on offshore energy oversight. He told the court that the Navy had never once raised any issues with the project’s export cable and that as recently as July 2025, no military officials had expressed lingering concerns about electromagnetic emissions, vessel collisions or other potential national security problems.
“To date, Revolution Wind has never received a notice or any indication that it has failed to coordinate with DOD regarding its offshore activities, or that the U.S. Navy or DOD has any concerns with the ongoing coordination,” LeBlanc stated.
It was after this filing that the justice overseeing the case, U.S. District Judge Royce Lamberth, approved the preliminary injunction and lifted the stop-work order.
As long as offshore wind has existed there has been tension with the U.S. military over use of the sea, and it is true that turbines could hinder radar detection.
In 2011, the Defense Department established a “clearinghouse” to resolve any potential issues with ocean energy development of any kind, whether oil, gas, or wind power. The clearinghouse reviews more than 5,000 projects every year, and its activities include regular give and take with the Interior Department and Federal Aviation Administration. One of the many pieces of evidence Orsted submitted in the Revolution Wind case was a December 2024 letter from the clearinghouse stating the project “would not have adverse impacts to DOD missions in the area.”
Josh Kaplowitz, an environmental attorney who represents renewable energy companies including offshore wind developers, and who previously worked in the Interior Department solicitor’s office, told me: “There is not a single situation I am aware of where the Defense Department ever requested something and the approving agency said, ‘No, we’re going to do something else.’”
“There are some problems with coming in after the fact and coming up with post hoc national security rationalizations when the process of review was so rigorous,” Kaplowitz said.
Independent analysis has also cleared the military’s consultation with offshore wind permitting agencies of having any serious issues.
Earlier this year the Government Accountability Office — a quasi-independent watchdog under the control of Congress — released a detailed review of the offshore wind industry’s federal permitting process. The review was requested by one of the sector’s biggest adversaries in Congress, Representative Chris Smith of New Jersey, who has been heavily involved in fighting offshore wind development in his home state.
Smith, a Republican, ultimately celebrated the review’s publication because it pointed out certain ways offshore wind could impact radar detection and military readiness. In his public statements, however, the lawmaker left out a key detail of the report — that it raised no issues with interactions between the military and offices involved in greenlighting offshore wind projects. In fact, it went into great detail on the lengths researchers and government officials had gone toward solving these potential problems.
“We didn’t have any recommendations there,” Frank Russo, director of GAO’s natural resources department, told me in an interview. “It seemed like coordination was going well, that DOD was satisfied with what was going on, and if there were concerns they could be mitigated.”
Russo said that Defense officials had for years been involved in offshore wind leasing, meaning that military staff from the Navy and Coast Guard had already weighed in on potential safety and readiness problems before companies even knew where they were allowed to build, and certainly prior to the project-specific permitting stage.
“At the very start of it, they know where their main concerns are,” Russo said of the Defense Department’s role in offshore wind development.
The Interior Department normally declines to comment on pending litigation. But I still wanted to ask Interior to comment on the assertions from Russo that the Interior Department and military were properly handling the security implications of offshore wind. It felt especially important to ask them about this because Interior Secretary Doug Burgum last month explained the Revolution Wind stop work order on national TV by claiming radar interference would leave the country vulnerable to “swarm attacks” from underwater drones.
Tory Peabody, a Bureau of Ocean Energy Management spokesperson, provided the following statement to Heatmap: “As a result of the court’s decision, Revolution Wind will be able to resume construction as BOEM continues its investigation into possible impacts by the project to national security and prevention of other uses on the Outer Continental Shelf. The Department of the Interior remains committed to ensuring that prior decisions are legally and factually sound.”
Editor’s note: This story has been updated to include a statement from BOEM, and to remove an errant “not” in the second-to-last paragraph.
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
A third judge rejected a stop work order, allowing the Coastal Virginia offshore wind project to proceed.
Offshore wind developers are now three for three in legal battles against Trump’s stop work orders now that Dominion Energy has defeated the administration in federal court.
District Judge Jamar Walker issued a preliminary injunction Friday blocking the stop work order on Dominion’s Coastal Virginia offshore wind project after the energy company argued it was issued arbitrarily and without proper basis. Dominion received amicus briefs supporting its case from unlikely allies, including from representatives of PJM Interconnection and David Belote, a former top Pentagon official who oversaw a military clearinghouse for offshore wind approval. This comes after Trump’s Department of Justice lost similar cases challenging the stop work orders against Orsted’s Revolution Wind off the coast of New England and Equinor’s Empire Wind off New York’s shoreline.
As for what comes next in the offshore wind legal saga, I see three potential flashpoints:
It’s important to remember the stakes of these cases. Orsted and Equinor have both said that even a week or two more of delays on one of these projects could jeopardize their projects and lead to cancellation due to narrow timelines for specialized ships, and Dominion stated in the challenge to its stop work order that halting construction may cost the company billions.
It’s aware of the problem. That doesn’t make it easier to solve.
The data center backlash has metastasized into a full-blown PR crisis, one the tech sector is trying to get out in front of. But it is unclear whether companies are responding effectively enough to avoid a cascading series of local bans and restrictions nationwide.
Our numbers don’t lie: At least 25 data center projects were canceled last year, and nearly 100 projects faced at least some form of opposition, according to Heatmap Pro data. We’ve also recorded more than 60 towns, cities and counties that have enacted some form of moratorium or restrictive ordinance against data center development. We expect these numbers to rise throughout the year, and it won’t be long before the data on data center opposition is rivaling the figures on total wind or solar projects fought in the United States.
I spent this week reviewing the primary motivations for conflict in these numerous data center fights and speaking with representatives of the data center sector and relevant connected enterprises, like electrical manufacturing. I am now convinced that the industry knows it has a profound challenge on its hands. Folks are doing a lot to address it, from good-neighbor promises to lobbying efforts at the state and federal level. But much more work will need to be done to avoid repeating mistakes that have bedeviled other industries that face similar land use backlash cycles, such as fossil fuel extraction, mining, and renewable energy infrastructure development.
Two primary issues undergird the data center mega-backlash we’re seeing today: energy use fears and water consumption confusion.
Starting with energy, it’s important to say that data center development currently correlates with higher electricity rates in areas where projects are being built, but the industry challenges the presumption that it is solely responsible for that phenomenon. In the eyes of opponents, utilities are scrambling to construct new power supplies to meet projected increases in energy demand, and this in turn is sending bills higher.
That’s because, as I’ve previously explained, data centers are getting power in two ways: off the existing regional electric grid or from on-site generation, either from larger new facilities (like new gas plants or solar farms) or diesel generators for baseload, backup purposes. But building new power infrastructure on site takes time, and speed is the name of the game right now in the AI race, so many simply attach to the existing grid.
Areas with rising electricity bills are more likely to ban or restrict data center development. Let’s just take one example: Aurora, Illinois, a suburb of Chicago and the second most-populous city in the state. Aurora instituted a 180-day moratorium on data center development last fall after receiving numerous complaints about data centers from residents, including a litany related to electricity bills. More than 1.5 gigawatts of data center capacity already operate in the surrounding Kane County, where residential electricity rates are at a three-year high and expected to increase over the near term – contributing to a high risk of opposition against new projects.
The second trouble spot is water, which data centers need to cool down their servers. Project developers have face a huge hurdle in the form of viral stories of households near data centers who suddenly lack a drop to drink. Prominent examples activists bring up include this tale of a family living next to a Meta facility in Newton County, Georgia, and this narrative of people living around an Amazon Web Services center in St. Joseph County, Indiana. Unsurprisingly, the St. Joseph County Council rejected a new data center in response to, among other things, very vocal water concerns. (It’s worth noting that the actual harm caused to water systems by data centers is at times both over- and under-stated, depending on the facility and location.)
“I think it’s very important for the industry as a whole to be honest that living next to [a data center] is not an ideal situation,” said Caleb Max, CEO of the National Artificial Intelligence Association, a new D.C.-based trade group launched last year that represents Oracle and myriad AI companies.
Polling shows that data centers are less popular than the use of artificial intelligence overall, Max told me, so more needs to be done to communicate the benefits that come from their development – including empowering AI. “The best thing the industry could start to do is, for the people in these zip codes with the data centers, those people need to more tangibly feel the benefits of it.”
Many in the data center development space are responding quickly to these concerns. Companies are clearly trying to get out ahead on energy, with the biggest example arriving this week from Microsoft, which pledged to pay more for the electricity it uses to power its data centers. “It’s about balancing that demand and market with these concerns. That’s why you're seeing the industry lean in on these issues and more proactively communicating with communities,” said Dan Diorio, state policy director for the Data Center Coalition.
There’s also an effort underway to develop national guidance for data centers led by the National Electrical Manufacturers Association, the American Society of Heating, Refrigerating, and Air-Conditioning Engineers, and the Pacific Northwest National Laboratory, expected to surface publicly by this summer. Some of the guidance has already been published, such as this document on energy storage best practices, which is intended to help data centers know how to properly use solutions that can avoid diesel generators, an environmental concern in communities. But the guidance will ultimately include discussions of cooling, too, which can be a water-intensive practice.
“It’s a great example of an instance where industry is coming together and realizing there’s a need for guidance. There’s a very rapidly developing sector here that uses electricity in a fundamentally different way, that’s almost unprecedented,” Patrick Hughes, senior vice president of strategy, technical, and industry affairs for NEMA, told me in an interview Monday.
Personally, I’m unsure whether these voluntary efforts will be enough to assuage the concerns of local officials. It certainly isn’t convincing folks like Jon Green, a member of the Board of Supervisors in Johnson County, Iowa. Johnson County is a populous area, home to the University of Iowa campus, and Green told me that to date it hasn’t really gotten any interest from data center developers. But that didn’t stop the county from instituting a one-year moratorium in 2025 to block projects and give time for them to develop regulations.
I asked Green if there’s a form of responsible data center development. “I don’t know if there is, at least where they’re going to be economically feasible,” he told me. “If we say they’ve got to erect 40 wind turbines and 160 acres of solar in order to power a data center, I don’t know if when they do their cost analysis that it’ll pencil out.”
Plus a storage success near Springfield, Massachusetts, and more of the week’s biggest renewables fights.
1. Sacramento County, California – A large solar farm might go belly-up thanks to a fickle utility and fears of damage to old growth trees.
2. Hampden County, Massachusetts – The small Commonwealth city of Agawam, just outside of Springfield, is the latest site of a Massachusetts uproar over battery storage…
3. Washtenaw County, Michigan – The city of Saline southwest of Detroit is now banning data centers for at least a year – and also drafting regulations around renewable energy.
4. Dane County, Wisconsin – Another city with a fresh data center moratorium this week: Madison, home of the Wisconsin Badgers.
5. Hood County, Texas – Last but not least, I bring you one final stop on the apparent data center damnation tour: Hood County, south of the Texas city of Fort Worth.