Bedford County U.d.

PWSID: TN0000517

System Details

Population Served22,908
Service Connections8,270
Water SourceSurface Water
System TypeCommunity Water System
OwnerLocal Government
StatusActive
CityShelbyville
Zip Code37160

Areas Served

  • Shelbyville, Bedford County

Lead & Copper Testing

ContaminantLevelEPA Action LevelStatus
Lead (90th percentile)0.0021 mg/L0.015 mg/LBelow Action Level
Lead (90th percentile)0.0011 mg/L0.015 mg/LBelow Action Level
Lead (90th percentile)0.0010 mg/L0.015 mg/LBelow Action Level
Lead (90th percentile)0.0010 mg/L0.015 mg/LBelow Action Level

2 Active Violations

ContaminantViolationDateHealth-BasedStatus
2022-07-01Open
2012-07-01Open

Violation History (58 total)

ContaminantViolationDateHealth-BasedStatus
2023-08-01YesReturned to Compliance
2023-07-01YesReturned to Compliance
2023-04-01YesAcknowledged
2023-04-01YesAcknowledged
2023-04-01YesAcknowledged
2023-04-01YesReturned to Compliance
2022-10-01YesReturned to Compliance
2022-05-01YesAcknowledged
2022-05-01YesAcknowledged
2022-05-01YesAcknowledged
2022-05-01YesReturned to Compliance
2022-02-01YesAcknowledged
2022-02-01YesAcknowledged
2022-02-01YesAcknowledged
2022-02-01YesReturned to Compliance
2022-01-01YesAcknowledged
2022-01-01YesAcknowledged
2022-01-01YesAcknowledged
2022-01-01YesReturned to Compliance
2021-02-01YesAcknowledged
2021-02-01YesAcknowledged
2021-02-01YesAcknowledged
2021-02-01YesReturned to Compliance
2021-01-01Returned to Compliance
2021-01-01Returned to Compliance
2021-01-01Returned to Compliance
2021-01-01Returned to Compliance
2021-01-01Returned to Compliance
2021-01-01Returned to Compliance
2020-10-01YesAcknowledged
2020-10-01YesAcknowledged
2020-10-01YesAcknowledged
2020-10-01YesReturned to Compliance
2020-09-01YesAcknowledged
2020-09-01YesAcknowledged
2020-09-01YesAcknowledged
2020-09-01YesAcknowledged
2020-09-01YesReturned to Compliance
2018-01-01YesReturned to Compliance
2018-01-01YesReturned to Compliance
2017-10-01YesReturned to Compliance
2017-10-01YesReturned to Compliance
2017-07-01YesReturned to Compliance
2017-07-01YesReturned to Compliance
2017-07-01Returned to Compliance
2017-07-01Returned to Compliance
2016-01-01 MajorReturned to Compliance
2016-01-01 MajorReturned to Compliance
2015-10-01 MajorReturned to Compliance
2015-10-01 MajorReturned to Compliance

Showing 50 of 56 historical violations.