Skip to content

PJM · Virginia · Public-record retrospective

Chesterfield 230 kV: interconnection queue history

3,190 MW filed. 66 MW built.

GridVision AI ResearchUpdated

Nine interconnection requests since 2007: 3 reached commercial operation, 3 withdrew, and 3 remain active.

Built
3
Withdrawn
3
Still in queue
3

The queue record

Every interconnection request the dataset records at this point of interconnection, in filing order.

Interconnection requests recorded at this point of interconnection, with request date, capacity and outcome.
RequestedProjectTechnologyCapacityOutcome
2007-01-11Chesterfield Unit #5Coal19 MWBuilt2011-06-01 · 4.4 yrs
2007-07-31Chesterfield Unit #5Coal20 MWBuilt2011-06-01 · 3.8 yrs
2007-07-31Chesterfield Unit #6Coal27 MWBuilt2010-12-01 · 3.3 yrs
2011-07-28(unnamed)Gas1575 MWWithdrawn2012-12-05
2019-09-18Chesterfield CT Units 1 and 2Gas569 MWStill in queue
2019-09-18Chesterfield CT Units 3&4Gas569 MWStill in queue
2021-03-19(unnamed)Battery150 MWWithdrawn2024-12-17
2025-02-03(unnamed)Battery200 MWWithdrawn2025-11-25
2025-02-04(unnamed)Battery60.82 MWStill in queue

What the record shows

  • 1,925 MW of the 3,190 MW filed here withdrew, and 66 MW reached commercial operation.
  • Completions here took between 3.3 and 4.4 years from request to commercial operation (median 3.8).
  • The largest request filed here, 1,575 MW (gas), withdrew 1.4 years after filing.
  • Two requests were filed on 2019-09-18; all of them remain active.
  • One of the 3 withdrawals came within a year of filing.
  • By technology, the requests here were battery 3, coal 3, gas 3.
  • The longest-standing active request here was filed on 2019-09-18.
  • The dataset records this point of interconnection under two spellings, which are combined here.

What a decision record would have to make explicit

  • What separated the requests that reached operation from those that withdrew, such as study results, upgrade assignments or site conditions, is not in the public queue record, so a decision record here would have to carry it as an unknown.
  • Three requests are unresolved, so the outcome counts at this node can still change.
  • The dataset records outcomes and dates, not reasons, so no cause is attributed to any outcome here.

What this does and does not show

This is a reading of a public dataset, not a customer case study: no engagement, customer or client is involved. The dataset records outcomes — what was built, what withdrew, and when — but not why any project withdrew, so no cause is attributed here. Nothing on this page claims GridVision predicted, influenced or would have changed any outcome, and a pattern at one point of interconnection does not generalise to another.

Source: Lawrence Berkeley National Laboratory, Queued Up: 2026 Edition — project-level interconnection queue dataset. Interconnection requests through year-end 2025. Used under CC BY 4.0; attribution to Lawrence Berkeley National Laboratory and GridTracker.