HazardNow icon

HazardNow

Real-time situational awareness

County disaster-history profile

Pulaski County, Arkansas disaster history

Explore federal administrative declarations and NOAA county-coded observed-event records with their meanings, coverage periods, seasonal patterns, and limitations kept separate.

Data updated Aug 21, 2026 · Sources validated Aug 21, 2026

History, not a forecast

These historical records do not show current danger, future probability, or modeled risk. FEMA declarations and NOAA observed-event reports have different meanings and are never added into a danger score. For current conditions, use the live HazardNow dashboard.

Download share card

Two official histories, kept separate

Counts below describe records in each dataset. They do not measure event severity, loss, personal exposure, or the likelihood of a future disaster.

Administrative records

FEMA declaration history

Unique federal disaster declarations that include a county designation. A declaration is a government action, not a complete census of physical events.

Unique FEMA declarations
33
County designation records
33

Coverage: Jan 1, 1964 – Aug 21, 2026

Record categories

  • Severe storm12
  • Flood8
  • Winter storm5
  • Tornado4
  • Biological2
  • Hurricane2

Same-source state comparison

This county
33
Arkansas county median
24

This county count is 9 above the Arkansas county median for the same source and coverage period. Based on 75 county equivalents. This is a record-count comparison, not a risk ranking.

Observed-event reports

NOAA observed-event history

Distinct Storm Events records coded to this county. Forecast-zone and marine-zone reports are excluded from these county totals.

Unique NOAA county-event records
1,447

Coverage: Jan 1, 1996 – May 31, 2026

Record categories

  • High wind500
  • Hail490
  • Flood271
  • Tornado75
  • Severe storm64
  • Lightning46
  • Other1

Same-source state comparison

This county
1,447
Arkansas county median
335

This county count is 1,112 above the Arkansas county median for the same source and coverage period. Based on 75 county equivalents. This is a record-count comparison, not a risk ranking.

Year-by-year official records

Years appear newest first when at least one source has a record. FEMA administrative declarations and NOAA observed county-event records remain in separate columns and are never added or ranked together.

FEMA administrative records

Unique federal disaster declarations that include this county, grouped by the declaration record’s incident start year. A declaration is a government action, not a physical-event census.

Source: FEMA OpenFEMA Disaster Declarations Summaries v2 · Coverage: Jan 1, 1964 – Aug 21, 2026

NOAA observed-event records

Distinct NOAA Storm Events records explicitly coded to this county, grouped by event start year. Forecast-zone and marine-zone records are excluded from county counts.

Source: NOAA NCEI Storm Events Database · Coverage: Jan 1, 1996 – May 31, 2026

Annual FEMA unique declaration and NOAA county-event record counts, kept as separate source measures
YearUnique FEMA declarationsNOAA county-event records
202617
2025242
2024048
2023139
2022042
2021030
2020346
2019254
2018070
2017138
2016044
2015042
2014149
2013042
2012130
20111119
2010061
2009382
2008273
2007065
2006039
2005130
2004025
2003039
2002027
2001021
2000237
1999179
1998065
1997121
1996041
199010
198810
198710
198210
198010
197810
197610
197310
196910
196810

History, not a forecast: annual record counts do not measure current danger, future probability, severity, losses, or personal exposure. Differences can also reflect reporting and administrative practices.

When NOAA county-event records began

Monthly counts use only NOAA county-coded observed-event start dates. FEMA declaration dates are excluded. Historical reporting patterns are planning context, not a forecast of what will happen next.

Source: NOAA NCEI Storm Events Database · Coverage: Jan 1, 1996 – May 31, 2026

Exact monthly observed-event record counts
MonthRecords
January38
February85
March147
April295
May202
June194
July176
August110
September41
October79
November44
December36

Compare with another county

Compare like-for-like official record counts. FEMA declarations and NOAA observed-event records remain separate and do not form a combined risk score.

Comparing Pulaski County, Arkansas with Jefferson County, Alabama

Unique FEMA declarations

FEMA OpenFEMA Disaster Declarations Summaries v2 · Jan 1, 1964 – Aug 21, 2026

Pulaski County, Arkansas
33
Jefferson County, Alabama
39

Unique NOAA county-event records

NOAA NCEI Storm Events Database · Jan 1, 1996 – May 31, 2026

Pulaski County, Arkansas
1,447
Jefferson County, Alabama
1,116

Comparison updated to Jefferson County, Alabama. FEMA: 33 versus 39. NOAA: 1447 versus 1116.

Recent representative records by source

These bounded, newest-first lists make official identifiers inspectable. Aggregate totals above come from each validated corpus, not from counting only the records shown here.

FEMA representative declarations

Administrative declaration titles and dates from OpenFEMA.

  10. FEMA administrative declaration

    SEVERE STORMS, TORNADOES, STRAIGHT-LINE WINDS, AND FLOODING

    –

    Official source
    FEMA OpenFEMA Disaster Declarations Summaries v2
    Official ID
    FEMA disaster 4318
    Record type
    Severe storm
    Open official record

NOAA representative observed events

County-coded observed-event types and dates from NOAA NCEI Storm Events.

Practical preparedness implications

