Catalyst N° 114 of 125 25 Jun 2026
How data centers are complicating transmission expansion
with Maeve Allsup, senior reporter, Latitude Media
In this note
The question
Why is a transmission line that the AI boom made more necessary getting harder to build because of the AI boom?
The answer
Because the rules for deciding who pays assumed load growth is spread roughly evenly around a region, and concentrated data center growth broke that assumption. Once one state asks why its ratepayers should fund a line that mostly serves someone else’s data centers, answering honestly means reopening cost allocation for the whole region, which nobody has done. The line sits in limbo meanwhile, and Allsup is less than optimistic about this one, with the caveat that it is early.
03The argument
The project is the Mid-Atlantic Resiliency Link: about 107 miles, roughly $960 million, developed by NextEra, running from southwestern Pennsylvania to northern Virginia through Maryland and West Virginia. PJM, the regional grid operator, approved it in 2022 as a reliability project addressing a shortage of west-to-east capacity, driven largely by growing data center load in northern Virginia, under the standard model that spreads costs across the region while assigning a bigger share to the zone expected to benefit most. Note the date: ChatGPT had not been released. NextEra then spent years in development and only began filing for state siting approvals in 2025 and this spring. The intuition Kann puts on the table is the obvious one. Demand exploded in exactly the place the line was meant to serve, so everyone should now want it faster and bigger. The reverse happened.
The reason is that regional cost sharing is a reciprocity bargain. Virginia ratepayers help fund a line in New Jersey on the understanding that New Jersey will return the favor, and it evens out because growth is roughly even. Concentrated growth destroys the evening-out. So consumer advocates now argue first that data centers should pay, and failing that, that Virginia ratepayers should carry the bulk. Maryland took the allocation to federal regulators at FERC in 2024 arguing Virginia should pay more, and was rejected. It returned in May 2026 with a broader ask: assign data-center-driven transmission costs to the specific zone, in this case Dominion’s, and let the utility work out internally how to make data centers pay, a version that would apply to future lines too. NextEra faces pushback at all four state commissions, and the March 2026 ratepayer protection pledge the hyperscalers signed at the White House now turns up in filings as leverage.
The deeper problem is that the mechanism everyone points to does not fit transmission. The hyperscaler playbook works when the cost is attributable: negotiate a tariff with the local utility covering the incremental generation and any specific upgrade your load requires, then announce it with community investment and a claim of no detrimental rate impact. A multi-state line serving many customers has no comparable instrument. Kann calls it a tragedy of the commons and cannot see how joint payment would be structured; Allsup says the systems simply do not exist yet and calls it building the plane while flying it. Timing cuts both ways. Construction is targeted for 2029 and operation years later, well past the horizon data center developers plan to, and nobody knows the retroactivity rule. If FERC decides how data centers must cover grid upgrade costs, does that reach a line approved in 2022? Allsup says plainly that she does not know and neither does NextEra, and that the question of what date divides projects presumed to serve data centers from those judged under the old framework keeps coming up in her reporting.
It would be a mistake to read this as data centers alone stopping the line. Asked to separate generalized anti-data-center sentiment from the specific northern Virginia cost question, Allsup answers that it is all of the above. The ordinary siting objections are all present, property values, agriculture, views, pace of life, and opposition runs from individual landowners through state legislators to a state consumer advocate at FERC. She also notes that every data center already running in northern Virginia sits on infrastructure the whole region paid for and nobody objected at the time; what changed is that people are watching. Kann’s counterfactual has the same shape: without the AI wave NextEra would still have needed four state approvals, and states might have made a version of this argument anyway. What the boom added was magnitude, which makes it harder to argue the line does not disproportionately serve data centers, and a generalized backlash for which this project has become a convenient vessel. The conclusion is not that data centers are hard to serve. It is that transmission fails for reasons people mostly do not name: everyone reaches first for NIMBYism, and here NIMBYism is not really the story.
04What you need to know first
- Cost allocation
- The rules deciding which ratepayers pay for a transmission line and in what proportion. Because a line crosses states while its benefits do not divide neatly, this is where multi-state transmission usually breaks, and it is the entire dispute here.
- PJM
- The regional grid operator that plans and approves transmission across the mid-Atlantic, including all four states this line crosses. It approves the project and sets the regional cost-sharing model; it does not grant state siting permits, which are separate and are where the fight is now.
- FERC
- The federal regulator with authority over interstate transmission and cost allocation formulas. States appeal there when a regional allocation looks unfair, and it has an open rulemaking on whether data centers should cover all the grid upgrade costs they cause.
- Ratepayer protection pledge
- The March 2026 White House commitment by hyperscalers to cover the cost of power infrastructure their data centers require. Kann notes it has no teeth, which has not stopped its being cited in filings.
05Details worth keeping
- The name is wrong throughout the episode. Both speakers call it the Mid-Atlantic Reliability Line; an editor’s note on the source page corrects it to Mid-Atlantic Resiliency Link.
- The approval document helps both sides. PJM specifically cited large load growth including data centers in northern Virginia, but approved the line as a reliability project, and did so before the AI boom. That ambiguity is why nobody can settle whether this is a data center line.
- Allsup’s framing of the timing problem: the project is in the right place at maybe the wrong time.
- Local opposition is not confined to the data centers. She reports on a project in Indiana where residents were tracking the roads that would be needed to build the substations, not just the facility itself. She distinguishes that scrutiny from misinformation: residents are trying to follow water use, chip types and cooling proposals, all genuinely hard, and she notes that transmission cost allocation confuses her too, and she covers energy.
- Other forms of backlash Kann lists: talk of moratoria or temporary pauses locally, and states suspending sales and use tax exemptions for data centers.
- Kann’s read on the pledge is two-sided. He thinks hyperscalers should be held to it, but expects it to be wielded as a cudgel in any fight over a tariff or a line. Allsup calls that ironic, given it was designed partly as a speed-to-power and public-sentiment play.
- Allsup’s watch list: how fast the data center projects themselves get approved and built, what generation approvals they get, and how the utility tariffs tying data center costs to data centers fare, since those draw opposition of their own.
06Claims worth citing
All figures and regulatory status as stated on 2026-06-25. This is an active proceeding, and Allsup says a FERC ruling might land between the recording and publication, so the status is the most perishable part of this note.
- The line: about 107 miles, roughly $960 million expected cost, developed by NextEra, southwestern Pennsylvania to northern Virginia through Maryland and West Virginia. Allsup
- Approved by PJM in 2022 as a reliability project adding west-to-east capacity, largely to serve growing data center load in northern Virginia. Allsup
- Construction targeted to begin in 2029. Kann’s guess of operation around 2032 or 2033 is his inference, not reported. Allsup for 2029; Kann for the rest
- Maryland complained to FERC in 2024 that Virginia should pay more and was rejected; it filed a broader complaint in May 2026 seeking to assign data-center-driven transmission costs to the specific zone. Allsup
- Hyperscalers signed the ratepayer protection pledge at the White House in March 2026. Allsup
- Three of the four states had filings underway in spring 2026 at different stages, with West Virginia beginning public hearings that month. Allsup
- FERC had an advance notice of proposed rulemaking open on ensuring data centers cover 100% of the grid upgrade costs they require. Allsup
- The United States built nearly 4,000 miles of high-voltage transmission in 2013 and has averaged hundreds of miles a year recently. Kann’s view that the country needs thousands and maybe tens of thousands of miles is his assertion, not a cited study. Kann
07Where it’s contested
- Whether the line gets built. Allsup says she is less than optimistic about this project and attaches three caveats: it is early, she has not spoken to NextEra, and much may hinge on the parallel FERC proceeding. What she reports as sourced is that everyone she spoke to sees a real chance of delay, which is weaker than cancellation.
- Whether it is a data center line at all. Genuinely unresolved. Approved as a reliability project, the approval did cite data center load, and it predates the AI boom. No cutoff date exists after which a project is presumed to serve data centers.
- Whether new rules apply backwards, and whether they arrive. She twice says she does not know whether a FERC decision now would reach a line approved in 2022, and that NextEra does not appear to know either. Nor is anyone sure whether FERC and PJM will reopen cost allocation at all, which is both what would settle the case and what would most delay it.
- How the causes divide. Asked to separate data center backlash from the cost allocation question, Allsup declines and says it is all of the above, layered on ordinary siting opposition. Kann concedes in his own counterfactual that some of this fight might have happened without the AI boom.
- Expertise disclaimed. Allsup twice flags that she is not a transmission cost allocation expert and calls her own summary greatly oversimplified. The reporting is on the dispute, not the merits of the formula.