Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Pedestrian Safety topic
No spam. Unsubscribe anytime.
Committee hears bill to fast‑track pedestrian safety projects after Moorhead child’s death
Summary
House Transportation Committee heard House File 3418, an opt‑in program that would give communities premade pedestrian‑safety templates and fund 80% of quick projects. A Moorhead council member testified about a 9‑year‑old killed in a crosswalk; DOT staff noted existing demonstration programs and flagged fiscal and program overlaps.
House File 3418 was presented to the House Transportation Finance & Policy Committee as a proposal to let communities opt into a state‑backed, rapid pedestrian‑safety program aimed at speeding up low‑cost interventions at dangerous intersections.
The bill’s author told the committee the measure responds to a recent tragedy in Moorhead, where a 9‑year‑old child was struck and killed while crossing a street. The author described the proposal as an opt‑in system that would use the Office of Traffic Safety to provide communities with largely prebuilt design templates — for example lane narrowing, rumble strips, bollards or other standard countermeasures — so localities could implement remedies without “months and years” of study. The bill’s amendment would have the state pick up 80% of project costs for participating communities.
A Moorhead city council member testified in support, saying the city lost a 9‑year‑old, cited crash‑speed fatality statistics presented at a community meeting (for example, higher vehicle speeds raise fatality risk substantially), and said inexpensive measures such as bollards could have reduced risk quickly. He urged the committee to back the bill’s potential for immediate, low‑cost protections near schools.
A Department of Transportation active‑transportation staff member told the committee that DOT already supports community demonstration projects through Safe Routes to School and other active‑transportation programs and has funded roughly 30 community projects since 2019. DOT staff urged coordination so the new program would not duplicate existing efforts, and staff and authors flagged questions in the fiscal note (the draft assumes a biennial appropriation and additional FTE) that the committee said would need to be resolved.
Committee members asked about equity and allocation (how communities with louder voices will be weighed against others), jurisdictional limits on what countermeasures can be installed on state vs. local roads, and how templates would be prioritized. The author said the bill is intended to work with existing programs and to be fleshed out in follow‑up work.
Action: The committee laid House File 3418 over for continued development and fiscal review.
What’s next: Committee staff will work with the author and DOT on fiscal impacts, program overlap, and draft language to clarify allocation and project eligibility.
