FHWA NBI 2024 Inspection record Public-domain dataset

SR 500

Carrying SR 500 over I-205

3.8 N JCT SR 14, Clark, Washington

Data updated May 2026

FHWA NBI record, refreshed with each annual release.

Unknown

Bridge Snapshot: SR 500

The SR 500 bridge in Clark, Washington carries SR 500 over I-205. It was built in 1973, making it 53 years old today. The structure is built primarily of prestressed concrete continuous. Daily traffic averages 64,630 vehicles, placing it in the heavily-trafficked tier of Washington bridges.

The latest FHWA inspection records show limited component ratings on file. The weakest component sits in unrated condition. None of this bridge's reported major components fall into the Poor condition range.

Sourced from the FHWA National Bridge Inventory. See our methodology for refresh cadence and NBI release vintage.

How SR 500 compares

228
Bridges in Clark · 8 in Poor condition

Live comparison across Washington.

Historical Sufficiency Rating

PlainBridge-computed
90.4 / 100 - historical 80–100 band
Structural adequacy /55
53.7
Serviceability /30
28.6
Essentiality /15
8.2
Special reductions
0

FHWA discontinued this calculated item; it does not determine current condition, funding eligibility, posting, or closure. How the historical reference is calculated.

Condition Ratings

Overall Condition
Unrated

Full 0–9 scale + sufficiency-rating breakdown: how condition ratings work.

Structural Details

Year Built
1973
Material
Prestressed Concrete Continuous
Avg Daily Traffic
64,630 vehicles/day
Structure Number
0009214B0000000

How to read this record

This page shows what the last federal inspection recorded, not whether SR 500 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 SR 500 against other structures in Clark 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 SR 500?

SR 500 in Clark, Washington on the FHWA's 0–9 scale.

How often is SR 500 inspected?

SR 500'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 64,630 vehicles per day.

What does “structurally deficient” mean in older bridge reports?

FHWA retired that reported status beginning with the 2018 archive. SR 500 is currently shown as unrated condition from its component ratings; that category is not a live closure or safety decision.

What is the inventory load rating for SR 500?

An inventory load rating is not recorded for SR 500.

Who is responsible for maintaining SR 500?

Ownership is not specified for SR 500 in the NBI.

How old is SR 500 and does age affect safety?

SR 500 was built in 1973, making it 53 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.

Data sourced from the Federal Highway Administration National Bridge Inventory. See our methodology for details. Retrieved and formatted by PlainBridges

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.