Monterey Cnty Lake San Antonio

Terminated WDID 3 27I005646 Salinas, Monterey County Region 3 · Central Coast

At a glance

Permit Evidence: SMARTS record
Terminated Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Salinas, Monterey County
Region 3 · Central Coast · Location · Statewide map
Receiving water
San Antonio River Basin (as reported by the facility)
Evidence: not confirmed 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
1 waterbody; 1 on the 2026 303(d) list
Proximity only; not a discharge pathway · Nearby waterbodies
Monitoring results Evidence: facility-reported
94 distinct results, 5 reporting years (2015 to 2019)
Most recent sample Apr 09, 2020 · Monitoring
Compliance and enforcement records Evidence: SMARTS record
0 inspections · 3 violation records · 6 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
36.67307, -121.65952
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
168 W Alisal St 2nd Fl, Salinas 93901
Regional Water Board
3 — Central Coast

HUC12 watershed Evidence: spatial

  • Alisal Slough-Tembladero Slough HUC12 180600150103

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
Terminated
Operator
Monterey Co RMA Administration
Primary industry (SIC)
4953-Refuse Systems
Application ID
185163
NOI processed
Apr 07, 1992
Termination effective
Dec 03, 2020
Last certified
Jun 20, 2018
Facility size
2 Acres

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
185163 IndustrialTerminatedApr 07, 1992 Dec 03, 2020Jun 20, 2018

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

Receiving water

Reported by the facility Evidence: facility-reported
San Antonio River Basin
Discharges directly / indirectly
N / Y (as answered in the permit application)

Evidence: not confirmed Not matchable to a single waterbody

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

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
Salinas Reclamation Canal CAR3091101019980828112229934 m listed31

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.

94 distinct measurements across 7 parameters, most recent sample Apr 09, 2020.

By reporting year

Distinct results by reporting year
Reporting year (July–June)Distinct resultsParametersWith several versionsFirst sampleLast sample
2019204 0 Dec 05, 2019Apr 09, 2020
2018305 0 Nov 30, 2018Mar 07, 2019
201744 0 Dec 29, 2017Dec 29, 2017
2016244 0 Oct 28, 2016Feb 22, 2017
2015166 0 Dec 15, 2015Jan 21, 2016

By parameter

Distinct results by parameter
ParameterUnitsMeasurementsBelow detectionFirst sampleLast sampleResults
pHSU22 0Dec 15, 2015Apr 09, 2020 Results
Total Suspended Solids (TSS)mg/L22 1Dec 15, 2015Apr 09, 2020 Results
Oil and Greasemg/L19 18Jan 21, 2016Apr 09, 2020 Results
Iron, Totalmg/L14 1Dec 15, 2015Apr 09, 2020 Results
Iron, Total Recoverableug/L8 2Dec 28, 2015Feb 22, 2017 Results
TurbidityNTU6 0Nov 30, 2018Mar 07, 2019 Results
Total Organic Carbon (TOC)mg/L3 0Dec 15, 2015Jan 11, 2016 Results

pH results (22 distinct rows, show all)

Reported monitoring results, newest first
Sample dateParameterResultUnitsLocation typeEventMethodReportVersions
Apr 09, 2020 pH 6.57 SU Effluent Qualifying Storm Event pH_Field 1109064
Mar 19, 2020 pH 6.88 SU Effluent Qualifying Storm Event pH_Field 1109064
Mar 11, 2020 pH 6.54 SU Effluent Qualifying Storm Event pH_Field 1109064
Dec 30, 2019 pH 6.7 SU Effluent Qualifying Storm Event pH_Field 1109064
Dec 05, 2019 pH 6.89 SU Effluent Qualifying Storm Event pH_Field 1109064
Mar 07, 2019 pH 6.71 SU Effluent Qualifying Storm Event pH_Field 1055128
Feb 06, 2019 pH 6.59 SU Effluent Qualifying Storm Event pH_Field 1055124
Jan 21, 2019 pH 6.79 SU Effluent Qualifying Storm Event pH_Field 1055121
Jan 10, 2019 pH 7.01 SU Effluent Qualifying Storm Event pH_Field 1055119
Dec 07, 2018 pH 6.41 SU Effluent Qualifying Storm Event pH_Field 1055117
Nov 30, 2018 pH 6.59 SU Effluent Qualifying Storm Event pH_Field 1055115
Dec 29, 2017 pH 6.41 SU Effluent Qualifying Storm Event pH_Field 990042
Feb 22, 2017 pH 6.83 SU Effluent Qualifying Storm Event A4500HB 927103
Jan 24, 2017 pH 6.6 SU Effluent Qualifying Storm Event A4500HB 927098
Jan 09, 2017 pH 6.82 SU Effluent Qualifying Storm Event A4500HB 915855
Dec 16, 2016 pH 6.92 SU Effluent Qualifying Storm Event A4500HB 912660
Nov 21, 2016 pH 6.94 SU Effluent Qualifying Storm Event A4500HB 908504
Oct 28, 2016 pH 6.38 SU Effluent Qualifying Storm Event A4500HB 908504
Jan 21, 2016 pH 6.88 SU Effluent Qualifying Storm Event A4500HB 888561
Jan 11, 2016 pH 7.04 SU Effluent Qualifying Storm Event A4500HB 888561
Dec 28, 2015 pH 6.79 SU Effluent Qualifying Storm Event A4500HB 888561
Dec 15, 2015 pH 7.37 SU Effluent Qualifying Storm Event A4500HB 888561

Results are shown exactly as reported by the discharger. Identical rows repeated in the State's export are shown once. Where the export contains different versions of the same sample and parameter, each version is listed and flagged. Details.

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
Violations3 3 Violation · 0 Potential (preliminary) · 0 Dismissed Feb 07, 2005 – Jul 16, 2020 Oct 21, 2026 All violations
Enforcement actions6 6 issued · 0 draft · 0 withdrawn, rescinded or superseded Feb 07, 2005 – Sep 25, 2020 Oct 21, 2026 All actions
Inspections0inspections, not findings — Oct 21, 2026
Annual reports5certified reports (contents not shown) 2015 – 2019 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 (14 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Sep 25, 2020 Annual reports 983852 Annual report 2019 —
Sep 25, 2020 Enforcement actions 437964 2nd NNC - AR (Second Notice of Non-Compliance (annual report)) Historical
Aug 17, 2020 Enforcement actions 437260 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 16, 2020 Violations 873703 Late Report ViolationReport
Aug 12, 2019 Annual reports 951343 Annual report 2018 —
Jul 16, 2018 Annual reports 936749 Annual report 2017 —
Jul 11, 2017 Annual reports 875875 Annual report 2016 —
Jul 15, 2016 Annual reports 838983 Annual report 2015 —
Apr 08, 2014 Enforcement actions 414704 ACL (Administrative Civil Liability) HistoricalR3-2014-0017
Sep 26, 2013 Enforcement actions 414368 2nd NNC - AR (Second Notice of Non-Compliance (annual report)) Historical
Aug 09, 2013 Enforcement actions 413076 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 01, 2013 Violations 851688 Late Report ViolationReport
Feb 07, 2005 Enforcement actions 256186 SEL (Staff Enforcement Letter) HistoricalUNKNOWN
Feb 07, 2005 Violations 264384 Deficient BMP Implementation ViolationInspection

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.