Design Events: What the Code Assumes Will Happen to the House
Why this matters
Every house in your service area was built, at least on paper, to survive a specific bad day: a wind speed, a flood height, a ground shaking level, a snow depth, an ember storm. That bad day is called the design event, and the little details that carry the house through it (a hurricane tie, the height of an equipment stand, the screen on a crawlspace vent, a footing below the frost line) are exactly the parts a service call moves. A tech who knows what event the house was designed against can tell which of those details matter on this street, and can answer the customer who says "it made it through the last storm, it's fine" with something better than a shrug.
What a design event is
A design event is the specific, quantified hazard a building is designed to resist without failing. It is not the worst thing that could ever happen. It is a chosen level of a hazard, usually defined by how rarely it is expected to occur, that society has agreed a house should survive.
Each hazard has its own measure:
- Wind: a design wind speed, a 3-second gust at 33 feet above open ground.
- Flood: the base flood, the flood with a 1 percent chance of being equaled or exceeded in any year, and its height, the base flood elevation (BFE). A local ordinance often adds freeboard, extra height above the BFE, to set the design flood elevation.
- Earthquake: a seismic design category (SDC), a letter from A to E that rolls up expected ground shaking and soil.
- Snow: a ground snow load in pounds per square foot, from which the roof load is derived.
- Wildfire: not a number but a mapped exposure, a fire hazard severity or wildland-urban interface zone. See related: The Wildland-Urban Interface Code in Plain Terms.
- Freeze: frost line depth and design temperatures, which set footing depth and where pipes may run.
The key word is chosen. The code does not design against the storm of record. It designs against a statistically defined event, and the recurrence chosen differs by hazard.
Where the residential code takes its numbers
The International Residential Code (IRC) does not invent hazard values. Most come from ASCE 7, Minimum Design Loads and Associated Criteria for Buildings and Other Structures, a consensus standard published by the American Society of Civil Engineers. ASCE 7 binds nobody on its own. It becomes law only when a state or local building code adopts it by reference, and the IRC, as adopted by your jurisdiction, is how it reaches a house.
The IRC then asks each jurisdiction to fill in a local table of climatic and geographic design criteria (Table R301.2 in the 2021 edition; the numbering has moved between editions, with older editions splitting it into numbered parts). The building department publishes its filled-in version, usually on a one-page handout or the permit portal. That table is the most useful single page a field shop in a hazard area can keep. Finding it for your own jurisdiction belongs to the Place group of this library; what follows is how to read it.
CLIMATIC AND GEOGRAPHIC DESIGN CRITERIA
(illustrative jurisdiction, IRC as adopted)
Ground snow load ........... 25 psf
Wind design speed (Vult) ... 130 mph
Topographic effects ........ Yes, see map
Special wind region ........ No
Windborne debris zone ...... No
Seismic design category .... C
Frost line depth ........... 24 in
Winter design temp ......... 18 F
Ice barrier underlayment ... Yes
Flood hazards .............. FIRM dated, panel list
Wildland-urban interface ... Mapped areas, see ord.
Three lines on that sheet trip people up:
- Topographic effects: Yes means a house on a ridge, an escarpment or the crest of a hill sees higher wind than the mapped speed, sometimes much higher. Two houses a block apart can have different real exposure.
- Flood hazards is not a height. It points to the Flood Insurance Rate Map (FIRM) and its date. The height comes off the map for that parcel.
- Seismic design category C in a residential table matters because the IRC's detailed seismic provisions for one- and two-family dwellings switch on at SDC D0 and above, while townhouses pick them up at C. A category letter is a switch, not just a label.
How rare each design event is
The recurrence is where "the house survived the last storm" falls apart, so know the rough basis for each.
| Hazard | Basis in current practice | What it means in plain terms |
|---|---|---|
| Flood | 1 percent annual chance (the "100-year" flood), NFIP and IRC R322 as adopted | About a 26 percent chance of at least one over a 30-year mortgage |
| Wind (ordinary house) | Ultimate design speed, a mean recurrence of roughly 700 years in ASCE 7-10 and 7-16 for Risk Category II | Rare at any one house, but the map value is reached somewhere almost every hurricane season |
| Earthquake | Maximum considered earthquake, about a 2 percent chance in 50 years | A long-return event the house must survive without collapse, not without damage |
| Snow | Historically a 50-year ground snow value; ASCE 7-22 moved to a reliability-based map | Check which edition your table was built from |
The 26 percent figure is arithmetic you can show a customer: the chance of no 1 percent flood in a year is 0.99, so the chance of none in 30 years is 0.99 multiplied by itself 30 times, about 0.74, leaving about 0.26 for at least one. "The 100-year flood" is a name for a probability, not a schedule.
Ultimate versus allowable: one house, two wind numbers
Since the 2015 edition, the IRC has published ultimate design wind speeds (Vult), which come straight from ASCE 7-10 and later. Older codes, and some product literature still in circulation, used a lower nominal or allowable stress design speed (Vasd). The two describe the same wind on different bases, and the IRC carries a conversion table (R301.2.1.3 in the 2018 edition): Vasd equals Vult multiplied by the square root of 0.6, about 0.775.
So a house described as "a 130 mph zone" under the current code was "about a 100 mph zone" under the old basis. Neither number moved the hazard. This matters when a homeowner or a salesperson tells you equipment is "rated to 100 mph": ask which basis, because a tie-down rated against a 100 mph allowable value and one rated against a 100 mph ultimate value are not the same product. The owner of rating literacy for outdoor equipment is the sibling on high-wind installations; here, the point is that a wind number without its basis is not yet a number.
Worked example: "it survived the last storm"
A homeowner in the illustrative jurisdiction above, 130 mph Vult, has a condenser on a roof-adjacent platform. The service tech notes the original tie-downs are rusted through and recommends replacement. The customer pushes back: the house came through a hurricane two years ago with peak gusts reported at 85 mph at the nearest station, and nothing moved.
Work it through.
Step 1, put both speeds on the same basis. The 85 mph figure is a measured 3-second gust at a reporting station, which is the same kind of quantity as the ultimate design speed (both are 3-second gusts at 33 feet in open terrain), so it compares directly to 130 mph. If the customer had quoted an old "100 mph rated" figure instead, the first move would be the 0.775 conversion before comparing anything.
Step 2, compare pressure, not speed. Wind load on equipment scales with the square of velocity. 85 divided by 130 is 0.654; squared, 0.43. The storm delivered about 43 percent of the design pressure.
Step 3, read what the survival proves. The tie-downs, rusted as they were, held 43 percent of design load once. That says nothing about 100 percent. A connection with half its section lost to corrosion can carry 43 percent and fail at 60.
Step 4, check the station against the site. The station is at an airport on flat ground. The house sits on a ridge, and the table says topographic effects apply. Speed-up over a ridge means the gust at the platform was probably higher than 85 mph, so the tie-downs may have seen more than 43 percent of the mapped load. But the same ridge raises the design load for that site above the mapped value too, by the topographic factor the engineer would apply. Neither number is known precisely from the curb, and the conclusion does not depend on it: the storm was a partial test, well short of the event the connection exists for.
Step 5, what the tech says. "The storm you had was a bit under half the push this house is designed for. Your tie-downs got through that while already rusted. The one they're built for is more than twice as strong." That is accurate, uses the customer's own storm, and does not overclaim.
What changes the answer. If the reported gusts had been near the design speed, survival would be real evidence for the structure, though still weak evidence for a part that has corroded since. And if the platform is inside a special wind region or windborne debris zone on the table, the equipment requirements are stricter again and the replacement tie-down has to be rated for that region, not just for the mapped speed.
Why surviving proves so little, in general
The worked example generalizes into four reasons, each true across hazards:
- Most events are smaller than the design event. By construction, the design event is rare. The storms, floods and quakes a house has actually met are mostly well below it, so "it survived" is usually a test at a fraction of the load.
- Load rises faster than the headline number. Wind pressure goes with speed squared. Flood force rises sharply with depth and much more with velocity and debris. A modest step in the headline number is a large step in load.
- The house has changed since. Corrosion, rot, a cut strap, a replaced vent, a condenser set back lower: the house that survived the last event is not the house that will meet the next one. That failure pattern belongs to the sibling card on how service work removes hazard resistance.
- The maps change. FIRMs are revised, ASCE 7 is reissued about every six years, and wildfire hazard maps have been redrawn in several western states recently. A house compliant when built may sit in a stricter zone today, and new work is judged against the code in force when the permit is pulled, not the one it was built under.
What a tech should actually carry
You do not need to compute loads. You need four facts per service area, and the habit of checking them before you touch the details that carry them:
- The design wind speed and whether topographic effects, special wind regions or debris zones apply.
- Whether the address is in a mapped flood hazard area, and the design flood elevation if it is.
- The seismic design category.
- Whether the address is in a mapped wildfire zone.
When a job touches a strap, a pad height, a vent, a seismic brace or a roof penetration, those four facts decide whether the detail is decoration or the reason the house stands. Where the call genuinely needs a load calculation (a new rooftop unit on an existing roof, a platform for elevated equipment, a reframed opening), stop at the fork and route it to a licensed engineer or the building department, and walk in with the address, the design criteria table, photographs of the existing connection, and the weight and dimensions of what is going on.
References
- ASCE 7, Minimum Design Loads and Associated Criteria for Buildings and Other Structures (7-10, 7-16 and 7-22 editions), binding only where adopted through the building code
- International Residential Code, Section R301.2 and Table R301.2 (2021 edition numbering), and R322 flood-resistant construction, as adopted by your jurisdiction
- FEMA, National Flood Insurance Program and Flood Insurance Rate Maps
- See related: How Service Work Quietly Removes a House's Hazard Resistance
- See related: The Wildland-Urban Interface Code in Plain Terms