CAISO node intelligence

EAGLE ROCK

county unknown (CA) · utility unknown · node key EAGLE ROCK · CAISO run date 2026-10-12

Seven questions a developer, lender or counsel asks before filing here. Every figure is a CAISO row; Not public marks what the public files cannot answer and where to get it. Definitions: methodology.

Can you get in?

No official Cluster 16 availability statement names this POI. Absence of a statement is not availability.

Not public: per-constraint transmission headroom at this POI — CAISO's cluster study reports (RIMS login).
Not on this site yet: the zonal transmission-capability table CAISO publishes for cluster scoring — public; the join is planned.

Who is ahead of you?

0 MW (n=0)
queued ahead of a new request (legacy + C15)
0 MW (n=0)
with an executed interconnection agreement · public report; C15 has no IA yet
0 MW (n=0)
operating at this node
0 MW
Cluster 15 requests seeking full capacity
Not public: who the interconnection customers are (the queue) — CAISO's public files carry project names only; the projects table below is the full public record. EIA-860 names the owners of what already operates nearby, not of what is queued.

Do projects leave after seeing the costs?

0 MW (n=0)
received Phase II / Facilities Study results here · any sheet, public report
0 MW (n=0)
of that, withdrew with results in hand
n/a (n=0)
Phase II attrition (MW share)
Not public: the network upgrade cost allocated to a project here — Phase I / Phase II study reports, served through RIMS. Ask the incumbent developer or request the report; nothing public reconstructs it.

Will you be deliverable?

0 MW (n=0)
2025 TPD requested at this node
0 MW
allocated
0 MW
refused at 0 % — contracted / shortlisted (groups A+B)
0 MW
refused at 0 % — no PPA (group D)
0 / 0
2024 cycle: projects given full / partial capacity

No request from this node appears in the 2025 allocation results.

A 0 % in group D is the expected result for an uncontracted project; a 0 % in group A or B is a contracted project that did not get deliverability. Rows are joined through all three sheets, so a request whose project has since withdrawn still appears. CAISO states no reason.

Will the power be worth anything here?

The Local Capacity Technical Report does not name this substation on any area boundary: not encoded, which is not the same as outside every area.

Not on this site yet: day-ahead price history at this POI — CAISO OASIS publishes it; it is shown only for a pricing node confirmed by hand in data/poi_pnodes.csv, and this one is not confirmed yet.

Will the land pass intake?

Intake scoring under the 2023 IPE rewards site control, permitting progress and system need before study begins. Parcel, zoning, Williamson Act and CEC exclusion screens run for Kings and Kern counties (caiso-siting parcels, layers screen); results are in outputs/parcels_*.md for the nodes they were run on and are not yet rendered per node here.

Not public: landowner willingness and option terms — county assessor parcels give ownership class, not intent; owner names are withheld on purpose.

How long, and who gave up?

100 MW (n=1)
withdrawn since 2022 (both reports)
100 MW
of that, storage
n/a (n=1)
storage churn · withdrawn storage ÷ queued + operating storage
0.00 (n=1)
Cluster 15 survival · active ÷ (active + withdrawn)
226 MW (n=2)
all-time withdrawn since 2006 · mostly wind/solar-era; colour, not signal
none active
current on-line dates of active projects

Cluster-level time-to-withdrawal curves are on the Survival page; they compare process regimes, not only nodes.

Projects at this node (2)

Both reports. cod = current on-line date (public report) or proposed on-line date (Cluster 15). ia_status exists only in the public report. Cluster 15 deliverability is requested, not allocated.

project_namequeue_positionsheet_statusclusternet_mwstorage_mwdeliverabilityia_statuscodwithdrawn_date
MAYACMAS WIND POWER556WITHDRAWNC021260ENERGY ONLY2013-10-312010-04-09
Ulua2340WITHDRAWNC15100100FULL CAPACITY (REQ)2029-06-302026-07-06

WDAT requests at this substation (1)

WDAT = distribution-level queue at the same substation, PG&E file today; not CAISO deliverability. WDAT requests connect below CAISO's transmission grid; they carry no CAISO deliverability unless separately studied.

queue_positionstatus_rawprocessgen_typenet_mwrequest_receivedcurrent_codia_statusft_over_cap
2909-WDActiveIndependent StudyWind1312021-08-25Tendered

Geocode provenance

Position is approximate or unknown (ambiguous): several OSM features share this name more than 50 km apart — the position may be the wrong one.

geo_method
ambiguous
geo_score
0.50
osm_name
Eagle Rock Switchyard
lat, lon
34.15083, -118.18431

All metrics

