Skip to content
GridVision AI

CAISO · California · Public-record retrospective

Arco 230 kV: interconnection queue history

Nine of fourteen requests withdrew; five are still in the queue.

GridVision AI ResearchUpdated

Fourteen interconnection requests since 2010: 9 withdrew and 5 remain active.

Built
0
Withdrawn
9
Still in queue
5

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
2010-07-31ARCO SOLAR STATIONSolar300 MWWithdrawn2011-07-11
2011-03-31CENTRAL VALLEY II SEGSSolar540 MWWithdrawn2012-03-31
2015-04-30ANCHO CREEK SOLARSolar200 MWWithdrawn2015-07-09
2016-05-02ROLLING HILLS SOLARSolar206.27 MWWithdrawn2016-07-06
2018-04-16CHALAN SOLARSolar + battery66.6 MWStill in queue
2019-04-15KINGSROAD HYBRID SOLARSolar + battery101.78 MWStill in queue
2019-04-15ARCTURUSSolar + battery151.794 MWWithdrawn2025-03-03
2020-04-15PUFF HYBRID SOLARSolar + battery101.8 MWStill in queue
2020-04-15HAWKINS SOLAR HYBRIDSolar + battery250 MWStill in queue
2021-04-15CALLINAN SOLAR AND STORAGESolar + battery160.3879 MWWithdrawn2025-08-01
2021-04-15ARTEMISSolar + battery412.336 MWStill in queue
2023-04-17Callinan Solar 2Solar + battery155 MWWithdrawn2024-12-02
2023-04-17Tule Fog SolarSolar + battery316 MWWithdrawn2024-12-02
2023-04-17Pepper GrassSolar + battery320 MWWithdrawn2024-12-02

What the record shows

  • 2,349 MW of the 3,282 MW filed here withdrew.
  • The largest request filed here, 540 MW (solar), withdrew 1.0 years after filing.
  • Three requests were filed on 2023-04-17; all of them withdrew.
  • Three of the 9 withdrawals came within a year of filing.
  • By technology, the requests here were solar + battery 10, solar 4.
  • The longest-standing active request here was filed on 2018-04-16.
  • The dataset records this point of interconnection under five spellings, which are combined here.

What a decision record would have to make explicit

  • None of the resolved requests at this node reached operation, and the public record does not say why.
  • Five 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.

Related points of interconnection

How the CAISO process works today: CAISO interconnection queue. Comparing candidate nodes for a project? Read how to choose a point of interconnection.

Bring One Live DecisionOther retrospectives