I-15 (SR-15)NB&
Carrying I-15 (SR-15)NB& over DRY CREEK
0.6 MI NO KOLOB CAN. INT., Washington, Utah
Data updated May 2026
FHWA NBI record, refreshed with each annual release.
Bridge Snapshot: I-15 (SR-15)NB&
The I-15 (SR-15)NB& bridge in Washington, Utah carries I-15 (SR-15)NB& over DRY CREEK. It was built in 1959, making it 67 years old today. The structure is built primarily of concrete and spans 1 section, stretching 7.7 meters (25 feet) end to end. Daily traffic averages 32,993 vehicles, placing it in the heavily-trafficked tier of Utah 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. No reported major component scores in the Poor range under the current federal condition thresholds. Its NBI inventory load rating is 31.8 metric tons.
Sourced from the FHWA National Bridge Inventory. See our methodology for refresh cadence and NBI release vintage.
How I-15 (SR-15)NB& compares
Live comparison across Utah.
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
- 1959
- Material
- Concrete
- Number of Spans
- 1
- Structure Length
- 7.7 m (25 ft)
- Owner
- State Highway Agency
- Avg Daily Traffic
- 32,993 vehicles/day
- Structure Number
- 0E1128
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 I-15 (SR-15)NB& 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 I-15 (SR-15)NB& against other structures in Washington and across Utah. Utah 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 I-15 (SR-15)NB&?
I-15 (SR-15)NB& in Washington, Utah on the FHWA's 0–9 scale.
How often is I-15 (SR-15)NB& inspected?
I-15 (SR-15)NB&'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 32,993 vehicles per day.
What does “structurally deficient” mean in older bridge reports?
FHWA retired that reported status beginning with the 2018 archive. I-15 (SR-15)NB& 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 I-15 (SR-15)NB&?
I-15 (SR-15)NB& has an NBI inventory load rating of 31.8 metric tons.
Who is responsible for maintaining I-15 (SR-15)NB&?
I-15 (SR-15)NB& is owned and maintained by State Highway Agency.
How old is I-15 (SR-15)NB& and does age affect safety?
I-15 (SR-15)NB& was built in 1959, making it 67 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.