City of Hollister
Terminated WDID 3 35I004716 Hollister, San Benito County Region 3 · Central Coast
At a glance
- Permit Evidence: SMARTS record
- Terminated Industrial
- Notice of Intent (WDID code I) · Permits and applications
- Location Evidence: facility-reported
- Hollister, San Benito County
- Region 3 · Central Coast · Location · Statewide map
- Receiving water
- Santa Ana Creek (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
- None
- Monitoring results Evidence: facility-reported
- 12 distinct results, 1 reporting year (2016 to 2016)
- Most recent sample Feb 22, 2017 · Monitoring
- Compliance and enforcement records Evidence: SMARTS record
- 0 inspections · 4 violation records · 3 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.89007, -121.40313
- 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
- 90 Skylane Dr Ste 101, Hollister 95023
- Regional Water Board
- 3 — Central Coast
HUC12 watershed Evidence: spatial
- Tequisquita Slough HUC12 180600020103
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
- Hollister City
- Primary industry (SIC)
- 4581-Airports, Flying Fields, and Airport Terminal Services
- Application ID
- 185293
- NOI processed
- Apr 07, 1992
- Termination effective
- Aug 12, 2019
- Last certified
- Oct 16, 2026
- Facility size
- 343 Acres
Retrieved from SMARTS Oct 20, 2026. Verify against SMARTS before relying on it.
Permit history
| Application | Type | Status | Processed | Terminated | Certified |
|---|---|---|---|---|---|
| 185293 | Industrial | Terminated | Apr 07, 1992 | Aug 12, 2019 | Oct 16, 2026 |
Every storm water application SMARTS records for this WDID, newest first (1).
Receiving water
- Reported by the facility Evidence: facility-reported
- Santa Ana Creek
- Discharges directly / indirectly
- Y / 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
1 official waterbody shares 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.
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.
12 distinct measurements across 3 parameters, most recent sample Feb 22, 2017.
By reporting year
| Reporting year (July–June) | Distinct results | Parameters | With several versions | First sample | Last sample |
|---|---|---|---|---|---|
| 2016 | 12 | 3 | 0 | Jan 05, 2016 | Feb 22, 2017 |
By parameter
| Parameter | Units | Measurements | Below detection | First sample | Last sample | Results |
|---|---|---|---|---|---|---|
| Oil and Grease | mg/L | 4 | 2 | Jan 05, 2016 | Feb 22, 2017 | Results |
| pH | SU | 4 | 0 | Jan 05, 2016 | Feb 22, 2017 | Results |
| Total Suspended Solids (TSS) | mg/L | 4 | 0 | Jan 05, 2016 | Feb 22, 2017 | Results |
All results (12 distinct rows)
| Sample date | Parameter | Result | Units | Location type | Event | Method | Report | Versions |
|---|---|---|---|---|---|---|---|---|
| Feb 22, 2017 | Oil and Grease | 1.7 | mg/L | Effluent | Qualifying Storm Event | E1664A | 934010 | |
| Feb 22, 2017 | pH | 7.04 | SU | Effluent | Qualifying Storm Event | A4500HB | 934010 | |
| Feb 22, 2017 | Total Suspended Solids (TSS) | 33 | mg/L | Effluent | Qualifying Storm Event | A2540D | 934010 | |
| Jan 12, 2017 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | A5220B | 934010 | |
| Jan 12, 2017 | pH | 7.43 | SU | Effluent | Qualifying Storm Event | A4500HB | 934010 | |
| Jan 12, 2017 | Total Suspended Solids (TSS) | 59 | mg/L | Effluent | Qualifying Storm Event | A2540D | 934010 | |
| Oct 28, 2016 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | A5220B | 934010 | |
| Oct 28, 2016 | pH | 6.64 | SU | Effluent | Qualifying Storm Event | A4500HB | 934010 | |
| Oct 28, 2016 | Total Suspended Solids (TSS) | 7 | mg/L | Effluent | Qualifying Storm Event | A2540D | 934010 | |
| Jan 05, 2016 | Oil and Grease | 2.4 | mg/L | Effluent | Qualifying Storm Event | E1664A | 934010 | |
| Jan 05, 2016 | pH | 7.68 | SU | Effluent | Qualifying Storm Event | A4500HB | 934010 | |
| Jan 05, 2016 | Total Suspended Solids (TSS) | 2 | mg/L | Effluent | Qualifying Storm Event | A2540D | 934010 |
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 | 4 | 4 Violation · 0 Potential (preliminary) · 0 Dismissed | Jul 02, 1999 – Jul 01, 2010 | Oct 21, 2026 | All violations |
| Enforcement actions | 3 | 3 issued · 0 draft · 0 withdrawn, rescinded or superseded | Jul 11, 2008 – Jul 15, 2010 | Oct 21, 2026 | All actions |
| Inspections | 0 | inspections, not findings | — | Oct 21, 2026 | |
| Annual reports | 4 | certified reports (contents not shown) | 2015 – 2018 | 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 (11 records, newest first)
| Date | Record | ID | Type or purpose | Status as published | Detail |
|---|---|---|---|---|---|
| Aug 12, 2019 | Annual reports | 954233 | Annual report 2018 | — | |
| Jul 06, 2018 | Annual reports | 939650 | Annual report 2017 | — | |
| Jun 12, 2017 | Annual reports | 878932 | Annual report 2016 | — | |
| Jul 15, 2016 | Annual reports | 843771 | Annual report 2015 | — | |
| Jul 15, 2010 | Enforcement actions | 403310 | 1st NNC - AR (First Notice of Non-Compliance (annual report)) | Active | |
| Jul 01, 2010 | Violations | 843017 | Late Report | Violation | Report |
| Jul 28, 2009 | Enforcement actions | 369573 | NNC (Notice of Non-Compliance) | Active | |
| Jul 28, 2009 | Violations | 833082 | Late Report | Violation | Report |
| Jul 11, 2008 | Enforcement actions | 356248 | NNC (Notice of Non-Compliance) | Active | |
| Jul 01, 2008 | Violations | 795577 | Late Report | Violation | Report |
| Jul 02, 1999 | Violations | 143459 | Deficient Report | Violation | Inspection |
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.