Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Annexation topic
No spam. Unsubscribe anytime.
Fredericksburg council tables Homick Lane annexation after residents raise drainage, school‑crossing concerns
Summary
Council tabled ordinance 2025‑37 on an annexation for about 39 acres on Homick/Holmink Lane after residents and the developer asked for more meetings; concerns focused on stormwater drainage, downstream erosion and safe school crossings; city staff will convene county and developer meetings and return with an update Nov. 4.
Get email alerts on the Annexation topic
No spam. Unsubscribe anytime.
Council on [date] temporarily tabled a proposed voluntary annexation on Homick (Holmink) Lane after residents pressed for more study of drainage and safety impacts and the developer asked for a facilitated forum to seek compromise.
Developer representative Corey Keller, speaking for Horizon Development, asked the council for what he called “a setting, a different type of meeting … a facilitator where we can exchange ideas back and forth and seek understanding.” Keller said the team has bank loans and contracts pending and asked the council either to approve the project or to set a clear pause and a path for discussion.
Residents who live near the project told the council the neighborhood’s infrastructure is already strained. Marshall Epley, who said he lives on Bob White Trail, told the council Holmick Lane “was never designed for that much traffic” and raised worries about children crossing near the new middle school. Several speakers urged delaying approval until traffic and crossing solutions and drainage controls are agreed. Deb Youngblood, representing the Pertinallis River Alliance, described a low‑lying area that could be shaped to hold and filter stormwater and asked to be included in planning discussions.
City staff and councilors said the matter overlaps city and county responsibilities. A staff speaker noted the annexation is voluntary and that annexation gives the city leverage to set development standards, but several council members said the downstream impacts cross jurisdictional lines and recommended a joint city‑county effort. The county engineer said county staff would participate in initial discussions.
Council member (speaker4) moved to table the annexation; the motion was amended and the council voted to table ordinance 2025‑37 for an update on November 4. Council directed staff to convene meetings with the developer, affected property owners and county representatives before that update.
The action applies only to the city’s procedural action on annexation at this meeting; no rezoning or final plat approvals were adopted. The council and staff said they want concrete engineering or mitigation proposals before taking a final vote.
What’s next: Staff committed to scheduling county/city/developer discussions as soon as possible and to report back at the November 4 council meeting. The council asked participants to prepare specific engineering and traffic‑safety proposals and to identify statutory deadlines that might affect timing.
