Port Labelle

PWSID: FL5260226

System Details

Population Served11,782
Service Connections4,208
Water SourceGroundwater
System TypeCommunity Water System
OwnerPrivate
StatusActive
CityLabelle
Zip Code33975

Areas Served

  • Port Labelle, Hendry County

Lead & Copper Testing

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

1 Active Violations

ContaminantViolationDateHealth-BasedStatus
2005-07-01Open

Violation History (62 total)

ContaminantViolationDateHealth-BasedStatus
2024-06-01 MajorAcknowledged
2024-06-01 MajorReturned to Compliance
2024-06-01 MajorReturned to Compliance
2024-06-01 MajorReturned to Compliance
2024-06-01 MajorAcknowledged
2024-06-01 MajorAcknowledged
2024-06-01 MajorReturned to Compliance
2024-06-01 MajorReturned to Compliance
2024-04-01 MajorReturned to Compliance
2024-04-01 MajorReturned to Compliance
2024-04-01 MajorReturned to Compliance
2024-04-01 MajorReturned to Compliance
2024-04-01 MajorReturned to Compliance
2024-04-01 MajorReturned to Compliance
2024-04-01 MajorReturned to Compliance
2024-04-01 MajorReturned to Compliance
2024-02-01 MajorReturned to Compliance
2024-02-01 MajorReturned to Compliance
2023-07-01Acknowledged
2023-07-01Acknowledged
2023-07-01Acknowledged
2023-07-01Returned to Compliance
2023-07-01Returned to Compliance
2023-07-01Returned to Compliance
2023-07-01Acknowledged
2023-07-01Acknowledged
2023-07-01Acknowledged
2023-07-01Returned to Compliance
2023-07-01Returned to Compliance
2023-07-01Returned to Compliance
2023-07-01 MajorAcknowledged
2023-07-01 MajorAcknowledged
2023-07-01 MajorAcknowledged
2023-07-01 MajorAcknowledged
2023-07-01 MajorReturned to Compliance
2023-07-01 MajorReturned to Compliance
2023-07-01 MajorAcknowledged
2016-01-01YesReturned to Compliance
2016-01-01YesReturned to Compliance
2016-01-01YesReturned to Compliance
2016-01-01YesReturned to Compliance
2016-01-01YesReturned to Compliance
2016-01-01YesReturned to Compliance
2015-10-01YesReturned to Compliance
2015-10-01YesReturned to Compliance
2015-10-01YesReturned to Compliance
2015-10-01YesReturned to Compliance
2015-10-01YesReturned to Compliance
2015-10-01YesReturned to Compliance
2015-07-01YesReturned to Compliance

Showing 50 of 61 historical violations.