Welcome to California
California Home
Welcome to California - images of Golden Gate Bridge, ocean sunset, waterfall, flowers, and city skyline California Home Welcome to the California Environmental Protection Agency
California Integrated Water Quality System Project (CIWQS)
   Facility At-A-Glance Report

  
   [VIEW PRINTER FRIENDLY VERSION] [EXPORT THIS REPORT TO EXCEL]

  
   SEARCH CRITERIA:      [REFINE SEARCH] [NEW SEARCH] [GLOSSARY]
Place ID 272960 		  
  
  
  
Hide All Show All
General Information
Region Place ID Place Name Place Type Place Address Place County
5S 272960 Woodland Water Pollution Control Facility Wastewater Treatment Facility 42929 County Road 24 Woodland, CA, 95776 Yolo
Expand/Contract Related Parties
Related Parties
Party Party Type Party Name Role Classification Relationship Start Date Relationship End Date
640353 Person Michael Schultz Is A Data Submitter For 06/30/2023
622683 Person Craig Locke Contact 03/11/2021
594964 Person Melissa Lee Is A Data Submitter For 02/15/2019
594019 Person Teresa Lopez Is A Data Submitter For 01/16/2019 02/02/2024
577868 Person Angela S Clemons Is A Data Submitter For 05/22/2018
541093 Person Shane Carlsen Is Onsite Manager For 11/26/2014
520231 Person Mark Severeid Is A Data Submitter For 10/09/2014 01/16/2019
526984 Person Paul Roy Is Onsite Manager For 05/23/2011 07/01/2013
520229 Person Crystal Whiteleather Is A Data Submitter For 10/14/2009 07/01/2013
520215 Person Mark Hierholzer Is Onsite Manager For 10/14/2009 01/14/2013
51158 Organization Woodland City Owner City Agency 04/19/2005
51158 Organization Woodland City Owner and Operator City Agency 11/14/1996
Total Related Parties: 12
Expand/Contract Regulatory Measures
Regulatory Measures
Reg Measure ID Reg Measure Type Region Program Order No. WDID Effective Date Expiration Date Status Amended?
406725 Enrollee - WDR 5S REC 2016-0068-DDW 5A57NC00046 05/26/2026 Active N
464598 NPDES Permit 5S NPDMUNILRG R5-2026-0004 5A570105001 04/01/2026 03/31/2031 Active N
440459 Co-Permitee SB SLIC 2020-0015-DWQ 5A570105001 07/09/2020 Active N
438341 NPDES Permit 5S NPDMUNILRG R5-2020-0015 5A570105001 06/01/2020 05/31/2025 Historical N
398643 NPDES Permit 5S NPDMUNILRG R5-2014-0120-01 5A570105001 12/01/2014 11/30/2019 Historical Y
362114 NPDES Permit 5S NPDMUNILRG R5-2009-0010 5A570105001 03/27/2009 02/01/2014 Historical N
305260 NPDES Permit 5S NPDMUNILRG R5-2003-0031-R01 5A570105001 09/16/2005 03/30/2008 Historical N
194656 Enrollee 5S NPDNONMUNIPRCS 2004-0009-DWQ 5A57AP00001 05/19/2005 05/19/2009 Historical N
131959 NPDES Permit 5S NPDMUNILRG R5-2003-0031 5A570105001 03/13/2003 09/14/2005 Historical N
131666 NPDES Permit 5S NPDMUNILRG 98-021R1 5A570105001 03/01/2002 03/01/2007 Historical N
146363 NPDES Permit 5S NPDMUNILRG 98-021 5A570105001 01/23/1998 01/30/2003 Historical N
140520 NPDES Permit 5S NPDMUNILRG 92-093 5A570105001 05/29/1992 05/01/1997 Historical N
140935 NPDES Permit 5S NPDMUNILRG 87-093 5A570105001 05/22/1987 05/01/1992 Historical N
139664 NPDES Permit 5S NPDMUNILRG 82-092 5A570105001 07/23/1982 Historical N
Total Reg Measures: 14
Expand/Contract Violations
Violations
Violation ID Occurred Date Violation Type (-) Violation Description Corrective Action Status Classification Source
1157185 07/29/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157202 07/28/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157184 07/26/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157191 07/25/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157190 07/24/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157201 07/19/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157199 07/17/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157198 07/16/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157183 06/27/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157189 06/23/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157188 06/22/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157187 06/21/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157186 06/20/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157200 06/18/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157197 06/15/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157196 06/14/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. e SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157194 06/13/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157195 06/12/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157193 06/11/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1157192 06/10/2026 DMON ¿ The City initiated a SCADA system update in May. Due to this update, a software issue occurred on June 10, 2026 in which the internal tags for new flow variables were lost. As a result, the flow data from 6/10/26 ¿ 6/29/26 for monitoring location LND-002 could not be recovered. A monitoring violation occurred during this period (6/10/26 ¿ 6/29/26) because the City did not meet the minimum continuous monitoring sampling frequency required while discharging to the ponds, as specified in the NPDES Permit (Attachment E, Item VI. A and Table E-4). Once the City identified this error, the City promptly corrected the internal SCADA tags, restoring proper flow monitoring. The SCADA configuration has since been updated to ensure the tags are properly maintained during future system updates, preventing this issue from recurring. Violation U eSMR
1154836 04/02/2026 DMON Total Coliform Daily Discharge limit is 0 MPN/100 mL and reported value was 0 MPN/100 mL at UVS-002. coverage will be verified to insure testing and monitoring is completed on time. Violation B eSMR
1157450 03/31/2026 DMON The Discharger self-reported deficient monitoring under WDRs R5-2020-0015 for total nitrate nitrogen at PND-002, PND-005, PND-007, PND-008, and PND-013 for the First Quarter 2026 reporting period. The Discharger stated that the deficiency occurred due to inaccurate internal record keeping and has prepared new monitoring checklists to avoid repeat violations. The Discharger stated that the deficiency occurred due to inaccurate internal record keeping and has prepared new monitoring checklists to avoid repeat violations. Violation B Report
1147957 06/12/2025 DMON A total coliform result was not reported on 06/12/2025. The Discharger stated the total coliform samples were collected on 06 June 2025 but could not provide results due to a laboratory error. The Discharger has initiated lab analyst retraining on the sample analysis method to prevent a recurrence Violation B eSMR
1147958 06/05/2025 OEV Total Coliform 7-Day Median limit is 2.2 MPN/100 mL and reported value was 7.8 MPN/100 mL at EFF-001. increased cleaning of filters and UV channels and make process adjustment to help resolve the issue Violation B eSMR
1147959 06/04/2025 OEV Total Coliform 7-Day Median limit is 2.2 MPN/100 mL and reported value was 6.8 MPN/100 mL at EFF-001. increased cleaning of UV channels and filters and process changes. Violation B eSMR
1141741 02/26/2025 DMON The Discharger stated the total coliform samples collected on 25 and 26 February 2025 were not properly stored and incubated at the correct temperature. Therefore, the analyses performed on the samples were considered invalid. The Discharger plans to retrain staff and perform a corrective action and root cause analysis to prevent this from happening in the future. retraining and increased monitoring of incubator is recommended in the future, Violation B eSMR
1141740 02/25/2025 DMON The Discharger stated the total coliform samples collected on 25 and 26 February 2025 were not properly stored and incubated at the correct temperature. Therefore, the analyses performed on the samples were considered invalid. retraining and increased monitoring of incubator is recommended in the future. Violation B eSMR
1136780 10/24/2024 DMON Facility staff accidentally disposed of the total coliform sample collected on 24 October 2024. The city will retrain staff and preform a corrective Action and root Cause Analysis to prevent this from happing in the future. Violation B eSMR
1132884 08/09/2024 DMON The Discharger stated the missed total coliform monitoring on 09 August 2024 was due to a power outage that began before the Facility’s laboratory staff arrived in the morning and ended after laboratory staff left for the day. No disinfected effluent/recycled water was available at monitoring location UVS-002 while staff qualified to collect a sample was onsite. Total coliform monitoring results on the day prior to, and after the power loss were within the effluent limitations contained in WDRs. repaired power pole. Violation B eSMR
1125982 04/02/2024 LREP Monthly SMR ( MONNPDES ) report for February 2024 (2346195) was due on 01-APR-24 Violation B Report
1119563 07/01/2023 DMON ¿ The weekly minimum sampling required for effluent BOD (3/week) was not met for the week ending July 1. The City of Woodland collected four effluent composites June 26th through 29th and sent them to a subcontracted lab to be analyzed for BOD, but the subcontracting lab failed to analyze two of the samples within hold time (samples from June 27th and 29th). The City was not notified within the same week and could not resample. The City is working with the subcontracting lab to prevent this from happening again Violation B eSMR
1119360 06/30/2023 DMON The Discharger indicated the deficient monitoring violation for biochemical oxygen demand (BOD) during the week of 25 June 2023 occurred because one of the samples was analyzed out of the allowable hold time. The Discharger is working with the contract laboratory to mitigate the potential for future occurrences of this nature. Violation B Report
1119128 06/28/2023 DMON Nitrate was not included on the COC for this sampling event, They will stop using an old COC to make the new COC so all the field locations and tests will be entered each time, the issue has been documented and they have put measures in place to make sure this does not happen in the future. Violation B eSMR
1116651 05/01/2023 LREP Annual SMR ( TECHRPT ) (Recycled Water Policy Annual Report) report for 2022 (2346328) was due on 30-APR-23 Violation B Report
1115782 02/18/2023 CAT1 Biochemical Oxygen Demand (BOD) (5-day @ 20 Deg. C) Weekly Average limit is 15.0 mg/L and reported value was 16.0 mg/L at EFF-001. Violation B Report
1103470 12/31/2021 DMON Acute Toxicity - The Discharger indicated that quarterly acute toxicity testing is typically coordinated concurrently with routine quarterly toxicity testing. However, there was an oversight in scheduling acute toxicity testing during Fourth Quarter 2021 due to the Toxicity Reduction Evaluation (TRE) monitoring schedule. The Discharger is implementing additional scheduling protocols to prevent similar occurrences in the future Violation B Report
Report displays most recent five years of violations. Refer to the Interactive Violation Report for more data.
Total Violations: 36 Priority Violations: 0
*Click the "(+/-) Violation Description" link to expand and contract the violation description.
*As of 5/20/2010, the Water Board's Enforcement Policy requires that all violations be classified as 1, 2 or 3, with class 1 being the highest. Prior to this, violations were simply classified as Yes or No. If a 123 classification has been assigned to a violation that occurred before this date, that classification data will be displayed instead of the Yes/No data.
Violation Types
CAT1 = Category 1 Pollutant (Effluent Violation for Group 1 Pollutant) DMON = Deficient Monitoring
LREP = Late Report OEV = Other Effluent Violation
Expand/Contract Enforcement Actions
Enforcement Actions
Enf Id Enf Type Enf Order No. Effective Date Status
466025 Notice of Violation null 08/03/2026 Historical
462995 Notice of Violation null 10/17/2025 Historical
461863 Notice of Violation null 07/08/2025 Historical
459748 Notice of Violation null 01/17/2025 Historical
458209 Notice of Violation null 08/23/2024 Historical
456291 Notice of Violation null 03/06/2024 Historical
454323 Notice of Violation null 08/30/2023 Historical
452624 Notice of Violation null 04/23/2023 Historical
447608 Notice of Violation null 04/28/2022 Historical
445591 Admin Civil Liability R5-2021-0529 01/27/2022 Historical
446272 Notice of Violation null 12/14/2021 Historical
444718 Notice of Violation null 07/22/2021 Historical
444405 Notice of Violation null 07/22/2021 Historical
443871 Expedited Payment Letter R5-2021-0513 06/18/2021 Active
442932 Notice of Violation null 02/19/2021 Historical
442890 Notice of Violation null 07/03/2020 Historical
437067 Notice of Violation null 03/02/2020 Historical
434288 Notice of Violation 09/11/2019 Historical
419677 Notice of Violation 02/22/2018 Historical
412834 Notice of Violation 04/18/2017 Historical
409635 Notice of Violation 10/05/2016 Historical
408217 Notice of Violation 07/27/2016 Historical
406323 Notice of Violation 03/18/2016 Historical
402830 Admin Civil Liability R5-2015-0535 10/21/2015 Historical
402505 Notice of Violation 08/13/2015 Historical
401515 Notice of Violation 04/29/2015 Historical
401519 Notice of Violation 04/28/2015 Historical
400043 Notice of Violation 02/25/2015 Historical
397229 Notice of Violation 07/11/2014 Historical
393901 Notice of Violation 11/14/2013 Historical
393002 Notice of Violation 07/30/2013 Historical
390974 Notice of Violation 06/06/2013 Historical
388971 Admin Civil Liability R5-2013-0508 01/11/2013 Historical
388408 Notice of Violation 12/07/2012 Historical
387512 Notice of Violation 09/20/2012 Historical
385992 Notice of Violation 07/05/2012 Historical
384350 Notice of Violation 04/09/2012 Historical
381687 Time Schedule Order R5-2011-0907 09/21/2011 Historical
381335 Notice of Violation 09/06/2011 Historical
379127 Notice of Violation 05/12/2011 Historical
378994 Admin Civil Liability R5-2011-0568 05/06/2011 Historical
378729 Notice of Violation 04/20/2011 Historical
378383 Notice of Violation 03/25/2011 Historical
377991 Notice of Violation 03/08/2011 Historical
377806 Notice of Violation 02/18/2011 Historical
377172 Admin Civil Liability R5-2011-0504 01/07/2011 Historical
377053 Notice of Violation 12/21/2010 Historical
376656 Notice of Violation 11/12/2010 Historical
376277 Notice of Violation 10/13/2010 Historical
376602 Notice of Violation 09/10/2010 Historical
376667 Staff Enforcement Letter 08/17/2010 Historical
373212 Notice of Violation 02/18/2010 Historical
373193 Notice of Violation 01/28/2010 Historical
374740 Notice of Violation 12/16/2009 Historical
367740 Notice of Violation 05/22/2009 Historical
367499 Notice of Violation 05/22/2009 Historical
354929 Admin Civil Liability R5-2008-0604 11/10/2008 Historical
308118 Cease and Desist Order R5-2003-0032-R01 09/16/2005 Historical
256112 Cease and Desist Order R5-2003-0032 03/13/2003 Historical
247554 Oral Communication 09/16/2002 Historical
248826 Notice of Violation 07/02/2002 Historical
231720 Cease and Desist Order R5-1998-0022 01/23/1998 Historical
Total Enf Actions: 62
Expand/Contract Inspections
Inspections
Inspection ID Inspection Type Lead Inspector Actual End Date Planned Violations Attachment
61675995 B Type compliance inspection Paul Wadding 10/07/2025 N 0 Download
56084385 B Type compliance inspection Paul Wadding 05/16/2024 N 0 Download
48694159 Pretreatment compliance Jim Polek (Multiple) 05/05/2022 N 0 Download
46258236 B Type compliance inspection Paul Wadding 12/21/2021 N 0 Download
38810299 B Type compliance inspection Paul Wadding 12/13/2019 N 0 Download
30325451 B Type compliance inspection Ayda Soltani 10/17/2017 Y 0 [Attachments]
25807880 Pretreatment compliance Chuck Durham 12/08/2015 N 0 Download
22407834 B Type compliance inspection Michael A Fischer 10/22/2015 N 0 Download
16563994 Preatment Audit EPA Contractor 02/27/2014 N 0 Download
16655769 Prerequirement inspection David Kirn 12/13/2013 N 0 Download
14440087 B Type compliance inspection Lucio Orellana 11/08/2013 N 0 N/A
12119789 B Type compliance inspection Matthew Reusswig 02/21/2013 N 0 N/A
8564974 B Type compliance inspection Lucio Orellana 05/29/2012 N 0 N/A
8228746 Pretreatment compliance Tetra Tech Inspector 01/25/2012 N 0 N/A
4451107 B Type compliance inspection Luz Slauter 03/28/2011 N 2 Download
2421424 Pretreatment compliance Danny O'Connell 01/13/2010 N 0 Download
1872338 B Type compliance inspection Oscar Biondi 09/02/2009 N 1 N/A
1701725 B Type compliance inspection Scott Slamal 01/20/2009 N 2 Download
1455962 B Type compliance inspection Oscar Biondi 04/18/2008 N 0 [Attachments]
1029238 B Type compliance inspection Karen Bigham (Multiple) 01/17/2007 N 0 [Attachments]
1029291 Pretreatment compliance Tetra Tech 5S-NPDES 09/15/2006 N 0 [Attachments]
336128 Pretreatment compliance Tetra Tech 5S-NPDES 07/22/2004 Y 0 N/A
330733 B Type compliance inspection Kathleen Harder 06/30/2003 Y 0 N/A
324958 A Type compliance inspection Trinh Pham 06/27/2002 Y 0 N/A
321288 B Type compliance inspection Kathleen Harder 05/07/2001 Y 0 N/A
321289 B Type compliance inspection Kathleen Harder 05/16/2000 Y 0 N/A
321284 B Type compliance inspection Richard McHenry 05/05/1999 Y 0 N/A
321285 A Type compliance inspection Richard McHenry 06/15/1998 Y 0 N/A
321287 B Type compliance inspection Richard McHenry 06/30/1997 Y 0 N/A
321286 A Type compliance inspection Richard McHenry 06/25/1996 Y 0 N/A
321280 B Type compliance inspection Richard McHenry 06/27/1995 Y 0 N/A
321283 A Type compliance inspection Richard McHenry 06/09/1994 Y 0 N/A
321282 Prerequirement inspection Richard McHenry 03/09/1994 Y 0 N/A
321281 A Type compliance inspection Richard McHenry 05/11/1993 Y 0 N/A
Total Inspections: 34 Last Inspection: 10/07/2025
  
The current report was generated with data as of: 09/18/2026
Regional Boards are in the process of entering backlogged data.
As a result, data may be incomplete.
Back to Main Page  |  Back to Top of Page

Conditions of Use | Privacy Policy
Copyright © 2024 State of California

The Board is one of six boards, departments, and offices under
the umbrella of the California Environmental Protection Agency.
Cal/EPA | ARB | DPR | DTSC | OEHHA | SWRCB