Skip to content
← All retrospectives

PJM · Maryland

Everything large withdrew. Everything built was tiny and fast.

Dickerson 230 kV

Six requests: the two that reached operation total 21 MW and took under a year each, while four requests between 234 MW and 910 MW withdrew.

Built
2
Withdrawn
4
Still in queue
0

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
2001-01-31DickersonGas16 MWBuilt2001-03-17 · 0.1 yrs
2001-02-14(unnamed)Gas234 MWWithdrawn2003-10-23
2001-07-31(unnamed)Gas910 MWWithdrawn2002-05-25
2008-07-30(unnamed)Gas400 MWWithdrawn2008-12-01
2010-10-29Dickerson CT1 (D-CT1)Oil5 MWBuilt2011-08-23 · 0.8 yrs
2011-10-31(unnamed)Gas440 MWWithdrawn2012-06-21

What the record shows

  • The two projects that reached operation took 0.1 and 0.8 years — the fastest completions in this set by a wide margin.
  • Both are small: 16 MW of gas and 5 MW of oil, against withdrawn requests of 234, 400, 440 and 910 MW.
  • 21 MW of the 2,005 MW filed at this node reached operation, about one per cent.
  • The 910 MW request, the largest ever filed here, withdrew ten months after filing.
  • No request at this node remains active; the most recent was filed in 2011.

What a decision record would have to make explicit

  • Completions measured in weeks alongside withdrawals of several hundred megawatts suggest the two built requests are a different kind of thing from the rest, but the dataset does not record what a request represents.
  • Four of the six requests are unnamed, so nothing here can be attributed to a developer.
  • The dataset records no withdrawal reasons, so nothing explains why every large request at this node withdrew.

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.