Feather River Concrete Product

Terminated WDID 5S51I011536 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
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
11 inspections · 15 violation records · 10 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.148798, -121.614627
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
1257 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
Terminated
Operator
Feather River Concrete Product
Primary industry (SIC)
3273-Ready-Mixed Concrete
Application ID
202732
NOI processed
Apr 06, 1995
Termination effective
Jul 18, 2014
Last certified
—
Facility size
54250 SqFt

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
202732 IndustrialTerminatedApr 06, 1995 Jul 18, 2014—

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
— / — (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) CAR5192200019980817161057713 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
Violations15 15 Violation · 0 Potential (preliminary) · 0 Dismissed Jul 02, 1999 – Jul 01, 2014 Oct 21, 2026 All violations
Enforcement actions10 10 issued · 0 draft · 0 withdrawn, rescinded or superseded Mar 27, 2000 – Aug 15, 2014 Oct 21, 2026 All actions
Inspections11inspections, not findings Mar 23, 2005 – Jun 05, 2014 Oct 21, 2026 All inspections
Annual reports0certified reports (contents not shown) — Oct 21, 2026
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 (36 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Aug 15, 2014 Enforcement actions 416674 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 01, 2014 Violations 855017 Late Report ViolationReport
Jun 05, 2014 Inspections 2022543 Enforcement Follow-up —No Further Action
Oct 31, 2013 Inspections 2020269 B Type compliance —Follow-up Inspection Needed
Mar 05, 2013 Inspections 2018463 B Type compliance —Follow-up Inspection Needed
Mar 05, 2013 Violations 851028 Deficient BMP Implementation ViolationInspection
Aug 01, 2012 Inspections 2016201 B Type compliance —Follow-up Inspection Needed
Feb 08, 2012 Inspections 2014209 B Type compliance —Follow-up Inspection Needed
Nov 30, 2011 Inspections 2013432 B Type compliance —Follow-up Inspection Needed
Nov 30, 2011 Violations 846824 Deficient BMP Implementation ViolationInspection
Nov 15, 2011 Enforcement actions 407186 Verbal Communication Historical
Nov 15, 2011 Inspections 2013431 B Type compliance —Follow-up Inspection Needed
Nov 15, 2011 Violations 846822 Deficient BMP Implementation ViolationInspection
Nov 03, 2011 Inspections 2013247 B Type compliance —Follow-up Inspection Needed
Nov 03, 2011 Violations 846823 Deficient BMP Implementation ViolationInspection
Sep 03, 2010 Enforcement actions 402592 NOV (Notice of Violation) Historical
Aug 24, 2010 Inspections 2008593 B Type compliance —Follow-up Inspection Needed
Aug 24, 2010 Violations 842414 Deficient BMP Implementation ViolationInspection
Aug 24, 2010 Violations 842415 Deficient BMP Implementation ViolationInspection
Aug 03, 2010 Enforcement actions 402591 Verbal Communication Historical
Aug 03, 2010 Inspections 2008590 B Type compliance —Follow-up Inspection Needed
Aug 03, 2010 Violations 842413 Deficient BMP Implementation ViolationInspection
May 01, 2008 Enforcement actions 347508 SEL (Staff Enforcement Letter) Historical
Jul 01, 2007 Violations 765707 Deficient BMP Implementation ViolationStorm Water Discharge
Mar 30, 2007 Enforcement actions 328468 NOV (Notice of Violation) Historical

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.