Hazard Plain Automated baseline

Daggett County, UT

Risk-assessment baseline packet

County FIPS:
49009
Release:
2026-10
Data as of:
2026-09-30
Storm Events data through:
2026-06-30

Hazard Plain is an independent product built from public federal data. It is not a FEMA document and is not reviewed or endorsed by FEMA or any state agency.

Hazard Plain release 2026-10, as of 2026-09-30.

Summary

Plan status as of 2026-09-30: Approved, expires 2030-09-08. Plan: Uintah Basin Region 5, UT Hazard Mitigation Plan 2025 (FEMA plan 109462), approved 2025-09-09.

Since the plan was approved on 2025-09-09: no new hazard declaration and 16 NOAA Storm Events records; details under "What changed since your last plan".

Highest expected annual loss (FEMA National Risk Index, modeled total; see B1-a): Avalanche ($1,370,001 a year), Lightning ($538,931) and Wildfire ($304,481).

The tables that follow are organized by the items of FEMA's Local Mitigation Plan Review Tool, Element B (B1-a to B2-c); each heading says which item its tables support.

Plan clock

Status:
Approved, expires 2030-09-08
Plan:
Uintah Basin Region 5, UT Hazard Mitigation Plan 2025 (FEMA plan 109462)
Approved:
2025-09-09
Days to expiry:
1,439

What changed since your last plan (approved 2025-09-09)

New federal declarations:
none
Storm Events records since approval:
16 records (data through 2026-06-30)
Repetitive loss now:
FMA RL 0, SRL 0 (44 CFR 77.2); any definition: 0
Repeat-flood change:
this release sets the baseline count.

Sources: 1, 2, 4, 6 (numbered list at the end)

Plan status for every jurisdiction listed in this county

Source: 1

JurisdictionTypeStatusPlanApprovedExpiresDays to expirynegative = days since expiryNotes
Daggett CountyCountyApproved, expires 2030-09-08Uintah Basin Region 5, UT Hazard Mitigation Plan 2025 (FEMA plan 109462)2025-09-092030-09-081,439this jurisdiction approved 2026-04-29
Dutch John townTownApproved, expires 2030-09-08Uintah Basin Region 5, UT Hazard Mitigation Plan 2025 (FEMA plan 109462)2025-09-092030-09-081,439this jurisdiction approved 2026-04-29
Manila townTownApproved, expires 2030-09-08Uintah Basin Region 5, UT Hazard Mitigation Plan 2025 (FEMA plan 109462)2025-09-092030-09-081,439this jurisdiction approved 2026-04-29
Daggett School DistrictSchool/School DistrictApproved, expires 2030-09-08Uintah Basin Region 5, UT Hazard Mitigation Plan 2025 (FEMA plan 109462)2025-09-092030-09-081,439this jurisdiction approved 2026-09-23

Plan 109462 covers 9 other participants, named in the Excel file.

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

Supports FEMA checklist item B1-a: hazard identification

Hazards NRI does not cover (local data needed)

  • 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
  • expansive soils

The 18 National Risk Index hazards, ranked by expected annual loss (EAL)

Sources: 5, 6

