Most wildfires are somewhere else. This one was five miles from downtown Reno. The Hawk Fire was discovered just before noon on August 22 on Peavine Mountain, in the short grass and brush northwest of Reno, Nevada — and short grass is the fastest fuel there is. Within hours it was making wind-driven runs toward the city: between 12:17 and 22:00 that day, Washoe County issued five successive "EVACUATE NOW" emergency alerts, each covering more ground than the last, expanding from Peavine into Lemmon Drive, Silver Lake, and northwest Reno. At the height of the evacuation that evening, the alert areas in force covered census blocks home to roughly 19,000 households — about 50,000 residents — and across the day roughly 28,000 households sat inside an evacuation alert at some point. The fire ran to about 15,000 acres in two days at zero containment before the line turned: by August 25 it was 27% contained with 816 personnel on the incident under a Type 3 incident commander and suppression costs near $6 million. The cause has been identified as human. The Hawk Fire anchors this brief because it compresses the week's global story into one valley: a ten-day window holding 4,611 verified events, of which 3,675 — 80% — were wildfires, including a 289-fire belt burning along an active war front in Ukraine, while three magnitude-7-class earthquake responses ran simultaneously on two continents.
Update, August 26: the Hawk Fire is now reported 85% contained at 15,067 acres — the growth phase is over, and full containment is the remaining milestone.
What's confirmed and what's forecast: Every Hawk Fire number above is observed. Fire figures come from National Interagency Fire Center incident reports as they arrived in the DisasterAWARE feed, including the day-over-day progression from "extreme fire behavior with wind-driven runs" (August 24 report) to "minimal, smoldering, and backing behavior" at 27% containment (August 25). Evacuation figures come from the archived IPAWS/Wireless Emergency Alert record of Washoe County's five broadcast alert areas, with household counts derived from 2020 Census housing units in blocks intersecting those areas — edge blocks count fully, so treat them as a modest overestimate, and "households" includes apartments and vacant units. One tier is not recoverable: Washoe County manages its GET SET / GO NOW zone system on a platform with no public historical record, so this brief counts broadcast alert areas, not named evacuation zones, and the GET SET (prepare-to-leave) footprint — necessarily larger still — is not included in any number here. DisasterAWARE's own model estimated 283 people, 113 households, and $98.3 million of infrastructure inside the fire's mapped exposure area — the footprint of the burn perimeter itself, not the platform's broader alert circle — and the gap between that perimeter figure and the ~50,000 alerted residents is itself the story; we return to it below. As always, the 6,243 formal warnings, watches, and advisories our occurrence filter set aside this week are context only, never counted as events, and anything forward-looking below is labeled as forecast.
Open map full screen in a new tab ↗
Reading the map: it opens zoomed all the way in on the Hawk Fire, over satellite imagery with street names — so you can see the actual neighborhoods, subdivisions, and homes the polygons cover. The solid red, fingered polygon is the detailed NIFC-mapped burn perimeter (15,085 GIS acres) draped over Peavine Mountain's burn scar; the dashed orange outlines are Washoe County's five successive EVACUATE NOW alert areas from August 22, reaching across Silver Lake, Lemmon Valley, and Golden Valley — territory holding ~19,000 households at the peak. The pulsing marker is the incident location; the violet fan streaming northeast is the NOAA-analyzed smoke plume from fire day, its nested bands showing satellite smoke density (palest = light, darkest = the window's only heavy-density smoke); and the cloud markers are AirNow monitors colored by their peak hourly AQI — yellow for Moderate, red for the Unhealthy 156 at Spanish Springs. (DisasterAWARE's 283-person exposure estimate is computed on the burn-perimeter footprint — the solid red shape — not the wider dashed-amber alert circle you'll see as you pull back.) The rest of the week's events — all of them — are on this same map: zoom out to see the world. As you pull back to the world view — bright red flames are the 290 warning-level wildfires worldwide, dark red flames are the 289 conflict-zone fires clustered along the Ukraine/Russia front line, amber markers are earthquakes M5.5+ sized by magnitude (the M7.7 Ende and M7.4 Colombia response operations stand out), and the layer control (bottom right) toggles this week's flood/severe-weather warnings and the 16 warning-level volcanoes.
The Hawk Fire started the way the Great Basin's worst fires usually do: in grass, in wind, close to people. Discovered August 22 about five miles north of Reno, it burned through fuels the NIFC reports describe as "primarily short grass with brush" — cheatgrass country, where flame fronts move at the speed of the wind rather than the speed of a forest fire. The first incident reports in the DisasterAWARE feed carried the phrase "extreme fire behavior, including wind-driven runs", and the growth curve matched: roughly 15,000 acres inside two days, with containment stuck at zero.
That's the phase when a fire stops being an acreage statistic and becomes a household decision — and on August 22, the archived alert record shows exactly how that afternoon unfolded, message by message. The fire was discovered at 11:23 a.m. Fifty-four minutes later, at 12:17, Washoe County's first wireless emergency alert hit phones: "WILDLAND FIRE in the Peavine area. EVACUATE NOW." Four more followed — 17:09, 18:37, 19:40, 22:00 — each polygon larger than the last as the wind pushed the fire off Peavine toward the city, and you can read the escalation in the messages themselves: by 19:40, "Evacuations have expanded into the area of Lemmon Drive and Silver Lake"; by 22:00, "WILDLAND FIRE in Northwest Reno… Evacuate point at Reno Sparks Convention Center." The alert durations tell the same story — the afternoon orders carried two-hour windows; the evening orders were set to run eight hours, through the night. By that evening, the alert areas simultaneously in force covered census blocks holding roughly 19,000 households and 50,000 residents; across the full day, about 28,000 households were inside an EVACUATE NOW area at some point. News coverage described residents rushing to escape as the fire swept toward subdivisions, and schools in the area, including Coral Academy, remained closed days later. For a fire this size, the operational response was substantial and fast: by August 25, 816 personnel were assigned under a Type 3 incident commander, with an estimated $6 million in suppression costs already on the books.
The August 25 report reads like a different fire: the perimeter held at 15,040 acres, containment climbed to 27%, and fire behavior dropped to "minimal, smoldering, and backing." That pivot — from wind-driven runs to backing fire in 72 hours — is what a successful initial-attack-to-containment transition looks like, and the feed captured it report by report.
The intelligence story sits in the gap between two numbers: 283 and 50,000. DisasterAWARE's exposure model put 283 people, 113 households, and $98.3 million of infrastructure inside the fire's perimeter footprint — the people and assets in the burned area itself — while the evacuation alerts reached areas holding some 50,000 residents, 175 times more people than the fire touched. That's not a modeling failure; it's the physics of evacuation. Emergency managers draw GO NOW polygons around where a wind-driven grass fire could be in three hours, not where it burns now, and the map above shows both boundaries around the same fire. For enterprises with assets in the urban-wildland interface, that multiple is the planning number that matters: which facilities sit not just in a fire's path but in its evacuation path, which employees live inside the polygons that will be drawn, which suppliers and routes go dark when a highway closes. It's the same exposure-first workflow we detailed for underwriters in hazard data for insurers, pointed at a fire instead of a hurricane.
There's a quieter lesson in what this reconstruction couldn't recover. Washoe County ran a two-tier evacuation — GET SET (prepare to leave) and GO NOW — but only the GO NOW orders were broadcast over the federal IPAWS system, whose record is archived. The GET SET tier lived on a county mapping platform that keeps no public history, so the fullest picture of who was told to get ready on August 22 has, for practical purposes, already vanished. Emergency alerting data is perishable: it describes a moment, and unless something captures that moment as it happens, there is nothing to analyze afterward — no evacuation-footprint numbers, no polygons on a map, no after-action baseline. Every evacuation figure in this brief exists only because the alert stream was archived in real time.
How big is the Hawk Fire near Reno? As of August 26, the Hawk Fire's mapped perimeter covered 15,067 acres about five miles north of Reno, Nevada, at 85% containment, with 816 personnel assigned at the response's height. Nearly all of its growth came in the first two days after discovery on August 22, driven by wind through short grass and brush.
What caused the Hawk Fire? NIFC incident reports list the cause as human, and it is not listed as under investigation. The fire's explosive early growth came from wind-driven runs through cheatgrass and brush — the fastest-moving fuel type in the Great Basin.
How many people were evacuated in Reno? Washoe County issued five successive EVACUATE NOW wireless emergency alerts on August 22 as the fire ran toward the city. At the peak that evening, the alert areas in force covered census blocks holding roughly 19,000 households — about 50,000 residents — and about 28,000 households were inside an alert area at some point that day. (Those are the households in the alerted areas, not a count of people who left; the county's GET SET "prepare to leave" tier covered additional territory that isn't in these figures.) Area schools, including Coral Academy, remained closed days later.
How bad was Reno's air quality during the Hawk Fire? Worst the morning after the fire's biggest day. On August 22 itself, wind kept the smoke lofted and Reno-area monitors peaked at AQI 58 (Moderate) even as satellites tracked heavy smoke overhead. Overnight the smoke settled into the basin: hourly AQI hit 156 (Unhealthy) at Spanish Springs on August 23, then eased to Moderate (64–66) through August 26.
Is the Hawk Fire contained? Mostly. As of August 26 it was 85% contained at 15,067 acres, after fire behavior collapsed from extreme wind-driven runs (August 22–24) to minimal, smoldering, and backing behavior. Check the live wildfire intelligence hub for current status.
Here's the counterintuitive part of the Hawk Fire's air-quality story: on the day the fire exploded, Reno's air was fine. NOAA's satellite smoke analysis for August 22 shows the window's only Heavy-density smoke plume fanning northeast from Peavine — the dark plume on the map above, and the same one visible from space in this article's banner image — yet surface monitors across the Reno area peaked at just 58 (Moderate) that day. The wind driving the evacuations was also keeping the smoke lofted, carrying it up and over the basin.
The region also caught a genuine break in where the smoke went. The same southwest wind that drove the fire toward north Reno's neighborhoods pushed its plume north and east — out over the sparsely populated basin-and-range country toward Pyramid Lake — rather than south into the Reno–Sparks core or southwest toward Lake Tahoe, both of which routinely spend stretches of fire season buried under smoke from California fires. A fire this size burning under a northeast wind instead would have written a very different air-quality story for both.
Then the wind died. Overnight, the smoke settled into the Truckee Meadows, and the worst air arrived after the fire's worst day: on the morning of August 23, hourly AQI reached 156 — Unhealthy — at Spanish Springs, before easing back to Moderate (peaks of 64–66) from August 24 through 26 as the plume tapered. Even that was a comparatively light toll for a 15,000-acre fire on the city's doorstep — the plume's northeast track meant most of its smoke never crossed the urban core at all. It's a pattern worth internalizing: "smoke overhead" and "bad air" are different events, often a day apart, and the people who sheltered from one were breathing the other. The map above shows both sides of it — the fire-day plume as violet density bands, and the AQI monitors colored by their peak readings. (Air-quality figures are provisional AirNow hourly PM2.5 readings from five monitors within 35 km of Reno; smoke extents are NOAA Hazard Mapping System satellite analyses.)
Wildfire was 80% of the planet's confirmed hazard activity this window — 3,675 events, 580 at warning severity — and the belt ran everywhere it has run all summer: the interior American West (where the Hawk Fire had plenty of company, from Oregon's fire-number complexes to Montana's Moose Fire), the Mediterranean rim, central and southern Africa, and an early-spring start across Australia. The count is up sharply from the 1,835 of the Typhoon Dolphin window, partly because August is the belt's historical peak and partly because this brief's occurrence filter now correctly credits incident-report fires that arrive wrapped in formal-warning language — more on that in the methods note below.
The starkest cluster on the map isn't in any of those places. 289 warning-level wildfires — half of the global warning total — sit along the Ukraine/Russia front line, from Donetsk and Luhansk through Kharkiv to the Kursk–Sumy border region. These are fires with a property no other cluster has: many simply cannot be fought. Front-line territory means mined ground, artillery ranges, and no fire crews, so ignitions that would be one-day initial-attack stories anywhere else burn until weather or fuel breaks stop them. On the map they render in a darker red — a fire belt inside a war, visible from a hemisphere away.
Methods note: this window's wildfire count is not directly comparable to prior briefs. A filter correction on August 25 restored NIFC-sourced incident fires (like the Hawk Fire itself) that were previously misclassified as formal alerts because their reports lead with warning boilerplate. The correction added roughly 240 verified U.S. fires to this window's board — all real, burning incidents.
For most of this window, DisasterAWARE carried three simultaneous magnitude-7-class response-support operations — a coincidence of timing the seismic record doesn't produce often. The M7.7 near Ende, Indonesia (August 14, on Flores) and the M7.4 near San José del Palmar, Colombia (August 10) both entered the window as young, active responses; the M7.5 Yumare, Venezuela operation has run since June's doublet, which we anatomized in Venezuela's Earthquake Doublet: Why It Killed. Around them, the week's seismicity stayed loud: 96 earthquakes on the board, 31 at M5.5+, led by a M6.9 near Pematangsiantar, Sumatra on August 15 — the window's largest new quake — and a M6.7 in Peru's Ayacucho region on August 20.
Southeast Asia's flood season concentrated on the Mekong basin this window: repeated riverine flood warnings on the Se Bang Fai river in Laos and on the Mekong mainstem at Nong Khai and Mukdahan, Thailand, alongside flood warnings in Sri Lanka, Afghanistan's Nuristan province, and northwest Colombia. The 125 flood events on the board also included a run of flash-flood impacts across the U.S. Midwest — Indiana, Illinois, and Ohio all recorded confirmed flood events — and southeastern Australia's winter storms pushed flood warnings across Victoria, South Australia, and New South Wales.
The Hawk Fire's push from 85% to full containment — and whether the Washoe Zephyr's afternoon winds test the remaining open line before crews close it out. The response tails at Ende and San José del Palmar, both young operations in difficult terrain. The conflict-zone fire belt, which will burn as long as the front line does. And the Mekong's crest as the basin moves through peak monsoon season.
Every number in this brief comes from the DisasterAWARE platform: 4,611 verified events deduplicated across live and historical feeds, with the Hawk Fire's incident reports — acreage, containment, personnel, fire behavior, exposure — arriving as structured data with every NIFC update. The exposure model that put 283 people and $98.3 million of infrastructure inside the fire's perimeter footprint runs automatically on every event, worldwide, the moment it's detected. For what "event intelligence" means end to end — detection, verification, impact assessment — see our full explainer.
Track wildfires live:
Put this intelligence to work:
Produced with DisasterAWARE® — the multi-hazard monitoring, alerting, and decision-support platform from Pacific Disaster Center. Data window: August 15–25, 2026.
-min.png)
.png)
.png)
Decision-ready intelligence for understanding what's happening, what is impacted, and what to do next. Global hazard, severe weather, catastrophe, and physical risk intelligence trusted by governments, enterprises, insurers, humanitarian organizations, and technology platforms worldwide.
Request DemoContact Us