These actions translate record categories into low-regret planning steps. They are not predictions and do not replace local emergency instructions.

  1. Priority 1

    Prepare for observed high wind events

    High Wind is the most frequently reported NOAA hazard type among 1447 exact county-coded observed events in this profile.

    • Review household alerts, evacuation routes, and insurance coverage for this hazard.
    • Keep a documented communication and reunification plan that works during power or cellular outages.

    Evidence sections: NOAA observed events

  2. Priority 2

    Review declared severe storm history

    Severe Storm is the most frequent hazard category among 33 unique exact-county FEMA declarations in this profile.

    • Review insurance, documentation, and recovery contacts relevant to this declaration category.
    • Learn which local and state assistance channels operate before any federal declaration is made.

    Evidence sections: FEMA declarations

  3. Priority 3

    Use April as a readiness checkpoint

    NOAA records place 295 observed county events in April, the profile's highest observed monthly count.

    • Before this historically high-count month, refresh supplies, medications, contact lists, and alert settings.
    • Recheck transportation and shelter options for people, pets, and accessibility needs.

    Evidence sections: NOAA observed events

  4. Priority 4

    Plan from both observed and declared history

    NOAA event reports describe observed local frequency, while FEMA declarations identify a narrower administrative record of incidents receiving federal declarations.

    • Do not treat the absence of a FEMA declaration as evidence that a damaging local event cannot occur.
    • After an incident, preserve photos, receipts, policy records, and official notices for local, state, insurance, and possible federal processes.

    Evidence sections: FEMA declarations and NOAA observed events

Methodology and profile limitations

A source-separated county history using exact OpenFEMA county designations and NOAA county-coded observed events.

Counting rules

  • FEMA counts one declaration per unique disasterNumber for exact county designations dated 1964 or later.
  • NOAA counts one unique EVENT_ID only when CZ_TYPE=C and the constructed state-plus-county FIPS matches exactly, from 1996 onward.
  • Statewide-only FEMA rows, NOAA forecast zones, and NOAA marine zones are excluded from county metrics.

Comparison rules

  • Each county is compared only with the median of the same source and metric across every county equivalent in its state.
  • The Arkansas baseline contains every compatible county equivalent, including zero-count counties if any.

Limitations

  • This atlas publishes source-separated historical records, not a probability of future loss.
  • Records can be revised by their issuing agencies; regeneration selects the newest official NOAA revision for every year.
  • Statewide-only FEMA declarations are disclosed but excluded from exact county metrics.
  • Observed history is not a forecast or modeled risk score.
  • FEMA declarations and NOAA event reports measure different phenomena and are never merged into one event total.

Sources, coverage, and limitations

Each official dataset retains its own meaning, coverage period, freshness, and limitations.

Profile generated:

FEMA OpenFEMA Disaster Declarations Summaries v2

Federal Emergency Management Agency

Current for expected cadence
Coverage period
Jan 1, 1964 – Aug 21, 2026
Completeness
Complete for stated coverage and inclusion rules
Source updated
Retrieved by HazardNow
Expected update cadence
HazardNow refresh target: about weekly
Official dataset pageOpenFEMA API

Coverage notes

  • OpenFEMA v2 exact county designations from 1964 onward; disasterNumber is the unique declaration key.
  • Statewide-only, tribal, and other non-county designations are excluded from county metrics and medians.
  • Current Census county-equivalent FIPS define state comparison baselines; obsolete historical county codes are not reassigned.
  • County-level designation history is most consistently available from 1964 onward.
  • A declaration can designate multiple counties; each designation is a source record, not a separate physical event.

Limitations

  • Federal declarations are administrative actions and do not enumerate every damaging local incident.
  • Statewide-only and tribal designations are intentionally excluded from exact-county counts.
  • Federal declarations are administrative Stafford Act actions and do not capture every damaging local event.
  • Declaration counts should not be presented as forecasts or direct probabilities of future loss.

NOAA NCEI Storm Events Database

National Oceanic and Atmospheric Administration, National Centers for Environmental Information

Current for expected cadence
Coverage period
Jan 1, 1996 – May 31, 2026
Completeness
Partial for stated coverage or inclusion rules
Source updated
Retrieved by HazardNow
Expected update cadence
HazardNow refresh target: about monthly after source publication
Official dataset pageOfficial bulk files

Coverage notes

  • NCEI Storm Events details files for every year from 1996 through the current available year.
  • Only exact county-coded CZ_TYPE=C records are counted; forecast-zone and marine-zone records are excluded and disclosed.
  • Current Census county-equivalent FIPS define state comparison baselines; obsolete historical county codes are not reassigned.
  • 15 optional damage cells contained a bare K/M/B suffix; those amounts are retained as unknown/null and are never inferred as zero.
  • 1 record had an unrecognized CZ_TYPE and was excluded because it could not be assigned to an exact county geography.
  • The 2026 shard is preliminary; coverage ends at the latest accepted county event present for this state in the selected official revision.
  • Comparable all-event statistics begin in 1996; earlier reporting eras cover only a subset of event types.
  • County profiles count only exact county-coded CZ_TYPE=C records; forecast-zone and marine-zone records are excluded.
  • Finalized Storm Events records typically lag the event month by about 75 to 90 days.

Limitations

  • Storm Events reports are not a complete loss inventory and reporting practices vary over time.
  • Forecast-zone and marine-zone records are excluded because they cannot be assigned exactly to one county.
  • 15 optional archive damage cells contained only a K/M/B suffix, so their dollar amounts remain unknown/null rather than inferred.
  • 1 archive record with an unrecognized CZ_TYPE was excluded rather than attributed to a county.
  • The current-year file is preliminary through the latest event present in its selected official revision.
  • Storm Events is a report database; reporting practices and included event types change over time.
  • Damage estimates and narratives may be incomplete and should retain their source-level caveats.