| 981 | 446 | SFJ | State Formal Notice of Violation issued | 06-MAR-2025 | Region | - |
| 984 | 447 | SIE | State Public Notification requested | 06-MAR-2025 | Region | - |
| 978 | 445 | SIE | State Public Notification requested | 07-FEB-2025 | Region | - |
| 975 | 444 | SFJ | State Formal Notice of Violation issued | 07-FEB-2025 | Region | - |
| 973 | 443 | SIF | State Public Notification received | 02-MAY-2024 | Region | PN was initially issued on 4/17, but was only posted in businesses and not sent to homes (sent to EPA on 4/25). Notice was handed door to door on 5/2 with another notice and certificate sent to Region 7 on 5/15. |
| 969 | 442 | SOX | State Compliance achieved | 01-MAY-2023 | Region | - |
| 960 | 436 | SIE | State Public Notification requested | 06-OCT-2021 | Region | - |
| 960 | 437 | SIE | State Public Notification requested | 06-OCT-2021 | Region | - |
| 960 | 439 | SIE | State Public Notification requested | 06-OCT-2021 | Region | - |
| 960 | 440 | SIE | State Public Notification requested | 06-OCT-2021 | Region | - |
| 960 | 438 | SIE | State Public Notification requested | 06-OCT-2021 | Region | - |
| 941 | 435 | EOX | Federal Compliance achieved | 06-JUN-2019 | Region | Tribe did not submit to Region 7 a copy of their lead and copper sample results to Region 7 timely when they sampled for Lead and Copper in 2016. Sent copies of their lead and copper information to Region 7 on 06/05/2019. EPA approved on 06/06/2019. Violation will be put in their 2018 CCR. |
| 944 | 434 | EOX | Federal Compliance achieved | 05-JUN-2019 | Region | - |
| 956 | 406 | SOX | State Compliance achieved | 01-JAN-2019 | Region | Violation was SOX'd with 01/01/2019 date to indicate that the violation was RTC'd as part of data clean-up. |
| 955 | 405 | SOX | State Compliance achieved | 01-JAN-2019 | Region | Violation was SOX'd with 01/01/2019 date to indicate that the violation was RTC'd as part of data clean-up. |
| 951 | 202 | SOX | State Compliance achieved | 01-JAN-2019 | Region | Violation was SOX'd with 01/01/2019 date to indicate that the violation was RTC'd as part of data clean-up. |
| 950 | 193 | SOX | State Compliance achieved | 01-JAN-2019 | Region | Violation was SOX'd with 01/01/2019 date to indicate that the violation was RTC'd as part of data clean-up. |
| 949 | 191 | SOX | State Compliance achieved | 01-JAN-2019 | Region | Violation was SOX'd with 01/01/2019 date to indicate that the violation was RTC'd as part of data clean-up. |
| 946 | 102 | SOX | State Compliance achieved | 01-JAN-2019 | Region | Violation was SOX'd with 01/01/2019 date to indicate that the violation was RTC'd as part of data clean-up. |
| 957 | 408 | SOX | State Compliance achieved | 01-JAN-2019 | Region | Violation was SOX'd with 01/01/2019 date to indicate that the violation was RTC'd as part of data clean-up |
| 954 | 305 | SOX | State Compliance achieved | 01-JAN-2019 | Region | Violation was SOX'd with 01/01/2019 date to indicate that the violation was RTC'd as part of data clean-up |
| 932 | 432 | EFJ | Federal issued Formal Notice of Violation | 22-AUG-2016 | Region | - |
| 934 | 433 | EFJ | Federal issued Formal Notice of Violation | 10-JUN-2016 | Region | - |
| 925 | 414 | EIE | Federal Public Notification requested | 08-AUG-2014 | Region | - |
| 922 | 413 | EIE | Federal Public Notification requested | 26-JUN-2014 | Region | - |
| 919 | 412 | EIF | Federal Public Notification received from PWS | 02-JUL-2013 | Region | - |
| 917 | 410 | EOX | Federal Compliance achieved | 18-JAN-2013 | Region | - |
| 917 | 411 | EOX | Federal Compliance achieved | 18-JAN-2013 | Region | - |
| 914 | 409 | EOX | Federal Compliance achieved | 25-AUG-2011 | Region | - |
| 912 | 407 | EOX | Federal Compliance achieved | 20-SEP-2010 | Region | - |
| 496 | 196 | EOX | Federal Compliance achieved | 30-JUN-1996 | Region | - |
| 194 | 194 | EOX | Federal Compliance achieved | 01-AUG-1994 | Region | - |
| 493 | 293 | EOX | Federal Compliance achieved | 26-OCT-1993 | Region | - |