Pinole Rodeo Auto Wreckers

Active WDID 2 07I012545 Rodeo, Contra Costa County Region 2 · San Francisco Bay

At a glance

Permit Evidence: SMARTS record
Active Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Rodeo, Contra Costa County
Region 2 · San Francisco Bay · Location · Statewide map
Receiving water
Rodeo Creek (as reported by the facility)
Evidence: candidate, awaiting review Details
Identified receiving water on the 2026 303(d) list
Not established
Shown only when the reported receiving water is identified and corroborated.
2026 Integrated Report waters within 1.0 km Evidence: geographic proximity
2 waterbodies; 2 on the 2026 303(d) list
Proximity only; not a discharge pathway · Nearby waterbodies
Monitoring results Evidence: facility-reported
None in the current exports
Compliance and enforcement records Evidence: SMARTS record
5 inspections · 9 violation records · 12 enforcement actions
Counts as published in SMARTS; not a compliance determination · Details
SMARTS TMDL records Evidence: SMARTS-reported
0 records
TMDL records

Each label shows where a statement comes from. How to read the labels.

Overview and location

Reported facility location HUC12 watershed Corroborated receiving water 2026 Integrated Report waterbodies nearby

Open this facility on the statewide map

Reported location Evidence: facility-reported

Coordinates
38.02795, -122.26592
Precision
5 decimal places
Shared point
No
Matches application record
same

Facility location as reported by the discharger in SMARTS; not a discharge point or outfall.

Facility address
700 Parker Ave, Rodeo 94572
Regional Water Board
2 — San Francisco Bay

HUC12 watershed Evidence: spatial

  • Pinole Creek-Frontal San Pablo Bay Estuaries HUC12 180500020702

The facility's reported location lies within this HUC12 watershed (spatial derivation); it is not a discharge location.

Permits and applications Evidence: SMARTS record

Current permit record

Permit type
Industrial
Application type
Notice of Intent (WDID code I)
Status
Active
Operator
Auto Wreckers
Primary industry (SIC)
5015-Motor Vehicle Parts, Used
Application ID
181886
NOI processed
Sep 06, 1996
Last certified
Mar 06, 2015
Facility size
2 Acres
Impervious area
25 %

Retrieved from SMARTS Oct 20, 2026. Verify against SMARTS before relying on it.

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
181886 IndustrialActiveSep 06, 1996 —Mar 06, 2015

Every storm water application SMARTS records for this WDID, newest first (1).

Receiving water

Reported by the facility Evidence: facility-reported
Rodeo Creek
Discharges directly / indirectly
N / Y (as answered in the permit application)

Evidence: not confirmed Evidence: candidate, awaiting review Awaiting review

Receiving-water text as reported by the discharger in SMARTS; no waterbody identification has been confirmed.

Why it is not confirmed (1)
  • C1 name is only a prefix of official names

3 official waterbodies share this name; none is assigned without review.

Impaired waters and TMDLs

Two kinds of information, kept apart: 2026 Integrated Report waterbodies near the reported location (geographic proximity only), and TMDL records that SMARTS lists for this facility. Neither establishes where the facility discharges; see Receiving water for the facility's own statement.

Nearby waterbodies Evidence: geographic proximity

Spatial proximity only; discharge pathway not established. Being near a waterbody does not mean the facility discharges to it.

Nearest 2026 Integrated Report waterbodies
Waterbody (2026 Integrated Report)Distance2026 303(d) listAppendix A decisions
Rodeo Creek (Contra Costa County) CAR2066002219990219092843121 m listed2
San Pablo Bay CAB2061001019980928100945945 m listed10

Waterbodies within 1.0 km of the reported facility location. Method proximity/1.

SMARTS TMDL records Evidence: SMARTS-reported

No TMDL records for this facility in the SMARTS TMDL export.

Reported monitoring results Evidence: facility-reported

Numeric Action Level (NAL) screening is being independently validated and is not shown. Nothing on this page states whether a result exceeded a NAL.

No industrial monitoring results for this permit are in the current exports.

Compliance and enforcement records Evidence: SMARTS record

