9.1 Design Storms, IDF, and Time of Concentration

Why This Topic Matters

The PE Civil WRE hydrology domain starts before any runoff equation is used. A storm problem may give an intensity-duration-frequency (IDF) table, a rainfall hyetograph, a return period, a drainage map, or a flow-path sketch. Your first job is to decide what storm quantity the later calculation needs: peak intensity, total rainfall depth, rainfall excess, or a full time pattern. Picking the wrong quantity is the single most common way examinees lose an otherwise easy hydrology point.

The current NCEES PE Civil WRE specification, effective April 1, 2024, defines an 80-question, 9-hour closed-book CBT delivered with the searchable NCEES PE Civil Reference Handbook. Hydrology is listed as roughly an 8-12 question slice and includes storm characteristics, storm frequency, rainfall measurement and distribution, IDF, time of concentration, Rational and SCS/NRCS runoff, hydrographs, depletions, and stormwater management. Expect both quick peak-flow setup items and multi-step hydrograph logic.

Design-Storm Vocabulary

A 25-year storm has a 4% AEP; a 50-year storm, 2%. The chance of at least one exceedance over n years is the risk equation R = 1 - (1 - AEP)^n. For a 1% AEP event over a 30-year service life the risk is about 26%, and for a 2% AEP event over 30 years it is roughly 45%. This is why design language stays probabilistic: "100-year" never guarantees a 100-year quiet spell after the event occurs.

Reading IDF Data

IDF data converts a selected frequency and duration into a rainfall intensity in inches per hour. For Rational Method peak discharge, the standard assumption is that the critical storm duration equals the watershed time of concentration, so every contributing point reaches the outlet simultaneously and the whole area contributes at the peak. If the computed Tc is 27 minutes and the table lists 25 and 30 minutes, interpolate only when the problem expects it; otherwise use the nearest listed value or the stated design convention.

Watch the chart axes: log-log IDF plots compress short durations, so a 5-minute read can be far higher than a 60-minute read for the same frequency.

For NRCS or routing problems, IDF intensity alone is rarely enough. You may need total rainfall depth for a 24-hour storm, a dimensionless distribution (NRCS Type I, IA, II, or III), or rainfall increments by time step. Always ask whether the problem wants a single peak rate or volume and timing.

Time of Concentration

Time of concentration (Tc) is the travel time from the hydraulically most remote relevant point in the drainage area to the point of analysis. It is not automatically the longest straight-line distance: a paved path feeding a storm sewer may deliver water faster than a shorter grassy swale, and a nearly flat overland segment often dominates the clock.

A typical Tc calculation breaks the controlling path into segments:

1. Sheet flow — shallow overland flow near the upstream divide; the NRCS sheet-flow equation is very sensitive to Manning roughness n, slope, and the 2-year 24-hour rainfall, and is normally capped at about 100 ft of length.
2. Shallow concentrated flow — flow in rills, gutters, or small swales; velocity is read from paved vs. unpaved curves, then time = length / velocity.
3. Channel or pipe flow — travel time from length divided by velocity, with velocity from Manning's equation using hydraulic radius, slope, and roughness, or from pipe hydraulics.

The workflow is: delineate the drainage area, identify the controlling flow path, split it into hydraulic segments, compute travel time for each, sum the segment times, then use that Tc to select storm intensity or hydrograph lag. Keep units consistent: minutes for IDF lookup, seconds for hydraulic velocity work, and hours for unit-hydrograph timing when the formula requires hours.

Exam Workflow and Common Traps

Under timed conditions: (1) identify whether the output is intensity, peak discharge, runoff depth, hydrograph peak, or routed outflow; (2) select the storm frequency or AEP given; (3) compute or confirm Tc, honoring any stated minimum (many local codes floor Tc at 5-10 minutes); (4) read IDF at the design frequency and correct duration; (5) sanity-check that the intensity is plausible for that duration and region.

Classic traps: using a 24-hour rainfall depth as if it were an IDF intensity, treating a return period as a fixed calendar schedule, changing imperviousness without recomputing Tc, applying a pipe velocity before the pipe size or slope is established, and floor-ing Tc so low that intensity (and therefore peak flow) is unrealistically inflated. A short Tc is conservative for peak flow but punishing for storage volume, so the "safe" assumption depends on the design decision.