Skip to content
worldfires
US · United States · –

Grouse Creek Fire, July 2019 Yukon-Koyukuk

Out · last detection 1 Aug 2019, 23:32 UTC

The fire started on 10 July 2019 in Yukon-Koyukuk, United States, and satellites saw it burning for 23 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 20,118 hectares, spread across a single county.

It is the 52th largest in Alaska since 2016 (of 472 with a page). Number 19 in United States in 2019, of 367.

Burnt area
20,118ha
official perimeter (MTBS / NIFC)
Duration
≈ 23days
10 Jul 2019 – 1 Aug 2019
Counties hit
1
counties
Started on
10 Jul
2019
Heat detections
3,054
in a single hotspot: 181 MW
Danger at start
29
High · FWI index
Average daily power
1.3GW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 10 Jul1 Aug
1 Aug 2019

How it evolved, day by day

11 Jul 2019 · 331 MW · 37 12 Jul 2019 · 227 MW · 61 13 Jul 2019 · 195 MW · 29 14 Jul 2019 · 2,777 MW · 195 15 Jul 2019 · 1,100 MW · 183 16 Jul 2019 · 333 MW · 120 17 Jul 2019 · 72 MW · 44 18 Jul 2019 · 1,597 MW · 128 19 Jul 2019 · 632 MW · 139 20 Jul 2019 · 220 MW · 149 21 Jul 2019 · 1,120 MW · 72 22 Jul 2019 · 4,990 MW · 571 23 Jul 2019 · 3,889 MW · 589 24 Jul 2019 · 934 MW · 148 25 Jul 2019 · 3,358 MW · 558 26 Jul 2019 · 669 MW · 30 1 Aug 2019 · 2 MW · 1
11 Jul 15 Jul 19 Jul 22 Jul 1 Aug

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

28°high
53km/h · peak gust
38%lowest humidity

It had gone 16 days without rain (1 mm or more) when it started. Rain came after the fire: 24.4 mm on 2 Aug.

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 13% of the area of London (201 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. Yukon-Koyukuk where it started
    20,341 ha reached on 11 Jul
    0.0 %

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.

People and buildings inside the perimeter

GHSL 2020
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, satellite-based estimate).

This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned.

Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu

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)
10 Jul 28.4 °C 38 % 30 km/h 0.0 mm High 29
11 Jul 26.6 °C 46 % 27 km/h 0.8 mm High 23
12 Jul 20.4 °C 70 % 28 km/h 8.4 mm Very low 0
13 Jul 24.2 °C 56 % 34 km/h 3.7 mm Very low 0
14 Jul 25.1 °C 52 % 26 km/h 1.1 mm Very low 3
15 Jul 25.1 °C 49 % 25 km/h 3.7 mm Very low 2
16 Jul 23.2 °C 54 % 20 km/h 6.0 mm Very low 2
17 Jul 24.3 °C 64 % 20 km/h 5.8 mm Very low 0
18 Jul 24.2 °C 58 % 32 km/h 5.7 mm Very low 1
19 Jul 20.1 °C 60 % 36 km/h 0.1 mm Very low 1
20 Jul 19.7 °C 58 % 53 km/h 0.0 mm Very low 4
21 Jul 23.2 °C 53 % 41 km/h 0.0 mm Low 8
22 Jul 25.0 °C 48 % 13 km/h 0.0 mm Low 6
23 Jul 27.8 °C 43 % 21 km/h 0.0 mm Low 10
24 Jul 24.8 °C 57 % 36 km/h 2.7 mm Low 10
25 Jul 22.0 °C 57 % 29 km/h 0.0 mm Very low 2
26 Jul 18.5 °C 70 % 28 km/h 8.0 mm Very low 1
27 Jul 19.4 °C 64 % 17 km/h 4.9 mm Very low 0
28 Jul 18.0 °C 75 % 22 km/h 7.3 mm Very low 0
29 Jul 20.9 °C 64 % 34 km/h 2.4 mm Very low 0
30 Jul 20.4 °C 45 % 31 km/h 0.0 mm Very low 1
31 Jul 21.6 °C 51 % 48 km/h 2.5 mm Very low 5
1 Aug 18.5 °C 47 % 48 km/h 1.0 mm Very low 1
2 Aug after 17.5 °C 67 % 77 km/h 24.4 mm Very low 0

Its twins: fires that started in the same weather

It started with an FWI of 28.7, a minimum humidity of 38% and 16 days without rain. Fires in the area that started in weather like this since 2016: 14.

FWI at the start 28.7
Minimum humidity 38 %
Days without rain 16
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Tatlanika Fire, June 2026
15,636 ha 1 day FWI 23.1 Min. humidity 37 % 163 km away, in 2026

First rain (1 mm or more) after it ended: 7.6 mm on 22 Jun.

What happened to them

Fires in the area that started in similar weather: 14. With fewer than 15 we give no figures: they would be more noise than signal.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

24.4 mmfirst rain
2 Augthe day after it ended
53km/h · max. gust

It was considered over on 1 Aug, and on 2 Aug 24.4 mm fell. We do not know whether the rain or the firefighters put it out.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2016.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

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

Before · 3 Jul 2019
After · 8 Aug 2019

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

Detections table · 3,054Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
Date and timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in United States

Frequently asked questions

How long did the Grouse Creek Fire last?
The official perimeter only gives the start date (10 July 2019). The end comes from the heat detections inside the perimeter: it burned until 1 August 2019 (23 days from 10 July 2019), the last day with detections before more than 10 days in a row without any, so it is approximate.
How much area did it burn?
The official perimeter published by United States agencies (MTBS / NIFC) is 20,118 hectares (201.2 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered Yukon-Koyukuk (20,341 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 28.4 °C, humidity dropped to 38 % and gusts hit 53 km/h. The fire danger index (FWI) reached 29, class High.
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.

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.
  • The official perimeter has no end date: the end is the last day with VIIRS detections inside the perimeter before a gap of more than 10 days (150 days at most), so it is approximate. 3,054 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.
  • Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2020, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.

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.