Live TVMarketsFinanceEconomicsIndustriesTechReal EstateSmall BusinessPoliticsVideo
Top SecuritiesDOW (DIA) $520.19 ▼2.42%S&P 500 (SPY) $740.54 ▼3.43%NASDAQ 24,419 ▼5.12%10Y 4.90% ▼5 bpBITCOIN $76,032 ▼5.56%NASDAQ 100 (QQQ) $652.56 ▼5.69%30Y MORTGAGE 7.24% ▼0.08
Thursday, November 5, 2026 Edition · Raleigh 73° Cloudy Watch Live Sign in Subscribe
Genius Eye NewsA service of The GET Network, Inc.
Markets
Economics

Third northbound I-81 lane near Staunton to open in November 2026

VDOT is widening I-81 near Staunton with a $101 million project to add a third northbound lane by late 2026.

Nov 5, 2026, 9:55 AM By the Genius Eye newsroom (Economics Reporter) · Fact-checkedHow we report
Doug Kerr from Albany, NY, United States / CC BY-SA 2.0, via Wikimedia Commons

The Virginia Department of Transportation (VDOT) is expanding Interstate 81 near Staunton by adding a third northbound lane, scheduled to open in November 2026, according to richmond.com.

This work is part of a $101 million design-build contract under the I-81 Corridor Improvement Program (CIP), which aims to enhance safety, reduce congestion, and support economic growth along the corridor.

Construction began in fall 2023 and is expected to continue through summer 2027, including widening five bridges—four on I-81 South and one on I-81 North—as well as final paving, striping, and installation of guardrails and signs.

Traffic in both directions is subject to a 60 mph work-zone speed limit, with possible shoulder closures, traffic pattern shifts, and overnight single-lane closures. All work depends on weather conditions and may be rescheduled.

The I-81 CIP encompasses 65 projects across the corridor with nearly $4 billion invested. VDOT provides updates and resources through Improve81.org and maintains a 24/7 Customer Service Center for roadway user support.

Sources
  1. richmond.com: Third northbound I - 81 lane near Staunton to open
We read public reporting and official data, confirm what we can, and write our own story. See something wrong? Request a correction.

Comments

No comments yet.

Sign in to comment