Licking Valley Rd
Carrying Licking Valley Rd over Trib of Wakatomika Creek
250 Ft S of Mckee Hill Rd, Licking, Ohio
Data updated May 2026
FHWA NBI record, refreshed with each annual release.
Bridge Snapshot: Licking Valley Rd
The Licking Valley Rd bridge in Licking, Ohio carries Licking Valley Rd over Trib of Wakatomika Creek. It was built in 2015, making it 11 years old today. The structure is built primarily of concrete and spans 1 section, stretching 7.3 meters (24 feet) end to end. Daily traffic averages 596 vehicles, placing it in the lower-traffic tier of Ohio bridges. It is owned and maintained by County Highway Agency.
The latest FHWA inspection records show culvert at 9/9. The weakest component sits in good condition. All reported major components score above the Poor range. Its NBI inventory load rating is 38.9 metric tons.
Sourced from the FHWA National Bridge Inventory. See our methodology for refresh cadence and NBI release vintage.
How Licking Valley Rd compares
Live comparison across Ohio.
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
- 2015
- Material
- Concrete
- Number of Spans
- 1
- Structure Length
- 7.3 m (24 ft)
- Owner
- County Highway Agency
- Avg Daily Traffic
- 596 vehicles/day
- Structure Number
- 4531020
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 Licking Valley Rd 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 Licking Valley Rd against other structures in Licking and across Ohio. Ohio 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 Licking Valley Rd?
Licking Valley Rd in Licking, Ohio on the FHWA's 0–9 scale.
How often is Licking Valley Rd inspected?
Licking Valley Rd'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 596 vehicles per day.
What does “structurally deficient” mean in older bridge reports?
FHWA retired that reported status beginning with the 2018 archive. Licking Valley Rd is currently shown as Good condition from its component ratings; that category is not a live closure or safety decision.
What is the inventory load rating for Licking Valley Rd?
Licking Valley Rd has an NBI inventory load rating of 38.9 metric tons.
Who is responsible for maintaining Licking Valley Rd?
Licking Valley Rd is owned and maintained by County Highway Agency.
How old is Licking Valley Rd and does age affect safety?
Licking Valley Rd was built in 2015, making it 11 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.