Castle Valley committee prioritizes culvert repairs, catchment ponds and cost‑share options for flood resilience

The Castle Valley Hazard Mitigation Committee met Feb. 25 at Lot 2 Castle Valley Drive and on Zoom and spent the second half of the meeting reviewing flood risks and mitigation measures, including local culvert performance, potential catchment ponds and options for cost‑sharing repairs on private property.

Committee members framed the update as both short‑term repairs and long‑term planning tied to FEMA mapping and LiDAR data. Members said FEMA’s LiDAR collection is complete for the area, but hydrologic analysis and formal FEMA flood mapping (which could influence insurance and building decisions) remain in process.

The committee discussed local flood history and magnitude. Members said last year’s events included several localized, intense runoff episodes; the group debated how to reflect probability and magnitude in the plan. They agreed that while short, intense flows are typical, potential magnitude is high and the town should prepare for likely repeat events and for scenarios that could cause significant road or access damage.

Near‑term mitigation items discussed included: monitoring and clearing culverts and channels, reinforcing or replacing crossings where they repeatedly wash out, creating or maintaining strategically located detention/catchment ponds to slow peak flows, and establishing a town procedure for waivers or temporary access agreements so road crews can reasonably work on private property where flood impacts originate.

Two specific local sites were raised. Members described a damaged catchment and berm issue near Upper Holyoke Lane (lot numbers discussed during the meeting) where a cut in a catchment and an altered berm have diverted sheet flow toward several down‑valley properties. The committee agreed this location merits prioritized channeling and coordination with the affected private owners to prevent repeated downstream damage.

Engineering‑scale interventions were discussed but not committed. Committee members noted such projects can be costly and require ongoing maintenance: a large detention or engineered pond can reduce peak flow, but it also requires inspection and debris removal to remain effective. The committee ranked large catchment ponds high for potential benefit but acknowledged lower scores for political and financial viability.

Operational items included maintaining a town sandbag stockpile (committee members said the town previously staged filled sandbags and should do another fill event), documenting and repairing known problem road crossings, and reviewing earlier NRCS studies of the Upper Plaster Creek area. Members also discussed prefabricated or low‑water crossing options for paint hollow and other frequently impacted crossings.

Liability and easement questions surfaced repeatedly. The committee discussed alternatives to long, difficult easement processes and signaled a preference for 90‑day waivers or temporary agreements to authorize town crews to perform channel maintenance on private land; members described current practice of using short waivers and re‑issuing them if work continues.

Committee members also discussed outreach and homeowner responsibility. They proposed prioritizing assessments of the most vulnerable lots, educating buyers and property owners on safe siting, and encouraging preparedness items such as a 72‑hour kit. The committee recommended adding an action item to pursue resident cost‑share options so property owners could pay a portion of repair costs for work that benefits both their lot and downstream neighbors.

No formal votes were taken. The committee directed staff to fold these flood mitigation edits into the draft plan, coordinate follow‑up with the county flood administrator and invite relevant state or federal technical staff (NRCS, FEMA) to review proposed engineering approaches before formal adoption and public hearings.