Cherry Fire (Eureka Area) Resources & Recovery

About the Cherry Fire

The Cherry Fire broke out on June 26, 2026, southwest of Eureka, when two ignitions merged and tore through dry grass, sagebrush, and juniper. It made an explosive run almost immediately — covering roughly eleven miles in a matter of hours and burning into the tens of thousands of acres on its first day, at zero containment. The Juab County Sheriff ordered residents of Mammoth, Silver City, and parts of Eureka to leave, sending them east on Highway 6 to a shelter set up at a church in Elberta, and the area around Vernon Reservoir and Lofgreen was evacuated as well. The Cherry Fire arrived just as the nearby Iron Fire was winding down, stretching crews and forcing some Eureka-area residents to flee a second time in a single fire season. Burning in the same rugged Tintic country, it has been slower to contain than the Iron Fire that preceded it.

This is an active, fast-changing incident. The figures here reflect public reporting as of late June 2026 and will be out of date quickly — use the official links above.

Recovery resources

When it's safe to focus on recovery, these are the Utah and federal resources to lean on — closest to home first:

For the full set of Utah recovery resources, see our Utah wildfire recovery hub.

If you're in or near the Cherry Fire

1. Go when told to goWith a fire this fast, an evacuation order can come with little warning. If the Juab County Sheriff says leave, take Highway 6 east as directed and don't wait to gather belongings.
2. Expect the situation to changeAreas downgraded one day can be re-evacuated the next. Keep your phone alerts on and check Utah Fire Info before assuming it's safe to return.
3. Once cleared, record what you lostWhen officials reopen your area, document damage thoroughly before cleanup and build a written inventory for your insurer.
4. Start your claim and save your costsNotify your insurance company as soon as you're able, and hold onto receipts for lodging, meals, and other expenses from being displaced.