Violations and Permit Triggers

Use this report to view violations and permit triggers. These include benchmark and limit exceedances on monitoring data, late permit submittals and other violations noted during an inspection. Click the "More Info" link to view more information about the violation/trigger including any related enforcement actions.

In Addition to Dates Please Also Fill in one or more fields and click Search

Example: WAR0011379 or 11379
Look Up Permit Types
Use Region Map

This report includes both permit violations and permit triggers. Permit triggers are not violations but rather when triggered require the permit holder to take an action defined in the permit. Benchmark exceedances and design criteria (85%) exceedances are permit triggers and not permit violations.

If the “is addressed” column in this report states “yes” then Ecology has taken an informal or formal action to address the violation or permit trigger. It does not refer to any action taken by the permit holder. Ecology’s performance goal is to address all permit violations for individual permits. The report includes NA (not applicable) for general permits.

Search Results

Remove the Permit Status = Active filter to view both active and inactive permits.
Filter Search Result
(Permit Status = 'Active')
  • And
  • Or
  • Not And
  • Not Or
  • Contains
  • DoesNotContain
  • StartsWith
  • EndsWith
  • EqualTo
  • NotEqualTo
  • GreaterThan
  • LessThan
  • GreaterThanOrEqualTo
  • LessThanOrEqualTo
  • Between
  • NotBetween
  • IsEmpty
  • NotIsEmpty
  • IsNull
  • NotIsNull
  • Facility Id
  • Violation Id
  • Water Quality name
  • Permit Number
  • Permit Status
  • Permit Type
  • City
  • County
  • Violation Date
  • Is Addressed
  • Category
  • Type
  • Parameter
  • Units
  • Statistical Base
  • Measurement value
  • Benchmark/Limit
  • Violation Notes
  • Violation Override
  • Feature Name
-Facility NamePermit NumberPermit StatusPermit TypeCityCountyViolation DateIs AddressedCategoryTypeParameterUnitsStatistical BaseMeasurement ValueBenchmark/LimitViolation NotesViolation OverrideFeature Name
Page size:
 35 items in 4 pages
More Info MARYSVILLE STP WA0022497ActiveMunicipal NPDES IPMARYSVILLESnohomish2/1/2025N/AEffluent ViolationsNumeric effluent violation   2763 Leung: In early this month, the weather was cold with snows in the areas. A large portion of their lagoon system was frozen over causing lagoon process performance upset resulting in elevated TSS levels during that time. It's getting better later this month, but the overall effluent TSS levels are still higher than the permit limits.  
More Info MARYSVILLE STP WA0022497ActiveMunicipal NPDES IPMARYSVILLESnohomish2/1/2025N/AEffluent ViolationsNumeric effluent violation   52.7 Leung: In early this month, the weather was cold with snows in the areas. A large portion of their lagoon system was frozen over causing lagoon process performance upset resulting in elevated TSS levels during that time. It's getting better later this month, but the overall effluent TSS levels are still higher than the permit limits.  
More Info MARYSVILLE STP WA0022497ActiveMunicipal NPDES IPMARYSVILLESnohomish2/1/2025N/AEffluent ViolationsNumeric effluent violation   40.8333 Leung: In early this month, the weather was cold with snows in the areas. A large portion of their lagoon system was frozen over causing lagoon process performance upset resulting in elevated TSS levels during that time. It's getting better later this month, but the overall effluent TSS levels are still higher than the permit limits.  
More Info MARYSVILLE STP WA0022497ActiveMunicipal NPDES IPMARYSVILLESnohomish2/1/2025N/AEffluent ViolationsNumeric effluent violation   2291.67 Leung: In early this month, the weather was cold with snows in the areas. A large portion of their lagoon system was frozen over causing lagoon process performance upset resulting in elevated TSS levels during that time. It's getting better later this month, but the overall effluent TSS levels are still higher than the permit limits.  
More Info MARYSVILLE STP WA0022497ActiveMunicipal NPDES IPMARYSVILLESnohomish2/1/2025N/AEffluent ViolationsNumeric effluent violation   79 Leung: In early this month, the weather was cold with snows in the areas. A large portion of their lagoon system was frozen over causing lagoon process performance upset resulting in elevated TSS levels during that time. It's getting better later this mont, but the overall effluent TSS levels are still higher than the permit limits.  
More Info MARYSVILLE STP WA0022497ActiveMunicipal NPDES IPMARYSVILLESnohomish6/1/2024N/AEffluent ViolationsNumeric effluent violation   31.3333 Leung: The elevated effluent TSS levels were due to algae issues in the lagoons.  
More Info MARYSVILLE STP WA0022497ActiveMunicipal NPDES IPMARYSVILLESnohomish2/1/2023N/ADesign Criteria ExceedanceExceedance of Design Criteria   21061.4 Leung: Staff continue investigating the causes of the higher influent BOD5 loadings. All effluent levels are in compliance with permit limits.  
More Info MARYSVILLE STP WA0022497ActiveMunicipal NPDES IPMARYSVILLESnohomish12/1/2022N/AEffluent ViolationsNumeric effluent violation   32 It's due to the flow discharged through Outfall 001 or Outfall 100 during the monitoring period. It's a permit violation if the calculations of effluent TSS MoAvg are based on data for Outfall 100 only but it's not a permit violation if calculations are based on all data from Outfall 001 and Outfall 100. This is not a permit violation. This is a DMR setup issue in the current permit.  
More Info MARYSVILLE STP WA0022497ActiveMunicipal NPDES IPMARYSVILLESnohomish5/31/2022N/AReporting ViolationsFailure to submit required report (non-DMR, non-pretreatment)     The permit renewal application submittal is due 5/31/22. It's received on 5/31/22. However, the submittal due date is listed 5/21/22 in PARIS. This was a setup error in PARIS. This is not a late submittal/permit violation.  
More Info MARYSVILLE STP WA0022497ActiveMunicipal NPDES IPMARYSVILLESnohomish5/1/2022N/AEffluent ViolationsNumeric effluent violation   31.8889 It's due to the flow discharged through Outfall 001 or Outfall 100 during the monitoring period. It's a permit violation if the calculations of effluent TSS MoAvg are based on data for Outfall 100 only but it's not a permit violation if calculations are based on all data from Outfall 001 and Outfall 100. This is not a permit violation. This is a DMR setup issue in the current permit.  
  • NoFilter
  • Contains
  • DoesNotContain
  • StartsWith
  • EndsWith
  • EqualTo
  • NotEqualTo
  • GreaterThan
  • LessThan
  • GreaterThanOrEqualTo
  • LessThanOrEqualTo
  • Between
  • NotBetween
  • IsEmpty
  • NotIsEmpty
  • IsNull
  • NotIsNull
  • Custom