MOSS LANDING

MONTEREY (CA) · PGAE · node key MOSS LANDING · 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?

2,449 MW (n=3)

queued ahead of a new request (legacy + C15)

2,250 MW (n=2)

with an executed interconnection agreement · public report; C15 has no IA yet

932 MW (n=3)

operating at this node

199 MW

Cluster 15 requests seeking full capacity

Already operating within 5 km (EIA-860): 2 plants; 2,030 MW nameplate; 632 MW / 2,530 MWh storage; oldest unit 2002. Technology: Natural Gas Fired Combined Cycle 1,398; Batteries 632. Operators: Dynegy -Moss Landing LLC; Pacific Gas & Electric Co.. Joined by distance to this node's mapped position, not by point of interconnection: a plant on a long gen-tie lands on the nearest substation. Corporate names from a federal filing.

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?

3,182 MW (n=5)

received Phase II / Facilities Study results here · any sheet, public report

0 MW (n=0)

of that, withdrew with results in hand

0.00 (n=5)

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?

1,500 MW (n=1)

2025 TPD requested at this node

1,500 MW

allocated

0 MW

refused at 0 % — contracted / shortlisted (groups A+B)

0 MW

refused at 0 % — no PPA (group D)

0 / 1

2024 cycle: projects given full / partial capacity

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?

Local Capacity Area: Greater Bay Area · sub-area South Bay-Moss Landing — The 2027 report lists Moss Landing as in at every tie (Los Banos / Coburn / Las Aguilas are out, Moss Landing is in); earlier LCT reports drew the 500 kV boundary differently Final 2027 LCT Report [2026-04-29]

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?

0 MW (n=0)

withdrawn since 2022 (both reports)

0 MW

of that, storage

0.00 (n=6)

storage churn · withdrawn storage ÷ queued + operating storage

1.00 (n=1)

Cluster 15 survival · active ÷ (active + withdrawn)

1,000 MW (n=2)

all-time withdrawn since 2006 · mostly wind/solar-era; colour, not signal

2030-08-01 to 2034-02-17

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 (8)

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_name	queue_position	sheet_status	cluster	net_mw	storage_mw	deliverability	ia_status	cod	withdrawn_date
HOLMAN	1889	ACTIVE	C14	1,500	757	FULL CAPACITY	EXECUTED	2034-02-17
IRVING STORAGE	1539	ACTIVE	ISP	750	750	FULL CAPACITY	EXECUTED	2030-08-01
Antlia	2204	ACTIVE	C15	199	199	FULL CAPACITY (REQ)		2031-12-01
DALLAS ENERGY STORAGE	1472	COMPLETED	C11	400	400	FULL CAPACITY	EXECUTED
PLANO STORAGE	1540	COMPLETED	ISP	350	350	FULL CAPACITY	EXECUTED
ELKHORN ENERGY STORAGE	1374	COMPLETED	C10	182	182	FULL CAPACITY	FILED UNEXECUTED
ROCKFISH STORAGE 1	1486	WITHDRAWN	C11	500	500	FULL CAPACITY		2023-12-01	2019-03-08
ROCKFISH STORAGE 2	1487	WITHDRAWN	C11	500	500	FULL CAPACITY		2024-12-01	2019-03-08

TPD allocation requests at this node (2)

CAISO Transmission Plan Deliverability allocation results, joined on queue position through all three sheets of the public report (a request whose project has since withdrawn still appears). 2024 rows carry no MW. Groups: A = executed power purchase agreement requiring FCDS, or an LSE serving its own load; B = shortlisted for, or actively negotiating, a power purchase agreement; C = already in commercial operation for the capacity seeking TP deliverability; D = no PPA; electing the Section 8.9.2.3 (financial-security) path.

tpd_year	queue_id	project_name	allocation_group	mw_requested	allocation_pct	mw_allocated	status
2025	1889	HOLMAN	B	1,500	100%	1,500	FCDSA
2024	1889	HOLMAN	B		50%		PCDSA

Geocode provenance

