Floodwater fills Pataskala homes and forces overnight evacuations
AUG 19, 7 PM UTC
First warning
Carroll County, Indiana
AUG 19, 11 PM UTC
Considerable threat
Logan County, Ohio
AUG 24, 7 PM UTC
Last warning
Jackson County, Indiana
- Flash flooding — coloured as water. 129 counties in the Ohio Valley, Aug 19–20.
In Pataskala during the overnight flooding, Robert Thomas said his trailer and neighboring trailers were under four feet of water within 20 minutes. A tree limb had crashed through his roof. “This is the scariest thing I've ever been through,” the resident told The Columbus Dispatch.
The warnings had begun in Carroll County, Indiana, on the afternoon of August 19. By evening, the weather service had issued a flash flood warning carrying a considerable damage threat for Logan County, Ohio. Licking County lay within the broader flooding area marked 1 on the map.
In Pataskala, police and firefighters began evacuations around 1:15 a.m. on August 20, The Newark Advocate reported. Crews also evacuated riverside residents in Buckeye Lake and Newark. Elsewhere in Licking County that day, emergency crews conducted water rescues after people drove into flooded areas, according to the same newspaper.
By daylight, leaving home was not an option for some residents of Pataskala's Bright Waters subdivision: high water blocked their way out, The Columbus Dispatch reported. The newspaper also documented a washed-away portion of Beaver Run Road that day. The Newark Advocate reported that shelters opened in Heath and Hebron, with additional shelter assistance in Newark and Buckeye Lake.
As of 11:30 a.m. on August 20, Licking County interim Emergency Management Director John Wieber told The Newark Advocate he was not aware of any flood injuries. More broadly, reporting reviewed for this flooding found no death or injury reported. That finding does not diminish the disruption documented in damaged homes, rescues and impassable roads.
Flood alerts by the numbers: every published month, by state and county.
Oregon fires close Highway 26 and bring shelters into service
AUG 5, 3 AM UTC
County order
Josephine County, Oregon
AUG 5, 3 AM UTC
County order
Josephine County, Oregon
AUG 6, 8 PM UTC
County order
Jackson County, Oregon
- Wildfire — coloured as heat and fire. 5 counties in Oregon, Aug 5–7.
Near Prineville on August 5, U.S. Highway 26 remained closed while crews dealt with falling rocks and fire-weakened trees, the Oregon State Fire Marshal reported. Firefighters were also preparing a forest road for a burnout intended to create a protective buffer between the Rowe Creek Complex and the city's eastern edge.
The Oregon fires marked 2 on the map were separate incidents, with county agencies issuing the emergency messages. In Josephine County on the evening of August 4, the sheriff sent an immediate evacuation order and then a separate notice telling residents to be set to evacuate. Those messages should not be read as a single fire advancing across Oregon.
By August 7, a Red Cross shelter for the Rowe Creek Complex was operating at East Side Church in Prineville, according to Central Oregon Fire Information. Its update reported 357,895 acres burned across the complex, not a total confined to Crook County.
Separately, near Ruch on August 6, the Jackson County Sheriff's Office issued readiness notices for the Woodrat Mountain Fire, including: “Jackson County Sheriff's Office: Level 2 BE SET / Nivel 2 ESTÉ LISTO - Woodrat Mtn Fire”. Medford Alert News reported that Jacksonville Elementary School opened as a shelter for people and small domestic pets. Livestock shelter was provided at the Jackson County Expo Fairgrounds in Central Point.
By the morning of August 7, firefighters had built fire line around the entire Woodrat Mountain Fire, which more accurate mapping placed at 282 acres, Medford Alert News reported. Officials cautioned that extensive work remained before the fire could be considered secure; the sheriff also issued an immediate evacuation order that day. Across the Oregon incidents covered here, the reporting and official updates reviewed found no death or injury reported.
Wildfire alerts by the numbers: every published month, by state and county.
Floods damage Springdale homes and close Zion's trails
AUG 30, 5 PM UTC
County order
Emery County, Utah
AUG 30, 6 PM UTC
County order
Emery County, Utah
AUG 30, 6 PM UTC
County order
Emery County, Utah
AUG 30, 6 PM UTC
First warning
Coconino County, Arizona
AUG 30, 6 PM UTC
Considerable threat
Coconino County, Arizona
SEP 1, 12 AM UTC
Last warning
Garfield County, Utah
- Flash flooding — coloured as water. 18 counties in Utah, Arizona and Colorado, Aug 30–31.
In Springdale on August 31, floodwater left its mark inside Angelea Glazier's children's bedroom. “There's a four-foot water line in my boys' room that just totally destroyed all of their stuff,” she told KSL. The station reported that water broke a window before entering the room.
The regional warnings had begun the previous day. On August 30, the Emery County Sheriff's Office sent this message: “POSSIBLE FLASH FLOODING IN THE GOBLIN VALLEY AND SAN RAFAEL AREA”. A flash flood warning carrying a considerable damage threat followed in Coconino County, Arizona, before noon local time. These were parts of the Southwest flooding marked 3 on the map.
Back in Springdale on August 31, about 30 people came to Glazier's home to help sort through flood-damaged belongings, she told KSL. The station documented damaged homes and mud and debris across roads. The household cleanup was the immediate work left after the water entered.
Across nearby Zion National Park that afternoon, flooding brought further restrictions. The weather service in Salt Lake City wrote: “At 358 PM MDT, National Park Service reported flash flooding from earlier thunderstorms producing heavy rain across Zion National Park.” FOX 13 News Utah reported road and trail closures, including all park slot canyons and the Narrows. Transportation officials told the station that fallen rocks closed Zion–Mount Carmel Highway between the east entrance and Canyon Junction.
In Bouse, Arizona, on August 31, trained spotters reported a swift-water rescue along Bouse Wash and Joshua Drive, according to the National Weather Service in Phoenix. The report did not specify how many people were rescued. A separate weather service report said Plamosa Road was impassable approaching Bouse. Across this regional flooding, the official reports and news coverage reviewed found no death or injury reported.
Flood alerts by the numbers: every published month, by state and county.
A tree strikes a Bethesda home as a tornado damages Dundalk
AUG 9, 3 AM UTC
County order
Fauquier County, Virginia
AUG 10, 12 PM UTC
First warning
Adams County, Pennsylvania
AUG 11, 12 PM UTC
Last warning
Wayne County, Indiana
- Tornadoes and severe storms — coloured as storms. 389 counties in the Mid-Atlantic, Aug 10–11.
In Bethesda on August 10, a falling tree struck John Edwards's home during the Maryland storms, part of the broader storm area marked 4 on the map. “All of a sudden there was a big bang and the whole house shook,” the homeowner told WJLA 7News.
Earlier that day, at 8:08 a.m. local time, the weather service issued a severe thunderstorm warning for Adams County, Pennsylvania. The Baltimore/Washington office's warnings described potential damage rather than confirmed losses: “Expect considerable damage to trees and power lines. Your life is at significant risk if outdoors. In addition to some trees falling into homes, wind damage is possible to roofs, sheds, open garages, and mobile homes.”
Damaging winds will cause some trees and large branches to fall. This could injure those outdoors, as well as damage homes and vehicles. Roadways may become blocked by downed trees. Localized power outages are possible. Unsecured light…
At the West Cedar Lane home in Bethesda that afternoon, the damage was no longer a forecast. Montgomery County Fire and Rescue crews found a fallen tree and an electrical fire originating at an outlet, WJLA reported. The station said two residents were displaced and, as far as the record shows, no one was hurt.
In Baltimore and Dundalk, a weather service team surveyed the storm damage on August 11. Its subsequent report confirmed that the previous day's tornado uprooted and snapped trees near Broening Highway and snapped a power pole on Ralls Avenue. It also documented a displaced vehicle near Sollers Point Road and an awning torn from an apartment in Dundalk. Those findings establish tornado damage there, not at the Bethesda home.
During the August 10 storms, more than 25,500 Baltimore Gas & Electric customers lost power at one point, CBS Baltimore reported. Across the broader storm event covered here, the official reports and news coverage reviewed found no death or injury reported. The documented costs nevertheless included a household displaced, damaged property and interrupted electricity.
Tornado alerts by the numbers: every published month, by state and county.
How BePrepared monitors this, all year
This report exists because we already monitor the whole country. Every couple of minutes, around the clock, we read the emergency alerts going out across all fifty states and territories, and we keep them. A month of that record is what you have just read.
The national picture is the part most people never see. What matters to you is much smaller: which of these warnings would have reached your street, and what the risks around you look like on an ordinary day.
That is what BePrepared is for. Put in your ZIP code and you get the picture for where you live — the flood, fire and storm history around you, the dams and facilities nearby, and a plan for your household rather than a general one. With a free account you can keep a watchlist of the places you care about, like your home, your parents' address, and your kids' school, and set what you want to hear about.
Where it hit hardest
Counted as distinct warnings, and as the days a county spent under one. A county is the smallest area these warnings describe.
Warnings by region
- Ohio Valley1,028
- Southwest935
- Southeast871
- Midwest860
- Mid-Atlantic735
Most days under a warning
- San Bernardino County, CA29 days
- Pinal County, AZ28 days
- Randall County, TX28 days
- Riverside County, CA28 days
- La Paz County, AZ27 days
- Coconino County, AZ27 days
- Gila County, AZ27 days
- Clark County, NV27 days
Where the warnings landed
- Severe storms
- Extreme heat
- Flooding
- Everything else
Severe storms34,018 warnings · 2,528 counties
Extreme heat25,791 warnings · 1,963 counties
Flooding21,160 warnings · 1,792 counties
Fire3,382 warnings · 398 counties
Tornadoes1,173 warnings · 309 counties
Safety & civil700 warnings · 318 counties
Hurricane & tropical185 warnings · 38 counties
View as a table
| County | State | Warnings | Most frequent kind |
|---|---|---|---|
| Pima | AZ | 510 | Flooding |
| Maricopa | AZ | 326 | Everything else |
| Pueblo | CO | 271 | Everything else |
| Cochise | AZ | 268 | Severe storms |
| Pinal | AZ | 263 | Everything else |
| Cherry | NE | 246 | Severe storms |
| Arapahoe | CO | 226 | Everything else |
| Fremont | CO | 221 | Everything else |
| El Paso | CO | 208 | Everything else |
| San Bernardino | CA | 203 | Flooding |
| La Paz | AZ | 193 | Severe storms |
| Elbert | CO | 192 | Everything else |
| Duval | FL | 192 | Everything else |
| Custer | CO | 188 | Everything else |
| Douglas | CO | 185 | Everything else |
| Washington | OH | 181 | Flooding |
| Laramie | WY | 178 | Everything else |
| Huerfano | CO | 175 | Everything else |
| Weld | CO | 170 | Everything else |
| Adams | CO | 168 | Everything else |
What it cost
No documented outcome figures were available for this period at the time of publication. This report therefore describes the warnings that went out, and makes no claim about deaths, damage or acreage.
The numbers behind this report
Every warning counted once, by type, place, day and hour, with the method below and the whole table downloadable at the end of the page.
What was warned about
| Alert type | Warnings | Messages |
|---|---|---|
| Severe Thunderstorm Warning | 11,205 | 11,205 |
| Special Weather Statement | 9,778 | 9,783 |
| Flood Advisory | 2,672 | 2,673 |
| Flash Flood Warning | 2,659 | 2,659 |
| Special Marine Warning | 1,606 | 1,606 |
| Heat Advisory | 1,570 | 3,130 |
| Small Craft Advisory | 1,346 | 5,022 |
| Flood Warning | 1,221 | 1,900 |
Where
| State | Warnings |
|---|---|
| AZ | 1,956 |
| CO | 1,744 |
| FL | 1,698 |
| IN | 1,628 |
| OH | 1,558 |
| NC | 1,514 |
| GA | 1,497 |
| NE | 1,314 |
The busiest hour of the period was 5pm local time, with 3,610 warnings.
Counties reached most often
| County | State | Warnings |
|---|---|---|
| Pima | AZ | 510 |
| Maricopa | AZ | 326 |
| Pueblo | CO | 271 |
| Cochise | AZ | 268 |
| Pinal | AZ | 263 |
| Cherry | NE | 246 |
| Arapahoe | CO | 226 |
| Fremont | CO | 221 |
| El Paso | CO | 208 |
| San Bernardino | CA | 203 |
A county with no alerts is not a county with no risk. It can mean a quiet period, or a hazard that this feed does not carry.
When the warnings arrived
View as a table
| Local hour | Warnings | Of which most severe |
|---|---|---|
| 12am | 1,011 | 19 |
| 1am | 870 | 18 |
| 2am | 870 | 9 |
| 3am | 670 | 6 |
| 4am | 611 | 7 |
| 5am | 650 | 7 |
| 6am | 592 | 13 |
| 7am | 553 | 14 |
| 8am | 640 | 26 |
| 9am | 668 | 25 |
| 10am | 744 | 37 |
| 11am | 908 | 23 |
| 12pm | 1,146 | 31 |
| 1pm | 1,690 | 47 |
| 2pm | 2,510 | 53 |
| 3pm | 3,106 | 92 |
| 4pm | 3,507 | 124 |
| 5pm | 3,610 | 104 |
| 6pm | 3,360 | 84 |
| 7pm | 3,028 | 93 |
| 8pm | 2,473 | 76 |
| 9pm | 1,974 | 82 |
| 10pm | 1,489 | 65 |
| 11pm | 1,251 | 23 |
The feed repeats itself
View as a table
| Stage | Count |
|---|---|
| Messages received | 47,345 |
| Of which updates | 20,465 |
| Of which cancels | 0 |
| Distinct warnings | 37,931 |
| Counties reached | 3,752 |
How severe they were
- Minor
- Moderate
- Severe
- Extreme
- Not classified
View as a table
| Severity | Warnings |
|---|---|
| Minor | 5,047 |
| Moderate | 12,232 |
| Severe | 19,132 |
| Extreme | 1,078 |
| Not classified | 442 |
What people were told to do
- Follow instructions
- Shelter
- Avoid
- Everything else
Where those instructions came from
- Shelter (11,832) — 2,690 corroborated as flood, 1,009 corroborated as tornado, 34 corroborated as wildfire, 10 corroborated as hurricane, 8,089 with no hazard stated in the alert text
- Evacuate (107) — 8 corroborated as flood, 76 corroborated as wildfire, 23 with no hazard stated in the alert text
View as a table
| Response | Warnings | Share |
|---|---|---|
| Follow instructions | 12,215 | 32.2% |
| Shelter | 11,832 | 31.2% |
| Avoid | 10,163 | 26.8% |
| Monitor | 2,251 | 5.9% |
| Prepare | 1,045 | 2.8% |
| Unstated | 303 | 0.8% |
| Evacuate | 107 | 0.3% |
| All clear | 15 | 0.0% |
What this report cannot tell you
- This report records the warnings that were sent: when, where, and what people were told to do. It cannot say whether anyone received them, whether they acted, or whether they had anywhere to go.
- Deaths, injuries, damage and acreage come from the news organizations and agencies named beside each figure. Our own records measure warnings, never outcomes, and are never the source for a toll.
- A county is the smallest area these alerts describe, so "a county was warned" does not mean every street in it was at risk.
- Where no figure has been reported, this report says so rather than estimating.
How these numbers were counted
Counted AUG 1, 2026 – SEP 1, 2026 · Frozen at publishThe alert figures in this report — how many warnings, where, when, and how severe — come from the alerts this archive received from FEMA IPAWS and the National Weather Service between August 1, 2026 and September 1, 2026, counted once and frozen when the report was published.
Deaths, damage and acreage are not ours and are never drawn from this archive. Each is attributed to the organization that reported it, above.
What was counted
- cap_status = 'Actual' (tests, exercises and demos excluded)
- SAME test codes RWT/RMT/DMO/NPT/NAT excluded, and any event type containing "test"
- An event is the first message of a CAP identifier chain; updates and cancels are counted separately
- Alert time is cap_sent, falling back to ingest time when the feed omits it
- Counties come from the alert geocodes (SAME/FIPS); statewide codes are not counted as counties
What these numbers cannot tell you
- Lead time is the gap between when an alert was sent and when it takes effect. This archive collapses CAP onset into effective, so for many products those are the same instant by design — it is not a measure of forecast warning time.
- 142 alerts expire exactly 24 hours after they were sent because the feed omitted an expiry and the ingest substitutes a default. They are excluded from the duration distribution rather than charted as real forecasts.
- Evacuation and shelter figures are RESPONSE counts. They record what people were told to do, not what caused it; where the alert text does not name a hazard, the row is reported as unstated.
- Hour-of-day figures use each alert’s own local time, resolved from its state. Alerts spanning several states resolve to the first state in their geocodes.
- National Weather Service alerts began arriving in volume on 2026-06-12. Earlier months hold only the handful that reached this archive by other routes, so they undercount weather alerts badly and cannot be compared with later months.
- Population figures are not available for these counties, so alert counts are reported per county and never per resident.
This archive
Collection began 2026-03-27. National Weather Service alerts began arriving in volume on 2026-06-12 (a small number reached the archive by other routes from 2026-03-31). Months from 2026-07-01 onward can be compared with each other; earlier ones cannot.
Corrections and updates
- v2September 19, 2026improved prompts
- v2September 19, 2026improved prompts
- v4September 22, 2026new version of report builder
For newsrooms and researchers
Use these figures
Journalists, emergency managers and researchers are welcome to reuse anything in this report, including the underlying counts, with attribution. Version 4 of these figures is frozen: if a correction changes them, it appears above as a dated note rather than silently replacing what you cited.
BePreparedSolutions.co. "Floods, fires and storms disrupt homes and roads across the United States." Alert Pulse, September 22, 2026. https://bepreparedsolutions.co/reports/alert-pulse/2026-08
Source: BePrepared Solutions, Alert Pulse (2026). Alert counts from FEMA IPAWS and National Weather Service feeds; casualty and damage figures as attributed in the report.
<iframe src="https://bepreparedsolutions.co/reports/alert-pulse/2026-08/embed/reach_map" width="100%" height="520" style="border:0" loading="lazy" title="Floods, fires and storms disrupt homes and roads across the United States"></iframe>
The embed updates itself if we publish a correction, so it never goes stale the way a screenshot does.
The CSV carries the same frozen figures as this page, keyed to version 4.