Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Transportation Bus Rapid Transit topic
No spam. Unsubscribe anytime.
Officials debate SR‑224 bus‑rapid‑transit plan as Park City seeks clearer costs and impact maps
Summary
High Valley Transit presented a revised SR‑224 BRT design and ridership case — including a day‑one capacity of about 5,000 rides and a narrower 96‑foot corridor — while Park City councilors pressed for Park City‑specific metrics, a shaded overlay of right‑of‑way impacts and clarity on any local contribution (a $20M worst‑case placeholder was discussed).
At a joint briefing, High Valley Transit outlined a revised bus‑rapid‑transit (BRT) plan for State Route 224 that would run from Kimball Junction into Park City and use dedicated lanes, signal priority and upgraded stations to speed service and increase reliability.
“On day 1, we are ready to provide 5,000 rides every day,” said Gabriel Shields, High Valley Transit’s project manager, as he described seven‑day service from 6 a.m. to midnight with 10‑minute peak headways and stations at Cutter & Bobsled and Thanes Canyon. Shields also said the current 10X express route averages a 15‑minute trip on typical days and can take up to 45 minutes under bad conditions.
Project staff reviewed the program’s design timeline and costs. The NEPA worst‑case design delivered in 2022 showed a total estimate of $70.9 million; accounting for inflation, staff said that scenario would range roughly from $97 million to $103 million in 2024 dollars. The NEPA build footprint in the worst case would have been about 115 feet across, would affect 62 parcels and require roughly 2.5 acres of new right‑of‑way, the presentation said. Staff added they have narrowed the typical corridor cross‑section to about 96 feet to reduce pavement, utility relocations and property impacts.
Shields said project milestones include 30% design by the end of the year, 60% by May and 100% construction‑ready plans by the end of 2025; contractor proposals were reported as due the coming Wednesday with an anticipated award in December.
Park City council members who spoke at the meeting raised three recurring concerns: the distribution of benefits to Park City residents, the precise extent of right‑of‑way impacts inside city limits, and how much Park City should contribute to the project. Councilors requested a shaded overlay map showing where shoulders or private property would be cut into under prospective cross‑sections and asked for Park City‑specific modeling that quantifies time savings and other local benefits.
One council member noted experience with micro‑transit and local geography, saying, “I tried to use micro on four different occasions … it was a 45‑minute ride to get to city,” to underline that some neighborhoods are hard to serve without clearer last‑mile connections. Other council members emphasized the difference between frequency and speed, with presenters and some councilors arguing that ten‑minute frequencies combined with queue‑jumping and signal priority would change rider behavior more than speed alone.
Staff acknowledged there is a placeholder Park City contribution figure in the materials — described repeatedly in the meeting as a worst‑case request of about $20 million — and said that earlier budgeting had included a roughly $6 million Park City commitment in prior planning. Several Park City members asked for analysis showing exactly what would be delivered for a higher local contribution and whether value engineering could reduce the ask.
High Valley Transit staff and other presenters cautioned that delaying or formally withdrawing Park City participation could jeopardize federal and state funding relationships, and that the project team needed a clearer signal from Park City to protect those funding streams. Presenters asked Park City to decide whether it will participate in funding discussions or if the project should terminate in the Canyons area instead of entering city limits.
Council members and staff agreed on next steps: produce a shaded overlay of the narrower and wider cross‑section options showing property and trail impacts inside Park City; provide Park City‑specific ridership and time‑saving metrics; and increase staff‑to‑staff engagement between Park City planners and the county/High Valley Transit team so technical comments can be incorporated into the design. No formal vote or binding funding commitment was taken at the briefing.
The project remains positioned to proceed through the 30% design milestone; Park City councilors said they could provide a topline commitment pending rapid follow‑up on the overlay map and specific local impacts. High Valley Transit said procurement would continue on the announced schedule unless funding partners explicitly withdrew support.
