ProjectOR

Arlington Wind_Wheatfield Wind

About this record

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

BPA interconnection request

Bonneville Power Administration
Request
G95 · Generator interconnection· ERIS
Requestor
EDP Renewables North America LLC
StatusBPA’s own status word for the request (received, study, energized, withdrawn …); grouped into a stage for filtering.Definition ↗
ENERGIZED · energized· on-line November 2008 for 103 MW and February 2009 for 93 MW (LGIA split)
Requested
2002-02-15· in service requested 2008-10-01
Point of interconnection
Jones Canyon Substation
Location
Gilliam, OR · county only, no coordinates
Components
Wind Turbine · Wind Turbine · 200 MW
Studies
None recorded
EIA plant
Wheat Field Wind Power Project (new plant; units GEN1)Arlington Wind Power Project (new plant; units GEN1)

Against EIA’s generator inventory

Linked· new plant

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.

BPA's comment: on-line November 2008 for 103 MW and February 2009 for 93 MW (LGIA split). EIA's two plants match those months: Arlington Wind Power Project (102.9 MW, 2008-12) and Wheat Field (102.9 MW, 2009-02); EDP's fact sheet: Wheat Field near Arlington, 97 MW, online since 2009

Identified by BPA record of decision, January 2005: in February 2002 Columbia Energy Partners requested interconnection of up to 200 MW from its Arlington Wind Project to the McNary-Santiam No. 2 line, at the Jones Canyon switching station about 3 miles southwest of Arlington, Gilliam County ↗· read 2026-09-28· corroborating page ↗

The request as BPA states it: OR, Gilliam · Wind Turbine · 200MW(bpa Nameplate MW Total). Each unit below is EIA’s account; the two are compared, never merged.
EIA unitState · countyResourceNameplate · MWStatusOperatingMonths from request
Wheat Field Wind Power Project unit GEN1 · eia860m-inventoryOR · Gilliamstate agrees, county agreeswindagrees102.9MWEIA nameplate MW of this unit (latest_generator)OPFebruary 200984 months
Arlington Wind Power Project unit GEN1 · eia860m-inventoryOR · Gilliamstate agrees, county agreeswindagrees102.9MWEIA nameplate MW of this unit (latest_generator)OPDecember 200882 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.

Project nameplate capacity as statedThe publisher’s stated project rating. The project’s status determines whether it is operating; a connection request alone does not establish that.Definition ↗
200MW
Source & method

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=G95; field=Nameplate MW Total

Publisher & attribution ↗ Cite this released fact ↗
Maximum summer interconnection service requestedThe maximum summer connection service requested, which can differ from the project’s nameplate MW. Neither a request nor its size establishes an operating plant.Definition ↗
200MW
Source & method

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=G95; field=Max Summer Interconnection Service MW

Publisher & attribution ↗ Cite this released fact ↗

This request’s life

OperationalWhere an interconnection request stands as of its source's cutoff, in one vocabulary mapped from each provider's own status text, which stays beside it: active, operational, withdrawn, suspended, decommissioned or unknown. An executed interconnection agreement is not operation, and a request still active or suspended at the cutoff is unresolved, not failed. Elapsed days run from the request date to a published milestone date and exist only where both dates do.Definition ↗

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.

AccountOutcomeRequestedAgreementOperationWithdrawnRequest to agreementRequest to operationAs of
Providerbpa-queue· BPA's workbook dates the request and the expected in-service only; agreement, energization and withdrawal are statuses without datesOperationalENERGIZED2002-02-15———not datednot dated2026-09-28
BPA request G95 in LBNL's compilationlbnl-queueOperationalIA Executed2002-02-152008-08-29——2,387 daysnot dated2025-12-24

Dated events

Each source’s own dates, in order: a day where the source gives a day, a month where it gives a month. An expectation is not an event, and an assertion month is when EIA first listed the unit, not when anything happened there.
WhenEventUnitDate isSource
2002-02-15day precisionRequest received—Dated eventbpa-queue
2008-08-29day precisionInterconnection agreementLBNL's account of the same request number—Dated eventlbnl-queue
December 2008month precisionBegan operatingGEN1102.9 MWDated eventeia860m-inventory
February 2009month precisionBegan operatingGEN1102.9 MWDated eventeia860m-inventory

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.

Geographic & reporting context

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.

Sources for this record

Frozen citation page ↗

Request to generator dispositions (pipeline/config/crosswalks/queue_generator_links.csv)

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.

Preliminary Monthly Electric Generator Inventory, August 2026

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.

Interconnection Request Queue (generator interconnection and line/load requests), published workbook

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.

Queued Up: 2026 Edition, interconnection queue data file (data through 2025; workbook dated May 2026)

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