Trentadue Winery

Active WDID 1 49I014126 Geyserville, Sonoma County Region 1 · North Coast

At a glance

Permit Evidence: SMARTS record
Active Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Geyserville, Sonoma County
Region 1 · North Coast · Location · Statewide map
Receiving water
Russian 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
0 inspections · 9 violation records · 11 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
38.678484, -122.880056
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
19170 Geyserville Ave, Geyserville 95441
Regional Water Board
1 — North Coast

HUC12 watershed Evidence: spatial

  • Sausal Creek-Russian River HUC12 180101100602

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
Leo Trentadue
Primary industry (SIC)
2084-Wines, Brandy, and Brandy Spirits
Application ID
178888
NOI processed
Jun 11, 1998
Last certified
Nov 20, 2023
Facility size
2 Acres
Impervious area
0 %

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
178888 IndustrialActiveJun 11, 1998 —Nov 20, 2023

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

Receiving water

Reported by the facility Evidence: facility-reported
Russian River
Discharges directly / indirectly
N / Y (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

19 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
Russian River HU, Middle Russian River HA, Geyserville HSA CAR1142503219990615082353788 m listed12

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
Violations9 9 Violation · 0 Potential (preliminary) · 0 Dismissed Jul 02, 2002 – Jul 16, 2026 Oct 21, 2026 All violations
Enforcement actions11 11 issued · 0 draft · 0 withdrawn, rescinded or superseded Sep 09, 2002 – Jul 22, 2026 Oct 21, 2026 All actions
Inspections0inspections, not findings — Oct 21, 2026
Annual reports8certified reports (contents not shown) 2015 – 2023 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 (28 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Jul 22, 2026 Enforcement actions 470106 NOV (Notice of Violation) Active
Jul 16, 2026 Violations 904182 Late Report ViolationReport
Sep 10, 2025 Enforcement actions 463258 NOV (Notice of Violation) Active
Aug 08, 2025 Enforcement actions 457288 NOV (Notice of Violation) Active
Jul 15, 2025 Violations 892759 Late Report ViolationReport
Jul 01, 2024 Annual reports 1245365 Annual report 2023 —
Jun 27, 2023 Annual reports 1191471 Annual report 2022 —
Jul 11, 2022 Annual reports 1115037 Annual report 2021 —
Jul 13, 2021 Annual reports 1063129 Annual report 2020 —
Jun 18, 2020 Annual reports 980001 Annual report 2019 —
Jul 12, 2018 Annual reports 956253 Annual report 2018 —
Jul 10, 2017 Annual reports 881078 Annual report 2016 —
Oct 05, 2016 Annual reports 844254 Annual report 2015 —
Aug 14, 2013 Enforcement actions 413694 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 01, 2013 Violations 852235 Late Report ViolationReport
Sep 17, 2012 Enforcement actions 410043 2nd NNC - AR (Second Notice of Non-Compliance (annual report)) Active
Aug 03, 2012 Enforcement actions 409668 1st NNC - AR (First Notice of Non-Compliance (annual report)) Active
Jul 02, 2012 Violations 848662 Late Report ViolationReport
Aug 04, 2010 Enforcement actions 402853 1st NNC - AR (First Notice of Non-Compliance (annual report)) Active
Jul 01, 2010 Violations 842673 Late Report ViolationReport
Aug 01, 2009 Enforcement actions 370126 NNC (Notice of Non-Compliance) Active
Jun 30, 2009 Violations 835299 Late Report ViolationReport
Aug 08, 2008 Enforcement actions 350947 NNC (Notice of Non-Compliance) Active
Jul 01, 2008 Violations 780800 Late Report ViolationReport
Aug 01, 2007 Enforcement actions 343623 SEL (Staff Enforcement Letter) 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.