Mathews Readymix Yuba City

Terminated WDID 5S51I003508 Yuba City, Sutter County Region 5S · Central Valley (Sacramento)

At a glance

Permit Evidence: SMARTS record
Terminated Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Yuba City, Sutter County
Region 5S · Central Valley (Sacramento) · Location · Statewide map
Receiving water
Gilsizer Slough / Sutter Bypass (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
None in the current exports
Compliance and enforcement records Evidence: SMARTS record
9 inspections · 5 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
39.140933, -121.610264
Precision
6 decimal places
Shared point
2 permits report this exact point
Matches application record
same

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

Facility address
249 Lamon Wy, Yuba City 95993
Regional Water Board
5S — Central Valley (Sacramento)

HUC12 watershed Evidence: spatial

  • Gilsizer Slough-Snake River HUC12 180201590400

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
Mathews Readymix LLC
Primary industry (SIC)
3273-Ready-Mixed Concrete
Application ID
202722
NOI processed
Apr 03, 1992
Termination effective
Dec 07, 2021
Last certified
Jul 19, 2016
Facility size
2 Acres
Impervious area
95 %

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
202722 IndustrialTerminatedApr 03, 1992 Dec 07, 2021Jul 19, 2016

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

Receiving water

Reported by the facility Evidence: facility-reported
Gilsizer Slough / Sutter Bypass
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
Feather River, Lower (Lake Oroville Dam to Confluence with Sacramento River) CAR5192200019980817161057225 m listed4

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
Violations5 5 Violation · 0 Potential (preliminary) · 0 Dismissed Mar 23, 2005 – Feb 08, 2012 Oct 21, 2026 All violations
Enforcement actions5 5 issued · 0 draft · 0 withdrawn, rescinded or superseded May 03, 2005 – Mar 30, 2012 Oct 21, 2026 All actions
Inspections9inspections, not findings Mar 23, 2005 – Mar 03, 2015 Oct 21, 2026 All inspections
Annual reports7certified reports (contents not shown) 2015 – 2021 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 (26 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Dec 07, 2021 Annual reports 1114691 Annual report 2021 —
Jul 09, 2021 Annual reports 1070789 Annual report 2020 —
Jul 14, 2020 Annual reports 988208 Annual report 2019 —
Jul 10, 2019 Annual reports 955841 Annual report 2018 —
Jul 09, 2018 Annual reports 941265 Annual report 2017 —
Jul 12, 2017 Annual reports 880639 Annual report 2016 —
Jul 25, 2016 Annual reports 839461 Annual report 2015 —
Mar 03, 2015 Inspections 2024976 B Type compliance —No Further Action
Mar 13, 2013 Inspections 2018467 B Type compliance —No Further Action
Mar 30, 2012 Enforcement actions 408426 13267 Letter/Order (Water Code section 13267 letter or order) Historical
Feb 08, 2012 Enforcement actions 408079 Verbal Communication Active
Feb 08, 2012 Inspections 2014292 B Type compliance —Follow-up Inspection Needed
Feb 08, 2012 Violations 847401 Deficient BMP Implementation ViolationInspection
Jul 01, 2011 Violations 847730 Deficient BMP Implementation ViolationReport
Apr 21, 2011 Inspections 2012562 Non-compliance Follow-up —Follow-up Inspection Needed
Apr 06, 2011 Inspections 2011307 B Type compliance —Follow-up Inspection Needed
Feb 15, 2011 Inspections 2010677 B Type compliance —No Further Action
Aug 24, 2010 Inspections 2008460 B Type compliance —No Further Action
Oct 23, 2009 Enforcement actions 401764 SEL (Staff Enforcement Letter) Historical
Jul 01, 2009 Violations 841606 Deficient BMP Implementation ViolationReport
May 01, 2008 Enforcement actions 347679 SEL (Staff Enforcement Letter) Active
Jul 01, 2007 Violations 766023 Deficient BMP Implementation ViolationStorm Water Discharge
May 03, 2006 Inspections 599754 B Type compliance —No Further Action
May 03, 2005 Enforcement actions 256526 NOV (Notice of Violation) Historical
Mar 23, 2005 Inspections 338358 B Type compliance —

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.