Austin Water Responds to Sanitary Sewer Overflow Near E. Howard Lane
AUSTIN – Austin Water responded to a sanitary sewer overflow on Monday afternoon, Sept.
AUSTIN – Austin Water responded to a sanitary sewer overflow on Monday afternoon, Sept. 14, near 2500 E. Howard Lane. More than 100,000 gallons of sewage spilled from two manholes. Crews have stopped the spill and will remain on-site to make final repairs and assess remediation. The community’s drinking water supply is not affected and remains safe.
The overflow reached a nearby storm drain which connects to a private stormwater control wet pond a few yards away. Austin Water has notified the Texas Commission on Environmental Quality.
As a precaution, Austin Water advises:
- Persons using private drinking water supply wells located within a half-mile of the overflow site or within the potentially affected area should use only water that has been distilled or boiled at a rolling boil for at least one minute for all personal uses including drinking, cooking, bathing and tooth brushing. Individuals with private water wells should have their well water tested and disinfected, if necessary, before discontinuing distillation or boiling.
- Persons who purchase water from another public water supply may contact their water supply distributor to determine if the water is safe for personal use.
The public should avoid contact with waste material, soil or water in the area potentially affected by the overflow. If the public comes into contact with waste material, soil or water potentially affected by the spill, they should bathe and wash clothes thoroughly as soon as possible.
This story was originally published by City of Austin News.




Discussion
Share your perspective. Please stay respectful and keep comments relevant to this story. Comments are reviewed before appearing.
Start the conversation — no comments here yet.
Discussion at the original source
These comments belong to readers of the original publisher. Replies here stay on this website.
Source comments are not available here. Visit the original article to check its discussion.
Open original article