By: Sam Belfield, Senior Transportation Engineer
HRTPO staff has recently released the Existing and Future Truck Delay in Hampton Roads draft report.
In September 2012, The Hampton Roads Metropolitan Organization (HRTPO) staff completed the Hampton Roads Regional Freight Study (September 2012). This 2013 study builds on the work contained within the 2012 study, expanding the analysis of existing truck volumes and delays by location to include future truck volumes and delays in Hampton Roads. It uses the new truck component and time-of-day capability of the regional travel demand model to forecast truck volumes and congestion to be faced by trucks in the next 20 years. This is the first time that the HRTPO staff has forecasted future truck traffic or truck delays. The results of this analysis include future roadway segments with the highest total weekday truck delays.
It is important to note that the truck delay analysis contained in this report is not the same as the congestion analysis in the Hampton Roads Congestion Management Process (CMP). The CMP congestion analysis determines weekday congestion levels by roadway segment for all vehicles including trucks. Weekday truck delay in this report is a function of the congestion on a given roadway segment and the number of trucks that use that same segment each weekday. For example, a roadway segment with high congestion levels and low truck volumes will have low total truck delay due to that volume.
The HRTPO staff plans to review the freight component of the HRTPO Project Prioritization Tool and incorporate any changes related to truck delays that are warranted. In this way, the HRTPO Board can better consider freight when making funding decisions for transportation improvements.
The Existing and Future Truck Delay in Hampton Roads draft report is available for public review and comment through July 26th, 2013. You may access the draft report by clicking on the following link:
All interested parties are encouraged to review the draft report and send comments to Sam Belfield at firstname.lastname@example.org