N4060 (S177E)
Carrying N4060 (S177E) over SPUNKY CREEK
1300 SO 177TH E AVE, Tulsa, Oklahoma
Data updated May 2026
FHWA NBI record, refreshed with each annual release.
Bridge Snapshot: N4060 (S177E)
The N4060 (S177E) bridge in Tulsa, Oklahoma carries N4060 (S177E) over SPUNKY CREEK. It was built in 2023, making it 3 years old today. The structure is built primarily of concrete and spans 2 sections, stretching 10.1 meters (33 feet) end to end. Daily traffic averages 4,041 vehicles, placing it in the moderately-trafficked tier of Oklahoma bridges. It is owned and maintained by City/Municipal Highway Agency.
The latest FHWA inspection records show culvert at 8/9. The weakest component sits in good condition. All reported major components score above the Poor range. Its NBI inventory load rating is 32.7 metric tons.
Sourced from the FHWA National Bridge Inventory. See our methodology for refresh cadence and NBI release vintage.
How N4060 (S177E) compares
Live comparison across Oklahoma.
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
- 2023
- Material
- Concrete
- Number of Spans
- 2
- Structure Length
- 10.1 m (33 ft)
- Deck Width
- 12.3 m (40 ft)
- Owner
- City/Municipal Highway Agency
- Avg Daily Traffic
- 4,041 vehicles/day
- Structure Number
- 332550000000000
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 N4060 (S177E) 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 N4060 (S177E) against other structures in Tulsa and across Oklahoma. Oklahoma 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 N4060 (S177E)?
N4060 (S177E) in Tulsa, Oklahoma on the FHWA's 0–9 scale.
How often is N4060 (S177E) inspected?
N4060 (S177E)'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 4,041 vehicles per day.
What does “structurally deficient” mean in older bridge reports?
FHWA retired that reported status beginning with the 2018 archive. N4060 (S177E) 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 N4060 (S177E)?
N4060 (S177E) has an NBI inventory load rating of 32.7 metric tons.
Who is responsible for maintaining N4060 (S177E)?
N4060 (S177E) is owned and maintained by City/Municipal Highway Agency.
How old is N4060 (S177E) and does age affect safety?
N4060 (S177E) was built in 2023, making it 3 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.