These are records as the State Water Board publishes them in SMARTS, with the source's own types and statuses. They are not a compliance determination or rating. A record listed here is not proof of a violation beyond what the source states, and the absence of records does not establish compliance.

Compliance and enforcement records by type
Record typeRecordsAs publishedDatesRetrievedList
Violations9 7 Violation · 0 Potential (preliminary) · 2 Dismissed Jul 04, 2005 – Jul 15, 2023 Oct 21, 2026 All violations
Enforcement actions12 10 issued · 2 draft · 0 withdrawn, rescinded or superseded Aug 05, 2005 – May 23, 2024 Oct 21, 2026 All actions
Inspections5inspections, not findings Oct 20, 2006 – Oct 17, 2016 Oct 21, 2026 All inspections
Annual reports11certified reports (contents not shown) 2015 – 2025 Oct 21, 2026 All reports
Water-quality-based corrective action reports0reports, by parameter — Oct 21, 2026

Each record type is counted by its own SMARTS identifier. A violation and the enforcement action that cites it are two records in two lists; they are never added together.

Chronological record history (37 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Jul 14, 2026 Annual reports 1336620 Annual report 2025 —
Jun 10, 2025 Annual reports 1244639 Annual report 2023 —
Jun 10, 2025 Annual reports 1295489 Annual report 2024 —
May 23, 2024 Enforcement actions 453413 NOV (Notice of Violation) Active
Jul 15, 2023 Violations 889093 Deficient Report ViolationReport
Jun 15, 2023 Annual reports 1190708 Annual report 2022 —
Jun 28, 2022 Annual reports 1114206 Annual report 2021 —
Jul 13, 2021 Annual reports 1070283 Annual report 2020 —
Jul 08, 2021 Annual reports 955280 Annual report 2018 —
Jul 27, 2020 Annual reports 987662 Annual report 2019 —
Jul 21, 2020 Enforcement actions 438186 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 15, 2020 Violations 874525 Late Report ViolationReport
Jul 16, 2018 Annual reports 940700 Annual report 2017 —
Jul 15, 2017 Annual reports 880042 Annual report 2016 —
Nov 01, 2016 Annual reports 844384 Annual report 2015 —
Oct 17, 2016 Inspections 2035234 B Type compliance —No Further Action
Dec 11, 2015 Enforcement actions 421960 NNC (Notice of Non-Compliance) Active
Oct 30, 2015 Enforcement actions 421027 NNC (Notice of Non-Compliance) Active
Aug 15, 2015 Violations 858706 Failure to Obtain Permit ViolationReport
Jun 09, 2015 Enforcement actions 419753 ACL (Administrative Civil Liability) Historical
Apr 17, 2015 Inspections 2025448 Inspection from Vehicle —Additional Info Required
Nov 07, 2014 Inspections 2023897 Inspection from Vehicle —Follow-up Inspection Needed
Jul 02, 2014 Violations 857527 Late Report ViolationReport
Jan 30, 2014 Enforcement actions 415773 1st NNC - AR (First Notice of Non-Compliance (annual report)) Active
Jul 02, 2013 Violations 854154 Late Report ViolationReport

Sources and provenance

Sources behind this page
InformationSourceRetrieved or published
Permit, location, receiving-water textSMARTS Industrial Application Specific DataOct 20, 2026
Permit historySMARTS Storm Water ApplicationsOct 20, 2026
Monitoring resultsSMARTS Industrial Parameter DataOct 20, 2026
Watershed Boundary Dataset HU2 GeoPackages 15, 16, 18 (WBDHU12)USGS2026-10-22
2026 California Integrated Report, Appendix A: 2026 303(d) List (final)SWRCB2026-10-22
Final_2026_Rivers_and_Streams + Final_2026_Lakes_and_Reservoirs (FeatureServer 0)SWRCB GIS2026-10-22
SMARTS TMDL requirementsSMARTS2026-10-21

Relationships computed 2026-10-22 with methods facility_huc12/1, proximity/1, receiving_water/2, tmdl_reference/1, waterbody_huc12_ovl/1, waterbody_huc12_pub/1; proximity threshold 1.0 km.

How to read the evidence labels

Records are shown as published and are not compliance determinations. How geographic context is derived.