geo_method: override
geo_score: 1.00
osm_name: OSM: convergence of Moss Landing 115 kV line ends (ways 974695020, 974462217, 97
lat, lon: 36.80832, -121.77800

All metrics

metric	value	definition
`legacy_active_mw`	2,250	active MW in the public report (C14 and earlier)
`c15_active_mw`	199	active MW in the Cluster 15 report
`operating_mw`	932	completed MW in the public report
`pipeline_storage_mw`	1,706	storage MW inside legacy_active_mw + c15_active_mw
`operating_storage_mw`	932	storage MW inside operating_mw (completed, public report)
`wd_recent_mw`	0	withdrawn in the last 5 years (both reports)
`wd_recent_storage_mw`	0	storage 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_mw`	0	withdrew AFTER Phase II / Facilities Study results (public report only)
`p2_reached_mw`	3,182	MW of projects that received Phase II / Facilities Study results here (public report, any sheet)
`p2_withdrawn_mw`	0	of those, MW that then withdrew (== wd_post_phase2_mw)
`p2_attrition`	0.00	p2_withdrawn_mw / p2_reached_mw — share of studied MW that left with results in hand
`committed_mw`	2,250	ACTIVE MW holding an executed interconnection agreement (public report)
`churn_n`	6	projects behind storage_churn (withdrawn recent + queued + operating)
`c15_n`	1	projects behind c15_survival
`p2_n`	5	projects behind p2_attrition
`eia_plants`	2	operable EIA-860 plants within 5 km of the node's mapped position (positioned nodes only)
`eia_nameplate_mw`	2,030	their nameplate MW, all technologies (EIA-860 Generator file, Operable sheet)
`eia_storage_mwh`	2,530	battery energy capacity among them (EIA-860 Energy Storage file), as reported
`eia_storage_1h_mw`	0	storage 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_mw`	0	nameplate MW in EIA-860's Proposed sheet within the same radius (planned / under construction)
`wd_alltime_mw`	1,000	every withdrawn MW since 2006 (includes dead wind/solar-era projects)
`storage_churn`	0.00	wd_recent_storage_mw / (active + operating storage MW) — the one to quote
`churn_alltime`	0.30	wd_alltime_mw / (pipeline + operating MW) — historical color only
`c15_survival`	1.00	c15_active / (c15_active + c15_withdrawn)
`c15_fcds_req_mw`	199	C15 active MW that requested Full Capacity Deliverability Status (requested, not allocated)
`tpd25_projects`	1	projects at the node that sought TPD in CAISO's 2025 allocation cycle
`tpd25_req_mw`	1,500	MW at the node that sought TPD in CAISO's 2025 allocation cycle
`tpd25_alloc_mw`	1,500	MW allocated in that cycle (requested × allocation %)
`tpd25_denied_mw`	0	MW requested by rows that received 0 %
`tpd25_unalloc_mw`	0	requested minus allocated: MW refused outright PLUS the remainder left by partial allocations — quote this for 'what the developer did not get'
`tpd25_unknown_mw`	0	MW requested by rows with no allocation percentage in the file; 0 today
`tpd25_req_A_mw`	0	of tpd25_req_mw, requested in allocation group A: executed PPA (or LSE own load)
`tpd25_req_B_mw`	1,500	of tpd25_req_mw, requested in allocation group B: shortlisted / negotiating a PPA
`tpd25_req_C_mw`	0	of tpd25_req_mw, requested in allocation group C: already in commercial operation
`tpd25_req_D_mw`	0	of tpd25_req_mw, requested in allocation group D: no PPA, Section 8.9.2.3 path
`tpd25_denied_A_mw`	0	of tpd25_denied_mw, refused at 0 % in group A
`tpd25_denied_B_mw`	0	of tpd25_denied_mw, refused at 0 % in group B
`tpd25_denied_C_mw`	0	of tpd25_denied_mw, refused at 0 % in group C
`tpd25_denied_D_mw`	0	of tpd25_denied_mw, refused at 0 % in group D
`tpd25_denied_ppa_mw`	0	refused MW in groups A + B: contracted or shortlisted projects that did not get deliverability; the refusal that matters
`tpd24_fcdsa_projects`	0	projects at the node allocated Full Capacity in the 2024 cycle
`lcr_status`	in Greater Bay Area	CAISO 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_area`	South Bay-Moss Landing	sub-area / load pocket within that area, when the LCT report delineates it
`wdat_active_projects`	0	active WDAT requests at the same substation (WDAT = distribution-level queue at the same substation, PG&E file today; not CAISO deliverability)
`wdat_active_mw`	0	MW of active WDAT (distribution-level) requests at the same substation (PG&E file today)
`wdat_active_storage_mw`	0	storage 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_mw`	0	WDAT MW already in service at that substation
`wdat_withdrawn_mw`	0	WDAT MW withdrawn at that substation (all-time in the file)
`wdat_ft_over_cap_n`	0	active Fast Track requests above the 5 MW Fast Track ceiling — held out of wdat_active_*
`wdat_ft_over_cap_mw`	0	MW 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.