White Sage Fire
The White Sage Fire was reported on July 9, 2025 in Coconino County, Arizona and burned 58,985 acres. It was declared out on December 22, 2025. The cause is listed as natural.
- Size
- 58,985 acres
- Contained
- 100%
- Discovered
- July 9, 2025
- Personnel
- 5
Map
Perimeter mapped February 3, 2026 at 1:13 PM MST, 58,985 acres (mixed methods). Point of origin 36.795, -112.380.
The incident
- Size
- 58,985 acres
- Containment
- 100%
- Discovered
- July 9, 2025 at 6:05 PM MST
- Contained
- August 21, 2025 at 2:00 PM MST
- Controlled
- October 7, 2025 at 7:45 AM MST
- Declared out
- December 22, 2025 at 4:20 PM MST
- Cause
- Natural
- Location
- 15 Miles SE from Fredonia, AZ
- County
- Coconino County
- State
- Arizona
- Nearest city reported
- Fredonia
- Protecting agency
- BLM
- Jurisdiction
- BLM
- Land ownership at origin
- BLM
- Personnel assigned
- 5
- Incident management
- Type 4 IC, Type 4 Incident
- Primary fuel
- Timber (Grass and Understory)
- Estimated cost to date
- $20,710,000
- Incident type
- Wildfire
- Unique fire identifier
- 2025-AZASD-000294
- IRWIN identifier
- B17A9902-EDF0-4D8D-96B4-5F09080CC620
Growth
Mapped area at the last perimeter of each day, from July 11, 2025 (8,641 acres) to February 3, 2026 (58,985 acres). The largest one-day growth was 21,033 acres, mapped July 13, 2025.
| Day | Acres | Change |
|---|---|---|
| July 11, 2025 | 8,641 | |
| July 12, 2025 | 19,153 | +10,512 |
| July 13, 2025 | 40,186 | +21,033 |
| July 14, 2025 | 49,357 | +9,171 |
| July 15, 2025 | 52,990 | +3,633 |
| July 16, 2025 | 58,559 | +5,569 |
| July 18, 2025 | 58,631 | +72 |
| July 19, 2025 | 58,639 | +8 |
| July 20, 2025 | 58,842 | +203 |
| July 24, 2025 | 58,980 | +138 |
| February 3, 2026 | 58,985 | +5 |
Weather in the area
This fire is no longer listed as current. The forecast for Fredonia, AZ covers the area today.
Nearby
Arizona wildfires today Wildfires of 2025 All current fires
Incident record from the National Interagency Fire Center’s Wildland Fire Interagency Geospatial Services (WFIGS), as the incident’s managers report it; last updated February 3, 2026 at 1:13 PM MST. Identifier 2025-AZASD-000294.