A scour evaluation is a substantial document and most of it is supporting material. The conclusions rest on four numbers and one comparison.
This is written for the person who has to act on it rather than the person who produced it.
The four numbers
1. Long-term degradation. How much the channel bed is expected to lower over the remaining life of the structure, independent of any flood.
2. Contraction scour. How much the bed lowers across the whole opening during the design event, because the opening is narrower than the natural flood width.
3. Local scour. The depth of the hole at each individual pier and abutment during the design event.
4. Total scour, which is those three added, giving a predicted bed elevation at each foundation.
Then the comparison: total scour elevation against foundation elevation. If the scour goes below the foundation, the bridge is scour critical. If it does not, it is not. Everything else in the report exists to produce those numbers.
Contraction, local, and degradation scour covers why they are computed separately.
The assumptions that govern the answer
Six things determine whether those numbers mean anything, and each is worth finding in the document.
The design event
Usually a 100-year flood for the scour computation, often with a check at a larger event. Two questions:
- What discharge was used, and where did it come from? A gauged record, a regional regression, a watershed model?
- How old is the hydrology? Design discharges get revised. An evaluation built on a superseded estimate is computing the right thing about the wrong flood.
The foundation elevation
This is the number the whole conclusion turns on, and it is the one most often uncertain.
- Is the foundation depth known from as-built records, or inferred?
- If inferred, from what?
An evaluation on an assumed foundation depth is a conditional result. A bridge with genuinely unknown foundations is in a separate category and is coded as such — see scour critical bridges.
The bed material
Scour computations are sensitive to grain size, and to whether the material is cohesive or non-cohesive.
- Was a sample taken, or was the material assumed?
- Was the bed treated as cohesive? Cohesive materials scour more slowly, and an evaluation that credits cohesion is assuming the event is short enough for that to matter.
The hydraulic model
- What model, and how was it calibrated? A HEC-RAS model calibrated against an observed high-water mark is a different quality of input from an uncalibrated one.
- Where were velocities taken from? Depth-averaged section velocity is not the local velocity at a pier. The answer bank covers this distinction under design and hydraulics.
- What roughness and geometry were used, and how old is the survey?
Debris
- Was debris loading considered? On a stream that delivers woody debris, a raft against a pier is hydraulically a much wider pier, and effective width drives local scour strongly.
- If debris was not considered, and the site has a debris history, the local scour figures are optimistic.
Pier alignment
- At what flow was alignment assessed? A pier square to the low-flow channel can be badly skewed at flood stage, when the flow crosses the floodplain on a different path.
Reading the conclusion
Evaluations generally land in one of a few positions:
Scour critical. Computed scour reaches or passes the foundation. This triggers a plan of action: monitoring, countermeasures, or both.
Stable. Computed scour stays above the foundation with margin. Note the size of the margin — a bridge that clears by a small amount on a degrading channel is not stable for long.
Unknown foundations. The evaluation cannot conclude because the depth is not known. Common on older structures. The options are foundation investigation, or managing the bridge as though it were scour critical.
Stable subject to conditions, for example on the basis of countermeasures being installed and maintained. Check what the condition was and whether it was met.
Questions worth asking the engineer
- How much margin is there between computed scour and the foundation?
- How sensitive is the answer to bed material and to the discharge estimate?
- What is the degradation trend from historical survey, rather than the estimate?
- Was debris considered, and does this stream deliver it?
- If countermeasures are recommended, what plan extent do they assume, and was that computed or nominal?
- What monitoring does this assume, and is it happening?
- What would change the conclusion?
That last one is the most useful. If the answer is “a lower foundation than we assumed” or “one more foot of degradation,” you know what to watch.
What an evaluation does not tell you
Present condition. It is a prediction under a design event, not a survey. Actual bed elevation today comes from soundings, not from the report.
Whether a hole is currently there. Scour is deepest at the flood peak and often refills as flow drops — see what is scour. The bed you can measure now may be loose infill over a foundation that was briefly exposed.
Whether existing protection is performing. That is an inspection question. Post-flood scour inspection covers what to look at.
What to install. It sizes the problem. The scour countermeasure families covers the response options.
Where to go next
- Scour critical bridges for what the rating means and what follows
- Bridge pier scour and abutment scour for the mechanisms
- Design and sizing for what data a countermeasure calculation needs
- DOT and municipal for agency process
We are a supplier, not the engineer of record. If an evaluation recommends countermeasures and you want a read on what the armor scope implies, send the report and the bridge geometry through the quote form.