IDOT is planning on doing a weekend closure of 55/70 between 64 and 203 next weekend for bridge demolition, so expect heavier than normal traffic on April 9 and 10. (This is weather permitting, though.)
Speaking of heavy traffic, this still from the Gateway Guide 270/Riverview camera should prove the capacity issue during peak periods:

- Hourly capacity of the Chain of Rocks Bridge is approximately 3700 vehicles per hour.
- Projected AADT for 2020 at 71,100 with westbound peak hour right at 3700 vehicles if the No Build plan was selected.
When IDOT starts putting out the orange barrels this year for the construction season, the off-peak congestion will obviously be there, and weekend hassles are not out of the question. Although IDOT is spending their time fixing up 55/70, don't expect the 270 corridor to be let off the hook. Much of it is 45-46 years old and is already showing its age. The last hardcore work done on that corridor happened 13-15 years ago and most of it is showing signs of wear and tear. The bridge decks on the canal bridge is in terrible shape, the river bridge is going in that same direction, and the pavement is rough and loaded with potholes (even though much of it was done in 2008). Decades of heavy truck traffic (20% to 25% of all traffic in spots) has contributed to much of the deterioration, and it is common to find overweight trucks on the corridor just to avoid the weigh station on westbound 55/70 near Collinsville. Trucks also use the 270 corridor to Route 4 east of Troy just to bypass the weigh station on eastbound 64 near Shiloh. Route 4, despite being 2 lanes and hilly, has a high truck percent between 270 and 64. The truck AADT on 270 west of 255 never dips below 10,000 while the truck AADT on 55/70 west of 255 does not top 10,000 until the merge with 64. (The overall AADT on 270 w/0 255 is in the high 50s; while 55/70 w/0 255 stays in the high 40s until the merge with 64.)
No comments:
Post a Comment