BPA interconnection requestin Gilliam, OR. A project record with the source’s own status, dates and estimates. A proposal or connection request does not establish operation.
2026-09-28
Linked: a cited public source identifies the facility, and the state, county and resource both accounts give agree.New plant: the linked generators came into service through this request.
EIA lists Leaning Juniper II (the IIA and IIB sections) as one unit, 199.2 MW, 2011-03. G0917 repowers part of it
Identified by BPA record of decision, April 2009: Iberdrola requested 200 MW under GI request G0226 (submitted 2006-05-24) for its Leaning Juniper II Wind Project in Gilliam County, at BPA's Jones Canyon Substation ↗· read 2026-09-28
| EIA unit | State · county | Resource | Nameplate · MW | Status | Operating | Months from request |
|---|---|---|---|---|---|---|
| Leaning Juniper Wind Power II unit 1 · eia860m-inventory | OR · Gilliamstate agrees, county agrees | windagrees | 199.2MWEIA nameplate MW of this unit (latest_generator) | OP | March 2011 | 58 months |
A link needs a cited public source that identifies the facility, and the state, county and resource both accounts give agree; a name is never enough. Each account keeps its own MW and status; nothing is summed across sources. Elapsed time runs from the request month to EIA's operating month, only for a new plant or a phase, because an uprate, a repower or an agreement for a running plant did not create the unit. Reviewed by claude-w11 on 2026-09-28. queue-generator-links
A queue request is a request for interconnection service, not a plant: many requests can describe one facility, requests are withdrawn or restudied, and an energized request does not name the operating plant. Request numbers and study milestones are BPA's; nameplate and interconnection MW are the requestor's figures. No location beyond county and the named point of interconnection.
Map location unavailable. This plant remains part of the source inventory and tables.
The figure the issuing record states for the project (BPA queue Nameplate MW Total; EFSEC facility page); a proposal, not operating capacity
2026-09-28 · reported · direct · valid · final
Interconnection Request Queue (generator interconnection and line/load requests), published workbook; request_number=G0226; field=Nameplate MW Total
Publisher & attribution ↗ Cite this released fact ↗BPA queue Max Summer Interconnection Service MW: the service the requestor asked for, which can differ from nameplate
2026-09-28 · reported · direct · valid · final
Interconnection Request Queue (generator interconnection and line/load requests), published workbook; request_number=G0226; field=Max Summer Interconnection Service MW
Publisher & attribution ↗ Cite this released fact ↗Operational: the provider reports the request in service or energized. An interconnection agreement is not operation, and a request still active at a source’s cutoff is unresolved, not failed.
| Account | Outcome | Requested | Agreement | Operation | Withdrawn | Request to agreement | Request to operation | As of |
|---|---|---|---|---|---|---|---|---|
| Providerbpa-queue· BPA's workbook dates the request and the expected in-service only; agreement, energization and withdrawal are statuses without dates | OperationalENERGIZED | 2006-05-24 | — | — | — | not dated | not dated | 2026-09-28 |
| BPA request G0226 in LBNL's compilationlbnl-queue | OperationalIA Executed | 2006-05-24 | 2010-05-14 | — | — | 1,451 days | not dated | 2025-12-24 |
| When | Event | Unit | Date is | Source |
|---|---|---|---|---|
| 2006-05-24day precision | Request received | — | Dated event | bpa-queue |
| 2010-05-14day precision | Interconnection agreementLBNL's account of the same request number | — | Dated event | lbnl-queue |
| March 2011month precision | Began operating | 1199.2 MW | Dated event | eia860m-inventory |
| 2011-04-01day precision | Agreed in-service dateBPA's agreed in-service date, an expectation, not a commitment or an event | — | Expectation | bpa-queue |
The outcome is BPA's status mapped to the common vocabulary, with the status kept beside it. A candidate is LBNL's row carrying this request number: its dates and status are LBNL's account of the same request as of its own cutoff, shown beside BPA's and never merged into it. How requests from 2015–2020 turned out.
A queue request is a request for interconnection service, not a plant: many requests can describe one facility, requests are withdrawn or restudied, and an energized request does not name the operating plant. Request numbers and study milestones are BPA's; nameplate and interconnection MW are the requestor's figures. No location beyond county and the named point of interconnection.
Facility identities as stated by the BPA, agency, commission, utility or developer page cited on each row
A reviewed judgement, not a source's statement: a link needs a cited identity source and agreeing attributes, a name is never enough, and unresolved rows say why. The queue's and EIA's MW and status stay each source's own.
U.S. EIA, preliminary monthly generator inventory, August 2026 (released September 24, 2026)
Preliminary monthly estimates; subsequent editions can revise values. Current assertions use the complete pinned workbook; cancelled and indefinitely postponed units share a sheet and are not distinguished.
Bonneville Power Administration, Interconnection Request Queue
A queue request is a request for interconnection service, not a plant: many requests can describe one facility, requests are withdrawn or restudied, and an energized request does not name the operating plant. Request numbers and study milestones are BPA's; nameplate and interconnection MW are the requestor's figures. No location beyond county and the named point of interconnection.
Lawrence Berkeley National Laboratory and GridTracker, Queued Up: 2026 Edition, interconnection queue data file (Rand et al., 2026), CC BY 4.0
A compilation of transmission providers' interconnection queues in one schema, as each provider published them and as LBNL and GridTracker cleaned them: a request for interconnection service, not a plant, with the provider's own status text kept beside LBNL's status, and with agreement, operation and withdrawal dates only where the provider publishes them. Requests sited in WA, OR, ID and MT are loaded; the compilation lags the providers' own queues by months, so an active request here can have changed since. MW are the requester's figures and never enter capacity totals. Rows carrying BPA's request numbers are candidates for the same request in BPA's own workbook and are never merged with it.
Release 20260929T050546Z-51ae0f7d3c78 · Record JSON