Preview: automated baseline. Built automatically from federal data and not yet checked by hand. Check every figure against your own records before you use it in a plan.

Clallam County, WA

Risk-assessment baseline packet. County area 53009. Release 2026-10, data as of 2026-09-28.

Download the packet

PDF: PDF, for printing and reading. Word: Word document, tables ready to paste into a plan. Excel: Excel workbook, one sheet per section, full tables. JSON: Packet data (JSON), for analysts. Full packet as a web page. File manifest (checksums, source versions).

Plan clock

Approved, expires 2030-09-30

Plan
Clallam County Hazard Mitigation Plan (2025) (FEMA plan 110577)
Approved
2025-10-01
Expires
2030-09-30
As of
2026-09-28
Days
1,463 days to expiry

Map group: Covered beyond 24 months.

What changed since your last plan (approved 2025-10-01)

New federal declarations
EM-3629-WA, DR-4906-WA (2 declaration rows; 1 counted incident)
Storm Events records since approval
0 (data through 2026-06-30)
Repetitive loss now
FMA RL 0, SRL 1 (44 CFR 77.2); any definition: 6
Repeat-flood change
First release: no prior release to compare.

Plan status for every jurisdiction in the plan

8 jurisdictions. Each row is that jurisdiction's own plan clock. Notes include other approved plans FEMA lists for the same jurisdiction.

JurisdictionTypeStatusPlanApprovedExpiresDays to expirynegative = days since expiryUpdate underwayNotes
Clallam CountyCountyApproved, expires 2030-09-30Clallam County Hazard Mitigation Plan (2025) (FEMA plan 110577)2025-10-012030-09-301,463
Forks cityCityPlan 110577 approved 2025-10-01, pending adoption here; not yet eligibleClallam County Hazard Mitigation Plan (2025) (FEMA plan 110577), pending adoption here2025-10-01 by FEMA; not yet adopted here2030-09-30 once adoptedFEMA tracker shows a plan approvable pending adoptionNot yet eligible: adopt the approved plan.
Port Angeles cityCityApproved, expires 2030-09-30Clallam County Hazard Mitigation Plan (2025) (FEMA plan 110577)2025-10-012030-09-301,463
Sequim cityCityApproved, expires 2030-09-30Clallam County Hazard Mitigation Plan (2025) (FEMA plan 110577)2025-10-012030-09-301,463
Crescent School DistrictSchool/School DistrictNo approved plan on record. Approvable pending adoption, not yet eligiblenonenonenoneFEMA tracker shows a plan approvable pending adoptionNot yet eligible: adopt the approved plan.
Other (Peninsula College)College/UniversityPlan 110577 approved 2025-10-01, pending adoption here; not yet eligibleClallam County Hazard Mitigation Plan (2025) (FEMA plan 110577), pending adoption here2025-10-01 by FEMA; not yet adopted here2030-09-30 once adoptedFEMA tracker shows a plan approvable pending adoptionNot yet eligible: adopt the approved plan.
Other (Port of Port Angeles)Highway/Port/RailApproved, expires 2030-09-30Clallam County Hazard Mitigation Plan (2025) (FEMA plan 110577)2025-10-012030-09-301,463
Other (Public Utility District)Electric/Power AuthorityPlan 110577 approved 2025-10-01, pending adoption here; not yet eligibleClallam County Hazard Mitigation Plan (2025) (FEMA plan 110577), pending adoption here2025-10-01 by FEMA; not yet adopted here2030-09-30 once adoptedFEMA tracker shows a plan approvable pending adoptionNot yet eligible: adopt the approved plan.

Plan 110577 lists 2 other participants not on this page. Not covered by it yet: Jamestown S'Klallam Tribe (approvable pending adoption, not yet adopted); Lower Elwha Tribal Community (approvable pending adoption, not yet adopted).

State plan status and tribal plans in this state: see the state page.

What the packet contains

Sections in FEMA checklist order. Each heading names the review item its tables support; whether the item is satisfied is decided by the plan and its reviewers. Full tables are in the downloads above.

Supports B1-a Hazards

