Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Transit topic
No spam. Unsubscribe anytime.
Hampton Roads Transit proposes cutting low‑performing routes, expanding microtransit to shore up service
Summary
At a Sept. 9 Chesapeake City Council work session, Hampton Roads Transit proposed a System Optimization Plan that would eliminate underperforming routes across the six‑city system, free operator capacity to expand 15‑minute backbone service, and pilot microtransit zones in Chesapeake to replace some fixed‑route coverage.
Hampton Roads Transit told Chesapeake city leaders on Sept. 9 that it wants to reallocate service from low‑ridership routes to a regional high‑frequency backbone and pilot app‑based microtransit in parts of the city.
"Frequency does indeed equal freedom," Ray Amoruso, chief of planning and development for Hampton Roads Transit, said during a work‑session briefing, arguing the agency must match services to limited financial and human resources. Amoruso said the system has 68 bus routes across six member cities, faces a shortfall of roughly 50 operators each day, and is in the bottom quartile of comparable agencies on passengers per revenue hour.
Amoruso described a System Optimization Plan (SOP) that would target about 12 underperforming routes system‑wide — routes that together account for less than 3% of boardings — to free roughly 90,000 local service hours, 14 peak vehicles and about 65 operators. Those resources would be redirected to implementing up to 13 regional backbone routes running every 15 minutes, which HRT says would place about 300,000 more residents within walking distance of frequent service.
To mitigate loss of fixed‑route coverage where needed, HRT proposed three microtransit pilot zones in Chesapeake. One pilot, centered on Mount Pleasant Road, covers about 11 square miles and was awarded a one‑year state "trip" grant that covers 80% of the pilot's cost; Chesapeake is expected to provide a 20% local match. Amoruso described microtransit as an app‑based demand‑response minivan service that would direct riders to virtual stops and link them to fixed routes or local destinations.
Council members asked about likely cost savings, legal constraints and coverage. "Will there be a reduction in cost?" Councilmember Smith asked; Amoruso said eliminating low‑productivity routes should improve productivity and increase state funding that is awarded based on passengers per trip, mile and hour. On federal civil‑rights rules, Amoruso said HRT will perform Title VI analyses for any elimination or reduction of service and that the proposed microtransit mitigations are intended to prevent disproportionate impacts on low‑income and minority communities.
Councilmembers also pressed for local details: whether microtransit zones would serve shelters such as Stepping Stone and how short turning or right‑of‑way limits (for example, where a 40‑foot bus cannot turn safely) would be addressed. Amoruso said staff would follow up and consider additional microtransit overlays where fixed‑route service is impractical.
HRT outlined a staged implementation approach: additional city briefings through fall, public open houses on the draft SOP, a commission briefing in February on the draft, and three service boards (noted in the briefing as October 2026, May 2027 and October 2027) before full implementation. Amoruso emphasized the SOP is a draft and that the agency intends further public feedback.
What’s next: HRT will continue council work‑session briefings, hold public open houses on the draft SOP recommendations, return to Chesapeake with public input in January, and brief its commission in February before any adoption vote.
