BEEVILLE LOOP
Carrying BEEVILLE LOOP over RABBIT CREEK
BEEVILLE LOOP, Mason, Washington
Data updated May 2026
FHWA NBI record, refreshed with each annual release.
Bridge Snapshot: BEEVILLE LOOP
The BEEVILLE LOOP bridge in Mason, Washington carries BEEVILLE LOOP over RABBIT CREEK. It was built in 2010, making it 16 years old today. The structure is built primarily of steel and spans 1 section, stretching 7.6 meters (25 feet) end to end. Daily traffic averages 32 vehicles, placing it in the lower-traffic tier of Washington bridges. It is owned and maintained by County Highway Agency.
The latest FHWA inspection records show culvert at 8/9. The weakest component sits in good condition. No reported major component scores in the Poor range under the current federal condition thresholds. Its NBI inventory load rating is 27.2 metric tons.
Sourced from the FHWA National Bridge Inventory. See our methodology for refresh cadence and NBI release vintage.
How BEEVILLE LOOP compares
Live comparison across Washington.
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
- 2010
- Material
- Steel
- Number of Spans
- 1
- Structure Length
- 7.6 m (25 ft)
- Deck Width
- 9.1 m (30 ft)
- Owner
- County Highway Agency
- Avg Daily Traffic
- 32 vehicles/day
- Structure Number
- 088237000000000
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 BEEVILLE LOOP 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 BEEVILLE LOOP against other structures in Mason and across Washington. Washington 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 BEEVILLE LOOP?
BEEVILLE LOOP in Mason, Washington on the FHWA's 0–9 scale.
How often is BEEVILLE LOOP inspected?
BEEVILLE LOOP'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 vehicles per day.
What does “structurally deficient” mean in older bridge reports?
FHWA retired that reported status beginning with the 2018 archive. BEEVILLE LOOP 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 BEEVILLE LOOP?
BEEVILLE LOOP has an NBI inventory load rating of 27.2 metric tons.
Who is responsible for maintaining BEEVILLE LOOP?
BEEVILLE LOOP is owned and maintained by County Highway Agency.
How old is BEEVILLE LOOP and does age affect safety?
BEEVILLE LOOP was built in 2010, making it 16 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.