Skip to content

CAISO · Nevada / California · Public-record retrospective

Trout Canyon Substation 230 kV: interconnection queue history

Five of fourteen requests withdrew; nine are still in the queue.

GridVision AI ResearchUpdated

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

Built
0
Withdrawn
5
Still in queue
9

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
2019-04-12BONANZA PEAK SOLAR FARMSolar + battery441 MWStill in queue
2019-04-15ROUGH HAT HYBRID SOLARSolar + battery204 MWStill in queue
2019-04-15YELLOW PINE 3Solar + battery261.954 MWStill in queue
2020-04-15ROUGH HAT 2Solar + battery203.8 MWStill in queue
2020-04-15CALVADA SPRINGS SOLARSolar + battery250 MWStill in queue
2020-04-15PURPLE SAGE ENERGY CENTERSolar + battery409.2 MWStill in queue
2021-04-15LARREA SOLARSolar + battery307 MWStill in queue
2021-04-15SUNBAKED SOLARSolar + battery508.56 MWStill in queue
2021-04-15MOSEYSolar + battery543.856 MWStill in queue
2023-04-17Rock CanyonSolar + battery250 MWWithdrawn2024-12-02
2023-04-17DumontSolar + battery427 MWWithdrawn2024-12-02
2023-04-17CrossoverSolar + battery527 MWWithdrawn2024-12-02
2023-04-17Campito PeakBattery565.769988 MWWithdrawn2025-04-28
2023-04-17Borderline SolarSolar + battery638.1349 MWWithdrawn2025-05-01

What the record shows

  • 2,408 MW of the 5,537 MW filed here withdrew.
  • The largest request filed here, 638 MW (solar + battery), withdrew 2.0 years after filing.
  • Five requests were filed on 2023-04-17; all of them withdrew.
  • None of the 5 withdrawals came within a year of filing; the quickest took 1.6 years.
  • By technology, the requests here were solar + battery 13, battery 1.
  • The longest-standing active request here was filed on 2019-04-12.
  • The dataset records this point of interconnection under three 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.
  • Nine 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.