The Hawk Fire’s Uneven Aftermath: What Burned, What Failed, Who Was Neglected
The Hawk Fire didn’t just scorch 15,000 acres northwest of Reno. It exposed a pattern — one that North Valleys residents have been warning about for years. Here’s what they told me.
Michael Leonard
Sep 09, 2026
The Haw Fire exposed unequal firefighting response. Delayed evacuation alerts. Neglected mitigation in annexed neighborhoods. And now, a growing list of GoFundMes that read like obituaries for homes, livelihoods, and stability.
This article explains what the official updates don’t say, but what neighbors shared with me.
A Neighborhood Left to Its Own Luck
Sierra described her evacuation as a near‑entrapment. She and her partner loaded four dogs, two cats, and a flock of chickens into their car and drove through burning sagebrush on the only road in or out.
“I was calling my grandmas, like, I don’t know if I’m gonna get out or not,” Sierra said.
The Watch Duty app still showed yellow — get ready. Sierra said it didn’t flip to go now until an hour after they had already escaped.
Liz said they saw no firefighting personnel in the neighborhood as flames advanced. They watched the fire approach with no engines, no crews, and no visible aerial support.
Liz told me that Old South Virginia and the 395 freeway were closed at Stead and Red Rock before evacuation orders were given.
The only open route required driving through Truckee to get back to Reno, which was not feasible for residents low on gas or money, especially since local gas stations were closed.
While Silver Lake Road was open, it is a two-lane road that does not connect all the way into town, resulting in severe gridlock for thousands of residents.
Jordan described a two‑hour window on August 22 when the Hawk Fire shifted toward Mohawk Lane, but no visible engines, dozers, or air support arrived to defend the neighborhood.
Watch Duty showed the change around 3:30 p.m., yet they saw aircraft fly overhead without dropping retardant near homes, and the first drop they witnessed — at 5:14 p.m. — was too late and too high on the hillside to help.
By the time the GO NOW alert arrived, flames were already in backyards. Their home, the place they imagined their future unfolding, burned soon after.
Jordan’s central question is simple: if officials knew the fire was moving toward Mohawk, why did the neighborhood receive no meaningful protection?
Their account raises the broader issue of how — and why — resource allocation decisions left some families defended and others exposed.
Link: North Valleys Post-Fire Resources & Support Event
Candidate for District 5, Rob Pierce sent me this link for a community support event on September 21 at 6:30–8:00 PM at Granite Hills Baptist Church.
Click to see this video of the fire burning that was sent to me by Jordan.
Evacuation Chaos in the North Valleys
The evacuation failures were not isolated. They were systemic.
Residents across Stead, Silver Knolls, and Lemmon Valley reported:
No phone alerts
Blocked evacuation routes
Traffic signals out
Construction closures still in place
Police loudspeakers as the only warning
Councilmember Meghan Ebert — who was herself evacuated — publicly criticized the breakdown:
Evacuation orders issued after major roads were already closed
Residents forced into gridlocked two‑lane bottlenecks
Conflicting information between agencies
No unified communication channel
For many, the evacuation wasn’t coordinated. It was improvised. A resident told me they were not notified to evacuate until it was too late to get out because of gridlock.
The primary alert came from a police officer using a loudspeaker, which many residents likely didn't hear. No official emergency announcement was sent to their phones; they had to rely on the perimeter map for updates. It was mass confusion.
The Fire Didn’t End When the Evacuation Orders Lifted
Residents say that they received no official notification regarding when it was safe to return home. They only found out because a neighbor discovered the area was open and informed them.
At the Bonanza Terrace RV Park, residents returned after five days of displacement. The next morning, they woke to an explosion.
“They were woken by the explosion to get out of their home before it caught fire,” Amanda Peña said.
Tammy and John escaped unharmed, but their trailer was destroyed. They are now living in a relative’s small travel trailer while they try to figure out what comes next.
Their GoFundMe is blunt: “This is not something our family was comfortable asking for… but after losing our home, even a little support can make a real difference.”
The Hawk Fire didn’t just burn homes. It destabilized the infrastructure around them. Secondary fires are now part of the recovery landscape.
How the Hawk Fire Exposed Reno’s Unequal Wildfire Defenses: Who Gets Protected
A Small Business Reduced to Ashes
Another fundraiser tells Casey's story, who ran a niche slot‑machine repair business. His rented shop, along with dozens of machines and thousands of specialized parts, burned in the fire.
“This was not simply a loss of property. It was the loss of his business, his livelihood, and years of dedicated work.”
This is the kind of loss that doesn’t show up in acreage counts or containment percentages. It’s the quiet collapse of a local economy built on small operators.
North Valleys Residents Push Back on Stereotypes
Some online commentary tries to frame the North Valleys as “just mobile homes.” Residents are pushing back.
Many homes in the burn zone are $400,000+ on acreage and are owned by long‑term residents who have watched the city annex their neighborhoods but have failed to maintain them, said one neighbor.
Another resident described paying a $35/month landscaping fee for a greenbelt that the city hasn’t properly maintained since annexing the neighborhood and dissolving the neighborhood’s HOA in 2005.
The watershed and railroad property near Peppermint Drive — a known fire corridor overgrown with dry brush and sage — has reportedly been cleared only once in 22 years. The fire didn’t create inequity. It revealed it.
The Official Line vs. The Lived Reality
The final incident update from Great Basin IMT 6 reads like a standard wrap‑up:
98% containment
187 personnel
Suppression repair underway
Transition to a Type 4 local team
But the lived reality is different:
Residents evacuated with no official alerts
Some neighborhoods saw no firefighting presence
Return notifications lagged behind conditions
Secondary fires destroyed homes after reentry
Small businesses collapsed
GoFundMe became the primary recovery mechanism
This is not a story of a fire. It’s a story of a system.
The Pattern Is Clear
Across all accounts, the same themes repeat:
Delayed evacuation alerts
Unequal resource allocation
Neglected mitigation in annexed neighborhoods
Infrastructure failures during evacuation
Secondary destruction after reentry
Residents relying on crowdfunding to survive
The Hawk Fire will be remembered not only for the acres burned, but for the inequities it exposed.
Do you have a story to tell? Write to me at: mike@mikesrenoreport.com
Support independent journalism. Click to donate to: Mike’s Reno Report.