A A Concrete Supply Tracy
Active WDID 5S39I016015 Tracy, San Joaquin 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
- Tracy, San Joaquin County
- Region 5S · Central Valley (Sacramento) · Location · Statewide map
- 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
- None
- Monitoring results Evidence: facility-reported
- None in the current exports
- Compliance and enforcement records Evidence: SMARTS record
- 5 inspections · 1 violation record · 1 enforcement action
- Counts as published in SMARTS; not a compliance determination · Details
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
Reported location Evidence: facility-reported
- Coordinates
- 37.696005, -121.43288
- 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
- 10250 W Linne Rd, Tracy 95377
- Regional Water Board
- 5S — Central Valley (Sacramento)
HUC12 watershed Evidence: spatial
- Upper Old River HUC12 180400030601
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
- 201831
- NOI processed
- Aug 14, 2000
- Last certified
- Jun 04, 2026
- Facility size
- 2.2 Acres
- Impervious area
- 85 %
Retrieved from SMARTS Oct 20, 2026. Verify against SMARTS before relying on it.
Permit history
| Application | Type | Status | Processed | Terminated | Certified |
|---|---|---|---|---|---|
| 201831 | Industrial | Active | Aug 14, 2000 | — | Jun 04, 2026 |
Every storm water application SMARTS records for this WDID, newest first (1).
Receiving water
- Reported by the facility Evidence: facility-reported
- Corral Hollow Creek
- Discharges directly / indirectly
- N / N (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.
No 2026 Integrated Report waterbody lies within the proximity threshold of the reported location.
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.
| Record type | Records | As published | Dates | Retrieved | List |
|---|---|---|---|---|---|
| Violations | 1 | 1 Violation · 0 Potential (preliminary) · 0 Dismissed | Mar 30, 2006 – Mar 30, 2006 | Oct 21, 2026 | All violations |
| Enforcement actions | 1 | 1 issued · 0 draft · 0 withdrawn, rescinded or superseded | Mar 30, 2007 – Mar 30, 2007 | Oct 21, 2026 | All actions |
| Inspections | 5 | inspections, not findings | Apr 21, 2004 – Dec 20, 2017 | Oct 21, 2026 | All inspections |
| Annual reports | 11 | certified reports (contents not shown) | 2015 – 2025 | Oct 21, 2026 | All reports |
| Water-quality-based corrective action reports | 0 | reports, 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 (18 records, newest first)
| Date | Record | ID | Type or purpose | Status as published | Detail |
|---|---|---|---|---|---|
| Jun 09, 2026 | Annual reports | 1333818 | Annual report 2025 | — | |
| Jun 20, 2025 | Annual reports | 1292578 | Annual report 2024 | — | |
| Jul 02, 2024 | Annual reports | 1241560 | Annual report 2023 | — | |
| Jul 11, 2023 | Annual reports | 1187474 | Annual report 2022 | — | |
| Jul 07, 2022 | Annual reports | 1110700 | Annual report 2021 | — | |
| Jul 08, 2021 | Annual reports | 1066614 | Annual report 2020 | — | |
| Jul 07, 2020 | Annual reports | 983738 | Annual report 2019 | — | |
| Jul 01, 2019 | Annual reports | 951226 | Annual report 2018 | — | |
| Jun 13, 2018 | Annual reports | 936632 | Annual report 2017 | — | |
| Dec 20, 2017 | Inspections | 2036357 | B Type compliance | — | Additional Info Required |
| Jul 14, 2017 | Annual reports | 875753 | Annual report 2016 | — | |
| Jun 27, 2016 | Annual reports | 845963 | Annual report 2015 | — | |
| Aug 16, 2012 | Inspections | 2016217 | B Type compliance | — | No Further Action |
| Nov 16, 2011 | Inspections | 2013380 | B Type compliance | — | No Further Action |
| Aug 05, 2010 | Inspections | 2008354 | B Type compliance | — | No Further Action |
| Mar 30, 2007 | Enforcement actions | 328318 | NOV (Notice of Violation) | Active | |
| Mar 30, 2006 | Violations | 497424 | Deficient Report | Violation | Report |
| Apr 21, 2004 | Inspections | 335230 | B Type compliance | — |
Sources and provenance
| Information | Source | Retrieved or published |
|---|---|---|
| Permit, location, receiving-water text | SMARTS Industrial Application Specific Data | Oct 20, 2026 |
| Permit history | SMARTS Storm Water Applications | Oct 20, 2026 |
| Monitoring results | SMARTS Industrial Parameter Data | Oct 20, 2026 |
| Watershed Boundary Dataset HU2 GeoPackages 15, 16, 18 (WBDHU12) | USGS | 2026-10-22 |
| 2026 California Integrated Report, Appendix A: 2026 303(d) List (final) | SWRCB | 2026-10-22 |
| Final_2026_Rivers_and_Streams + Final_2026_Lakes_and_Reservoirs (FeatureServer 0) | SWRCB GIS | 2026-10-22 |
| SMARTS TMDL requirements | SMARTS | 2026-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
- Evidence: SMARTS record Evidence: facility-reported Information as published in SMARTS or reported by the discharger.
- Evidence: identification corroborated The reported receiving-water name identifies one official waterbody and the facility's location is consistent with it. It does not establish a discharge pathway.
- Evidence: candidate, awaiting review Evidence: not confirmed The reported name could match one or more official waterbodies, but no identification has been confirmed; nothing is assigned without review.
- Evidence: spatial Evidence: geographic proximity Derived from the reported location only.
- Evidence: SMARTS-reported Source records whose links to official references are not yet reviewed.
- Evidence: unavailable The information could not be loaded or is not in the sources.
Records are shown as published and are not compliance determinations. How geographic context is derived.