Rank by EALHazardNRI risk ratingEAL ratingEAL buildingsmodeled dollars per yearEAL agriculturemodeled dollars per yearCost of expected deaths and injuriesFEMA's dollar value per year, not property damageEAL total (see note)modeled dollars per yearStorm Events records, 1996 to 2026-06-30countWhy this hazard can be left outNRI Not Applicable, no declaration and no Storm Events record since 1996Storm Events coverage note
1AvalancheRelatively HighRelatively Moderate$1n/a$1,370,000$1,370,0011
2LightningRelatively ModerateRelatively Moderate$717n/a$538,214$538,93110
3WildfireRelatively LowRelatively Low$298,950$18$5,513$304,4819
4Inland FloodingVery LowVery Low$192,060$0$0$192,06012
5Winter WeatherRelatively LowRelatively Low$7,689$11$18,452$26,152372
6EarthquakeVery LowVery Low$22,023n/a$2,485$24,508Storm Events does not record earthquakes.
7Cold WaveVery LowVery Low$34$293$4,730$5,0583
8HailVery LowVery Low$4,826$71$89$4,98611
9TornadoVery LowVery Low$2,187$11$1,436$3,6342
10DroughtVery LowVery Lown/a$3,628n/a$3,628148
11Strong WindVery LowVery Low$706$33$2,151$2,89010Includes 6 High Wind records (a NOAA non-thunderstorm wind type, outside NRI's Strong Wind definition).
12LandslideVery LowVery Low$171n/a$2,658$2,8291
13Ice StormVery LowVery Low$449n/a$63$5120No recorded events in Storm Events since 1996 (data through 2026-06-30).
14Heat WaveNo RatingNo Expected Annual Losses$0$0$0$00No recorded events in Storm Events since 1996 (data through 2026-06-30).
HurricaneNot ApplicableNot Applicable0NRI rates hurricane Not Applicable for this county, and no counted federal declaration for this county names it (EM-3223-UT names it but is not counted as a local occurrence; see B1-d).No recorded events in Storm Events since 1996 (data through 2026-06-30).

Total = buildings + agriculture + population equivalence; FEMA values each expected death (or 10 injuries) at $13.7 million (2024 dollars).

NRI risk rating combines expected annual loss with social vulnerability and community resilience; EAL rating rates expected annual loss alone. Both compare this county with all U.S. counties.

Not applicable to this county per NRI, with no federal declaration and no Storm Events record since 1996: coastal flooding, tsunami and volcanic activity. That is the evidence for leaving them out of the plan.

The state hazard mitigation plan also lists hazards for this county; FEMA asks the plan to explain any hazard it leaves out.

Supports FEMA checklist item B1-b: hazard location

Affects the whole county (national data give no location within it): Cold Wave, Drought, Hail, Heat Wave, Ice Storm, Lightning, Strong Wind and Winter Weather.

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.

NRI rating of the county's single census tract

Source: 5

HazardCensus tractNRI risk rating, score 0 to 100
Avalanchetract 9601 (Relatively Moderate, 84.3)
Earthquaketract 9601 (Relatively Low, 48.4)
Hurricaneno tract has a National Risk Index rating for this hazard
Landslidetract 9601 (Relatively Moderate, 95.6)
Tornadotract 9601 (Very Low, 9.8)
Wildfiretract 9601 (Relatively High, 97.5)

A tract number is the Census tract number (for example 9601 is Census Tract 9601). FEMA's Resilience Analysis and Planning Tool maps the National Risk Index for every tract: https://www.fema.gov/emergency-managers/practitioners/resilience-analysis-and-planning-tool

Supports FEMA checklist item B1-c: hazard extent

Extent: scale, observed range and worst recorded event per hazard

Sources: 6, 7

HazardScaleRecordscount and yearsObserved rangeWorst recorded eventMost damaging (when different)How it applies to jurisdictionsNote
Avalanchenone (count and damage only)1 record, 2017 (1 zone-level)No damage reported in 1 record.Countywide (zone-level records).
Cold/Wind Chill, Extreme Cold/Wind Chillwind chill3 records, 1998 to 2011 (3 zone-level)2 days to 16 days (median 4 days); 3 with a recorded value16 consecutive days, 2005-12-04 to 2005-12-19, zone-levelCountywide (zone-level records).
Frost/Freeze (outside NRI's Cold Wave definition)crop damage0
DroughtU.S. Drought Monitor scale (D0 to D4)148 records, 2002 to 2026 (148 zone-level)7 days to 1,493 days (median 141 days); 16 with a recorded value1493 days (about 49.0 months), 2002-05-01 to 2006-06-01, a run of 50 consecutive Storm Events drought records, zone-levelCountywide (zone-level records).Storm Events enters a drought at D2 or worse east of the Rockies and D3 or worse from the Rockies west (NWS Instruction 10-1605); NRI drought counts D3 and D4 only.
EarthquakeModified Mercalli (local data)0Storm Events does not record earthquakes; the USGS earthquake catalog is the source.
Hailhail size (inches)12 records, 1980 to 20110.75 in to 1.75 in (median 1.25 in); 12 with a recorded value1.75 in hail, 2009-08-06; same size also recorded on 1980-08-15, 2007-08-18Event records naming jurisdictions in the plan: Manila town (6 records), Dutch John town (5 records).
Excessive Heat, Heatheat index (in event narratives)0
Hurricane, Tropical Storm, Tropical DepressionSaffir-Simpson0Storm Events files every zone of a storm's episode under the storm's type; flooding from the storm is filed as Flood or Flash Flood records.
Ice StormSperry-Piltz ice scale (local data)0
Flash Flood, Flood, Lakeshore Flooddamage and flood days (flood depth: FIRM)12 records, 1996 to 2017 (1 zone-level)Flash Flood, 2014-08-26, $100,000 property; $0 crops (2014 dollars)Event records naming jurisdictions in the plan: Dutch John town (7 records), Manila town (3 records). Zone-level records (1) apply countywide.Flood depth: see the FEMA Flood Insurance Rate Map. Storm Events damage is often $0 or blank for floods, major ones included; FEMA Public Assistance by declaration (B1-d) shows which floods cost the most.
Debris Flownone (count and damage only)1 record, 2005 (1 zone-level)Debris Flow, 2005-08-09, $500 property; crops not reported (2005 dollars); NWS zone UTZ023Countywide (zone-level records).
Lightningannualized frequency (the measure FEMA's Local Mitigation Planning Handbook names)10 records, 2004 to 2016Lightning, 2016-07-22, $0 property; $0 crops (2016 dollars), 1 direct death, 1 direct injuryLightning, 2004-06-20, $2,000 property; crops not reported (2004 dollars)Event records naming jurisdictions in the plan: Dutch John town (5 records), Manila town (4 records).Storm Events lists lightning with damage or casualties.
High Wind and Strong Wind (outside NRI's Strong Wind definition)wind speed (kt and mph)6 records, 2000 to 2026 (6 zone-level)45 kt (52 mph) to 68 kt (78 mph) (median 65 kt (75 mph)); 6 with a recorded value68 kt (78 mph) measured gust, High Wind, 2023-02-15; NWS zone UTZ023Countywide (zone-level records).
Thunderstorm Windwind speed (kt and mph)4 records, 2007 to 202150 kt (58 mph) to 70 kt (81 mph) (median 61 kt (70 mph)); 4 with a recorded value70 kt (81 mph) estimated gust, Thunderstorm Wind, 2015-06-16Event records naming jurisdictions in the plan: Dutch John town (4 records).
TornadoEnhanced Fujita (Fujita before Feb 2007)2 records, 1999 to 2001F/EF0; 2 with a recorded valueF0 tornado, 2001-08-21, 2 mi within this county, 25 yd wide, damage not reported; same rating, casualties and property damage also recorded on 1999-05-05Event records naming jurisdictions in the plan: Dutch John town (2 records).Before 1996 a tornado is listed once, under the county where it began, with its whole path's rating and length; from 1996 on, each county lists its own segment. Length is not used to rank tornadoes (see Methods).
Wildfireacres burned (local data)9 records, 2002 to 2024 (7 zone-level)Wildfire, 2024-08-01, $0 property; $9,500,000 crops (2024 dollars) (as recorded; larger than this county's annual agriculture value in the National Risk Index (the county or state extension service keeps crop loss records)); NWS zone UTZ023Event records naming jurisdictions in the plan: Dutch John town (2 records). Zone-level records (7) apply countywide.
Winter Storm, Heavy Snow, Blizzard, Lake-Effect Snow, Winter Weather, Sleetnone in data (snowfall: local data)372 records, 1997 to 2026 (372 zone-level)No damage reported in 372 records.Countywide (zone-level records).

In event narratives only (local data needed): wind chill, temperature, heat index, ice thickness, acres burned and snow depth; any physical measure of avalanche, debris flow and lightning.

Storm Events records are more complete after 1996; before 1996 only Tornado (from 1950), Hail and Thunderstorm Wind (from 1955) exist. Zone-level records from zones that no NWS zone-county file places in this county (mostly before 2020) are not counted here (the Methods page explains the zone matching).

Dollars are nominal (as reported), labeled with the year; not adjusted for inflation.

Supports FEMA checklist item B1-d: previous occurrences

Federal declarations for this county: 7 declarations covering 4 separate hazard incidents counted in this packet (declarations for the same incident count once; non-natural and evacuation-only declarations are not counted).

Federal disaster declarations for this county

Sources: 1, 2, 3

DeclaredIncident beganFEMA numberTypeTitleMapped hazardCounty Public Assistancefederal share obligated, nominal dollarsNotes
2020-04-042020-01-20DR-4525-UTMajor disasterCOVID-19 PandemicNon-natural, not countedno Public Assistance recorded
2020-03-132020-01-20EM-3478-UTEmergencyCOVID-19Non-natural, not countedno Public Assistance recordedsame incident as DR-4525
2011-08-082011-04-18DR-4011-UTMajor disasterFloodingInland Flooding$7,661.48
2005-09-052005-08-29EM-3223-UTEmergencyHurricane Katrina EvacuationHurricane: evacuation support, not a local hazard event; not countedno Public Assistance recorded
2002-07-012002-06-30FM-2437-UTFire managementUt - Mustang Fire - 07/01/2002Wildfireno Public Assistance recorded
1983-04-301983-04-13DR-680-UTMajor disasterSevere Storms, Landslides & FloodingInland Flooding (primary); also designated: Landslideno Public Assistance recorded
1977-01-201977-01-20EM-3024-UTEmergencyDroughtDroughtno Public Assistance recorded

County Public Assistance: applicants the FEMA record places in this county, including any state agencies FEMA files there; statewide rows are listed on the state page; federal share obligated, nominal dollars.

Previous occurrences by hazard, with explicit no-event rows

Sources: 2, 6, 7

HazardStorm Events records, all years on file(years in the Period column)Since plan approvalrecordsIn the 12 months before plan approvalrecordsLast 5 yearsrecordsDeclared incidents, all yearsseparate disastersDeclared since approvalseparate disastersPeriodStatement
Avalanche1000001996 to 2026-06-30
Cold Wave3000001996 to 2026-06-30
Drought1488326101996 to 2026-06-30
Earthquake000000Storm Events does not record earthquakes; the USGS earthquake catalog is the source.
Hail12000001955 to 2026-06-30
Heat Wave0000001996 to 2026-06-30No recorded events, 1996 to 2026-06-30, NOAA NCEI Storm Events
Hurricane0000001996 to 2026-06-30No recorded events, 1996 to 2026-06-30, NOAA NCEI Storm Events
Ice Storm0000001996 to 2026-06-30No recorded events, 1996 to 2026-06-30, NOAA NCEI Storm Events
Inland Flooding12000201996 to 2026-06-30
Landslide1000101996 to 2026-06-30
Lightning10000001996 to 2026-06-30
Strong Wind10103001955 to 2026-06-30Includes 6 High Wind records.
Tornado2000001950 to 2026-06-30
Wildfire9002101996 to 2026-06-30
Winter Weather3727961001996 to 2026-06-30

Notable Storm Events records

Sources: 1, 6, 7

DateEvent typeMagnitude or extentDamagenominal dollarsDeaths, injuriesdirect onlyLocationFlagsWhy listed
2024-08-01Wildfire$0 property; $9,500,000 crops (zone total, 2024 dollars) (as recorded; larger than this county's annual agriculture value in the National Risk Index (the county or state extension service keeps crop loss records))0, 0NWS zone UTZ023 (EASTERN UINTA MOUNTAINS), zone-levelwithin last 5 yearsB1-c worst recorded: Wildfire
2023-02-15High Wind68 kt (78 mph) measured gust$0 property; $0 crops (zone total, 2023 dollars)0, 0NWS zone UTZ023 (EASTERN UINTA MOUNTAINS), zone-levelwithin last 5 yearsB1-c worst recorded: High Wind and Strong Wind
2016-07-22Lightning$0 property; $0 crops (2016 dollars)1, 1LUCERNE VALLEYdeaths or injuries recorded
2015-06-16Thunderstorm Wind70 kt (81 mph) estimated gust$0 property; $0 crops (2015 dollars)0, 0DUTCH JOHNB1-c worst recorded: Thunderstorm Wind
2014-08-26Flash Flood$100,000 property; $0 crops (2014 dollars)0, 0DUTCH JOHNB1-c worst recorded: Flash Flood, Flood, Lakeshore Flood
2009-08-06Hail1.75 in$80,000 property; $0 crops (2009 dollars)0, 0DUTCH JOHNB1-c worst recorded: Hail
2008-07-22Flash Flood$75,000 property; $10,000 crops (2008 dollars)0, 0MANILAlarge reported damage
2005-12-04Cold/Wind Chilldamage not reported0, 0NWS zone UTZ023 (EASTERN UINTA MOUNTAINS), zone-levelB1-c worst recorded: Cold/Wind Chill, Extreme Cold/Wind Chill
2005-08-09Debris Flow$500 property; crops not reported (zone total, 2005 dollars)0, 0NWS zone UTZ023 (EASTERN UINTA MOUNTAINS), zone-levelB1-c worst recorded: Debris Flow
2004-06-20Lightning$2,000 property; crops not reported (2004 dollars)0, 0MANILAB1-c most damaging: Lightning
2002-05-01Droughtdamage not reported0, 0NWS zone UTZ023 (EASTERN UINTA MOUNTAINS), zone-levelB1-c worst recorded: Drought
2001-08-21TornadoF0, 2 mi within this county, 25 yd widedamage not reported0, 0DUTCH JOHNB1-c worst recorded: Tornado

The full list is in the Excel file, sheet "B1-d Storm Events history" (580 rows).

Location is the place NOAA recorded, as written in its data; it need not be a jurisdiction in this plan.

2 Fire Management declarations (1994-08-06 to 1994-08-06) FEMA filed as Statewide with no county; each names one local fire. Listed on the state page.

Local data needed: state-declared emergencies, from your state emergency management agency (federal data do not include them).

Tribal and special-area declarations in this state are listed on the state page.

Supports FEMA checklist item B1-e: probability of future events

Probability: FEMA annualized frequency and descriptor per hazard

Sources: 5, 6

HazardFEMA annualized frequency (modeled)unit per rowUnitIn plain termsDescriptorDescriptor basisNRI events or days in its record period (hail, wind and tornado are area-weighted, so can be fractional)NRI periodLocationNote
Avalanche0.0667events per yearabout 1 in 15 yearsPossibleFEMA annualized frequency (modeled)21994 to 2023 (30 years)see B1-f
Cold Wave0.158event-days per yearabout 0.158 days per yearLikelyStorm Events event-days in 3 of 30 years, 1996 to 2025 (10%)32005-11-12 to 2024-11-12 (19 years)countywide
Drought104event-days per yearabout 104 days per yearLikelyStorm Events event-days in 19 of 30 years, 1996 to 2025 (63.3%)2,6182000 to 2025 (25.25 years; D3 and D4 only)countywide
Earthquake0.00156annual probability at a locationchance a given location in the county has at least minor-damage shaking in a year: 0.156%not shownmodeledsee B1-fNo descriptor (Storm Events does not record earthquakes).
Hail0.0978events per yearabout 1 in 10 yearsPossibleFEMA annualized frequency (modeled)3.7 (modeled)1986 to 2023 (38 years)countywide
Heat Wave0event-days per yearnone modeledStorm Events event-days in 0 of 30 years, 1996 to 2025 (0%)02005-11-12 to 2024-11-12 (19 years)countywideNo Storm Events heat wave record, 1996 to 2025
Hurricaneevents per year1851 to 2024 (Atlantic)see B1-fNot Applicable in NRI for this county; no descriptor.
Ice Storm0.0149event-days per yearabout 0.0149 days per yearStorm Events event-days in 0 of 30 years, 1996 to 2025 (0%)01946-12-31 to 2014-02-12 (67 years)countywideNo Storm Events ice storm record, 1996 to 2025
Inland Flooding0.393event-days per yearabout 0.393 days per yearLikelyStorm Events event-days in 10 of 30 years, 1996 to 2025 (33.3%)111996 to 2023 (28 years)see B1-f
Landslide0.325events per year (modeled)about 1 in 3 yearsLikelyFEMA annualized frequency (modeled)not shownmodeledsee B1-f
Lightning45.7days per year with a strikeabout 45.7 days per yearHighly likelyFEMA annualized frequency (modeled)not shown1995 to 2023 (29 years; CONUS)countywide
Strong Wind0.173events per yearabout 1 in 6 yearsLikelyFEMA annualized frequency (modeled)71986 to 2023 (38 years)countywide
Tornado0.0293events per yearabout 1 in 34 yearsPossibleFEMA annualized frequency (modeled)not shown1950 to 2023 (EF2+); 1986 to 2023 (EF0-1)see B1-f
Wildfire0.00228annual probability at a locationchance a given location in the county burns in a year: 0.228%LikelyStorm Events records in 6 of 30 years, 1996 to 2025 (20%)not shownmodeledsee B1-f
Winter Weather25.7event-days per yearabout 25.7 days per yearHighly likelyStorm Events event-days in 29 of 30 years, 1996 to 2025 (96.7%)4882005-11-12 to 2024-11-12 (19 years)countywide

FEMA annualized frequency (modeled) is the National Risk Index v1.20 (December 2025) estimate of how often a hazard affects this county in a year; it is not recorded events divided by years, and its unit differs by hazard (events, event-days, or days with a lightning strike per year). For earthquake, wildfire, coastal flooding and tsunami the value is the chance (or number of events) at a location in the county, not across the county, so no "1 in N years" is given and the descriptor comes from Storm Events where it has a record (none for earthquake). The Methods page gives each hazard's method, from FEMA's National Risk Index Technical Documentation v1.20.

Descriptor scale used in this packet (defined per unit)

Sources: 5, 6

UnitDescriptorDefinition
events per yearHighly likely1 or more per year
events per yearLikelyabout once in 1 to 10 years
events per yearPossibleabout once in 10 to 100 years
events per yearUnlikelyless than once in 100 years
annual probabilityLikely10% to under 100% chance in a given year
annual probabilityPossible1% to under 10% chance in a given year
annual probabilityUnlikelyunder 1% chance in a given year
event-days (share of years)Highly likelyevent-days recorded in 90% or more of years
event-days (share of years)Likelyevent-days recorded in 10% to under 90% of years
event-days (share of years)Possibleevent-days recorded in some years but under 10% of years
lightning strike-daysHighly likelycloud-to-ground strikes on 1 or more days per year

Intensity bands: historical frequency (Storm Events)

Source: 6

HazardBandYearsEventscounty-coded recordsYears in periodEvents per yearevents / years
Hail1.00-1.99 in1996 to 20258300.267
Hail2.00 in+1996 to 20250300
Thunderstorm Wind (counted as NRI Strong Wind)50-64 kt1996 to 20252300.0667
Thunderstorm Wind (counted as NRI Strong Wind)65 kt+1996 to 20252300.0667
Thunderstorm Wind (counted as NRI Strong Wind)unmeasured or below 50 kt1996 to 20250300
TornadoEF0-11996 to 20252300.0667
TornadoEF2-31996 to 20250300
TornadoEF4-51996 to 20250300
Tornadounrated (EFU)1996 to 20250300

The bands show how often events of each severity were recorded in this county, to profile how severe events have been (FEMA's probability item asks for the range of intensities).

Hail smaller than 1 inch is not counted: on 2010-01-05 the National Weather Service raised its severe-hail threshold from 3/4 inch to 1 inch, so smaller reports became less common after 2009 (NWS Service Change Notice 09-52). NRI hail frequency uses a 0.75 inch threshold.

Optional: future conditions. Not a required item in the 2025 FEMA Local Mitigation Planning Policy Guide; some states ask for it. The federal Climate Mapping for Resilience and Adaptation (CMRA) site gives county exposure to future climate conditions (https://resilience.climate.gov/).

Supports FEMA checklist item B1-f: hazards that vary across jurisdictions

NRI risk score of the county's single census tract

Source: 5

HazardTract scoreNRI score, 0 to 100Rating
Avalanche84.3Relatively Moderate
Cold Wave21.2Relatively Low
Drought84.4Relatively Low
Earthquake48.4Relatively Low
Hail46.2Relatively Low
Heat WaveNo Rating
HurricaneNot Applicable
Ice Storm6.7Very Low
Inland Flooding10.5Very Low
Landslide95.6Relatively Moderate
Lightning100.0Very High
Strong Wind17.9Very Low
Tornado9.8Very Low
Wildfire97.5Relatively High
Winter Weather95.9Very High

The score ranks a tract against all U.S. tracts (100 = highest). The rating is FEMA's category for the tract's risk value, computed differently, so the two can disagree.

Each jurisdiction (starting figures from federal data)

Sources: 1, 3, 4, 6

JurisdictionTypePlan statusRepetitive lossFMA RL and SRL (44 CFR 77.2); repeat-flood, any definitionPublic Assistance to this jurisdictionFEMA records matched by applicant name; federal share obligated, nominal dollarsEvent records naming this placeall years; since its planNotes
Daggett CountyCountyApproved, expires 2030-09-08FMA RL 0, SRL 0; any 0$7,661.480 total; 0 since its plan
Dutch John townTownApproved, expires 2030-09-08no Public Assistance recorded25 total; 0 since its planNo NFIP community ID on this jurisdiction's plan row.
Manila townTownApproved, expires 2030-09-08FMA RL 0, SRL 0; any 0no Public Assistance recorded13 total; 0 since its plan

Repetitive-loss counts are for whole NFIP communities, which can extend beyond this county (see the note in B2-c).

School districts and special districts get a plan clock row only.

Supports FEMA checklist items B2-a and B2-b: vulnerability and potential impacts

Local data needed

The table below gives county-level starting figures; the plan describes impacts for each jurisdiction and its own assets.

  • Critical facilities and lifelines per hazard
  • A problem statement per jurisdiction per hazard
  • Changes in development in hazard-prone areas since the last approval, or a statement of none (E1-a)
  • Future assets

County-level starter: exposure, expected annual loss and damage since the plan

Sources: 1, 2, 3, 5, 6, 7

HazardBuilding exposuremodeled dollarsAgriculture exposuremodeled dollarsPopulation exposedpeopleEAL buildingsmodeled dollars per yearEAL agriculturemodeled dollars per yearCost of expected deaths and injuriesFEMA's dollar value per year, not property damageEAL as % of exposurebuildings; agriculture where notedStorm Events damage since 2025-09-09county-coded records, property plus crops, nominal dollarsZone-level damage since planproperty plus crops, reported for the zonePublic Assistance since plannominal dollars; see noteNote
Avalanche$640,980n/a10$1n/a$1,370,0000.0002%
Cold Wave$498,431,800$3,094,507927$34$293$4,730under 0.0001%
Droughtn/a$225,935n/an/a$3,628n/a1.61% (agriculture)$0NRI has no building exposure for this hazard; agriculture shown
Earthquake$868,157,345n/a935$22,023n/a$2,4850.00254%
Hail$498,431,800$3,094,507927$4,826$71$890.000968%
Heat Wave$0$00$0$0$0building exposure is 0 in NRI
HurricaneNot Applicable in NRI for this county
Ice Storm$498,431,800n/a927$449n/a$63under 0.0001%
Inland Flooding$498,373,623$00$192,060$0$0n/a (see note)NRI counts the full building value of any census block with some flood loss; this is not the value of buildings in the floodplain. Use local FIRM overlays for B2-a/B2-b.
Landslide$16,086,719n/a20$171n/a$2,6580.00106%
Lightning$498,431,800n/a927$717n/a$538,2140.000144%
Strong Wind$498,431,800$3,094,507927$706$33$2,1510.000142%$0
Tornado$498,431,800$3,094,507927$2,187$11$1,4360.000439%
Wildfire$311,946,330$2,729,586781$298,950$18$5,5130.0958%
Winter Weather$498,431,800$3,094,507927$7,689$11$18,4520.00154%$0

Totals since 2025-09-09 (Storm Events through 2026-06-30): 0 county-coded records, 0 with a damage value recorded (including $0), $0; 16 zone-level records, 16 with a damage value recorded (including $0), $0 reported for the zone; Public Assistance: no counted declaration since the plan.

FEMA does not split Public Assistance by hazard. A declaration mapped to several hazards is listed under each of them with its full amount, so the per-hazard column does not add up to the total; the unit total counts each declaration once.

NRI computes earthquake exposure on its own basis, so it exceeds the county building value in B2-a.

Supports FEMA checklist item B2-a: vulnerability (county context)

County context

Source: 5

MeasureValue
Population927
Building value (total, not at risk)$498,431,800
Agriculture value (total, not at risk)$3,094,507
NRI risk rating (all hazards)Very Low
Expected annual loss, buildings and agriculture, all hazards$533,879
Expected annual loss, population equivalence, all hazards (NRI values each statistical life at $13.7M; a modeled value of expected deaths and injuries, not property damage)$1,945,793
Social vulnerability ratingRelatively Moderate
Community resilience ratingVery High
NRI versionDecember 2025

FEMA's all-hazard expected annual loss adds buildings, agriculture and population equivalence; this table gives the property part and the population-equivalence part as separate rows.

Social vulnerability: higher means people are more likely to be harmed and slower to recover. Community resilience: lower means the community is less able to recover. High social vulnerability and low resilience both raise the NRI risk rating.

Supports FEMA checklist item B2-c: repetitive loss properties

Repetitive loss in this county, both definitions

Sources: 1, 4

DefinitionPropertiesSevere repetitive lossProperties
Repetitive loss, FMA definition (44 CFR 77.2)0Severe repetitive loss, FMA definition (44 CFR 77.2)0
Repetitive loss, NFIP insurance definition0Severe repetitive loss, NFIP insurance definition0

The state NFIP coordinator's list, the source FEMA's Handbook names, often uses the NFIP insurance definition (second row).

Repeat-flood properties: county total and NFIP communities

Sources: 1, 4

ScopeRL, FMApropertiesSRL, FMApropertiesRL, NFIPpropertiesSRL, NFIPpropertiesAny categorypropertiesMitigatedpropertiesCurrently insuredproperties
County total0000000

Repeat-flood properties by jurisdiction in the plan (NFIP community)

Sources: 1, 4

JurisdictionNFIP community IDRL, FMApropertiesSRL, FMApropertiesRL, NFIPpropertiesSRL, NFIPpropertiesAny categorypropertiesMitigatedpropertiesCurrently insuredproperties
Daggett County4902300000000
Manila town4902020000000

Counts by occupancy group for each jurisdiction are in the Excel file, sheet "B2-c Jurisdictions".

Jurisdiction rows are whole NFIP communities and need not add up to the county total: a community that extends into another county is counted in full on each jurisdiction row, while the county table counts only its part in this county.

County repeat-flood properties by occupancy group: 0 in every occupancy group.

Sources: 1, 4

FMA RL and FMA SRL are the Flood Mitigation Assistance definitions (44 CFR 77.2), the ones the FEMA Local Mitigation Planning Policy Guide cites. NFIP repetitive loss (the FEMA insurance definition) is 2 or more claims over $1,000 in 10 years, and a property can leave that group once it is mitigated. Also shown: NFIP severe repetitive loss, any category, mitigated and currently insured. The Methods page gives the OpenFEMA field details.

Counts are aggregates of FEMA's public NFIP Multiple Loss Properties file (FEMA's data date 2026-08-02; file version 2026-08-04). No property is identified. County assignment is FEMA's geocode.

In this county 0 properties are FMA repetitive loss but not NFIP repetitive loss, and 0 properties are NFIP repetitive loss but not FMA repetitive loss.

Exact counts; no count suppression.

Sources

Tables cite these sources by number. The full list, for the plan's bibliography (FEMA review item A4-a):

  1. FEMA, OpenFEMA HazardMitigationPlanStatuses v1, version 2026-09-29T134039Z, pulled 2026-09-30, https://www.fema.gov/api/open/v1/HazardMitigationPlanStatuses (API)
  2. FEMA, OpenFEMA DisasterDeclarationsSummaries v2, version 2026-09-29T162832Z, pulled 2026-09-30, https://www.fema.gov/api/open/v2/DisasterDeclarationsSummaries (API)
  3. FEMA, OpenFEMA PublicAssistanceFundedProjectsSummaries v1, version 2026-09-29T150754Z, pulled 2026-09-30, https://www.fema.gov/api/open/v1/PublicAssistanceFundedProjectsSummaries (API)
  4. FEMA, OpenFEMA NfipMultipleLossProperties v1, version 2026-08-04T164045Z, pulled 2026-09-30, https://www.fema.gov/api/open/v1/NfipMultipleLossProperties (API)
  5. FEMA, FEMA National Risk Index 1.20.0 (December 2025), county and census tract tables, version 1.20.0, pulled 2026-09-30, https://www.fema.gov/about/reports-and-data/openfema/nri/v120/NRI_Table_Counties.zip (download, 25 MB), https://www.fema.gov/about/reports-and-data/openfema/nri/v120/NRI_Table_CensusTracts.zip (download, 635 MB)
  6. NOAA NCEI, NOAA NCEI Storm Events Database, details files (csvfiles v1.0), version c20260918, pulled 2026-09-30, https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/
  7. NOAA National Weather Service, NWS county-public forecast zones correlation file, version bp03mr20 to bp16ap26 (11 files; newest bp16ap26), pulled 2026-09-30, https://www.weather.gov/gis/ZoneCounty
  8. U.S. Census Bureau, Census 2024 Gazetteer, 2020 place by county, CT county-to-cousub crosswalk, version 2024-gazetteer, pulled 2026-09-30, https://www2.census.gov/geo/docs/maps-data/data/gazetteer/2024_Gazetteer/2024_Gaz_counties_national.zip, https://www2.census.gov/geo/docs/maps-data/data/gazetteer/2024_Gazetteer/2024_Gaz_cousubs_national.zip, https://www2.census.gov/geo/docs/maps-data/data/gazetteer/2024_Gazetteer/2024_Gaz_place_national.zip, https://www2.census.gov/geo/docs/maps-data/data/gazetteer/2024_Gazetteer/2024_Gaz_unsd_national.zip, https://www2.census.gov/geo/docs/maps-data/data/gazetteer/2024_Gazetteer/2024_Gaz_elsd_national.zip, https://www2.census.gov/geo/docs/maps-data/data/gazetteer/2024_Gazetteer/2024_Gaz_scsd_national.zip, https://www2.census.gov/geo/docs/reference/codes2020/national_place_by_county2020.txt, https://www2.census.gov/geo/docs/reference/ct_change/ct_cou_to_cousub_crosswalk.xlsx (used to match place names and codes; no table prints its values)

What this packet is and what the plan adds

This packet is the federal data for the plan's risk assessment (the summary on page 1 says how it is organized); the plan and FEMA's review decide whether each item is met.

The plan adds what only the community has: local data on assets, critical facilities, development and each jurisdiction's impacts; local hazard history, including state-declared emergencies; the mitigation strategy; and adoption.

How the federal data are built: National Risk Index values are FEMA's model, not counts of events. Storm Events is more complete from 1996; zone-level records are placed by forecast zone, not by location in the county. Public Assistance for a jurisdiction is matched by applicant name. The Methods page gives every rule and the known edge cases.

OpenFEMA disclaimer

This product uses the Federal Emergency Management Agency's OpenFEMA API, but is not endorsed by FEMA. The Federal Government or FEMA cannot vouch for the data or analyses derived from these data after the data have been retrieved from the Agency's website(s).

Reuse, citation and corrections

Reuse and citation: Hazard Plain text and tables are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0, https://creativecommons.org/licenses/by/4.0/); credit Hazard Plain and the release. The underlying federal data are public domain; OpenFEMA data are also subject to the OpenFEMA terms and conditions.

Cite this: Hazard Plain (2026). Daggett County, UT: risk-assessment baseline packet, release 2026-10 (data as of 2026-09-30; County FIPS 49009). Automated baseline. https://hazardplain.org/ut/49009/ Built from FEMA OpenFEMA, the FEMA National Risk Index and NOAA NCEI Storm Events; source versions in the packet's Sources list.

Corrections: to report an error, name the packet, the table and what your records show. Contact: contact@hazardplain.org