 |
| |
Party At-A-Glance Report |
|
| |
[VIEW PRINTER FRIENDLY VERSION]
[EXPORT THIS REPORT TO EXCEL]
|
|
| |
|
|
| |
| |
| General Information |
|
| Party ID |
Party Name |
Party Classification |
Mailing Address |
Work Phone |
Email/Website |
| 51158 |
Woodland City |
City Agency |
655 North Pioneer Avenue Woodland, CA 95776 |
530-661-5983 |
None |
|
|
| |
|
|
| |
Related Places
|
|
|
|
Total Related Places: 6
|
|
|
| |
|
|
| |
Related Parties
|
| Party ID |
Party Name |
Party Type |
Role/Relationship |
Relationship Start Date |
Relationship End Date |
Classification |
| 653641 |
Kevin Eagle |
Person |
Data Submitter |
01/05/2026 |
None |
None |
| 652476 |
Matthew Cohen |
Person |
Data Submitter |
09/17/2025 |
None |
None |
| 640353 |
Michael Schultz |
Person |
Data Submitter |
06/30/2023 |
None |
None |
| 622683 |
Craig Locke |
Person |
Legally Responsible Official |
09/24/2025 |
None |
None |
| 594964 |
Melissa Lee |
Person |
Data Submitter |
02/15/2019 |
None |
None |
| 594019 |
Teresa Lopez |
Person |
Data Submitter |
01/16/2019 |
02/02/2024 |
None |
| 577868 |
Angela Clemons |
Person |
Data Submitter |
05/22/2018 |
None |
None |
| 555095 |
Andrew Cital |
Person |
Data Submitter |
03/11/2016 |
02/13/2017 |
None |
| 549348 |
Tim Busch |
Person |
Legally Responsible Official |
09/24/2025 |
None |
None |
| 549140 |
Greg Meyer |
Person |
Legally Responsible Official |
10/09/2014 |
None |
None |
| 541622 |
Alex Truitt |
Person |
Data Submitter |
07/03/2013 |
04/06/2016 |
None |
| 541622 |
Alex Truitt |
Person |
Legally Responsible Official |
04/06/2016 |
None |
None |
| 541093 |
Shane Carlsen |
Person |
Legally Responsible Official |
06/24/2013 |
None |
None |
| 526984 |
Paul Roy |
Person |
Legally Responsible Official |
05/23/2011 |
07/23/2013 |
None |
| 522303 |
Tim Lloyd |
Person |
Legally Responsible Official |
05/05/2010 |
03/17/2016 |
None |
| 522086 |
Eric Medrano |
Person |
Legally Responsible Official |
04/17/2017 |
None |
None |
| 522086 |
Eric Medrano |
Person |
Data Submitter |
04/19/2010 |
04/17/2017 |
None |
| 520713 |
Robert Galindo |
Person |
Legally Responsible Official |
01/04/2010 |
05/21/2013 |
None |
| 520571 |
Mark Clifton |
Person |
Data Submitter |
12/07/2009 |
None |
None |
| 520231 |
Mark Severeid |
Person |
Data Submitter |
03/16/2006 |
10/13/2009 |
None |
| 520231 |
Mark Severeid |
Person |
Data Submitter |
10/14/2009 |
None |
None |
| 390750 |
David Settles |
Person |
Data Submitter |
07/27/2007 |
None |
None |
| 390744 |
Chris Mosier |
Person |
Data Submitter |
07/27/2007 |
None |
None |
| 390684 |
Vince Ayon |
Person |
Legally Responsible Official |
07/27/2007 |
None |
None |
| 390679 |
Deanna Huntley |
Person |
Data Submitter |
07/27/2007 |
None |
None |
| 300348 |
Cathy Lee |
Person |
Legally Responsible Official |
04/03/2006 |
None |
None |
| 143841 |
Craig Powell |
Person |
Enforcement Contact |
09/05/2003 |
None |
None |
| 64820 |
Roy Wilson |
Person |
Legally Responsible Official |
04/03/2006 |
None |
None |
| 64820 |
Roy Wilson |
Person |
Legal representative |
11/14/1996 |
04/02/2006 |
None |
|
|
Total Related Parties: 29
|
|
|
| |
|
|
| |
Regulatory Measures (non-enforcement)
|
| Reg. Measure ID |
Regulatory Measure Type |
Region |
WDID |
Status |
Program |
Order No. |
RM Effective Date |
RM Termination Date |
Relationship |
Relationship Start Date |
Relationship End Date |
Amended? |
| 464598 |
NPDES Permit |
5S |
5A570105001 |
Active |
NPDMUNILRG |
R5-2026-0004 |
04/01/2026 |
None |
Discharger |
02/27/2026 |
None |
N |
| 440459 |
Co-Permitee |
SB |
5A570105001 |
Active |
SLIC |
2020-0015-DWQ |
07/09/2020 |
None |
Discharger |
09/18/2020 |
None |
N |
| 438341 |
NPDES Permit |
5S |
5A570105001 |
Historical |
NPDMUNILRG |
R5-2020-0015 |
06/01/2020 |
03/31/2026 |
Discharger |
06/01/2020 |
None |
N |
| 406725 |
Enrollee - WDR |
5S |
5A57NC00046 |
Active |
REC |
2016-0068-DDW |
05/26/2026 |
None |
Discharger |
06/08/2016 |
None |
N |
| 398643 |
NPDES Permit |
5S |
5A570105001 |
Historical |
NPDMUNILRG |
R5-2014-0120-01 |
12/01/2014 |
05/31/2020 |
Discharger |
10/09/2014 |
None |
Y |
| 301277 |
Enrollee - WDR |
5S |
5SSO10903 |
Active |
SSOMUNILRG |
2022-0103-DWQ |
05/29/2007 |
None |
Discharger |
04/18/2006 |
None |
N |
| 194656 |
Enrollee |
5S |
5A57AP00001 |
Historical |
NPDNONMUNIPRCS |
2004-0009-DWQ |
05/19/2005 |
01/29/2010 |
Discharger |
09/01/2005 |
None |
N |
| 194661 |
Enrollee |
5S |
5A57NC00015 |
Historical |
WDR |
R5-2003-0008 |
08/27/2004 |
01/31/2008 |
Discharger |
09/01/2005 |
None |
N |
| 172151 |
Enrollee |
5S |
5A57NP00017 |
Historical |
MNSTW2 |
2003-0005-DWQ |
10/24/2004 |
06/30/2013 |
Discharger |
06/17/2005 |
None |
N |
| 131959 |
NPDES Permit |
5S |
5A570105001 |
Historical |
NPDMUNILRG |
R5-2003-0031 |
03/13/2003 |
09/14/2005 |
Discharger |
03/13/2003 |
None |
N |
| 362114 |
NPDES Permit |
5S |
5A570105001 |
Historical |
NPDMUNILRG |
R5-2009-0010 |
03/27/2009 |
11/30/2014 |
Discharger |
03/13/2003 |
None |
N |
| 305260 |
NPDES Permit |
5S |
5A570105001 |
Historical |
NPDMUNILRG |
R5-2003-0031-R01 |
09/16/2005 |
03/26/2009 |
Discharger |
03/13/2003 |
None |
N |
| 131502 |
WDR |
5S |
5A570105002 |
Historical |
WDRINDFP |
02-122 |
06/07/2002 |
05/30/2018 |
Discharger |
06/07/2002 |
None |
N |
| 131666 |
NPDES Permit |
5S |
5A570105001 |
Historical |
NPDMUNILRG |
98-021R1 |
03/01/2002 |
03/12/2003 |
Discharger |
03/01/2002 |
None |
N |
| 146363 |
NPDES Permit |
5S |
5A570105001 |
Historical |
NPDMUNILRG |
98-021 |
01/23/1998 |
02/28/2002 |
Discharger |
01/23/1998 |
None |
N |
| 140520 |
NPDES Permit |
5S |
5A570105001 |
Historical |
NPDMUNILRG |
92-093 |
05/29/1992 |
01/22/1998 |
Discharger |
05/29/1992 |
None |
N |
| 140392 |
WDR |
5S |
5A570105002 |
Historical |
WDR |
90-077 |
03/23/1990 |
06/06/2002 |
Discharger |
03/23/1990 |
None |
Y |
| 140935 |
NPDES Permit |
5S |
5A570105001 |
Historical |
NPDMUNILRG |
87-093 |
05/22/1987 |
05/28/1992 |
Discharger |
05/22/1987 |
None |
N |
| 139664 |
NPDES Permit |
5S |
5A570105001 |
Historical |
NPDMUNILRG |
82-092 |
07/23/1982 |
05/21/1987 |
Discharger |
07/23/1982 |
None |
N |
| 139480 |
WDR |
5S |
5A570105002 |
Historical |
WDR |
81-013 |
01/23/1981 |
12/31/1989 |
Discharger |
01/23/1981 |
None |
N |
|
|
Total Regulatory Measures: 20
|
|
|
| |
|
|
| |
Violations within the past year
|
| Violation ID |
Occurrence Date |
Violation Type |
Violation Description(-) |
Violation Status |
Priority |
Source |
Facility Name |
Violated Reg. Meas. ID |
Violated Reg. Meas. Order No. |
Linked to Enf. |
| 1157450 |
03/31/2026 |
Deficient Monitoring |
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. |
Violation |
N |
Report |
Woodland Water Pollution Control Facility |
438341 |
R5-2020-0015 |
Y |
| 1157202 |
07/28/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157201 |
07/19/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157200 |
06/18/2026 |
Deficient Monitoring |
¿ 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. |
Violation |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157199 |
07/17/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157198 |
07/16/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157197 |
06/15/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157196 |
06/14/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157195 |
06/12/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157194 |
06/13/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157193 |
06/11/2026 |
Deficient Monitoring |
¿ 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. |
Violation |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157192 |
06/10/2026 |
Deficient Monitoring |
¿ 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. |
Violation |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157191 |
07/25/2026 |
Deficient Monitoring |
¿ 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. |
Violation |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157190 |
07/24/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157189 |
06/23/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157188 |
06/22/2026 |
Deficient Monitoring |
¿ 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. |
Violation |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157187 |
06/21/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157186 |
06/20/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157185 |
07/29/2026 |
Deficient Monitoring |
¿ 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. |
Violation |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157184 |
07/26/2026 |
Deficient Monitoring |
¿ 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 |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1157183 |
06/27/2026 |
Deficient Monitoring |
¿ 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. |
Violation |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
N |
| 1154836 |
04/02/2026 |
Deficient Monitoring |
Total Coliform Daily Discharge limit is 0 MPN/100 mL and reported value was 0 MPN/100 mL at UVS-002. |
Violation |
N |
eSMR |
Woodland Water Pollution Control Facility |
464598 |
R5-2026-0004 |
Y |
|
Report defaults to display violations within the last year. Click here to see last five years of violations. Refer to the Interactive Violation Report for more data.
|
|
|
Total Violations: 22
|
|
*Click the "(+/-) Violation Description" link to expand and contract the violation description.
|
|
|
| |
|
|
| |
Enforcement Actions
|
| Enforcement ID |
Enforcement Type |
Enf. Order No. |
Title |
Program |
Effective Date |
Status |
| 466025 |
Notice of Violation |
None |
NOV 08/03/2026 for Woodland City |
NPDMUNILRG |
08/03/2026 |
Historical |
| 462995 |
Notice of Violation |
None |
NOV 10/17/2025 for Woodland City |
NPDMUNILRG |
10/17/2025 |
Historical |
| 461863 |
Notice of Violation |
None |
NOV 07/08/2025 for Woodland City |
NPDMUNILRG |
07/08/2025 |
Historical |
| 459748 |
Notice of Violation |
None |
NOV 01/17/2025 for Woodland City |
NPDMUNILRG |
01/17/2025 |
Historical |
| 458209 |
Notice of Violation |
None |
NOV 08/23/2024 for Woodland City |
NPDMUNILRG |
08/23/2024 |
Historical |
| 456291 |
Notice of Violation |
None |
NOV 03/06/2024 for Woodland City |
NPDMUNILRG |
03/06/2024 |
Historical |
| 454323 |
Notice of Violation |
None |
NOV 08/30/2023 for Woodland City |
NPDMUNILRG |
08/30/2023 |
Historical |
| 452624 |
Notice of Violation |
None |
NOV 04/23/2023 for Woodland City |
NPDMUNILRG |
04/23/2023 |
Historical |
| 447608 |
Notice of Violation |
None |
NOV 04/28/2022 for Woodland City |
NPDMUNILRG |
04/28/2022 |
Historical |
| 446272 |
Notice of Violation |
None |
NOV 12/14/2021 for Woodland City |
NPDMUNILRG |
12/14/2021 |
Historical |
| 445591 |
Admin Civil Liability |
R5-2021-0529 |
ACL R5-2021-0529 for Woodland City |
NPDMUNILRG |
01/27/2022 |
Historical |
| 444718 |
Notice of Violation |
None |
NOV 07/22/2021 for Woodland City |
NPDMUNILRG |
07/22/2021 |
Historical |
| 444405 |
Notice of Violation |
None |
NOV 07/22/2021 for Woodland City |
NPDMUNILRG |
07/22/2021 |
Historical |
| 443871 |
Expedited Payment Letter |
R5-2021-0513 |
EPL R5-2021-0513 for Woodland City |
NPDMUNILRG |
06/18/2021 |
Active |
| 442932 |
Notice of Violation |
None |
NOV 02/19/2021 for Woodland City |
NPDMUNILRG |
02/19/2021 |
Historical |
| 442890 |
Notice of Violation |
None |
NOV 07/03/2020 for Woodland City |
NPDMUNILRG |
07/03/2020 |
Historical |
| 437067 |
Notice of Violation |
None |
NOV 03/02/2020 for Woodland City |
NPDMUNILRG |
03/02/2020 |
Historical |
| 434288 |
Notice of Violation |
None |
NOV 09/11/2019 for Woodland City |
NPDMUNILRG |
09/11/2019 |
Historical |
| 419677 |
Notice of Violation |
None |
NOV 02/22/2018 for Woodland City |
NPDMUNILRG |
02/22/2018 |
Historical |
| 412834 |
Notice of Violation |
None |
NOV 04/18/2017 for Woodland City |
NPDMUNILRG |
04/18/2017 |
Historical |
| 409714 |
Notice of Violation |
None |
NOV 09/27/2016 for Woodland City |
WDRINDFP |
09/27/2016 |
Historical |
| 409635 |
Notice of Violation |
None |
NOV 10/05/2016 for Woodland City |
NPDMUNILRG |
10/05/2016 |
Historical |
| 408217 |
Notice of Violation |
None |
NOV 07/27/2016 for Woodland City |
NPDMUNILRG |
07/27/2016 |
Historical |
| 406323 |
Notice of Violation |
None |
NOV 03/18/2016 for Woodland City |
NPDMUNILRG |
03/18/2016 |
Historical |
| 402830 |
Admin Civil Liability |
R5-2015-0535 |
ACL R5-2015-0535 for Woodland City |
NPDMUNILRG |
10/21/2015 |
Historical |
| 402505 |
Notice of Violation |
None |
NOV 08/13/2015 for Woodland City |
NPDMUNILRG |
08/13/2015 |
Historical |
| 401519 |
Notice of Violation |
None |
NOV 04/28/2015 for Woodland City |
NPDMUNILRG |
04/28/2015 |
Historical |
| 401515 |
Notice of Violation |
None |
NOV 04/29/2015 for Woodland City |
NPDMUNILRG |
04/29/2015 |
Historical |
| 400043 |
Notice of Violation |
None |
NOV 02/25/2015 for Woodland City |
NPDMUNILRG |
02/25/2015 |
Historical |
| 397229 |
Notice of Violation |
None |
NOV 07/11/2014 for Woodland City |
NPDMUNILRG |
07/11/2014 |
Historical |
| 396764 |
Notice of Violation |
None |
NOV 06/12/2014 for Woodland City, City of Woodland CS |
SSOMUNILRG |
06/12/2014 |
Historical |
| 393901 |
Notice of Violation |
None |
NOV 11/14/2013 for Woodland City |
NPDMUNILRG |
11/14/2013 |
Historical |
| 393002 |
Notice of Violation |
None |
NOV 07/30/2013 for Woodland City |
NPDMUNILRG |
07/30/2013 |
Historical |
| 390974 |
Notice of Violation |
None |
NOV 06/06/2013 for Woodland City WPCF |
NPDMUNILRG |
06/06/2013 |
Historical |
| 388971 |
Admin Civil Liability |
R5-2013-0508 |
ACL R5-2013-0508 for Woodland City |
NPDMUNILRG |
01/11/2013 |
Historical |
| 388408 |
Notice of Violation |
None |
NOV 12/07/2012 for Woodland City WPCF |
NPDMUNILRG |
12/07/2012 |
Historical |
| 387512 |
Notice of Violation |
None |
NOV 09/20/2012 for Woodland City WPCF |
NPDMUNILRG |
09/20/2012 |
Historical |
| 385992 |
Notice of Violation |
None |
NOV 07/05/2012 for Woodland City WPCF |
NPDMUNILRG |
07/05/2012 |
Historical |
| 384350 |
Notice of Violation |
None |
NOV 04/09/2012 for Woodland City WPCF |
NPDMUNILRG |
04/09/2012 |
Historical |
| 381687 |
Time Schedule Order |
R5-2011-0907 |
TSO R5-2011-0907-01 for Woodland City, Water Pollution Control Facility |
NPDMUNILRG |
09/21/2011 |
Historical |
| 381335 |
Notice of Violation |
None |
NOV 09/06/2011 for Woodland City WPCF |
NPDMUNILRG |
09/06/2011 |
Historical |
| 379127 |
Notice of Violation |
None |
NOV 05/12/2011 for Woodland City WPCF |
NPDMUNILRG |
05/12/2011 |
Historical |
| 378994 |
Admin Civil Liability |
R5-2011-0568 |
MMPC R5-2011-0568 for Woodland City, Water Pollution Control Facility |
NPDMUNILRG |
05/06/2011 |
Historical |
| 378729 |
Notice of Violation |
None |
NOV 04/20/2011 for Woodland City WPCF |
NPDMUNILRG |
04/20/2011 |
Historical |
| 378383 |
Notice of Violation |
None |
NOV 03/25/2011 for Woodland City WPCF |
NPDMUNILRG |
03/25/2011 |
Historical |
| 377991 |
Notice of Violation |
None |
NOV 03/08/2011 for Woodland City WPCF |
NPDMUNILRG |
03/08/2011 |
Historical |
| 377806 |
Notice of Violation |
None |
NOV 02/18/2011 for Woodland City WPCF |
NPDMUNILRG |
02/18/2011 |
Historical |
| 377172 |
Admin Civil Liability |
R5-2011-0504 |
MMPC R5-2011-0504 for Woodland City, Woodland Water Pollution Control Facility |
NPDMUNILRG |
01/07/2011 |
Historical |
| 377053 |
Notice of Violation |
None |
NOV 12/21/2010 for Woodland City WPCF |
NPDMUNILRG |
12/21/2010 |
Historical |
| 376667 |
Staff Enforcement Letter |
None |
SEL 08/17/2010 for Woodland City WPCF |
NPDESWW |
08/17/2010 |
Historical |
| 376656 |
Notice of Violation |
None |
NOV 11/12/2010 for Woodland City WWTP |
NPDMUNILRG |
11/12/2010 |
Historical |
| 376602 |
Notice of Violation |
None |
NOV 09/10/2010 for Woodland City WPCF |
NPDMUNILRG |
09/10/2010 |
Historical |
| 376277 |
Notice of Violation |
None |
NOV 10/13/2010 for Woodland City WPCF |
NPDMUNILRG |
10/13/2010 |
Historical |
| 374740 |
Notice of Violation |
None |
NOV 12/16/2009 for Woodland City, Water Pollution Control Facility |
NPDMUNILRG |
12/16/2009 |
Historical |
| 373212 |
Notice of Violation |
None |
NOV 02/18/2010 for Woodland City, Woodland Water Pollution Control Facility |
NPDMUNILRG |
02/18/2010 |
Historical |
| 373193 |
Notice of Violation |
None |
NOV 01/28/2010 for Woodland City, Woodland Water Pollution Control Facility |
NPDMUNILRG |
01/28/2010 |
Historical |
| 367740 |
Notice of Violation |
None |
NOV 05/22/2009 for Woodland City, Woodland Water Pollution Control Facility |
NPDMUNILRG |
05/22/2009 |
Historical |
| 367499 |
Notice of Violation |
None |
NOV 05/22/2009 for Woodland City, Woodland Water Pollution Control Facility |
NPDMUNILRG |
05/22/2009 |
Historical |
| 354929 |
Admin Civil Liability |
R5-2008-0604 |
MMPC R5-2008-0604 for Woodland City, Woodland Water Pollution Control Facility |
NPDMUNILRG |
11/10/2008 |
Historical |
| 317799 |
Notice of Violation |
None |
NOV 12/21/2006 for Woodland City, Pacific Coast Producers |
WDR |
12/21/2006 |
Historical |
| 308118 |
Cease and Desist Order |
R5-2003-0032-R01 |
CDO R5-2003-0032-R01 for Woodland City |
NPDMUNILRG |
09/16/2005 |
Historical |
| 256112 |
Cease and Desist Order |
R5-2003-0032 |
CDO R5-2003-0032 for Woodland City |
NPDMUNILRG |
03/13/2003 |
Historical |
| 250447 |
13267 Letter |
None |
13267 Letter 02/09/2004 for PACIFIC COAST PRODUCERS |
WDR |
02/09/2004 |
Historical |
| 248826 |
Notice of Violation |
None |
NOV 07/02/2002 for Woodland City, Woodland Water Pollution Control Facility |
NPDMUNILRG |
07/02/2002 |
Historical |
| 247554 |
Oral Communication |
None |
Enforcement - 5A570105001 |
NPDMUNILRG |
09/16/2002 |
Historical |
| 242228 |
Notice of Violation |
None |
NOV 09/05/2003 for Woodland City, PACIFIC COAST PRODUCERS |
WDR |
09/05/2003 |
Historical |
| 231720 |
Cease and Desist Order |
R5-1998-0022 |
CDO R5-1998-0022 for Woodland City |
NPDMUNILRG |
01/23/1998 |
Historical |
| 224107 |
Cease and Desist Order |
R5-1987-0096 |
CDO R5-1987-0096 for Woodland City, Pacific Coast Producers |
WDR |
05/22/1987 |
Historical |
| 223687 |
Cease and Desist Order |
R5-1991-0180 |
CDO R5-1991-0180 for Woodland City, Pacific Coast Producers |
WDR |
09/06/1991 |
Historical |
|
|
Total Enforcement Actions: 69
|
|
|
| |
|
|
| |
Regulatory Measures linked to Related Parties
|
|
|
|
Total Regulatory Measures linked to Related Parties: 0
|
|
|
|
|
|
 |
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
|
|
|
|
|
|