Castoro Cellars

Active WDID 3 40I014451 San Miguel, San Luis Obispo 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
San Miguel, San Luis Obispo County
Region 3 · Central Coast · Location · Statewide map
Receiving water
Estrella River (as reported by the facility)
Evidence: identification corroborated Estrella River Details
Identified receiving water on the 2026 303(d) list
Yes · 7 Appendix A decisions, category 5 Evidence: State-published
Describes the waterbody, not this facility · Waterbody profile
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
0 inspections · 3 violation records · 2 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
35.73234, -120.5886
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
6465 Von Dollen Rd, San Miguel 93451
Regional Water Board
3 — Central Coast

HUC12 watershed Evidence: spatial

  • Town of Estrella-Estrella River HUC12 180600040410

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
Niels Udsen
Primary industry (SIC)
2084-Wines, Brandy, and Brandy Spirits
Application ID
185737
NOI processed
Aug 03, 1998
Last certified
Jan 16, 2023
Facility size
87 Acres
Impervious area
100 %

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
185737 IndustrialActiveAug 03, 1998 —Jan 16, 2023

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

Receiving water

Reported by the facility Evidence: facility-reported
Estrella River
Discharges directly / indirectly
N / Y (as answered in the permit application)

Evidence: identification corroborated Estrella River CAR3170007119990225125807

Receiving water reported by facility — waterbody identification corroborated by geographic evidence.

Nearest distance from the reported facility location: 3.5 km. Method receiving_water/2.

2026 Integrated Report status Evidence: State-published

Estrella River is on the 2026 Clean Water Act section 303(d) list (7 Appendix A decisions; category 5).

2026 Appendix A decisions for the identified receiving water
PollutantCategoryListing decisionTMDL requirementDecision ID
Boron5Do Not Delist from 303(d) list (being addressed with USEPA approved TMDL) 5B · Estrella River Basin Boron TMDL111068
Chloride5Do Not Delist from 303(d) list (TMDL required list) 5A111069
Escherichia coli (E. coli)5List on 303(d) list (TMDL required list) 5A125762
pH5Do Not Delist from 303(d) list (TMDL required list) 5A111074
Sodium5Do Not Delist from 303(d) list (TMDL required list) 5A111075
Toxicity5List on 303(d) list (TMDL required list) 5A91152
Turbidity5Do Not Delist from 303(d) list (TMDL required list) 5A111077

Published by the State Water Resources Control Board (2026 California Integrated Report, Appendix A). Listing status is taken from Appendix A only. State Board adoption 2026-02-03; USEPA approval not confirmed. A listing describes the waterbody, not this facility. Waterbody profile.

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.

Compliance and enforcement records by type
Record typeRecordsAs publishedDatesRetrievedList
Violations3 2 Violation · 0 Potential (preliminary) · 1 Dismissed Jul 02, 1999 – Aug 15, 2015 Oct 21, 2026 All violations
Enforcement actions2 2 issued · 0 draft · 0 withdrawn, rescinded or superseded Jul 11, 2008 – Nov 20, 2015 Oct 21, 2026 All actions
Inspections0inspections, not findings — Oct 21, 2026
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 (16 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Jul 15, 2026 Annual reports 1335928 Annual report 2025 —
Jul 16, 2025 Annual reports 1294765 Annual report 2024 —
Jul 16, 2024 Annual reports 1243878 Annual report 2023 —
Aug 21, 2023 Annual reports 1189909 Annual report 2022 —
Feb 02, 2023 Annual reports 1113331 Annual report 2021 —
Oct 26, 2021 Annual reports 1069370 Annual report 2020 —
Jul 24, 2020 Annual reports 986682 Annual report 2019 —
Jul 16, 2019 Annual reports 954263 Annual report 2018 —
Jul 16, 2018 Annual reports 939681 Annual report 2017 —
Jul 17, 2017 Annual reports 878964 Annual report 2016 —
Jul 18, 2016 Annual reports 842712 Annual report 2015 —
Nov 20, 2015 Enforcement actions 421615 NNC (Notice of Non-Compliance) Active
Aug 15, 2015 Violations 859276 Failure to Obtain Permit DismissedReport
Jul 11, 2008 Enforcement actions 356432 NNC (Notice of Non-Compliance) Active
Jul 01, 2008 Violations 797309 Late Report ViolationReport
Jul 02, 1999 Violations 143536 Deficient Report ViolationInspection

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.