ERCOT · Texas · Public-record retrospective
Clear Crossing 345 kV: interconnection queue history
Two of four requests reached commercial operation.
GridVision AI ResearchUpdated
Four interconnection requests since 2018: 2 reached commercial operation and 2 withdrew.
- Built
- 2
- Withdrawn
- 2
- Still in queue
- 0
The queue record
Every interconnection request the dataset records at this point of interconnection, in filing order.
| Requested | Project | Technology | Capacity | Outcome |
|---|---|---|---|---|
| 2018-06-28 | Azure Sky Wind 1 | Wind | 350 MW | Withdrawn2019-10-04 |
| 2019-05-01 | Quantum Increase | Solar | 61.2 MW | Withdrawn2019-06-26 |
| 2019-12-11 | Azure Sky BESS | Other | 77.6 MW | Built2022-05-12 · 2.4 yrs |
| 2019-12-11 | Azure Sky Solar | Solar | 228.4 MW | Built2021-11-15 · 1.9 yrs |
What the record shows
- 411 MW of the 717 MW filed here withdrew, and 306 MW reached commercial operation.
- Completions here took between 1.9 and 2.4 years from request to commercial operation (median 2.2).
- The largest request filed here, 350 MW (wind), withdrew 1.3 years after filing.
- Two requests were filed on 2019-12-11; all of them reached operation.
- One of the 2 withdrawals came within a year of filing.
- By technology, the requests here were solar 2, other 1, wind 1.
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
- ERCOT · TexasHillje 345 kV10 requests · 2 built · 4 withdrawn · 4 still in queueRead the record
- ERCOT · TexasSchneeman Draw 345 kV8 requests · 4 built · 4 withdrawn · 0 still in queueRead the record
- ERCOT · TexasTesla 345 kV8 requests · 1 built · 3 withdrawn · 4 still in queueRead the record
- ERCOT · TexasBakersfield 345 kV7 requests · 4 built · 3 withdrawn · 0 still in queueRead the record
How the ERCOT process works today: ERCOT interconnection queue. Comparing candidate nodes for a project? Read how to choose a point of interconnection.