17 of the 18 National Risk Index hazards apply here; omission evidence is shown only where NRI rates a hazard "Not Applicable", no federal declaration names it and Storm Events has no record of it since 1996.

Highest expected annual loss (NRI, modeled): Earthquake, Inland Flooding and Tsunami.

Also check locally (not covered by NRI): dam failure (incl. upstream dams), levee failure, flash flood as its own subtype, ice jams, debris flows, erosion (riverine and coastal), land subsidence and sinkholes and expansive soils.

Check your state hazard mitigation plan's hazard list for this county; explain any hazard you drop.

Supports B1-b Location

  • Avalanche, Earthquake, Hurricane, Landslide, Tornado, Tsunami, Volcanic Activity and Wildfire: Census tract rating counts from the National Risk Index tract table (see B1-f). Tract maps and place names are not in this packet.
  • Coastal Flooding and Inland Flooding: The FEMA Flood Insurance Rate Map (FIRM) is the required location source for flooding. See the FEMA Flood Map Service Center (https://msc.fema.gov) for this county.
  • Cold Wave, Drought, Hail, Heat Wave, Ice Storm, Lightning, Strong Wind and Winter Weather: Affects the whole planning area; national data do not distinguish locations within the county. Confirm locally.

Supports B1-c Extent

Storm Events records for 9 of 20 hazard groups, with the scale, observed range and worst recorded event for each; the others say local data required.

Supports B1-d Previous occurrences

30 federal declaration rows for this area (25 counted incidents), each with type, dates and county Public Assistance dollars.

New since the last plan (approved 2025-10-01): DR-4906-WA and EM-3629-WA.

4 statewide declarations listed separately.

Hazards with no recorded events are stated as such (6 of 18).

Storm Events history: 207 records (notable ones in the PDF, all of them in the Excel file).

Supports B1-e Probability

FEMA annualized frequency (modeled) for each hazard, with a descriptor from a scale defined in the packet.

  • Highly likely: Coastal Flooding, Landslide and Lightning
  • Likely: Cold Wave, Heat Wave, Inland Flooding and Winter Weather
  • Possible: Avalanche, Drought and Tornado
  • Unlikely: Hail, Strong Wind and Volcanic Activity

Historical frequency by intensity band (tornado, hail, wind): 9 bands from Storm Events.

Supports B1-f Variation across the planning area

Range of census tract risk scores within the area for 18 hazards (24 tracts; rated tracts only).

4 member jurisdictions: plan clock, repeat-flood count, Public Assistance dollars and event records naming the place (starter, confirm locally).

Supports B2-a, B2-b Assets and impacts

Local data required

County-level starter. The plan must describe impacts for each participant and its own assets.

Storm Events damage since 2025-10-01: none reported in county-coded records (0 records); none reported reported for the zone (0 zone records). Data through 2026-06-30; nominal dollars.

Checklist of what to gather locally: Critical facilities and lifelines per hazard; A problem statement per participant per hazard; Changes in development in hazard-prone areas since the last approval, or a statement of none (E1-a); Future assets.

Supports B2-a Context

Population 77,054; building value $16,971,117,121 and agriculture value $15,479,906 (total, not at risk).

National Risk Index rating Relatively Moderate; social vulnerability Relatively High; community resilience Relatively High.

Supports B2-c Repetitive loss

Repetitive-loss properties, FMA definition (44 CFR 77.2): 0 repetitive loss, 1 severe repetitive loss. NFIP insurance definition: 6 and 1.

Mitigated 0; insured 1; NFIP data as of 2026-08-02. Counts by occupancy and for each member community are in the packet.

Releases

Monthly releases are planned (not yet running); files for a release never change. Earlier releases will be listed here with what changed between them. All releases.

Cite this

Hazard Plain (2026). Clallam County, WA: risk-assessment baseline packet, release 2026-10 (data as of 2026-09-28; County area 53009). Preview: automated baseline. https://hazardplain.org/wa/53009/ Built from FEMA OpenFEMA, the FEMA National Risk Index and NOAA NCEI Storm Events; source versions in the packet's Sources list.

Source citations for the plan's bibliography (8)

How this packet is built, its sources and its limits