Virginia Mountains Complex
The Virginia Mountains Complex was reported on July 29, 2016 in Washoe County, Nevada and burned 59,727 acres. It is 100 percent contained.
- Size
- 59,727 acres
- Contained
- 100%
- Discovered
- July 29, 2016
- Personnel
- 4
Radar
Reflectivity now over Virginia Mountains Complex. Open it to see fires and the fire weather outlook on the map.
Radar mosaic and map layers from NOAA MRMS and NOAA Storm Prediction Center. Boundaries from the Iowa Environmental Mesonet.
Map
Perimeters are mapped for the fires in the complex; the map shows each one. Point of origin 39.985, -119.873.
The incident
- Size
- 59,727 acres
- Containment
- 100%
- Discovered
- July 29, 2016 at 8:58 AM PDT
- Cause
- Undetermined
- County
- Washoe County
- State
- Nevada
- Nearest city reported
- Reno, NV
- Protecting agency
- BLM
- Personnel assigned
- 4
- Incident management
- Type 4 IC
- Primary fuel
- Short Grass (1 foot)
- Estimated cost to date
- $8,000,200
- Incident type
- Complex
- Unique fire identifier
- 2016-NVCCD-030409
- IRWIN identifier
- 5D1D231A-D674-4150-89DB-A955CED736D4
Fires in the Virginia Mountains Complex4
| Fire | County | Acres | Contained | Discovered |
|---|---|---|---|---|
| Tule Fire | Washoe | 36,142 | 100% | Jul 28, 2016 |
| Anderson Fire | Washoe | 16,284 | 100% | Jul 29, 2016 |
| Sage Fire | Washoe | 4,238 | 100% | Jul 28, 2016 |
| Seven Lakes Fire | Washoe | 3,063 | 100% | Jul 28, 2016 |
Weather in the area
This fire is no longer listed as current. The forecast for Doyle, CA covers the area today.
Nearby
- Doyle, CA13 miles west of the fire’s origin
- Cold Springs, NV22 miles south of the fire’s origin
- Lemmon Valley, NV24 miles south of the fire’s origin
- Spanish Springs, NV25 miles south of the fire’s origin
- Golden Valley, NV26 miles south of the fire’s origin
- Sun Valley, NV27 miles south of the fire’s origin
Nevada wildfires today Wildfires of 2016 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 11, 2020 at 10:25 AM PST. Identifier 2016-NVCCD-030409.