Fort Sumner Municipal Water System

PWSID: NM3527706

System Details

Population Served1,789
Service Connections832
Water SourceGroundwater
System TypeCommunity Water System
OwnerLocal Government
StatusActive
CityFort Sumner
Zip Code88119

Areas Served

  • Fort Sumner, De Baca County

Lead & Copper Testing

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

1 Active Violations

ContaminantViolationDateHealth-BasedStatus
2001-07-01Open

Violation History (83 total)

ContaminantViolationDateHealth-BasedStatus
2023-05-09 MajorReturned to Compliance
2023-05-09 MajorReturned to Compliance
2023-05-09 MajorReturned to Compliance
2021-06-28Returned to Compliance
2021-06-28Returned to Compliance
2019-10-01 MajorReturned to Compliance
2019-10-01 MajorReturned to Compliance
2019-10-01 MajorReturned to Compliance
2019-10-01 MajorReturned to Compliance
2019-08-19Returned to Compliance
2019-08-19Returned to Compliance
2019-03-28Returned to Compliance
2019-03-28Returned to Compliance
2018-10-01Returned to Compliance
2018-08-12Returned to Compliance
2018-08-12Returned to Compliance
2018-08-10YesReturned to Compliance
2018-08-10YesReturned to Compliance
2018-07-01Returned to Compliance
2018-07-01Returned to Compliance
2018-04-27Returned to Compliance
2018-04-27Returned to Compliance
2018-04-01Returned to Compliance
2018-04-01Returned to Compliance
2017-11-17YesReturned to Compliance
2017-11-17YesReturned to Compliance
2017-10-01Returned to Compliance
2017-10-01Returned to Compliance
2017-10-01 MajorReturned to Compliance
2017-10-01 MajorReturned to Compliance
2017-10-01 MajorReturned to Compliance
2017-10-01 MajorReturned to Compliance
2017-09-16Returned to Compliance
2017-09-16Returned to Compliance
2017-09-16Returned to Compliance
2017-09-16Returned to Compliance
2017-09-16Returned to Compliance
2017-09-16Returned to Compliance
2017-08-22YesReturned to Compliance
2017-08-22YesReturned to Compliance
2017-07-01Returned to Compliance
2017-07-01Returned to Compliance
2017-06-04Returned to Compliance
2017-06-04Returned to Compliance
2017-06-04Returned to Compliance
2017-06-04Returned to Compliance
2017-05-27YesReturned to Compliance
2017-05-27YesReturned to Compliance
2017-04-01Returned to Compliance
2017-04-01Returned to Compliance

Showing 50 of 82 historical violations.