metricvaluedefinition
legacy_active_mw0active MW in the public report (C14 and earlier)
c15_active_mw0active MW in the Cluster 15 report
operating_mw0completed MW in the public report
pipeline_storage_mw0storage MW inside legacy_active_mw + c15_active_mw
operating_storage_mw0storage MW inside operating_mw (completed, public report)
wd_recent_mw100withdrawn in the last 5 years (both reports)
wd_recent_storage_mw100storage MW of those rows — each project's storage components capped at its net-to-grid figure; a handful of filings report net-to-grid as 0 and keep the component MW, so this can exceed the row above at 3 nodes.
wd_post_phase2_mw0withdrew AFTER Phase II / Facilities Study results (public report only)
p2_reached_mw0MW of projects that received Phase II / Facilities Study results here (public report, any sheet)
p2_withdrawn_mw0of those, MW that then withdrew (== wd_post_phase2_mw)
p2_attritionn/ap2_withdrawn_mw / p2_reached_mw — share of studied MW that left with results in hand
committed_mw0ACTIVE MW holding an executed interconnection agreement (public report)
churn_n1projects behind storage_churn (withdrawn recent + queued + operating)
c15_n1projects behind c15_survival
p2_n0projects behind p2_attrition
eia_plants0operable EIA-860 plants within 5 km of the node's mapped position (positioned nodes only)
eia_nameplate_mw0their nameplate MW, all technologies (EIA-860 Generator file, Operable sheet)
eia_storage_mwh0battery energy capacity among them (EIA-860 Energy Storage file), as reported
eia_storage_1h_mwstorage MW at units whose reported MWh is no more than their MW (one hour or less); shown with 'duration not established' because the value may reflect how the form was filled
eia_proposed_mw0nameplate MW in EIA-860's Proposed sheet within the same radius (planned / under construction)
wd_alltime_mw226every withdrawn MW since 2006 (includes dead wind/solar-era projects)
storage_churnn/awd_recent_storage_mw / (active + operating storage MW) — the one to quote
churn_alltimen/awd_alltime_mw / (pipeline + operating MW) — historical color only
c15_survival0.00c15_active / (c15_active + c15_withdrawn)
c15_fcds_req_mw0C15 active MW that requested Full Capacity Deliverability Status (requested, not allocated)
tpd25_projects0projects at the node that sought TPD in CAISO's 2025 allocation cycle
tpd25_req_mw0MW at the node that sought TPD in CAISO's 2025 allocation cycle
tpd25_alloc_mw0MW allocated in that cycle (requested × allocation %)
tpd25_denied_mw0MW requested by rows that received 0 %
tpd25_unalloc_mw0requested minus allocated: MW refused outright PLUS the remainder left by partial allocations — quote this for 'what the developer did not get'
tpd25_unknown_mw0MW requested by rows with no allocation percentage in the file; 0 today
tpd25_req_A_mw0of tpd25_req_mw, requested in allocation group A: executed PPA (or LSE own load)
tpd25_req_B_mw0of tpd25_req_mw, requested in allocation group B: shortlisted / negotiating a PPA
tpd25_req_C_mw0of tpd25_req_mw, requested in allocation group C: already in commercial operation
tpd25_req_D_mw0of tpd25_req_mw, requested in allocation group D: no PPA, Section 8.9.2.3 path
tpd25_denied_A_mw0of tpd25_denied_mw, refused at 0 % in group A
tpd25_denied_B_mw0of tpd25_denied_mw, refused at 0 % in group B
tpd25_denied_C_mw0of tpd25_denied_mw, refused at 0 % in group C
tpd25_denied_D_mw0of tpd25_denied_mw, refused at 0 % in group D
tpd25_denied_ppa_mw0refused MW in groups A + B: contracted or shortlisted projects that did not get deliverability; the refusal that matters
tpd24_fcdsa_projects0projects at the node allocated Full Capacity in the 2024 cycle
lcr_statusCAISO Local Capacity Area (Resource Adequacy geography): 'in <area>' or 'outside <area>' as the LCT report's boundary lists state it; blank = not encoded, never 'outside every area'
lcr_sub_areasub-area / load pocket within that area, when the LCT report delineates it
wdat_active_projects1active WDAT requests at the same substation (WDAT = distribution-level queue at the same substation, PG&E file today; not CAISO deliverability)
wdat_active_mw131MW of active WDAT (distribution-level) requests at the same substation (PG&E file today)
wdat_active_storage_mw0storage MW attributed from wdat_active_mw — an assumption: the PG&E file publishes one MW figure per request, so storage-only requests count in full and solar+storage requests count at half (160 of 1,011 active requests carry storage; 362 of their 479 MW is attributed as storage).
wdat_inservice_mw0WDAT MW already in service at that substation
wdat_withdrawn_mw0WDAT MW withdrawn at that substation (all-time in the file)
wdat_ft_over_cap_n0active Fast Track requests above the 5 MW Fast Track ceiling — held out of wdat_active_*
wdat_ft_over_cap_mw0MW of those held-out rows, as posted; cause not established

No figure on this site states a cause. CAISO files carry no withdrawal reason beyond "IC Request".

Screening tool, not engineering advice. Built from public filings by an engineer who is not a licensed PE. Verify every figure against the source filing named in its row before you rely on it for any decision. No warranty of any kind. Not affiliated with CAISO, EIA, or any utility. No engineering services are offered.