A A Concrete Supply Yuba City

Active WDID 5S51I007216 Yuba City, Sutter County Region 5S · Central Valley (Sacramento)

At a glance

Permit Evidence: SMARTS record
Active 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
Feather River (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
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
5 inspections · 4 violation records · 4 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.147909, -121.614588
Precision
6 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
1201 Market St, Yuba City 95991
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
Active
Operator
A & A Ready Mixed Concrete Inc dba A & A Concrete Supply
Primary industry (SIC)
3273-Ready-Mixed Concrete
Application ID
202727
NOI processed
Jun 18, 1992
Last certified
Jun 04, 2026
Facility size
1.25 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
202727 IndustrialActiveJun 18, 1992 —Jun 04, 2026

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

Receiving water

Reported by the facility Evidence: facility-reported
Feather River
Discharges directly / indirectly
N / N (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

8 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
Feather River, Lower (Lake Oroville Dam to Confluence with Sacramento River) CAR5192200019980817161057664 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
Violations4 4 Violation · 0 Potential (preliminary) · 0 Dismissed Jul 01, 2005 – Oct 04, 2019 Oct 21, 2026 All violations
Enforcement actions4 4 issued · 0 draft · 0 withdrawn, rescinded or superseded Sep 12, 2006 – Oct 04, 2019 Oct 21, 2026 All actions
Inspections5inspections, not findings Aug 03, 2010 – May 21, 2024 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 (24 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Jun 09, 2026 Annual reports 1334626 Annual report 2025 —
Jun 20, 2025 Annual reports 1293416 Annual report 2024 —
Jul 02, 2024 Annual reports 1242446 Annual report 2023 —
May 21, 2024 Inspections 2064601 B Type compliance FinalizedAdditional Info Required
Jul 11, 2023 Annual reports 1188408 Annual report 2022 —
Jul 07, 2022 Annual reports 1111708 Annual report 2021 —
Jul 09, 2021 Annual reports 1067673 Annual report 2020 —
May 27, 2021 Annual reports 876975 Annual report 2016 —
May 27, 2021 Annual reports 937790 Annual report 2017 —
May 27, 2021 Annual reports 952377 Annual report 2018 —
May 27, 2021 Annual reports 984862 Annual report 2019 —
Oct 04, 2019 Enforcement actions 434238 13267 Letter/Order (Water Code section 13267 letter or order) Historical
Oct 04, 2019 Violations 871123 Deficient Report ViolationReport
Jun 27, 2016 Annual reports 845577 Annual report 2015 —
Feb 11, 2015 Inspections 2024974 Complaint —Additional Info Required
Jun 11, 2014 Violations 853833 Deficient BMP Implementation ViolationInternal Report
Jun 10, 2014 Enforcement actions 415552 Verbal Communication Historical
Aug 01, 2012 Inspections 2016187 B Type compliance —No Further Action
Nov 03, 2011 Inspections 2013246 B Type compliance —No Further Action
Aug 03, 2010 Inspections 2008353 B Type compliance —No Further Action
May 01, 2008 Enforcement actions 347366 SEL (Staff Enforcement Letter) Historical
Jul 01, 2007 Violations 765019 Deficient BMP Implementation ViolationStorm Water Discharge
Sep 12, 2006 Enforcement actions 309227 NOV (Notice of Violation) Historical
Jul 01, 2005 Violations 432644 Deficient 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.