Skip to content
GridVision AI

CAISO · California · Public-record retrospective

Highwind Substation 230 kV: interconnection queue history

3,428 MW filed. 162 MW built.

GridVision AI ResearchUpdated

Fourteen interconnection requests since 2006: 1 reached commercial operation and 13 withdrew.

Built
1
Withdrawn
13
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
2006-09-27NORTH SKY RIVER WINDWind162 MWBuilt2012-12-07 · 6.2 yrs
2008-05-30RED MOUNTAIN RIDGEWind150 MWWithdrawn2012-04-25
2009-07-31CITY OF VERNON RENEWABLE PROJECT 1Wind688 MWWithdrawn2009-11-03
2011-03-31SOLDIER FLATWind400 MWWithdrawn2012-02-23
2011-03-31ALTA 15Wind502 MWWithdrawn2012-03-07
2012-04-02TEHACHAPI VALLEY SOLAR ISolar45 MWWithdrawn2015-06-15
2012-04-02HIGHWIND POWER PROJECTGas291 MWWithdrawn2014-10-13
2016-05-02GRAPEVINE 1Battery406 MWWithdrawn2017-04-25
2017-05-01JAWBONE WIND ENERGY PROJECTWind37.4 MWWithdrawn2019-07-08
2018-04-16HIGHLINE SOLAR ENERGY CENTERSolar + battery80 MWWithdrawn2019-02-26
2019-04-15HIGHWIND ENERGY CENTERSolar + wind + battery51.75 MWWithdrawn2020-02-27
2019-04-15FOKUS RENEWABLE ENERGY CENTERSolar + wind + battery152.4 MWWithdrawn2019-07-19
2020-04-15VALOREMSolar + wind + battery208.08 MWWithdrawn2021-05-10
2021-04-15WINOKA HYBRID SOLARSolar + battery253.88 MWWithdrawn2021-08-10

What the record shows

  • 3,266 MW of the 3,428 MW filed here withdrew, and 162 MW reached commercial operation.
  • The one request that reached operation took 6.2 years from request to commercial operation.
  • The largest request filed here, 688 MW (wind), withdrew 0.3 years after filing.
  • Two requests were filed on 2019-04-15; all of them withdrew.
  • Eight of the 13 withdrawals came within a year of filing.
  • By technology, the requests here were wind 6, solar + wind + battery 3, solar + battery 2, battery 1, gas 1, solar 1.
  • The dataset records this point of interconnection under five 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.
  • 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