Skip to content
worldfires
US · United States · →

Cortez Fire, July 2017 Eureka

Out · last measured on 8 Jul 2017

The fire started on 8 July 2017 in Eureka, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 737 hectares, spread across a single county.

It is the 178th largest in Nevada since 2016 (of 237 with a page). Number 461 in United States in 2017, of 619.

Compare with…

We have the official perimeter (MTBS / NIFC) for this fire, but the VIIRS sensors did not capture it in enough detail: no day-by-day evolution, but the split by county is there.

Burnt area
737ha
official perimeter (MTBS / NIFC)
Duration
1day
8 Jul 2017 – 8 Jul 2017
Counties hit
1
counties
Started on
8 Jul
2017
Danger at start
58
Extreme · FWI index

Where it burned

The weather it burned in

38°high
32km/h · peak gust
8%lowest humidity

It had gone 18 days without rain (1 mm or more) when it started.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

How big is it?

10 km
It burned the equivalent of 0.5% of the area of London (7.4 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each county

  1. Eureka where it started
    742 ha
    0.1 %

Burnt area inside each county, from crossing the official perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.

The weather day by day

ECMWF ERA5 reanalysis at the fire location, the standard reference for past weather, and the Canadian Fire Weather Index (the same system Copernicus uses), computed by WorldFires from that data. Days after the fire run until the first rain.

Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

Day High Min. humidity Peak gust Rain Danger (FWI)
8 Jul 37.6 °C 8 % 32 km/h 0.0 mm Extreme 58
9 Jul after 36.9 °C 12 % 34 km/h 0.0 mm Extreme 66
10 Jul after 35.2 °C 11 % 47 km/h 0.0 mm Extreme 68
11 Jul after 34.5 °C 5 % 37 km/h 0.0 mm Extreme 60
12 Jul after 34.9 °C 9 % 27 km/h 0.0 mm Extreme 54
13 Jul after 35.1 °C 7 % 23 km/h 0.0 mm Very high 50
14 Jul after 36.4 °C 14 % 23 km/h 0.7 mm Very high 42
15 Jul after 36.6 °C 9 % 39 km/h 0.0 mm Extreme 57
16 Jul after 35.1 °C 12 % 40 km/h 0.0 mm Extreme 60
17 Jul after 34.5 °C 7 % 46 km/h 0.0 mm Extreme 65
18 Jul after 35.4 °C 6 % 36 km/h 0.0 mm Extreme 61

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 1 Jul 2017
After · 15 Jul 2017

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

Other fires nearby

All fires in United States ›

Frequently asked questions

How long did the Cortez Fire last?
It burned between 8 July 2017 and 8 July 2017: 1 day, according to the start date recorded by United States agencies (MTBS / NIFC) and the heat detections seen by satellite.
How much area did it burn?
The official perimeter published by United States agencies (MTBS / NIFC) is 737 hectares (7.4 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered Eureka (742 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 37.6 °C, humidity dropped to 8 % and gusts hit 32 km/h. The fire danger index (FWI) reached 58, class Extreme.
Where does this data come from?
From the official burnt perimeter of United States agencies (MTBS / NIFC, public domain), NASA FIRMS VIIRS hotspots and the administrative boundaries of United States. It is not an official report.

Where to verify it

A satellite detection is not an official report. Final figures and the fire’s status are published by each country’s emergency service.

Emergency number: 911 · Emergency number and official warnings ›

Satellite cross-check

History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.

No changes since 24 October 2026.

RSS Changes to this page

Does something look wrong on this page?

This page is built from satellite data and official records, and it sometimes gets things wrong: the wrong dates, the wrong town, two fires merged into one, or something that was not a wildfire at all. If you know this fire first-hand (you live nearby, saw it, fought it or reported on it), tell us what really happened and we will check it.

Report an error
What do you think is wrong?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 911.

How we know this
  • Perimeter: MTBS (US Geological Survey and US Forest Service), official.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. No Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.
  • Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.

How we build fire pages: methodology ›

Where this data comes from

The perimeter is official and in the public domain. For past years it comes from MTBS (Monitoring Trends in Burn Severity), run by the U.S. Geological Survey and the USDA Forest Service, which map it on Landsat and Sentinel-2 imagery. For the current and last year it comes from WFIGS at the National Interagency Fire Center (NIFC): incident perimeters mapped by fire crews, aircraft and imagery. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. County boundaries come from geoBoundaries ADM2 (Public Domain). The area per county is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from official figures.