| Violation ID |
Occurred Date |
Violation Type |
(-) Violation Description |
Corrective Action |
Status |
Classification |
Source |
| 1150129 |
11/14/2025 |
Order Conditions |
Our D.O. Scada systems upgrade had a glitch and lost highest 8-hour avg. data. D.O. was recorded at 0.51. |
New software glitch was fixed. |
Violation |
U |
eSMR |
| 1150135 |
11/13/2025 |
DMON |
Our D.O. Scada systems upgrade had a glitch and lost highest 8-hour avg. data. D.O. was recorded at 0.47. |
IT was called to fix the issue. |
Violation |
U |
eSMR |
| 1150134 |
11/07/2025 |
Order Conditions |
Our D.O. Scada system quit functioning, and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.38 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1150133 |
11/06/2025 |
Order Conditions |
Our D.O. Scada system quit functioning, and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.40 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1150136 |
11/06/2025 |
OEV |
pH Daily Maximum limit is 09.5 SU and reported value was 9.53 SU at EFF-001. |
Team meeting on the importance of good Lab and Sample taking practices. Purchased probe specific cleaner and storage solution. |
Violation |
U |
eSMR |
| 1150131 |
11/05/2025 |
Order Conditions |
Our D.O. Scada system quit functioning and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.40 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1150130 |
11/04/2025 |
Order Conditions |
Our D.O. Scada system quit functioning and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.35 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1150132 |
11/01/2025 |
Order Conditions |
Our D.O. Scada system quit functioning, and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.96 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1149611 |
10/31/2025 |
DMON |
Our D.O. Scada system quit functioning and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.87 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November.
|
Violation |
U |
eSMR |
| 1149610 |
10/16/2025 |
DMON |
Our D.O. Scada system quit functioning and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.98 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1149609 |
10/14/2025 |
DMON |
Our D.O. Scada system quit functioning and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.90 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1149607 |
10/13/2025 |
DMON |
Our D.O. Scada system quit functioning and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.75 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1149608 |
10/12/2025 |
DMON |
Our D.O. Scada system quit functioning and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.08 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1149606 |
10/02/2025 |
DMON |
Our D.O. Scada system quit functioning and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.62 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1149605 |
10/01/2025 |
Order Conditions |
Our D.O. Scada system quit functioning and we lost the ability to digitally collect DO. readings around the clock. The reading was only taken once per day and recorded at 0.34 which was the real time result for that moment. It did not reflect the highest 8 hours of the day. |
We had to develop a new software to collect the data around the clock that wasn't completed until the 1st part of November. |
Violation |
U |
eSMR |
| 1146498 |
07/30/2025 |
DMON |
Methylene Chloride sample from July 30th was not tested at the lab due to an issue with the preservation of the sample. We received notification from the lab on August 15th and then resampled after receiving new preservation containers on August 20th. The late pull for the July sample was due to not discharging for most of July. |
Ensure we take our Monthly samples on the first sample day of the month to allow for potential needs for resampling.
Robert Pacheco will be working with the lab to ensure we have more timely communication when a sample does not meet a requirement to allow time for resampling when necessary. We will also have a refresher training on the proper sampling techniques for Methylene Chloride. |
Violation |
U |
eSMR |
| 1142063 |
02/28/2025 |
CAT2 |
Copper, Total Recoverable Monthly Average limit is 16 ug/L and reported value was 29.4 ug/L at EFF-001. |
|
Violation |
B |
Report |
| 1142064 |
02/28/2025 |
CAT2 |
Zinc, Total Recoverable Monthly Average limit is 67 ug/L and reported value was 87 ug/L at EFF-001. |
|
Violation |
B |
Report |
| 1140354 |
02/02/2025 |
DMON |
Discharger did not conduct receiving water sampling due to the boat launch ramp being flooded, therefore they could not access the monitoring location. |
|
Violation |
B |
Report |
| 1140355 |
01/02/2025 |
DMON |
No RW monitoring conducted the week of 11/24 due to boat ramp being flooded |
|
Violation |
B |
Report |
| 1135410 |
09/30/2024 |
Order Conditions |
Violation of Treatment Pont Operating Requirements: Maintain the dissolved oxygen (DO) content in the upper one foot of any wastewater treatment or storage pond at or above 1.0 mg/L. On 9/1 and 9/2 DO in pond 001 was reported at 0.95 mg/L |
|
Violation |
B |
Report |
| 1135406 |
08/31/2024 |
Order Conditions |
Violation of Treatment Pont Operating Requirements: Maintain the dissolved oxygen (DO) content in the upper one foot of any wastewater treatment or storage pond at or above 1.0 mg/L. On 8/29, 8/30, and 8/31 DO in pond 001 was reported at 0.95 mg/L |
|
Violation |
B |
Report |
| 1128617 |
05/31/2024 |
LREP |
Once Only OneTime ( MONNPDES ) (ROWD) report for 2024/01/01 (2483881) was due on 30-MAY-24 |
|
Violation |
B |
Report |
| 1113954 |
01/12/2023 |
Order Conditions |
During the month of January, we experienced an excessive amount of rainfall. In order to not reach our pond freeboard limits, we ceased operation at our manufacturing facility, and discharged >50 GPM. We monitored / documented / reported the river conditions daily. During this time, we did not exceed any of our permitted effluent limits. and we notified your office prior to the change in operation. |
Ceased operation at the manufacturing facility, and increased the effluent to >50GPM, until pond levels were within acceptable levels. |
Violation |
B |
eSMR |
| 1109521 |
09/30/2022 |
DMON |
Deficient monitoring of DO in PND-001, PND-002, and PND-003. Per cover letter, Discharger reports that daily DO for 9/13 through 9/20 was not automatically logged. In the past, they were able to retrieve the data, but have been unsuccessful in these attempts. per Discharger "In the future, if this were to reoccur, we will log the D.O. readings manually." |
|
Violation |
B |
Report |
| 1101003 |
11/19/2021 |
Order Conditions |
Pond 1 DO reported under 1 mg/L (0.85), which violates Construction, Operation, and Maintenance Specifications Section VI.C.4.c.iv.a |
|
Violation |
B |
Report |
| 1101002 |
11/12/2021 |
Order Conditions |
Pond 1 DO reported under 1 mg/L (0.81), which violates Construction, Operation, and Maintenance Specifications Section VI.C.4.c.iv.a |
|
Violation |
B |
Report |
| 1101001 |
11/05/2021 |
Order Conditions |
Pond 1 DO reported under 1 mg/L (0.59), which violates Construction, Operation, and Maintenance Specifications Section VI.C.4.c.iv.a |
|
Violation |
B |
Report |
| 1093696 |
07/07/2021 |
DMON |
On 07/07/21 Samples were taken in the Sacramento river (RSW1 & RSW 2) An error was made on the chain of custody document (box not checked) resulting in the sample for RSW2 has no TDS results, The TDS was measured, analyzed and reported for RSW1. |
We have reviewed with our team to be more thorough when completing the chain of custody documentation. |
Violation |
U |
eSMR |
|
Report displays most recent five years of violations. Refer to the Interactive Violation Report for more data.
|