Diamond Valley Lake Marina

Active WDID 9 33I022661 Hemet, Riverside County Region 9 · San Diego

At a glance

Permit Evidence: SMARTS record
Active Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Hemet, Riverside County
Region 9 · San Diego · Location · Statewide map
Receiving water
Diamond Valley Lake (as reported by the facility)
Evidence: identification corroborated Diamond Valley Lake Details
Identified receiving water on the 2026 303(d) list
Yes · 1 Appendix A decision, category 5 Evidence: State-published
Describes the waterbody, not this facility · Waterbody profile
2026 Integrated Report waters within 1.0 km Evidence: geographic proximity
1 waterbody; 1 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
1 inspection · 4 violation records · 5 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
33.70382, -117.00315
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
2615 Angler Ave, Hemet 92545
Regional Water Board
9 — San Diego

HUC12 watershed Evidence: spatial

  • Warm Springs Creek HUC12 180703020401

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
Urban Park Concessionaires
Primary industry (SIC)
4493-Marinas
Application ID
403584
NOI processed
Jun 07, 2010
Last certified
Jun 24, 2015
Facility size
7.5 Acres
Impervious area
75 %

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
403584 IndustrialActiveJun 07, 2010 —Jun 24, 2015

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

Receiving water

Reported by the facility Evidence: facility-reported
Diamond Valley Lake
Discharges directly / indirectly
N / — (as answered in the permit application)

Evidence: identification corroborated Diamond Valley Lake CAL9023600020190708042418

Receiving water reported by facility — waterbody identification corroborated by geographic evidence.

Nearest distance from the reported facility location: 85 m. Method receiving_water/2.

2026 Integrated Report status Evidence: State-published

Diamond Valley Lake is on the 2026 Clean Water Act section 303(d) list (1 Appendix A decision; category 5).

2026 Appendix A decisions for the identified receiving water
PollutantCategoryListing decisionTMDL requirementDecision ID
Mercury5List on 303(d) list (TMDL required list) 5A128217

Published by the State Water Resources Control Board (2026 California Integrated Report, Appendix A). Listing status is taken from Appendix A only. State Board adoption 2026-02-03; USEPA approval not confirmed. A listing describes the waterbody, not this facility. Waterbody profile.

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
Diamond Valley Lake CAL902360002019070804241885 m listed1

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
Violations4 4 Violation · 0 Potential (preliminary) · 0 Dismissed Jul 01, 2012 – Jul 16, 2026 Oct 21, 2026 All violations
Enforcement actions5 5 issued · 0 draft · 0 withdrawn, rescinded or superseded Aug 09, 2012 – Jul 22, 2026 Oct 21, 2026 All actions
Inspections1inspections, not findings Jan 28, 2015 – Jan 28, 2015 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 (21 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Sep 02, 2026 Annual reports 1296537 Annual report 2024 —
Sep 02, 2026 Annual reports 1337614 Annual report 2025 —
Jul 22, 2026 Enforcement actions 471066 NOV (Notice of Violation) Active
Jul 16, 2026 Violations 905143 Late Report ViolationReport
Sep 10, 2025 Enforcement actions 463741 NOV (Notice of Violation) Active
Aug 08, 2025 Enforcement actions 457320 NOV (Notice of Violation) Active
Jul 15, 2025 Violations 892791 Late Report ViolationReport
Jul 14, 2024 Annual reports 1191872 Annual report 2022 —
Jul 15, 2023 Annual reports 1245749 Annual report 2023 —
Jul 14, 2022 Annual reports 1115476 Annual report 2021 —
Jul 15, 2021 Annual reports 1063577 Annual report 2020 —
Jul 15, 2020 Annual reports 980483 Annual report 2019 —
Jul 14, 2019 Annual reports 956749 Annual report 2018 —
Sep 05, 2018 Annual reports 942179 Annual report 2017 —
Jul 15, 2017 Annual reports 881603 Annual report 2016 —
Oct 18, 2016 Annual reports 844155 Annual report 2015 —
Aug 01, 2016 Enforcement actions 423878 1st NNC - AR (First Notice of Non-Compliance (annual report)) Active
Jul 16, 2016 Violations 861015 Late Report ViolationReport
Jan 28, 2015 Inspections 2024617 B Type compliance —No Further Action
Aug 09, 2012 Enforcement actions 411581 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 01, 2012 Violations 850526 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.