US311, NC770
Carrying US311, NC770 over DRY CREEK
0.2 MI. E. JCT. SR1741, Rockingham, North Carolina
Data updated May 2026
FHWA NBI record, refreshed with each annual release.
Bridge Snapshot: US311, NC770
The US311, NC770 bridge in Rockingham, North Carolina carries US311, NC770 over DRY CREEK. It was built in 1965, making it 61 years old today. The structure is built primarily of concrete continuous and spans 2 sections, stretching 6.4 meters (21 feet) end to end. Daily traffic averages 3,900 vehicles, placing it in the moderately-trafficked tier of North Carolina bridges. It is owned and maintained by State Highway Agency.
The latest FHWA inspection records show culvert at 6/9. The weakest component sits in fair condition. All reported major components score above the Poor range. Its NBI inventory load rating is 32.6 metric tons.
Sourced from the FHWA National Bridge Inventory. See our methodology for refresh cadence and NBI release vintage.
How US311, NC770 compares
Live comparison across North Carolina.
Historical Sufficiency Rating
PlainBridge-computedFHWA discontinued this calculated item; it does not determine current condition, funding eligibility, posting, or closure. How the historical reference is calculated.
Condition Ratings
Full 0–9 scale + sufficiency-rating breakdown: how condition ratings work.
Structural Details
- Year Built
- 1965
- Material
- Concrete Continuous
- Number of Spans
- 2
- Structure Length
- 6.4 m (21 ft)
- Owner
- State Highway Agency
- Avg Daily Traffic
- 3,900 vehicles/day
- Structure Number
- 000000001570162
Location
Data Source
FHWA National Bridge Inventory (NBI).
FHWA NBI Program ↗How to read this record
This page shows what the last federal inspection recorded, not whether US311, NC770 is safe to cross today. Here is how to use it.
- NBI condition ratings reflect the latest record in this annual dataset, not a live status. Current routine inspection intervals are risk-based.
- Learn how the 0–9 condition scale and Good/Fair/Poor categories are defined. How condition ratings work
- Compare US311, NC770 against other structures in Rockingham and across North Carolina. North Carolina bridges
- Noticed visible damage or a safety concern? Report it to the agency that owns the bridge, or call 911 in an emergency. How to report a bridge
Condition codes come straight from the FHWA National Bridge Inventory and are not a real-time safety judgment. Only the owning agency, a state DOT, county, or other owner, can post, restrict, or close a bridge.
Frequently Asked Questions
What do the condition ratings mean for US311, NC770?
US311, NC770 in Rockingham, North Carolina on the FHWA's 0–9 scale.
How often is US311, NC770 inspected?
US311, NC770's responsible agency sets its routine interval under FHWA's risk-based inspection rules; this page does not expose the scheduled interval. It carries about 3,900 vehicles per day.
What does “structurally deficient” mean in older bridge reports?
FHWA retired that reported status beginning with the 2018 archive. US311, NC770 is currently shown as Fair condition from its component ratings; that category is not a live closure or safety decision.
What is the inventory load rating for US311, NC770?
US311, NC770 has an NBI inventory load rating of 32.6 metric tons.
Who is responsible for maintaining US311, NC770?
US311, NC770 is owned and maintained by State Highway Agency.
How old is US311, NC770 and does age affect safety?
US311, NC770 was built in 1965, making it 61 years old.
Disclaimer: Bridge condition data is from the FHWA NBI and reflects the last reported inspection. A Poor condition rating is not a live declaration that a bridge is closed or unsafe for travel. For current closure, posting, or safety information, contact the responsible transportation agency.
Every figure on PlainBridge is rendered directly from federal source data, no number is typed in by an editor. This page draws directly on federal source data, no figure is typed in by an editor. See our editorial standards & corrections policy, the methodology behind these numbers, or report a data error.