GooseCreekRun 660
Carrying GooseCreekRun 660 over Goose Creek
0.50 RT 653; 0.35 RT 659, Floyd, Virginia
Data updated May 2026
FHWA NBI record, refreshed with each annual release.
Bridge Snapshot: GooseCreekRun 660
The GooseCreekRun 660 bridge in Floyd, Virginia carries GooseCreekRun 660 over Goose Creek. It was built in 1980, making it 46 years old today. The structure is built primarily of steel and spans 3 sections, stretching 7.0 meters (23 feet) end to end. Daily traffic averages 85 vehicles, placing it in the lower-traffic tier of Virginia bridges. It is owned and maintained by State Highway Agency.
The latest FHWA inspection records show culvert at 7/9. The weakest component sits in good condition. None of this bridge's reported major components fall into the Poor condition 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 GooseCreekRun 660 compares
Live comparison across Virginia.
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
- 1980
- Material
- Steel
- Number of Spans
- 3
- Structure Length
- 7.0 m (23 ft)
- Deck Width
- 7.4 m (24 ft)
- Owner
- State Highway Agency
- Avg Daily Traffic
- 85 vehicles/day
- Structure Number
- 000000000007564
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 GooseCreekRun 660 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 GooseCreekRun 660 against other structures in Floyd and across Virginia. Virginia 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 GooseCreekRun 660?
GooseCreekRun 660 in Floyd, Virginia on the FHWA's 0–9 scale.
How often is GooseCreekRun 660 inspected?
GooseCreekRun 660'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 85 vehicles per day.
What does “structurally deficient” mean in older bridge reports?
FHWA retired that reported status beginning with the 2018 archive. GooseCreekRun 660 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 GooseCreekRun 660?
GooseCreekRun 660 has an NBI inventory load rating of 32.7 metric tons.
Who is responsible for maintaining GooseCreekRun 660?
GooseCreekRun 660 is owned and maintained by State Highway Agency.
How old is GooseCreekRun 660 and does age affect safety?
GooseCreekRun 660 was built in 1980, making it 46 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.