Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Stormwater topic
No spam. Unsubscribe anytime.
Residents implore Arlington council to address stormwater erosion in Prestonwood West
Summary
Homeowners from Prestonwood West urged the council to redesign city stormwater conveyance after describing repeated erosion and sedimentation on private property caused, they said, by high‑velocity municipal runoff; speakers asked the city to intercept watershed flows before they reach private corridors.
Several Prestonwood West residents told the Arlington City Council on Jan. 27 that stormwater runoff and a failing conveyance corridor are causing ongoing erosion, property damage and safety concerns.
Alberto Vasquez said the corridor is functioning as a municipal stormwater conveyance and that the flows driving erosion originate from public streets and approved development. “We're asking the city leadership to address a stormwater velocity problem that homeowners cannot solve on their own,” Vasquez said.
Steven Daniels, speaking for homeowners, emphasized the fiscal strain on many residents and said the corridor no longer functions as a neighborhood amenity. “With this waterway, no longer functions as an amenity,” Daniels said, adding that a substantial share of homeowners are on fixed incomes and cannot absorb major repair costs caused by upstream flows.
Both speakers asked the council and staff to acknowledge the corridor as a city stormwater issue and to consider watershed‑scale measures rather than shifting responsibility to the HOA or individual homeowners. The transcript shows city engineers have evaluated the corridor and that emergency authority has been exercised for drainage and public safety issues, but no formal action or motion was recorded during citizen participation.
Under the council’s citizen‑participation rules, mayor and council are limited to clarifying questions or directing staff to follow up; the speakers urged such staff follow‑up and indicated they will continue to press the issue in coming meetings.
This report draws from public‑comment segments beginning at SEG 1001 and continuing through SEG 1176.
