Sturdy Oil Company
Active WDID 3 27I027251 Salinas, Monterey County Region 3 · Central Coast
At a glance
- Permit Evidence: SMARTS record
- Active Industrial
- Notice of Intent (WDID code I) · Permits and applications
- Location Evidence: facility-reported
- Salinas, Monterey County
- Region 3 · Central Coast · 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
- 2 waterbodies; 2 on the 2026 303(d) list
- Proximity only; not a discharge pathway · Nearby waterbodies
- Monitoring results Evidence: facility-reported
- 106 distinct results, 9 reporting years (2016 to 2025)
- Most recent sample Feb 10, 2026 · Monitoring
- Compliance and enforcement records Evidence: SMARTS record
- 0 inspections · 0 violation records · 0 enforcement actions
- 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
- 36.65149, -121.6213
- Precision
- 4 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
- 1511 Abbott st, Salinas 93901
- Regional Water Board
- 3 — Central Coast
HUC12 watershed Evidence: spatial
- Alisal Creek-Salinas River HUC12 180600051509
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
- STURDY OIL COMPANY
- Primary industry (SIC)
- 5171-Petroleum Bulk Stations and Terminals
- Application ID
- 477521
- NOI processed
- Jul 14, 2017
- Last certified
- Jul 13, 2017
- Facility size
- 0.99 Acres
- Impervious area
- 0 %
Retrieved from SMARTS Oct 20, 2026. Verify against SMARTS before relying on it.
Permit history
| Application | Type | Status | Processed | Terminated | Certified |
|---|---|---|---|---|---|
| 477521 | Industrial | Active | Jul 14, 2017 | — | Jul 13, 2017 |
Every storm water application SMARTS records for this WDID, newest first (1).
Receiving water
- Reported by the facility Evidence: facility-reported
- Salinas River (460)
- Discharges directly / indirectly
- Y / 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.
| Waterbody (2026 Integrated Report) | Distance | 2026 303(d) list | Appendix A decisions |
|---|---|---|---|
| Alisal Creek (Monterey County) CAR3097009519990222130537 | 584 m | listed | 18 |
| Salinas Reclamation Canal CAR3091101019980828112229 | 963 m | listed | 31 |
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.
106 distinct measurements across 6 parameters, most recent sample Feb 10, 2026.
By reporting year
| Reporting year (July–June) | Distinct results | Parameters | With several versions | First sample | Last sample |
|---|---|---|---|---|---|
| 2025 | 10 | 5 | 0 | Oct 13, 2025 | Feb 10, 2026 |
| 2024 | 13 | 5 | 0 | Dec 24, 2024 | Mar 12, 2025 |
| 2023 | 10 | 5 | 0 | Dec 20, 2023 | Jan 22, 2024 |
| 2022 | 15 | 5 | 0 | Dec 01, 2022 | Mar 10, 2023 |
| 2020 | 12 | 6 | 0 | Feb 11, 2021 | Mar 10, 2021 |
| 2019 | 11 | 6 | 0 | Nov 26, 2019 | Jan 16, 2020 |
| 2018 | 6 | 3 | 0 | Nov 28, 2018 | May 15, 2019 |
| 2017 | 6 | 6 | 0 | Jan 08, 2018 | Jan 08, 2018 |
| 2016 | 23 | 6 | 0 | Dec 08, 2016 | Mar 21, 2017 |
By parameter
| Parameter | Units | Measurements | Below detection | First sample | Last sample | Results |
|---|---|---|---|---|---|---|
| pH | SU | 21 | 0 | Dec 08, 2016 | Feb 10, 2026 | Results |
| Total Suspended Solids (TSS) | mg/L | 21 | 0 | Dec 08, 2016 | Feb 10, 2026 | Results |
| Oil and Grease | mg/L | 20 | 13 | Dec 08, 2016 | Feb 10, 2026 | Results |
| Gasoline | mg/L | 18 | 10 | Dec 08, 2016 | Feb 10, 2026 | Results |
| Diesel Oil | mg/L | 17 | 0 | Dec 08, 2016 | Feb 10, 2026 | Results |
| Benzene | ug/L | 9 | 8 | Dec 08, 2016 | Mar 10, 2021 | Results |
Benzene results (9 distinct rows, show all)
| Sample date | Parameter | Result | Units | Location type | Event | Method | Report | Versions |
|---|---|---|---|---|---|---|---|---|
| Mar 10, 2021 | Benzene | ND | ug/L | Effluent | Qualifying Storm Event | E624 | 1146138 | |
| Feb 11, 2021 | Benzene | ND | ug/L | Effluent | Qualifying Storm Event | 1156145 | ||
| Jan 16, 2020 | Benzene | ND | ug/L | Effluent | Qualifying Storm Event | E602 | 1108276 | |
| Nov 26, 2019 | Benzene | ND | ug/L | Effluent | Qualifying Storm Event | E602 | 1102611 | |
| Jan 08, 2018 | Benzene | ND | ug/L | Effluent | Qualifying Storm Event | E624 | 1003374 | |
| Mar 21, 2017 | Benzene | ND | ug/L | Effluent | Qualifying Storm Event | E502.2 | 924969 | |
| Jan 18, 2017 | Benzene | ND | ug/L | Effluent | Qualifying Storm Event | E502.2 | 924969 | |
| Dec 15, 2016 | Benzene | ND | ug/L | Effluent | Qualifying Storm Event | E502.2 | 924969 | |
| Dec 08, 2016 | Benzene | .69 | ug/L | Effluent | Qualifying Storm Event | E502.2 | 924969 |
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.
| Record type | Records | As published | Dates | Retrieved | List |
|---|---|---|---|---|---|
| Violations | 0 | 0 Violation · 0 Potential (preliminary) · 0 Dismissed | — | Oct 21, 2026 | |
| Enforcement actions | 0 | 0 issued · 0 draft · 0 withdrawn, rescinded or superseded | — | Oct 21, 2026 | |
| Inspections | 0 | inspections, not findings | — | Oct 21, 2026 | |
| Annual reports | 10 | certified reports (contents not shown) | 2016 – 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 (10 records, newest first)
| Date | Record | ID | Type or purpose | Status as published | Detail |
|---|---|---|---|---|---|
| Jul 09, 2026 | Annual reports | 1338616 | Annual report 2025 | — | |
| Jun 16, 2025 | Annual reports | 1297622 | Annual report 2024 | — | |
| Jul 09, 2024 | Annual reports | 1246869 | Annual report 2023 | — | |
| Jul 10, 2023 | Annual reports | 1193040 | Annual report 2022 | — | |
| Jul 11, 2022 | Annual reports | 1116814 | Annual report 2021 | — | |
| Aug 25, 2021 | Annual reports | 1065001 | Annual report 2020 | — | |
| Jul 14, 2020 | Annual reports | 982058 | Annual report 2019 | — | |
| Jul 06, 2019 | Annual reports | 958388 | Annual report 2018 | — | |
| Jul 05, 2018 | Annual reports | 975801 | Annual report 2017 | — | |
| Jul 13, 2017 | Annual reports | 906434 | Annual report 2016 | — |
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.