Filter Effluent Turbidity Excursion After Backwash
A conventional plant with four dual-media filters is running at 4.0 MGD against a design of 4.8 MGD. Filter 3 was backwashed at 06:00 and returned to service. At 06:20 the combined filter effluent turbidity rose from 0.08 NTU to 0.35 NTU, then settled at 0.18 NTU by 07:00. Individual filter effluent for Filter 3 was 0.9 NTU at 06:15 and 0.25 NTU at 06:45. The plant's state rule requires combined filter effluent below 0.3 NTU in 95 percent of monthly measurements and individual filter effluent below 1.0 NTU, with a filter-to-waste or slow-start option available but not currently used. The operator is also watching a rising headloss trend on Filter 1.
1. Assess whether this event is a compliance concern and what the operator should investigate.
Read the worked answer
The combined effluent briefly exceeded 0.3 NTU, and Filter 3 individual effluent was near the 1.0 NTU limit at 06:15. Whether this is a violation depends on the state's measurement frequency and averaging rules, but it is clearly an excursion that must be documented and investigated. The operator should check backwash effectiveness (bed expansion, backwash rate, duration, air scour if present), filter ripening behavior, media condition (loss, mudballs, cracking), and whether the filter was returned to service too quickly. The rising headloss on Filter 1 suggests a separate loading or media issue that should be evaluated before it affects effluent quality.
2. Should the operator begin using filter-to-waste or slow-start? Explain the reasoning.
Read the worked answer
Yes, the plant has the option and the excursion occurred during the ripening period, which is exactly when filter-to-waste or a slow-start ramp is most effective. Returning a freshly backwashed filter directly to service at full rate sends the initial turbidity spike to the clearwell. Using filter-to-waste until effluent turbidity stabilizes, or ramping flow gradually, would have kept the spike out of the combined effluent. The operator should implement the practice, document the change, and verify that the spike is controlled on subsequent backwashes.
3. What should be done about Filter 1's rising headloss?
Read the worked answer
Rising headloss can indicate media clogging, inadequate backwash, surface loading, or changes in upstream coagulation. The operator should review Filter 1's backwash records, check for media loss or mudballs, verify upstream settled turbidity, and compare its loading rate to the other filters. If headloss continues to rise, the filter may need a more thorough backwash or media evaluation. This should be handled before it forces a shortened run or a turbidity breakthrough.