Fairystn Pk Hwy 57
Carrying Fairystn Pk Hwy 57 over Goblintown Creek
1.20 Rt 635; 0.02 Rt 847, Patrick, Virginia
Data updated May 2026
FHWA NBI record, refreshed with each annual release.
Bridge Snapshot: Fairystn Pk Hwy 57
The Fairystn Pk Hwy 57 bridge in Patrick, Virginia carries Fairystn Pk Hwy 57 over Goblintown Creek. It was built in 1968, making it 58 years old today. The structure is built primarily of concrete and spans 4 sections, stretching 15.2 meters (50 feet) end to end. Daily traffic averages 2,233 vehicles, placing it in the moderately-trafficked tier of Virginia 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 32.7 metric tons.
Sourced from the FHWA National Bridge Inventory. See our methodology for refresh cadence and NBI release vintage.
How Fairystn Pk Hwy 57 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
- 1968
- Material
- Concrete
- Number of Spans
- 4
- Structure Length
- 15.2 m (50 ft)
- Owner
- State Highway Agency
- Avg Daily Traffic
- 2,233 vehicles/day
- Structure Number
- 000000000013216
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 Fairystn Pk Hwy 57 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 Fairystn Pk Hwy 57 against other structures in Patrick 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 Fairystn Pk Hwy 57?
Fairystn Pk Hwy 57 in Patrick, Virginia on the FHWA's 0–9 scale.
How often is Fairystn Pk Hwy 57 inspected?
Fairystn Pk Hwy 57'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 2,233 vehicles per day.
What does “structurally deficient” mean in older bridge reports?
FHWA retired that reported status beginning with the 2018 archive. Fairystn Pk Hwy 57 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 Fairystn Pk Hwy 57?
Fairystn Pk Hwy 57 has an NBI inventory load rating of 32.7 metric tons.
Who is responsible for maintaining Fairystn Pk Hwy 57?
Fairystn Pk Hwy 57 is owned and maintained by State Highway Agency.
How old is Fairystn Pk Hwy 57 and does age affect safety?
Fairystn Pk Hwy 57 was built in 1968, making it 58 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.