CONTRA COSTA GENERATING STATION

3201 WILBUR AVENUE, ANTIOCH, CA, 94509
No open violations Compliance record — not a listed provider
Compliance record, not a business listing. This facility is a hazardous-waste generator (it produces regulated waste as part of an unrelated business), not a waste-management vendor — it isn't eligible to be claimed or listed. Data below is shown for compliance transparency, sourced from EPA ECHO & RCRAInfo.

Facility identity · canonical

EPA Registry ID
110019003790
RCRA Handler ID(s)
CAR000219410, CAT080011489
Generator status
Large Quantity Generator (LQG)
County
CONTRA COSTA
EPA Region
09
Active
Yes
NAICS
221112
Coordinates
38.018333, -121.761389
Compliance summary · canonical · EPA source pulled Aug 11, 2026 · summary recalculated Aug 26, 2026
3-year compliance history Not in the compliance universe for any of the last 12 quarters
Not in universe In violation Significant non-compliance
Significant non-complier
No
Last inspection
Sep 25, 2024
Inspections (5 yr)
1
Informal actions (5 yr)
—
Formal actions (5 yr)
—
Total penalties
—
Permits & authorizations · canonical
ProgramTypeStatusEffective
RCRA LQG Not reported Not reported
RCRA SQG Not reported Not reported
Type is EPA's RCRA handler classification. Permit status and effective date are not published in the RCRAInfo handler dataset.
Violations · canonical · 5 total, 0 open
3 distinct violation categories on record:
CountCodeCategoryEPA description
3 264.A TSDF standards (permitted) Standards for Owners and Operators of HW TSDs: General
1 264.H TSDF standards (permitted) Standards for Owners and Operators of HW TSDs: Financial Requirements
1 265.F TSDF standards (interim status) Interim Status Standards for Owners and Operators of HW TSDs: Ground-Water Monitoring
All violations:
DeterminedCategoryStatusAgency
Jun 24, 1992
TSDF standards (permitted)
264.H · Standards for Owners and Operators of HW TSDs: Financial Requirements
Resolved Oct 13, 1992 E
Feb 23, 1989
TSDF standards (permitted)
264.A · Standards for Owners and Operators of HW TSDs: General
Resolved Aug 5, 1991 S
Dec 8, 1987
TSDF standards (interim status)
265.F · Interim Status Standards for Owners and Operators of HW TSDs: Ground-Water Monitoring
Resolved Jan 18, 1988 S
Nov 24, 1987
TSDF standards (permitted)
264.A · Standards for Owners and Operators of HW TSDs: General
Resolved Jan 18, 1988 S
Nov 25, 1986
TSDF standards (permitted)
264.A · Standards for Owners and Operators of HW TSDs: General
Resolved Aug 5, 1991 S
Inspection history · canonical · 11 total
DateTypeAgencyOutcome
Sep 25, 2024 COMPLIANCE EVALUATION INSPECTION (CEI) S In compliance
Jan 7, 2010 COMPLIANCE EVALUATION INSPECTION (CEI) S In compliance
Jan 27, 2009 COMPLIANCE EVALUATION INSPECTION (CEI) S In compliance
Jun 24, 1992 FINANCIAL RECORD REVIEW (FRR) C Violation found
Sep 27, 1991 COMPLIANCE EVALUATION INSPECTION (CEI) S In compliance
Feb 23, 1989 COMPLIANCE EVALUATION INSPECTION (CEI) S Violation found
Feb 16, 1989 FINANCIAL RECORD REVIEW (FRR) S In compliance
Dec 8, 1987 GROUNDWATER MONITORING EVALUATION (GME) S Violation found
Showing 8 most recent of 11.

Data sources

EPA ECHO — this facility's detailed report — facility, compliance summary, permits, evaluations & violations
RCRAInfo evaluation and violation records for this facility are integrated into the ECHO report linked above — RCRAInfo's own public search doesn't offer a stable per-facility link. General source: EPA ECHO, EPA RCRAInfo.
Compliance, permit, and location data come straight from EPA and can't be edited. Contact info and description come from the business's claimed listing, if any. This profile is not an official regulatory determination.
EPA ECHO Exporter
Source snapshot pulled Aug 11, 2026 · batch 20260811T113837Z
EPA RCRAInfo (ECHO download)
Source snapshot pulled Aug 11, 2026 · batch 20260811T113837Z
Two different dates can appear on this page, and both are correct but mean different things: "Source snapshot pulled" above is when we last pulled that source's raw data — this is the date to check for source currency. "Recalculated" on the compliance summary is when we last recomputed that summary from the data on hand, which can land on a later date than the source pull itself — a later recalculation date does NOT mean the underlying source has data through that date.