Figures on this page are from Load Factor’s queue data as of March 2026. Live totals, withdrawn requests included, are on the coverage page.
PJM's interconnection queue is not just the largest in the US. It is the queue that most clearly shows the distance between development ambition and grid-process capacity.
Load Factor tracks 10,875 PJM projects - more than MISO and ERCOT combined, and more than PJM, CAISO, NYISO, and SPP combined. At that scale, PJM is not simply a large queue. It is the central case study for understanding interconnection backlog in US energy markets.
The challenge: 7,282 of those projects are already marked withdrawn. That 67.0% withdrawal rate, combined with the scale, is what makes PJM simultaneously the most important queue to watch and one of the hardest to interpret correctly.
PJM Interconnection Queue by the Numbers
| Metric | PJM |
|---|---|
| Total projects | 10,875 |
| Withdrawn | 7,282 (67.0%) |
| Active | 1,379 |
| In Service | 1,234 |
| Engineering and Procurement | 273 |
| Confirmed | 224 |
| Under Construction | 97 |
| Unknown / unresolved developers | 4,229 |
4,229 projects with no identified developer is the starkest developer-identification gap of any major US ISO. PJM is not just a backlog problem - it is a visibility problem.
PJM Queue by Fuel Type
| Fuel Type | Projects | Capacity (MW) |
|---|---|---|
| Solar | 4,505 | 165,653.4 |
| Battery Storage | 1,414 | 104,796.9 |
| Gas | 1,245 | 334,962.0 |
| Wind | 799 | 36,748.5 |
| Hybrid | 555 | 35,176.3 |
| Offshore Wind | 90 | 24,009.7 |
Solar leads PJM by project count (4,505). Gas remains the largest fuel category by MW (334,962.0 MW), reflecting the legacy gas project pipeline still in the study process. Battery storage has already grown to 1,414 projects - a number that would be the standalone storage queue of most other ISOs.
Offshore wind deserves attention beyond its count: 90 projects at 24,009.7 MW represents some of the largest individual project applications in any US queue.
PJM Queue by State
PJM's 13-state territory spans from Illinois to New Jersey, and from Virginia to Michigan. The project distribution is concentrated in a few states.
| State | Projects | Capacity (MW) |
|---|---|---|
| Pennsylvania | 2,144 | 186,201.2 |
| Virginia | 1,791 | 132,422.4 |
| New Jersey | 1,354 | 111,513.7 |
| Ohio | 1,080 | 90,041.5 |
| Illinois | 844 | 86,130.4 |
| Maryland | 643 | 60,269.3 |
| Indiana | 514 | 66,954.6 |
| West Virginia | 327 | 36,290.0 |
Pennsylvania, Virginia, and New Jersey together account for nearly half of all PJM projects by count. The withdrawal rates at the state level reinforce the backlog story: New Jersey 72.7%, Pennsylvania 72.4%, Maryland 73.3%, Virginia 64.0%.
The PJM Developer Identification Gap
PJM has 4,229 projects where the developer is unknown - not inferred, not estimated, but genuinely unidentified from available public sources. That is the largest absolute developer-unknown count of any ISO in Load Factor's database.
Why is PJM so much harder than MISO?
Less project-level transparency. PJM publishes less project-level detail than MISO, so each attribution starts from less.
Harder state and county records. Pennsylvania, New Jersey, and Virginia - the three largest PJM states - keep their public records in ways that are harder to work with than MISO's midwestern states. Load Factor's coverage there is still being built.
Filing entity complexity. PJM's project filing pool includes a higher proportion of out-of-state registered entities with complex corporate structures, requiring deeper federal research per project.
The commercial implication is direct: anyone doing developer research in PJM is doing it manually, because no platform has yet filled the gap at scale. Load Factor is actively building toward this - the PJM developer identification backlog represents one of the largest information arbitrage opportunities in US queue intelligence.
Why the 67% Withdrawal Rate Doesn't Make PJM Useless
The instinct when seeing a 67% withdrawal rate is to dismiss PJM queue data as noise. That is a mistake.
PJM's queue has functioned partly as an option register: developers secure positions, absorb study results, and exit if project economics or transmission costs no longer support development. High withdrawal rates are partly a signal of disciplined capital allocation, not just project failure.
The commercially relevant signal is not "are projects being withdrawn?" - they always have been. It is "where are developers still willing to spend option value, and where is attrition becoming the dominant signal?"
The answer right now: solar and storage applications continue to enter PJM's queue at substantial volumes even as legacy gas projects withdraw. The queue is being repriced from within. Understanding which queue positions are connected to developers who are genuinely advancing projects requires the developer identification layer that Load Factor is building toward.
Frequently Asked Questions
How many projects are in the PJM interconnection queue?
As of March 2026, Load Factor tracked 10,875 PJM projects - the largest ISO total in the US database.
Why does PJM have such a high withdrawal rate?
As of March 2026, 7,282 PJM projects (67.0%) were marked withdrawn. PJM's backlog accumulated across multiple study cycles, and many positions represent options that were exercised but not advanced. The queue is a development pipeline; withdrawal is a normal outcome at the scale PJM accumulated.
Why is PJM developer identification so difficult?
PJM's project filings are dominated by SPVs and LLCs, and the public records that name the companies behind them are harder to connect to PJM projects than to MISO projects. In Load Factor's March 2026 snapshot, 4,229 PJM projects remained unknown.
What fuel types dominate PJM's interconnection queue?
As of March 2026: solar (4,505 projects), battery storage (1,414), gas (1,245 but large MW), wind (799), hybrid (555), and offshore wind (90 projects at 24,009.7 MW).
How do I browse PJM projects on Load Factor?
Filter by PJM on the Browse page. No account required for the public layer.
Browse all PJM projects | PJM queue analysis - the backlog problem | How developer attribution works | US Queue by the Numbers
See also: MISO Interconnection Queue | ERCOT Interconnection Queue | Best Interconnection Queue Tools