Skip to content
LOAD FACTOR
Back to Insights
PJM

PJM's Interconnection Queue Problem

Published April 29, 2026 • 6 min read • Load Factor team
Share this

PJM is not just the largest interconnection queue in the US. It is the queue that most clearly shows the gap between development ambition and grid-process capacity. Load Factor's canonical product snapshot tracks 10,875 PJM projects, the largest count of any ISO by a wide margin. In the current status rollup, 7,282 PJM projects are already marked withdrawn, a 67.0% withdrawal rate.

That combination of scale and attrition is why PJM remains the center of gravity for queue-backlog analysis. The issue is not simply that the queue is long. It is that the queue is large, historically layered, commercially important, and still difficult to interpret from public data alone.

PJM is larger than every other queue that dominates public discussion

At 10,875 projects, PJM sits far above every other named ISO in Load Factor's public breakdown.

ISOProjects
PJM10,875
MISO5,545
ERCOT3,089
SPP2,830
CAISO2,448
NYISO1,419

PJM alone is larger than MISO and ERCOT combined in the canonical Load Factor market summary. That matters because PJM is also one of the most scrutinized interconnection regions in US power markets. When reform proposals are debated, developers are often reacting to a queue that already carries far more volume than most summary charts make intuitive.

The problem is not theoretical. A queue of this size changes how market participants interpret every adjacent signal: transmission planning, project valuation, land strategy, developer concentration, and offtake timing.

Solar leads on project count, but PJM's backlog is fuel-diverse

The current PJM fuel mix shows why backlog analysis cannot be reduced to one technology narrative.

Fuel typeProjectsCapacity (MW)
Solar4,505165,653.4
Battery Storage1,414104,796.9
Gas1,245334,962.0
Wind79936,748.5
Hybrid55535,176.3
Offshore Wind9024,009.7

Solar is the dominant PJM queue story by project count. Battery storage is already large enough to be a second-order story on its own. Gas remains outsized in MW terms. Hybrid projects are numerous enough that they should be analyzed separately rather than folded into solar. Offshore wind is small by count but material in project scale.

This matters because a queue backlog is not just a congestion problem. It is a portfolio-composition problem. Different fuel types place different demands on transmission studies, capacity expectations, siting strategy, and development timelines.

The backlog is concentrated in a few states

PJM's queue is broad geographically, but the largest project concentrations sit in a handful of states.

StateProjectsCapacity (MW)
Pennsylvania2,144186,201.2
Virginia1,791132,422.4
New Jersey1,354111,513.7
Ohio1,08090,041.5
Illinois84486,130.4
Maryland64360,269.3
Indiana51466,954.6
West Virginia32736,290.0

Pennsylvania, Virginia, New Jersey, and Ohio form the core of the PJM queue by project count. That concentration matters for everyone from developers and lenders to consultants and equipment vendors. PJM is not one market in any practical sense. It is a cluster of state-level development theaters operating inside one interconnection process.

The geographic concentration also helps explain why PJM queue discussion so often feels simultaneously national and local. The headline count is systemwide. The competitive reality is county- and state-specific.

The withdrawal rate is the backlog's clearest stress signal

A queue can be large and still commercially useful if projects move through it. PJM's stress signal is that such a large share of applications exit before completion.

In the current project-status snapshot:

  • 7,282 PJM projects are marked Withdrawn
  • 1,379 are marked Active
  • 1,234 are marked In Service
  • 273 are in Engineering and Procurement
  • 224 are Confirmed
  • 97 are Under Construction

That 67.0% withdrawn share does not mean two-thirds of all future PJM development is impossible. It means the queue has been functioning partly as an option register: a place where developers secure positions, test economics, absorb study results, and then exit if the path no longer clears.

At the state level, the pressure is also visible. New Jersey's current withdrawn share is 72.7%. Pennsylvania is 72.4%. Maryland is 73.3%. Virginia is lower at 64.0%, but still elevated. Those are not edge-case readings. They are the core of the queue.

Developer identification is still a major PJM data gap

The backlog story is only half of PJM's problem. The other half is visibility.

Load Factor's canonical product snapshot shows:

  • 10,875 PJM projects
  • 4,229 of them with no identified developer

That gap is commercially significant. It means a user can often see the queue position, project size, and location, but still lack a clean evidence-backed answer to the question that matters most: who controls this project?

This is where PJM differs sharply from MISO. MISO is far from perfect, but it has deeper evidence coverage for developer-level research. PJM remains more opaque. The result is a queue where the project count is huge, the commercial stakes are high, and the identity layer is still incomplete.

That is not just a product challenge. It reflects the structure of the public record. PJM queue analysis often requires stitching together service agreements, FERC documents, EIA references, project-level news, and state records that do not always align neatly.

Why PJM's queue still matters despite the noise

The temptation with PJM is to treat the queue as too crowded and too stale to be useful. That would be a mistake.

PJM remains useful because it is where development pressure is most visible. Solar counts are large. Storage is meaningful. State concentration is obvious. Withdrawals show how much attrition the market is already absorbing. And the unresolved identity layer creates an information premium for anyone who can go beyond the spreadsheet.

For investors, that means queue diligence still matters even when the project attrition rate is high. For developers, it means competitor mapping is still worthwhile because a withdrawn-heavy queue can still reveal where capital keeps reappearing. For advisors and service providers, it means the best opportunities sit where project density and identity clarity can be connected.

Methodology

This post uses Load Factor's canonical PJM headline count of 10,875 projects from product documentation. Canonical attribution-coverage figures also come from Load Factor's documented market snapshot: 4,229 unknowns in PJM. Fuel mix, state concentration, queue-year, and application-status distributions come from the current PostgreSQL project snapshot for iso='PJM'. Capacity totals use summer_mw with winter_mw fallback where needed. Withdrawal rate is calculated from current application_status='Withdrawn' records in the PJM slice.

Conclusion

PJM's interconnection queue problem is not one issue. It is three issues stacked together: too many projects, too much attrition, and too little developer clarity in the public record. That is why PJM remains the most important queue to watch and one of the hardest to interpret correctly.

If you want to inspect the underlying records, browse all 10,875 PJM projects on Load Factor. For the national context, read US Interconnection Queue by the Numbers. For the storage angle that increasingly overlaps PJM's backlog, read Battery Storage Is Flooding US Interconnection Queues.

Share this

Load Factor tracks 38,000+ interconnection queue projects, withdrawn included, across 16 North American markets, with the evidence behind every developer it names.

Next step

See your market in 30 minutes.

A walkthrough of the projects, developers and evidence in the markets you work in.

Get the weekly brief

Queue movement, newly identified developers and the week’s deals, every Monday. Read past issues

Book a 30-min walkthrough